Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Namespaces best practice in XML

From: "Jon Gorman" <jonathan.gorman@--------->
To:
Date: 4/4/2006 2:36:00 PM
On 4/4/06, tom tom <tomxsllist@xxxxxxxxxxx> wrote:
> Thats what I figured. The reason I ask is that I need this stylesheet to be
> as accessible to as many people as possible. Having to prefix all source
XML
> elements in the XSLT when that prefix doesn't physically exist in the XML
> adds a level of complexity that non-namespace-savvy developers might find
> confusing.

True, but everyone has to learn sometime :).

>
> I guess my alternatives are to remove the namespace declaration from the
> source XML, use a version of HTML which doesn't require a namespace
> declaration or just deal with namespaces!

I've removed the namespace from the source documents in the past when
dealing with similar situations.  Of course, in all of these
sitautions I was usually involved in some way with a classroom
situation where I had non-techie classmates.  (One of the perks of
getting an library degree). It's not the best though since at some
point they will have to deal with it if they want to do some complex
(read cool) applications with xml/xslt.  (And once dealt with it's
pretty painless).

Honestly though, if it's other developers, once they know the basics
of XML I can't imagine namespaces taking that long to wrap their heads
around.  (Playing with xhtml and svg might be the way to go for some
quick examples.)

Jon Gorman


transparent
Print
Mail
Like It
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