Hi Denes, all, Do you think that we can come to a decision in tomorrow's WP5 phone conference? We might also want to make a plan about how and when to finalize the NGSI-9 binding. Maybe we can make this the first agenda point, so that also people from other WPs have the possibility to take part in the discussion and then leave the call. Best Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Dienstag, 29. Mai 2012 15:03 To: Tobias Jacobs; fiware-ngsi at lists.fi-ware.eu Subject: RE: [Fiware-ngsi] FW: NGSI - 9 Dear All, As a generic answer, whatever the outcome of this decision will be, NSN is happy to implement it. However to give my to cents, I'd go strongly towards the one resource tree approach for two reasons: 1. Simpler indeed. A generic developer may get confused on the creation of the same resource structure twice 2. The various HTTP verbs may not collide as dedicated subresources can be introduced. The resource structure is just convenience after all, we can change it the way we like. And the non-convenience methods will not collide as they are different. Best, Dénes From: fiware-ngsi-bounces at lists.fi-ware.eu<mailto:fiware-ngsi-bounces at lists.fi-ware.eu> [mailto:fiware-ngsi-bounces at lists.fi-ware.eu]<mailto:[mailto:fiware-ngsi-bounces at lists.fi-ware.eu]> On Behalf Of ext Tobias Jacobs Sent: Monday, May 21, 2012 11:45 AM To: fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu> Subject: [Fiware-ngsi] FW: NGSI - 9 (apologies to everybody receiving this twice) Dear NGSI-interested people, We are more than late with the definition of a binding for OMA-NGSI 9. There is one fundamental question we need to settle before going into the details: Should the resource structure be the integrated into the NGSI-10 resource structure, or should NGSI-9 have its separated resource structure? Why have only one resource tree for both NGSI-9 and 10? - Simpler Why have a dedicated resource structure for NGSI-9 and 10 - More clear separation of concerns - There are hardly any components in FI-WARE that expose both interfaces anyway. Personally I am a bit more in favor of the second option, but not too strictly. Please feel free to convince me ;-) Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120529/c52410e5/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy