Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xsl] document() function and error-handling

From: "Scott Trenda" <Scott.Trenda@-------->
To:
Date: 1/4/2008 11:35:00 PM
I'm really not trying to beat a nearly-dead horse here (I swear!), but the XML
spec says in '2.6:
[17] PITarget ::= Name - (('X' | 'x') ('M' | 'm') ('L' | 'l'))

If I'm reading it correctly, this only reserves "xml", and variations in
letter cases, for internal use. Whether or not it's bad form to create PIs of
the form <?xml-whatever?> is a separate issue, but the spec doesn't forbid
it.


Like I said before, bad form is bad form and I'll alter it in the end, I just
haven't thought of a better name for it yet. :( And again, thanks for the
responses, they've been really helpful.

~ Scott


-----Original Message-----
From: David Carlisle [mailto:davidc@xxxxxxxxx]
Sent: Friday, January 04, 2008 5:13 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] document() function and error-handling


> Wouldn't
> "xml-" be the most appropriate prefix here?

No, such names are reserved for other use. You can call it result-xml or
_xml_result or pretty much anything you like. Why trample on the
reserved names?

even w3c specs avoid doing this, consider xslt for example an early draft
had an attribute xml-declaration on xsl:output,
but they thought better of it and changed to
omit-xml-declaration
http://www.w3.org/1999/08/WD-xslt-19990813#section-XML-Output-Method

David


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