How we make sense of our enterprise and communicate to people what it does.
This is a part of the EDGY language.
How we make sense of our enterprise and communicate to people what it does.
This is a part of the EDGY language.
A reason why our enterprise exists and what our people believe in.
This is a part of the EDGY language.
The individuals co-creating and co-consuming the outcomes we help create.
This is a part of the EDGY language.
A result, goal or change we achieve within our enterprise or its ecosystem.
This is a part of the EDGY language.
What people go through in their lives (and when interacting with us).
This is a part of the EDGY language.
What we communicate to people, expressed in information and media.
This is a part of the EDGY language.
The Class:owl template contains definitions, descriptions, and ontology characteristics according to the ontology diagrams which contain it. This content is synchronized at close of the diagram.
In the future, when there will be a rdf/owl (and possibly turtle and json) loader from text source defining ontologies, these properties will be filled automatically, and the ontology diagram will also be generated.
A class is described with:
It can be:
These five options determine the appearance of the class in the diagram.
These fields are synchronized with the diagrams which the class appears in.
A class is part of a class hierarchy as :
These fields are synchronized with the diagrams which the class appears in, when it participates to set rules.
When participating to a disjoint rule, the classes which the class is Disjoint with are listed here.
When participating to an intersection rule, the classes which the class is in Intersection with are listed here.
When participating to a complement rule, the classes which the class is Complement for are listed here.
When participating to a union rule, the classes which the class is in Union with are listed here.
This field is synchronized with the diagrams which the class appears in.
A class has Properties.
This field is synchronized with the diagrams which the class appears in.
A class has Datatype Properties.
These are the DataTypeProperties which the class is Domain for (source of the relationship).
This field is synchronized with the diagrams which the class appears in.
A class has Instances.
These are the declared instances of the class.