Hello again,
As promised, my comments to the backlog follow. The deadline is tight (tomorrow) so please react promptly.
General comments (for all WPs)
=============================
You should review the full description of your backlog entries in the Wiki to make sure all fields are properly filled in. Despite we provided a spreadsheet explaining how to fill each fields and some examples when we started this exercise (the spreadsheet was distributed in mid August) we have found that that guidelines haven't been followed in many cases. We have enhanced the tutorial on the Wiki to include all the explanations now and to make sure that there is a place on the Wiki that you can check out in case of doubt. You can find it at:
* http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_upload_the_full_description_of_backlog_entries_to_the_Wiki
Particularly important is the style used for the text provided as "Goal" field. Please try to align with the patterns provided in the description of this field.
Do not forget to visit the pages with instructions to handle the trackers:
* http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_and_configure_trackers_in_FusionForge
* http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapter
Particular comments (for this WP)
=============================
* Naming convention for naming (Id) user stories may be good to export to the rest of project
* No backlog entries on the Wiki nor the tracker regarding the Unstructured Data Analysis GE !
* typos in Ids of metadata pre-processing GE ?
* Backlog entries on the Wiki and tracker fully alligned except:
* Location Platform: some entries on the Wiki have no ticket
* There is functionality on the CEP that should be captured as Epic but still not there
The deadline is tomorrow, Friday 4 EOB
Best regards,
Miguel
El 03/11/2011 7:06, Juanjo Hierro escribió:
Hi all,
We need to make the final push to get the "Materializing the FI-WARE Vision" chapter of the Wiki done. Note that this part is quite important since identification of baseline assets and the planning for those assets was one of the major differences between the second and first release of the FI-WARE High-level Description (Product Vision) deliverable. This work about description of baseline assets and creation of the different chapter/GE backlogs is also a fundamental step in our process.
Please find bellow a message from Miguel Carrillo with detailed comments on things that are pending regarding Wiki contents. Please take a look to APs that are on your plate and get them done by EOB this Friday Nov 4th. They are not that complex, so I believe there is enough time to deal with all of them. Don't hesitate to ask any question you may have on the mailing list so that we can solve it asap.
Note that contents of the "Materializing the FI-WARE Vision" chapter will be one of the elements that will be carefully evaluated by our reviewers (and keep in mind that the second release of the FI-WARE Product Vision should have been delivered by end of September so we are already running late). We need to get this finished now so that we can announce the official delivery next week.
Best regards,
-- Juanjo
-------- Original Message --------
Subject: Materializing Data/Context Management in FI-WARE
Date: Wed, 2 Nov 2011 17:56:04 +0100
From: MIGUEL CARRILLO PACHECO <mcp at tid.es><mailto:mcp at tid.es>
To: JUAN JOSE HIERRO SUREDA <jhierro at tid.es><mailto:jhierro at tid.es>, CARLOS RALLI UCENDO <ralli at tid.es><mailto:ralli at tid.es>
Dear Juanjo & Carlos,
I am sending private emails to all WPLs with further comments to the " Materializing the FI-WARE Vision"<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision> section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. You have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) so you there is little more I have to tell you.
General comments (for all WPs)
=============================================================
* Still there are heterogeneous templates for assets. Take Samson<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform> and Hadoop<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Hadoop> as the reference templates for assets
* IPRs in Assets are very frequently expressed in a vague manner. “This product has IPR associated to it”, “Open source”… To end with this situation change all assets and put this:
* Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory<http://en.wikipedia.org/wiki/Fair,_reasonable,_and_non-discriminatory_terms>) Terms according to pre-requisites of the FI-PPP program".
* If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ")
* Open source: see Hadoop <http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Hadoop> and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible.
* If you rephrase this or use variants it's ok as long as the additions are properly explained.
* Programming Artifacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... )
* Delete empty sections. I see many blocks of "Themes", "Features" and "User Storys" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki
Particular comments (specific to your WP)
=============================================================
If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes.
1) COMMENTS ON ASSETS
* Publish/Subscribe Broker<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Publish.2FSubscribe_Broker>
* Context Awareness Platform (CAP<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Context_Awareness_Platform_%28CAP%29>) – ok
* Complex Event Processing<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Complex_Event_Processing>
* AMIT<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/AMIT> -Most of the fields empty (Programming artifacts, technologies used, Runtime pre-requisites and IPR) – no changes since my last communication.
* BigData Analysis<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#BigData_Analysis>
* Hadoop<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Hadoop> - ok
* MongoDB<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/MongoDB> - ok
* SAMSON Platform<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform> - Publicly Av. Info to be enriched
* Multimedia Analysis<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Multimedia_Analysis>
* codoan<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Codoan> – “Programming artifacts” and “Publicly available documentation” are empty– no changes since my last communication.
* 'White Diamond'<https://forge.fi-ware.eu/docman/view.php/9/504/TI+Recognition+Sep+2011.pdf> – ok
* Unstructured Data Analysis<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Unstructured_Data_Analysis>
* The format is ignored in the main page of “Materializing Data/Context Management in FI-WARE”, it does not show the sections nor identifies “Baseline Assets”, “Themes”, “Epics” ,”Features” & “User-Stories”
* Just links to external sites. No work here at all.
* Meta-data Pre-processing<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Meta-data_Pre-processing>
* SinoVE Meta-data Processor<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SinoVE_Meta-data_Processor> - “Runtime pre-requisites” still “t.b.d.”
* Location Platform<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Location_Platform>
o location server<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Location_server> – OK.
o Location Provider<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Location_Provider> – OK
* Query Broker<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Query_Broker>
* THESEUS QueryBroker<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/QueryBroker> – Empty “Programming artifacts” & “Runtime pre-requisites”. The “Tecnologies used” section seems somewhat poor(“The asset is implemented in Java. ”).
* Semantic Annotation<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Semantic_Annotation>
* TI's 'Semantic Annotator (SAnr)'<https://forge.fi-ware.eu/docman/view.php/9/503/TI+Semantic+Sep+2011.pdf> – ok
* Semantic Application Support<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Semantic_Application_Support>
* NeOn Toolkit<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/NeOn_Toolkit> - ok (if it is an external tool, we should remove fields and go for the “short” template)
* Sesame<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Sesame> - ok (if it is an external tool, as I believe, we should remove fields and go for the “short” template)
* OWLIM<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/OWLIM> - ok (if it is an external tool, as I believe, we should remove fields and go for the “short” template)
2) COMMENTS ON BACKLOG
* I will send you this first thing in the morning
Please make sure that this is properly looked at by all the concerned members of the WP under your supervision.
Deadline: Friday, 4 EOB.
Thanks for your cooperation
Miguel
--
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito C
_/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 5
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
_/ _/_/ Madrid 28050 (Spain)
Tel: (+34) 91 483 26 77
e-mail: mcp at tid.es<mailto:mcp at tid.es>
----------------------------------------------------------------------
________________________________
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
--
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito C
_/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 5
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
_/ _/_/ Madrid 28050 (Spain)
Tel: (+34) 91 483 26 77
e-mail: mcp at tid.es<mailto:mcp at tid.es>
----------------------------------------------------------------------
________________________________
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-data/attachments/20111103/19c93319/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy