[Fiware-oasc-etsi] Revised ToR with section on compatibility with OneM2M

[Mulligan, Catherine E A]

Hi juanjo,

Thanks for your comments.  Two points:

1) Telefonica is a member of ETSI.  You don't need to pay.  My concern is OASC and others being able to attend :)
2) as I have said multiple times, I support the ISG being used for things other than smart cities, indeed I have significant amounts of industrial information that could usefully be put in (I am taking those to other SDO instead however).  I am concerned with the conflation of OASC = FIWARE.  It is not a direct translation.... it is one component of OASC.  There are other technical architectures that can be used.  Oasc is for all members, not just those that use FIWARE.

Best,
Cathy

Skaffa Outlook för Android<https://aka.ms/ghei36>



On Thu, May 26, 2016 at 10:54 PM -0700, "Juanjo Hierro" <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>> wrote:


On 26/05/16 12:35, Mulligan, Catherine E A wrote:

Hi All,

Many thanks for this – I have reviewed the text and have two main questions:


  1.  The costs for attending the ISG meetings have been removed from the relevant section.  What is the reason for this?  Can we please put it back in – my concern is that not specifying the costs will lead to people being “costed” out of attending who really should be there in order to ensure the ISG is effective.

  I don't recall having dropped this but I hope someone else can recall.   On the other hand, sometimes this kind of costs become hard to justify in companies with lot of admin burocreacies (like Telefónica :-).   For instance, I tell you that paying the typical fee for attending some ICT events organized by the EC have always been a nightmare.  We have to justify them under "training" budget internally and only after a cumbersome administrative process.

  Could we agree in something like fees will be paid by organizations attending the meetings unless they have proven active contribution to agenda items in at least two previous meetings or something like that?


  1.  Again, there has been a significant reduction in the relationship to OASC.  The Standardisation Rolling plan is clear – OASC is the reason for the creation of the ISG.  While I see no reason that it should not also cover other areas as well and fully support that it does, the role of OASC needs to be clearly stated.  The text from the standardisation rolling plan seems to have been edited to remove OASC.  It needs to be put back in.

  I have reviewed the text again and sincerely, I don't see the point:

  *   The text that is quoted when elaborating on the need for context information management standards (first subsection of the Rationale section) is literally taken from the 2016 Rolling Plan on ICT Standardization.
  *   We clarify that an initial area of focus is Smart Cities and we close the first subsection of the rationale saying "By focusing on the Smart Cities as a first and catalysing domain, this ISG is also intended to fulfil OASC standardization needs"
  *   We elaborate on OASC in a second subsection of the Rationale subsection, highlighting the relevance and giving OASC the right visibility.   We put it ahead of the subsections on impact on Digitising the Industry and the Economy of Data which are highly relevant.
  *   We brought OASC to the title of the ISG, anyways, referring to it as catalyst

  We have reach a good balance (emphasizing the contribution of OASC to the creation of the ISG) and we are reluctant to break it.

  The ETSI industry companies that are pushing for the creation of the ISG wish to apply and push for the adoption of the proposed standards in many different domains, not just Smart Cities.   On the other hand, the EC has already expressed their interest in pushing for the application of results in a wider context, overall digitising the European Industry.   Just consider references to FIWARE in the recent communications regarding the Digital Single Market strategy.

  Please bear this in mind when proposing concrete editorial comments.

  Cheers,

-- Juanjo
Many thanks and best wishes,
Cathy

From: <<mailto:fiware-oasc-etsi-bounces at lists.fiware.org>fiware-oasc-etsi-bounces at lists.fiware.org<mailto:fiware-oasc-etsi-bounces at lists.fiware.org>> on behalf of Franck Le Gall <franck.le-gall at eglobalmark.com<mailto:franck.le-gall at eglobalmark.com>>
Date: Friday, 20 May 2016 at 15:29
To: Juanjo Hierro <<mailto:juanjose.hierro at telefonica.com>juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>>, "Fiware-oasc-etsi at lists.fiware.org<mailto:Fiware-oasc-etsi at lists.fiware.org>" <Fiware-oasc-etsi at lists.fiware.org<mailto:Fiware-oasc-etsi at lists.fiware.org>>
Subject: Re: [Fiware-oasc-etsi] Revised ToR with section on compatibility with OneM2M

Hello

Thanks for the text. I am just landing  back from Seoul so too late to discuss the section wit Omar.

However, we briefly exchanged with Omar on the ISG yesterday. He told not having been consulted that much and in any case, he does not see oneM2M and FIWARE NGSI at the same level as FIWARE provides high level interfaces for data management that oneM2M does not provide. So he does not see one competing with the other but rather complementarity.

I will go through the text.
Kind regards
Franck



De : fiware-oasc-etsi-bounces at lists.fiware.org<mailto:fiware-oasc-etsi-bounces at lists.fiware.org> [mailto:fiware-oasc-etsi-bounces at lists.fiware.org] De la part de Juanjo Hierro
Envoyé : vendredi 20 mai 2016 08:10
À : Fiware-oasc-etsi at lists.fiware.org<mailto:Fiware-oasc-etsi at lists.fiware.org>
Objet : [Fiware-oasc-etsi] Revised ToR with section on compatibility with OneM2M


Dear all,

  Please find enclosed a version of the ToR that includes a new version of section 5 which elaborates on the complementary of the work to be done under the CIM ISG and OneM2M.   The picture shown is very much based on the figure that I draw when I met with Patrick Guillemin and Hermann Brand from ETSI in Nice.   They seemed to feel very comfortable with it, so I went for it.

  Now I'm working on a few paragraphs that would be incorporated in the scope section, elaborating on background info about FIWARE NGSI, as requested by ETSI.

  Franck: I don't know if you are still in Seoul with Omar.   If so, it might not be a bad idea to show the section and gather his feedback.  Note that the ETSI team explained to me that we should not go into much more level of detail.  Goal is to show very clearly how the scope of work do not overlap but is complementary.

  Please try to get it reviewed before Monday noon.   I would like to send it to ETSI and Omar Elloumi, as agreed with the ETSI team, Monday evening.

  Thanks to Carlos for his initial input.

  Cheers,

-- Juanjo



______________________________________________________



Coordinator and Chief Architect, FIWARE platform

IoT Unit, Telefónica



email: juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>

twitter: @JuanjoHierro



You can follow FIWARE at:

  website:  http://www.fiware.org

  twitter:  @FIWARE

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

  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


________________________________

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-oasc-etsi/attachments/20160527/8f60ed1c/attachment.html>