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 attributeDomainName seem to be the same (see //{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/8a3a6969/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Ngsi10.xsd Type: text/xml Size: 9881 bytes Desc: Ngsi10.xsd URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120206/8a3a6969/attachment.xml>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy