Why does Doctype change processing of a document

Subjects

•	Home
•	Xalan extension functions
•	Fomatting question serializing DOM with pretty print
•	xalan with pull parser
•	Cannot find the declaration
•	Apache Xalan drop support to run on JRE 1 1 x
•	Why does Doctype change processing of a document
•	Node set to XML string via Java extensions in Xalan J: possible?
•	Templates/Transformers + thread safety???
•	Problem evaluating xpath with muliple prefix with different namespace
•	remove an arbitrary attribute from xsl output
•	Xalan3 XSLT 2 0 XPath 2 0 support?
•	Problem using compiled translets with Xalan !!
•	Xalan and jstl 1 1 problem with transform tag
•	NullPointer in DOM2DTM getLocalName
•	URIResolvers base parameter with xsltc and cascaded imports
•	Performance problem for Xalan J on intel dual core
•	Standard libraries in JAXP?
•	Serializing a DOM tree to XML file, customize entities replacement
•	Library Conflict Involving BCEL Library
•	A question on how users are using <xsl:message >
•	Kevin Cormier as a new Apache Xalan J committer
•	Struggling to iterate over tokenized string
•	Xalan count() trouble
•	Problem with recursive xpath
•	Error when switching to java 1 5
•	document( ' ')
•	Problem with Xalan2 7 0 transformation
•	cr/lf options
•	entity encoded XML
•	can xalan transform 2 xml using one xslt?
•	Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
•	xsl transform with cdata section elements
•	xslt parameters not expanded
•	Weird behavior of XPath evaluate()
•	How to avoid <xsl:message > instruction prints stylesheet file informations ?
•	Cannot find SimpleTransform subdirectory after installing Xalan J
•	recover from document not found exceptions
•	jdk1 5 and Xalan jar differences?
•	Performance Issue
•	Error/Bug adding floating point numbers
•	XPathAPI: eval exp using nodes with default namespace
•	modifying xalan to output invalid XML
•	NullPointerException
•	mege two separate xml nodes into one
•	Is this a XALAN document identification bug?
•	is StylesheetRoot really java io Serializable ?
•	transform() fails for DOMSource but succeeds for StreamSource
•	Thoughts on Transformer parameter passing
•	HELP, Xalan and jstl 1 1 problem with transformer
•	Problem with XPath namespace axis?
•	string utils:replace deleting search string if replacement string is an HTML
•	help with enumeration values pls
•	xalan 2 5 1 vs 2 7 performance question
•	How to insert/update in XML document
•	HTML Serialization and Handling of Ampersands in HREF Attributes
•	XHTML link tag stripping
•	SystemId Unknown; Line #24; Column #49; java lang NullPointerException
•	xpath text() help
•	Apostrophe problem with xalan 2 7 0
•	How to set variables in XML document?

Links

Home

Oracle database error code ...

Why does Doctype change processing of a document

Why does Doctype change processing of a document

2007-05-02 - By Erin Harris

Reply: 1 2 3 4 5 6 7

Hi,

> except for the div-element

The div element is a literal element so all of the currently in scope
namespaces get copied to literal elements in the output document (unless
they have already been copied to a parent element). From the XSLT 1.0
Specification, Section 7.7.1 Literal Result Elements (
http://www.w3.org/TR/xslt#literal-result-element)

The created element node will also have a copy of the namespace nodes that
were present on the element node in the stylesheet tree with the exception
of any namespace node whose string-value is the XSLT namespace URI (
http://www.w3.org/1999/XSL/Transform), a namespace URI declared as an
extension namespace (see [14.1 Extension Elements]), or a namespace URI
designated as an excluded namespace.

> And also: I expected to be able to do away with /*[local-name()='html']
> now that xhtml is default namespace. But it doesn't work that way. Why?

The default namespace is not used when matching nodes. From the XPath 1.0
Specification, Section 2.3 Node Tests (
http://www.w3.org/TR/xpath#node-tests):

A QName in the node test is expanded into an expanded-name using the
namespace declarations from the expression context. This is the same way
expansion is done for element type names in start and end-tags except that
the default namespace declared with xmlns is not used: if the QName does
not have a prefix, then the namespace URI is null (this is the same way
attribute names are expanded).

> and try to remove xhtml with exclude-result-prefixes then things turn
> around. div will no longer have a namespace attribute while all the
> copied element do. Misterious really.

The copied elements are in the http://www.w3.org/1999/xhtml namespace in
the input document so the way copy works is that it makes sure that those
elements are also in that namespace in the output document. Because you
excluded the namespace it no longer appears on the <div> element (which I
assume is the parent of the copied nodes) so now it must appear on the
copied nodes themselves since there is no ancestor which has declared the
namespace.

If you don't want any namespace declarations showing up at all in the
output document then you will probably have to do your own copy such as:

<xsl:template match="*">
<xsl:element name="{local-name()}">
<xsl:apply-templates
select="*|@*|text()|processing-instruction()|comment()"/>
</xsl:element>
</xsl:template>

<xsl:template match="@*|text()|processing-instruction()|comment()">
<xsl:copy>
<xsl:apply-templates
select="*|@*|text()|processing-instruction()|comment()"/>
</xsl:copy>
</xsl:template>

Thanks.

Erin Harris

Ferdinand Soethe <ferdinand@(protected)>
02/05/2007 02:14 PM

To
xalan-j-users@(protected)
cc

Subject
[Fwd: Re: Why does Doctype change processing of a document]

-------- Original Message --------
Subject: Re: Why does Doctype change processing of a document
Date: Wed, 02 May 2007 20:03:38 +0200
From: Ferdinand Soethe <ferdinand@(protected)>
To: Larry Trammell <larryt@(protected)>
References:
<22A20AD271DB4949836F85AACBB90A770892A0@(protected)>

Thanks to all of you for helping me understand my mistake. At least I
know what is going wrong now.

Adding xmlns:xhtml="http://www.w3.org/1999/xhtml" to my stylesheet
worked well but added all those ugly xhtml:... to the generated elements.

So I declared xhtml as default namespace
xmlns="http://www.w3.org/1999/xhtml" to make them disappear.

Which worked really well in this template and let to the resulting
document being free of xhtml:...

> <xsl:stylesheet
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="
http://www.w3.org/1999/xhtml"
> version="1.0" >
>
> 
> <xsl:import href="copyover.xsl"/>
>
> 
> <xsl:template match="/*[local-name()='html']">
> <xsl:apply-templates select="*[local-name()='body']"/>
> </xsl:template>
>
> 
> <xsl:template
match="/*[local-name()='html']/*[local-name()='body']">
> <div class="content">
> <xsl:apply-templates/>
> </div>
> </xsl:template>

except for the div-element.
Has anyone the patience to explain?

And also: I expected to be able to do away with /*[local-name()='html']
now that xhtml is default namespace. But it doesn't work that way. Why?

And when I change the style-sheet to

> <xsl:stylesheet
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xhtml="
http://www.w3.org/1999/xhtml"
> version="1.0" exclude-result-prefixes="xhtml">
>
> 
> <xsl:import href="copyover.xsl"/>
>
> 
> <xsl:template match="/*[local-name()='html']">
> <xsl:apply-templates select="*[local-name()='body']"/>
> </xsl:template>
>
> 
> <xsl:template
match="/*[local-name()='html']/*[local-name()='body']">
> <div class="content">
> <xsl:apply-templates/>
> </div>
> </xsl:template>
>

and try to remove xhtml with exclude-result-prefixes then things turn
around. div will no longer have a namespace attribute while all the
copied element do. Misterious really.

Best regards,
Ferdinand Soethe

 <tt>Hi,</tt>
 
 <tt>> except for the div-element</tt>
 
 The div element is a literal element
so all of the currently in scope namespaces get copied to literal elements
in the output document (unless they have already been copied to a parent
element).  From the XSLT 1.0 Specification, Section 7.7.1 Literal
Result Elements (<a href="http://www.w3.org/TR/xslt#literal-result
-element">http://www.w3.org/TR/xslt
#literal-result-element</a>)
 
 The created element node will also have a copy of the
namespace nodes that were present on the element node in the stylesheet
tree with the exception of any namespace node whose string-value is the
XSLT namespace URI (<tt>http://www.w3.org/1999/XSL
/Transform</tt>),
a namespace URI declared as an extension namespace (see <a href="http:/
/www.w3.org/TR/xslt#extension-element">[14.1
Extension Elements]</a>), or a namespace
URI designated as an excluded namespace. 
 
 <tt>> And also: I expected to be able to do away with
/*[local-name()='html'] 
> now that xhtml is default namespace. But it doesn't work that way.
Why? 
</tt>
 The default namespace is not used when
matching nodes.  From the XPath 1.0 Specification, Section 2.3 Node
Tests (<a href="http://www.w3.org/TR/xpath#node-tests">http://www.w3.org/TR/xpath#node-tests</a>
):
 
 A <a href="http://www.w3.org/TR/REC-xml-names#NT-QName"
>QName</a>
in the node test is expanded into an <a href="http://www.w3.org/TR/xpath
#dt-expanded-name">expanded-name</a>
using the namespace declarations from the expression context. This is the
same way expansion is done for element type names in start and end-tags
except that the default namespace declared with <tt>xmlns</tt>
is not used: if the <a href="http://www.w3.org/TR/REC-xml-names#NT-QName
">QName</a>
does not have a prefix, then the namespace URI is null (this is the same
way attribute names are expanded). 

 <tt>> and try to remove xhtml with  exclude-result
-prefixes
then things turn 
> around. div will no longer have a namespace attribute while all the 
> copied element do. Misterious really.</tt>
 
 The copied elements are in the <tt>
http://www.w3.org/1999/xhtml</tt>
namespace in the input document so the way copy works is that it makes
sure that those elements are also in that namespace in the output document.
 Because you excluded the namespace it no longer appears on the <div>
element (which I assume is the parent of the copied nodes) so now it must
appear on the copied nodes themselves since there is no ancestor which
has declared the namespace.
 
 If you don't want any namespace declarations
showing up at all in the output document then you will probably have to
do your own copy such as:
 
 <xsl:template match="*">
   <xsl:element name="{local
-name()}">
     <xsl:apply-templates
select="*|@*|text()|processing-instruction()|comment()"/>
   </xsl:element>
 </xsl:template>
 
 <xsl:template match="@*|text()
|processing-instruction()|comment()">
   <xsl:copy>
     <xsl:apply-templates
select="*|@*|text()|processing-instruction()|comment()"/>
   </xsl:copy>
 </xsl:template>
 
 Thanks.
 
Erin Harris 
 

 
 
 
<table width=100%>
<tr valign=top>
<td width=40%>Ferdinand Soethe <ferdinand
@(protected)>

02/05/2007 02:14 PM
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right>To</div>
<td>xalan-j-users@(protected)
<tr valign=top>
<td>
<div align=right>cc</div>
<td>
<tr valign=top>
<td>
<div align=right>Subject</div>
<td>[Fwd: Re: Why does Doctype change processing
of a document]</table>
 
<table>
<tr valign=top>
<td>
<td></table>
 </table>
 
 
 <tt> 
 
-------- Original Message -------- 
Subject: Re: Why does Doctype change processing of a document 
Date: Wed, 02 May 2007 20:03:38 +0200 
From: Ferdinand Soethe <ferdinand@(protected)> 
To: Larry Trammell <larryt@(protected)> 
References: 
<22A20AD271DB4949836F85AACBB90A770892A0@(protected)> 
 
Thanks to all of you for helping me understand my mistake. At least I 
know what is going wrong now. 
 
Adding xmlns:xhtml="http://www.w3.org/1999/xhtml" to my stylesheet 
worked well but added all those ugly xhtml:... to the generated elements. 
 
So I declared xhtml as default namespace 
xmlns="http://www.w3.org/1999/xhtml" to make them disappear. 
 
Which worked really well in this template and let to the resulting 
document being free of xhtml:... 
 
> <xsl:stylesheet 
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns="http://www.w3.org/1999/xhtml" 
>     version="1.0" > 
>     
>      
>     <xsl:import href="copyover.xsl"/> 
>     
>      
>     <xsl:template match="/*[local-name()='html']"
> 
>         <xsl:apply-templates select="*[local
-name()='body']"/> 
>     </xsl:template> 
>     
>      
>     <xsl:template match="/*[local-name()='html']/*[local
-name()='body']"> 
>         <div class="content"> 
>             <xsl:apply-templates/> 
>         </div> 
>     </xsl:template> 
 
except for the div-element. 
Has anyone the patience to explain? 
 
And also: I expected to be able to do away with /*[local-name()='html'] 
now that xhtml is default namespace. But it doesn't work that way. Why? 
 
And when I change the style-sheet to 
 
> <xsl:stylesheet 
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xhtml="http://www.w3.org/1999/xhtml" 
>     version="1.0" exclude-result-prefixes="xhtml
"> 
>     
>      
>     <xsl:import href="copyover.xsl"/> 
>     
>      
>     <xsl:template match="/*[local-name()='html']"
> 
>         <xsl:apply-templates select="*[local
-name()='body']"/> 
>     </xsl:template> 
>     
>      
>     <xsl:template match="/*[local-name()='html']/*[local
-name()='body']"> 
>         <div class="content"> 
>             <xsl:apply-templates/> 
>         </div> 
>     </xsl:template> 
>     
 
and try to remove xhtml with  exclude-result-prefixes then things
turn 
around. div will no longer have a namespace attribute while all the 
copied element do. Misterious really. 
 
Best regards, 
Ferdinand Soethe 
 
 
</tt>