OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: System URIs


John Cowan wrote:
>For example, the system ids "http://example.org/étude" (unnormalized
>URI) and "http://example.org/%C3%A9tude" (normalized URI) mean exactly
>the same thing, and should match either form as a catalog entry.

John, just to make this absolutely clear, are you saying that the following
entity declarations:-

<!ENTITY etude1 SYSTEM "http://example.org/étude">
<!ENTITY etude2 SYSTEM "http://example.org/%C3%A9tude">

...should each match all of the following catalog entries:-

<system systemId="http://example.org/%C3%A9tude" uri="etude.ent"/>
<system systemId="http://example.org/étude" uri="etude.ent"/>
<delegateSystem systemIdStartString="http://example.org/%C3"
catalog="example.cat"/>

If this is what you are proposing [I got the impression that Paul was
against this] then the XML Catalog specification needs clarifying.  It needs
to point out that both sides need to be %-escaped before a comparison is
made.  If the XML Processor has already %-escaped the system identifier,
then the catalog resolver only has to %-escape the systemId and
systemIdStartString.

In the case of URIs, I don't think there is anything in XML 1.0 or
Namespaces describing %-escaping.  So the catalog resolver will have to
%-escape both sides if you want the following namespace declaration to match
the uri catalog entry:-

<a xmlns:a="http://example.org/étude"/>
<uri name="http://example.org/%C3%A9tude" uri="etude"/>

Is this what you had in mind?

Regards
Rob Lugt
ElCel Technology




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC