No problem, simply that I implemented using a QueryContextAttributeResponse structure with ContextResponseList consisting of ContextElementResponse elements. And a Statuscode typed ErrorCode field. Can you update the doc then? Also Salvatore, can you modify the test xsd? Best, Dénes From: ext Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Thursday, May 10, 2012 1:04 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Salvatore Longo; fiware-iot at lists.fi-ware.eu; Tschirschnitz, Fabian (fabian.tschirschnitz at sap.com) Subject: RE: GET for context Attribute Hi Denes, There was as inconsistency between the binding document and the xsd. In the xsd a ContextAttributeResponse only contained a single attribute (see the email sent by Fabian last week's Wednesday). I changed the binding document accordingly, but I think that you are right, the ContextAttributeResponse should contain a list of attributes (as there might be multiple value instances), so I should rather have changed the xsd. If you agree with that view, I am happy correct this error. Sorry for the trouble! Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Donnerstag, 10. Mai 2012 12:44 To: Tobias Jacobs Cc: Salvatore Longo Subject: GET for context Attribute Hi Tobias, There seems to be a huge error int he NGSI-10 document! The GET at Attribute of individual context entity returns only a single ContextAttribute! It supposed to return a queryContextAttributeResponse, with a contextAttributeList!! Can you check who edited this out of the document? Currently this is simply wrong! Best, Dénes -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120510/26d0430d/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy