[Fiware-wpl] Re-structuring contents of the public wiki towards re-submission of deliverables associated to FI-WARE GE open Specifications

Juanjo Hierro jhierro at tid.es
Mon Oct 1 20:06:42 CEST 2012


Hi all,

  Uwe Riss, Thorsten Sandfuchs and me have been working on the definition of a general schema to re-structure the contents linked to the FI-WARE Architecture Description and FI-WARE GE Open Specifications on the public wiki.   We have agreed on a schema that, in our honest opinion, will allow to resubmit the FI-WARE GE Open Specifications deliverables that will contain ALL the information that is expected by reviewers.

  According to the DoW (text in black):
GE Open Specifications will contain all the information required in order to build compliant products which can work as alternative implementations of GEs developed in FI-WARE and therefore may replace a GE implementation developed in FI-WARE within a particular FI-WARE Instance. GE Open Specifications will typically include, but not necessarily will be limited to, information such as:
*    Description of the scope, behaviour and intended use of the GE ==> This was, or should have been, covered in the Architecture Description of the GE (sections 1 - Overview, 2 - Basic Concepts, 3 - GE Reference Architecture, 4 - Main Interactions)
*    Terminology, definitions and abbreviations to clarify the meanings of the specification ==> This was covered in the section on 'Summary of key concepts introduced' of each chapter in the FI-WARE Product Vision
*    Signature and behaviour of operations linked to APIs (Application Programming Interfaces) that the GE should export.  Signature may be specified in a particular language binding or through a RESTful interface. ==> This was covered in the Open Specifications section within the Architecture description
*    Description of protocols that support interoperability with other GE or third party products ==> This should have been covered in the Open Specifications section within the Architecture description, although in most of the cases a protocol is not needed because interoperability would be achieved through REST
*    Description of non-functional features  ==> This should have been covered, at least partially, in the Architecture Description of the GE associated to section 5 on Design Principles

  All this information was already available on the public wiki at the time the FI-WARE GE Open Specifications were delivered (see comments in green color).   What the reviewers seem to miss were all points but the third (see comment on page 29 of the review report).    It now seems clear to us, according some feedback we ave received as well as our own analysis, that one of the mistakes we actually made is that we only submitted information about the 3rd point without little explanation why we omit the rest.

  Therefore, we should solve this issue for sure.   Ideally, this can be accomplished by making some re-structuring of the contents that should not require too much work/changes to the existing public Wiki.

  The approach that we will follow will be distributed via a wiki page which is still to be stabilized until tomorrow, but you can have a sneak preview here: (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template)

  Each WPL/WPA has to carry out the following basic tasks:


  1.  Perform the tasks described in the wiki page above per each GE of their chapters, which basically will mean rearranging some contents and creation of some wiki pages
  2.  Report progress via a web-cockpit out of the fi-ware-private-wiki page (sneak preview: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_cockpit)

  We hope that for all involved parties, the changes needed and time invest is designed to be as little as possible - if you see further possibilities on how to optimized this, please give feedback or provide your thoughts tomorrow in the call.
  Following this approach, we will be able to produce the Open Specification of a given GE <ge-name> part of Chapter <chapter-name> by printing the tree of contents linked to the FIWARE.OpenSpecification.<chapter-name>.<ge-name> wiki page.

  Tomorrow, we will explain all this in more detail and we will provide the calendar that we will follow with deadlines for applying these changes as well as changes resulting from the last peer-review.    Once we have dealt with the re-estructuring of contents on the public wiki, we will conduct a final peer-review to be closed by November 5th.

  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

________________________________

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




________________________________

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/fiware-wpl/attachments/20121001/139aa8a3/attachment.html>


More information about the Fiware-wpl mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy