[Fiware-ngsi] voting for subscribeContextRequest option

[Haller, Stephan]

All,

My vote goes to the flexible approach.

I would recommend though that the response body should contain some "warning" if the attribute doesn't exist.
It is then up to the app if it wants to react (change/delete the subscription) or not.

Regards,
-Stephan


From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest)
Sent: Donnerstag, 22. März 2012 10:25
To: fiware-ngsi at lists.fi-ware.eu
Subject: [Fiware-ngsi] voting for subscribeContextRequest option


Dear All,

I would like to set up a vote for one of the issues having been discussed in the last NGSI technical meeting. It is about 5.4.2.1 subscribeContextRequest and the question is whether we allow (flexible approach) to subscribe for attributes that still do not exist or not (return an error - conservative approach).

Please take a look at the minutes (pages 6, 7, https://forge.fi-ware.eu/docman/view.php/11/884/NGSI-Minutes-Telco-20032012.docx) for the discussions on the topic, make up your mind and cast your vote per partner by EOB 23.03.2012.

If no consensus is reached, I guess we will need to take a majority approach.

Thanks & Br,

Lorant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120322/c7e48a93/attachment.html>