[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
RE: [xml-dev] RE: Compelling use case for XML Catalogs?
- From: "Tony Graham" <tgraham@mentea.net>
- To: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
- Date: Mon, 13 Jun 2011 18:04:10 +0100 (IST)
On Mon, June 13, 2011 4:24 pm, Costello, Roger L. wrote:
> John Cowan responded to my post:
>
>> Does XML Catalog have the ability to express this:
>>>
>>>[snip various conditional things]
>>>
>>> No, of course not. Catalogs can only express one thing: when you
>>> see this URI, use this other URI instead. (And ditto for public
>>> identifiers.)
>
> The inability of XML Catalog to check for the presence of correct URLs
> seems like a significant limitation.
XML Catalogs are just data. Throwing an error in the absence of a match,
forcing validation against a specified schema, and prohibiting network
access when validating are all things you would do in software.
See, e.g., the '--dtdvalid', '--relaxng', '--schema', '--schematron', and
'--nonet' options of 'xmllint' [1]. 'xmllint' doesn't complain if the
document doesn't refer to a URI that's in a catalog, but you could modify
it to do so if you wanted, and you could do much the same as 'xmllint' in
any XML processor for which you had the source code (if it doesn't do it
already that is).
Regards,
Tony Graham tgraham@mentea.net
Consultant http://www.mentea.net
Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
XML, XSL FO and XSLT consulting, training and programming
[1] http://www.xmlsoft.org/xmllint.html
The help for the under-documented '--nonet' option is:
refuse to fetch DTDs or entities over network
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]