Research project of the Cluster of Excellence "Integrative Computational Design and Construction for Architecture" (IntCDC) https://www.intcdc.uni-stuttgart.de/ **Project Name**: Knowledge Representation for Multi-Disciplinary Co-Design of Buildings. https://www.intcdc.uni-stuttgart.de/research/research-projects/rp-20/
GNU Lesser General Public License v3.0
9
stars
4
forks
source link
RDF_Engine: Object/Data Properties domain should be the base type they originate from #49
Our current converter assigns properties to objects we see in Rhino. However, following BHoM conventions most of the properties that objects have are coming from interfaces they implement.
Since, when converted to graph, interfaces are also classes, so properties should be assign to the parent class (BHoM interface). Eg, in the case of a room, the Perimeter's domain (ICurve Property's domain) should be IRegion, instead of Room.
Steps to reproduce:
The object properties derive from the interfaces they implement; these should be assigned to the interfaces instead of the object (Room class in this case).
Description:
Our current converter assigns properties to objects we see in Rhino. However, following BHoM conventions most of the properties that objects have are coming from interfaces they implement.
Since, when converted to graph, interfaces are also classes, so properties should be assign to the parent class (BHoM interface). Eg, in the case of a room, the Perimeter's domain (ICurve Property's domain) should be IRegion, instead of Room.
Steps to reproduce:
The object properties derive from the interfaces they implement; these should be assigned to the interfaces instead of the object (Room class in this case).
Expected behaviour:
Test file(s):