Is there a vision or guide for discrete states and enumerations? #478
Unanswered
hicksjacobp
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Speaking just for myself, this is a part of the QUDT ontology that has not been updated in years. Our focus has been on Quantifiable values, i.e. those that have a numerical value, rather than enumerations. As you correctly point out, the notion of enumerations is present in the ontology, but I haven't taken a look at that part of the model and am not surprised if there are some inconsistencies. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I see
qudt:DiscreteState
is defined inschema/SCHEMA_QUDT-DATATYPE-v2.1.ttl
, but I see there are only 3 sub-classes:qudt:OnOffStateType
,qudt:OpenCloseStateType
, andqudt:WetDryStateType
.I then see that these 3 sub-classes go on to further define possible values of those states, for example:
However, I see that:
qudt:code
is marked as deprecated inschema/SCHEMA_QUDT-v2.1.ttl
qudt:literal
has a sub-class ofqudt:symbol
, but I don't understand the difference of when to use one over the other and thequdt:On
example usesqudt:literal
instead ofqudt:symbol
.qudt:EnumeratedValue
has a constraint to be a sub-class of aqudt:symbol
, and notqudt:literal
.I also see
qudt:Enumeration
inschema/SCHEMA_QUDT-DATATYPE-v2.1.ttl
which I assume would allow one to define a set of discrete states that belong together.I see that
qudt:DiscreteState
is a sub-class ofqudt:EnumeratedValue
, which has a few more examples not considered discrete states and also aren't considered enumerations.And I can't seem to find much written guidance around enumerations throughout the QUDT website or GitHub repository. So I'm just looking for some insight and possible direction of where this ontology is taking enumerated values / states.
Beta Was this translation helpful? Give feedback.
All reactions