[Fiware-apps] [Fiware-wpl] Update on State of the Art deliverable (action required)

Heller, Markus markus.heller at sap.com
Wed Jun 12 15:16:21 CEST 2013


Hi Pablo, Javier, Koen, Joaquin, SOTA contributors,

We together are the SOTA contributors if I am not mistaken, I copy it to FIware List if I forgot a colleague....

Sorry If I should have caused confusion (thanks to Miguel to point me to this error): I used "automatic numbering" wrongly here, "automatic sorting" is better.

I wanted to ask you to do your parts using Micrsoft citation/reference stuff and I hope that we can use the _automatic_ SORTING  (when I merge things later from your inputs) so that I need not do that manually.
Please simply obey the citation style / guidelines that _Miguel_ describes / demands in his mail attached below in the mail thread.
References are _not_ to be numbered (e.g. 1,2...) but they follow another style (--> see DOW)....

@Pablo, Javier, Koen, Joaquin: Can you please confirm to me by e-mail that you will do the task so that I am sure on this?

Best wishes
Markus


From: markus.heller at sap.com
Sent: Mittwoch, 12. Juni 2013 09:46
To: 'fiware-apps at lists.fi-ware.eu'
Cc: 'Sandfuchs, Thorsten (thorsten.sandfuchs at sap.com)'
Subject: RE: [Fiware-wpl] Update on State of the Art deliverable (action required)

Dear WP3

To emphasize, the deadline is Monday next week, we have to deliver on time, so please start your tasks and send to me as early as you can.
As I will be on the review until Friday, I would like to rely on you to be active here since we have not much time to try it again.

To be clear:
- You have to change the references (e.g. "[xxx]") WITHIN the text and
- the format of the referecens in the "REFERENCS" table to comply with the citation style from DOW.

You might send a snippet to the list if you are in doubt to have done it right, so that the other can help you here.
Please also send on this list if you see that the approach taken does not work for all inputs isolated taken and them combined so that we can choose another way.

Best wishes
Markus


From: markus.heller at sap.com<mailto:markus.heller at sap.com>
Sent: Mittwoch, 12. Juni 2013 01:00
To: 'fiware-apps at lists.fi-ware.eu'
Subject: FW: [Fiware-wpl] Update on State of the Art deliverable (action required)

Dear WP3

We have to follow Miguels Guidelines for SOTA Deliverable. We have to update the format of the references table in our SOTA part for Apps.

Please note that we have to use the attached WOPRD Format from Miguel

I propose (hope it works):

1)      Please start with the activity: Make a copy of the DOC, then create/update with guideline below ("use convention from the DOW") the references in YOUR PART properly leading to a single table where only your references are now correctly formatted.

2)      Important: Please make sure to use the Microsoft WORD automatic (!) numbering for your references, so that when I combine, all of them are automatically numbered. If you fail to do so, I need to send it back to you to correct.

3)      Send me your contribution update.

4)      I will consolidate this and submit.

If ýou have questions on this, please ask.

(I need to deliver this Deadline: Tuesday, 18th of June, so deadline for you is one day earlier, so please obey... )

Your Deadline: Monday 17.06.2013 EOB

Best wishes
Markus




From: fiware-wpl-bounces at lists.fi-ware.eu<mailto:fiware-wpl-bounces at lists.fi-ware.eu> [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo
Sent: Montag, 10. Juni 2013 16:11
To: fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>
Subject: [Fiware-wpl] Update on State of the Art deliverable (action required)

Dear all,

This message is to update you on the status of this deliverable and also to allow direct forwarding to your teams if you like( you are very busy these days). @WPL: be aware that you have to unify the contributions of the partners in your WP.

The last contribution came extremely late (last tuesday) so delivering now could even be backfiring:

  *   If we deliver, they will complain about delivering 3-4 days before the review (this will irritate them) and also that the document could be seen as a muddle of different contributions put together with no accord (the references section is largely different across WPs)
  *   If we do not deliver, they will complain about not having the deliverable
Assuming that they will complain anyway (and they will be right in doing so), let us get this properly done. After putting all your contributions together and reformatting all the whole lot, it became apparent that each chapter was using a different approach. Theoretically we should have followed the convention from the DoW, that is the one that I circulated in the initial "skeleton" I sent. It is essential to unify it.

Things to do/change:

  *   Some have a table at the end, some have more than a table (one at the end of each intra-WP section). We need a single unified table at the end of each chapter.
  *   Some follow the original convention, some other write [1], [2] .... We want the original one.
  *   Please make sure that the contributions are in alphabetical order (sorted by reference code)
In summary:

  *   Apps, Cloud and Security to reformat their references (not numbers) and to add a single table at the end (take  the table in Data as the reference). Please use the table format (same as Data)
  *   IoT to add such a table
  *   I2ND do not follow it 100% but we can take it as it is. Just convert it into a table (now it is just plain text if I am right).
Please use the attached document as the starting point to do this work. It took hours to reformat and we cannot lose all that work.

Let us prevent the usual iterations. The way to do it is to get it right from the start. These are the checkpoints would cause a rejection so please avoid them and all of us will make good use of our time:

  *   Contributions not using the attached doc as starting point
  *   Contributions not following the naming convention  (also the format - capital letters, table format, etc.)
  *   Contributions with more than one table
  *   Contributions not in alphabetical order
  *   Mismatches between the references in the text  and the references table
Deadline: Tuesday, 18th of June

It is the time to start applying the new rules that we discussed in out latest WPL/WPA call. So please note that if a given WPL sends me a contribution, it means that he has personally checked that the above list of checkpoints is met.

Best regards,

Miguel

--

----------------------------------------------------------------------

     _/          _/_/                     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: mcp at tid.es<mailto:mcp at tid.es>



Follow FI-WARE on the net



        Website:  http://www.fi-ware.eu

        Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

        Twitter:  http://twitter.com/Fiware

        LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932

----------------------------------------------------------------------

________________________________

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-apps/attachments/20130612/a495af88/attachment.html>


More information about the Old-Fiware-apps mailing list

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