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]

Unparsed entities and public identifiers



Hi,

The XSLT Recommendation (Section 3.3, Unparsed Entities) contains the
following phrase:

"The XSLT processor may use the public identifier to generate a URI for
the entity instead of the URI specified in the system identifier."

Do any of the extant XSLT processors take advantage of this opportunity?  

One obvious approach would be a command-line option to specify an OASIS
Catalog file, mapping public to system identifiers.  Public identifiers
could be looked up in this file, with the system identifier being used
(as it must) if no match is found for the public identifier.

Richard Light.

Richard Light
SGML/XML and Museum Information Consultancy
richard@light.demon.co.uk


 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]