[Fiware-testbed] d10.5.3 for your validation and eventual submission

MIGUEL CARRILLO PACHECO miguel.carrillopacheco at telefonica.com
Fri Feb 6 11:54:45 CET 2015


Hi Stefano,

My comments are here:

  *   We are using FIWARE (not hyphenated) in all deliverables. If this is wrong, it is wrong in all the docs I've already sent. The only place where I keep it is in the "Project acronym" in case this refers to a fixed text in the systems of the EC or something. Right or wrong, I'd ask you to delete the hyphen in all the other places.
  *   The cover does not have footer or header. The rest of the doc does. If you go and start editing the header, word shows a flag allowing this. My MS Word is in Spanish but the capture is understandable
     *   [cid:part1.00000807.09030908 at telefonica.com]
  *   The footer must be regular font (no bold)
  *   "1.2    About This Document ":  "Normally those documents makes use of the feedback from the Use Case projects"
  *   "1.8    Changes History " - delete the empty rows at the end
  *   I do not understand why there are blank cells in "Testing applies?" and "Testing FI-Lab?"
  *   I see that IoT failed to do their part. This is the WPL's fault?
  *   I am not reading all the tables, I simply do not have the time. Whatever the partners provided, it is their responsibility.

I'd advocate to express clearly what is missing and why it is missing. I.e. "The WPL of X failed to provide the data we needed for this doc" "Partner X failed to provide info of the test on CC", etc. Ensure that you have evidences in each case to avoid complaints.

Once it is internally reviewed and you have the ok from this thread, if you agree I would also circulate the doc to the general mailing list prior to delivery.

Best regards,

Miguel




El 06/02/2015 a las 2:34, stefano de panfilis escribió:
dear miguel and manuel,

attached the d10.5.3 for your validation and eventual submission.
please note that not always fiware shall be written without the hyphen, becouse somtimes it refers to the fi-ware project and this case shall be left with the hyphen as the name of the project did not change (and actually cannot). please remember that sometimes we must tell also what the project did ... ;-)

anyway, to avoid confusion, i added always the word "project" when meaning it after "fi-ware".
thsi si particularly tru for deliverables such d10.2.3 and d10.5.3 which are not public.

for this deliverable again a "political" decision is needed as many contributions are missing.
partners have been warned many times.

btw, still waiting for the kind help of manuel on the "product" and "service" defintions for the final submission of d10.2.3.

ciao,
stefano

--
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy

tel (direct): +39-06-8759-4253
tel (secr.): +39-068307-4513
fax: +39-068307-4200
cell: +39-335-7542-567
skype: depa01
twitter: @depa01



--

Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

----------------------------------------------------------------------
     _/          _/_/                     Miguel Carrillo Pacheco
    _/   _/     _/  _/   Telefónica       Distrito Telefónica
   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 9
  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N
 _/          _/_/                         28050 Madrid (Spain)
                                          Tel:  (+34) 91 483 26 77

                         e-mail: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

Follow FIWARE on the net

        Website:  http://www.fiware.org
        Facebook: https://www.facebook.com/eu.fiware
        Twitter:  http://twitter.com/Fiware
        LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-testbed/attachments/20150206/86a9def4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gieaijhg.png
Type: image/png
Size: 49940 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-testbed/attachments/20150206/86a9def4/attachment.png>


More information about the Fiware-testbed mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy