Skip to content
This repository has been archived by the owner on Jun 15, 2018. It is now read-only.

Units of measure #20

Open
GoogleCodeExporter opened this issue Mar 13, 2015 · 3 comments
Open

Units of measure #20

GoogleCodeExporter opened this issue Mar 13, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

Description of the issue or change request

Units of measure is currently captured in a preliminary way via a datatype 
property hasUnitsOfMeasure with domain ValueType and range string.

This issue is how to incorporate units of measure in general?

A possible immediate next step is to set the range of hasUnitsOfMeasure to 
rdfs:Resource, so a URI can be indicated.

Some relevant links include:

* 
http://forge.morfeo-project.org/wiki_en/index.php/Units_of_measurement_ontology
Good description of the issue of modeling units of measure in general and the 
MUO ontology in particular. Also many links therein.


* http://www.qudt.org/  

Original issue reported on code.google.com by [email protected] on 22 Jun 2010 at 9:17

@GoogleCodeExporter
Copy link
Author

hasUnitsOfMeasure's range is now rdfs:Resource

http://mmisw.org/ont/mmi/20100623T004300/device


Original comment by [email protected] on 23 Jun 2010 at 12:42

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

I'm having trouble seeing where this ties into the ontology - it could be used 
in many places (tolerances, ranges, as well as process outputs). Definitely 
agree that it should use an external UOM resource.

Original comment by [email protected] on 17 Aug 2010 at 3:03

@GoogleCodeExporter
Copy link
Author

Relevant discussion during the MMI TEch telecon today: 
http://marinemetadata.org/community/teams/tech/agendas/20101005tech


Original comment by [email protected] on 5 Oct 2010 at 11:44

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant