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: Catalog requirements

Norman Walsh wrote:

> That's very noble, and I offer my wholehearted support. But I also
> think we need to be practical.

	"We'll argue that point," said Jack.
		-- Frederick Marryat, _Mr. Midshipman Easy_


"Content negotiation", the mechanism for a client to ask a server (or in this
case a resolver) for resource R cast to type T (e.g. "http://www.w3.org"
in XHTML-1.1 format, or in Japanese, or whatever).  The server responds with the
reformatted resource if possible, or if not, a list of the types T1, T2, T3, ...
which it has available.  The client may then re-request or give up.

> | Both to URLs and to URNs (passim).
> URI covers both, doesn't it?

Yes:  <!ENTITY URI "URL or URN">

There is / one art                   || John Cowan <jcowan@reutershealth.com>
no more / no less                    || http://www.reutershealth.com
to do / all things                   || http://www.ccil.org/~cowan
with art- / lessness                 \\ -- Piet Hein

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

Powered by eList eXpress LLC