This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4922 - modelGroups: redefined schemaLocation not present
Summary: modelGroups: redefined schemaLocation not present
Status: RESOLVED INVALID
Alias: None
Product: XML Schema Test Suite
Classification: Unclassified
Component: Microsoft tests (show other bugs)
Version: 2006-11-06
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Henry S. Thompson
QA Contact: XML Schema Test Suite mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-08 14:12 UTC by Michael Chan
Modified: 2007-08-09 13:13 UTC (History)
0 users

See Also:

Attachments

Description Michael Chan 2007-08-08 14:12:37 UTC 
testcases affected:
msData/modelGroups/mgO020.xsd
msData/modelGroups/mgP041.xsd
msData/modelGroups/mgP050.xsd

Testcases are trying to redefine a group that is originated from foo.xsd.  foo.xsd does not exist and xml4c has thrown a warning instead of an error.  The schema spec is open in this issue because it says that these are only 'hints'.  The processor/parser have a lot of freedom in how this type of issue is handled.  

Currently, it seems that xml4c will handle this type of issue with a warning instead of an error.  Therefore, a scenario that tests for warnings should be used to test the above testcases.
Comment 1 Henry S. Thompson 2007-08-08 15:31:56 UTC 
I think this comment is mistaken -- schemaLocation is a hint in instance documents, and on xs:import, but not on xs:include or xs:redefine.  The spec ("Schema Representation Constraint: Redefinition Constraints and Semantics", http://www.w3.org/TR/xmlschema-1/#src-redefine) says "1 If there are any element information items among the [children] other than <annotation> then the ·actual value· of the schemaLocation [attribute] must successfully resolve."  As the most recent PWD of XML Schema 1.1 clarifies, that "must" is an RFC2119 MUST.