Hi, I wouldn't like to spend too much time on this because, at the end of the day, if may well happen that we spent more time discussing this on the email that actually implementing the changes we are requesting. On 28/02/12 11:49, Leidig, Torsten wrote: Hi Juanjo, Again I’m confused. You write we should rename OpenSpecification into ArchitectureDescription. Besides the fact that the majority of GE are described as Open Specifications in the Wiki, As I have explained that the change is not just a matter of taste. I believe that keeping usage of the term "specification" limited to the set of specs we have to deliver in month 12 we will avoid problems (see below). By using the term "specification" here and there, people may get confused on what we mean when we talk about "specifications". I see the following problems: · If the Open Specs are now the Architecture, what do we deliver in M12 for the Open Specifications? I believe I have explained this several times. In M12 we have to specify, in their full extend, the signature and behavior (including, exception handling) of all the operations in interfaces supported by FI-WARE GEs. In my honest opinion (this is a discussion we have to launch right now) we should also provide a RESTful binding for the interface specifications. In this deliverable we have introduced names of interfaces and operations, and have provided a high-level description of arguments/responses linked to operations as well as behavior operations. We have also illustrated usage of interfaces and operations through description of main interactions. · The current content for the Open Specs in the Wiki are actually high-level (abstract) specifications for the GE. This is the kind of discussion I want to avoid. If we say that what we deliver now are "high-level specifications" and what we will deliver in month 12 are "open specifications", I'm sure we will open a debate about what "specification" means. Given the fact that the deliverable committed in month 9 was titled "FI-WARE Architecture", let's then call what we have produced in a way that sounds more consistent. Some people may argue that what we are delivering is not an Architecture Description but this is again a religious discussion. I can argue that we are delivering the description of a Reference Architecture for each chapter and, in line with the definition of wikipedia: "A reference architecture often consists of a list of functions and some indication of their interfaces (or APIs) and interactions with each other and with functions located outside of the scope of the reference architecture" which actually matches pretty well with what we are delivering now. · The internal architecture of a GE is irrelevant to the users of a GE. They just need to now the interaction protocols and non-functional properties. That's why we are not delivering in the current deliverable the internal architecture of GEs. · Shouldn’t we focus on implementation of the first release now? From now on, we should focus on delivering an implementation of the GEs for the first release, as well as the full specification of those GEs. Both are the main deliverables in month 12: open specifications (detailed to full extend) and software implementing those open specifications that works. My understanding so far was that there is a Chapter Architecture for each chapter, which is D.2.3 and the Open Specifications for each GE, which is D.3.1. (D.x.1) Yes ! So ? What’s really missing is the overall architecture across the chapters as part of D.2.3! That's true. We haven't had time to cover that and probably this will be a criticism we will receive. My plan on the matter is that TID will produce a first draft of a section that we may title "Bringing all pieces together" that would be part of the deliverable. We will try to have it ready by end of March so that we can submit it to all WPAs and discuss it before publication. Hopefully, this may take place by end of April, that is before the official review, which is what at the end of the day matters. This, on the other hand, makes more sense now that still are some issues regarding cross-chapter integration that are still under discussion (e.g., integration of IoT GEs with Data Context Management GEs) Best, -- Juanjo Regards, Torsten From: fiware-wpa-bounces at lists.fi-ware.eu<mailto:fiware-wpa-bounces at lists.fi-ware.eu> [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 28. Februar 2012 07:43 To: 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> Subject: [Fiware-wpa] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki Hi all, You will find the instructions to port contents of the Architecture deliverable from the FI-WARE Private wiki to the public FI-WARE wiki at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_publish_contents_in_the_FI-WARE_public_wiki PLEASE take your time to review the steps (there are some IMPORTANT notes you have to follow in order to perform the publication properly) Please note that ONLY the following chapters/GEs Architecture Descriptions will be published: * Cloud: all contents except those of the Monitoring GE * Data: all contents except those of the Pub/Sub GE * IoT: backend part (but pending of last revision, overall of the exposure GE, I'm currently doing) * Apps: all contents of the Business-related GEs (that is, USDL, Repository, Marketplace, Registry, RSS) Publication of the whole contents of the Security, I2ND and Tools chapters, as well as remaining contents of the chapters listed above will be deferred to March 6th. We will continue working on each chapters during this week until we close the deliverable. Please share this instructions with members of your team. If you have any comment or question, please don't hesitate to formulate it. 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 ________________________________ 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/20120228/567f94f8/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy