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/
This PR adds support for non-bhom objects. However, this only works on the assumption that our ontology mapper assumptions are respected by the input objects. As a reminder, these assumptions are BHoM's underlying assumptions, which is why we ask people to operate with BHoM objects if they can; these are:
input object must have all public properties (only public properties are gathered)
input object's public properties must have get avaiable, and also the set if conversion back from TTL is desired
(non mandatory, nice to have) input object must have orthogonal properties
Tests
See the function FromTTLTests.NonBHoMType() for an example test.
@DiellzaElshani please test with Grasshopper scripts.
Issues addressed by this PR
Closes #38
This PR adds support for non-bhom objects. However, this only works on the assumption that our ontology mapper assumptions are respected by the input objects. As a reminder, these assumptions are BHoM's underlying assumptions, which is why we ask people to operate with BHoM objects if they can; these are:
getavaiable, and also thesetif conversion back from TTL is desiredTests
See the function
FromTTLTests.NonBHoMType()for an example test. @DiellzaElshani please test with Grasshopper scripts.Changelog
Additional comments