On 1/25/10 2:17 AM, Peter Mount wrote: > Ok one last one that I can see in Section 6, however this one is not > strictly muc as it's an issue in the schema for XEP-0030. > > In 6.2 Discovering Rooms, example 5 shows how the service can return a > partial list of room by using ResultSet management (XEP-0059). > > The problem here is that in the schema defined in for disco#items > (XEP-0030) it doesn't > allow for any additional elements to be included in the query element, > only 0 or more 'item' elements - however example 5 shows a 'set' > element in the 'http://jabber.org/protocol/rsm' namespace. > > So does disco-items.xsd need changing, and would this be part of the > muc review or should it be done separately? > > In either case the fix would be to add an xs:element to > disco-items.xsd either refering directly to 'set' in the rsm namespace > or as xs:any
Well, *none* of our schemas provide detailed information about extensibility because we assume that everything is extensible. That's one reason why our schemas are descriptive, not normative. Updating all of our schemas to explicitly define extension points would be a big job. Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
