Introduction to Open Services for Lifecycle Collaboration (OSLC)
0 likes173 views
The presentation discusses the Open Services for Lifecycle Collaboration (OSLC), highlighting its importance for semantic web experts in solving the challenge of defining standard APIs to connect distributed engineering data. OSLC aims to decouple applications from data and improve collaboration across silos, while also providing a standard structure for unique identifiers and data accessibility. It has seen adoption mainly in engineering and offers modular architecture benefits, with growing interest from vendors and institutions.
Introduction to Open Services for Lifecycle Collaboration (OSLC)
- 1. Introduction to Open Services for Lifecycle Collaboration (OSLC) Presentation for ISWC2018 workshop on Decentralizing the Semantic Web Axel Reichwein, Koneksys October 8, 2018 1
- 2. Axel Reichwein ● Background in aerospace engineering ● PhD and postdoc focused on tradeoff studies ● Reconfiguring single architecture model to automatically reconfigure detailed discipline-specific models 2
- 3. Why is OSLC interesting for Semantic Web experts? ● OSLC addresses a BIG problem using Semantic Web standards ● BIG problem: how to define a Standard API? ● OSLC objectives: connecting data across silos (Web of data) + decoupling applications from data ● OSLC adopted until now in engineering , but applicable in other domains ● Semantic Web experts can improve and adopt OSLC 3
- 4. Distributed Engineering Information One technical system described from different perspectives One technical system, but a lot of distributed information Distributed information is challenging for collaboration 4
- 5. Overlaps and Relationships in Engineering Overlaps due to data duplication (e.g. same parameter used in different models or reports) Logical relationships such as a requirement verified by a test case The more complex a system is, the more relationships exist Knowing relationships is crucial for traceability, change management, reuse 5
- 6. Status Quo According to David Meza, Head of Knowledge Management at NASA ● “Most engineers have to look at 13 different sources to find the information they are looking for” ● “46% of workers can’t find the information about half the time” ● “30% of total R&D funds are spent to redo what we’ve already done once before” ● “54% of our decisions are made with inconsistent, or incomplete, or inadequate information” Quote from https://www.youtube.com/watch?v=QEBVoultYJg 6
- 7. Connecting all possible data is currently impossible! 7
- 8. OSLC key idea 1: Standard API Data is accessible through a standard API Standard API using standard concepts to describe ● CRUD web services ● Constraints on data ● Versions of data ● Updates to data Machine-readable description of all services made available by API 8
- 9. OSLC Core Specification v2 9 From http://open-services.net/bin/view/Main/OslcCoreSpecification
- 10. OSLC Core 3.0 Architecture 10 From http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/oslc-core-v3.0-part1-overview.html
- 11. OSLC key idea 2: Unique Global identifiers Data has unique global identifiers Using HTTP URLs 11
- 12. Principle 3: Connections across silos Data is connected 12
- 13. OSLC key idea 4: Applications decoupled from data Applications decoupled from data True data ownership Reusing existing data 13 Modular architecture Freedom to pick-n-choose applications and data
- 14. OSLC Adoption By vendors mostly in ALM: IBM Jazz/CLM, Mentor Graphics By universities and consultants for MBSE, simulation: https://github.com/ld4mbse + https://github.com/oslc Over 50 OSLC APIs developed for different applications New vendors creating OSLC solutions General Motors in their MBSE efforts and vision https://koneksys.com/blog/present ation-of-oslc-at-purdue-plm-meeti ng-2018/ 14
- 15. 15
- 16. Viewing Data as Universal Asset Data = new “electric power” Standard API = new “standard electric power outlet Semantic Web experts can make it happen! 16
- 17. Thanks and get in touch! axel.reichwein@koneksys.com