The Data Web and PLM Transforming PLM through Web Standards and Technologies

Size: px

Start display at page:

Download "The Data Web and PLM Transforming PLM through Web Standards and Technologies"

Marilynn Anderson
6 years ago
Views:

1 The Data Web and PLM Transforming PLM through Web Standards and Technologies PDT Europe October 2017 Brian King - Koneksys

2 About Me 20 years experience in industry Software development background, consultancy for 8 years Tomtom, Facebook, Microsoft, Zemanta,. Mozilla - 5 yrs Community Manager NOW... Koneksys - Business Development OSLC Community Manager 2

3 Data Integration 3

4 Relationships between Engineering Data

5 Reality: Many Relationships between Engineering Data

6 Data Integration for Basic Queries

7 Data Integration for Traceability/Impact Analysis

8 Data Integration for decision-making Good overview = Better decisions Big projects fail because systems are becoming too complex, and this is becoming more common in large engineering organisations as they handle more and more data.

9 Benefits of Connecting Data Silos * * * * Recap: Integrated dataset Traceability Transparency Collaboration Better decisions Knowledge sharing * Icon by madebyoliver from are licensed by CC 3.0 BY 9

10 Why is Data Integration Complicated? Different APIs Java, REST, query languages Different Data Formats XML, JSON, CSV, binary Different Data Models Relational, Graph, Document Different Data IDs integer, path, guid 10

11 Why is Data Integration Expensive? Proprietary APIs and Data Formats Your Data Your Data Integration Solution Vendor $ $ 11

12 Current Data Integration Solutions in Engineering Product Lifecycle Management (PLM)/ Mechanical Engineering Application Lifecycle Management (ALM)/ Software Engineering Proprietary data integration solutions end up being new data silos Where is the integration? Enterprise Resource Planning (ERP)/ Manufacturing etc. Business Intelligence/ Analytics 12

13 The Web 13

14 Why Choose the Web for Data Integration? No license costs No vendor lock-in Mature and widely adopted infrastructure Abundance of Web specialists/developers Original vision of Tim Berners Lee, inventor of the Web 14

15 Hypertext + Internet = Web BEFORE THE WEB Hypertext System 1 WITH THE WEB Hypertext System 2 Problem: No Compatibility between hypertext systems + different protocols to access and connect documents on the internet (Gopher, WAIS, etc...) One global hypertext system = Web One protocol to access and connect documents 15

16 Web Server URL HTML Private/public Web <!DOCTYPE html> <html> <head> <title>requirement 112</title> </head> <body> <p>type = Requirement</p> <p>id = 112</p> <p>text = Only authorized users shall access the system </p> </body> </html> HTTP Web Server Doc Requirement id = 112 text = Only authorized users shall access the system 16

Data Web Server! URL http://example.com/req112 { Only Change between regular Web and Data Web RDF Private/public Web "@context": { "text": "http://myvocab.com/text", "id": "http://myvocab.

17 Data Web Server! URL { Only Change between regular Web and Data Web RDF Private/public Web "@context": { "text": " "id": " "Requirement": " }, "@id": " "@type": "Requirement", "id": "112", "text": "Only authorized users shall access the system" } HTTP Data Web Server Data Requirement Requirement id = 112 idtext = 112 = Only authorized users shall access the text = Only authorized users shall system access the system 17

18 Linked Data = Next Web = Web of Data = Data Web Examples Engineering: IBM - Jazz applications integrated through OSLC Open Initiative: Open Services for Lifecycle Collaboration (OSLC) Public knowledge graph: DBpedia Improving search results: Schema.org Media: BBC Things API + more... 18

Rating in HTML of IMDB page re-appears in HTML of Google search result http://www.imdb.

19 Schema.org: Example of Data Web Example: Google reuses rating of IMDB to display in search results Rating in HTML of IMDB page re-appears in HTML of Google search result <div class="imdbrating" itemtype=" itemprop="aggregaterating"> <div class="ratingvalue"> <span itemprop="ratingvalue">8.0</span> </div> 19

20 Data Web Server Examples Open-source examples at Eclipse Lyo Simulink AMESim MagicDraw Open-source examples at Linked Data for Model-Based Systems Engineering (ld4mbse) Developed by Koneksys FMI PTC Integrity 20

21 Data Web Integration Example Navigable URL RDF Link to related data { "Req113": " }... "id": "112" "Req113" "Requirement", "id": "113"... HTTP Data Requirement id = 112 derived_from= Requirement 113 Reference to related data Requirement id =

22 Data Web Applications Private/ public Data Web Distributed Data Silos Search Visualize CRUD Analytics Link Creator RDF RDF RDF Link Link HTTP HTTP HTTP OSLC Adapter 1 OSLC Adapter 2 OSLC Adapter 3 Data Repository 1 Data Repository 2 Data Repository 3

23 Data Web Application Example Link Editor Private/public Data Web Distributed Data Silos RDF Link RDF Link Data Data Data Repository 1 Repository 2 Repository 3 23

24 Data Web Application Example Google-like Search Private/public Data Web Distributed Data Silos RDF Link RDF Link Data Data Data Repository 1 Repository 2 Repository 3 24

25 Data Web Application Example Tree (BOM-like) Viewers Private/public Data Web Distributed Data Silos RDF Link RDF Link Data Data Data Repository 1 Repository 2 Repository 3 25

26 Data Web Application Example Graph (Context-like) Viewers Private/public Data Web Distributed Data Silos RDF Link RDF Link Data Data Data Repository 1 Repository 2 Repository 3 26

27 New Data Management Application Architecture Traditional App Logic Specific API Data New App Logic HTTP Integrated Dataset Specific API Multiple Data Sources 27

28 Open Services for Lifecycle Collaboration (OSLC) 28

Open Services for Lifecycle Collaboration (OSLC) Standard for

interoperability Adopted so far mainly for Application Lifecycle

Community Linked Data (RDF) REST API (HTTP) Standardized Web API

CSV, binary Different Data Models Relational, Graph, Document

29 Open Services for Lifecycle Collaboration (OSLC) Standard for Linked Data RESTful APIs Domain-specific standards for data interoperability Adopted so far mainly for Application Lifecycle Management (ALM), systems and requirements engineering Open Community Linked Data (RDF) REST API (HTTP) Standardized Web API OSLC Adapter (Data Web Server) Different Data Formats XML, JSON, CSV, binary Different Data Models Relational, Graph, Document Data Different Data IDs integer, path, guid Different APIs Java, REST, query languages 29

30 OSLC Core Specification Mainly to support discovery (Hypermedia REST API) delegated dialogs for improved UI Response Information (such as for resource paging, or for errors) Selective Property Values Reuse of existing domain-specific specifications (e.g. Dublin Core) OSLC v2 spec: (not always accessible!) v3 in draft, awaiting implementations. 30

31 OSLC Community We are remaking the OSLC website! 31

32 Specifications for Web-based data interoperability 32

33 Data Web Interoperability Example Reading Data HTTP GET Data Web Server PLM System Writing Data Data Web Client " "Requirement", "id": "112",... RDF HTTP POST Data Web Server Web-based Export/Import Scenario between data stores ALM System 33

34 OSLC Domain-Specific Specifications 34

35 Data Web Interoperability Example Bidirectional model transformation between SysML and Simulink Developed by Koneksys Open-source implementation at ld4mbse 35

36 Converting Existing Schemas Into RDF 36

37 Traditional Schema Schema <xs:schema xmlns:xs=" <xs:element name="requirement"> <xs:complextype> <xs:sequence> <xs:element name="identifier" type="xs:string"/> <xs:element name="description" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> </xs:schema> XML Document Schema describes the structure of an XML document The purpose of an XML Schema is to define the legal building blocks of an XML document: the elements and attributes that can appear in a document the number of (and order of) child elements data types for elements and attributes default and fixed values for elements and attributes <requirement> <identifier>123</identifier> <description>x shall Y</description> </requirement> 37

38 Converting Schema into RDF Schema <xs:schema xmlns:xs=" <xs:element name="requirement"> <xs:complextype> <xs:sequence> <xs:element name="identifier" type="xs:string"/> <xs:element name="description" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> </xs:schema> RDF Schema? 38

39 Converting Schema types into RDF Schema element type RDF Resource Type <xs:schema xmlns:xs=" <rdfs:class <xs:element name="requirement"> <xs:complextype> <xs:sequence> <xs:element name="identifier" type="xs:string"/> <xs:element name="description" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> </xs:schema> rdf:about=" /rm#requirement"> <rdfs:label xml:lang="en-gb">requirement</rdf s:label> </rdfs:class> 39

40 Converting Schema properties into RDF Schema element property (e.g. of type String) RDF Resource property <xs:schema xmlns:xs=" <xs:element name="requirement"> <xs:complextype> <xs:sequence> <rdf:description <xs:element name="identifier" type="xs:string"/> <xs:element name="description" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> </xs:schema> rdf:about=" ntifier"> <rdfs:label xml:lang="en">identifier</rdfs:label> </rdf:description> 40

41 Converting Schema property multiplicities into RDF Schema element property multiplicity (e.g. identifier must occur once and only, default value in XSD for minoccurs and maxoccurs is 1 ) <xs:schema xmlns:xs=" <xs:element name="requirement"> <xs:complextype> <xs:sequence> <xs:element name="identifier" type="xs:string"/> <xs:element name="description" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> </xs:schema> RDF Resource property <oslc:property> <oslc:propertydefinition rdf:resource=" identifier"/> <oslc:occurs rdf:resource=" ns/core#exactly-one"/> </oslc:property> 41

Converting existing schemas into RDF - Example SysML metamodel as RDF vocabulary More details at http://www.omgwiki.

42 Converting existing schemas into RDF - Example SysML metamodel as RDF vocabulary More details at MGSysML/lib/exe/fetch.ph p?media=sysml-oslc:mappin g_sysml_to_rdf_vocabulary april_28_2014.pdf ocess/experimental-rdf/sys ML/1.3/ 42

43 Universal specs vs Web specs Universal Standards Web Standards Example SysML/STEP OSLC Specifications Scope Large (Example SysML: approx. 300 concepts) Minimalistic (Example OSLC RM Spec: 2 concepts) Effort until release High Small Time until release Long Short Ease of implementation Difficult Easy Ease of adoption Difficult Easy 43

44 Koneksys 44

collaboration, and analytics Providing consulting and

45 Koneksys Creating solutions to connect data silos using the Web for improved traceability, transparency, collaboration, and analytics Providing consulting and research services Creating open-source software Promoting the Data Web 45

46 Koneksys Clients Located in San Francisco. In business since More at koneksys.com 46

47 Summary Data Web = Web-based data integration Distributed Based on open-standards Using standardized REST APIs (e.g. OSLC) Using RDF for limitless links between data having URLs as global identifiers Data Management Applications with Web as data source 47

48 Thanks and get in touch!

Overview of Open Services for Lifecycle Collaboration (OSLC)

Overview of Open Services for Lifecycle Collaboration (OSLC) INCOSE IW MBSE Workshop Axel Reichwein January 21, 2018 Koneksys Axel Reichwein Developer of multiple data integration solutions based on Open