Accord-Project / aec3po

AEC3PO: Architecture, Engineering, Construction Compliance Checking and Permitting Ontology
https://w3id.org/lbd/aec3po/
2 stars 1 forks source link

make richer diagrams #33

Closed VladimirAlexiev closed 1 year ago

VladimirAlexiev commented 1 year ago

We got some diagrams in https://github.com/Accord-Project/aec3po/tree/main/resources, but we should strive to make richer diagrams as in DiCon, see #32 for an example.

The diagrams should make it clear:

We use the same graphical notation, so it should be easier to accommodate graphical constructs as in DiCon. @maximelefrancois86 , I see you use Draw.io, but which stencil is this?

EdliraK commented 1 year ago

I agree and yes is in our todo list. We also like how DiCON is documented. BRICK is also a good example @AmnaKRDB as we have discussed before. @tanhe-git we need to coordinate with Tan as well as their task is pure in documentation.

VladimirAlexiev commented 1 year ago

@AmnaKRDB @maximelefrancois86 @EdliraK What notation did you use, is it Chowlk?


Another great notation is Grafoo, it can also generate OWL from the diagram (DITTO). I have a bunch of Grafoo examples (in g:\Shared drives\KGS\data-tools\ontology\editors, visualization\Grafoo):

EdliraK commented 1 year ago

Yes we used Chowlk.

maximelefrancois86 commented 1 year ago

As a complement, we use Chowlk only for preparing the diagrams. Not for generating the OWL. Actually I'd like Chowlk to do the other way around: help generate nice figures from an ontology

Now each the documentation of each module may have its own diagram, like

https://w3id.org/lbd/aec3po/document

and

https://w3id.org/lbd/aec3po/feature_of_interest