Your SlideShare is downloading. ×
Produce and consume_linked_data_with_drupal
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

Produce and consume_linked_data_with_drupal

297
views

Published on

Published in: Education, Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
297
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. Produce and Consume Linked Data with Drupal Stephane Corlosquet, Renaud Delbru, Tim Clark, Axel Polleres and Stefan Decker Ioan Toma©www.sti-innsbruck.at INNSBRUCK www.sti-innsbruck.at Copyright 2008 STI
  • 2. Acknowledge • Many of the slides in this presentation are based on: http://www.slideshare.net/scorlosquet/produce-and-consume-linked- data-with-drupal?src=related_normal&rel=4796732www.sti-innsbruck.at
  • 3. Motivation • There is a lot of data on the web in Content Management Systems (CMS) • Moreover this data is structured data. • However, • It is not possible to reuse this data outside the CMS (except RSS), but RSS limited when it comes to semantic • This data is not available in a unified machine readable formatwww.sti-innsbruck.at
  • 4. Approach• Goal: • integrate “any” CMS site to the Web• Implementation in Drupal, why?: • One of the most popular CMS • Lots of extra functionality available as modules• Approach in short: Develop a set of modules that perform: 1. Automatically site vocabulary generation 2. Mapping content models (site vocabulary) to existing vocabularies 3. Data endpoint for SPARQL querying 4. Lazy loading of external data (data import)www.sti-innsbruck.at
  • 5. Approachwww.sti-innsbruck.at
  • 6. Related work• Ontology based CMSs: • Semantic community Web portals (2000) • Model Driven Ontology-Based Web site management Approach in the paper starts from existing CMS infrastructure• Mapping RDBMS underlying CMS to RDF/RDFS Approach in the paper starts from site model and constraint and not from underlying data base model • SCF Node proxy architecture - RDF to Drupal mapping, not general, specific to bio domain Approach in the paper has as starting point SCF Node proxy architecture www.sti-innsbruck.at
  • 7. Drupal• Drupal: • Easy to use • Large community • Popular on the Web • Modular design• Drupal terminology: • Node – corresponds to Drupal Web page • Module – functionality that alter and extend Drupal core functionality • Site administrators: set up the site and install modules they like/need • Module developers: develop module(s) • Site editors: create the content of the site following the schema defined by the site administratorwww.sti-innsbruck.at
  • 8. Drupal: Content Construction Kit• GUI for extending the internal schema of a Drupal site• Used on many Drupal sites• Can build new types of pages, known as content types• Can create fields for each content types. Fields can be of various types: plain text fields, dates, email addresses, file uploads, references to other pages www.sti-innsbruck.at
  • 9. Drupal: Content Construction Kit – User Interfacewww.sti-innsbruck.at
  • 10. Drupal: Content Construction Kit – User Interfacewww.sti-innsbruck.at
  • 11. Drupal: Content Construction Kit – User Interfacewww.sti-innsbruck.at
  • 12. Approach 4 1, 2 3www.sti-innsbruck.at
  • 13. 1. Site Vocabulary• Automatic site vocabulary in RDFS/OWL: • Content types and fields are mapped to classes (rdfs:Class) and properties (rdf:Property) • Label and descriptions of content types and fields are mapped to rdfs:label and rdf:comment • Cardinality is mapped to cardinality restrictions in OWL • Required – owl:cardinality 1 • Maximum cardinality – owl:maxCardinality n • Domains and ranges of fields to rdfs:domain and rdfs:rangewww.sti-innsbruck.at
  • 14. 2. Mapping Content Models to existing ontologies• Import of any vocabulary published online • One needs to specify the URL of the vocabulary • By default FOAF, DublinCore, SIOC are imported• External ontology search service • Entity centric search – returns the relevant classes, properties • Based on SWSE and Sindice• Local terms are subclasses/subproperties of public terms • To ensure safe vocabulary reuse – avoid redefinitionwww.sti-innsbruck.at
  • 15. 2. Mapping Content Models to existing ontologies – RDF mapping pagewww.sti-innsbruck.at
  • 16. 2. Mapping Content Models to existing ontologies – RDF mapping pagewww.sti-innsbruck.at
  • 17. 3. Data endpoint for complex queries• Local RDF data exposed in a SPARQL endpoint • Enables interoperability across sites • Build on the PHP ARC2 library • All RDF data index in the endpoint • Each page stored as a graph an kept up to datewww.sti-innsbruck.at
  • 18. 4. Lazy loading of external data• Lazy loading (caching) of distant RDF resources • Enables interoperability across sites • Build on the PHP ARC2 library • CONSTRUCT query to map distant schema to local schemawww.sti-innsbruck.at
  • 19. Summary• Practical work to add RDF support to Drupal through a set of Drupal modules that do: 1. Automatically site vocabulary generation 2. Mapping content models (site vocabulary) to existing vocabularies 3. Data endpoint for SPARQL querying 4. Lazy loading of external data (data import)www.sti-innsbruck.at
  • 20. Relation to OC work• DERI approach does not use semantic repositories as a backend solution for storing RDF; we use OWLIM• Things that might be relevant for us: • Mapping approach • Lazy loading of data from external sourceswww.sti-innsbruck.at