RE: BioRDF: URI Best Practices

--Alan,
 
> notwithstanding, I'd rather know that I am dealing with a 
> non-information resource *before* I touch the network.

I am very puzzled, how can you tell a IR or non-IR given any URI, unless you
have the knowledge about all URI before hand?  Don't you have to
de-reference the URI at first hand? 

To discribe if an IR has multiple representations is different from to
describe if it is IR or non-IR. Let's not mess this two up.  The former is
useful.  For instance, if a data is available in XHTML, WML, word, PDF, etc.
Then we can further use the content negotiation to further retrieve the
resources if using the same URI.  Or use different URIs to represent
different types/versions of representations. But it will be useless to
classify IR vs. non-IR. Of course, you can develop ontology and use it to
describe it, it just won't offer much help.

> So my proposal suggests a class that defines ways of transforming
> the URI you find in a SW document into URLs that get specific types of
information.

I would also be cautious about that.  This seems to be similar to what the
web service is doing.  I hope we don't try to reinvent the wheel, especially
it isn't a small wheel to invent by any means.

Xiaoshu

Received on Friday, 21 July 2006 15:40:28 UTC