Altova Mailing List Archives

Re: [xml-dev] RE: Formatting Processing Instructions

From: Michael Kay <mike@--------.--->
To: xml-dev@-----.---.---
Date: 2/23/2012 9:33:00 AM
On 22/02/2012 20:30, David Lee wrote:
> I for one have NEVER used a PI nor have ever encountered one nor have 
> ever found any desirable use for one.
I admit to occasional use of PIs. Here are some of the ways I have used 

- metadata in XSLT test stylesheets, where I want confidence that the 
metadata will be thrown away by the XSLT processor. I could use a 
top-level data element, but that would involve declaring a namespace, 
and the extra namespace could in theory disturb the test.

- an alternative to entity references or numeric character references 
that will survive XSLT transformation without making the document 
DTD-invalid or schema-invalid. Doesn't work in attributes, of course.

- an instruction to the XSLT processor, like <?generate-glossary-here?>. 
Shouldn't this be an element? Perhaps yes; I'm doing this where I 
control the XSLT processing but not the schema/DTD, so it's a form of 
tag abuse. But it would probably be wrong to add the element to the 
schema/dtd, because there are really two content models here: the "raw" 
content and the "preprocessed" content, and the PI appears only in the 
raw content, while the schema describes the structure of the 
preprocessed content. I'm using a PI so that I can use one DTD/schema 
for both content models.

And I would defend it as better than using dummy content like

<div id="glossary">

which I have also been known to do.

Michael Kay


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 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.