-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quantity Value restrictions based on Unit or QuantityKind #1052
Comments
Hopefully we can treat this explicitly once our datatypes graphs are cleaned up in the near future. Then we could create SHACL shapes for the appropriate datatype for all quantitykinds and units. I imagine we would use qudt:Aspect subclassing for this. |
Need to look into that, but I thought it's probably just one triple linking the unit/quantitykind to a definition of the data type - no? |
Could be, unless we want to construct things like unions of datatypes. We wouldn't want to have to repeat multiple triples for units. |
We'll see, I suppose. |
Union types make a lot of sense, as do enumerations. In the early days of QUDT there was support for that. Maybe that was not promoted to the public QUDT. I will look into this. It is relevant for me, because I am reviewing/updating the datatypes ontology, the "T" in QUDT. |
As we see in many issues, for example #1047, some units or quantitykinds require datatypes vor the quantity values other than xsd:double or xsd:decimal.
How about making it explicit by adding a shacl shape that checks quantity values based on some information associated with units and quantity kinds and assuming a floating point number as default?
The text was updated successfully, but these errors were encountered: