Jose M. Cantera

NGSI-LD has already solved this issue https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.01.01_60/gs_CIM009v010101p.pdf Section 6.6 207 Status UpdateResult data structure (Section 5.2.18)

sorry for jumping in here. the #, / and ? should be valid chars for Entity Ids. We already had this discussion with NGSI-LD. There is no risk of ambiguity...

The intent of the keyValues format was to provide a simplified representation to be consumed by readers but not a "convenient" but in the end semantically incomplete format for writers....

try with http instead of https ... on the other hand I would strongly recommend that you use NGSIv2 and GeoJSON for your API and payloads

@LeonanCarvalho could you provide a contribution? I would be happy to review it

Future-wise I prefer to evolve towards what is going to be defined by iot.schema.org (W3C is creating a new CG on that) rather than changing existing Data Models. https://github.com/iot-schema-collab

partially fixed. need also to launch Orion-LD

taken, probably we need to downsize it a bit, so leaving this open

why do you need a new query parameter `attr`. Wouldn't just suffice with allowing `attrs` to be just an empty list?

And the spec would need an update to allow empty attr list both in queries and subscriptions El jueves, 19 de septiembre de 2019, Jason Fox escribió: > I agree....