[Fiware-ngsi] Questions regarding NGSI-10 RESTful binding

[Tobias Jacobs]

Dear Fabian, dear Armin,

About the resource paths for Attributes / Attribute Domains:
The sub-resources of //{serverRoot}/NGSI10/contextElements and  //{serverRoot}/NGSI10/contextElementTypes/ are there to enable simple query operations. The query operation can be found on page 18 of the NGSI-10 specs (http://www.openmobilealliance.org/Technical/release_program/docs/CopyrightClick.aspx?pck=NGSI&file=V1_0-20101207-C/OMA-TS-NGSI_Context_Management-V1_0-20100803-C.pdf).
The AttributeList is one parameter of the query operation, and each attribute in that list is a string that can either denote an individual attribute or the name of domain. In other words, the query does not distinguish between attributes and domains, and so I believe that there is  no need to introduce a distinction in the RESTful binding. The Context Management System knows if the resource corresponds to an individual attribute or a domain and can answer the query accordingly.

Best regards
Tobias
NEC

From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Zamani Farahani, Armin
Sent: Montag, 6. Februar 2012 13:03
To: fiware-ngsi at lists.fi-ware.eu
Cc: Tschirschnitz, Fabian
Subject: [Fiware-ngsi] Questions regarding NGSI-10 RESTful binding

Hi all,

while working on a first implementation of a test client for the NGSI-10 REST interface we found some issues in the specification that we want to share with you:

We implemented our Java classes based on the XML schema file that was part of the WSDL Documentation (see mail sent on 5th December 2011 of Laurence Dupont). We found two issues that had to be improved in the XML schema file. See comments in the attached schema file.

In the draft for the RESTful binding of NGSI-10 the routes for attributeName and attribute DomainNa ee //{serverRoot}/NGSI10/contextElements/{contextElementID} and //{serverRoot}/NGSI10/contextElementTypes/{typeName}).
How should requests for attributes and attribute domains be distinguished in an implemented version of the REST bindings? Alternatively we thought of adding a new path segment for attribute domain requests, e.g. (//{serverRoot}/NGSI10/contextElements/{contextElementID}/domain/{attributeDomainName}).

Best regards,

Fabian Tschirschnitz and Armin Zamani
SAP Research
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120206/3fe8a44e/attachment.html>