My site - Latest question feed source question and answer forum written in Python and DjangoenCopyright Askbot, 2010-2011.Thu, 10 Dec 2020 13:42:38 +0100Data Modeling with NGSI-LD: Relationship re-utilization everyone, I have a doubt relative to Relationship attribute definition in a NGSI-LD data models. I was wondering if is posible to re-use the same relationship (with the same relationship name) to point to different Entity types encoded as the objects of the relationship itself. For example, if we have the use case of a Store that sells different type of electronics Items (e.g. computers, smartphones or printers), can we establish the relationship between a Store entity and these types of Item entities (Computer, Smartphone and Printer) with the same "hasItem" Relationship? In this use case, would the data model lose semantics? NGSI-LD simplified representation for Store entity pointing to Computer and Printer entity objects: { "id": "urn:ngsi-ld:Store:store-1", "type": "Store", "hasItem": [{ "type": "Relationship", "object": "urn:ngsi-ld:Computer:computer-HP-0001" },{ "type": "Relationship", "object": "urn:ngsi-ld:Printer:printer-HP-0001" }] ... } I've seen in different tutorials of FIWARE about data models in NGSI-LD that one NGSI-LD entity with different relationships of properties (relationship like a metadata of property) can re-use the same type of relationship. There is an example of this with a "providedBy" relationship between Building properties and Temperature and FillingLevel Sensors entities in Step-by-Step for NGSI-LD Tutorial of FIWARE: My doubt is about if is posible to re-use the same type of relationship between different entities if we use normal relationship like "hasItem" in the explained use case (no metadata Relationship of Property like "providedBy"). If this were posible, like "hasItem" is a multi-relationship entry with different entity objects, it would be necessary to introduce a "datasetId" parameter in each relationship instance in "hasItem" to uniquely identify these relationship instances (i.e. one datasetId por Computer instance object and another one for Printer instance object in the hasItem multi-relationship)? I think not because this multi-relationship entry points to different types of entities and it would not be necessary to uniquely identify them. Finally, also I was wondering if is posible to re-use the same relationship (with the same relationship name) in different types of Entities. For example, if we have the use case of two different stores: Electronic Store and Garden Store that sells different types of Items, can we re-use the same "hasItem" Relationship for both ElectronicStore and GardenStore entities? NGSI-LD simplified representations for ElectronicStore and GardenStore entities using the "hasItem" Relationship: { "id": "urn:ngsi-ld:ElectronicStore:electronic-store-1", "type": "ElectronicStore", "hasItem": { "type": "Relationship", "object": "urn:ngsi-ld:Computer:computer-HP-0001" } ... } { "id": "urn:ngsi-ld:GardenStore:garden-store-1", "type": "GardenStore", "hasItem": { "type": "Relationship", "object": "urn:ngsi-ld:Mower:mower-model-AX23" } ... } Thank you very much in advance. Sincerely, Daniel González Sánchez DanielThu, 10 Dec 2020 13:42:38 +0100 model templates for Information Model creation in NGSI LD format, We are trying to create a Smart Building Model in Fiware (Foundation Model, Domain Model). For that do we have the following in Fiware: - Model management tool: Do we have a UI based tool in Fiware for Instance model creation and maintenance - How to handle model versions ? if Domain model is changed, how will it affect the Instance model for Existing projects. What is the procedure ? - How do we perform Model Validation Thanks for your help!KavipriyaMon, 16 Mar 2020 14:52:02 +0100 a gateway device + attached end devices Hi, What is the manner to model a gateway device to which several end devices are connected? My idea was: For the Gateway: DeviceModel -> category -> network All End devices: Device -> refDeviceModel (the above defined DeviceModel) Is this correct? Thanks.GuyDFri, 08 May 2020 11:43:24 +0200 - Device "A DeviceModel captures the static properties of a Device." Can I interpret that a DeviceModel is a "class" of Devices: meaning I can have several Devices ("instances") with the same DeviceModel: DeviceModel 1 -> N Device? Or is there a 1:1 relationship between DeviceModel and Device? Thanks. GuyDFri, 08 May 2020 11:55:58 +0200 DataModels, What's the difference between 'timestamp' and 'dateModified'? In some datamodels are used 2 different attribute name to represent time instant, `timestamp` or `dateModified`. For exemple on [Device]( datamodel the attribute `batteryLevel` are used `timestamp` and on `configuration`, `dateModified`. > dateModified : It captures the last modification timestamp of this attribute. > timestamp: Timestamp when the last update of the attribute happened. This value can also appear as a FIWARE TimeInstant It's sounds quite similar. The difference between this two attributes justify use a two different names? > Check for the existence of the same attribute on any of the other models and reuse it, if pertinent.LeonanCarvalhoTue, 25 Oct 2016 20:20:38 +0200