[Fiware-apps] Open Specifications

[Rafael Fernández]

Dear Yosu,

It seems the message took about 7 hours to get our mailbox, but it finally
reached it! :-)

We (UPM) are currently writing the Open Specs of both the Composition
Editor and Composition Execution enablers, but our "interactions" are
taking into account only our focus on application mashup, so it would be
great if you can participate on it.

We think editing the text in the wiki is ok, but you should try to avoid
clicking on the main "edit" link (located in the upper tabs section) since
it edits the whole page and two simultaneous edits will result in a
conflict. Instead, use the other edit links next to every section headers...

Best regards,
Rafa

On Tue, Feb 7, 2012 at 11:32 AM, Yosu Gorroñogoitia <
jesus.gorronogoitia at atosresearch.eu> wrote:

> Dear Marco Ughetti, Rafael Fernández
>
> we are interested in participating in the specification of open
> specifications for Mediator, CompositionEditor and CompositionExecution.
> ¿Could you explain us how do you think we should participate? ¿Editing
> directly the text in the WIKI? ¿Should we have some preliminar
> discussion by email? ¿How can we manage versioning if different
> contributors are working in parallel? ¿How do we get consensus?
>
> Particular questions:
> - Current CompositionEditor is very mash-up oriented, which does not fit
> with our requirements for composition, basically a BPMN 2.0 editor, such
> as Oryx. Can we add our methods/features in the interaction protocol for
> service composition? I am planning just to add very generic service
> composition interactions from the typical task composition using work
> and data flow (i.e. BPMN/BPEL, etc)
>
> - Mediation: current specification is a bit generic, based on proxy. Can
> we add our methods/features in the interaction protocol for data
> mediation?
>
> Kind regards
> Yosu
>
> ------------------------------------------------------------------
> 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-apps mailing list
> Fiware-apps at lists.fi-ware.eu
> http://lists.fi-ware.eu/listinfo/fiware-apps
>



-- 
*Dr. Rafael Fernández*
Dept. Lenguajes y Sistemas Informáticos e Ingeniería de Software
Facultad de Informática - Universidad Politécnica de Madrid
Campus Internacional de Excelencia Montegancedo
28660 - Boadilla del Monte, Madrid
Spain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20120207/2a03a605/attachment.html>