- From: <bugzilla@farnsworth.w3.org>
- Date: Wed, 07 May 2008 14:32:31 +0000
- To: www-xml-schema-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5200 ------- Comment #5 from petexmldev@tech-know-ware.com 2008-05-07 14:32 ------- Over all this looks very good to me. There's just a few things I would like to check before closing it. 1) (The main issue) I don't think it's relevant to discuss attributes when talking about ##definedSibling. Surely an attribute wildcard can never match an already defined attribute sibling anyway. Assuming I haven't missed something (!), it may be appropriate to just remove the bits that mention attributes, or (better?) add a note to say that ##definedSibling is not applicable to the attribute wildcard case. 2) Maybe more of a tool chain issue, but ##definedSibling is not included as part of NotQName in the "XML Representation Summary: any Element" table in 3.10.2. Just to let you know, as I'm not sure whether the above are issues or not, I've left the status as Resolved/Fixed.
Received on Wednesday, 7 May 2008 14:33:07 UTC