[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ebxml-msg] Issue73:http://schemas.xmlsoap.org/soap/envelopenamespace
Arvola,
I agree we need all of the current import statements and namespace declarations. Namespaces must be declared where they are used (in both instance and schema documents). Schema documents need the import as well for reasons documented in the excerpt below. About the only thing that might be removable is the ds, xlink and soap namespace declarations in our schema document. (I haven't tried this removal with existing XML parsers but it might work since those namespaces are referenced only within attribute content.) It wouldn't be a worthwhile change at this stage because the declarations in question certainly do no harm and have no effect on users of the schema. On your original question: The new schema you mention is for SOAP 1.2 which remains under development. While SOAP 1.1 is only a Note, it is at least more stable than a draft Recommendation. Further, switching from SOAP 1.1 to 1.2 would be a rather large change to our document. thanx,
Arvola Chan wrote: David: I don't think the import constructs in msg-header-2_0 are redundant. Here is an excerpt from http://www.w3.org/TR/xmlschema-0/#import:The report schema, report.xsd, makes use of the simple type xipo:SKU that is defined in another schema, and in another target namespace. Recall that we used include so that the schema in ipo.xsd could make use of definitions and declarations from address.xsd. We cannot use include here because it can only pull in definitions and declarations from a schema whose target namespace is the same as the including schema's target namespace. Hence, the include element does not identify a namespace (although it does require a schemaLocation). The import mechanism that we describe in this section is an important mechanism that enables schema components from different target namespaces to be used together, and hence enables the schema validation of instance content defined across multiple namespaces. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC