Cross-Industry Semantic Interoperability: Achieving Interop

1
How to Achieve
Cross-Industry Semantic Interoperability

2
Contributions from industry experts
(Alphabetically)
Based on a multi-part article series intended to broaden the perspectives of contributors to standards
organizations (SDOs) to develop an interop model spanning both IoT and business “systems”.
Victor Berrios
Zigbee Alliance
Richard Halter
Global Retail Tech. Advisors
Mark Harrison
Milecastle Media
Adam Hise
Harbor Research
Scott Hollenbeck
Verisign
Elisa Kendall
Thematix Partners
Doug Migliori
ControlBEAM
Bob Parker
IDC Research
John Petze
SkyFoundry
Ron Schuldt
Data Harmonizing
J. Clarke Stevens
Shaw Communications
Dan Yarmoluk
ATEK Access Technologies
(Speaker)
Slide 1 Image Credit: leowolfert/Shutterstock

3
The metadata (information) model challenge for widespread IoT adoption:
 Support Cross-Industry Use Cases
 Support Business and Device “Systems”
 Distribute Computing from Cloud to Edge
 Efficiently Manage and Share Semantic Metadata
 Dynamically Generate UI/HMI
 Eliminate Middleware and Custom System Integration
 Simple
 Scalable  Sustainable Sensing Actuating
Computing
Communicating
B2B B2C
M2M
Transport &
Logistics
Energy
Homes &
Buildings

4
Cross-Industry Semantic Interoperability | The Basics
Semantics Provides Context to Raw Data
A Time Series includes data & metadata for context
77.6
Point
Controller
Homes &
Buildings The value is 77.6
The Temperature is 77.6
The Temperature is 77.6 ◦F
The Air Temperature of Floor # 4 is 77.6 ◦F
At 09:00 on 10/25 the Air Temperature of Floor # 4 is 77.6 ◦F
Timestamp Attribute Class Object Value Unit
At 12:00 on 10/25 the Air Temperature of Floor # 4 Is 77.4 ◦F
Interval-based
Event-based
Context

5
At 9:00a on 10-25 the air_Temp of Level # Fourth is 77.6 F
At 9.00 on 10.25 the temp of bldg_flr # 4 is 77.6 ◦C
At 09:00 on 10/25 the 28DJ… of 82AZ… # 8T02… is 77.6 928…
1
2
3
4
1 2 3 4
Vendor System A Vendor System B Interop Standard C Interop Standard D
Semantic Disparity Limits Value Time Series data from multiple disparate sources
must be normalized before processing

6
Bi-directional data flowSemantic annotation
A common Information Model, abstracted to the lowest common denominator,
can minimize semantic disparity by incorporating broad cross-industry perspectives
Point
Controller
Attributes
Object
Payload
Data Map
Values
Time Series
Object
Identifier Clock
Cnt-01 10/25 09:00
Data Exchange
09:00 on 10/25 Air Temperature Floor 4 77.6 ◦F
09:00 on 10/25 Rotation Speed Fan 31 30 RPM
Identifier Attribute Class Object
zn3-wwfl4 Air Temperature Floor 4
Identifier Temperature
zn3-wwfl4 77.6 ◦F
Identifier Value Unit
zn3-wwfl4 77.6 ◦F
Metadata Data
Data
Normalization
Sensor Data
Point Object
Identifier Speed
zn3-fan6 30 RPM
Actuator Data
Payload
Data Map
Identifier Attribute Class Object
zn3-fan6 Rotation Speed Fan 31
Identifier Value Unit
zn3-fan6 30 RPM

7
IoT Consortia effort transitioning from
Syntactic to Semantic Interoperability
Interdependent Use Cases
Application Layer Standards & Open-Source Initiatives
Interoperability Layers
Interdependent, cross-industry use cases
need semantic interop for highest value
Transport &
Logistics
Energy
Homes &
Buildings
E-Commerce
Supply Chain
Traceability
Energy
ManagementSmart Grid
Building
Automation
Payment
Processing
Digital
Wallet
Electronic
Health Record
Patient
Monitoring
Patient
Generated
Healthcare
Home
Automation
EDI
Building Information
Modeling
Point of Sale
Traffic Monitoring Route Optimization
Load Monitoring
OSI Model IIC Framework
Semantic
Interoperability
Syntactic
Interoperability
Physical Layer
Data Link Layer
Network Layer
Transport Layer
Application Layer
Presentation Layer
Session Layer
Technical
Interoperability
1
2
3
4
5
6
7
LCIM

8
Consortia-driven semantics work (a “fringe” use case to one may be “core” to another)
Consortia have been largely unsuccessful in developing semantic data schemes that
are applicable to broad-based, cross-industry use cases - their experience tends to
be based on narrow sets of technology or industry segments.
Industries
Energy
Transport &
Logistics
Homes &
Buildings
Retail
Healthcare
ZigbeeOCF
Blue
tooth Haystack
Open
GroupOMGGS1
GuidelinesSubstantive specifications
Schema
.org

9
“Business standards” and “device standards”
consortia must converge on a center point of
interoperability within the application layer.
Proposed “Blending”:
❶ Object-based, Top-Level Ontology
❷ Ontology for an Information Model
❸ System Ontology for Business & Devices
❹ Time Series for Business & Device Events
❺ Common API Gateway & Services
❻ Grid Format for Payloads
❼ Event Store for Object State
❽ Metadata Managed as Data
❾ Hub for Mapping Legacy Platforms
❿ Metadata for Dynamic UI/HMI
CoAP
HTTP
JSON
GS1
EDI
ID Keys EPCIS
GDSN CBV
SmartSearch
GPC
IETF
EPP
OMG
UPOS
UML DDS
ODM
OCF
Models
Haystack
Tags
“Business Standards”
Consortia
“Device Standards”
Consortia
Open
Group
O-DEF
TOGAF
Zigbee
Clusters
dotdot
Schema
.org
Ontology
Bluetooth
Profiles
Assigned
Numbers
“Blended”
Approach
XML
RDF OWL
MQTT OPC

10
The Role of a Top-Level Ontology
Semantic Levels Hierarchical Classes
• An ontology can provide a standardized classification of domain concepts through a collection of classes.
• Each class (concept) can represent a category of like objects (things) which can be uniquely identified.
• A class is defined to reflect the attributes, restrictions, and relationships unique to its objects (instances).
• A class (such as Sensor or Actuator) can
be a subclass (type) of another class
(Device).
• All subclasses inherit the attributes of its
class.
• An attribute is attached at the most
general class applicable to all of its
objects, including subclasses.
• Similar to, but metadata abstraction from
object-oriented programming
Class
Subclass
Object
Object
Subclass
Object

11
Consortia Object Class Comparison Object-Based Top-Level Ontology
Top-level object classes can facilitate the exchange of data and interoperability across different domains (industries)
“Blended”
Approach
#1
Vocabulary
Term
(English)
GS1
EDI
IETF
EPP
OMG
ARTS ODM
Open
Group
O-DEF
Schema
.org
Ontology
Object Object Object Thing /Item
Class Class Object Class Type
Info… Model Information-Set Intangible
Asset Asset Asset Resource
Product Product Item Product Product
Location Place Place Place
Party Party Party
Person Person Person Person
Organization Organization Enterprise Organization
Transaction Transaction
System Environment
Process Process Action
Rule Law-Rule
Event Event Event Event
Relationship
Domain (DNS) Domain (DNS)
Object
Identifier [Identifier]
Name [Term]
Description [Text]
Class [Relation]
Owner Party [Relation]
Attributes
Name [Data Type]
Name [Data Type]
…
Root
Top-Level
Subclass
Information Model
Asset
Product
Location
Party
Transaction
System
Process
Rule
Event
Relationship
Person
Organization
Domain (DNS)

12
An Ontology for an Information Model
An information model, as a knowledge
domain, can have its own ontology which
can model a multi-level ontology. An
Information Model top-level object class can
be used to contain subclasses that define an
information model
“Blended”
Approach
#2
Attribute
Within Class [Relation]
Data Type [Relation]
Information Model
Repository [Relation]
Unit
Base Unit [Relation]
Conv… Factor [Number]
Conv… Offset [Number]
Term
Role
Data Type
Bits [Integer]
String
Length [Integer]
Pattern [String]
Number
Precision [Integer]
Default Value [Number]
Minimum Value [Number]
Maximum Value [Number
Quantity (Amount)
Unit [Relation]
Relation
Class [Relation]
Role
Reverse Role [Relation]
o Temperature
o Volume
o Weight
o Monetary
…
View

13
The Intersection of Business & Device Ontologies
Towards a System of Business and Device Systems
As business systems and platforms are being re-designed to become IoT-centric, smart devices can be
engineered to be system-centric and leverage a Common Business Ontology to provide inherent
interoperability between business and device systems.
Smart
Product
Smart, Connected
Product Product System System of SystemsProduct
Irrigation
System
Weather Data
System
Seed Optimization
System
Equipment
System
Management
Business
System
Equipment
System
Controller
System
Source: Object Management Group / HBR

14
System Ontology for
Business & Device Processes…
…reference Attributes
within a Product/Device Ontology
“Blended”
Approach
#3
Class attributes within a single
Product ontology can support both
e-commerce & device system interop
A System
encapsulates Rule-
based Processes,
Attributes and
Connections to
other systems
Relationship
System Connection
System [Relation]
Sub System [Relation]
Enabled [Enumeration]
Rule
Within Process [Relation]
Process
Within System [Relation]
System Attribute
System [Relation]
Attribute [Relation]
System
Address [String]
Weight
Weight [Weight]
Temperature
Temperature [Temp…]
Sensor
Unit [Relation]
Time Interval [Time]
Controller
System [Relation]
Clock [Date/Time]
Switch [Boolean]
Motor
Speed [Rotat… Speed]
Valve
Open Level [Level]
Device
Status [Enumeration]
Battery Level [Level]
Product
Model [Identifier]
Image [URL]
Weight [Weight]
Actuator
Unit [Relation]

15
“Blended”
Approach
#4
Time Series for Business & Device Events
At 10:03 on 10/25 the Speed of Fan # 31 is 30 RPM
At 12:07 on 10/25 the Status of Order # 1032 is Shipped
State changes of devices and business objects can be both be recorded within a common-structured time series.
Order
Smart by Design
3100 Main Street
Suite 401
Glendale, CA 91201
Number: 1032
Date: 10/25/2017
Item Quantity Price Total Price
28301-42, Fan 1 129.95 129.95

16
Ontologies and Common API/Data Formats Positioned on the Interop Stack
TSN / Ethernet
(802.1, 802.3)
Wireless
PAN
(802.15)
Wireless
LAN
(802.11 Wi-Fi)
Wireless
2G/3G/LTE
(3GPP)
Wireless
Wide Area
(802.16)
Internet Protocol (IP)
IIC Framework
Top-Level Ontology (incl. Information Model) and Domain-Specific Ontologies
Common API & Message Payload Format
TCP UDP TCP
CoAP MQTT HTTP OPC-UA BinDDSI-RTPS
DDS
Partial Source: Industrial Internet Consortium
Towards a Common Data Format and API

17
This model can “blend” trending
architectural styles (such as
domain-driven design, model-
driven design , event sourcing, and
command query responsibility
segregation (CQRS)) to define
simple and scalable application
services for distributed object
management within a system of
interoperable systems.
A “Common API” Service Model for Semantic Interop and Fog Computing“Blended”
Approach
#5
HTML
Domain
Micro Service
Domain
Micro Service
Domain
Micro Service
HTML
Domain
Micro Service
Domain
Micro Service
Application
Service
Common API
Gateway
Controller
Controller
HTML
Domain
Micro Service
Domain
Micro Service
Domain
Micro Service
HTML
Domain
Micro Service
Domain
Micro Service
Application
Service
Common API
Gateway
Sensor
Actuator
Order
Item
Customer Site Inventory
Order
Business Ontology
Rule
System Unit Process
Attribute
Top-Level Ontology
Cloud
Source: ControlBEAM
Transport
Protocols

18
Serialized Grid Formats
For Data Exchange Payloads
Event/Query Processing
with Event Store
“Blended”
Approach
#6
“Blended”
Approach
#7
Common API
Gateway
Airflow Control System
Controller
Common API
Gateway
2D array
HVAC System
Controller
JSON
CBOR
Event
Processor
Event Store
Common API
Gateway
Query
Processor
QUERYEVENT
Identifier
Conversion
Unit
Conversion
… …
… …
… …
… …
Time-series and query-response
data are most efficiently contained
within a grid (2D array) structure
that can be serialized for transport.
The gateway can invoke separate
event and query-processing
services, which can update and
retrieve the state of objects that
persist in an “event store”.

19
“Event Sourcing” from Time Series Events within Event Store
An event store persists the state of
objects as a sequence of state-
changing events within a time
series.
Whenever the state of an object
changes, a new event is appended
to the event store.
By disallowing changes or
deletions of events, an event store
can provide a reliable audit log of
all changes made to an object.
05:25 on 10/2 Within Location Floor 4 3100 Main…
05:24 on 10/2 Deleted? Floor 4 No
12:47 on 9/19 Deleted? Floor 4 Yes
02:16 on 9/18 Name Floor 4 Fourth
02:15 on 9/18 Owner Party Floor 4 Investco
Location
Object
Object Location
Class Identifier Owner
Party
Name Deleted? Within Location Air Temp.
Floor 4 Investco Fourth No 3100 Main Street 77.4 ◦F
Event Store
Current State Primary Key
Event Sourcing
Object Creation

20
Location
Object
Attribute
A Common “Alternate Identifier” Conversion Service
Transport
& Logistics
An application service
can reference attributes,
modeled in a top-level
ontology, to convert
alternate identifiers
included in a time series
event.
air_Temp 28DJ…
Timestamp Attribute Class Object Value …
08:46 on 02/17 Location Inventory 18234… 3100 Main…
Object Attribute
Identifier Name Class Owner
Party
Within
Class
Data
Type
urn:epc:id:sgtin GTIN Attribute GS1 Product Identifier
urn:epc:id:sgln GLN Attribute GS1 Location Identifier
Object Location
Name GLN
3100 Main… 012345…
Identifier
Conversion
What Where When Why
Object Value Timestamp Attribute
[…id:sgtln]
0123456789012
[…id:sgln]
012345612345
08:46 on 02/17 Location

21
A Common “Measurement Unit” Conversion Service
An application service can
reference units, modeled in a
top-level ontology, to convert
alternate units of measure
included in a time series
event.
◦F ◦C
Unit
Conversion
Object Unit
Identifier Name Class Data Type
Base
Unit
Conv…
Factor
Conv…
Offset
◦F Fahrenheit Unit Temperature Celsius 1.8 32
◦C Celsius Unit Temperature
10:03 on 10/25 Air Temperature Floor Fourth 77.4 ◦F
Unit
Object
10:03 on 10/25 Air Temperature Floor Fourth 25.22 ◦C

22
Device Event triggers Business Events within a Time Series
Microservices consume and produce events
Order
Smart by Design
3100 Main Street
Suite 401
Glendale, CA 91201
Number: 1032
Date: 10/25/2017
28301-42, Fan 1 129.95 129.95
Event
Processor
Create Order
from Equipment
10:21 on 10/25 Status Fan zn3-fan6 Failed
10:21 on 10/25 Owner Party Order 1032 Smart by Design
10:21 on 10/25 Vendor Party Order 1032 Arrow
10:21 on 10/25 To Site Order 1032 3100 Main…
10:21 on 10/25 Status Order 1032 Released
10:21 on 10/25 Order Order Item 1 1032
10:21 on 10/25 Product Order Item 1 Fan
10:21 on 10/25 Quantity Order Item 1 1
10:21 on 10/25 Unit Price Order Item 1 129.95 USD
Order
Item
Order
Business Ontology

23
10:04 on 1/16 Data Type Attribute 84A5… Relation to Party
10:04 on 1/16 Within Class Attribute 84A5… Order
10:04 on 1/16 Name Attribute 84A5… Vendor
Object Creation 10:04 on 1/16 Owner Party Attribute 84A5… Verisign
10:03 on 1/16 Data Type Attribute 2ZK8… Enumeration
10:03 on 1/16 Within Class Attribute 2ZK8… Order
10:03 on 1/16 Name Attribute 2ZK8… Status
Object Creation 10:03 on 1/16 Owner Party Attribute 2ZK8… Verisign
Order
[Vendor]
[Street Address]
Number: [Number]
Date: [Date]
28301-42, Fan 1 129.95 129.95
Order
Vendor [Relation]
Status [Enumeration]
Attribute
Within Class [Relation]
Object
Class [Relation]
Identifier [Identifier]
Owner Party [Relation]
Name [Term]
Managing and Sharing Semantic Metadata
Metadata Managed as Data In addition to object instances,
an event store can persist the
definition of object classes and
attributes within an ontology,
as a sequence of state-
changing, time series events.
This “metadata” can be
created, updated, and shared
using the same Common API
and services utilized for “data”.
“Blended”
Approach
#8
Event Store
Event Sourcing
Object Attribute
Class Identifier Owner
Party
Name Within
Class
Data Type
Attribute 84A5… Verisign Vendor Order Relation to Party
Attribute 2ZK8… Verisign Status Order Enumeration
Vendor
Order
Business Ontology

24
Route Load
Vehicle
Top-Level Domains (TLDs) can host .commerce and industry-specific Ontologies
Order
Item
Order
Business Ontology
.transport
.energy
.com
[Brand].com
[Retailer].com
[Carrier].com
[Hospital].com
[ElectricCo].com
[Hospital].health
[Carrier].transport
[Retailer].retail
[ElectricCo].energy
Meter Grid
Service
Registry Layaway
Loyalty
Organ Disease
Patient
Object Internet Domain
Name
Owner
Party
Within
Domain
Registrant
Party
[Brand] Verisign, Inc. com [Brand, Inc.]
[Retailer] Verisign, Inc. com [Retailer, Inc.]
[Retailer] [Registrar, Inc.] retail [Retailer, Inc.]
Information within systems of TLD
registrants can inherently interoperate and
aggregate by sharing a common ontology
representing the “domain” of the TLD

25
At 10:04… the Temp… of Floor : 4 is 77.6 ◦F
At 09:17… the Building of Floor : 4 is 3100…
At 06:46… the Data Type of Attribute : Floor is Relation
Hub for Mapping to Legacy Platforms
“Blended”
Approach
#9
Driver/
Adapter
Relation-Centric
Model
Flexible
to Graph
Human-Generated
Web Content
Event
Processor
Event Store
Common API
Gateway
Query
Processor
QUERYEVENT
… …
… …
… …
… …
Triples Store
W3C
OWL
RDF RDFS
SPARQL
JSON-LD
Event-Centric
Model
Structured
to React
Machine-Generated
Data and Metadata
Floor 4 has the temperature 77.6
Floor 4 is within 3100…
Floor has the attribute Temp…
Descriptive predicateAttribute-value pair
 Simple  Scalable  Sustainable√ √ √

26
Business to Machine to Human Communications
Dynamically-Generated UI/HMI from Ontology Metadata“Blended”
Approach
#10
Enables replacement of single-
purpose native control apps
with a single UI framework
(runtime) that executes
metadata for contextual
information management and
remote device control. Also
providing a unified alternative
to SMTP.
Power: On
Common API
Gateway
Controller
EVENT
Source: ControlBEAM
Order
Item
Order
Business Ontology
Rule
System Unit Process
Attribute
Top-Level Ontology
Event
Processor
Event Store
Query
Processor
QUERY
Identifier
Conversion
Unit
Conversion
Runtime
API First
Controller
Arrow
Order 132
Status
Shipped
Items
Fan
X
… …
… …
… …
… …
… …
… …
… …
… …

27
Business to Machine to Human Communications
UI Translation from Controlled Vocabulary Terms First Primera
Primera: 75.9
Vocabulary Terms, modeled in a top-
level ontology, include separate
identifier/name attributes for machine
(382Y…) and human (First, Primera)
languages.
Elements Filter
Max
Rows
Floor,
Air Temperature
Site=
3100…
4
First 75.9
Second 72.3
Third 73.8
Fourth 77.4
Common Query Format
Query
Processor
(Request) (Response)
Event Store
Common API
Gateway
QUERY
Runtime
… …
… …
… …
… …
Primera 75.9
Segundo 72.3
Tercer 73.8
Cuarto 77.4
Elements Filter Language
… … Spanish
Object Term
Identifier Class English Spanish
382Y… Term First Primera
6839… Term Second Segundo
Term
Object
Query
Processor
Common Query Format

28
At 10:03 on 10/25 the Speed of Fan # 31 is 30 RPM
At 10:21 on 10/25 the Status of Fan # 31 is Failed
At 12:07 on 10/25 the Location of Inventory # 18234… is 3100…
At 12:07 on 10/25 the Status of Order # 1032 is Shipped
Towards an Ecosystem of Interdependent Systems
1
1
Homes &
Buildings
3
Transport
& Logistics
Retail
2
3
4
5
2
4 5
Common API
Gateway
Common API
Gateway
Common API
Gateway
Common API
Gateway
Common API
Gateway
3
Cross-Industry
Event Sharing
Time series events are a
lowest common denominator
spanning use cases and industries

29
Payment
Smart by Design
3100 Main Street
Suite 401
Glendale, CA 91201
Number: 1032
Date: 10/25/2017
28301-42, Fan 1 129.95 129.95
Invoice
Smart by Design
3100 Main Street
Suite 401
Glendale, CA 91201
Number: 1032
Date: 10/25/2017
28301-42, Fan 1 129.95 129.95
Shipment
Smart by Design
3100 Main Street
Suite 401
Glendale, CA 91201
Number: 1032
Date: 10/25/2017
28301-42, Fan 1 129.95 129.95
Order
Smart by Design
3100 Main Street
Suite 401
Glendale, CA 91201
Number: 1032
Date: 10/25/2017
28301-42, Fan 1 129.95 129.95
3
1
2
3
4
Store Home Public (Mall)
Create Invoice
from Order
Status of Order
is Shipped
Warehouse
Solving the Unified Commerce Challenge
1
[Brand].com [Retailer].comRetail
Transaction
Business Ontology
Process
Rule
1
2
A unified alternative to EDI
3 1
4
4
1

30
Inventory
Asset
… Attribute Class Object Value …
… Status Lot 3891 Recalled
Object Asset Inventory
Owner Party Location Lot Quantity
[Retailer] 210 Main St... 3891 1 EA
[Consumer] 650 4th Ave… 3891 1 EA
Store Home Public (Mall)
Retail
Warehouse
Solving the Supply Chain Traceability Challenge
[Brand].com [Retailer].com
1
1
Business Ontology

31
A McKinsey report estimates that
achieving interoperability in IoT would
unlock an additional 40 percent value in
the total available market.
Scaling Adoption of a Unified Approach | Business Value
Nearly 40 percent of value requires interop between IoT Systems
Source: McKinsey Global Institute 2015
1.3
0.7
0.7
0.5
0.4
0.3
0.3
Value potential requiring interoperability
$ trillion
Factories
Cities
Retail
Work sites
Vehicles
Agriculture
Outside
Potential
economic
impact of IoT
$11.1 trillion
38%
62%
% of total
value
36
43
57
56
44
20
29

32
Source: CrowdFlower Data Science Report 2016
Data scientists spend most of their time normalizing data
AI BI
A B C D
Adopting a unifying model for
Semantic Interoperability will
minimize data normalization
tasks and allow data scientists
to re-allocate their time to
refining algorithms, adding
significant business value.

33
Runtime ML AI
Top-Level Ontology (incl. Information Model)
and Domain-Specific Ontologies
Common API & Message Payload Format
BI
Enable business differentiation thru value-add services
built on a foundational layer of semantic interoperability
Moving Towards the Middle  Simple  Scalable  Sustainable
CoAP
HTTP
JSON
GS1
EDI
ID Keys EPCIS
GDSN CBV
SmartSearch
GPC
IETF
EPP
OMG
UPOS
UML DDS
ODM
OCF
Models
Haystack
Tags
“Business Standards”
Consortia
“Device Standards”
Consortia
Open
Group
O-DEF
TOGAF
Zigbee
Clusters
dotdot
Schema
.org
Ontology
Bluetooth
Profiles
Assigned
Numbers
“Blended”
Approach
XML
RDF OWL
MQTT OPC

34
Cross-industry semantic
interoperability, part two:
Application-layer standards
and open-source initiatives
interoperability, part three:
The role of a top-level
ontology
interoperability:
Glossary
“When we define a word
we are merely inviting
others to use it as we
would like it to be used;
that the purpose of
definition is to focus
argument upo…
embedded-computing.com
Q & A | More Info
Semantic Interoperability
A multi-part article series on cross-industry IoT interoperability from multiple industry experts
Hardware
Automotive
Networking
Processing
MakerPro
Industrial
Security
IoT
Storage
Medical
interoperability, part one
The basics
READ ARTICLE > READ ARTICLE > READ ARTICLE > READ ARTICLE >
IoT
What’s New
Semantic Interoperability
Node.js

Cross-Industry Semantic Interoperability: Achieving Interop

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Cross-Industry Semantic Interoperability: Achieving Interop

Similar to Cross-Industry Semantic Interoperability: Achieving Interop (20)

Recently uploaded

Recently uploaded (20)

Cross-Industry Semantic Interoperability: Achieving Interop