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: Issue: do we map to URIs or URI References?


As part of my general cleanup to the document, I need to tackle
carefully the issue of what we map to and from. My first inclination
was to say that we map from external identifiers and URIs to URI
references.

However, after further consideration, I'm not sure that's right.
I think we map URIs to URIs, not URI references.

In other words, I think these should be non-conformant:

  <system systemId="http://example.com/foo"
          uri="http://example.com/bar#xyz"/>

  <uri name="http://example.com/someResource"
       uri="http://example.com/somewhereElse?id=3"/>

My reasoning is that an application might very well strip off a
fragment identifier, grab a resource (going through a catalog) and
then search for the fragment identifier inside that resource. Getting
back a resource with a fragment identifier from the catalog would be
confusing at best and broken at worst.

Comments?

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM   | It is so comic to hear oneself called old,
XML Standards Engineer | even at ninety I suppose.--Alice James
Technology Dev. Group  | 
Sun Microsystems, Inc. | 


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


Powered by eList eXpress LLC