Hi Denes,
My understanding was that we introduce the "ContextAttributeReponse" in analogy with the existing "ContextElementResponse". This structure is used several times in the binding.
Best
Tobias
From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com]
Sent: Donnerstag, 10. Mai 2012 13:56
To: Salvatore Longo; Tobias Jacobs
Cc: fabian.tschirschnitz at sap.com; fiware-ngsi at lists.fi-ware.eu
Subject: RE: GET for context Attribute
I mean you meant
<queryContextAttributeResponse>
<contextAttributeList>
<contextAttribute>
....
</contextAttribute>
<contextAttribute>
....
</contextAttribute>
</contextAttributeList>
<statusCode>
....
</statusCode>
</queryContextAttributeResponse>
From: ext Salvatore Longo [mailto:Salvatore.Longo at neclab.eu]<mailto:[mailto:Salvatore.Longo at neclab.eu]>
Sent: Thursday, May 10, 2012 1:53 PM
To: Bisztray, Denes (NSN - HU/Budapest); Tobias Jacobs
Cc: fabian.tschirschnitz at sap.com<mailto:fabian.tschirschnitz at sap.com>; fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu>
Subject: RE: GET for context Attribute
OK, I update the XmlSchema and also the example queryConytexAttributeReponse with the new version.
Example:
<contextAttributeResponse>
<contextAttributeList>
<contextAttribute>
....
</contextAttribute>
<contextAttribute>
....
</contextAttribute>
</contextAttributeList>
<statusCode>
....
</statusCode>
</contextAttributeResponse>
BR,
- Salvatore
________________________________
Salvatore Longo
Software Engineer
NEC Europe Ltd.
Kurfürsten-Anlage 36
D-69115 Heidelberg
Tel. +49/(0) 62 21/43 42 - 246
Fax. +49/(0) 62 21/43 42 - 115
E-Mail: Salvatore.longo at neclab.eu<mailto:Salvatore.longo at neclab.eu>
NEC Europe Limited
Registered Office: NEC House,
1 Victoria Road, London W3 6BL
Registered in England 2832014
________________________________
From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com]
Sent: Donnerstag, 10. Mai 2012 13:12
To: Tobias Jacobs
Cc: Salvatore Longo; fabian.tschirschnitz at sap.com<mailto:fabian.tschirschnitz at sap.com>; fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu>
Subject: RE: GET for context Attribute
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]<mailto:[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<mailto:fiware-iot at lists.fi-ware.eu>; Tschirschnitz, Fabian (fabian.tschirschnitz at sap.com<mailto: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/c18908f6/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy