On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
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 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 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 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 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
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