<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div class="">Abajo encontrarán información sobre un workshop que puede interesarles </div>
<div class=""><br class="">
</div>
<div class="">Resumen: The workshop’s main focus will be on discussing the harmonization of </div>
information and data models for use with IoT deployments.
<div class=""><br class="">
</div>
<div class=""><br class="">
(A discussion about the difference between information and data models <br class="">
can be found in RFC 3444.)</div>
<div class=""><br class="">
<div class=""><br class="">
<div class="">
<div class=""><span style="font-family: Arial; font-size: x-small; orphans: 2; widows: 2;" class="">Christian O'Flaherty </span><a href="mailto:oflaherty@isoc.org" class="" style="font-family: Arial; orphans: 2; widows: 2;"><font color="#1c4aff" class="">oflaherty@isoc.org</font></a></div>
<div class=""><span style="font-family: Arial; font-size: x-small; orphans: 2; widows: 2;" class="">Regional Development -</span> <font color="#1c4aff" style="font-family: Arial; orphans: 2; widows: 2;" class="">Internet Society </font><br class="" style="font-family: Arial; orphans: 2; widows: 2;">
<span style="font-family: Arial; font-size: x-small; orphans: 2; widows: 2;" class="">Skype/Gmail/Yahoo!: </span><font color="#1c4aff" style="font-family: Arial; orphans: 2; widows: 2;" class="">christian.oflaherty</font><span style="font-family: Arial; font-size: x-small; orphans: 2; widows: 2;" class=""> </span><br class="" style="font-family: Arial; orphans: 2; widows: 2;">
<span style="font-family: Arial; font-size: x-small; orphans: 2; widows: 2;" class="">Mobile/WhatsApp:</span> <font color="#1c4aff" style="font-family: Arial; orphans: 2; widows: 2;" class="">+598 98769636</font></div>
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">Begin forwarded message:</div>
<br class="Apple-interchange-newline">
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">IAB Executive Administrative Manager <<a href="mailto:execd@iab.org" class="">execd@iab.org</a>><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">Call For Papers: IoT Semantic Interoperability Workshop</b><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">December 9, 2015 at 3:26:18 PM GMT-3<br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">"IETF Announcement List" <<a href="mailto:ietf-announce@ietf.org" class="">ietf-announce@ietf.org</a>><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Cc:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:iotsi@iab.org" class="">iotsi@iab.org</a><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Reply-To:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:ietf@ietf.org" class="">ietf@ietf.org</a><br class="">
</span></div>
<br class="">
<div class="">
<div class="">IoT Semantic Interoperability Workshop<br class="">
<br class="">
Background<br class="">
<br class="">
With the expansion of the Internet of Things (IoT), interoperability <br class="">
becomes more and more important. Standards-developing organizations have <br class="">
done a tremendous amount of work to standardize protocols to simplify <br class="">
implementation and to lower the cost of IoT products. As a result, new <br class="">
protocols were developed, existing protocols were combined in new ways, <br class="">
and lightweight profiles were defined.<br class="">
<br class="">
At the application layer, interoperability is not yet mature; the work <br class="">
on data formats (in the form of data models and information models) has <br class="">
not seen the same level of consistency throughout various <br class="">
standardization groups. Examples of standardization efforts in this area <br class="">
include the work by IPSO on their Starter Pack, the Cluster Library <br class="">
developed by the Zigbee Alliance, the OMA LWM2M, or the UPnP Management <br class="">
and Control:1 specifications.<br class="">
<br class="">
One common problem is the lack of an encoding-independent <br class="">
standardization of the information, the so-called information model. <br class="">
Another problem is the strong relationship with the underlying <br class="">
communication architecture, such as an RPC or a RESTful design. <br class="">
Furthermore, different groups develop similar concepts that only differ <br class="">
slightly, leading to interoperability problems. Finally, some groups <br class="">
favor different encodings for use with various application layer <br class="">
protocols.<br class="">
<br class="">
This raises a number of questions:<br class="">
<br class="">
- What is the state of the art in data and information models? What <br class="">
should an information model look like?<br class="">
- What is the role of formal languages, such as schema languages, in <br class="">
describing information and data models?<br class="">
- What is the role of metadata, which is attached to data to make it <br class="">
self-describing?<br class="">
- How can we achieve interoperability when different organizations, <br class="">
companies and individuals develop extensions?<br class="">
- What is the experience with interworking various data models developed <br class="">
from different groups, or with data models that evolved over time?<br class="">
- What functionality should online repositories for sharing schemas <br class="">
have?<br class="">
- How can existing data models be mapped against each other to offer <br class="">
interworking?<br class="">
- Is there room for harmonization, or are the use cases of different <br class="">
groups and organizations so unique that there is no possibility for <br class="">
cooperation?<br class="">
- How can organizations better work together to increase awareness and <br class="">
information sharing?<br class="">
<br class="">
(A discussion about the difference between information and data models <br class="">
can be found in RFC 3444.)<br class="">
<br class="">
Workshop Style<br class="">
<br class="">
The workshop’s main focus will be on discussing the harmonization of <br class="">
information and data models for use with IoT deployments. In order to <br class="">
keep the group at a manageable size, prospective participants are <br class="">
required to submit a position paper as an expression of interest. We <br class="">
will invite the authors of accepted position papers to attend the <br class="">
workshop.<br class="">
<br class="">
The workshop will be structured as a series of working sessions <br class="">
punctuated by invited speakers, who will present on-going <br class="">
standardization and research developments. The organizing committee may <br class="">
ask submitters of particularly salient papers to present their ideas and <br class="">
experiences at the workshop. We expect active participation of all <br class="">
guests.<br class="">
<br class="">
Participation at the workshop is free of charge.<br class="">
<br class="">
Important Dates<br class="">
<br class="">
Position papers must be submitted by February 22nd, 2016 at the latest.<br class="">
<br class="">
The program committee will review submitted position papers and send an <br class="">
invitation to the workshop to one of the paper authors. Invitations will <br class="">
be distributed by February 27th, 2016 at the latest.<br class="">
<br class="">
This workshop will be a day and a half, and take place on the 17th and <br class="">
18th of March, 2016.<br class="">
<br class="">
Position Paper Requirements<br class="">
<br class="">
Interested parties must submit a brief document. We welcome papers that <br class="">
describe existing work, answers to the questions listed above, new <br class="">
questions, write-ups of deployment experience, lessons-learned from <br class="">
successful or failed attempts, and ideally a vision. Contributions are <br class="">
not required to be original in content.<br class="">
<br class="">
We solicit brief write-ups of one to three pages, formatted as HTML, <br class="">
PDF, or plain text (for example as a submitted Internet Draft). <br class="">
Representatives of IoT Standards Development Organizations or Alliances, <br class="">
who have published relevant specifications, and representatives of <br class="">
vendors who have shipped commercial IoT products supporting multiple <br class="">
schemas, may minimally submit a pointer to existing documentation.<br class="">
<br class="">
We will publish accepted position papers (as well as meeting minutes, <br class="">
slides, and a workshop report). Please send your position paper to <br class="">
<a href="mailto:iotsi@iab.org" class="">iotsi@iab.org</a>.<br class="">
<br class="">
Venue<br class="">
<br class="">
The planned location for the workshop is San Jose, California, US. We <br class="">
will provide the full details of the meeting venue to the invited <br class="">
workshop participants. The workshop includes coffee and tea during <br class="">
breaks.<br class="">
<br class="">
IPR Policy<br class="">
<br class="">
The workshop will have no expectation of IPR disclosure or licensing <br class="">
related to its submissions.<br class="">
<br class="">
Privacy Notice<br class="">
<br class="">
You provide your name and your email address for the registration to <br class="">
this workshop. We use this information for planning purposes (such as <br class="">
finding rooms and ordering refreshments). We will also use this <br class="">
information to contact you about the location of the meeting venue, or <br class="">
other urgent and relevant notifications. Before the meeting minutes are <br class="">
publicly distributed, you will also receive a copy for review. We will <br class="">
share your contact details with the other workshop participants.<br class="">
<br class="">
Program Committee<br class="">
<br class="">
This workshop is organized by the Internet Architecture Board (IAB) and <br class="">
the following persons:<br class="">
<br class="">
- Jari Arkko, IETF Chair / Ericsson, Finland.<br class="">
- Ralph Droms, IAB / Cisco, US.<br class="">
- Jaime Jimenez, Ericsson, Finland.<br class="">
- Michael Koster, SmartThings/Samsung, US.<br class="">
- Dave Thaler, IAB / Microsoft, US.<br class="">
- Hannes Tschofenig, ARM Ltd, Austria.<br class="">
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</body>
</html>