Denes, I think any kind of relationship can be expressed by attributes. So building: has an attribute hasRooms with the values room_1 and room_2. Now, I think the point you are implicitly looking at is that containment hierarchies can be used for special purposes, e.g. for naming. So by making the containment relationship a special relationship, we might use this e.g. for having a hierarchical structured resource tree following the containment relationship and having respective hierarchical names. The "containment" relationship is special, but there might be also other and the might be more than one "logical" containment. Person X is in his private life meber of his family and in his business life member of his company, and in his sports life member of his sport club. Conclusion: - Relationships can be expresses - No special relationships We understand that some things can be done/expressed more efficient with special relationships. - Ernö From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest) Sent: Samstag, 24. März 2012 13:51 To: fiware-ngsi at lists.fi-ware.eu Subject: [Fiware-ngsi] hierarchical entities Dear all, Let me raise a problem with NGSI: it seems it does not support containment. That is, we can have entities building_1, room_1 and room_2 with their own attributes, but no relationship between them. Is anyone aware of some solution for expressing that building_1 contains room_1 and room_2, apparently? (apart from adding metadata to bulding_1 such as childentity=room_1) Best, Dénes -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120324/d50fc4a4/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy