-
Notifications
You must be signed in to change notification settings - Fork 4
Candidate Breakout Topics
This page collects potential topics for breakouts on Sunday.
Not all of them will be possible as we have limited time; we will decide on Saturday.
So far, the subjects that came up during the state-of-the-union talk coordination call are all that is listed.
Initiative -- interoperable data definition -- cross-domain interoperability
Express everything in RDF? (+ OWL + RDF-Shape?)
Schema Frameworks and their practicalities
Tools
"there are lots of competing attempts at standards. There is not much yet on delivering the promise on aggregating the data across different specs. Question is what would it take to get interoperability across specs; can we bring things together at an API or database level. Ari suggested that this might be a good topic for a Sunday breakout."
"Carsten suggested a breakout session about terminology on Sunday. Milan: we were talking for two months before realized we were talking about different things."
How do we know when we are done? We need to check our designs against realistic use cases, which then turn into examples of using the technology. Different technological approaches should be measured against the same set of use cases/examples, so it is a good idea to collect them for all to use. How do we do that?
(Also touches on licensing and organization, below.)
Organizations and projects have different scope and play different roles with respect to each other. Still there is a fair amount of overlap and responsibilities. It is proposed to have a Breakout session to discuss about scopes (technical and commercial), overlaps, and potential collaborations, considering also administrative topics such as licenses, membership, openness, means of participation, etc.
Contact: Juan Carlos
"Identity management is an example for an issue not provided yet because different players have different models. Might use breakout to see how things can be harmonized. Carsten suggests having a Sunday breakout specifically for modeling identity management."
(Oscar Garcia-Morchon and Thorsten Dahm)
The IoT is exposed to a high number of attack vectors, that if sucessfully exploited by an attacker can have severe consequences. However, there are many different use cases and many different types of threats. Topics for discussion include: What are those threats? What are potential mitigation strategies? Which classification of use cases is a good one? Which threats apply to which use cases and which mitigation strategies should be used? What should be the processes to ensure a secure IoT system?
How do we handle the evolution of media types? The browser Web handles media type evolution (e.g., of HTML) pretty much outside the protocol features for content negotiation. For IoT, various proposals around media type versioning and the addition of version parameters to messages are more about preventing communication between incompatible implementations than actually about enabling communication. CoAP also has the specific challenge of mapping each new media type definition to a single number, so there is no "+cbor" or generic media type information that can be used in an implementation to enable partial processing of information. Can this maybe remedied by metadata (self-description/thing description)?