Towards an architecture and adoption process for Linked Data technologies in Open Government contexts - A case study for the Librery of Congress of Chile
Regarding the slides, I liked the diagram that shows a clear overview of the URI design (Slide 20), It seems very useful to maintain URI schemes (I.E evolution of ontology/instances etc.)... Its the first time I see it. Also looking at the identifiers and I'm concerned about why time ({fechaversion}) was chosen as a variable to generate identifiers? is it safe to prevent collisions etc?
Towards an architecture and adoption process for Linked Data technologies in Open Government contexts - A case study for the Librery of Congress of ChilePresentation Transcript
Towards an architecture and adoption process for Linked Data technologies in Open Government contexts A case study for the Library of Congress of Chile Francisco Cifuentes – Christian Sifaqui – Jose Emilio Labra I-Semantics 2011
Overview: this talk in 1’ Why? Linked Open Data in Public Administrations How? Proposal of Architecture Adoption process Where? Library of Congress - Chile
Linked Open Data in Public Administrations Why? Government data & actions can be supervised Improve transparency & confidence
Linked Open Data inPublicAdministrations Why? Public value (generates citizen experience) Research & Collaboration Reuse data
Linked Open Data in Public Administrations Why? Public information belongs to citizens Financed by public resources Return of inversion
Linked Open Data inPublic Administrations Why? Legislation is public information… …and must be of public domain Everyone is affected by laws
OK, ¡Linked Open Data is good!but… ¿Howtopublish it?
Architecture & Adoption Process There is huge interest to publish LOD Practical guidelines & methodologies ? Our proposal: Architecture of Linked Open Data Implementation methodology How?
Considerations in Public Administrations context Largevolumes of data Semistructuredcontent Contents of general interest Highexpectations New projectsshouldnotinterfere Small teams in largeorganizations Lowsemanticexpertise How?
Linked Open Data Architecture How? Web Browser SemanticApplication Client side Server side Web Application Server Endpoint SPARQL Output RDF Graph Ontologies Update RDF Graph Service Documentation Portal RDF Storage Cache DB Web Server OperatingSystem
Adoption Process How? Contextualization Ontology design RDF Graph Modeling Phases SPARQL Endpoint Implementation RDF Graph Implementation Update Graph Service Documentation Web Portal Non functional Requirements Optional Data Visualization & demos Time
Contextualization Where? Publish Linked Open Data – 5 stars Norms and relationships in a global RDF graph Infrastructure for future developments First stage, pilot project
Contextualization Where? 300.000 norms and their relationships Modifications, Concordances, etc. First stage Only main metadata of norms Title, important dates, types, relationships We exclude body text (articles, chapters, etc.)
Contextualization Where? Definition of domain model: Norms, relationships, types of norms, metadata, Functional requirements for bibliographical records (FRBR) Output formats: RDFa, RDF/XML, JSON, N3,…
Domain Ontologies Where? Small Ontology about Norms
RDF Graph Modeling A norm can be modified by another norm Where? Decree 296 Published 1995-02-17 Art..1. abc. Art. 2. def. Artí.3. ghi. Decree 12066 Published 2005-05-15 Art. 1. Modify decree 296 in the following way:: substitute in Art.1 the words “a” by “xyz”. Now, Decree 296 should be: Decree 296 Artículo 1. xyzbc. Artículo 2. def. Artículo 3. ghi. We want URIs for all
RDF Graph Modeling Where? Careful URI Design Expressiveness
Where? RDF GraphModeling http://datos.bcn.cl/recurso/cl/DTO/ministerio-del-interior/1995-02-17/296/ Decree 296 http://datos.bcn.cl/recurso/cl/DTO/ministerio-del-interior/1995-02-17/296/es@1995-02-17 Original http://datos.bcn.cl/recurso/cl/DTO/ministerio-del-interior/1995-02-17/296/es@2005-05-10 Latest version
Where? Links to other datasets (Countries for International Treaties) DBPedia, Geonames Reuse vocabularies / Ontologies SKOS, DC, FOAF, DBPedia, ORG Triplestore: Openlink Virtuoso SPARQL Endpoint
SPARQL Endpoint Example of query Where? Findallnormsemittedby a municipality between 1995 and 2000 that were modified after 2005. PREFIX dc: <http://purl.org/dc/elements/1.1/> PREFIX n: <http://datos.bcn.cl/ontologies/bcn-norms#> SELECT ?normTitle ?creatorName ?pubDate ?pubDateOther WHERE { ?norm n:createdBy ?creator . ?creator n:hasName ?creatorName . ?norm dc:title ?normTitle . ?norm n:publishDate ?pubDate . ?norm n:isModifiedBy ?otherNorm . ?otherNorm n:publishDate ?pubDateOther . FILTER (regex(?creatorName,"MUNICIPALIDAD","i")) FILTER (?pubDate > "1995" && ?pubDate < "2000" && ?pubDateOther > "2005") } ORDER BY (?pubDate)
RDF Graph Implementation Where? We developed a Linked Data Frontend (WESO-DESH) Content negotiation based on HTTP 303 See Other Definition of URIs based on regular expressions Easy configuration Support for CONSTRUCT, ASK & DESCRIBE Delegates output formats to SPARQL Endpoint Result caching GUI for administration backend (in progress) http://code.google.com/p/weso-desh/
RDF Graph Implementation Where? WESO-DESH (Linked Data Frontend) XML Configuration Output HTML+RDFa
26 Update Graph Service Where? Automatic extraction & transformation process to update the RDF Graph Based on Pentaho - Kettle ETL Executes Transformations in threads Configuration in XML *ETL = Extraction, Transformation Loading
Documentation Documentation Web Portal: TYPO3 CMS Sections: URI constructionguidelines Examplequeries Output formats Ontology documentation etc. Where?
Non-Functional Requirements Answer time Cache system, Profiling Security & privacity Different views and access levels of RDF Graph Others Internationalization Accessibility Use of standards Where?
29 Optional: Data visualization Where? Protype tool: LODViz (Linked Open Data Vizualization) Based on HTML5 (pattern library) Work in progress http://www.weso.es/lodviz/
30 Results Public Dataset Catalogs Faceted Browser - CTIC Foundation Five stars Linked Open Data
31 Conclusions First stage finished > 300.000 norms exported 8mill. triples, 27 triples by norm 200/400 triples added each day 3 tools in development WESO DESH - Linked data frontend WESO RUD – RDF Updater LODVIZ – Linked Open Data Visualization Proposed methodology of Linked Open Data
Future Work Library of Congress of Chile More datasets: Biographies, Geographical data History of Law Improve documentation WESO Research group Semantic search engine Entity extraction & reconciliation in text Resource Recommendation Provenance & graph views
TheEnd http://www.weso.es More Information http://www.bcn.cl
34 Main Team Francisco Cifuentes Member of WESO Research Group and Library of Congress of Chile http://www.weso.es/~fcifuentes Christian Sifaqui Head of Systems and Network information services Library of Congress of Chile http://sifaqui.blogspot.com/ Jose Emilio Labra Associate Professor of University of Oviedo and Head of WESO Research Group http://www.di.uniovi.es/~labra/
Credits Most of the people were obtained from Internet. Imagen transparencia: http://2.bp.blogspot.com/--wFwsKwMgAg/TjSDXOLCTzI/AAAAAAAAOzQ/qvBtbShckdI/s1600/11.2.bmp Euros: Minuto digital. http://www.minutodigital.com/wp-content/uploads/euros-300x196.jpg Biblioteca: http://ffernandez.files.wordpress.com/2010/04/biblioteca.jpg FRBR: http://cucataloging.blogspot.com/ Contextualization: http://tentblogger.com/right-advertisers/ Documentation: http://susops.blogspot.com/2010/07/power-of-documentation.html
Regarding the slides, I liked the diagram that shows a clear overview of the URI design (Slide 20), It seems very useful to maintain URI schemes (I.E evolution of ontology/instances etc.)... Its the first time I see it. Also looking at the identifiers and I'm concerned about why time ({fechaversion}) was chosen as a variable to generate identifiers? is it safe to prevent collisions etc?
Keep up the good work! 1 year ago