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

[Mathieu Hutschemaekers]

Dear all,
In Calin's absence I looked at the comments and applied any changes I saw fit. I apologize if the changes are not as far reaching as expected.
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.CreateUIOrientedServiceComposition> 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<https://forge.fi-ware.eu/plugins/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.
 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.

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


  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


  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 goal so that it says "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

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