Re: [xsl] Long Namespaces

Subject: Re: [xsl] Long Namespaces
From: "Joe Fawcett" <joefawcett@xxxxxxxxxxx>
Date: Thu, 7 Jun 2007 19:45:32 +0100
I think it's one of those personal preferences such as general code styles and whether you use table aliases in SQL etc.
For me it depends on who I thought would be reading the raw XML. The only technical reason I can see for using one over the other is to reduce overall message size for transmission, but if that's a serious concern you're probably shouldn't be using XML :)
I did once have a situation whereby the buffer that held the XML could only contain 255 characters so we used single letter element names and no namespace declarations.


----- Original Message ----- From: "Karl Stubsjoen" <kstubs@xxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, June 07, 2007 7:36 PM
Subject: Re: [xsl] Long Namespaces

Ok, so I messed up that post ; )
I meant to ask about verbose prefixes!  So an example:

xmlns:myVerbosePrefix = "";

Anyone going that route?  Reason I ask, is here at work, my colleagues
are not so familiar with XSLT.  They did not like 3 letter prefixes,
said it was confusing.


On 6/7/07, Joe Fawcett <joefawcett@xxxxxxxxxxx> wrote:
----- Original Message -----
From: "Karl Stubsjoen" <kstubs@xxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, June 07, 2007 6:58 PM
Subject: [xsl] Long Namespaces

> Is there any creed that suggests that namespace decelerations are > either bad or shunned upon? It seems that 3 letter namespaces are the > norm. Is anyone using verbose namespace declarations regularly? > > Karl.. > > I presume you mean "declarations" :)

You appear to be confusing the namespace URI or name with its prefix. The
idea is that namespace URIs are globally unique, they are often similar to
URLs because that way you can use your domain and assure uniqueness,
although there's nothing to stop you creating a namespace such as if you wish, it's a "gentlemen's agreement".
The prefix is a way to save writing the long URI and just holds for the
lifetime of the document, maybe even less than that if you re-define the
prefix mappings. So you can say that "ns" actually represents
http:/// and use that prefix in a
number of situations, e.g.. in an XPath expression. You often this mapping
with xmlns:ns="http:///"; but this
only holds until the URI is mapped to a different prefix or the process
finishes. So in an XML document you could map "ns1" to the URI whereas in an
XSLT you use to transform it you could map to "ns2" instead.


Current Thread