A week has passed and got no reply to this mail. In case there is no reply in 2 days, I assume that that the attributeDomainName is indeed an entity level property, and as such is not relevant for special address in the RESTful binding. Neither in the contextElementId nor the contextElementType resource. Best, Dénes _____________________________________________ From: Bisztray, Denes (NSN - HU/Budapest) Sent: Thursday, March 01, 2012 1:06 PM To: fiware-ngsi at lists.fi-ware.eu Subject: AttributeDomainName problem Hi All, Sorry for bringing up yet another topic, but I realised that the RESTful binding of the AttributeDomainName is a bit questionable. The spec says (sec 5.5.1, pg 22): AttributeDomainName (xsd:string) - Name of the attribute domain that logically groups together set of Context Information attributes. Examples of attribute domain are: device info (battery level, screen size, ...), location info (position, civil address, ...). And below that at the ContextAttribute it says: ContextAttribute [0..unbounded] - List of Context Information attributes. Note: In case of the attributeDomainName is specified all contextAttribute have to belong to the same attributeDomainName. So as it seems inside a ContextElement you have only one attributeDomain. However, the restful binding puts in inside: /contextElements/{contextElementID}/{attributeDomainName} And says: Retrieve the values of all attributes of the context element belonging to the specific domain This seems to be a conflict to me. ( i.e. if that attributeDomainName is queried that is specified in the ContextElement then all attributes are returned otherwise none?). What if we move this one direction higher? i.e. /contextElements/{contextElementId} /contextAttributeDomains/{attributeDomainName} (not in the same level of {contextElementId} to avoid the resolution chaos) Best, Dénes -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120307/ff41c42d/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy