Page History
The
Gloss | ||||
---|---|---|---|---|
|
...
For the benefits of consistent representation and detection of changes to an expression, the style and rules are recommended though they have no semantic significance. The OWL expressions should be rendered in the form specified by the
Gloss | ||||
---|---|---|---|---|
|
Whitespace
Gloss | ||||
---|---|---|---|---|
|
The whitespace should only be represented as a single nonempty sequence of space (U+20) in the OWL refsets.
...
Gloss | ||||
---|---|---|---|---|
|
Comments could improve the readability. However, comments should not be included to minimize the size of the OWL refsets and reduce the need to maintain the alignment between an axiom and its comments.
Sorting Order
A standard sort order is very useful to enable fast matching of identical expressions though it has no impact to semantics and is not essential for general purpose use.
Each axiom is a serialization of a tree structure that can be traversed by nodes in the following order:
...
The Functional-Style Syntax determines the general order of most elements within an OWL axiom. In fact, the order can only be applied to the nodes within EquivalentClasses(), DisjointClasses(), EquivalentDataProperties(), and ObjectIntersectionsOf() for the current DOCLPS.
Syntax preference for expression variants
The same semantics can be represented by a single axiom or multiple axioms. When axioms are in the same SNOMED CT module,
- Expression in the OWL refset should be presented as an Equivalent Classes axiom instead of two Subclass axioms where both apply, e.g.
EquivalentClasses(A C) is recommended. The following two Subclass axioms are not.
SubClassOf(A C)
SubClassOf(C A)
- Expression in the OWL refset should be presented as a single Subclass axiom with intersection of Class expressions instead of multiple Subclass axioms where they apply, e.g.
SubClassOf(A ObjectIntersectionOf(C D)) is recommended. The following two Subclass axioms are not.
SubClassOf(A C)
SubClassOf(A D)