- From: <paul.downey@bt.com>
- Date: Mon, 6 Nov 2006 15:12:46 -0000
- To: <ejohnson@epicor.com>
- Cc: <public-xsd-databinding@w3.org>
Hi Erik! > I have noticed very uneven support for elements > of type xs:schema declared within a schema. right, it's not predefined type like say xs:string, but I get your drift .. > Some toolkits say that the Xml Schema namespace is not declared, > but you can’t really import it because there is no real normative > schema for XML Schema that completely conforms to the XML Schema spec. This sounds closely related to SSUE-68: http://www.w3.org/2002/ws/databinding/issues/68/ "xs:import of Schema 1.0 namespace" You could, of course, give a schemaLocation of http://www.w3.org/2001/XMLSchema.xsd (not normative, but as good as, or write one yourself ..) but that's not very desirable I guess. > Some databases (like SQL 2005) simply reject schemas > with element declarations of type xs:schema. sounds like it's not "Basic" then. > I’m not sure what the best solution is other than recommending > toolkits somehow support schemas for documents that themselves contain schemas. that's the main goal of our "Advanced" document, AIUI, a collection of schema patterns in common use that implementers can then ensure they support. I wonder if this is the same as ISSUE-68: http://www.w3.org/2002/ws/databinding/issues/68/ or if we need to open a separate issue. I'll create an issue, "example" and a pattern. Paul
Received on Monday, 6 November 2006 15:17:45 UTC