Changes between Version 15 and Version 16 of ImplementationBootcamp

Show
Ignore:
Timestamp:
2010/02/11 13:05:11 (9 years ago)
Author:
tkappler
Comment:

hints about what to serve to a GET

Legend:

Unmodified
Added
Removed
Modified
  • ImplementationBootcamp

    v15 v16  
    1313===  I have to build an OWL model of my data - how do I go about doing this? === 
    1414 
     15 
     16 
    1517===  When someone calls GET on my URLs, what should I return in order to be semantic webby? === 
     18 
     19You should probably use [http://en.wikipedia.org/wiki/Content_negotiation Content Negotation] using the HTTP Accept: header. That way you can return HTML and RDF under the same URI. However, it's fine for the time being to just accept a ".rdf" suffix or a "%format=rdf" URL parameter. 
     20 
     21At [http://www.uniprot.org UniProt], we use content negotiation for our OWL documentation, but not (yet) for the actual data. Example: 
     22{{{ 
     23> wget --header='Accept: application/rdf+xml' http://purl.uniprot.org/core/recommendedName 
     24[...] 
     25Saving to: `recommendedName.rdf 
     26 
     27> wget --header='Accept: text/html' http://purl.uniprot.org/core/recommendedName 
     28[...] 
     29Saving to: `recommendedName.html 
     30}}} 
    1631 
    1732===  What are the similarities and differences between the various shared names proposals?  ===