Organizations roles

What role could the various organizations fill in the architectural picture?

OneM2M:

• Core Ontology [license?], aligned with SAREF [SSN?]
• SDT tool (abstract information models)

iot.schema.org:

• Bridge between ontologies and connected things
• Design patterns for information models
  • "All smart home so far"
  • Cover domains automotive, healthcare
• Integrate IPSO, OCF models
• As we grow, add connections to physical world (➔ schema.org)
• "digital affordances for physical objects"
• out of comfort zone with protocols...

YANG directorate, YOT@IETF.ORG:

• (w/ OMA: YANG mapping of IPSO)
• SID registry
• import iot.schema.org semantics into YANG
• models for network and device management

OMA:

• Schema, LWM2M editor tool (used by IPSO smart objects)
• ? map to YANG? https://tools.ietf.org/html/draft-vanderstok-core-yang-lwm2m
• find right registry policy
• focus on "last mile", focus on constrained devices
• atoms (resources) and molecules (devices); levels of clustering

W3C WoT:

• Integration of different platforms
• Thing Description w/
  • Metadata about things
  • Interaction Model
  • Protocol mapping
• Thing descriptions:
  • can "attach" to Things
  • (partially) can be generated out of OCF metadata, easy with OneM2M, also BACnet; hard with MODBUS (but give the developer a way to annotate that)
• could integrate Linked-Data or even flat vocabularies -- do not define domain specific vocabularies here
• everything is in RDF ("JSON-LD"), or maybe go back to trees ("JSON") instead (can be converted to RDF)
• TD defines interaction patterns (properties, actions, events), iot.schema.org defines what they mean wrt outside world
• TD of thing classes vs. instances
• looking at lifecycle (manufacturer, installer)

OCF:

• works pairwise with other orgs (OneM2M, ...)
• bridging framework (not OCF specific), compare with other bridging frameworks?
• Making RDs be more common -- common RD implementation? (needs to accomodate OCF flavor link-format)
• attempt to not invent schema languages (was RAML/JSON Schema, now Swagger 2.0), would like address limitations in that! (Re JSON Schema: Written down on some OCF mailing list; data types are limited (Swagger a bit better -- can also use Regexps))
• oneIOTA repository; OCF, Alljoyn translated to Swagger ➔ supplier of Tagging dictionaries/vocabulary

openT2T.org:

• translators to things.org; github repo of implementations of translators (today: JS and node.js); can pull down JS dynamically based on RT

Fairhair:

• enable manufacturer to give the needed information
• no "fairhair objects", but reuse from BACnet, ZigBee, KNX -- provide information in a consistent way
• info ready for integration into a CoRE resource directory (RFC6690-based)
• authorization information
• control may be in the future
• get the semantic annotations from the manufacturers

Haystack:

• Supplier of Tagging dictionaries/vocabulary

IPSO:

• Supplier of Tagging dictionaries/vocabulary (existing Smart Objects, in Github; Tools can work closely with OMA)
• Collaborating with Haystack and several others