Changes between Version 5 and Version 6 of URI

Show
Ignore:
Timestamp:
2010/02/12 12:40:17 (13 years ago)
Author:
mccarthy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • URI

    v5 v6  
    66 
    77'''Guideline 2.''' 
    8 Often a provider offers multiple URLs for the same resource. e.g. the entrez query http://www.ncbi.nlm.nih.gov/sites/entrez?Db=pubmed&Cmd=ShowDetailView&TermToSearch=22177139 is the same as http://www.ncbi.nlm.nih.gov/pubmed/22177139 (the community recommend to use the later) or http://www.ebi.uniprot.org/entry/P05067 is the same as http://purl.uniprot.org/uniprot/P05067 (where UniProt asks you use the later, which will give RDF if your HTTP header accepts it). 
     8Often a provider offers multiple URLs for the same resource. e.g. the entrez query http://www.ncbi.nlm.nih.gov/sites/entrez?Db=pubmed&Cmd=ShowDetailView&TermToSearch=22177139 is the same as http://www.ncbi.nlm.nih.gov/pubmed/22177139 (the community recommend to use the later) or http://www.ebi.uniprot.org/entry/P05067 is the same as http://purl.uniprot.org/uniprot/P05067 (where UniProt asks you use the later, which will give RDF if your HTTP header accepts it).  
    99 
    10 Document the URI pattern you use on freebase, to encourage uniformity. http://www.freebase.com/view/user/biohackathon/default_domain/views/namespace_1  This is a first-come-first-served approach to pick preferred URL pattern; the first data provider to cross-reference to a third party, gets to decide what URL pattern is in Freebase as "approved" (ideally with the 'blessing' of the third-party data provider) 
     10Document the URI pattern you use on freebase, to encourage uniformity. http://www.freebase.com/view/user/biohackathon/default_domain/views/namespace_1  (is this the correct Freebase page?  it doesn't seem to be providing URI patterns.) This is a first-come-first-served approach to pick preferred URL pattern; the first data provider to cross-reference to a third party, gets to decide what URL pattern is in Freebase as "approved" (ideally with the 'blessing' of the third-party data provider) 
    1111 
    1212'''Guideline 3.'''