Dear all, Short status report: after we set up that voting procedure concerning the NGSI-9 resource structure (integrating in into NGSI-10 resources or not) we started to work on a first stable version of the NGSI-9 binding. Unfortunately this task moved further and further away from the top of my priority queue, but I am currently heavily trying to catch up. About restrictions: I agree that we need to think about how to do that with XPATH, as it is not clear how exactly this is to be done. Just "applying" the XPATH expression does not work out as far as I understand - because this extracts naked numbers with no xml left. And what we want - as far as I understand - is to get a subset of the results, but still in the normal xml format. About Juanjo's proposal to change the NGSI API section in the wiki: Actually we did not define any changes to the original OMA NGSI spec, only a few refinements of the operation's semantics. Therefore I am not so much in favor of the term "FI-WARE NGSI" - this makes the impression that this is a different API version, although it is functionally equivalent. Best Regards Tobias From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: Dienstag, 3. Juli 2012 16:18 To: Juanjo Hierro Cc: fiware-ngsi at lists.fi-ware.eu Subject: Re: [Fiware-ngsi] WORRIED: No progress in FI-WARE NGSI specs ? Hi Juanjo, right now I'm not 100% sure, based on my last update with our developers, the XPath requests restrictions will be supported by TI's implementation of Pub/Sub GE. Additionally, we will continue support of CQL as the secondary CB interface, as already claimed. Best Regards, Boris From: fiware-ngsi-bounces at lists.fi-ware.eu<mailto:fiware-ngsi-bounces at lists.fi-ware.eu> [mailto:fiware-ngsi-bounces at lists.fi-ware.eu]<mailto:[mailto:fiware-ngsi-bounces at lists.fi-ware.eu]> On Behalf Of Juanjo Hierro Sent: Tuesday, July 03, 2012 1:27 PM To: fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu> Subject: [Fiware-ngsi] WORRIED: No progress in FI-WARE NGSI specs ? Dear colleagues, I would like to share with you my concern/worries about work/progress regarding FI-WARE NGSI. It's been June 6th (almost one month) since I haven't seen any activity on the fiware-ngsi mailing list and this particularly worries me. All we know that the FI-WARE NGSI API is one of the most relevant and therefore critical APIs that will be offered to UC projects. There are two major points for which I would like to receive your feedback: * Status of FI-WARE NGSI-9 specifications: what is the status ? I haven't seen anything since a month ago and, actually, there is no reference to such spec on that part of the wiki where we are publishing the FI-WARE Open Specifications * There is at least one aspect of the FI-WARE NGSI specs that I'm particularly worried that has not been a matter of discussion and it's rather critical IMHO: the way "restrictions" are specified and passed into requests of several operations (discoverContextAvailability, subscribeContextAvailability, queryContext, subscribeContext, updateContextSubscription). According to the OMA specs, such restrictions should be formulated as "strings containing a XPath expression ... evaluated against ContextEntity structures" but ... is this going to be supported by TI's implementation of the Pub/Sub Broker GE ? Shouldn't restrictions based on some language based/derived from the CQL (Context Query Language) be supported as an alternative to XPath ? I would rather appreciate an update regarding the first point and a response to questions formulated as second point ... Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es<http://www.tid.es> email: jhierro at tid.es<mailto:jhierro at tid.es> twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120703/e8d6f78d/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120703/e8d6f78d/attachment.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy