Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Hiding namespace prefixes in the instance document

From: "Michael Kay" <mike@--------.--->
To: "'Antti Sissonen'" <antti_sissonen@-------.--->, <xmlschema-dev@--.--->
Date: 1/4/2006 2:32:00 PM
As George says, you need to concentrate on deciding which namespace the
elements are in; prefixes are purely cosmetic.

I think it's best when using schemas, in general, to use namespaces and
stick to them. I'm no fan of chameleon includes or redefines, they only lead
to confusion in the long run. You quickly find yourself having to write
transformations to move documents into and out of namespaces and it just
gets more and more messy.

Michael Kay
http://wwww.saxonica.com/
 

> -----Original Message-----
> From: Antti Sissonen [mailto:antti_sissonen@h...] 
> Sent: 04 January 2006 11:45
> To: mike@s...; xmlschema-dev@w...
> Subject: RE: Hiding namespace prefixes in the instance document
> 
> 
> What I meant was not having namespace prefixes in the 
> instance document 
> since in this particular case the xml instance presents 
> business content and 
> the element naming should be exact.
> So if I am using a common element coming from a common 
> component schema it 
> should look like this:
> <Schema>
>   <Aggregate>
>     <MaterialBatchIdentifier>
>     ...
> 
> instead of:
> <Schema>
>   <Aggregate>
>     <common:MaterialBatchIdentifier>
> 
> Does that help?
> 
> I've understood that I can get rid of prefixes by using the 
> correct design 
> (venetian blind) and the default namespace definition 
> (xmlns="foo", not 
> xmlns:foo="foo") if only one namespace is declared for the 
> instance. But 
> then if I'd like to have a separate namespace for the common 
> components I 
> run out of options. Thus, I've concluded that maybe I just 
> have to have 
> common component schema in no namespace and use include to 
> have it available 
> (chameleon).
> If the idea of the schema architecture is to assure that the 
> same name will 
> not be used for different things the chameleon design would 
> support/force 
> it. What is it that I'd lose if I switch from import to include?
> 
> Rgrds,
> 
> Antti
> 
> >
> > > I have a schema that imports another one. I'm trying to keep
> > > the namespace
> > > prefixes hidden in the xml instance
> >
> >Sorry, I've no idea what you mean. What does a "hidden 
> prefix" look like?
> >
> >Michael Kay
> >http://www.saxonica.com/
> >
> >
> 
> 
> 



From bkbonner@g... Thu Jan 05 03:41:51 2006
Received: from wiggum.w3.org ([128.30.52.23])
	by frink.w3.org wi


transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent