[Fiware-security] TR: "D2.3 FI-WARE Architecture" - Placeholder in Security WIKI READY

[BISSON Pascal]

Many thanks Francesco !
That's already great work to achieve at the level of this team and with other chapters :!
Good material also to use/show at plenary session Wednesday in complement the  slides you will prepare.

Best Regards,
Pascal

-----Message d'origine-----
De : DI CERBO, Francesco [mailto:francesco.di.cerbo at sap.com] 
Envoyé : jeudi 19 janvier 2012 18:44
À : BISSON Pascal; TRABELSI, Slim; Seidl, Robert (NSN - DE/Munich); Antonio Garcia Vazquez
Cc : Pascal Bisson(pascal.bisson at noos.fr); fiware-security at lists.fi-ware.eu
Objet : RE: [Fiware-security] TR: "D2.3 FI-WARE Architecture" - Placeholder in Security WIKI READY

Sorry, I forgot the link!

https://forge.fi-ware.eu/plugins/mediawiki/wiki/security/index.php/FIWARE.OpenSpecification.Security.Optional_Security_Enablers

best,

francesco

> -----Original Message-----
> From: DI CERBO, Francesco
> Sent: jeudi 19 janvier 2012 18:35
> To: 'BISSON Pascal'; TRABELSI, Slim; 'Seidl, Robert (NSN - DE/Munich)';
> 'Antonio Garcia Vazquez'
> Cc: 'Pascal Bisson(pascal.bisson at noos.fr)'; 'fiware-security at lists.fi-ware.eu'
> Subject: RE: [Fiware-security] TR: "D2.3 FI-WARE Architecture" - Placeholder
> in Security WIKI READY
> 
> Hello Pascal,
> 
> Please find the consolidated version of information available for  T8.4. For our
> asset, I also uploaded a block diagram, while I am sending a request to the
> other asset owners to do the same.
> 
> Best regards,
> 
> Francesco
> 
> > -----Original Message-----
> > From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-
> > bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal
> > Sent: jeudi 19 janvier 2012 12:14
> > To: TRABELSI, Slim; Seidl, Robert (NSN - DE/Munich); Antonio Garcia
> Vazquez
> > Cc: Pascal Bisson(pascal.bisson at noos.fr); fiware-security at lists.fi-ware.eu
> > Subject: [Fiware-security] TR: "D2.3 FI-WARE Architecture" - Placeholder in
> > Security WIKI READY
> >
> > Dear Slim, Francesco, Robert and Antonio,
> >
> > I'm forwarding you this email in order for you as Task leads and GE owners
> to
> > upload asap on the private Wiki the information you have produced so far
> for
> > M9 deliverable (D2.3) in order to share with other ATs and get feedback
> from
> > our CA (Juanjo).
> >
> > To give it a start I uploaded there already the information coming from T8.1
> > (Daniel to check and complete), also information provided by Antonio on
> T8.3
> > (Antonio please check and complete)
> >
> > Robert/Gabor please do the same for what concerns T8.2 core GEs
> > Slim/Francesco please do the same for T8.2 Optional GEs
> >
> > This as to be completed the sooner the better for Juanjo to have a look and
> > provide us with feedback. This in order to better to align to what Juanjo is
> > expecting us to deliver (for M9 deliverable - a bit critical since due end of
> > January !) and also benchmark us compare to others (what the others did
> > based as a follow-up of Juanjo's email on the topic)
> >
> > Counting on you and many thanks for your cooperation and support !
> >
> >
> > Hope what with feedback we will get from our CA we could align and go full
> > speed !!!
> >
> >
> > Best Regards,
> > Pascal
> >
> >
> >
> >
> > -----Message d'origine-----
> > De : CARLOS RALLI UCENDO [mailto:ralli at tid.es]
> > Envoyé : mercredi 18 janvier 2012 23:05
> > À : BISSON Pascal; GIDOIN Daniel
> > Cc : JUAN JOSE HIERRO SUREDA
> > Objet : "D2.3 FI-WARE Architecture" - Placeholder in Security WIKI READY
> >
> >
> > Dear Pascal, Daniel,
> >
> > In order to start providing your contributions to the above mentioned
> > deliverable, we have just created some placeholders or anchor points in
> the
> > Security WIKI.
> >  https://forge.fi-ware.eu/plugins/mediawiki/wiki/security/
> >    Do not forget to log in with usual user in the forge, prior to access.
> >    The first link points to the deliverables we are contributing, where you will
> > find D2.3 and afterwards the Sections to be completed.
> >
> > Please, let me recall here Juanjo's e-mail on establishing some guidelines
> and
> > providing a reference example based on CORBA specs.
> >
> > Should you have any question/suggestion, please let me know.
> > Best regards,
> > -------------------------------------------------------------------------------------------
> ---
> > --------------------------
> > Carlos Ralli Ucendo (ralli at tid.es<mailto:ralli at tid.es>)
> > Cell: +34696923588
> > Twitter: @carlosralli
> > Telefónica I+D SAU
> > Madrid, Spain
> > -------------------------------------------------------------------------------------------
> ---
> > --------------------------
> > Follow FI-WARE project (Future Internet Services Core Platform):
> > Website:  http://www.fi-ware.eu
> > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
> > Twitter: @fiware
> > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
> > -------------------------------------------------------------------------------------------
> ---
> > --------------------------
> >
> >
> > -------- Original Message --------
> > Subject:        IMPORTANT: Approach for Architecture Specification
> Deliverable
> > Date:   Wed, 30 Nov 2011 15:38:42 +0100
> > From:   Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es>
> > To:     fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>
> > <fiware-wpl at lists.fi-ware.eu><mailto:fiware-wpl at lists.fi-ware.eu>,
> fiware-
> > wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> <fiware-
> > wpa at lists.fi-ware.eu><mailto:fiware-wpa at lists.fi-ware.eu>
> >
> >
> > Hi all,
> >
> >   As you know, we have to start working on the Architecture Specifications,
> > which is one of the deliverables that is due in month 9, that is, end of
> > January.
> >
> >   My intention is to adopt a pragmatic approach, trying to generate
> something
> > that can be integrated as part of the GE Open Specifications that we have
> to
> > produce by month 12.
> >
> >   My vision is that all GE Open Specifications should start with a chapter
> > where an overview of the envisioned Architecture for the GE is described.
> > While style would be narrative, the description should be enough concrete,
> > i.e., formulated over actual data type, interface and operation names and
> > elaborating on the base interaction scenarios involving the different
> entities
> > exporting the defined interfaces.   Then, after that chapter, the detailed
> > specification of all data types and interfaces with their operations, are
> > provided (this including signature of operations and accurate description of
> > expected behaviour linked to operations)
> >
> >   Then, the Architecture Specification deliverable would be just the result of
> > developing this overview chapter.
> >
> >   But nothing better than an example, so let me use one taken from OMG's
> > set of CORBA Services Specifications.  Along my many years involved in
> > different standardization efforts, I have found that OMG CORBA Service
> > specs are rather comprehensive and close to what programmers (our
> > ultimate customers!) love to see.
> >
> >   Please find enclosed the CORBA Event Service Specifications.   What I
> would
> > then select as the Architecture description are the contents of the
> following
> > sections:
> >
> >  *   The whole chapter 1
> >  *   Section 2.2 and 2.4 (which some people may have argued should have
> > been included in chapter 1 :-)
> >
> >   Note that anyone who reads the mentioned sections would get a CLEAR
> > picture of what is the Architecture of the service and what are going to be
> > the entities and interfaces/operations that will be supported in a compliant
> > implementation.   The conceptual and programming model would be also
> > rather clear from a programmer's perspective.   Therefore, rather valuable
> > information for an application developer perspective which is what really
> > should matter to us.    A side benefit is that what will remain as pending
> > regarding GE Open Specifications will be less, that is, the detailed
> > specification of data types and interfaces/operations.
> >
> >   One thing that we will have to define is the set of conventions that we
> > should all follow whenever we need to draw any figure, like figures 1-x or
> 2-
> > x.   For this, Thomas and me will come soon to you with a proposal in short
> > time.
> >
> >   Please take your time to analyze this carefully and formulate any question
> > you may have.
> >
> >   From now on, I assume that you will start planning activities in Sprint 2 and
> 3
> > dealing with development of these specifications within each of your
> > chapters.   This may well take the form of Work Items in the tracker.
> >
> >   Best regards,
> >
> > -- Juanjo
> >
> >
> >
> > 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