Hi all, A few comments, sorry if I am out of discussion's context. · When I look at the picture in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3I2ND I have the impression ( from this picture) that the added value of S3C is only that it gives access to CDI and Cloud proxy to network operators. In effect apps developers and cloud services (in upper layer) have access to everything while network operators have also access to NetIC. As in the subsequent text in the Wiki, my understanding of the role of S3C was different, I supposed it was to expose Network APIs to the upper layer of effect apps developers and cloud services. Plus if network operators have a direct access to NetIC why would they bother to go to S3C first to give them access to NetIC? I would have expected something like that : · Another thing is that I don't feel at ease with the EPC "OTT API" for two reasons: o First, OTTs often use HTTP and Orange provides a HTTP API exposure layer. So if the "EPC OTT API is also in HTTP, probably it must go through the API mediation layer. o Second, even if the "EPC OTT API" is not about HTTP, IMO it must be a bit clearer defined both in terms of protocol and in terms of usage. Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoyé : mardi 28 février 2012 16:57 À : Hans Einsiedler (Hans.Einsiedler at telekom.de); WUENSTEL, Klaus; BANNIZA, Thomas-Rolf; Woods, Chris; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); Defrance Serge Cc : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] Wiki Architecture pages Dear All, Here is a short summary of the analysis on the I2ND pages for Architecture deliverable https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3I2ND Each Item below corresponds to one section of the document; for each, some suggestion is given about what needs to be done in my opinion, to better comply with templates and guidelines. - Introduction ok - Overview ok - Open specifications of each GE (Task Coords to organize work on them) o Note: Common structure of each GE page should be: § Overview · It might Include the architecture of GE (see below) § Basic Concepts · It might Include the architecture of GE (architecture must be present either here or in the Overview) § Main Interactions · Sub-sections for each interface/functionality exposed § Basic Design Principles o CDI page § Modifications are under evaluation between Chris and myself o CE page § The 'basic design principles' portion should be pulled out from each subsection of 'Main Interactions' and should go to the final 'Basic Design Principles' section (not present now) o NetIC page § General Note should go into Overview (subsection in it?) § Basic Design Principles: should these items go into Basic Concepts or should they be moved to end of page, as actual 'Basic Design Principles' section? I would vote for option 1... § Main Interactions should be moved up one layer of structure § NetIC Architecture should be moved down one layer of structure o S3C page § Hans is taking care of it, he'll provide more details on the possible updates - Interfaces to other GEs -> Pier/Hans agreed to populate the section according to the GE interfacing tables circulated in past days Can you have a look at these details and provide possible updates to the pages if you agree on what proposed, thanks a lot. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120228/17ffc369/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120228/17ffc369/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 83410 bytes Desc: image002.png URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120228/17ffc369/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy