Page History
...
- Importing or exporting complex, nested class expressions involving unions, intersections, complements, and restrictions no longer results in a loss of fidelity.
- Annotation language and datatype are no longer lost or forced to be "en".
- IRI annotations are no longer lost on import and export.
- Importing resources with local names that start with a number no longer fails.
- Annotations on an ontology are no longer incorrectly emitted as annotation assertions.
- Messages appearing in the notification window no longer have the beginning of the URL stripped off.
- Fixed a subtle notation inconsistency for
- Importing a restriction that has another restriction as its filler no longer causes a subtle notation inconsistency.
- Opening a project without AutoStyler installed no longer results in a prompt to update the 'Defined Elsewhere' style.
- Importing a property domain that is an intersection of classes no longer creates multiple named properties in UML.
- Importing a property with multiple domains now results in an intersection of those domains as the owner of the UML property.
- Exporting a property with multiple domains to OWL results in a union of those domains as the domain of the property.
- Exporting a property with multiple types to OWL results in a union of those types as the range of the property.
- Importing an ontology into CCM no longer refers to «Anything» as «Property Holder» in log messages.
- Importing an ontology into CCM no longer ignores annotations on ontologies imported by that ontology.
...