iot day 2016: cloud services for iot semantic interoperability

1

CLOUD SERVICES SUPPORT FOR IOTSEMANTIC INTEROPERABILITYIOT DAY 2016

IoT Day 2016 - Mark Underwood @Knowlengr Krypton Brothers - Creative Commons Attribution Share-Alike

MARK UNDERWOODKRYPTON BROTHERS LLC


2

ABOUT @KNOWLENGR (ME)

• CEO Krypton Brothers (NYC area) • Co-chair Summit on Ontologies for IoT

(2015)• Co-chair Security and Privacy subgroup

of the NIST Big Data Public Working Group

• Book chapter on Complex Event Processing for IoT Security (in press)

• ACM, IEEE, AAAI, ISACA, SHRM etc, etc.

3

MY IOT USE “CASES”



4

USE CASE:ELECTRIC VIOLIN

5

YAMAHA EV-5 CASE


6

SENSOR, DEVICE TYPES


7

REQUIREMENT: SENSOR, DEVICE UPGRADE


8

“TECHNICAL”REQUIREMENTS• Remote monitoring• Interface with existing applications• Recognize case placement• Issue alerts, not just continuous data stream• Support multiple models of humidistats• Identify location (geospatial)• Identify which instrument ($$$$ vs. $)• Recognize sensor failure • Full “ecosystem” (humidistat | humidifier | case

environment | location)


9

“BUSINESS” REQUIREMENTS

• Limited budget • Limited expertise for sensor technology• Access through smartphone • Access through web page • Prevent “catastrophic” drying • Address “case open” condition


10

FRONT-OF-NOSE CONSIDERATIONS?

• What solutions are already out there?• What are the sensor manufacturers providing?• What protocols are “winning”? • What giant, widely used apps or platforms should it

interface with (Facebook, Google, Microsoft, Verizon)?


11

BIG PICTURE CONSIDERATIONS• Use case contains multiple paradigmatic aspects• Hidden analytics needs (practical sweet spot for case

climate control)• Numerous rabbit holes for Not-Invented-Here development • Confluence of idiosyncratic requirements and “universal”

IoT requirements• Software development life cycle (SDLC) realities

• Error tolerance• Maintenance will exceed development costs

• Potential big distraction from practicing for performance


12

THE GO-TO, DEFAULTAGILE DEVELOPER SOLUTION IN 2016?

CLOUD SERVICES DRIVEN BY API-FIRST DESIGN

►Cloud often morphs to hybrid (connectivity, resilience, cost considerations apply), but folks embrace cloud-first mentality


13

CHECKERED SEMANTIC INTEROPERABILITY “SOLUTIONS” HISTORY


Credit: Leo Obrst, PhD at Mitre

14IoT Day 2016 - Mark Underwood @Knowlengr Krypton Brothers - Creative Commons Attribution Share-Alike This slide credit: Leo Obrst (Mitre)

15

ONTOLOGY MOTIVATORS

• Abstract models for devices, processes, events • “Upper ontology”

• Describe code fragments (e.g., classes) using taxonomies & vocabularies recognized by other developers

• Leverage stereotypical design patterns for UI• Recognize blurring with big data issue • Access “model-oriented” communities of interest


16

TRADEOFF DANCE• Implement an elegant solution • Avoid slippery floor spots

• endless refinement• unresolvable representation alternatives

• Devil is in the details • Cautionary tale:

Example from Financial Industry Business Ontology (FIBO)

• EHR Blockbuster film: EPIC vs. the Ontologists


17

QUESTIONS• What is the shape of existing cloud service design

patterns?• Are ontologies part of these patterns?• If so, what does it look like? • Which enterprise influencers are at work?• Which tools are being used? (Artifacts?)• Who are the people to watch?


18

CLOUD SERVICES ABSTRACT


Two important consequences of the “cloudification” of computing are DevOps and an API-first (espoused by Intel’s Brian Krzanich) design philosophy. While SOA and “composable services” introduced many of the same concepts in earlier generations (indeed, both DevOps and API-first steal from well-burnished concepts), the level of adoption across software and data providers is unprecedented. Computing environments for large scale projects can be stood up in minutes, tested and disposed of the following day. Products like Zapier and IFTTT allow for orchestration of cloud services across providers. The Zapier App Directory offers around 100 integrations. Interop exists across platforms (as in hybrid cloud storage), applications (e.g., between QuickBooks and a telephony app like DialMyCalls), and also what some are calling “cognitive services.” Cloudify suggests using TOSCA (a cloud orchestration standard) to connect resources like OpenStack or VMware using open source tools.)

Github repositories can store ontologies, but can this be scaled up to build applications, sharing ontologies within or across domains? Will developers tempted to use ontologies be able to gain the same productivity benefits they experience elsewhere with cloud services? We ask a few vendors.

https://zapier.com/zapbook/

https://zapier.com/zapbook/

19

API-FIRST DESIGN


API-first design is a result of ubiquitous cloud services and DevOps, but its impact is not limited to that: IoT development is inspired by the same design patterns. Ontologies could / should be similarly ubiquitous to deploy. Are they?

20

WHY API-FIRST?Browse cloud service integrations at Zapier, ProgrammableWeb and IFTTT


21IoT Day 2016 - Mark Underwood @Knowlengr Krypton Brothers - Creative Commons Attribution Share-Alike

22

PROGRAMMABLE WEB


23

CLOUD SOLUTIONS: COMMERCIAL TRACTION


25

IBM WATSON:“ONTOLOGY ANALYSIS”


27

SAS: ONTOLOGY FOR ANALYTICS & BIhttp://www.sas.com/en_us/software/analytics/ontology-management.html


28

SAS: ONTOLOGY MANAGEMENT STUDIOIncludes class editing, XML import, RDF formats


29

ORCHESTRATION AS KEY• Emerging as central issue

in NIST Big Data Working Group Security and Privacy (bigdatastandards.com)

• Reality: multiple services, vendors, standards

• Role of people must be surfaced design patterns

• Re-emergence of workflow


30

OASIS TOSCATOSCA: Topology and Orchestration Specification for Cloud Applications


https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca

31

SDN MEETS ONTOLOGY?


32

SAP RESEARCHVia: Florian Probst (c. 2012) “SAP Research: An Industry Perspective on Semantic Technologies”• Probst walks through several use cases and

prototypes, including EMS, oil & gas • Lessons learned:

• Establish role for “ontology engineer”• Improved browsers for ontology editors, help, &

visualization metaphors• “Ontologies are still hard to use for software

engineers while the benefit is not directly obvious”• There are performance issues• Need new mechanisms for semantic annotations


33

PROGRESS WITHIN THE DOMINANT DESIGN PATTERN? HTTP://ISERVE.KMI.OPEN.AC.UK/


34

ISERVE (CONT’D)Open Source: https://github.com/kmi/iserve •Web Application -iServe Browser•Read&Write RESTful API•Linked Data principles•SPARQL endpoint•Content negotiation (RDF, HTML)


https://github.com/kmi/iserve

https://github.com/kmi/iserve

36

ISERVE ON SWAGGER + GITHUB“By this all people will know you are my discipline.” (refactoring of John 13:25)



“Swagger is a simple yet powerful representation of your RESTful API. With the largest ecosystem of API tooling on the planet, thousands of developers are supporting Swagger in almost every modern programming language and deployment environment.With a Swagger-enabled API, you get interactive documentation, client SDK generation and discoverability.We created Swagger to help fulfill the promise of APIs. Swagger helps companies like Apigee, Getty Images, Intuit, LivingSocial, McKesson, Microsoft, Morningstar, and PayPal build the best possible services with RESTful APIs.

38

PROGRESS?

CLOUD SERVICES FOR ONTOLOGIES


39

WHERE ARE ONTOLOGIES?


40

CURRENT STATUS OF ONTOLOGY CLOUD SERVICE OFFERINGS• Too few initiatives (search Github, Swagger)• Some of the few are industry giants • Adoption is being pushed from top (SAS), bottom (Nakina

Systems), and middle (SAP) • There are clear use cases (e.g., CRM marketing automation) • Competing software development life cycle models still prevail• Among semantically rich alternative development models,

even they have light traction (model-driven development, domain-specific development)

• Roll-your-own (without ontologies) must get harder.• iServe, ProgrammableWeb potential influencers


https://msdn.microsoft.com/en-us/library/cc512847(v=vs.100).aspx


41

PROJECT STALL• Which upper ontologies do I

need?• Evolving home monitoring

ecosystem (Verizon?)• Lack of APIs• Low tech commercial

landscape • Use case not compelling

enough • Development challenge

nontrivial

42

MEANS TO AN END


Standards, APIs, even programming languages have limited lifetimes.(MIDI is a mind-numbing exception.)

Building apps that endure is a nontrivial challenge.

Think Bach, not Google.

43

SEMANTIC INTEROPVIA CLOUD SERVICES

MARK UNDERWOOD


KRYPTON BROTHERS LLC | KRYPTONBROTHERS.COM@KNOWLENGR [email protected] ALSO: ONTOLOGYSUMMIT.ORG

mailto:[email protected]

iot day 2016: cloud services for iot semantic interoperability

Technology