Hi, I finished the exercise and now you can get the list of FI-WARE GE Open Specifications linked to the IoT Chapter at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Internet_of_Things_.28IoT.29_Services_Enablement_Chapter Please, don't forget to confirm me what are the names of the companies we should list in the copyright sections of each specification. Last but not least, there is something that has called my attention ... I haven't seen any API specified regarding the IoT Gateway Protocol Adapter GE ... Is this correct ? It is the only FI-WARE GE that I know which doesn't export any API ... Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es<http://www.tid.es> email: jhierro at tid.es<mailto:jhierro at tid.es> twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 12/10/12 07:23, Juanjo Hierro wrote: Hi all, You may have probably received an email with the detailed instructions we will follow to carry out the third peer-review of FI-WARE GE Open Specifications. Previous to that, there was a step that each of the chapters had to carry out that implied a deep re-structuring of the wiki. This was decided several weeks ago and October 9-10 were days that were booked to perform the necessary steps in this re-structuring. Find below the email I sent to the WPLs/WPAs on the matter. Unfortunately, Thierry was sick and couldn't forward all this to you. Besides, I didn't realize myself because otherwise I may have forwarded the emails also to the IoT list. Nevertheless, don't worry, I'll take the action of re-structuring the contents of the wiki regarding the IoT chapter and get it ready along this morning (you owe me a beer ;-). The only info that I really need is who should be listed as owner of the specifications of each GE. My educated guess is the following: * Backend Things Management GE: NEC, Telefonica I+D * Backend Device Management GE: Orange, Telefónica I+D, NSN (we will need to consult Lorant or Denes) * Gateway Device Management GE: Ericsson * Gateway Data Handling GE: Orange * Gateway Protocol Adapter GE: Orange, Ericsson, Telecom Italia PLEASE, CONFIRM the above assumptions are correct. This is needed because we will include a copyright section on the Architecture Description and Open Specification documents linked to each of the FI-WARE GEs. A Legal Notice will also be added (the same we added to the API specs) which makes reference to the "copyright owners". Note that copyright only applies to specifications (and architecture descriptions). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es<http://www.tid.es> email: jhierro at tid.es<mailto:jhierro at tid.es> twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY Date: Tue, 09 Oct 2012 08:08:32 +0200 From: Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es> To: fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> <fiware-wpl at lists.fi-ware.eu><mailto:fiware-wpl at lists.fi-ware.eu>, fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> <fiware-wpa at lists.fi-ware.eu><mailto:fiware-wpa at lists.fi-ware.eu>, Sandfuchs, Thorsten <thorsten.sandfuchs at sap.com><mailto:thorsten.sandfuchs at sap.com> Hi all, This is a reminder that you have until EOB TODAY to re-structure the contents of the wiki that relate to GEs in your chapter. The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE <GE-name> in Chapter <Chapter-name> is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription.<Chapter-name>.<GE-name>. As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: 1. You should include a Copyright section which lists the copyright holders 2. You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications 3. You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. 4. Create a new page on the wiki named as FIWARE.OpenSpecification.Details.<chapter-name>.<ge-name>, where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. 5. Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.<chapter-name>.<ge-name> page) 6. On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and <any other potential user if applies>. For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to <explain-1>. Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. Indeed, it may not be a bad idea that each chapter leader takes care of the whole chapter revision himself or with the help of a few people. It's up to you. I have already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. That will save you some time. It took me a while (not more than half an hour) but I volunteered to speed up the overall process. If you have any doubt, don't hesitate to ask Thorsten (in copy of this email) or me Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es<http://www.tid.es> email: jhierro at tid.es<mailto:jhierro at tid.es> twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20121012/6e101a27/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy