From dmorris at redzinc.net Mon Apr 16 17:38:45 2012 From: dmorris at redzinc.net (Donal Morris) Date: Mon, 16 Apr 2012 16:38:45 +0100 Subject: [Fiware-opencall-middleware] Questions for FI Ware Open Call Message-ID: <4F8C3D05.50702@redzinc.net> Hello We are submitting a proposal for the FI-Ware open call related to QoS/Security-aware invocation of services. My question related to the EPICs mentioned. Invocation of QoS/Security-aware invocation of services is likely to require more then just the EPICs referenced in the call (as per list below). Are you anticipating a wider set of EPICs to be included as foreseen by the proposal, or do you have a rigorous approach and only require support for the narrow EPICs set listed below. As an example, monitoring information from the data plane for a QoS service may be necessary to ensure that the service can be invoked satisfactorily and also for billing validation. No mention of a monitoring EPIC is given below. Please could you clarify: is FI-WARE open to receive a wider set of related EPICS, within the context QoS/Security-aware invocation of service? Thanks for your help and clarification. Donal Morris ** =================================== http://www.fi-ware.eu/open-call/ (Click here to find the Epics linked to this topic) https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Common_base_technologies#FI-WARE_Advanced_Middleware * FIWARE.Epic.General.Middleware.IDL * FIWARE.Epic.General.Middleware.API * FIWARE.Epic.General.Middleware.DataAccess * FIWARE.Epic.General.Middleware.Marshaling * FIWARE.Epic.General.Middleware.Negotiation * FIWARE.Epic.General.Middleware.TransportProtocol * FIWARE.Epic.General.Middleware.TransportMechanisms * FIWARE.Epic.General.Middleware.Dispatching * FIWARE.Epic.General.Middleware.Security -- ======================== Donal Morris Founder& CEO RedZinc www.redzinc.net + 353 86 8130009 + 1 408 757 0070 ======================== -------------- next part -------------- An HTML attachment was scrubbed... URL: