search

ec-geolink / design

Design information about the EarthCube Geolink project.
8 stars 1 forks source link

Base ontology: why is the range of hasElevation set to xsd:string? #60

Closed krisnadhi closed 9 years ago

krisnadhi commented 9 years ago

Moved from #52

@mbjones asked:

Question: why is the range of hasElevation set to xsd:string? Shouldn't that be a numeric quantity, and are units implied?

krisnadhi commented 9 years ago

From #52

@sparkji comment:

Comments: In SESAR, elevation is a range, we use elevation, elevation_end and elevation unit to indicate it, so, xsd:string is good for our case, we could use the format like ' 10 to 100 m' to fill 'hasElevation' property.

krisnadhi commented 9 years ago

From #52 @mbjones:

@sparkji thanks for the explanation. Maybe the property should be renamed hasElevationDescription, to differentiate it from a future property that might be more quantitative and constrained.

krisnadhi commented 9 years ago

Question from me in #52:

@sparkji any objection in changing hasElevation to hasElevationDescription?

krisnadhi commented 9 years ago

@sparkji, any objection in replacing hasElevation with hasElevationDescription with string as the range?

sparkji commented 9 years ago

No objection. On Sep 10, 2015 6:34 PM, "krisnadhi" notifications@github.com wrote:

@sparkji, any objection in replacing hasElevation with hasElevationDescription with string as the range?

— Reply to this email directly or view it on GitHub.

krisnadhi commented 9 years ago

Done.