This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: ***********Transformation of an XML document containing a default namespace ************



In my case I was trying to fore the output to use the default
namespace (the zero length prefix) though my XSLT transformation did
not use the default namespace for the elements that would be output.

I needed for the output of the XSLT to not have a prefix because the
HTML and SVG viewers I was using were not XML namespace aware.

The XSLT I had written used the default namespace for the XSLT
namespace (http://www.w3.org/1999/XSL/Transform) since XSLT elements
were the predominant content of the stylesheet and that would make it
easier to type and to read.  The literal result elements were prefixed
in accord with a declaration for the SVG namespace
(http://www.w3.org/2000/svg).  I was unable to figure out how to get
the output to not use a prefix.

The problem is that there are three different prefix->namespace
mappings:  one in the source document, one in the stylesheet, and one
for thge output document.  The first of these is controlled by
namespace delcarations in the source document and the decond by those
in the stylesheet.  There doesn't appear to be a way to control what
prefixes are used in the output.

The less practical of you will argue that it doesn't matter as long as
the prefixes which are used are declared to be mapped to the proper
namespaces.  This fails to take into account that that output might
later be processed by software which is not namespace aware.  Also,
one might want the output document to use the zero length namespace
prefix for compactness or for ease of reading by a human.



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]