1 / 16

Best practices – Semantic interoperability C ollaborative O pen M arket to P lace O bjects at your Se rvice

Best practices – Semantic interoperability C ollaborative O pen M arket to P lace O bjects at your Se rvice. Charalampos Doukas 1 , Dave Raggett 2 1 CREATE-NET 2 W3C. IoT and COMPOSE. What is COMPOSE?. Provide an IoT enabling ecosystem

carr
Download Presentation

Best practices – Semantic interoperability C ollaborative O pen M arket to P lace O bjects at your Se rvice

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Best practices – Semantic interoperability Collaborative Open Market to Place Objects at your Service Charalampos Doukas1, Dave Raggett2 1CREATE-NET 2W3C

  2. IoT and COMPOSE

  3. What is COMPOSE? • Provide an IoT enabling ecosystem • Easily and securely develop, deploy, share and maintain services based on Internet-connected smart objects • Use-case driven • Cover the whole service lifecycle • Study and identify new business models and value chains • Promote standardization and adoption • Total Cost: 7.4M Euros; EC contribution: 5.35M

  4. Technical Approach A Services Objects Market to provide: • - Objects service management • Registration, object and interaction virtualization, maintenance, accounting, knowledge aggregation and dispatching • Service design and execution environment • SDK to easily develop and deploy services based on Internet connected Objects • Runtime environment (for both servers and mobile devices) to dynamically configure • and execute services • - Provide an IoT enabling middleware layer • Build on existing and forming technology to provide end-to-end eco-system for IoT • Distribute system functionalities • Seamless integration with a plethora of objects by abstracting them into service objects ensuring dependability and traceability

  5. Augmented Shopping Experience • “Smart space” • An indoor shopping environment, focusing on personalized interactions with objects • Connect the complete cycle from manufacturers to customers

  6. Smart City • Barcelona • Focusing on the integration of heterogeneous devices and technologies for searching cross-data opportunities, taking advantage of the wide set of existing sensors • Focus on the day-by-day citizens' experience derived from living in a smart city

  7. Smart Territory • Trentino • Focusing on the integration of highly distributed objects and utilization of smartphones as service objects • Create personalized, social- and environmentally-aware tourism services and territory monitoring services

  8. Interoperability Challenges? Services Description Object Discovery Services Discovery Semantics Common Data Language Common communication protocols Common API Description

  9. Solutions Search for existing standards • Communication/Transport • Application • Device Discovery • Data modeling • APIs • SDK • … • Search for solutions by existing projects: • Architectures • Data models • Services Integration • …. Data {JSON, JSON-LD, XML, HTTP, OWL, RDF-S} Common Vocabularies Appropriate Middleware? Help from groups (in-out W3C/OGC) – Anyone? COMPOSE approach: Do not re-invent the wheel, but form a group for evaluating existing solutions/propose SOS Interoperability Semantic Interoperability

  10. Standardization? Potential solution? W3C Web of Things Community Group See http://www.w3.org/community/ ●Open forum without fees ●W3C provides free infrastructure support ●Very easy to set up, and anyone can join ●Work with wider community to ● Help with organizing workshops and tutorials ● Discuss use cases and requirements ● Develop specifications and test suites ● Develop open source implementations ● Develop documentation and training materials ● Feed into subsequent standardization activities

  11. Standardization? Potential solution? W3C Web of Things Community Group See http://www.w3.org/community/ Community Group Specifications Working Group W3C Recommendation

  12. Standardization? Potential solution? W3C Web of Things Community Group Draft charter at http://bit.ly/Z60mb2 ●Public-web-of-things@w3.org ●People helping ●Benjamin Mandler, VladTrifa, Dave Raggett, Charalampos Doukas on behalf of the Compose project ●Nick Allott, Dave Raggett and Philipp Hoschka on behalf of the webinos project ●RaffaeleGiafreda on behalf of the iCore project ●PayamBarnaghi on behalf of the IoTest project ●PayamBarnaghi and Laurent Lefort on behalf of the Semantic Sensor Networks Community Group

  13. W3C Existing Groups • Semantic Web Interest Group • RDF Working Group • Linked Data Working Group • Geolocation Working Group • Device APIs Working Group • … OGC Existing Groups • Sensor Observation Discovery • Sensor Model Language (SensorML) • …

  14. Developers What else is needed? Researchers Engage Community Makers Business Stakeholders

  15. How? Build / Integrate into tools for the community -> see Eclipse M2M Workshops in Developer Conferences Maker Events Hackathons Hands On

  16. http://www.compose-project.eu/survey-iot-domains

More Related