[Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter

[Calin Curescu]

Dear Horst, Andreas

I have changed:

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository

with:

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.CommonRepositoryImportExport

See reasons below,
/C

From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Calin Curescu
Sent: den 30 juli 2012 23:16
To: 'fiware-apps at lists.fi-ware.eu'; Juanjo Hierro <jhierro at tid.es> (jhierro at tid.es); torsten.leidig at sap.com
Subject: Re: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter

Dear Juanjo, Torsten,

Please find some answers to several Features regarding Composition that we took care of. Mathieu did some changes and I added some too. Please find my additions with green below.


As a generic comment I think it's a relevant proposal to have different GEs for the compositions flavors, but this we will discuss only after the 1st year review is finished, it would not be good to rush it.

BR,
/Calin


From: fiware-apps-bounces at lists.fi-ware.eu<mailto:fiware-apps-bounces at lists.fi-ware.eu> [mailto:fiware-apps-bounces at lists.fi-ware.eu]<mailto:[mailto:fiware-apps-bounces at lists.fi-ware.eu]> On Behalf Of Mathieu Hutschemaekers
Sent: den 30 juli 2012 14:09
To: 'fiware-apps at lists.fi-ware.eu'
Subject: Re: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter

Dear all,
(apologies for the premature, incomplete first mail. Please ignore.)
I looked at the comments and applied any changes I saw fit. I apologize if the changes are not as far-reaching as expected. If the suggested changes are not (fully) implemented, I provide in-lined comments.
I now see that all items are covered, one way or other, with the exception of   FIWARE.FEATURE.Apps.CompositionEditor.IoTB


7. Composition
  First of all, I wanted to clarify whether we are using some sort of convention for ids ... In a first approach it seems like the id of any Feature that applies to the Composition Editor, no matter whether it applies to masup of UI gadgets, composition of backend services using BPM standards or composition of backend services using the ECE platform, is preceded by a 'C3' prefix ...  This to distinguish them from Features like FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.Create%0d%0aion> which are specific of UI gadgets mashups.   However, later I read some features that I would say are also common to all three paradigms ... shouldn't their ids be preceded by a 'C3' ?   I'm talking about:

 *   FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured>
 *   FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation>
 *   FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository<ht%0d%0augins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository> (this one I'm not pretty sure
I know that the original intention of 'C3' was to indicate Ericsson specific items. So I changed them to indicate 'ECE' now. Since I am not sure whether all partners want to support all the items in your list we have to consider that separately. rmal style='margin-bottom:12.0pt'>Regarding the "semantic" features above: Only Atos work deals with special semantic task transformation, thus the 2 fatures cannot be transferred to the other Composition Editors.
Regarding "common" features, I agree they exist and we should uniformize them, but we can more formally on this after this review. For the time being, there are two Features that all the editors need to do: Import/Export to/from USDL repository, and search services from the Marketplace.  The "USDL" feature above I have change to represent both import/export. The feature below I created to represent the search in the Marketplace. This answers also your concern on federation, the Marketplace is feder tories. To show this I put the name "common" in the 2 features.
Thus:
FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository is replaced by: FIWARE.FEATURE.Apps.CompositionEditor.CommonRepositoryImportExport
and
FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService is replaced by: FIWARE.FEATURE.Apps.CompositionEditor.CommonSearchInMarketplace
FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService> Feature: I guess it would be worth mentioning whether a given Composition Editor will be able to federate the services in multiple distributed USDL Repositories.   I guess it would be nice to support it.   Since I guess this will not be supported for the first release, I would go for splitting it into two Features or one Feature and an Epic, the former referring to access to a concrete USDL Repository (i.e., ability to connect to a single one) and the later linked to an extension of future releases to support federation.
At the moment the idea is that the composition editor works against the marketplace who could cover a number of stores and, in that way, a number of repositories. I do not see the need to include a separate item to work against multiple repositories.A marketplace is federating service from several USDL repositories, thus a composition editor will compose services from several repositories and/or several business entities. See change of name in answer above.

  FIWARE.FEATURE.Apps.CompositionEditor.ECE-CreateComposition<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.ECE-CreateComposition> Feature: I would change the goal so that it says "Creation of an ECE-based Service Composition" for the same reasons I gave with my last comment regarding DT's service composition technology.   In the description, I would bind an URL to "... The tool is using Ericsson Composition Editor<cid:part18.02000804.07090907 at tid.es> constructs ..." which points to descriptive documentation of that components of Ericsson's product
I changed the goal, but will consider the suggestion about the document (no such document readil style='font-family:"Arial","sans-serif";color:#1F497D'>
A pointer to such a document (ECE user guide) has been added.

  FIWARE.FEATURE.Apps.ExecutionEngine.ECE-ExecuteComposition<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.ExecutionEngine.ECE-ExecuteComposition> Feature: I would change the t;Execution of an ECE-based Service Composition" for the same reasons.   In the description, I would bind an URL to "...Given a composition description in the Ericsson Composition Format<cid:part18.02000804.07090907 at tid.es>, provide ..." which points to descriptive documentation of the format
I changed the goal, but will consider the suggestion about the document (no such document readily available).
This is considered internally for future addition.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20120730/4d2f067f/attachment.html>