Hi Juanjo, I am in client meetings all day - I won¹t be able to look at this until about 3pm so I won¹t make the 4pm deadline. I¹ll do it as soon as I can after I get out of meetings. Sorry but I needed this yesterday to get it ready for you by today. Best, Cathy -- Dr Catherine Mulligan Research Fellow Associate Director, Imperial College Centre for Cryptocurrency Research and Engineering OASC Standardisation // oascities.org <http://oascities.org/> Director and Co-Founder of Contextualised // http://www.contextualised.com/ + 44 753 888 7477 c.mulligan at imperial.ac.uk On 10/08/2016, 08:19, "fiware-oasc-etsi-bounces at lists.fiware.org on behalf of Juanjo Hierro" <fiware-oasc-etsi-bounces at lists.fiware.org on behalf of juanjose.hierro at telefonica.com> wrote: > > It would be nice to send to ETSI the draft today, sometime after >16:00. Please try to review the text quickly and bring comments >earlier so that we can make it. > > Cheers! > >-- Juanjo > > >On 10/08/16 09:16, Juanjo Hierro wrote: >> Dear all, >> >> Please find attached the version of ToR that I believe would be fine >> for submission to ETSI. >> >> Thanks to Lindsay for his contributions. I have finalized the ToR >> draft working on the version he distributed yesterday. I added his >> input on liaisons. I also incorporated the whole text of the action >> established in the EC 2016 rolling Plan on ICT Standardization as >> requested by Cathy. I also incorporate some clarifications about >> rules that would only apply to physical meetings (not virtual) like >> distributing the agenda 30 days in advance (this is non-practical in >> virtual confcalls which may be run more often). I have clarified >> that Reports and Specifications will only be approved in physical >> meetings which I believe is acceptable. I wonder whether you would >> agree on that. I have also revised the part of Liasions with FIWARE >> and give it some formatting here and there. >> >> One important point that I have added is the statement that Group >> Specifications will be public and royalty-free (check Scope section, >> phase 2). This was explicit in the very original drafts but after so >> many changes I found it got diluted and this was relevant. Note that >> such statement would apply not only to the CIM-API but the rest of >> specs we aim at producing (including information models). I guess we >> all agree on that. >> >> I have added Linsay to the FIWARE OASC mailing list to keep the more >> general discussion also under the list. >> >> The final version to be submitted to the ETSI team will have all >> those comments we have accepted already as clean revised text, so only >> our comments on their comments will be highlighted. However, I have >> kept their comments also highlighted in the version I send now for >> your convenience. >> >> Cheers, >> >> -- Juanjo >> >> ______________________________________________________ >> >> Coordinator and Chief Architect, FIWARE platform >> IoT Unit, Telefónica >> >> email: 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 >_______________________________________________ >Fiware-oasc-etsi mailing list >Fiware-oasc-etsi at lists.fiware.org >https://lists.fiware.org/listinfo/fiware-oasc-etsi
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy