[Fiware-chapter-architects] [Fiware-chapter-leaders] How to add bundles to the wiki

[Davide Dalle Carbonare]

Dear Javier,
  before to proceed with the implementation, we need to agree on the design
described in the document circulated by Stefano.

At the end we will have an interface, in the Catalogue, for editing bundles
entries like the one already available for GEis.

BR
Davide

2014-10-21 17:25 GMT+02:00 Javier Soriano (FI-UPM) <jsoriano at fi.upm.es>:

> Davide,
>
> There is another AP related to this one: how to publish in the catalog the
> template sent by Stefano once you have fulfilled it with the information
> regarding one particular bundle.
>
> I have sent to Stefano the template filled with the information of the two
> bundles we haver created in wp3 /Apps chapter. But I am not sure whether
> this is what is expected or not. Obviously we cannot update the catalog
> with this information until there is a new entry for the bundle. Any clue
> about this?
>
> Best regards,
> Javier
>
> 2014-10-21 17:11 GMT+02:00 Davide Dalle Carbonare <
> davide.dallecarbonare at eng.it>:
>
>> Dear Miguel,
>>   are we sure that the bundles we have now (and will have in the future)
>> are all built using GEs from the same Chapter?
>>
>> BR
>> Davide
>>
>> 2014-10-21 16:54 GMT+02:00 MIGUEL CARRILLO PACHECO <
>> miguel.carrillopacheco at telefonica.com>:
>>
>>>  Dear all,
>>>
>>> One of the pending APs on me from yesterday's meeting is to provide
>>> guidelines to include the bundles in the wiki. I will do it with one
>>> example.
>>>
>>> Let us use the bundle in Data as an example.
>>>
>>> *1)** Where *
>>> Under Materializing, at the end of the page,
>>> http://wiki.fi-ware.org/Materializing_Data/Context_Management_in_FI-WARE
>>> .
>>>
>>> *2) Structure*
>>> Wwe add a section called "<bundle name>(bundle)" as though it was one
>>> more GE.
>>>
>>> We also add just one single subsection ("*Bundle guides*")
>>>
>>> It will look like this in the wiki TOC
>>>
>>>
>>>  *3) Contents*
>>> Take this as a model, modifying it as needed in each WP.
>>>
>>>
>>>
>>> BR
>>>
>>> Miguel
>>>
>>> --
>>>
>>> Please update your address book with my new e-mail address: 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
>>>
>>> Follow FI-WARE on the net
>>>
>>> 	Website:  http://www.fi-ware.org
>>> 	Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
>>> 	Twitter:  http://twitter.com/Fiware
>>> 	LinkedIn: http://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
>>>
>>> _______________________________________________
>>> Fiware-chapter-leaders mailing list
>>> Fiware-chapter-leaders at lists.fi-ware.org
>>> https://lists.fi-ware.org/listinfo/fiware-chapter-leaders
>>>
>>>
>>
>> _______________________________________________
>> Fiware-chapter-architects mailing list
>> Fiware-chapter-architects at lists.fi-ware.org
>> https://lists.fi-ware.org/listinfo/fiware-chapter-architects
>>
>>
>
>
> --
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20141022/e715c90a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bcffeaee.png
Type: image/png
Size: 24090 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20141022/e715c90a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cfhhhedg.png
Type: image/png
Size: 7118 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20141022/e715c90a/attachment-0001.png>