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
Created TTL Adapter; changed to NETStandard 2.0 #65
Created new TTL_Adapter to export to TTL. This is because we will soon add more converts to different formats (e.g. Markdown, so that an Ontology web page "BHoWL" can be generated via Material for MkDocs).
Additionally, for compliance, Projects that are non-executable (i.e. all except the RDF_Tests and RDF_ConsoleApp) need to be NETStandard2.0. This PR adjusts for that.
Test files
This PR modifies the organisation of the functions, so it will likely require an update of any existing Grasshopper script.
The Unit Tests in RDF_Tests must be run via the Visual Studio Test Explorer and must all pass.
Created new TTL_Adapter to export to TTL. This is because we will soon add more converts to different formats (e.g. Markdown; also the old experimental WebVOWL Json format should be moved to a dedicated adapter at some point).
A limitation in what can be output from an Adapter's Pull action (it only outputs a List<object> and a success boolean) means that we need to keep supporting Engine Converts for now. This is because we want to get the pulled objects, and also the OntologySettings as a separate output. To retain this latter workflow, the TTL Conversion Engine methods are still public and located in the Engine, so they are still reflected as Grasshopper components. We might deprecate it in future in favour of Adapter-only workflow if we modify the base Adapter to allow multiple separate outputs.
Ported all projects that are non-executable (i.e. all except the RDF_Tests and RDF_ConsoleApp) to NETStandard2.0.
Issues addressed by this PR
Closes #64 Closes #66
Created new TTL_Adapter to export to TTL. This is because we will soon add more converts to different formats (e.g. Markdown, so that an Ontology web page "BHoWL" can be generated via Material for MkDocs). Additionally, for compliance, Projects that are non-executable (i.e. all except the RDF_Tests and RDF_ConsoleApp) need to be NETStandard2.0. This PR adjusts for that.
Test files
This PR modifies the organisation of the functions, so it will likely require an update of any existing Grasshopper script. The Unit Tests in RDF_Tests must be run via the Visual Studio Test Explorer and must all pass.
Additionally, here's a test file: TTLAdapterTest.zip
Changelog
List<object>and asuccessboolean) means that we need to keep supporting Engine Converts for now. This is because we want to get the pulled objects, and also theOntologySettingsas a separate output. To retain this latter workflow, the TTL Conversion Engine methods are still public and located in the Engine, so they are still reflected as Grasshopper components. We might deprecate it in future in favour of Adapter-only workflow if we modify the base Adapter to allow multiple separate outputs.