Introduce an owl:class to capture all BHoM interfaces

Open
#27 0 comments 1 reaction 1 assignee View on GitHub

@DiellzaElshani is already working on this.

Since Jun 13, 2022.

Assessment

This issue has not been assessed yet.

Description

priority:low type:feature

Mapping both BHoM's classes and interfaces to owl:classes has created a flattening in data structure, which can be complicated to map back to the original data model.

Description:

To distinguish between classes and interfaces in the graph, we can create a new owl:class named BHoM_Interface; where each interface is a subclass of this new class.

this is a suggestion from: Raul Garcia-Castro - Ontology Engineering Group https://www.linkedin.com/in/raulgarciacastro/

Dominant language
C#
Stars
10
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BHoM/RDF_Prototypes

All issues in BHoM/RDF_Prototypes

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.