- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 22 Jan 2007 19:19:21 +0000
- To: www-xml-schema-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4269 Summary: Element strictly assessed but not assessed Product: XML Schema Version: 1.0/1.1 both Platform: All URL: http://lists.w3.org/Archives/Public/www-xml-schema- comments/2005JanMar/0034.html OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Structures: XSD Part 1 AssignedTo: cmsmcq@w3.org ReportedBy: sandygao@ca.ibm.com QAContact: www-xml-schema-comments@w3.org See: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2005JanMar/0034.html According to constraint "Schema-Validity Assessment (Element)" in 3.3.4 of the structure spec, "So for an element information item's schema-validity to be assessed all of the following must be true: ..." and "[Definition:] If either case of clause 1 above holds, the element information item has been strictly assessed." Consider <parent> <child/> </parent> where <parent> has a corresponding element declaration or type definition (which means it's strictly assessed), but <child> matches a skip wildcard (which means it's not assessed). Now for <parent>, clause 1 of "Schema-Validity Assessment (Element)" is satisfied, but clause 2 is not. The result is it's strictly assessed, but not assessed. Clearly not correct to any English speaker. "Assessment attempted" has none -> partial -> full. It seems that the above "to be assessed" actually meant "to be fully assessed", which is also the fix I would offer.
Received on Monday, 22 January 2007 19:19:31 UTC