Re: [xsl] Long Namespaces

Subject: Re: [xsl] Long Namespaces
From: "James Fuller" <james.fuller.2007@xxxxxxxxx>
Date: Thu, 7 Jun 2007 20:45:14 +0200
I would rather have longer and more descripitve element and attributes
then namespace prefixes.....saves on keystrokes having something
shorter and you will reduce verbosity of a document if you avoid
longer then 3-4 character namespace prefixes.

As Joe said, it doesn't matter as these prefixes only have relevance
in that particular document...that being said, people tend to use the
same prefix.

If you have a deep inheritence hierarchy you might find having a long
descriptive prefix in the master document useful......though even then
I would advise that this type of question is typically answered by how
you generate the XML in question (e.g. using an editor, manual, or is
it the output of some process).

gl, Jim Fuller

On 6/7/07, Karl Stubsjoen <kstubs@xxxxxxxxx> wrote:
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.
> Joe

Current Thread