Accord-Project / aec3po

AEC3PO: Architecture, Engineering, Construction Compliance Checking and Permitting Ontology
https://w3id.org/lbd/aec3po/
2 stars 1 forks source link

Units #72

Closed beachtom closed 11 months ago

beachtom commented 1 year ago

Hi,

In my YAML file I find I need to refer to SI units using a URL.

Does using https://github.com/HajoRijgersberg/OM make sense or do you have an alternative suggestions?

AmnaKRDB commented 1 year ago

Hi Thomas,

For the moment, we are reusing the QUDT ontologies (:qudt and :unit) for both the property hasUnit and the units of measures. QUDT is based largely on the international standard for metric units (SI). In the following, an example of re-use:

ex:rampWidth a aec3po:Property , owl:NamedIndividual ; aec3po:hasValue 900 ; qudt:hasUnit unit:MilliM .

If this does not help, I may propose to redefine the property hasUnit with a range URL. Regarding the ontology of units of measures, I think om or unit would work similarly as they both use SI units.

beachtom commented 1 year ago

This is great - can we add unit: prefix to the jsonld context please?

Then all is good

beachtom commented 1 year ago

Sorry just also spotted the domain of hasUnit is wrong - it should point to an appropriate type in unit:

AmnaKRDB commented 1 year ago

This is great - can we add unit: prefix to the jsonld context please?

Then all is good

Hi @beachtom, could you please post the link to json-ld context file? It is used to be under the main branch, but it is no longer there.

AmnaKRDB commented 1 year ago

Sorry just also spotted the domain of hasUnit is wrong - it should point to an appropriate type in unit:

fixed in d00826d

beachtom commented 1 year ago

So it seems to be autogenerated by a script - perhaps @maximelefrancois86 can help

maximelefrancois86 commented 11 months ago

unit: prefix is added to the jsonld context in ce186e2