Skip to content
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

DwC Mapping - MIXS:0000093 elev #15

Closed
tucotuco opened this issue Feb 10, 2021 · 5 comments
Closed

DwC Mapping - MIXS:0000093 elev #15

tucotuco opened this issue Feb 10, 2021 · 5 comments
Labels
DwC Mapping The issue is about the mapping of a MIxS term to a Darwin Core term or terms. DwC-MIxS TG This issue is related to the work of the Sustainable DarwinCore MIxS Interoperability Task Group

Comments

@tucotuco
Copy link
Member

tucotuco commented Feb 10, 2021

Field Value
subject_id http://rs.tdwg.org/dwc/terms/verbatimElevation
subject_definition The original description of the elevation (altitude, usually above sea level) of the Location.
subject_usage_notes
subject_examples 100-200 m
predicate_id skos:broadMatch
object_id MIXS:0000093
object_label elev
object definition Elevation of the sampling site is its height above a fixed reference point, most commonly the mean sea level. Elevation is mainly used when referring to points on the earth's surface, while altitude is used for points above the surface, such as an aircraft in flight or a spacecraft in orbit
object source https://github.com/GenomicsStandardsConsortium/mixs-legacy/blob/master/mixs5/mixs_v5.xlsx
comment Going from MIxS to Darwin Core, the predicate would be skos:exactMatch, as the pattern in MIxS will always be acceptable on the Darwin Core side.
@tucotuco tucotuco added the DwC Mapping The issue is about the mapping of a MIxS term to a Darwin Core term or terms. label Feb 10, 2021
@raissameyer
Copy link
Collaborator

Should this term also be mapped to dwc:maximumElevationInMeters and dwc:minimumElevationInMeters, following the same structure as the depth mappings in #13 ?

We should think about what criteria decide whether we map terms with multiple possible matches to only one or all.

@tucotuco
Copy link
Member Author

tucotuco commented Mar 2, 2021

It could be, but it is an indirect mapping with a potential calculation, whereas the verbatimElevation is an exactMatch.

@pbuttigieg pbuttigieg added the DwC-MIxS TG This issue is related to the work of the Sustainable DarwinCore MIxS Interoperability Task Group label Mar 2, 2021
@raissameyer
Copy link
Collaborator

raissameyer commented Mar 30, 2021

Additional mapping options

Field Value
subject_id http://rs.tdwg.org/dwc/terms/minimumElevationInMeters
subject_definition The lower limit of the range of elevation (altitude, usually above sea level), in meters.
subject_value_syntax - expected_value - unit {float} - measurement value - meter
subject_examples -100, 802
predicate_id skos:narrowMatch
syntax_predicate_id skos:narrowMatch
object_id MIXS:0000093
object_label elev
object definition Elevation of the sampling site is its height above a fixed reference point, most commonly the mean sea level. Elevation is mainly used when referring to points on the earth's surface, while altitude is used for points above the surface, such as an aircraft in flight or a spacecraft in orbit
object_value_syntax - expected_value - unit {float} {unit} - measurement value - meter
object source https://github.com/GenomicsStandardsConsortium/mixs-legacy/blob/master/mixs5/mixs_v5.xlsx
comment
syntax_comment The DwC example does not include a unit, only a {float}, while MIxS expects the input to be {float} {unit}

and

Field Value
subject_id http://rs.tdwg.org/dwc/terms/maximumElevationInMeters
subject_definition The upper limit of the range of elevation (altitude, usually above sea level), in meters.
subject_value_syntax - expected_value - unit {float} - measurement value - meter
subject_examples -205, 1236
predicate_id skos:narrowMatch
syntax_predicate_id skos:narrowMatch
object_id MIXS:0000093
object_label elev
object definition Elevation of the sampling site is its height above a fixed reference point, most commonly the mean sea level. Elevation is mainly used when referring to points on the earth's surface, while altitude is used for points above the surface, such as an aircraft in flight or a spacecraft in orbit
object source https://github.com/GenomicsStandardsConsortium/mixs-legacy/blob/master/mixs5/mixs_v5.xlsx
comment
syntax_comment The DwC example does not include a unit, only a {float}, while MIxS expects the input to be {float} {unit}

@raissameyer
Copy link
Collaborator

As we have now decided to capture the syntax separately from the semantics, we can go back to the original mapping predicate skos:exactMatch for dwc:verbatimElevation and MIxS:elev

@raissameyer
Copy link
Collaborator

raissameyer commented Apr 16, 2021

Suggested syntax predicate for the mapping above #15 (comment)

Field Value
subject_id http://rs.tdwg.org/dwc/terms/verbatimElevation
subject_value_syntax - expected_value - unit verbatim
syntax_predicate_id skos:relatedMatch
object_id MIXS:0000093
object_value_syntax - expected_value - unit {float} {unit} - measurement value - meter
syntax_comment The DwC term expects verbatim input (so anything really), whereas MIxS expects {float} {unit} in meter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DwC Mapping The issue is about the mapping of a MIxS term to a Darwin Core term or terms. DwC-MIxS TG This issue is related to the work of the Sustainable DarwinCore MIxS Interoperability Task Group
Projects
None yet
Development

No branches or pull requests

3 participants