the tutorial about how to develop a semantic web application that I gave at ISWC 2008

1. Realizing a Semantic Web Application Emanuele Della Valle Dario Cerizza Irene Celino http://www.cefriel.it http://swa.cefriel.it [email_address] http://emanueledellavalle.org 7 th Int. Semantic Web Conference ISWC 2008 Karlsruhe, Germany, October 26, 2008 C enter of E xcellence F or R esearch, I nnovation, E ducation and industrial L ab partnership - Politecnico di Milano

17. The rough structure of data integration

19. So where is the Semantic Web?

21. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

22. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

23. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

32. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

44. The resulting ontology

55. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

56. Modeling MusicBrainz schema in OWL @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix mb: <http://musicbrainz.org/> . mb:Artist a owl:Class ; rdfs:label &quot;MusicBrainz Artist and Band&quot; . mb:artist_relation a owl:ObjectProperty ; rdfs:domain mb:Artist ; rdfs:range mb:Artist . MusicBrainz.n3 artist artist_relation id gid artist ref

58. MusicMoz schema category from * resource style 1 * name link name string type

59. Modeling MusicMoz schema in OWL @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix mm: <http://musicmoz.org/> . @prefix mb: <http://musicbrainz.org/> . mm:from a owl:DatatypeProperty ; rdfs:domain mb:Artist ; rdfs:range <http://www.w3.org/2001/XMLSchema#string>. mm:Style a owl:Class ; rdfs:label &quot;MusicMoz Music Style&quot; . mm:hasStyle a owl:ObjectProperty ; rdfs:domain mb:Artist ; rdfs:range mm:Style . MusicMoz.n3

63. “ Application Connected by Concepts ” artists Music styles events time places Meex ontology MusicBrainz EVDB MusicMoz Meex

71. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

73. meex interfaces MusicBrainz database Adapter Database  RDF SPARQL Server EVDB REST service MusicMoz File XML meex XML Browser Web 3) HTML and RDF 2) RDF GRDDL processor EVDB  RDF MusicMoz  RDF XML 2) RDF 1 ) Music style User

76. Designing how meex works inside Ajax Web Framework GRDDL Processor For each Artist SPARQL Client MusicBrainz SPARQL Endpoint HTTP REST Client EVDB HTTP REST service GRDDL Processor EVDB  RDF MusicMoz  RDF Linking Artists to Events RDF Merge Extraction and Transformation Ajax Web Framework Music style Set of artist in RDF Artist SPARQL Query Events in XML Events in RDF Artists and events in RDF Artist data in RDF HTTP Query Dati RDF Artists and events in RDF

81. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

86. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

92. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

94. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

96. meex interfaces (1) MusicBrainz database Adapter Database  RDF SPARQL Server EVDB REST service MusicMoz File XML meex XML Browser Web 3) HTML and RDF 2) RDF GRDDL processor EVDB  RDF MusicMoz  RDF XML 2) RDF 1 ) Music style User

102. meex interfaces (2) MusicBrainz database Adapter Database  RDF SPARQL Server EVDB REST service MusicMoz File XML meex XML Browser Web 3) HTML and RDF 2) RDF GRDDL processor EVDB  RDF MusicMoz  RDF XML 2) RDF 1 ) Music style User

107. So far so good! (1) MusicBrainz database Adapter Database  RDF SPARQL Server EVDB REST service MusicMoz File XML meex XML Browser Web 3) HTML and RDF 2) RDF GRDDL processor EVDB  RDF MusicMoz  RDF XML 2) RDF 1 ) Music style User

108. So far so good! (2) Ajax Web Framework GRDDL Processor For each Artist SPARQL Client MusicBrainz SPARQL Endpoint HTTP REST Client EVDB HTTP REST service GRDDL Processor EVDB  RDF MusicMoz  RDF Linking Artists to events RDF Merge Estrazione e trasformazione Ajax Web Framework Music style Set of artist in RDF Artist SPARQL Query Events in XML Events in RDF Artists and events in RDF Artist data in RDF HTTP Query Dati RDF Artists and events in RDF

109. D.1 Model the application ontology D.2 Model the content ontology R.1 Users’ needs analysis R.3 Software requirements analysis R.4 Content requirements analysis D.3 Model sample contents Reuse Merge Extend I.1 Implement the initial Knowledge Base V.1 Validation I.3 Choose content annotation methods I.2 Implement the integrated model Reuse Merge Extend I.4 Implement the application R.2 Risk analysis D.4 Design Application T.1 Testing

111. What’s left? Ajax Web Framework GRDDL Processor For each Artist SPARQL Client MusicBrainz SPARQL Endpoint HTTP REST Client EVDB HTTP REST service GRDDL Processor EVDB  RDF MusicMoz  RDF Linking Artists to events RDF Merge Estrazione e trasformazione Ajax Web Framework Music style Set of artist in RDF Artist SPARQL Query Events in XML Events in RDF Artists and events in RDF Artist data in RDF HTTP Query Dati RDF Artists and events in RDF

124. Step 5 and 6

125. Step 5 and 6

128. Thank you for paying attention Any Question?

129. Realizing a Semantic Web Application Emanuele Della Valle Dario Cerizza Irene Celino http://www.cefriel.it http://swa.cefriel.it emanuele.dellavalle@cefriel.it http://emanueledellavalle.org 7 th Int. Semantic Web Conference ISWC 2008 Karlsruhe, Germany, October 26, 2008 C enter of E xcellence F or R esearch, I nnovation, E ducation and industrial L ab partnership - Politecnico di Milano

131. Advertisement: if you speak Italian …