LOD2: State of Play WP6 - LOD2 Stack Architecture
0 likes151 views
The document outlines the current state and work plan for the LOD2 stack architecture, detailing the initial exploration and prototyping of a loosely coupled demonstrator architecture. It emphasizes the goals of achieving integration among various tools and components, with a focus on user-oriented interfaces and configurations, leading to a more cohesive architecture by August 2011. Moreover, it lists various discussions and proposals for improving communication and functionality within the LOD2 ecosystem, with a call for contributions and collaboration from stakeholders.
LOD2: State of Play WP6 - LOD2 Stack Architecture
- 1. LOD2 Stack Architecture WP1.3 & WP6Bert Van Nuffelen,Kurt De Muelenaere,Bastiaan Deblieck @ TenForce
- 2. Current state of work
- 3. The workplan
- 4. Discussion topics for tomorrowDelivery 1.3 document http://svn.aksw.org/lod2/D1.3It forms the initial start of WP6.Content is subject to improvement based on your inputDocument summaryUI interaction modelsLOD2 architectureLoosely coupled demonstrator architectureAgreements on target platform, component distribution, ...Surveys on topics such as configuration info, input/output interfaces, ...Current state of work
- 5. Interfaces to inspect Linked Open Data more developer orientedInterfaces to aid locating, ranking and comparing datasets end-user aidInteractive Linked Open Data powered widgetsend-user aid / more developer orientedLinked Open Data powered search interfaces end-user aidREST APImore developer orientedUI vision
- 8. Extraction
- 12. Quality Analysis
- 16. WP 1.3: (sep 2010 - aug 2011)initial exploration and prototyping results will be a loosely coupled demonstrator the architecture document (delivery WP1.3) a central repository of all necessary architecture information The process is started and under continuous improvement till aug 2011WP 6: (sep 2011 – sep 2013)real integration work towards a more tighten integration.Integration workplan
- 17. Concrete plan till aug 2011
- 18. Workplan WP6 (sep 2011-aug 2011)
- 19. Collecting all toolsAgreement: all tools will be available as debian packages Licenses! Session: Hands on Debian Package creationwiki: technical summary of each tool https://grips.punkt.at/pages/viewpage.action?pageId=21894276 Thanks for completing it.Target platformWP1.3: Ubuntu 10, Web enabled (Tomcat, FireFox)WP1.3 achievements
- 20. The demonstrator is a
- 21. loosely coupled set of components/tools
- 22. Able to demonstrate each functionality of LOD2 stack
- 23. Familiarization with each tool started
- 24. The interfaces (both input as output) available
- 26. The interaction flows between lod2 components
- 27. Test environment
- 28. VMware ubuntu 10
- 29. Installation steps will be documented.
- 30. Up to now subject of investigation by myself (TenForce)
- 31. Virtuoso
- 33. Collect all information in OWL model (designed in Protégé)
- 34. When possible use ontowiki to maintain and enrich the information.
- 35. Model will be published for review.
- 36. Component status w.r.t. LOD2 architecture
- 37. What is the status and possibilities of a component w.r.t. LOD2 architecture
- 38. Example: prerequisites, tested?, doc, active versions, …
- 40. Components
- 41. API
- 42. Layer
- 44. Currently contains most information available of
- 47. svn repository to publish LOD2 debian packages
- 51. Input from usecases WP 7,WP8 and WP9
- 52. Bug and CR tracking
- 53. tool and repository location have to be decided.Managing integration process
- 54. More uniform integration between tools
- 56. Functional communication via a LOD2 REST service definition.
- 58. A default simple architecture that works.
- 59. Setup document describing alternative setups
- 60. For demo and testing purposes.
- 62. forms research challenge: e.g. how do you exploit the result of a learning expressed in SKOS in an OWL environment.
- 63. e.g. wiki: https://grips.punkt.at/display/LOD2/Standards+for+Metadata+Life+Cycle
- 64. Satisfying WP7, WP8 and WP9feature requests:
- 66. Requires commitment from tool developers to adapt to the agreed architecture communication endpointsTowards a stronger LOD2 stack (WP6)
- 67. has birds eye overview
- 68. makes architecture proposals which have a large support
- 69. discusses architecture design issues such as
- 70. internal standards for communication, configuration, etc.
- 71. the impact of a tool’s status on the LOD2 stack
- 72. architectural solutions for usecase scenarios Architecture core team
- 73. PROPOSAL ONLYGlobal vision proposal: a LOD2 bus
- 74. Demonstrator is tool centric: a collection of tools acting in the same area
- 75. Move to LOD2 centric
- 76. a LOD2 bus which routes the communication between the components
- 77. Advantages:
- 78. component integration becomes ‘plug and play’
- 79. new component integration easy
- 80. LOD2 based applications ‘only’ to connect to the bus to get LOD2 stack access.Friday discussion topics
- 81. PROPOSAL ONLYData layer REST service definition:
- 82. Use existing SESAME (openRDF) definition
- 83. Sesame is the result of a previous EU funded project OnToKnowledge
- 84. Functional REST service definition:
- 86. Often tool specific services, but maybe we can identify common services like:
- 88. SPARQL endpoint configuration & reasoning:
- 89. Instead of hiding all info about the endpoint allow a tool to reason and exploit the meta-knowledge of the information structure.
- 90. Examples:
- 91. Local file : RDFEP:foo.rdf
- 94. Union of 2 endpoints: RDFEP:<rdfep1>+<rdfep2>
- 95. Taxonomy restricted endpoint: RDFEP:virtuoso?dns=DNS&login=dba&password=dba&ontology=foo.owl
- 96. These SPARQL endpoint definitions are processed through XML catalogs.
- 97. This allows extra flexibility in the configuration of the SPARQL endpoints.Friday discussion topics
- 98. Initial information collection is started and global outline decisions have been taken.
- 99. TenForce works on loosely coupled integration demo and sets up integration management processes.
- 100. Architecture core team will be created.
- 101. More complex integration decisions required for WP6 are in the pipeline.Thank you to all contribution so far &I Invite you to join our discussion session tomorrowConclusion
- 102. Bastiaan Debliek Bastiaan.Deblieck@tenforce.beBert Van Nuffelen Bert.Van.Nuffelen@tenforce.be
- 103. LOD2 usage context
- 104. Overview architecture as in WP1.3 document
- 106. Ontology screenshot
- 107. Packages & licenses tableSELECT ?t ?deb ?lic WHERE { ?t rdf:type lod2:Tool. OPTIONAL {?t lod2:debian_package ?deb} OPTIONAL {?t lod2:license ?lic} }Responsible tableSELECT ?t ?part ?remail ?bemail WHERE {?t rdf:type lod2:Tool. ?t lod2:contributed_by_partner ?part.OPTIONAL {?t lod2:responsible ?res. ?res lod2:person_email ?remail}OPTIONAL {?t lod2:backup_responsible ?bac. ?bac lod2:person_email ?bemail}}Generating the WP1.3 overviews
- 108. Tool usage w.r.t. functional areaSELECT ?area ?tool WHERE {?area rdf:type lod2:ArchitectureFunctionalArea. OPTIONAL {?tool lod2:supports_functional_area ?area}}Generating status views