Your SlideShare is downloading. ×
0
Rdf best practise
Rdf best practise
Rdf best practise
Rdf best practise
Rdf best practise
Rdf best practise
Rdf best practise
Rdf best practise
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Rdf best practise

255

Published on

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
255
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. RDF Best Practice Best Practice Recipes for Publishing RDF Vocabularies W3C Working Group Note 28. August 2008 - http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828/© Copyright 2008 STI INNSBRUCK www.sti-innsbruck.at www.sti-innsbruck.at
  • 2. 2 Publishing RDF Ontologies • Content Negotiation • Dereferencable concept URIs • HTTP 303 Redirects • Concept Name separated from the URI via slash (/) or hash (#) www.sti-innsbruck.at
  • 3. 3 Content Negotiation • Client specifies preferred format (in HTTP Header), e.g. – Accept: application/rdf+xml – Accept: application/xhtml+xml, text/html • Fallback type must be specified www.sti-innsbruck.at
  • 4. 4 Dereferencable Ontology URIs • Example: − Access e-Freight Ontology: http://efreight.sti2.at/ontology/crs.owl • Click to edit Master text styles – Second level • Third level – Fourth level » Fifth level www.sti-innsbruck.at
  • 5. 5 Dereferencable Concept URI • Example: − GET the class Shipment: http://efreight.sti2.at/ontology/crs.owl#Shipment − Redirect to vocabulary URI: http://efreight.sti2.at/ontology/crs.owl • Click to edit Master text styles – Second level • Third level – Fourth level » Fifth level www.sti-innsbruck.at
  • 6. 6 Server-Side Configuration • .htaccess for ‘hash namespaces‘, e.g. http://efreight.sti2.at/ontology/crs.owl#Shipment AddType application/rdf+xml .owl RewriteEngine On RewriteBase /crs RewriteRule ^crs$ crs.owl • .htaccess for ‘slash namespaces’, e.g. http://efreight.sti2.at/ontology/crs/Shipment AddType application/rdf+xml .owl RewriteEngine On RewriteBase /crs RewriteRule ^crs/.+ crs/ [R=303] RewriteRule ^crs/$ crs.owl www.sti-innsbruck.at
  • 7. 7 Redirect to SPARQL Query • Server-side configuration (.htaccess file) RewriteCond %{HTTP_ACCEPT} text/html RewriteRule ^crs/(.+) http://dbpedia.org/$1 [R=303] RewriteCond %{HTTP_ACCEPT} application/rdf+xml RewriteRule ^crs/(.+) http://dbpedia.org/sparql?query=DESCRIBE+<http://dbpedia.org/$1> [R=303] www.sti-innsbruck.at
  • 8. 8 Summary • Dereferencable URIs for all concept in the ontology • 303 Redirect to the Ontology if a concept is accessed • Possible to separate the namespace with a slash (/) or a hash (#) • Content Negotiation with fallback type • Redirecting to SPARQL Query www.sti-innsbruck.at

×