[Fiware-security] TR: [Fiware-wpl] Addressing the comments of reviewers on FI-WARE Product Vision document

[BISSON Pascal]

Dear Task leads and/or Caretakers,

I'm forwarding you this email for your information.

First: I'd like each of the task leads to perform final check of wiki content. Don't forget also as it has been done for Security Monitoring to indicate what (features/users stories or work items) would be in scope of the first (and second release if you manage) of the first Major release (M12). See fields on the Security Backlog management tracker to do so. Please do it right now ! (remember TID is going to generate a .pdf book for the official submission of the FI-WARE Product Vision deliverable tonight, based on contents of the Wiki at that time). In case of any difficulties please feel free to give me or Daniel a Call.


Second: I'd like each of you to provide me by tomorrow EOB your view on how the following points can be best highlighted at the review:
- Address Identity and privacy, content rights protection/management, network integrity and service operation protections for network providers, traceability as requested by government authorities and regulator requests.
- Elaborate an end-to-end overall strategy.
- explain approach about identification of Epics related to Security in the different chapters.


Counting on you and hearing from you.

Regards,
Pascal


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é : vendredi 11 novembre 2011 14:27
À : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Objet : [Fiware-wpl] Addressing the comments of reviewers on FI-WARE Product Vision document

Hi all,

  We have made an analysis of the comments that reviewers made on our first release of the FI-WARE Product Vision (referred in the Dow as "FI-WARE High-level Description".   Results of this analysis is provided below.   Please find enclosed the comments they sent to us and I forwarded to you at that time.

  This email has to do with a number of action points you should implement in order to cover most of the comments and show it in our review.   We have categorized them into:

 *   Changes to implement in contents linked to the FI-WARE Product Vision on the Wiki.  The suggested changes are quite straightforward and easy to implement, so it should be feasible to address them before Monday Nov 14th EOB.
 *   Points to highlight/explain in your presentation for the review.   You should have a few of slides (better if just one) ellaborating on these points (check my previous mail)
  This is kind of the minimum we should try to tackle.   Of course, feel free to add any more enhancements in the Vision description of your chapter to address the specific comments that reviewers have made on your chapter (again, the document with the comments from reviewers is attached for your convenience).   However, take into account that we will close and produce the .pdf book deliverable by Monday Nov 14th night.

  Thanks for your effort,

-- Juanjo


*******************************************************

Comments from reviewer follow the convention A<number>.<paragraph> where A<number> designates the numbering of the section in the document gathering reviewers' comments and <paragraph> designate the paragraph within that section.

1) Cloud WP
-> Issues to update on the Wiki
A4.2 Fig9 (section 3.2.5.1 D2.2): Game console could be considerd for the function of cloud proxy along the ISP/Telco classical CPE.
       (Note: It should be enough to mention this possibility of using other devices in terms/definition section)
A4.3 Resource Monitoring.  Try to enhance the description a bit.

-> Points to highlight/explain in the presentation for the review
- Areas demanding clear innovation: cloudbursting, federation, edge proxies/caches & mitigatin dependency risks.
- Approach regarding metering/billing
- Clarify that it's too early to describe in detail what users will have available regarding functionality of self-service portal (check if it would be feasible to enhance the current description on the Wiki, though).

2) Data/Context WP
-> Issues to update in the Wiki
A5.2 Unstructured data analysis: more detailed description.
A5.4 Change the text within section 4.3.1.2 "The Social Network Analytical capabilities..."

-> Points to highlight/explain in the presentation for the review
- Preference given to OMA's framework has to be justified.
- Unclear why GEs Implementin Intelligent Services are sub-classified. Are they so specific that should be tackled by U-C?
- Opinion mining (section 4.3.5) is addressing marketing and sales. What is the borderline between a real-field implementation project and interference with market functionalities.
- Internal GE communication (section 4.4.2) raises a concern that inter-GE communication may not be uniform across FIWARE infrastructure. Must be addressed at the level of a framework architecture identifying relationships between GEs.

3) Application & Services
-> Issues to update in the Wiki
A6.1 Should services and applications be considered as synonyms for the same functional entity type.  Probably a small change (adding some sort of statement) in the current description helps to close this comment.
A6.2 Add sentence where appropriate updating on status of endorsement of USDL by W3C/industry
A6.3 Federation should be considered in the descriptions of repository, registry and marketplace.   Try to add some wording on the matter (at least mentioning that this will be evaluated)
A6.5 Add definition of "Aggregator Repository" and "Model repository". Try to fix the issue referred regarding red question marks in initial figure and inconsistency with issues mentioned in section about issues

-> Points to highlight/explain in the presentation for the review
- Clarify that the concrete proposals on Composition/Mashup technologies has been address once we have started with the Materialization of the FI-WARE vision
- Explain positioning regarding BPMN/BPEL
- Explain why some of the GEs are not detailed described


4) IoT
-> Issues to update in the Wiki
A7.2 Standardization is generally well described but some more details are missing on surveillance cameras (ONVIF forum and formal stds at IEC and ISO).
A7.3 Better describe relation of IoT and I2ND GEs beyond clear association.
 Note: Just list which GEs/GEs-functions might be used by IoT components.

-> Points to highlight/explain in presentation for the review
- What we think on reviewer's recommendation: Use UDDI if compliant with GEs provided by Apps/Serv Ecosystem and Delivery GE.



5) IN2D
-> Issues to update in the Wiki
A8.3 For short range radio maybe consider NFC?  (note: Don't know if this comment is suitable, otherwise explain in presentation for the review)
A8.4 check if some easy explanation with a short paragraph can be provided to deal with the question: In the list of functionalities under Media Services, does "Graphics rendering" relate to those specific examples or Video in general?

-> Points to highlight in the presentation for the review
- Explain how this arch is suitable for small, embedded devices (limited regarding resources and connectivity).


6) Security Privacy and Trust
-> Issues to update in the Wiki
No further changes are foreseen.   Of course, further detail will be required but this will be addressed in the architecture specifications

-> Points to highlight in the review
- Address Identity and privacy, content rights protection/management, network integrity and service operation protections for network providers, traceability as requested by government authorities and regulator requests.
- Elaborate an end-to-end overall strategy.
- explain approach about identification of Epics related to Security in the different chapters.

*******************************************************



________________________________
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: <https://lists.fiware.org/private/old-fiware-security/attachments/20111114/39c31d96/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FI-WARE progress review 1 report.pdf
Type: application/pdf
Size: 50994 bytes
Desc: FI-WARE progress review 1 report.pdf
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20111114/39c31d96/attachment.pdf>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20111114/39c31d96/attachment.txt>