1 / 8

RDF Best Practice

This document outlines best practices for publishing RDF vocabularies, drawing from W3C recommendations. Key concepts include establishing dereferencable concept URIs, using HTTP 303 redirects for accessing vocabulary and concepts, and implementing content negotiation to serve different formats (e.g., RDF/XML, HTML). Examples illustrate configuring server-side settings using .htaccess for both hash and slash namespaces. The goal is to ensure that RDF ontologies are easily accessible and usable, supporting seamless integration into web applications and datasets.

alia
Télécharger la présentation

RDF Best Practice

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation 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/

  2. Publishing RDF Ontologies • Content Negotiation • Dereferencable concept URIs • HTTP 303 Redirects • Concept Name separated from the URI via slash (/) or hash (#)

  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

  4. Dereferencable Ontology URIs • Example: • Access e-Freight Ontology: http://efreight.sti2.at/ontology/crs.owl

  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

  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

  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]

  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

More Related