Please, make sure our standardization-related activities in the wiki are
up to date.
Thanks,
Alex
====================================================================================================
Alex Glikson
Manager, Cloud Operating System Technologies, IBM Haifa Research Lab
http://w3.haifa.ibm.com/dept/stt/cloud_sys.html |
http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml
Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile:
+972-54-6466667 | Fax: +972-4-8296112
----- Forwarded by Alex Glikson/Haifa/IBM on 08/07/2013 07:21 PM -----
From: Juan Bareño Guerenabarrena <juan.bareno at atosresearch.eu>
To: fiware-wpl at lists.fi-ware.eu, fiware-pcc at lists.fi-ware.eu,
fiware-exploitation at lists.fi-ware.eu,
Cc: Lindsay.Frost at neclab.eu
Date: 03/07/2013 09:48 AM
Subject: [Fiware-wpl] FW: Standardization_Plan_D11 4c - your input
needed by next week PLEASE REACT!
Sent by: fiware-wpl-bounces at lists.fi-ware.eu
Dear Colleagues
Please react to what people form NEC, as Standardization task leaders, are
requesting, see mail below
Take into account that The time has come to panic again and write the
FI-WARE D11.4c deliverable, due in July.
Thanks for your collaboration
Juan
From: Lindsay Frost [mailto:Lindsay.Frost at neclab.eu]
Sent: lunes, 01 de julio de 2013 16:39
To: Juan Bareño Guerenabarrena; fiware-standardization at lists.fi-ware.eu;
Ernoe Kovacs; fiware-wpl at lists.fi-ware.eu; mcp at tid.es; Nuria De-Lama
Sanchez; Miguel Carrillo; Nuria De-Lama Sanchez; Carmen Perea Escribano;
lorant.farkas at nsn.com
Cc: Ernoe Kovacs
Subject: Standardization_Plan_D11 4c - your input needed by next week
Importance: High
Dear all, please forward this if my mail does not reach all concerned.
Please note, I will probably ?deliver? whatever is made available to me on
July 15th, and then leave
Germany for 4 weeks holiday without email contact, in the Australian
outback. So please reply soon.
The time has come to panic again and write the FI-WARE D11.4c deliverable,
due in July.
Attached is a (badly formatted) doc version of the previous deliverable,
which I only use
to conveniently ask your opinion on a few "change tracked" remarks in
yellow highlighting.
I ask everyone receiving this to confirm if you agree with this basic
approach to updating ?
1) confirm who is "contact person" per topic
2) ask the contact person to supply (new) names of the "sdo
delegates"
3) ask the contact person to re-write the informative texts
in each chapter
(see attached file for getting the idea). Note that
the EC complained when they
read it about lack of details/deliverables (e.g BigData, HGI, OneM2M,
OMA NGSI, others).
4) write to old and new sdo delegates asking for immediate
update of
the tables of activities for each SDO (and chase
them!)
I ask the contact person for each topic to re-write their informative
texts in the wiki
http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Standardization_Activities
within the next week (otherwise I cannot guarantee the material will be
included in Deliverable).
Note that I already contacted everyone in some emails, asking for updates
(see attached,
(15.03.2013 " Request your input for D11.4 re Standardization activity in
your Work Package")
but only FRP at zurich.ibm.com and alexandre.boeglin at inria.fr replied (thanks
guys!)
Thank you for your confirmation (or improvement) of this approach.
Best wishes!
Lindsay
________________________________________
Dr. Lindsay Frost, Chief Standardization Eng.
frost at neclab.eu Mobile +49.163.275.1734
NEC Laboratories Europe, Kurfürsten-Anlage 36,
D-69115 Heidelberg, Germany.
Reg. Headoffice: NEC Europe Ltd, VAT DE161569151
Athene, Odyssey Business Park, West End Road,
London HA4 6QE, Reg. in England 2832014
------------------------------------------------------------------
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.
------------------------------------------------------------------
----- Message from Lindsay Frost <Lindsay.Frost at neclab.eu> on Sat, 16 Mar
2013 00:16:36 +0200 -----
To:
fiware-wpl at lists.fi-ware.eu
cc:
Juan Bareño Guerenabarrena <juan.bareno at atosresearch.eu>,
fiware-standardization at lists.fi-ware.eu, Ernoe Kovacs
<Ernoe.Kovacs at neclab.eu>
Subject:
Request your input for D11.4 re Standardization activity in your Work
Package
Dear Work Package Leaders,
(and people on CC who are referenced as SDO contacts for standardization)
REQUEST
For the Deliverable 11.4 on Standardization Plan, to show impact of FIWARE
work on Standardization,
I ask for your input on what kind of activity _your_ Work Package
considers to make to some SDOs ??
According to Juan Bareño Guerenabarrena, updated information will be
checked at every weekly WPL call.
BACKGROUND
The plan so far communicated to the EC for your Work Package is listed at
Cloud Hosting,
Data Context Management, Internet of Things, Applications Services
Ecosystem, Security, and
Interface to Networks and Devices, but the EC complained in the latest
review in November about lack
of details/deliverables (e.g BigData, HGI, OneM2M, OMA NGSI, others).
PROPOSED WAY TO INPUT DETAILS
Please inform what you plan:
(a) monitor and report, or (b) present introduction about FIWARE, or (c)
make contribution(s), or
even (d) show a FIWARE demo ? Of course there will be delays or changes,
but it is important to start !
To help your planning compared to SDO meetings, there is a small tool in
the form of an excel file at
SDO_Calendar_2013 on the FIWARE private wiki main page
https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Main_Page#FI-WARE_Exploitation
.
The file is intended to remind you when various SDOs are holding meetings
so you can easily compare.
You can choose any of the following ways to give inputs:
(a) download SDO_Calendar_2013, insert input to ColumnE of sheet
?Timeline? and send file to Lindsay,
(see the small example in Cell E347 = ?DRAFT SCHEDULE ´OSGi
Cloud proxy´ Presentation and/or
Demo of WP7 ´Interfaces to network´ technology at HGI EVENT)
(b) or you can just send Lindsay some text in an email telling the date,
SDO and intended input. He inserts it.
(c) you may want to add missing SDO meetings, just send Lindsay details
and links to insert.
(d) you may have more questions for the FAQ below
Thank you for your input!
/Lindsay
___FAQ ABOUT XLS file FOR PLANNING STANDARDIZATION ACTIVITIES___
Comment 1: I don't have sufficient permissions to update the excel sheet;
Answer1a: The excel sheet does contain a macro, and some companies forbid
enabling external macros. However the whole document still works without
the macro except for the "colourful" summary page. Sheet ?Timeline? works
well ;-)
Answer1b: Some companies do not allow specific FIWARE members to confirm
attendance or activities in advance for SDO meetings, because travel is
not confirmed or other reasons. Nevertheless the IDEA to make such a
contribution can be entered as long as there is significant chance of
approval.
Comment2: multiple people work on the same offline document are likely to
overwrite one another's modifications
Answer2: yes, this is a problem, but Lindsay is willing (at this early
stage) to integrate all contributions sent to him, then he will upload a
revised version. Actually FIWARE has quite separate work packages so he
expects that within one WP the team members will succeed to "sent around
the file to eachother until it is finished" and cooperate well. Perhaps
after some experience of the desired inputs it may be possible to "custom
design" a web-page calendar instead, but first some data/experience needs
to be collected.
Comment3: information already present in the document implies it is not
intended for planning FIWARE contributions
Answer3: Trying to make one tool for all the relevant SDOs was difficult.
It is expected that modifications will be needed as soon as some
substantial inputs are received from WPLs. For example, it might be needed
to make extra columns for the planning of EACH work package, and to
install filters so that your viewing can be limited to exactly one WP at a
time. But the xls file is a start!
________________________________________
Dr. Lindsay Frost, Chief Standardization Eng.
frost at neclab.eu Mobile +49.163.275.1734
NEC Laboratories Europe, Kurfürsten-Anlage 36,
69115 Heidelberg, Germany.
Registered Headoffice: NEC Europe Ltd,
Athene, Odyssey Business Park, West End Road,
London HA4 6QE, Reg. in England 2832014
------------------------------------------------------------------
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.
------------------------------------------------------------------
_______________________________________________
Fiware-wpl mailing list
Fiware-wpl at lists.fi-ware.eu
https://lists.fi-ware.eu/listinfo/fiware-wpl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20130708/380268e4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Standardization_Plan_D11 4b.docx
Type: application/octet-stream
Size: 826460 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20130708/380268e4/attachment.obj>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy