Dear all, I have written below a draft letter for friendly ETSI Board members and additional potential Founding Members which you may want to adapt for your specific contacts ? I use very cautious language when referring to previous "concerns" of ETSI: if you can think of any better wording or extra points please let me know! Perhaps one strong paragraph about the urgent need for the CIM should be added? Any suggestion? cheers Lindsay Subject: Request support on an ETSI ISG on Context Information Management - may I please call you about it? Dear XXXX, The attached version of the ISG CIM may be on the 01.12.2016 ETSI BoD agenda for discussion, of may miss that and be sent a few days later by Board emails. I would very much like to discuss it with you, in the hope that your company might consider becoming a Founding Member. What is the purpose of the Industry Standards Group CIM? Basically a number of SmartCities and companies are trying to get clearer standards for exchange of "context" information, at the application level above oneM2M (or other IoT platforms). The prototype for the API is the OMA NGSI 9 and 10, but that may change/adapt during the work. Certainly a lot of people want to see a JSON-LD binding and interop with various Open Data systems. [cid:image003.png at 01D248FA.4C32FEC0] There are huge numbers of existing data exchange protocols, leading to lack of critical mass and lack of interoperability. The first work of the ISG CIM will be to draw together the different views (and stakeholders) and identify gaps and ways forward; the immediate next step will be to identify an API with widest possible support. We have had a LOT of discussions with ETSI officials, trying to overcome initial concerns due to a perhaps too strong emphasis on specific protocols as initial prototypes and also to too much emphasis on open source implementations (which Smart Cities very strongly want, but which cannot be written into ETSI documents because of current ETSI IPR policy). We have put a lot of emphasis on outreach to stakeholders, and also to "not reinventing the wheel" (i.e. avoiding duplicating work in ETSI SmartM2M or oneM2M) : a) Figure 1 now shows clearly that the CIM work is "on top of" oneM2M, not competing (oneM2M is concerned about this, and ETSI has some legal constraints as you may know). b) IPR rules are "Group Specifications developed within the ETSI ISG CIM will be public and subject to ETSI IPR policy." c) There is at 2 months a joint f2f workshop scheduled with ETSI SmartM2M and others, to compare approaches d) The "informative" phase of getting info from other SDOs is now increased to 5 months e) There is at 12 months a Review of Work and proposal to ETSI for next period (where ETSI might consider to stop the work if overlap with other SDOs is considered too strong) f) There is the option in month 22 for a revised version of specifications, if user groups show significant adaptions are needed in practice. We hope all these things will ensure success and wide support. My job now is to reach out to potential founding members, to enquire about interest. We believe that very many application developer companies, smart city integrators, major vendors and operators will see the potential. Please let me know when you would be available for a call? best wishes XXXQQQQ -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-oasc-etsi/attachments/20161128/04d982f7/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: oledata.mso Type: application/octet-stream Size: 161240 bytes Desc: oledata.mso URL: <https://lists.fiware.org/private/fiware-oasc-etsi/attachments/20161128/04d982f7/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 69928 bytes Desc: image003.png URL: <https://lists.fiware.org/private/fiware-oasc-etsi/attachments/20161128/04d982f7/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: Draft ETSI ISG proposal for cross-cutting Context Information Management.pdf Type: application/pdf Size: 543624 bytes Desc: Draft ETSI ISG proposal for cross-cutting Context Information Management.pdf URL: <https://lists.fiware.org/private/fiware-oasc-etsi/attachments/20161128/04d982f7/attachment.pdf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy