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


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: URI resolver was Re: RDDL and XML Schemas Proposed Recommendation

Michael Mealling wrote:

> > > > Jonathan Borden wrote:
> >
> > as i said. per RFC 2396 when you resolve a URI you get back an
> entity not a
> > resource. you are conflating resource and entity.
> Oh lordy be carefull here. RFC 2396 defines the term Resource. Are you
> using its definition or something else? Its kind of buried in the
> semantics but RFC 2396 defines a Resource as something that is bound
> to a URI.

Just to be clear, the binding of a resource to a URI need _not_ depend on
network resolution. From RFC 2396:

         A resource can be anything that has identity.  Familiar
         examples include an electronic document, an image, a service
         (e.g., "today's weather report for Los Angeles"), and a
         collection of other resources.  Not all resources are network
         "retrievable"; e.g., human beings, corporations, and bound
         books in a library can also be considered resources.

         The resource is the conceptual mapping to an entity or set of
         entities, not necessarily the entity which corresponds to that
         mapping at any particular instance in time.  Thus, a resource
         can remain constant even when its content---the entities to
         which it currently corresponds---changes over time, provided
         that the conceptual mapping is not changed in the process.

Let me emphasize the statement: "The resource is the conceptual mapping ..."
> Also, you may be using the term 'resolve' in a much more
> constrained sense
> than Justin is.  IMHO, any time you find out some information about a URI
> then you have just done the act of resolution. When I look in my
> local cache in
> my web browser that is resolution. When my entity resolver looks
> in its local catalog, that is resolution. True, many URIs were designed
> in a way that makes authoritative, global resolution impossible (the OID
> URN namespace I defined in RFC 3061 for example). But that doesn't mean
> that resolution in general is not possible...

Those example uses of the term "resolution" are fine but don't support the
statement that "any time you find out some information about a URI then you
have just done the act of resolution". I make a big distinction between URI
resolution and looking up some information about a URI which I am using as a

> >
> > Suppose this RDF is published by Amazon. And if I resolved this URN via
> > Amazon I assume a book would arrive at my doorstep. _I would return the
> > book_. If Amazon were to disagree I would call my Visa company
> and complain.
> > If I got nowhere I would call the FBI, my lawyer etc.
> It depends on what the RDF said. In this case what is authoritative
> is Amazon's promise to send you said book. Amazon isn't authoritative
> for the ISBN number, they're authoriative for the transaction you are
> currently in. If they screwed up the ISBN urn in the RDF then yes, they
> screwed up. But its no the fault of the URI....
> > Your concept of authority is interesting but I don't accept it.
> Authority for what? The ISBN organizatin is the _only_ entity that
> can truly know what ISBN number goes with what book since they're
> the ones that assigned it. If Amazon screws up their internal
> inventory list then is it the ISBN agency that made the mistake? No,
> its the mistake of Amazon for not checking with the authoritative
> agency....

Umm.. who said I was ever using ISBN numbers... I may have simply looked up
a book a (ficticious) Amazon catalog and ordered it. There can be an
infinite number of URIs each -resolving- to an instance or instances of the
same book, some might involve ISBN numbers.