From thierry.nagellen at orange.com Wed Feb 1 08:18:18 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 1 Feb 2012 08:18:18 +0100 Subject: [Fiware-wpl] Standardization Message-ID: Dear all, On behalf of NEC, do not forget standardization deliverable: one action per partner and one action per WPL (a whole introduction to describe how your WPs expect to deal with standardization) We missed the deadline which was yesterday so we have to improve it ASAP. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2012-01-25 FI-WARE Standardization_Request.pptx Type: application/octet-stream Size: 761098 bytes Desc: 2012-01-25 FI-WARE Standardization_Request.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-Ware_Input_for_Standardisation_Plan_5AnswersFrom26_20120125.docx Type: application/octet-stream Size: 284478 bytes Desc: FI-Ware_Input_for_Standardisation_Plan_5AnswersFrom26_20120125.docx URL: From jhierro at tid.es Wed Feb 1 08:49:42 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Feb 2012 08:49:42 +0100 Subject: [Fiware-wpl] First FI-WARE Open Call announced Message-ID: <4F28EE96.7060404@tid.es> Hi, The first FI-WARE Open Call has already been published. Details can be found at: http://www.fi-ware.eu/open-call/ Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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: From jhierro at tid.es Wed Feb 1 09:54:42 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Feb 2012 09:54:42 +0100 Subject: [Fiware-wpl] Standardization In-Reply-To: References: Message-ID: <4F28FDD2.10305@tid.es> Hi, I may be wrong, but there were a couple of comments we make during our IoT chapter session last week that should work to make development of this deliverable easier. I haven't seen any email from NEC updating all the chapters on this. But I may be wrong ... Please, take care of this. Regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 01/02/12 08:18, thierry.nagellen at orange.com wrote: Dear all, On behalf of NEC, do not forget standardization deliverable: one action per partner and one action per WPL (a whole introduction to describe how your WPs expect to deal with standardization) We missed the deadline which was yesterday so we have to improve it ASAP. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com ________________________________ 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: From Ernoe.Kovacs at neclab.eu Wed Feb 1 10:06:34 2012 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Wed, 1 Feb 2012 09:06:34 +0000 Subject: [Fiware-wpl] Standardization In-Reply-To: <4F28FDD2.10305@tid.es> References: <4F28FDD2.10305@tid.es> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C24F79880@PALLENE.office.hd> Hi Juanjo. the forwarded mail by Thierry included the changes. Due to timing issues, the proposed changes need to be worked into the sections of the WPL/WPAs. that's why it was forwarded... - Ern? From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Mittwoch, 1. Februar 2012 09:55 To: fiware-wpl at lists.fi-ware.eu; Ernoe Kovacs Cc: fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpl] Standardization Hi, I may be wrong, but there were a couple of comments we make during our IoT chapter session last week that should work to make development of this deliverable easier. I haven't seen any email from NEC updating all the chapters on this. But I may be wrong ... Please, take care of this. Regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 01/02/12 08:18, thierry.nagellen at orange.com wrote: Dear all, On behalf of NEC, do not forget standardization deliverable: one action per partner and one action per WPL (a whole introduction to describe how your WPs expect to deal with standardization) We missed the deadline which was yesterday so we have to improve it ASAP. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com ________________________________ 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: From jhierro at tid.es Wed Feb 1 10:29:42 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Feb 2012 10:29:42 +0100 Subject: [Fiware-wpl] Standardization In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C24F79880@PALLENE.office.hd> References: <4F28FDD2.10305@tid.es> <8152E2132B13FB488CFD1947E2DEF19C24F79880@PALLENE.office.hd> Message-ID: <4F290606.6070108@tid.es> Ok. I didn't realize about the attachments probably because Thierry didn't mention them in the body of his message. Hope my mistake helps to highlight that there were those attachments :-) Best, -- Juanjo On 01/02/12 10:06, Ernoe Kovacs wrote: Hi Juanjo. the forwarded mail by Thierry included the changes. Due to timing issues, the proposed changes need to be worked into the sections of the WPL/WPAs. that?s why it was forwarded? - Ern? From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Mittwoch, 1. Februar 2012 09:55 To: fiware-wpl at lists.fi-ware.eu; Ernoe Kovacs Cc: fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpl] Standardization Hi, I may be wrong, but there were a couple of comments we make during our IoT chapter session last week that should work to make development of this deliverable easier. I haven't seen any email from NEC updating all the chapters on this. But I may be wrong ... Please, take care of this. Regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 01/02/12 08:18, thierry.nagellen at orange.com wrote: Dear all, On behalf of NEC, do not forget standardization deliverable: one action per partner and one action per WPL (a whole introduction to describe how your WPs expect to deal with standardization) We missed the deadline which was yesterday so we have to improve it ASAP. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com ________________________________ 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: From jhierro at tid.es Thu Feb 2 09:14:53 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 02 Feb 2012 09:14:53 +0100 Subject: [Fiware-wpl] Guidelines section for Architecture Description deliverable available on the Wiki Message-ID: <4F2A45FD.8080607@tid.es> Hi all, I have published a set of guidelines to be followed for the development of the Architecture Description deliverable: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions This how-to will be enriched during the following days, including a complete example. However, I believe it contains already enough detailed instructions about how to proceed. Of course, your feedback is welcome. Answering your concrete questions may help to enrich the how-to material. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 From torsten.leidig at sap.com Thu Feb 2 15:58:06 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Thu, 2 Feb 2012 15:58:06 +0100 Subject: [Fiware-wpl] [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki In-Reply-To: <4F2A45FD.8080607@tid.es> References: <4F2A45FD.8080607@tid.es> Message-ID: Hi Juanjo, Now we have at least some guidelines. After looking at some of the existing OpenSpec pages from different chapters I found that no two pages look similar. So I still recommend to provide a template in order to ensure a common uniform style. Some comments to the instructions: You write the target audience are developers of applications or other GEs. Call me stupid but I still have the feeling that I don't get the meaning of GE concept right. My understanding is that a GE is describing a general functionality (such as a "network printing") for which a number of technical realizations can exist (several technical protocols for network printers). So a developer will not use the GE to build applications, he/she rather looks for implementations of the GE which match his/her requirements in terms of non-functional requirements such as cost, interoperability, performance, scalability, SLA, legal, .and so on. What we actually do in FI-WARE is defining the GE on a level that abstracts from concrete technical realizations. How do we describe GE? I think in terms of their interaction behavior, composition, dependencies, etc. which need to (or may) be provided by a GE implementation. Following this interpretation nobody develops GE, people rather should be able to implement components that conform to GE. The Open Specification must be written in a way to allow developers to implement a GE on its own. Also no one develops applications on top of GE, applications are developed on top of GE implementations exposing a GE conformant technical interfaces. There could be a catalog of GE implementations that can be used by application developers, which is organized around the GE model. For example as an application developer I look for a implementation of the "Network Printing" enabler, which satisfies my requirement in my situation. Via the catalog (or Marketplace) I can find it. So an Open Specification for a GE should only describe what it is used for and how one can interact with it, in a technology neutral way. It must not prescribe concrete technical interfaces. Nevertheless, FI-Ware can list or even recommend example technical interfaces in order to harmonize the platform architecture. In the example of the Apps Repository Enabler I tried to separate the generic part of the GE and the technical part of its implementation by keeping the GE specification neutral and linking to specific technical interfaces (of implementations) at the end of the article. If this doesn't make sense to you, please take another try to enlighten me. Regards, Torsten PS: According to the style suggestions you made (italic bold) I recommend to use MediaWiki templates again. I provided and used a couple of them in the Repository pages (e.g. {{Parameter}} ), we could provide more of them. The advantage would be that you can change the rendering and style later without having all people to change every page. -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Donnerstag, 2. Februar 2012 09:15 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki Hi all, I have published a set of guidelines to be followed for the development of the Architecture Description deliverable: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions This how-to will be enriched during the following days, including a complete example. However, I believe it contains already enough detailed instructions about how to proceed. Of course, your feedback is welcome. Answering your concrete questions may help to enrich the how-to material. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa From jhierro at tid.es Fri Feb 3 08:24:04 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 03 Feb 2012 08:24:04 +0100 Subject: [Fiware-wpl] [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki In-Reply-To: References: <4F2A45FD.8080607@tid.es> Message-ID: <4F2B8B94.10509@tid.es> Hi, I would never call someone stupid for asking questions :-) Besides, questions that come from a rigorous analysis of terms and definitions are always good questions because it's quite important that we align on terms and definitions. Strictly speaking, we should never use the term "Generic Enabler" or "GE" alone in many of our sentences. It doesn't mean anything tangible. What do really exist (i.e., refers to something "tangible") are things like: * "GE specifications" (or "GE Open Specifications") * "a GE implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". Then, whenever we say, as part of a given Architecture Description (which I believe we should not try to call "Specification") something like: "The IaaS Service Manager GE invokes the xxx operation exported by an IaaS Resource Manager GE to instruct them to provision the VApp" (A) we should indeed say: "The IaaS Service Manager GE implementation invokes the xxx operation exported by an IaaS Resource Manager GE implementation to instruct them to provision the VApp" (B) However, I believe that this would lead us to documents that would be rather "verbose". On the other hand, using (A) instead of (B) in standard specifications is rather common and many people would understand that you should make the distinction but you don't make it to for the sake of non-verbosity. I would go for putting a note somewhere at the beginning of the Architecture Description deliverable, where we may say something as: In order to avoid a too verbose text, we typically use the term " GE" or simply "" (e.g., "QueryBroker GE" or "QueryBroker") to refer to "an implementation of the GE Open Specifications" (e.g., "an implementation of the QueryBroker GE Open Specifications"). Note that the notion of GE is abstract and what actually refers to tangible things are: * "GE Open Specifications" which contain all information required in order to build components which can work as implementations of GEs. * "a GE Implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". You may refer to the set of terms and definitions provided at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision#Summary_of_key_concepts_introduced Would you agree ? (if you can produce a better text, I would be happy to take it) BTW, I honestly believe we provide an accurate definition of terms at the link referred about (part of the FI-WARE Product Vision. I tell you that I intend to make an serious effort to be rigorous and provide a set of consistent and well-defined terms, maybe we could add "GE implementation" but that was implicit in the existing ones and should be defined as a "Components in a given Platform Product that implement a given GE Open Specification". As for the template ... I'm not sure what do you mean what you say when you still ask for "a template". I would consider the proposed ToC for chapters as a "template" that chapter teams have to follow. If you mean that we should provide a "Wiki template", I'm not sure whether it would be a little bit cumbersome ... and at the end difficult to manage. I bought the benefit of using them for the Backlog Entry Descriptions but I'm not sure for each and every page on our Wiki ... May you provide an example of how that template may look like so that we can play with it a bit ? On the other hand, don't forget that there are many contributors who don't know the details about the MediaWiki language so that they indeed first write their contribution in Word and then "save as MediaWiki", then do some fine tuning ... We may need to explain what they should do there. As for the {{Parameter}} thing, I have to confess that I'm not that an expert on MediaWiki and probably you are right. However, we again have to take into account that many people will produce their initial input using Word, so therefore we should give them very precise instructions on how to edit the resulting MediaWiki text and add these {{Parameter}} thing. I sincerely take a look at what you did in your chapters and this is going to be wayyyy difficult to explain and cumbersome to implement. Best regards, -- Juanjo On 02/02/12 15:58, Leidig, Torsten wrote: Hi Juanjo, Now we have at least some guidelines. After looking at some of the existing OpenSpec pages from different chapters I found that no two pages look similar. So I still recommend to provide a template in order to ensure a common uniform style. Some comments to the instructions: You write the target audience are developers of applications or other GEs. Call me stupid but I still have the feeling that I don't get the meaning of GE concept right. My understanding is that a GE is describing a general functionality (such as a "network printing") for which a number of technical realizations can exist (several technical protocols for network printers). So a developer will not use the GE to build applications, he/she rather looks for implementations of the GE which match his/her requirements in terms of non-functional requirements such as cost, interoperability, performance, scalability, SLA, legal, .and so on. What we actually do in FI-WARE is defining the GE on a level that abstracts from concrete technical realizations. How do we describe GE? I think in terms of their interaction behavior, composition, dependencies, etc. which need to (or may) be provided by a GE implementation. Following this interpretation nobody develops GE, people rather should be able to implement components that conform to GE. The Open Specification must be written in a way to allow developers to implement a GE on its own. Also no one develops applications on top of GE, applications are developed on top of GE implementations exposing a GE conformant technical interfaces. There could be a catalog of GE implementations that can be used by application developers, which is organized around the GE model. For example as an application developer I look for a implementation of the "Network Printing" enabler, which satisfies my requirement in my situation. Via the catalog (or Marketplace) I can find it. So an Open Specification for a GE should only describe what it is used for and how one can interact with it, in a technology neutral way. It must not prescribe concrete technical interfaces. Nevertheless, FI-Ware can list or even recommend example technical interfaces in order to harmonize the platform architecture. In the example of the Apps Repository Enabler I tried to separate the generic part of the GE and the technical part of its implementation by keeping the GE specification neutral and linking to specific technical interfaces (of implementations) at the end of the article. If this doesn't make sense to you, please take another try to enlighten me. Regards, Torsten PS: According to the style suggestions you made (italic bold) I recommend to use MediaWiki templates again. I provided and used a couple of them in the Repository pages (e.g. {{Parameter}} ), we could provide more of them. The advantage would be that you can change the rendering and style later without having all people to change every page. -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Donnerstag, 2. Februar 2012 09:15 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki Hi all, I have published a set of guidelines to be followed for the development of the Architecture Description deliverable: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions This how-to will be enriched during the following days, including a complete example. However, I believe it contains already enough detailed instructions about how to proceed. Of course, your feedback is welcome. Answering your concrete questions may help to enrich the how-to material. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa . ________________________________ 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: From jhierro at tid.es Fri Feb 3 08:57:33 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 03 Feb 2012 08:57:33 +0100 Subject: [Fiware-wpl] SOME OF YOU ARE DOING IT WRONG Message-ID: <4F2B936D.9090104@tid.es> 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 email: 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: -------------- 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: From torsten.leidig at sap.com Fri Feb 3 11:33:22 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Fri, 3 Feb 2012 11:33:22 +0100 Subject: [Fiware-wpl] [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki In-Reply-To: <4F2B8B94.10509@tid.es> References: <4F2A45FD.8080607@tid.es> <4F2B8B94.10509@tid.es> Message-ID: Hi Juanjo, I think the definitions given in the "Summary of key concepts" is a good foundation for our work and I recognized that you spent a lot of efforts to make them consistent and well-defined. For the public audience it probably has already sufficient level of precision. For internal purpose there are some questions remaining. FI-WARE Generic Enabler (GE) It is said that an implementation of a GE provides a concrete set of APIs and interoperable interfaces. But what does the GE provide? An abstract set of APIs and interfaces or no API/interfaces at all? FI-WARE GE Open Specification API stands for Application Programmers Interface, which is synonym to Language Binding to me. Since programmers use different languages the use different APIs according to the programming paradigm, I tend to say that a GE Open Specification does not specify APIs. I rather expect something like an abstract interaction protocol (abstract in the sense that no specific technical protocol and no specific data representation is implied). From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Freitag, 3. Februar 2012 08:24 To: Leidig, Torsten Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki Hi, I would never call someone stupid for asking questions :-) Besides, questions that come from a rigorous analysis of terms and definitions are always good questions because it's quite important that we align on terms and definitions. Strictly speaking, we should never use the term "Generic Enabler" or "GE" alone in many of our sentences. It doesn't mean anything tangible. What do really exist (i.e., refers to something "tangible") are things like: * "GE specifications" (or "GE Open Specifications") * "a GE implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". Then, whenever we say, as part of a given Architecture Description (which I believe we should not try to call "Specification") something like: "The IaaS Service Manager GE invokes the xxx operation exported by an IaaS Resource Manager GE to instruct them to provision the VApp" (A) we should indeed say: "The IaaS Service Manager GE implementation invokes the xxx operation exported by an IaaS Resource Manager GE implementation to instruct them to provision the VApp" (B) However, I believe that this would lead us to documents that would be rather "verbose". On the other hand, using (A) instead of (B) in standard specifications is rather common and many people would understand that you should make the distinction but you don't make it to for the sake of non-verbosity. I would go for putting a note somewhere at the beginning of the Architecture Description deliverable, where we may say something as: In order to avoid a too verbose text, we typically use the term " GE" or simply "" (e.g., "QueryBroker GE" or "QueryBroker") to refer to "an implementation of the GE Open Specifications" (e.g., "an implementation of the QueryBroker GE Open Specifications"). Note that the notion of GE is abstract and what actually refers to tangible things are: * "GE Open Specifications" which contain all information required in order to build components which can work as implementations of GEs. * "a GE Implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". You may refer to the set of terms and definitions provided at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision#Summary_of_key_concepts_introduced Would you agree ? (if you can produce a better text, I would be happy to take it) BTW, I honestly believe we provide an accurate definition of terms at the link referred about (part of the FI-WARE Product Vision. I tell you that I intend to make an serious effort to be rigorous and provide a set of consistent and well-defined terms, maybe we could add "GE implementation" but that was implicit in the existing ones and should be defined as a "Components in a given Platform Product that implement a given GE Open Specification". As for the template ... I'm not sure what do you mean what you say when you still ask for "a template". I would consider the proposed ToC for chapters as a "template" that chapter teams have to follow. If you mean that we should provide a "Wiki template", I'm not sure whether it would be a little bit cumbersome ... and at the end difficult to manage. I bought the benefit of using them for the Backlog Entry Descriptions but I'm not sure for each and every page on our Wiki ... May you provide an example of how that template may look like so that we can play with it a bit ? On the other hand, don't forget that there are many contributors who don't know the details about the MediaWiki language so that they indeed first write their contribution in Word and then "save as MediaWiki", then do some fine tuning ... We may need to explain what they should do there. As for the {{Parameter}} thing, I have to confess that I'm not that an expert on MediaWiki and probably you are right. However, we again have to take into account that many people will produce their initial input using Word, so therefore we should give them very precise instructions on how to edit the resulting MediaWiki text and add these {{Parameter}} thing. I sincerely take a look at what you did in your chapters and this is going to be wayyyy difficult to explain and cumbersome to implement. Best regards, -- Juanjo On 02/02/12 15:58, Leidig, Torsten wrote: Hi Juanjo, Now we have at least some guidelines. After looking at some of the existing OpenSpec pages from different chapters I found that no two pages look similar. So I still recommend to provide a template in order to ensure a common uniform style. Some comments to the instructions: You write the target audience are developers of applications or other GEs. Call me stupid but I still have the feeling that I don't get the meaning of GE concept right. My understanding is that a GE is describing a general functionality (such as a "network printing") for which a number of technical realizations can exist (several technical protocols for network printers). So a developer will not use the GE to build applications, he/she rather looks for implementations of the GE which match his/her requirements in terms of non-functional requirements such as cost, interoperability, performance, scalability, SLA, legal, .and so on. What we actually do in FI-WARE is defining the GE on a level that abstracts from concrete technical realizations. How do we describe GE? I think in terms of their interaction behavior, composition, dependencies, etc. which need to (or may) be provided by a GE implementation. Following this interpretation nobody develops GE, people rather should be able to implement components that conform to GE. The Open Specification must be written in a way to allow developers to implement a GE on its own. Also no one develops applications on top of GE, applications are developed on top of GE implementations exposing a GE conformant technical interfaces. There could be a catalog of GE implementations that can be used by application developers, which is organized around the GE model. For example as an application developer I look for a implementation of the "Network Printing" enabler, which satisfies my requirement in my situation. Via the catalog (or Marketplace) I can find it. So an Open Specification for a GE should only describe what it is used for and how one can interact with it, in a technology neutral way. It must not prescribe concrete technical interfaces. Nevertheless, FI-Ware can list or even recommend example technical interfaces in order to harmonize the platform architecture. In the example of the Apps Repository Enabler I tried to separate the generic part of the GE and the technical part of its implementation by keeping the GE specification neutral and linking to specific technical interfaces (of implementations) at the end of the article. If this doesn't make sense to you, please take another try to enlighten me. Regards, Torsten PS: According to the style suggestions you made (italic bold) I recommend to use MediaWiki templates again. I provided and used a couple of them in the Repository pages (e.g. {{Parameter}} ), we could provide more of them. The advantage would be that you can change the rendering and style later without having all people to change every page. -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Donnerstag, 2. Februar 2012 09:15 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki Hi all, I have published a set of guidelines to be followed for the development of the Architecture Description deliverable: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions This how-to will be enriched during the following days, including a complete example. However, I believe it contains already enough detailed instructions about how to proceed. Of course, your feedback is welcome. Answering your concrete questions may help to enrich the how-to material. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa . ________________________________ 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: From torsten.leidig at sap.com Fri Feb 3 11:49:27 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Fri, 3 Feb 2012 11:49:27 +0100 Subject: [Fiware-wpl] [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki In-Reply-To: <4F2B8B94.10509@tid.es> References: <4F2A45FD.8080607@tid.es> <4F2B8B94.10509@tid.es> Message-ID: Sorry my last mail was incomplete and sent unintendend. Hi Juanjo, I think the definitions given in the "Summary of key concepts" is a good foundation for our work and I recognized that you spent a lot of efforts to make them consistent and well-defined. For the public audience it probably has already sufficient level of precision. For internal purpose a few questions remain. FI-WARE Generic Enabler (GE) It is said that an implementation of a GE provides a concrete set of APIs and interoperable interfaces. But what does the GE provide? An abstract set of APIs and interfaces or no API/interfaces at all? API stands for Application Programmers Interface, which is synonym to Language Binding to me. Since programmers use different languages the use different APIs according to the programming paradigm, I tend to say that a GE Open Specification does not specify APIs. I rather expect something like an abstract interaction protocol (abstract in the sense that no specific technical protocol and no specific data representation is implied). FI-WARE GE Open Specification The definition is quite complete. The only question is about the signature and API. Signature sounds very concrete to me. Should an GE Open Specification really prescribe concrete APIs? For example, should the ID Management GE really prescribe a concrete API/interface like OpenID or OAuth? Which one to choose? What if the future provides us with new mechanisms for ID management and new protocols? Shouldn't the Open Specification just describe the basic functionality and allow the use of different technologies? Regards, Torsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Freitag, 3. Februar 2012 08:24 To: Leidig, Torsten Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki Hi, I would never call someone stupid for asking questions :-) Besides, questions that come from a rigorous analysis of terms and definitions are always good questions because it's quite important that we align on terms and definitions. Strictly speaking, we should never use the term "Generic Enabler" or "GE" alone in many of our sentences. It doesn't mean anything tangible. What do really exist (i.e., refers to something "tangible") are things like: * "GE specifications" (or "GE Open Specifications") * "a GE implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". Then, whenever we say, as part of a given Architecture Description (which I believe we should not try to call "Specification") something like: "The IaaS Service Manager GE invokes the xxx operation exported by an IaaS Resource Manager GE to instruct them to provision the VApp" (A) we should indeed say: "The IaaS Service Manager GE implementation invokes the xxx operation exported by an IaaS Resource Manager GE implementation to instruct them to provision the VApp" (B) However, I believe that this would lead us to documents that would be rather "verbose". On the other hand, using (A) instead of (B) in standard specifications is rather common and many people would understand that you should make the distinction but you don't make it to for the sake of non-verbosity. I would go for putting a note somewhere at the beginning of the Architecture Description deliverable, where we may say something as: In order to avoid a too verbose text, we typically use the term " GE" or simply "" (e.g., "QueryBroker GE" or "QueryBroker") to refer to "an implementation of the GE Open Specifications" (e.g., "an implementation of the QueryBroker GE Open Specifications"). Note that the notion of GE is abstract and what actually refers to tangible things are: * "GE Open Specifications" which contain all information required in order to build components which can work as implementations of GEs. * "a GE Implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". You may refer to the set of terms and definitions provided at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision#Summary_of_key_concepts_introduced Would you agree ? (if you can produce a better text, I would be happy to take it) BTW, I honestly believe we provide an accurate definition of terms at the link referred about (part of the FI-WARE Product Vision. I tell you that I intend to make an serious effort to be rigorous and provide a set of consistent and well-defined terms, maybe we could add "GE implementation" but that was implicit in the existing ones and should be defined as a "Components in a given Platform Product that implement a given GE Open Specification". As for the template ... I'm not sure what do you mean what you say when you still ask for "a template". I would consider the proposed ToC for chapters as a "template" that chapter teams have to follow. If you mean that we should provide a "Wiki template", I'm not sure whether it would be a little bit cumbersome ... and at the end difficult to manage. I bought the benefit of using them for the Backlog Entry Descriptions but I'm not sure for each and every page on our Wiki ... May you provide an example of how that template may look like so that we can play with it a bit ? On the other hand, don't forget that there are many contributors who don't know the details about the MediaWiki language so that they indeed first write their contribution in Word and then "save as MediaWiki", then do some fine tuning ... We may need to explain what they should do there. As for the {{Parameter}} thing, I have to confess that I'm not that an expert on MediaWiki and probably you are right. However, we again have to take into account that many people will produce their initial input using Word, so therefore we should give them very precise instructions on how to edit the resulting MediaWiki text and add these {{Parameter}} thing. I sincerely take a look at what you did in your chapters and this is going to be wayyyy difficult to explain and cumbersome to implement. Best regards, -- Juanjo On 02/02/12 15:58, Leidig, Torsten wrote: Hi Juanjo, Now we have at least some guidelines. After looking at some of the existing OpenSpec pages from different chapters I found that no two pages look similar. So I still recommend to provide a template in order to ensure a common uniform style. Some comments to the instructions: You write the target audience are developers of applications or other GEs. Call me stupid but I still have the feeling that I don't get the meaning of GE concept right. My understanding is that a GE is describing a general functionality (such as a "network printing") for which a number of technical realizations can exist (several technical protocols for network printers). So a developer will not use the GE to build applications, he/she rather looks for implementations of the GE which match his/her requirements in terms of non-functional requirements such as cost, interoperability, performance, scalability, SLA, legal, .and so on. What we actually do in FI-WARE is defining the GE on a level that abstracts from concrete technical realizations. How do we describe GE? I think in terms of their interaction behavior, composition, dependencies, etc. which need to (or may) be provided by a GE implementation. Following this interpretation nobody develops GE, people rather should be able to implement components that conform to GE. The Open Specification must be written in a way to allow developers to implement a GE on its own. Also no one develops applications on top of GE, applications are developed on top of GE implementations exposing a GE conformant technical interfaces. There could be a catalog of GE implementations that can be used by application developers, which is organized around the GE model. For example as an application developer I look for a implementation of the "Network Printing" enabler, which satisfies my requirement in my situation. Via the catalog (or Marketplace) I can find it. So an Open Specification for a GE should only describe what it is used for and how one can interact with it, in a technology neutral way. It must not prescribe concrete technical interfaces. Nevertheless, FI-Ware can list or even recommend example technical interfaces in order to harmonize the platform architecture. In the example of the Apps Repository Enabler I tried to separate the generic part of the GE and the technical part of its implementation by keeping the GE specification neutral and linking to specific technical interfaces (of implementations) at the end of the article. If this doesn't make sense to you, please take another try to enlighten me. Regards, Torsten PS: According to the style suggestions you made (italic bold) I recommend to use MediaWiki templates again. I provided and used a couple of them in the Repository pages (e.g. {{Parameter}} ), we could provide more of them. The advantage would be that you can change the rendering and style later without having all people to change every page. -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Donnerstag, 2. Februar 2012 09:15 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki Hi all, I have published a set of guidelines to be followed for the development of the Architecture Description deliverable: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions This how-to will be enriched during the following days, including a complete example. However, I believe it contains already enough detailed instructions about how to proceed. Of course, your feedback is welcome. Answering your concrete questions may help to enrich the how-to material. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa . ________________________________ 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: From pascal.bisson at thalesgroup.com Mon Feb 6 12:13:36 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 6 Feb 2012 12:13:36 +0100 Subject: [Fiware-wpl] Actions Points to be Done In-Reply-To: <4F27C0D6.4080301@tid.es> References: <4F27C0D6.4080301@tid.es> Message-ID: <20199_1328526813_4F2FB5DD_20199_507_1_35258a11-bf3f-4dc8-9548-02362416e90d@THSONEA01HUB01P.one.grp> Dear Colleagues, I'm just forwarding you this email from Juanjo to remind you the Action Points Daniel and I on behalf of Security team were requesting from each of you. Counting on you to work on those actions points and report to us asap. Reading you soon. Pascal / Daniel * Address APs identified during Security plenary session: * Each Chapter to provide their answers to the questions raised by the Security team for each of the Security GEs (the sooner, the better and no later than by end of this week so 3/02/2012) * Each Chapters to consider integration of Security GEs within their Chapter architecture and whenever those are needed and at appropriate level (i.e. architecture level, GE level). As a first step, this should lead to definition of at least one Epic by chapter and GEs to reflect this as ongoing work * Each Chapter to analyze the interaction (sequence) diagram with the Security Monitoring GE to check, amend/complete and validate them (there is one for each of the Chapters that was elaborated by the Security team). This is needed prior delivery of the information requested by the Security Chapter (i.e. log, security events, countermeasures, ....) by Security Monitoring GE (also gets the architecture of the chapter ready to have this information delivered). The Security chapter will provide other chapters with information needed by Security Monitoring GE (also format under which this information has to be provided) De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mardi 31 janvier 2012 11:22 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Actions Points to be Done Dear WPLs/WPAs, I plan to deliver more precise guidelines, including some templates sometime today but probably very late in the evening, effectively to be ready tomorrow morning because I'm currently very busy finalization of the publication of the first Open Call which was due by today. Apologize for any problem this may cause, but I hope you will understand. In the meantime, please try to deal with the couple of urgent points that we revised during last week WPL/WPA meeting (some of them commented during our joint confcall yesterday). We should not forget to address them: * Provide complete and accurate minutes of the f2f meeting last week. As announced, Miguel sent detailed instructions to follow regarding this (based on feedback by some partners, we will change the place where you should upload them, Miguel will send an email updating on this). PLEASE don't forget to transform Actions Points you identified into WorkItems in the corresponding tracker (your chapter tracker or the FI-WARE-Private tracker). Miguel will setup a Backlog Management tracker on the "FI-WARE Private" project so that you will be able to create WorkItems you believe that need to be addressed and followed-up at FI-WARE global level. * Complete response to questionnaire distributed by the Testbed team. This is urgent in order to complete the Testbed design. * SAP: complete revision of Epics linked to BM&BE GE being considered in the first Open Call. * Planning of sprint 4 (this requires the first point regarding identification of WorkItems to be done) * Address APs identified during Security plenary session: * Each Chapter to provide their answers to the questions raised by the Security team for each of the Security GEs (the sooner, the better and no later than by end of this week so 3/02/2012) * Each Chapters to consider integration of Security GEs within their Chapter architecture and whenever those are needed and at appropriate level (i.e. architecture level, GE level). As a first step, this should lead to definition of at least one Epic by chapter and GEs to reflect this as ongoing work * Each Chapter to analyze the interaction (sequence) diagram with the Security Monitoring GE to check, amend/complete and validate them (there is one for each of the Chapters that was elaborated by the Security team). This is needed prior delivery of the information requested by the Security Chapter (i.e. log, security events, countermeasures, ....) by Security Monitoring GE (also gets the architecture of the chapter ready to have this information delivered). The Security chapter will provide other chapters with information needed by Security Monitoring GE (also format under which this information has to be provided) * Review status of UC project tickets to update them or make some progress. Don't forget to change the assignee of a ticket to be the issuer whenever you change the state to "Needs revision by the issuer". * Standardization Plan: please check latest requests on the matter ... there is info pending ! Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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: From jhierro at tid.es Mon Feb 6 19:59:16 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 06 Feb 2012 19:59:16 +0100 Subject: [Fiware-wpl] Reviewers have requested access to FusionForge In-Reply-To: <942FD2F004D742BAA1C638BDEB2354B4@ManSzePC> References: <942FD2F004D742BAA1C638BDEB2354B4@ManSzePC> Message-ID: <4F302304.9050400@tid.es> Hi all, Prior giving access to FusionForge to our reviewer, Man-Sze Li, I want you to be aware. I will give her access from tomorrow morning 11:00am on, unless I hear about any objection. A good reason for you to take care about the status of your stuff :-) particularly the tracker. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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: RE: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog Date: Mon, 6 Feb 2012 11:52:16 +0100 From: Man-Sze Li To: JUAN JOSE HIERRO SUREDA Dear Dr Hierro I would wish to take up the offer to be able to access the FI-WARE backlogs live. Thank you in advance for arranging for a user account on FusionForge for me. Best regards Man-Sze Li -----Original Message----- From: Arian.ZWEGERS at ec.europa.eu [mailto:Arian.ZWEGERS at ec.europa.eu] Sent: 26 January 2012 10:35 To: msli at icfocus.co.uk; dgr at whitestein.com; rdifrancesco at ymail.com; bel.piet1 at gmail.com Subject: FW: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog fyi -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Thursday, January 26, 2012 11:11 AM To: ZWEGERS Arian (INFSO); INFSO-ICT-285248 Cc: Jose Jimenez; Miguel Carrillo; jhierro >> "Juan J. Hierro" Subject: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog Dear Arian, This is the official submission of deliverable D.2.1.a "FI-WARE Requirements Backlog" of the FI-WARE project. As you know, the FI-WARE Backlog is managed through several trackers (each FI-WARE chapter managing its own tracker), in combination with the public Wiki. Contents of the FI-WARE Backlog are constantly updated through the subsequent FI-WARE sprints, following an Agile approach. Therefore, versions of deliverable D.2.1 correspond to snapshots of these trackers. It took some time to find the way we could generate such a snapshot and adjust the format. On the other hand, the exercise allowed us to identify some missalignments regarding formatting conventions across FI-WARE chapters (e.g., notation for release or sprint ids, ids for entries, etc.) we have fixed. There should not be that much delay in subsequent submissions of the deliverable. Given the nature of the deliverable, we found that an spreadsheet format was the most useful and convenient format. Note that the deliverable corresponded to a snapshot we took early in December. Therefore, the backlog has evolved since then. If you or the reviewers wish to access the FI-WARE Backlogs "live" it would be as easy to create a user account for you on the different FI-WARE chapter projects in FusionForge. I remind you that this was something we already offered in September 2011. Best regards, Juanjo Hierro Chief Architect & Technical Manager FI-WARE project www.fi-ware.eu 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: From matteo.melideo at eng.it Tue Feb 7 11:06:14 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 07 Feb 2012 11:06:14 +0100 Subject: [Fiware-wpl] [Fiware-wpa] Reviewers have requested access to FusionForge In-Reply-To: <4F302304.9050400@tid.es> References: <942FD2F004D742BAA1C638BDEB2354B4@ManSzePC> <4F302304.9050400@tid.es> Message-ID: <4F30F796.5000802@eng.it> Dear Juanjo, for sure this is a very good idea and incentive to keep updated the tracker, backlogs etc. Anyway, there is a non trivial problem to solve. If you want to do some query in the tracker the risk is that you cannot use it any more due to the bug still not solved. My two cents, Matteo P.S. It is now a week I cannot access any more the tracker due to this error. Il 06/02/2012 19:59, Juanjo Hierro ha scritto: > Hi all, > > Prior giving access to FusionForge to our reviewer, Man-Sze Li, I > want you to be aware. I will give her access from tomorrow morning > 11:00am on, unless I hear about any objection. > > A good reason for you to take care about the status of your stuff > :-) particularly the tracker. > > Cheers, > > -- Juanjo > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email: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: RE: Submission of deliverable D.2.1.a FI-WARE Requirements > Backlog > Date: Mon, 6 Feb 2012 11:52:16 +0100 > From: Man-Sze Li > To: JUAN JOSE HIERRO SUREDA > > > > Dear Dr Hierro > > I would wish to take up the offer to be able to access the FI-WARE backlogs > live. Thank you in advance for arranging for a user account on FusionForge > for me. > > Best regards > > Man-Sze Li > > -----Original Message----- > From:Arian.ZWEGERS at ec.europa.eu [mailto:Arian.ZWEGERS at ec.europa.eu] > Sent: 26 January 2012 10:35 > To:msli at icfocus.co.uk;dgr at whitestein.com;rdifrancesco at ymail.com; > bel.piet1 at gmail.com > Subject: FW: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog > > fyi > > -----Original Message----- > From: Juanjo Hierro [mailto:jhierro at tid.es] > Sent: Thursday, January 26, 2012 11:11 AM > To: ZWEGERS Arian (INFSO); INFSO-ICT-285248 > Cc: Jose Jimenez; Miguel Carrillo; jhierro>> "Juan J. Hierro" > Subject: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog > > Dear Arian, > > This is the official submission of deliverable D.2.1.a "FI-WARE > Requirements Backlog" of the FI-WARE project. > > As you know, the FI-WARE Backlog is managed through several trackers > (each FI-WARE chapter managing its own tracker), in combination with the > public Wiki. Contents of the FI-WARE Backlog are constantly updated > through the subsequent FI-WARE sprints, following an Agile approach. > Therefore, versions of deliverable D.2.1 correspond to snapshots of > these trackers. > > It took some time to find the way we could generate such a snapshot > and adjust the format. On the other hand, the exercise allowed us to > identify some missalignments regarding formatting conventions across > FI-WARE chapters (e.g., notation for release or sprint ids, ids for > entries, etc.) we have fixed. There should not be that much delay in > subsequent submissions of the deliverable. Given the nature of the > deliverable, we found that an spreadsheet format was the most useful and > convenient format. > > Note that the deliverable corresponded to a snapshot we took early in > December. Therefore, the backlog has evolved since then. > > If you or the reviewers wish to access the FI-WARE Backlogs "live" it > would be as easy to create a user account for you on the different > FI-WARE chapter projects in FusionForge. I remind you that this was > something we already offered in September 2011. > > > Best regards, > > Juanjo Hierro > Chief Architect& Technical Manager > FI-WARE project > www.fi-ware.eu > > > 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 > > > _______________________________________________ > Fiware-wpa mailing list > Fiware-wpa at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpa -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Miguel Carrillo Subject: [Fiware] Bug on the tracker Date: Mon, 06 Feb 2012 10:09:55 +0100 Size: 12704 URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Tue Feb 7 15:02:06 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 07 Feb 2012 15:02:06 +0100 Subject: [Fiware-wpl] WP9 Bilateral meeting minutes uploaded Message-ID: <4F312EDE.9040203@eng.it> Dear All, as requested by the project coordinator I have uploaded in the indicated folder the minutes of the bilateral meetings WP9 had with the other Workpackages. Unfortunately I received very few feedbacks from you both on the contents and the list of participants of your WPs. We tried to do our best to remember but in most cases it was almost impossible. Regards, Matteo Melideo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From mcp at tid.es Wed Feb 8 23:58:17 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 08 Feb 2012 23:58:17 +0100 Subject: [Fiware-wpl] Tutorial: Creation of deliverables with wiki pages Message-ID: <4F32FE09.6070307@tid.es> Dear WPLs/WPAs, Please note that there is a new tutorial to teach everyone to create pdf documents with the wiki. All public deliverables should use this method as all public deliverables will be worked and deposited on the wiki. * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_pdf_deliverables_from_wiki_pages Important: as leaders of your WPs, you have to make sure that all the editors of the documents are aware of this. Do not forget this, if not they get lost. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net 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: From jhierro at tid.es Fri Feb 10 07:55:11 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Feb 2012 07:55:11 +0100 Subject: [Fiware-wpl] URGENT AND IMPORTANT: Work in trackers Message-ID: <4F34BF4F.8020200@tid.es> Hi all, Please DON'T make any changes on your trackers until further notice (later today). This measure doesn't affect you work on the Wikis or other artifacts. You can still work there. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 From jhierro at tid.es Fri Feb 10 08:01:59 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Feb 2012 08:01:59 +0100 Subject: [Fiware-wpl] Further instructions regarding Architecture Description Deliverable Message-ID: <4F34C0E7.1080106@tid.es> Hi, I have updated the guidelines for developing the Architecture Description deliverable on the wiki. I have essentially added a target extension per section as well as hints about how to deal with the different releases https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Of course, don't hesitate to make comments or ask for any doubt. They may help to enrich the guidelines. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 From jhierro at tid.es Fri Feb 10 08:51:55 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Feb 2012 08:51:55 +0100 Subject: [Fiware-wpl] Portal GE? In-Reply-To: References: Message-ID: <4F34CC9B.5010705@tid.es> Hi Alex, Answers below. I copy the rest of WPLs and WPAs because I believe that answers are relevant to others. On 10/02/12 08:23, Alex Glikson wrote: Dear Juanjo, During our last weekly call this week, a question was raised whether the Portal that we are developing for Cloud is really a Generic Enabler, in the FI-WARE sense.. In particular, do we need an open specification for it? My initial opinion is that it is not. For example, I'm not sure whether we really need to have a specification now that outlines the interactions between the user and the portal -- we don't want to limit ourselves to a specifc WebUI design. More importantly, such a specification would be of low interest for application developer. Would appreciate your view on this, as this affects the upcoming M9 deliverable. a) We don't need an open specification for a portal, you are right b) We don't need an Architecture Description for the portal either, although I presume there will be description of Main interactions in some of the Generic Enablers where it is useful to describe how interaction with a portal would take place c) The portal should be part of the software release delivered and should be accompanied by the corresponding guides Hope it helps, -- Juanjo Thanks, Alex ________________________________ 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: From mcp at tid.es Fri Feb 10 09:52:02 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 10 Feb 2012 09:52:02 +0100 Subject: [Fiware-wpl] [Fiware-wpa] URGENT AND IMPORTANT: Work in trackers In-Reply-To: <4F34BF4F.8020200@tid.es> References: <4F34BF4F.8020200@tid.es> Message-ID: <8E434428-F178-46E9-B3A1-0C6F7E9DE31A@tid.es> Dear all, On second thoughts, we would recommend to stop all work on the forge until further notice. There is a demand from a chapter to restore a whole tracker. We are evaluating what the options are and in the worst case scenario we would need to restore a full backup and the changes would be lost. So please work offline for a few hours. This is under discussion at this very moment, we will keep you posted. Best regards Miguel El 10/02/2012, a las 07:55, Juanjo Hierro escribi?: > Hi all, > > Please DON'T make any changes on your trackers until further notice > (later today). > > This measure doesn't affect you work on the Wikis or other > artifacts. You can still work there. > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: 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 > _______________________________________________ > Fiware-wpa mailing list > Fiware-wpa at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpa 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 From mcp at tid.es Fri Feb 10 11:18:29 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 10 Feb 2012 11:18:29 +0100 Subject: [Fiware-wpl] [Fiware] [Fiware-wpa] URGENT AND IMPORTANT: Work in trackers In-Reply-To: <8E434428-F178-46E9-B3A1-0C6F7E9DE31A@tid.es> References: <4F34BF4F.8020200@tid.es> <8E434428-F178-46E9-B3A1-0C6F7E9DE31A@tid.es> Message-ID: <4F34EEF5.9090409@tid.es> Dear all, We have finished the meeting with our system administrator. Conclusions: * You can continue working on the wiki and SVN normally. Exclusively on these two. * This means not working with trackers and document management, all changes here would be lost! We will try to restore the tracker that got lost. First we will test the process internally, in a different environment. Then we will proceed to restore the database .Before we start the restore, we will disable web access to the forge temporarily until it's up and running again. This may happen today in the afternoon or even tomorrow. I will keep you informed. BR Miguel El 10/02/2012 9:52, Miguel Carrillo escribi?: Dear all, On second thoughts, we would recommend to stop all work on the forge until further notice. There is a demand from a chapter to restore a whole tracker. We are evaluating what the options are and in the worst case scenario we would need to restore a full backup and the changes would be lost. So please work offline for a few hours. This is under discussion at this very moment, we will keep you posted. Best regards Miguel El 10/02/2012, a las 07:55, Juanjo Hierro escribi?: Hi all, Please DON'T make any changes on your trackers until further notice (later today). This measure doesn't affect you work on the Wikis or other artifacts. You can still work there. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa 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 _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net 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: From mcp at tid.es Fri Feb 10 12:15:03 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 10 Feb 2012 12:15:03 +0100 Subject: [Fiware-wpl] Forge down from 15:00 onwards Message-ID: <4F34FC37.50804@tid.es> Dear all, In order to clone the VMs where the forge is hosted, we need to previously shut down the forge . This will take place today from 15:00 onwards. This is necessary to perform tests before restoring the information that got lost. Thanks for your understanding Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net 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 From jhierro at tid.es Mon Feb 13 09:55:28 2012 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Mon, 13 Feb 2012 09:55:28 +0100 Subject: [Fiware-wpl] Joint FI-WARE WPLs/WPAs follow-up confcall Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A67@EXCLU2K7.hi.inet> When: Occurs on Monday every other week from 11:00 AM to 12:30 PM effective 10/10/2011. (GMT+01:00) Sarajevo, Skopje, Warsaw, Zagreb *~*~*~*~*~*~*~*~*~* We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 7343 bytes Desc: not available URL: From jhierro at tid.es Mon Feb 13 10:48:29 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 Feb 2012 10:48:29 +0100 Subject: [Fiware-wpl] Webex details and shared minutes In-Reply-To: <30DB7E5C-E2EC-4892-B75F-F95C945CB37E@tid.es> References: <30DB7E5C-E2EC-4892-B75F-F95C945CB37E@tid.es> Message-ID: <4F38DC6D.4060707@tid.es> Hi all, Please find below the details of the Webex we may use. In addition, we will share the minutes at: https://docs.google.com/document/d/16e8vgHfdkIkNCY33fPvEGMvJqCQkTcR5A2wkoX0LQFs/edit (start registering you as attendee there) We'll use powwownow for the confcall. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf Talk to you in a few minutes. Best, -- Juanjo Inicio del mensaje reenviado: De: Gestor i-Reunion webex9100 > Fecha: 13 de febrero de 2012 10:34:28 GMT+01:00 Para: CARLOS RALLI UCENDO > Asunto: Meeting invitation: Fi-ware WPl/WPa call conf Responder a: "Webex9100 at tid.es" > Hello , Gestor i-Reunion webex9100 invites you to attend this online meeting. Topic: Fi-ware WPl/WPa call conf Date: Monday, February 13, 2012 Time: 11:00 am, Europe Time (Paris, GMT+01:00) Meeting Number: 676 419 892 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=14542083&UID=109908163&PW=NYTUwYjVkNzgw&RT=MiMyMw%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: 1234abcD 4. Click "Join Now". To view in other time zones or languages, please click the link: https://telefonica.webex.com/telefonica-en/j.php?ED=14542083&UID=109908163&PW=NYTUwYjVkNzgw&ORT=MiMyMw%3D%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex9100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=14542083&UID=109908163&ICS=MI&LD=1&RD=2&ST=1&SHA2=dQ03NzsPJgpH06K-2aYMtrp7ew/pFLC3srdWRaXdyT8=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ 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: From jhierro at tid.es Wed Feb 15 10:52:21 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 15 Feb 2012 10:52:21 +0100 Subject: [Fiware-wpl] IMPORTANT: Reference example on Main Interactions section to be followed Message-ID: <4F3B8055.1050703@tid.es> Hi, While reviewing the different drafts of the "Architecture Description" chapters, I have found that many of the descriptions of "Main Interactions" is quite poor. We have developed a good reference example for this kind of sections. You can find it at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 If you have followed the reference example provided initially based on the CORBA specifications as well as the guidelines already provided, you should not have anything too far from this, but unfortunately, I'm discovering that this is not the case in many of the GE Architecture Descriptions. The guidelines for editing the "Architecture Description" deliverable have been updated accordingly. I encourage you to review them carefully and add any question on teh FAQ section you may have. You may find them at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 From jhierro at tid.es Thu Feb 16 07:17:51 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Feb 2012 07:17:51 +0100 Subject: [Fiware-wpl] IMPORTANT REMARK: Consistency between contents of the FI-WARE Architecture Description and Product Vision Message-ID: <4F3C9F8F.9050901@tid.es> Hi all, I don't know if you have planned this, but one thing we should avoid is existence of inconsistencies between what we will say in the FI-WARE Architecture Description and what is currently being said in the FI-WARE Product Vision (which, I remind you, is already publicly available through the public Wiki). We shouldn't go public in any of the chapters without having this fixed. You should plan the necessary work for achieving the necessary alignment, updating the necessary FI-WARE Product Vision sections. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 From mcp at tid.es Thu Feb 16 18:03:04 2012 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 16 Feb 2012 18:03:04 +0100 Subject: [Fiware-wpl] Privacy of Documents on the Forge Message-ID: <4F3D36C8.7020606@tid.es> Dear all, As you all know (see tutorial "How to share documents with the FusionForge docman system" ) the docs are uploaded and then have to be marked as private if that's what you wish. If not , they will be public on the internet. I logged out of the forge and checked what an anonymous user would see on the internet and I saw a number of things that I do not know to what extent are intentional. You can verify by yourselves by logging out of the forge and going to the docman of your chapter. I enclose a capture for each one of the chapters for your convenience. If anything has to be changed, try yourselves. Failing this, go to your WPL/WPA, they should be able to change the settings of a given document to private. Conversely, if something should be public and is maked as private now, he can change it as well. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE_Public_doc_visibility.pdf Type: application/pdf Size: 86525 bytes Desc: not available URL: From jhierro at tid.es Fri Feb 17 14:23:16 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 17 Feb 2012 14:23:16 +0100 Subject: [Fiware-wpl] Deliverable on Architecture Description Message-ID: <4F3E54C4.505@tid.es> Hi all, I will be reviewing during the weekend the final draft that all chapter teams are expected to upload on the FI-WARE Private Wiki by EOB today. I will send a reasoned report by Monday morning about the results of that review. I assume there will be essentially three scenarios to report for a given chapter: 1. Contents of the chapter are mature enough and can be made public available, therefore transferred to the public Wiki. 2. Contents of the chapter are not mature enough but, implementing a number of quick changes, they can be transferred to the public Wiki by mid of next week 3. Contents of the chapter are immature and will require more work In cases 1, 2 I will also send a proposal on how to plan peer reviews that will have to be carried out once the contents are available on the public Wiki. In case 3, we will need to plan a dedicated confcall to plan the necessary APs to recover. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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: From mcp at tid.es Wed Feb 22 15:29:44 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 22 Feb 2012 15:29:44 +0100 Subject: [Fiware-wpl] Confidenciality in Contents in FI-WARE Document Manager Message-ID: <4F44FBD8.8030603@tid.es> Dear all, The other day I referred to the docs that were public on the internet. But there is more to it. Just to make sure that everyone is aware of this. * Docs in the "FI-WARE" project marked as "public" - visible to everyone * Docs in the "FI-WARE" project marked as "private" - visible to all people with access to the "FI-WARE" project (this includes Use Case projects) * Docs in the "FI-WARE private" project - just accessible to FI-WARE project members (this does not include Use Cases) We want to give the Use Cases information, but part of it should remain strictly private. When this happens, thery should go to the private project. I would invite the WPLs/WPAs to take a look and, if it is the case, transfer the docs that they want to keep strictly private to the private project. For instance, I just made a big zip file with our minutes of meeting in Madrid and moved it to the Doc. Manager of the "FI-WARE private" project. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net 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: From jhierro at tid.es Mon Feb 27 08:47:28 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Feb 2012 08:47:28 +0100 Subject: [Fiware-wpl] WPLs/WPAs follow-up confcall Message-ID: <4F4B3510.7010705@tid.es> Hi, This is a reminder of the joint WPLs/WPAs follow-up confcall we had scheduled starting at 11:00am We will use powwownow as always: We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf We will also pass you webex bridge details prior to the call. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 From jhierro at tid.es Mon Feb 27 10:43:31 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Feb 2012 10:43:31 +0100 Subject: [Fiware-wpl] Webex and shared minutes in google docs In-Reply-To: <270829481.1330333975265.JavaMail.nobody@jsj2wl016.webex.com> References: <270829481.1330333975265.JavaMail.nobody@jsj2wl016.webex.com> Message-ID: <4F4B5043.1070809@tid.es> Hi, The Webex bridge can be found at: https://telefonica.webex.com/telefonica/j.php?ED=191128867&UID=1272924167&PW=NYWNjYTYyZDk1&RT=MTQjMjM%3D If password is required, it is 1234abcD We will share the minutes during the confcall as we did the last time. The URL for the shared minutes is: https://docs.google.com/document/d/1gkEUTMfUizrYxt9y24jOWdT3fvFpv5nKQJch1_3sVAc/edit Cheers, -- Juanjo -------- Original Message -------- Subject: Invitaci?n a reuni?n: FI-WARE Joint WPLs/WPAs follow-up confcall Date: Mon, 27 Feb 2012 10:12:55 +0100 From: Gestor i-Reunion webex7000 Reply-To: Webex7000 at tid.es To: JUAN JOSE HIERRO SUREDA Hola , Gestor i-Reunion webex7000 lo invita a asistir a esta reuni?n en l?nea. Tema: FI-WARE Joint WPLs/WPAs follow-up confcall Fecha: lunes, 27 de febrero de 2012 Hora: 11:00, Europa Hora (Par?s, GMT+01:00) N?mero de la reuni?n: 964 407 309 Contrase?a de la reuni?n: 1234abcD ------------------------------------------------------- Para unirse a la reuni?n en l?nea (?Ahora tambi?n desde iPhones!) ------------------------------------------------------- 1. Vaya a https://telefonica.webex.com/telefonica/j.php?ED=191128867&UID=1272924167&PW=NYWNjYTYyZDk1&RT=MTQjMjM%3D 2. Introduzca su nombre y direcci?n de correo electr?nico. 3. Introduzca la contrase?a de la reuni?n: 1234abcD 4. Haga clic en "Entrar ahora". Para ver en otras zonas horarias o idiomas, haga clic en el enlace: https://telefonica.webex.com/telefonica/j.php?ED=191128867&UID=1272924167&PW=NYWNjYTYyZDk1&ORT=MTQjMjM%3D ------------------------------------------------------- Para obtener ayuda ------------------------------------------------------- 1. Vaya a https://telefonica.webex.com/telefonica/mc 2. En la barra de navegaci?n izquierda, haga clic en "Soporte". Puede ponerse en contacto conmigo en: Webex7000 at tid.es Para a?adir esta reuni?n al programa del calendario (por ejemplo Microsoft Outlook), haga clic en este enlace: https://telefonica.webex.com/telefonica/j.php?ED=191128867&UID=1272924167&ICS=MI&LD=12&RD=14&ST=1&SHA2=RKvdh4UUEmcynXedXePcLCBeH4YxexjTbu7LE9Akeo0=&RT=MTQjMjM%3D La reproducci?n de archivos multimedia enriquecidos con formato universal de comunicaciones (UCF) necesita reproductores adecuados. Para ver este tipo de archivos multimedia enriquecidos en esta reuni?n, compruebe si tiene los reproductores instalados en la computadora. Vaya a https://telefonica.webex.com/telefonica/systemdiagnosis.php Inscr?base para disfrutar de la prueba gratuita de WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com AVISO IMPORTANTE: Este servicio de WebEx incluye una funci?n que permite ver e intercambiar audio, documentos y otros materiales durante la sesi?n que va a grabarse. Al unirse a esta sesi?n, autom?ticamente da permiso para realizar dichas grabaciones. Si no est? de acuerdo con la grabaci?n, no se una a la sesi?n. ________________________________ 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: From torsten.leidig at sap.com Mon Feb 27 17:46:53 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Mon, 27 Feb 2012 17:46:53 +0100 Subject: [Fiware-wpl] FIWARE: FMC Block diagrams: Reference_Sheet-Block_Diagram.pdf (application/pdf Object) Message-ID: http://www.fmc-modeling.org/download/notation_reference/Reference_Sheet-Block_Diagram.pdf Dear Open Specification Writers, while having a quick look at different Open Specifications in the private Wiki I noticed that there is some confusion according to the meaning FMC block diagrams. Please have a look at this cheat sheet. The semantics is actually very simple. However, it would be nice if we can use it consistently across the different Specs. So for example: * The dotted rounded rectangle means: structure variance (parts of the diagram can be there multiple times, sometimes controlled by an agent.) * If you want to subsume parts of the diagram you should us a plain border box (maybe with a light grey background) * The R with a small arrow means an RPC-like semantics of a channel between two components (agents) * Two components can only be connected via a channel. (no direct lines between them) * A component (agent) can read/write from/to a storage (without a channel in between) Best regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Feb 27 19:11:50 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Feb 2012 19:11:50 +0100 Subject: [Fiware-wpl] [Fiware-wpa] FIWARE: FMC Block diagrams: Reference_Sheet-Block_Diagram.pdf (application/pdf Object) In-Reply-To: References: Message-ID: <4F4BC766.4080803@tid.es> Hi, Thanks Torsten for pointing this out ... Please bear in mind Torsten's comments. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 27/02/12 17:46, Leidig, Torsten wrote: http://www.fmc-modeling.org/download/notation_reference/Reference_Sheet-Block_Diagram.pdf Dear Open Specification Writers, while having a quick look at different Open Specifications in the private Wiki I noticed that there is some confusion according to the meaning FMC block diagrams. Please have a look at this cheat sheet. The semantics is actually very simple. However, it would be nice if we can use it consistently across the different Specs. So for example: * The dotted rounded rectangle means: structure variance (parts of the diagram can be there multiple times, sometimes controlled by an agent.) * If you want to subsume parts of the diagram you should us a plain border box (maybe with a light grey background) * The R with a small arrow means an RPC-like semantics of a channel between two components (agents) * Two components can only be connected via a channel. (no direct lines between them) * A component (agent) can read/write from/to a storage (without a channel in between) Best regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ 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: From jhierro at tid.es Tue Feb 28 07:43:01 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 Feb 2012 07:43:01 +0100 Subject: [Fiware-wpl] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki Message-ID: <4F4C7775.2040703@tid.es> 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 email: 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: From jhierro at tid.es Tue Feb 28 08:52:36 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 Feb 2012 08:52:36 +0100 Subject: [Fiware-wpl] [Fiware-wpa] FIWARE: FMC Block diagrams: Reference_Sheet-Block_Diagram.pdf (application/pdf Object) In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD059AF9B0@DEMUEXC013.nsn-intra.net> References: A <3F4C11BC54A36642BFB5875D599F47BD059AF9B0@DEMUEXC013.nsn-intra.net> Message-ID: <4F4C87C4.8030804@tid.es> Hi, IMHO, what they are referring there as "RPC" or "RPC-like" is something open enough so that we can assign it the semantics that better suit to our convenience. From my point of view, a RESTful interface could be categorized as having RPC-like semantics. As pointed by Denes, meaning that "Agent A1 can request information from agent A2 which in turn responds (e.g. function calls or http request/responses)" and this is something that you can argue is what actually happens in a RESTful interface. Therefore, I agree with Denes here: the R with small arrow simply indicates the direction of the request, in a request-response communication. Given said the above, all chapter teams should review their FMC block diagrams to make sure they align with the FMC principles summarized in the sheet distributed by Torsten. At least full alignment should be achieved by March 6 in the public wiki. Hope it helps, -- Juanjo On 28/02/12 07:56, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Thorsten, I agree with most of your points, lots of people doing it wrong. However, as far as I understood from the link you just provided the R with small arrow simply indicates the direction of the request-response communication, no RPC is mentioned anywhere. Quoting the pdf ?Agent A1 can request information from agent A2 which in turn responds (e.g. function calls or http request/responses)?. Best, D?nes From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Leidig, Torsten Sent: Monday, February 27, 2012 5:47 PM To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE: FMC Block diagrams: Reference_Sheet-Block_Diagram.pdf (application/pdf Object) http://www.fmc-modeling.org/download/notation_reference/Reference_Sheet-Block_Diagram.pdf Dear Open Specification Writers, while having a quick look at different Open Specifications in the private Wiki I noticed that there is some confusion according to the meaning FMC block diagrams. Please have a look at this cheat sheet. The semantics is actually very simple. However, it would be nice if we can use it consistently across the different Specs. So for example: * The dotted rounded rectangle means: structure variance (parts of the diagram can be there multiple times, sometimes controlled by an agent.) * If you want to subsume parts of the diagram you should us a plain border box (maybe with a light grey background) * The R with a small arrow means an RPC-like semantics of a channel between two components (agents) * Two components can only be connected via a channel. (no direct lines between them) * A component (agent) can read/write from/to a storage (without a channel in between) Best regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ 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: From denes.bisztray at nsn.com Tue Feb 28 07:56:22 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 28 Feb 2012 07:56:22 +0100 Subject: [Fiware-wpl] [Fiware-wpa] FIWARE: FMC Block diagrams: Reference_Sheet-Block_Diagram.pdf (application/pdf Object) In-Reply-To: A References: A Message-ID: <3F4C11BC54A36642BFB5875D599F47BD059AF9B0@DEMUEXC013.nsn-intra.net> Dear Thorsten, I agree with most of your points, lots of people doing it wrong. However, as far as I understood from the link you just provided the R with small arrow simply indicates the direction of the request-response communication, no RPC is mentioned anywhere. Quoting the pdf "Agent A1 can request information from agent A2 which in turn responds (e.g. function calls or http request/responses)". Best, D?nes From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Leidig, Torsten Sent: Monday, February 27, 2012 5:47 PM To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE: FMC Block diagrams: Reference_Sheet-Block_Diagram.pdf (application/pdf Object) http://www.fmc-modeling.org/download/notation_reference/Reference_Sheet-Block_Diagram.pdf Dear Open Specification Writers, while having a quick look at different Open Specifications in the private Wiki I noticed that there is some confusion according to the meaning FMC block diagrams. Please have a look at this cheat sheet. The semantics is actually very simple. However, it would be nice if we can use it consistently across the different Specs. So for example: * The dotted rounded rectangle means: structure variance (parts of the diagram can be there multiple times, sometimes controlled by an agent.) * If you want to subsume parts of the diagram you should us a plain border box (maybe with a light grey background) * The R with a small arrow means an RPC-like semantics of a channel between two components (agents) * Two components can only be connected via a channel. (no direct lines between them) * A component (agent) can read/write from/to a storage (without a channel in between) Best regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Feb 28 11:30:52 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 28 Feb 2012 11:30:52 +0100 Subject: [Fiware-wpl] [Fiware-wpa] FIWARE: FMC Block diagrams: Reference_Sheet-Block_Diagram.pdf (application/pdf Object) In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD059AF9B0@DEMUEXC013.nsn-intra.net> References: A <3F4C11BC54A36642BFB5875D599F47BD059AF9B0@DEMUEXC013.nsn-intra.net> Message-ID: Hi D?nes, You're right, I was a bit lazy. R actually means directed request-response communication. For me it was somehow synonym with RPC, but this is not completely correct. However, it is important to understand that this R channel is covering SOAP/WSDL as well as RESTful interfaces (and many other non-web interfaces). Regards, Torsten From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Dienstag, 28. Februar 2012 07:56 To: Leidig, Torsten; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: RE: [Fiware-wpa] FIWARE: FMC Block diagrams: Reference_Sheet-Block_Diagram.pdf (application/pdf Object) Dear Thorsten, I agree with most of your points, lots of people doing it wrong. However, as far as I understood from the link you just provided the R with small arrow simply indicates the direction of the request-response communication, no RPC is mentioned anywhere. Quoting the pdf "Agent A1 can request information from agent A2 which in turn responds (e.g. function calls or http request/responses)". Best, D?nes From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Leidig, Torsten Sent: Monday, February 27, 2012 5:47 PM To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE: FMC Block diagrams: Reference_Sheet-Block_Diagram.pdf (application/pdf Object) http://www.fmc-modeling.org/download/notation_reference/Reference_Sheet-Block_Diagram.pdf Dear Open Specification Writers, while having a quick look at different Open Specifications in the private Wiki I noticed that there is some confusion according to the meaning FMC block diagrams. Please have a look at this cheat sheet. The semantics is actually very simple. However, it would be nice if we can use it consistently across the different Specs. So for example: * The dotted rounded rectangle means: structure variance (parts of the diagram can be there multiple times, sometimes controlled by an agent.) * If you want to subsume parts of the diagram you should us a plain border box (maybe with a light grey background) * The R with a small arrow means an RPC-like semantics of a channel between two components (agents) * Two components can only be connected via a channel. (no direct lines between them) * A component (agent) can read/write from/to a storage (without a channel in between) Best regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Feb 28 11:49:56 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 28 Feb 2012 11:49:56 +0100 Subject: [Fiware-wpl] [Fiware-wpa] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki In-Reply-To: <4F4C7775.2040703@tid.es> References: <4F4C7775.2040703@tid.es> Message-ID: 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, I see the following problems: ? If the Open Specs are now the Architecture, what do we deliver in M12 for the Open Specifications? ? The current content for the Open Specs in the Wiki are actually high-level (abstract) specifications for the GE. ? 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. ? Shouldn't we focus on implementation of the first release now? 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) What's really missing is the overall architecture across the chapters as part of D.2.3! Regards, Torsten From: 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; 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 email: 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: From jhierro at tid.es Tue Feb 28 15:22:15 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 Feb 2012 15:22:15 +0100 Subject: [Fiware-wpl] [Fiware-wpa] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki In-Reply-To: References: <4F4C7775.2040703@tid.es> Message-ID: <4F4CE317.1040606@tid.es> 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] On Behalf Of Juanjo Hierro Sent: Dienstag, 28. Februar 2012 07:43 To: fiware-wpl at lists.fi-ware.eu; 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 email: 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: From jhierro at tid.es Tue Feb 28 17:08:12 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 Feb 2012 17:08:12 +0100 Subject: [Fiware-wpl] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki In-Reply-To: <4F4C7775.2040703@tid.es> References: <4F4C7775.2040703@tid.es> Message-ID: <4F4CFBEC.30104@tid.es> Hi all, I provided the instructions at 07:43 so that you can start with the task of migrating contents from the private to the public wiki and so far (ten hours after) I haven't seen anything on the public Wiki. The only chapter who was asked not to do this until I provided further comments (already sent a couple of minutes ago) was the IoT chapter. What about the others ? I believe that is important to show some results to Arian tomorrow morning ... Carrying out the transference is just a matter of few minutes (probably less than half an hour per chapter) ... Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 28/02/12 07:43, Juanjo Hierro wrote: 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 email: 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: From GLIKSON at il.ibm.com Tue Feb 28 21:48:48 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 28 Feb 2012 22:48:48 +0200 Subject: [Fiware-wpl] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki In-Reply-To: <4F4CFBEC.30104@tid.es> References: <4F4C7775.2040703@tid.es> <4F4CFBEC.30104@tid.es> Message-ID: Juanjo, all, I would recommend to plan our work in such a way that everyone have at least two work-days to respond to an email, and at least three work-days 'lead time' to perform any non-trivial action/task (or one week for tasks involving communication between partners). Regards, Alex P.S. the exact 'lead time' periods are negotiable, but it certainly can't be a matter of hours -- especially when it comes to important deliverables P.P.S in fact, since one also needs to download & upload again all the diagrams, it takes much more than half an hour From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 28/02/2012 06:08 PM Subject: Re: [Fiware-wpl] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki Sent by: fiware-wpl-bounces at lists.fi-ware.eu Hi all, I provided the instructions at 07:43 so that you can start with the task of migrating contents from the private to the public wiki and so far (ten hours after) I haven't seen anything on the public Wiki. The only chapter who was asked not to do this until I provided further comments (already sent a couple of minutes ago) was the IoT chapter. What about the others ? I believe that is important to show some results to Arian tomorrow morning ... Carrying out the transference is just a matter of few minutes (probably less than half an hour per chapter) ... Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 28/02/12 07:43, Juanjo Hierro wrote: 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 email: 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 _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Tue Feb 28 22:16:23 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 28 Feb 2012 23:16:23 +0200 Subject: [Fiware-wpl] code deliverables Message-ID: Dear all, I've been asked by one of my colleagues whether partners are supposed to provide source code of deliverables. To avoid confusion and legal issues in the future, it is important to clarify that per the Consortium agreement, partners are *NOT* obliged to provide any proprietary source code. I am not a lawyer, but my understanding is that exceptions are possible (when there is a clear need) -- but might require some legal formalities. Juanjo/Jose -- please, confirm/clarify. Thanks, Alex P.S. Consortium agreement can be found at https://forge.fi-ware.eu/docman/view.php/7/688/IPCA_FI-WARE_final_12th_sept_2011.pdf -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Feb 29 07:09:59 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 29 Feb 2012 07:09:59 +0100 Subject: [Fiware-wpl] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki In-Reply-To: References: <4F4C7775.2040703@tid.es> <4F4CFBEC.30104@tid.es> Message-ID: <4F4DC137.5080602@tid.es> Hi Alex, You are right about trying to follow that recommendation whenever we are not in a hurry. But, unfortunately, that is the case here :-) Nevertheless, thanks for your feedback. I'll take note of that for future situations where we may be a bit more relaxed. It may be true that the task doesn't take half an hour because you need to deal with uploading figures ... unless you organize the task so that each GE owner in your chapter team takes care of the part linked to its GE. But even if some WPL prefers to takes care of it in a centralized way, it wasn't a task of 10 hours. That was worried me: 10 hours had passed since I forwarded the instructions to follow and I hadn't seen any progress. I hope that you understand that I was a little bit worried and that it was normal that I sent an email asking what was going on :-) Fortunately, all of you have reacted quickly to my email and now we have all the expected contents on the publi Wiki. Thanks very much for your effort. I have already forwarded my comments to the IoT chapter so that, once they are implemented, we may upload contents of that chapter as well. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 28/02/12 21:48, Alex Glikson wrote: Juanjo, all, I would recommend to plan our work in such a way that everyone have at least two work-days to respond to an email, and at least three work-days 'lead time' to perform any non-trivial action/task (or one week for tasks involving communication between partners). Regards, Alex P.S. the exact 'lead time' periods are negotiable, but it certainly can't be a matter of hours -- especially when it comes to important deliverables P.P.S in fact, since one also needs to download & upload again all the diagrams, it takes much more than half an hour From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 28/02/2012 06:08 PM Subject: Re: [Fiware-wpl] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Hi all, I provided the instructions at 07:43 so that you can start with the task of migrating contents from the private to the public wiki and so far (ten hours after) I haven't seen anything on the public Wiki. The only chapter who was asked not to do this until I provided further comments (already sent a couple of minutes ago) was the IoT chapter. What about the others ? I believe that is important to show some results to Arian tomorrow morning ... Carrying out the transference is just a matter of few minutes (probably less than half an hour per chapter) ... Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 28/02/12 07:43, Juanjo Hierro wrote: 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 email: 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_______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ 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: From jhierro at tid.es Wed Feb 29 07:14:44 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 29 Feb 2012 07:14:44 +0100 Subject: [Fiware-wpl] Thanks for your effort uploading agreed contents of the Architecture Deliverable to the public wiki Message-ID: <4F4DC254.3000708@tid.es> Hi all, Thanks for your efforts uploading contents of the Architecture Deliverable to the public wiki. Today, we have an "educational session" about FI-WARE with the FINSENY UC project which happens to meet in Madrid today. Showing the contents we have been able to upload will be helpful to prove them that the FI-WARE Architecture deliverable will provide the kind of information that will allow them to understand how their applications can be designed/programmed. Once again, thanks. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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 From torsten.leidig at sap.com Wed Feb 29 08:48:59 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 29 Feb 2012 08:48:59 +0100 Subject: [Fiware-wpl] [Fiware-wpa] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki In-Reply-To: <4F4CE317.1040606@tid.es> References: <4F4C7775.2040703@tid.es> <4F4CE317.1040606@tid.es> Message-ID: Hi Junajo, thanks for your response despite your current workload. I agree that the FI-Ware results/publications (outside communication) appear as uniform and sound as possible. However, in order to achieve this, I think we should at least within the WPL/WPAs share our ideas and concerns frankly. Finally all partners should be on the same page. I'm probably interpreting more into FI-WARE than it actually is. So I would like to continue the discussion and learn what a GE and an Open Specification really means. Maybe we can continue on a later point in time if we don't have time now. If all other WPL/WPA don't see a problem with the current approach I will not object, I'm just asking questions. In the DoW it's said that the D.x.1 (Open Specifications) have to be delivered in a draft version in M9 too! I think we urgently have to think about how to recover from our permanent delay. Best regards, Torsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Dienstag, 28. Februar 2012 15:22 To: Leidig, Torsten Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] Instructions on how to publish contents of the Architecture deliverable in the FI-WARE public wiki 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] On Behalf Of Juanjo Hierro Sent: Dienstag, 28. Februar 2012 07:43 To: fiware-wpl at lists.fi-ware.eu; 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 email: 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: From matteo.melideo at eng.it Wed Feb 29 10:44:54 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 29 Feb 2012 10:44:54 +0100 Subject: [Fiware-wpl] code deliverables In-Reply-To: References: Message-ID: <4F4DF396.7050307@eng.it> Dear Alex, thank you for this mail, it is extremely important to be clarified. I raised the issue during the Wp9 conference call but I just want to clarify that when I talked about source code of the Prototype deliverables I meant only the foreground knowledge (i.e. software code developed under the FI-WARE Grant) and not background one (i.e. pre-existing code). In addition to this, I did not mean to provide the software code in a public repository market as Public (PU) but in the private area of our portal marked Restricted (RE) or Confidential (CO) according to the licence and Consortium Agreement agreed policies. Best Matteo Il 28/02/2012 22:16, Alex Glikson ha scritto: > Dear all, > > I've been asked by one of my colleagues whether partners are supposed > to provide source code of deliverables. > To avoid confusion and legal issues in the future, it is important to > clarify that per the Consortium agreement, partners are *NOT* obliged > to provide any proprietary source code. > I am not a lawyer, but my understanding is that exceptions are > possible (when there is a clear need) -- but might require some legal > formalities. > > Juanjo/Jose -- please, confirm/clarify. > > Thanks, > Alex > > P.S. Consortium agreement can be found at > https://forge.fi-ware.eu/docman/view.php/7/688/IPCA_FI-WARE_final_12th_sept_2011.pdf > > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From GLIKSON at il.ibm.com Wed Feb 29 11:09:59 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 29 Feb 2012 12:09:59 +0200 Subject: [Fiware-wpl] code deliverables In-Reply-To: <4F4DF396.7050307@eng.it> References: <4F4DF396.7050307@eng.it> Message-ID: Dear Matteo, all, Per the CA (Section 4.2.7.1 (c)): "...no Party shall be obliged to grant Access Rights to Source Code. All Access Rights to Software that is Foreground, whether for execution of the Project or for Use, shall be in the form of Limited Source Code Access." The definition of "Limited Source Code Access" is (Section 1.2): Limited Source Code Access means: (a) access to Object Code; or, where normal use of such Object Code requires an API, access to such Object Code and such API;or (b), if (a) is not available, access to Source Code if the requesting Party can demonstrate such access is Needed and in any case strictly limited to the extent Needed. To summarize, the "default" is to share binaries and APIs -- for both foreground and background. Only if there is a clear justification (e.g., integration can not be done otherwise), portions of the actual source code can be shared. In fact, this makes a lot of sense to me, because we start the project from existing assets, some of which are proprietary. And the "foreground" work is often about enhancing those assets. So, it doesn't make sense to share the "delta" if you don't share the original code base. Regards, Alex From: Matteo Melideo To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , "fiware-pcc at lists.fi-ware.eu" Date: 29/02/2012 11:44 AM Subject: Re: [Fiware-wpl] code deliverables Dear Alex, thank you for this mail, it is extremely important to be clarified. I raised the issue during the Wp9 conference call but I just want to clarify that when I talked about source code of the Prototype deliverables I meant only the foreground knowledge (i.e. software code developed under the FI-WARE Grant) and not background one (i.e. pre-existing code). In addition to this, I did not mean to provide the software code in a public repository market as Public (PU) but in the private area of our portal marked Restricted (RE) or Confidential (CO) according to the licence and Consortium Agreement agreed policies. Best Matteo Il 28/02/2012 22:16, Alex Glikson ha scritto: Dear all, I've been asked by one of my colleagues whether partners are supposed to provide source code of deliverables. To avoid confusion and legal issues in the future, it is important to clarify that per the Consortium agreement, partners are *NOT* obliged to provide any proprietary source code. I am not a lawyer, but my understanding is that exceptions are possible (when there is a clear need) -- but might require some legal formalities. Juanjo/Jose -- please, confirm/clarify. Thanks, Alex P.S. Consortium agreement can be found at https://forge.fi-ware.eu/docman/view.php/7/688/IPCA_FI-WARE_final_12th_sept_2011.pdf _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl [attachment "matteo_melideo.vcf" deleted by Alex Glikson/Haifa/IBM] -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Feb 29 15:09:34 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 29 Feb 2012 15:09:34 +0100 Subject: [Fiware-wpl] Technical roadmap Message-ID: <4F4E319E.9040301@tid.es> Hi all, We are still working on the reference example and guidelines for producing the Technical Roadmap deliverable. We will deliver it later this evening. We are trying to provide a rather clear set of instructions, plus an example around the Data/Context Management Chapter, that avoids having to fix things later in order to achieve the necessary alignment. At the same time, something rather easy to write (no more than two pages, probably closer to one, per chapter) which focuses on what can be useful. In the meantime, keep working on the Architecture Deliverable to meet the March 6 deadline, please. I also encourage you to plan activities in the Sprint of March (if you haven't already done so). I understand that this Sprint should already include activities dealing with actual software development around GEs for most of the chapters. I would like to review such planning in the bilateral meetings we will have next week. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: 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