[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Re: xmlns empty string
- From: Ran <ran256@g...>
- To: xml-dev@l...
- Date: Wed, 20 Dec 2006 13:08:25 -0800
Thanks Mike, Noah,
Pardon my newbie question on namespaces from previous.
I use <include /> for most my xsds since I do not need to come up and deal with so many different namespaces. What is your suggestion on using <include />
v.s. <import /> ?
ran
On 12/20/06, noah_mendelsohn@u... <
noah_mendelsohn@u...> wrote:Michael Kay writes:
> I forget how chameleon namespaces interact with
> elementFormDefault - it's a facility I never use, so I would > have to look it up.
OK, so I was feeling guilty about not remembering either, so I looked it up. From [1] (in which SII' is the schema document doing the including):
3.2 If clause 2.3 above is satisfied [I.e. if the targetNamespace of the included schema document is missing...Noah] , then the schema corresponding to the <include>d item's parent <schema> must include not
only definitions or declarations corresponding to the appropriate members of its own [children], but also components identical to all the ·schema components· of I, except that anywhere the ·absent· target namespace name
would have appeared, the ·actual value· of the targetNamespace [attribute] of SII' is used. In particular, it replaces ·absent· in the following places: 3.2.1 The {target namespace} of named schema components, both at the top
level and (in the case of nested type definitions and nested attribute and element declarations whose code was qualified) nested within definitions; 3.2.2 The {namespace constraint} of a wildcard, whether negated or not;
In case that for some reason that seems unclear, I'll translate: you can mostly assume that the included schema document behaves as if it did have a targetNamespace corresponding to that of the including schema document.
Specifically, this is true for "nested attribute and element declarations that have as their code "qualififed", which are the ones in question. If your elementForm is qualified, then the namespace used will be that of the
including schema document. That's my reading anyway.
Noah
[1] http://www.w3.org/TR/2004/PER-xmlschema-1-20040318/#compound-schema
-------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 --------------------------------------
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
RSS 2.0 |
|
Atom 0.3 |
|
|
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|