[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Unparsed entities and public identifiers
At 10:38 2000 07 17 +0100, Richard Light wrote: >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? It's relatively feasible (for a Java programmer) to add catalog support to something like XT. See below for more. >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. I agree, which is why I've been pushing catalog support whenever I can. As you mention, the obvious choice is the catalog support defined by the OASIS (née SGML Open) Entity Management Catalog Technical Resolution TR9401:1997 [1]. See Norm's article [2] for both a good description of the issues and for a pointer to some Java classes that implement both the TR9401:1997 catalogs and XML Catalogs [3]. paul [1] http://www.oasis-open.org/html/a401.htm [2] http://www.arbortext.com/Think_Tank/Norm_s_Column/Issue_Three/issue_three.html [3] http://www.ccil.org/~cowan/XML/XCatalog.html XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|