The catalog has public, system and uri mappings. I think that this
should be handled in the same way it is handled now the XML Schema
association.
Currently we use the Apache resolver and set a catalog resolver to the
parser, that is as an entity resolver, so schema locations will be
resolved using the system mappings.

Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


Bob Foster wrote:
> George Cristian Bina wrote:
>
>>There is not necessary to change the PI, you can have the public schema
>>location there and if the tool is XML Catalog aware it will resolve that
>>to a local copy.
>
>
> If the interpretation is that this is a location, then it will be looked
> up by catalog as a URI, not a public identifier. So you'd have to tweak
> your catalog to duplicate all the public references as URI references.
> Or is an implementation expected to send the URx down both paths and see
> if it gets a bite?
>
> Bob Foster
> http://xmlbuddy.com/
>
>
>

> Yahoo! Groups Links
>
>
>

>
>


YAHOO! GROUPS LINKS




Reply via email to