Closed b-gehrke closed 2 years ago
The original node ids are not kept because they are local to the file and keeping them means it's possible to get clashes between different files (e.g., when importing ontologies that lack an ontology declaration, where the contents of the file are meant to be inlined in the importing ontology).
The behaviour can be changed using ConfigurationOptions.REMAP_IDS and setting the property value for that option to false.
The Individuals: section appears to be just a list of individuals declared to have the class as one of their types (information duplicated in the individual declaration itself).
I'm not sure why it exists or why it's not defined in the standard; the renderer has been creating this section since I first started working on the OWLAPI, according to the history.
Thank you for your responses.
Regarding the Individuals:
section: Would you say the renderer should be changed to not produce those section or should the standard be extended and define this section?
In my opinion the renderer should not create the section as the information is - as you said - just duplicated and can be expressed with the current standard.
I'm not sure of the intent and don't feel confident to say which is the bug - the code or the standard. Maybe @matthewhorridge has an opinion?
When loading an ontology which contains anonymous individuals and rendering it to functional syntax or manchester syntax the nodeIds of those individuals get replaced by
_:genid<someNumber>
. Why aren't the original nodeIds kept?Furthermore, rendering in manchester Syntax introduces an
Individuals:
"axiom" (see example below). The standard doesn't define it. What does it mean and why is it used?Example (taken from bioportal/BRIDG.owl)
Rendered in manchester syntax
Rendered in functional syntax