- From: <bugzilla@jessica.w3.org>
- Date: Tue, 08 Mar 2011 15:26:46 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10125 --- Comment #8 from David Ezell <David_E3@VERIFONE.com> 2011-03-08 15:26:45 UTC --- The original bug report asked: >2. As a minimum, there should be a statement somewhere that such elements do >not generate any schema components and do not have to satisfy the (prose) rules >for the XML representation of schema components. Since XMLSpy 2008 does appear to validate <xs:annotation/>, I ran an additional test (obviously MSXML4.0 SP2 need not be tested again). I used this test schema: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:annotation> <xs:appinfo> <xs:element name="e" type="xs:string"/> <e>abc</e> </xs:appinfo> </xs:annotation> <xs:element name="e" type="xs:int"/> </xs:schema> XMLSpy 2008 rejects this schema document, based on the the fact that "e" doesn't match the correct type. This additional test implies, IMO: 1) we could make a statement that schema omponents need not be generated from definitions/declarations inside <xs:annotation/> 2) the contents of <xs:annotation/> will be laxly validated by the currently active set of schemas, including the S4S. In short, if you use the XSD namespace, the item will be validated. No component will created. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 8 March 2011 15:26:47 UTC