ISSUE-39
importing components from another namespace
- State:
- CLOSED
- Product:
- Basic
- Raised by:
- Paul Downey
- Opened on:
- 2006-05-04
- Description:
1) We currently have no basic patterns for importing schema components from another namespace. 2) The 'hint' nature of the xs:import schemaLocation is a source of confusion and interoperability problems 3) There is a common convention of referring to another schema already 'known' to a processor by not providing a schemaLocation attribute. Proposal: Provide the following Basic patterns: <xs:import namespace="{xs:anyURI}" schemaLocation="{xs:anyURI}" /> The schemaLocation attribute when present MUST be a single URI which when dereferenced resolves to a document whose whose root element is "schema" from the namespace "http://www.w3.org/2001/XMLSchema". <xs:import namespace="{xs:anyURI}" /> The absence of a schemaLocation attribute indicates there is a schema document defining components already 'known' to the processor within the current context, e.g. both the importing and imported documents are contained within the same WSDL "types" section.- Related emails:
- ISSUE-39: importing components from another namespace (from dean+cgi@w3.org on 2006-05-04)
- Agenda: XML Schema Patterns for Databinding Telcon 9 May 2006 (from paul.downey@bt.com on 2006-05-05)
- Minutes from XML Schema Patterns for Databinding call 9 May 2006 (from paul.downey@bt.com on 2006-05-09)
- Re: Minutes from XML Schema Patterns for Databinding call 9 May 2006 (from petexmldev@tech-know-ware.com on 2006-05-10)
- ISSUE-68: import patterns (from paul.downey@bt.com on 2006-08-24)
Related notes:
No additional notes.