Re: 303 +1, WSDL -1

On Sun, 2007-07-15 at 21:11 -0700, Balaji S. Srinivasan wrote:
> Also, from Matthias' recent email:
> 
>  > You should not try to pack ANY information about the 'resolution'  
> of a Semantic Web resource into its URI, quite to the contrary. Make  
> it as meaningless and generic as possible, in the best case it should  
> just be a large random alphanumeric string, e.g.  
> tag:uri:a938fjhsdcHSDu39. If all URIs look like this, nobody will be  
> detered from re-using a URI just because of how it looks.
> 
> I don't know if this is such a good idea -- when debugging, you want  
> to have some information about what the URIs represent (e.g. the  
> "http://beta.uniprot.org/uniprot/" prefix tells you that you're  
> looking at a UniProt protein with the given ID number). If URIs are  
> just alphanumeric strings, you need to constantly be doing lookups to  
> remind yourself of what a particular object means.

+1, Absolutely.  Bear in mind that the URI opacity 'principle' has to do
with machine consumption not human consumption, so complete obfuscation
is not helpful for human consumption / curation.  It is very important
that we remember that facilitating machine interpretation does not
completely remove the human factor from the equation.

-- 
Chimezie Ogbuji
Lead Systems Analyst
Thoracic and Cardiovascular Surgery
Cleveland Clinic Foundation
9500 Euclid Avenue/ W26
Cleveland, Ohio 44195
Office: (216)444-8593
ogbujic@ccf.org


===================================

Cleveland Clinic is ranked one of the top hospitals
in America by U.S. News & World Report (2007).  
Visit us online at http://www.clevelandclinic.org for
a complete listing of our services, staff and
locations.


Confidentiality Note:  This message is intended for use
only by the individual or entity to which it is addressed
and may contain information that is privileged,
confidential, and exempt from disclosure under applicable
law.  If the reader of this message is not the intended
recipient or the employee or agent responsible for
delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If
you have received this communication in error,  please
contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy.  Thank you.

Received on Monday, 16 July 2007 14:14:45 UTC