Re: Of public and urn:publicid URIs

[Norman Walsh <ndw@nwalsh.com>]

/ dcpleland@ftnetwork.com was heard to say:
| Hi Norm;
| 
| The alternative 'matches' did not show up in what I received.

Sorry, David, I don't understand what you mean. Is your email tool
possibly mangling things in angle brackets because it thinks they're
URLs? The message you quoted back to me is the whole message I sent,
and I don't see anything missing. (Though maybe I'm not seeing the
forest for the trees...)

| Please send so they do.
| 
| Thanks in advance,
| David Leland
| ************************************************************
| ndw@nwalsh.com wrote on 5/11/01 4:54:37 PM
| ************************************************************
| Ok, let's explore what it means if we always interpret urn:publicid
| URIs as public identifiers. Here's a first proposal:
| 
| In an entity resolver:
| 
| 1. If you're only passed a public identifier and it's a urn:publicid URI,
|    convert it to a public id and try that. If resolution fails, look
|    for a public entry that matches the URI form.
| 
|      entityResolve(null, "urn:publicid:foo::bar")
| 
|    matches
| 
|      <public publicid="foo//bar" .../>
| 
|    *and*
| 
|      <public publicid="urn:publicid:foo::bar" .../>
| 
|    but prefers the former.
| 
| 2. If you're passed only a system identifier and it's a urn:publicid URI,
|    convert it to a public id and proceed as if you'd only been given a
|    public ID.
| 
| 3. If you're passed both and the public identifier is a urn:publicid URI,
|    convert it to a public id and proceed. If resolution fails, look for
|    a public entry that matches the URI form.
| 
| 4. If you're passed both and the *system* identifier is a urn:publicid URI,
|    convert it to a public id.
| 
|    a. If the two public identifiers are identical, proceed as if you'd
|       only been given the public identifier.
| 
|    b. If they're different, try each in turn. As per 1.
| 
| In a URI resolver:
| 
| 1. If it's a urn:publicid URI, convert it to a public id and try that.
|    If resolution fails, look for a public entry that matches the URI form,
|    then look for a URI entry that matches the URI form.
| 
|      uriResolve("urn:publicid:foo::bar")
| 
|    matches
| 
|      <public publicid="foo//bar" .../>
| 
|    *and*
| 
|      <public publicid="urn:publicid:foo::bar" .../>
| 
|    *and*
| 
|      <uri name="urn:publicid:foo::bar" ../>
| 
|    in that order.
| 
| Comments?
| 
|                                         Be seeing you,
|                                           norm
| 
| -- 
| Norman.Walsh@Sun.COM   | The greatest of all secrets is knowing how to
| XML Standards Engineer | reduce the force of envy.--Cardinal De Retz
| Technology Dev. Group  | 
| Sun Microsystems, Inc. | 
| 
| ------------------------------------------------------------------
| To unsubscribe from this elist send a message with the single word
| "unsubscribe" in the body to: entity-resolution-request@lists.oasis-open.org
| 
| ___________________________________________________________________________________________________
| Get your free e-mail account with *unlimited* storage at  http://www.ftnetwork.com
| 
| Visit the web site of the Financial Times at  http://www.ft.com
| 
| ------------------------------------------------------------------
| To unsubscribe from this elist send a message with the single word
| "unsubscribe" in the body to: entity-resolution-request@lists.oasis-open.org

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM   | The finest amusements are the most pointless
XML Standards Engineer | ones.--Jacques Chardonne
Technology Dev. Group  | 
Sun Microsystems, Inc. |