Dear All,
please check whether you can update a little bit more the tables 7b and 7c, according to the suggestions reported by Lindsay in his mail below, concerninf I2ND chapter. I made already some few updates to some item I better know, for the others I rely on your support.
BR
Pier
Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juan Bareño Guerenabarrena
Inviato: giovedì 26 luglio 2012 10:37
A: fiware-wpl at lists.fi-ware.eu
Cc: Ernoe.Kovacs at neclab.eu; carmen.perea at atosresearch.eu; Lindsay.Frost at neclab.eu
Oggetto: [Fiware-wpl] Standardization Plan FI-WARE D11.4 Deliverable- LAST CALL FOR CONTRIBUTIONS
Dear WPLs
As we agreed on the last WPL weekly phone conference the deadline for last contributions, expired yesterday, and there has been few progress on this issue
Please review the NEC comments on the status of each chapter, and complete the missing information in each table, see guidelines about how to complete the tables in the last part of the mail form NEC below, additionally we need a picture of the overall architecture and exposed interfaces which we want to standardize, see (1) point and proceed accordingly
We set a final deadline for this contributions, before Saturday 28.07.2012 at 17:00, so please proceed accordingly and complete the missing information ASAP
Thanks for your contribution
Juan
From: Lindsay Frost [mailto:Lindsay.Frost at neclab.eu]
Sent: jueves, 26 de julio de 2012 0:05
To: Juan Bareño Guerenabarrena
Cc: Carmen Perea Escribano; Nuria De-Lama Sanchez; Ernoe Kovacs
Subject: RE: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2//
Dear Juan,
I looked at https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2
and do find quite some material has been input, but of course not enough to satisfy the EC.
So far I2ND is best and Data Context Management is worst. Please see action items below.
I explain below the status and what is missing, and I ask you to fwd this email to the WPLs to get them
to urgently add new material by Saturday 28.07.2012 at 17:00. Comments in red below are action items.
Please note that the intention is to show:
- FI-WARE knows what it wants to monitor/contribute
- FI-WARE has done monitoring and already some contributions
- FI-WARE has a plan to get some important interfaces (reference points) openly standardized.
At the end of this email I include an explanation in some detail for each required cell in the tables ..
Progress in the Standardization Plan plus action items
https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2
(1) Architecture diagram and labels of exposed interfaces
We need a picture of the overall architecture and exposed interfaces which we want to standardize.
We need the lists of Reference Points in Table(a)-Column3 to match those names on that picture.
So far the Table-a names do not even match the partial architectures found on the wiki at these places,
we need a single consistent picture.
· http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Cloud_Hosting_Architecture
· http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Internet_of_Things_%28IoT%29_Services_Enablement_Architecture
· http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Security_Architecture
· http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Architecture_of_Applications_and_Services_Ecosystem_and_Delivery_Frameworkhttp://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Interface_to_Networks_and_Devices_%28I2ND%29_Architecture
· http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Interface_to_Networks_and_Devices_%28I2ND%29_Architecture
· http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Data/Context_Management_Architecture
(2) Cloud Hosting
Table 7a (IF to SDO) is existing with quite a lot of content, thanks to GLIKSON, Alex <GLIKSON at il.ibm.com<mailto:GLIKSON at il.ibm.com>>.
But the Reference Points do not match the partial architecture in this figure<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Cloud_Hosting_Architecture>.
Please provide right figure and names.
The dates in Column1 are generic and do not show any history of contributions/monitoring of past meetings.
Please put in dates of some previous meetings and future ones and mention specific contributions.
The dates in Column1, even for the future, do not show any specific ideas to Contribute.
The list of Partners is present, thank you, but no list of names - that makes it look like nobody is allocated!
Please name the delegates who attend. Worst case, look at the meeting minutes!
Table 7b (partner responsibility)
Delegate names are missing.
Table 7c (Timeline) are empty.
Please add brief current status for each SDO.
(3) Data Context Management
CARLOS RALLI UCENDO ralli at tid.es<mailto:ralli at tid.es> has put nothing there yet
(4) Internet of Things
Table 7a is existing with quite a lot of content, thanks to thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com> and lorant.farkas at nsn.com<mailto:lorant.farkas at nsn.com>
But the Reference Points do not match well the partial architecture in this figure<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Internet_of_Things_%28IoT%29_Services_Enablement_Architecture>.
Please provide right figure and names.
The IETF CORE gives a quite good example of how to fill in the table with real contribution links
Please provide titles/links to contributions in other SDOs listed.
Table 7b is existing, but the names of reference points do not match Table 7a
Please fill in correct reference point names in Column2 (should be identical to table 7a)
Table 7C only started
Please fill in more specific goals and estimated dates. Should be something for each interface.
(5) Applications Services Ecosystem
Inputs from torsten.leidig at sap.com<mailto:torsten.leidig at sap.com>
(see above example explanations)
(6) Security
Table for 7a, 7b, 7c partially filled in. Thanks to pascal.bisson at thalesgroup.com<mailto:pascal.bisson at thalesgroup.com> and
daniel.gidoin at thalesgroup.com<mailto:daniel.gidoin at thalesgroup.com>
Some entries missing, but it is coming into shape. Please see above example explanations to improve it.
(7) I2ND
Table 7a is very good, thanks to pierangelo.garino at telecomitalia.it<mailto:pierangelo.garino at telecomitalia.it>
Table 7b is existing, but the names of reference points do not match Table 7a
Please fill in correct reference point names in Column2 (should be identical to table 7a)
Table 7c is very good, but does not include any future goals.
Are all needed specs completed? If not, say what is needing more work.
General explanations of what goes in each Table (comments in red)
The Table (a) is intended as a sequential sequence of dates to record past activities at specific meetings, and also to write in what future activities are planned.
TABLE (a) : Summary of SDO activities and interfaces for Cloud Hosting chapter
(This is meant to outline _future_ intended contributions or monitoring of _specific_ events, like a calendar, and to _record_ successful contributions or monitoring-reports of the past)
Dates
SDO as link
Exposed FI-WARE Interface
Contribute or Monitor
Contribution title as link and SDO ID
Responsible Partner(s) and Person(s)
Stds-Phase IPR-issues Comment & Status
(Date should be specific for when a meeting occurred and FI-WARE either monitored or contribute ... not just a span of xx months!)
(should be link to the main page of the SDO so EC can quickly see the Org.)
(should be _consistent_ name for the FI-WARE interface(s) which are _influenced_ by the SDO or are intended to be standardized openly in the SDO).
(Monitor an SDO which provides useful _input_ for FI-WARE and Contribute to an SDO where a FI-WARE interfaced needs open standardization.)
(Write specific document and link if possible, or for planned contributions give an indicative title.)
(Partner corporation)
(For the specific date of a meeting or planned meeting, write what was achieved or what is the monitored status of the specifications which are being tracked).
Table 7b
(This is meant to show which Person from which Partner is responsible for monitoring or contributing
for each "Exposed Interface" in each identified SDO. It shows who does what, for planning purposes)
SDO
Exposed FI-WARE Interface
Responsible Partner
Responsible Person
Comment
(duplicated from Table 7a)
(duplicated from Table 7a)
(duplicated from Table 7a)
(Add a delegate name. This is the key information!)
(Can be empty, or can say "delegate is vice-chair" or "delegate is expert in ontologies" or something like that)
Table 7c
(This table is intended as a summary of a long history of contributions in Tables 7a and 7b,
just showing to the EC the current/final result in Column7. )
Dates
SDO or event
contribution title and SDO ID
Exposed Interface
responsible partner
responsible person
phase/IPR/comment/status
...
...
...
...
...
...
(Explain if the work is Feasibility Study, Architecture, Protocol phase; explain if IPR is included from FI-WARE; explain if work is completed or blocked or ongoing ...)
From: Juan Bareño Guerenabarrena [mailto:juan.bareno at atosresearch.eu]<mailto:[mailto:juan.bareno at atosresearch.eu]>
Sent: Donnerstag, 5. Juli 2012 15:49
To: fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>
Cc: jhierro at tid.es<mailto:jhierro at tid.es>; mcp at tid.es<mailto:mcp at tid.es>; nuria.delama at atosresearch.eu<mailto:nuria.delama at atosresearch.eu>; carmen.perea at atosresearch.eu<mailto:carmen.perea at atosresearch.eu>; Ernoe Kovacs; Lindsay Frost
Subject: FW: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2//
Importance: High
Dear WPLs
Please find below the detailed plan for complete the standardization deliverable for M15, end of this month
Please react to what NEC, task leader, ask from you:
- Identify a responsible partner per WP
- Provide the inputs required in the wiki
- Review content and format requirements
For any doubt please contact Lindsay/Ernoe, in cc
Thanks for your contribution
Juan
From: Lindsay Frost [mailto:Lindsay.Frost at neclab.eu]<mailto:[mailto:Lindsay.Frost at neclab.eu]>
Sent: jueves, 05 de julio de 2012 15:12
To: Juan Bareño Guerenabarrena; Miguel Carrillo; Nuria De-Lama Sanchez; Carmen Perea Escribano; lorant.farkas at nsn.com<mailto:lorant.farkas at nsn.com>; thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>
Cc: Ernoe Kovacs
Subject: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2//
Importance: High
Dear FI-WARE management team,
Please distribute this email on PCC; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; and fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>
We refer to information provided to NEC in a teleconference on 02.07 by FI-WARE management regarding
providing in the next 3 weeks a new Standardization Plan.
NEC protests at the way the management decision was reached and communicated. The decision took
no account of NEC proposals which were sent 23.05.2012 and for which responses were
twice requested. The decision now requires NEC to make a burst of effort in the next 3 weeks
to immediately create a new Standardization Plan, without considering NEC staff availability.
Furthermore, the needed strategic inputs are not in the hands of NEC to create.
Nevertheless, NEC has created a new fast-track plan with some chance of success, assuming continuous
and strong input from partners. Endorsement, help and support from FI-Ware management and PCC
is strongly requested. Depending on the inputs from FI-WARE partners and the later review of the EC,
NEC will reconsider its' future participation in this part of WP11.
Outline of Plan (detailed plan below):
· FI-WARE WPLs identify which Generic Enabler interfaces are important and therefore crucial for standardization.
It is essential that a FI-WARE software architect complete such a list/diagram immediately to focus the work.
· FI-WARE WPLs nominate responsible partners and _persons_ who will input the plan and status for standardization
at _specific_ SDOs, for _each_ of those important interfaces (a subset of all interfaces)
· The nominated responsible persons input their plan into the private Wiki as described below, and update
the Wiki FI-WARE Standardization v2 (private wiki)<https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2> with (their) past contributions as well as planned future ones.
FI-WARE management team has promised weekly oversight of this activity.
· NEC summarizes results in last week of July, creating D11.4b pdf from the Wiki
NEC requests confirmation of this plan, which is detailed below.
Yours sincerely,
Dr. Lindsay Frost, Dr. Ernoe Kovacs
ATTACHMENTs
(1) Old, still valid Action Plan to react to EC comments (file 2012-05-23-ActionPlan.txt)
(2) Detailed Plan for D11.4.b by End July (see below)
Attachment 2:
The following is the step-by-step plan:
(D) NEC Conclusions for Standardization Plan content and format
6. General content required (to be generated by FI-WARE partners)
a. identify what standardization makes sense for FI-WARE (targets),
taking account of specific gaps which the EC requested fixed
b. identify where to do it (selected SDOs) /note: should reference "Section 2 CONTRIBUTE" actions in D11.4a/
c. explain (if it is planned) where IP generated in FI-WARE is inserted into SDOs specifications
d. for each selected SDO and FI-WARE target, show the timeline of how to achieve the target, with "concrete steps" and partners, starting work "even before usable results" as requested by EC
e. show how ongoing actual contributions to SDOs fulfill the "concrete steps" (i.e. ongoing status)
7. Step by step Format
a. WPLs create a webpage mapping important FI-WARE interfaces/protocols to the Target SDO which could be responsible. It should also indicate any IPR which FI-WARE may bring in. This webpage would satisfy (D)6.a and (D)6.b and (D)6.c above.
In the opinion of NEC, standardization is most valuable for the exposed interfaces, and in a secondary way to efficiently design the internal interfaces. Therefore all exposed interfaces are important, and some internal ones. As an example of some important interfaces, the (old) picture https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/Snapshot_2012.06.01_of_Deliverable_Page_for_D2.3_Architecture_Specifications could be used.
b. WPLs create a webpage showing which partner is responsible for each important interface and their responsible person to make it standardized. The format can be a table ("Target SDO / Responsible Persons") with entries <SDO><Exposed Interface><responsible partner><responsible person><comment>.
c. Responsible persons add to FI-WARE Standardization v2 (private wiki)<https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2> page, for each Target SDO, a timeline based on the SDO meeting schedules and methods, which is designed to get the exposed interface standardized. A partial example is given for ETSI M2M. This satisfies (D)6.d. This can only be created by the responsible persons who also ensure that that Target SDO work happens. It should indicate the phases as e.g. (1) feasibility-study (2) architecture (3) datamodels and protocols.
The format can be a table ("Target SDO / Contributions Table ") ordered by date, so later it is easier for the information to be integrated into a complete project plan, e.g. <dates> <SDO or Event><contribution title and SDO ID><Exposed Interface><responsible partner><responsible person><phase/IPR/comment/status>
d. The responsible person updates the Target SDO / Contributions Table every week, with new planned inputs and new results. Care should be taken to note any IPR. This satisfies (D)6.e.
e. NEC creates an integrated timetable showing the aggregated copies of all tables from step (c) above, which is the overview for the EC. NEC will combine it with (a) and (b) - assuming all partners have strongly contributed - so as to resolve all EC requests.
f. Optionally partners can extend the information in (c) above, to include highly relevant non-FI-WARE results which are monitored (M). Also partners can include relevant work they do which however is not part of the agreed important interface work. Monitoring standards is also part of the standardization plan and this work should be reported to the EC, as long as it is shown as supporting a significant amount of active contributions work.
NEC rejects proposals to use Googledocs because NEC was required to change from doc to Wiki during the previous phase of the project and the good reasons for doing that still hold.
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
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.
[cid:00000000000000000000000000000003 at TI.Disclaimer]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/20120726/08ed121f/attachment.html>
-------------- next part --------------
An embedded message was scrubbed...
From: Lindsay Frost <Lindsay.Frost at neclab.eu>
Subject: FI-WARE Exposed Interfaces
Date: Wed, 25 Jul 2012 15:31:19 +0200
Size: 547461
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120726/08ed121f/attachment.mht>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120726/08ed121f/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia2.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia2.jpg
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120726/08ed121f/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy