Replies: 1 comment
-
Yes, in OML v1 this is not allowed. This will be allowed in upcoming OML v2. However, notice that each set you assert, whether on the definition or on a ref, will be asserted as the exclusive set. So, if you have multiple such assertions, the DL reasoner will check that they are indeed the same instances; otherwise will complain about inconsistency.
What the |
Beta Was this translation helpful? Give feedback.
-
I have two additional questions related to enumeration:
I tried adding enumeration in a ref concept statement, but the build failed. Is the use of enumerates keyword not allowed in a reference statement?
What is the advantage of using a concept to enumerate concept instances? Is it helpful for reasoning and/or queries and if so, how?
I'm pasting the answer from Maged to my initial question about use of enumeration on concepts for context for additional discussions:
The case for enumerating instances of concepts is similar in principle to that of enumerating literals for scalars. Although the syntax in OML v1 for them is different (for literals it is specifying them within an
enumerated scalar
, while for instances, it is specifying them with theenumerates
keyword on a concept), I am unifying the syntax in OML v2 (both will be aoneOf <comma-sep-list>
keyword you can add to ascalar
or aconcept
within their [..] brackets).For instances, the idea is that you define them in a description and then enumerate them in a vocabulary:
description http://description1# as desc1 {
uses http://vocabulary1# as voca1
}
vocabulary http://vocabulary1# as voca1 {
uses http://description1# as desc1
}
Beta Was this translation helpful? Give feedback.
All reactions