[Fiware-wpl] SOME OF YOU ARE DOING IT WRONG

[Juanjo Hierro]

Hi,

  Some of you are doing it wrong and producing something that is more along the line of what should be added in month 12 than what I explained should go for month 9.

  For example, what is there regarding the Architecture Description of the Apps Repository:

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Apps.Repository

  Most of it is the enumeration of operations exported by the interface supproted an Apps Repository GE (implementation :-), even elaborating on the details of their signature (which is the level of detail that is not strictly needed in the Architecture Description).

  I understand this might be because you were still drafting this, but I'm worried that someone may go there and take it as a reference example.

  Please refer to the instructions provided.   For example, the "Main Interactions" section is missing.   The kind of narrative text that should go in a section within "Main Interactions" is the kind of text that I provided as reference example in the CORBA Event Service spec (which I attach again for your convenience).   If we were defining a Event GE implementing a service similar to the CORBA Event Service, the structure of the contents for the GE description would be the following:

 *   Overview (contents of sections 1.1 would go there, probably adding some sort of figure)
 *   Main concepts (contents of section 1.2 and 1.3 may go here and there wouldn't be a need for subsections but if we were talking about the CORBA Notification Service we would have a section elaborating on the language for filtering expressions)
 *   Main Interactions
    *   Basic Event Communication (contents of section 1.7 would go here, even with two subsections as in the CORBA spec)
    *   Event Communication through Event Channels (contents of section 2.2.1-2.2.4 would go here, including its subsections)
    *   Event Channel Administration (contents of section 2.2.5 would go here)
 *   Basic Design Principles (contents of section 1.4 and even 1.5 - 1.6, would go here)

  I hope this definitively helps.

  Even we are still refining it (the instructions came after Siemens had already provided a rather good piece of text)  you could see something more aligned to what is intended if you take a look of the QueryBroker GE Architecture Definition:

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Data.QueryBroker

  But what certainly provides a more accurate example is the mapping of CORBA specs to the template I provided above (of course, figures would need to be replaced by the corresponding FMC variants ;-)

  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/fiware-wpl/attachments/20120203/02db09dc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Event Service Specification 04-10-02.pdf
Type: application/pdf
Size: 515254 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20120203/02db09dc/attachment.pdf>