I am coming to this (and I think Alf too) from the perspective of wanting to develop practical services about actual stuff, as opposed to operating in domain neutral RDF world.
These services would build on top of all the abstract RDF stuff.
But ultimately, we need to boil things down to a few practical things that we know how to deal with.
i.e. the infinite regress has to bottom out somewhere, on some leaf nodes, which are taken as atoms to actually mean something.
info URIs are one way to provide this.
This may be philosophically inelegant, but it seems to me pragmatically invaluable.
In terms of the suggestions that have been made for alternatives:
If I have came across 2 URIs:
http://en.wikipedia.org/w/index.php?title=Special:Booksources&isbn=0393060349
and also:
http://isbn.org/madeupresolver?039-3-06034-9
Using those alternatives, how would I as an application developer know that they were corresponded to the same entity?
Matt
> -----Original Message-----
> From: Rickard Öberg [mailto:rickard.oberg_at_senselogic.se]
> Sent: 15 November 2005 09:45
> To: general_at_simile.mit.edu
> Subject: Re: infoURI standard officially blessed
>
>
> Also, IAAAE (I Am An AOP Expert), and in that world (which seems to
> correspond quite well with the RDF mindset) it is utterly and
> completely
> uninteresting what "class" or id a particular object has, in terms of
> determining what one can do with it. Instead one focuses
> entirely on the
> set of interfaces that are exposed by the aspects attached to it.
>
> /Rickard
>
> --
> Rickard Öberg
> rickard.oberg_at_senselogic.se
> _at_work +46-(0)19-173036
>
This email has been scanned by Postini.
For more information please visit
http://www.postini.com
Received on Tue Nov 15 2005 - 10:34:11 EST