Changes between Version 19 and Version 20 of URI

Show
Ignore:
Timestamp:
2010/02/12 15:33:48 (13 years ago)
Author:
jerven
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • URI

    v19 v20  
    66Ideally there should be no HTTP GET arguments in that URL, but if there are to avoid ambiguity for string comparison sort them in alphabetical order (e.g. http://www.example.com/?a=100&b=2 sorting a before b).  When minting new URLs for use as URIs please avoid this. 
    77 
    8 === Guideline 2. If there is no official URL === 
     8=== Guideline 2: If there is no official URL === 
    99Often 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 requests it).  
    1010 
     
    1313If you want to link to a provider for which the official URL is not clear, document the one you use on Freebase. State that you do not know if it is supported. Other providers should follow this first-come-first-served convention UNTIL the original provide states otherwise (see Guideline 1). 
    1414 
    15 === Guideline 3. Confusion === 
    16 Sometimes there is more than provider and thus more than one official URI for a record about a common concept, which can happen with consortia. e.g. PDB is available at PDBj, PDBe, RCSB PDB. Then choose the one that you prefer. Consider adding rdfs:seeAlso references between them, in strong preference over owl:sameAs due that giving misleading semantics. 
     15=== Guideline 3: Confusion === 
     16Sometimes there is more than provider and thus more than one official URI for a record about a common concept, which can happen with consortia. e.g. PDB is available at PDBj, PDBe, RCSB PDB. Then choose the one that you prefer. When the multiple URL's talk about the same concept consider adding owl:sameAs references to each to encode that these URL's talk about the same thing. When they are strongly related but have important differences in content/concept consider using skos:exactMatch or rdfs:seeAlso references.