[Fiware-data] Minutes of weekly followup confcall 11-06-10

[Moltchanov Boris]

*Starting from 4 point* that will take very short time (I'm in a short time-constraints now). the rest is next week:

*Problem statement*: we need a shared SVN to join all our works into the same result - document and avoid trashing with multiple uncontrolled versions.

*Possible solution* and steps:
- SVN (with control versioning solution);
- template of document (deliverables) are ready and published in SVN (with all styles and fonts already provided);
1. one (leader of deliverable or first initiative contributor) "instantiate" a document (deliverable) in its first (draft) version, that even might be empty but has the reference name, and assign to this a reasonable name (index or name or both of the document/deliverable);
2. a contributor (may act in parallel) download that document into local filesystem and perform changes regarding their respective sections (might be a new section or tracked review of an existing section);
3. once the contribution is ready the contributor lock the file, download the current already locked version, and insert his/her insertion or changes. This operation shall be relatively fast (question of minutes) in order to do not block the document more then necessarily for insertion;
4. [*optional*, and I hope this operation would be avoided] if contributor discover that the downloaded version is different from the one downloaded before starting the integration, a "merge" function of the MS World might be used (not always successful because only MS (probably) knows what happens insider their systems;
5. after the insertion or changes are done the contributor upload the file to the server under the same name and unlock the file.

Some subversioning systems combines the download/lock and upload/unlock in the one operation respectively edit and release.

In this case any user shall have its unique name within SVN and it would be really nice if the same name is used also for MS Word tracking inside the file in case of editing.

Any document deliverable *MUST* have its responsible Editor who is leader of that document, solve race condition and eventual integration issues asking required actions directly to tracked (in SVN and in the document body) contributors.

I hope this would help to our cooperation. If I missed something please integrate, improve, change or constructively suggest.

Best Regards,
Boris

From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro
Sent: Friday, June 10, 2011 7:27 PM
To: fiware-data at lists.fi-ware.eu
Subject: [Fiware-data] Minutes of weekly followup confcall 11-06-10

Hi,

  Quick and dirty, but hopefully clear and useful :-)

  Cheers,

-- Juanjo


Minutes:

During the follow-up confcall we reviewed the status of contributions to the Context/Data
Management Chapter in the FI-WARE High-level Description (product vision) deliverable.


1. Contribution by Siemen

  Uploaded on the server.

  Action on Juanjo to review whether it is now consistent with the conclusions from our
debate on the Publish/Subscribe GE and its relationship to the Query Access GE.

2. Contributions regarding Management of Data semantics

  ATOS has updated their contribution and uploaded it on the server.

  Telecom Italia has also uploaded a contribution on the matter.

  We will setup an initial confcall regarding discussion on overall approach regarding
Semantic Technology.   First confcall on monday 13th, 13:30 pm and then there will be an
additional one on tuesday 14 starting at 18:30.   Juanjo to send the dial-in and webex
details.


3. Contribution on CEP by IBM

  Action on Juanjo to review new draft produced by Guy.  To send comments before sunday
(working day in Israel)

  Action on All to review initial definition of Data vs Event provided IBM in their
contribution and send comments to the list.     In this respect, we need a definition of
three concepts:

- data element (data record)
- event
- context element

  The structure of data/event/context elements has to be common to several GEs, at least
in respect to how such elements are going to be passed from one GE to another and to final
applications.   In this respect:

- We should be able to subscribe to and notify plain data through the Publish/Subscribe
   Broker, not just context elements.  Same for events.
- We should be able to connect the output of the CEP GE to the Publish/Subscribe Broker GE
   and viceversa

  Action: Juanjo to make a proposal trying to start from Guy's proposal and the OMA
model and send it to the list before sunday or sunday morning.   We'll setup a confcall on
Wednesday and in the meantime let's discuss over the email.   Juanjo to make a doodle to
find the right time.

  Juanjo: the OMA Publish/Subscribe Service may give some hints on a model that
accomodates the three.

  Boris: agreed.

  Due to this linkage with the OMA model, we seamlessly continue addressing status of the
description of the Publish/Subscribe Broker GE.

4. Contribution on the Publish/Subscribe Broker GE

  General agreement in that it would be feasible to define the interfaces and entities that would
be supported in the FI-WARE Publish/Subscribe Broker GE along the lines of the OMA
Model.   But probably we may have to deal with particularities when dealing with the
details of defining types linked to arguments to operation requests/responses in FI-WARE
if we want to address the requirements mentioned in the previous point.

  General agreement that we should try to be as closer to the OMA spec as possible, trying
to keep as much compliance as possible.   Ideally, an implementation of the Publish/Subscribe
Broker in compliance with the FI-WARE spec should be able to interact with client programs
making use of the mandatory parts of OMA.   We may be more relaxed and not require compliance
with non-mandatory parts of the OMA specs (even if that means that we would not be able
to claim compliance with OMA, but what really matters is that a relevant % of client programs
that were able to work against OMA-compliant servers can port to use a FI-WARE-compliant
implementation without not too much burden).    Once we get a solid and tested spec, we
would determine how to fastrack its adoption in OMA (as an update o the existing spec ?
probably difficult ... as a variant of the existing one might be reasonable)

  Boris will start re-writing of Publish/Subscribe GE asap.  Goal to get it done for review
in following weekly confcall.


4. AOB

  Boris to send proposal on how to manage integration of contributions through SVN.


________________________________
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
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:00000000000000000000000000000001 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-data/attachments/20110610/53a222c5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia.jpg
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110610/53a222c5/attachment.jpg>