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

concept:measured #31

Open
dshorthouse opened this issue May 18, 2020 · 5 comments
Open

concept:measured #31

dshorthouse opened this issue May 18, 2020 · 5 comments

Comments

@dshorthouse
Copy link
Contributor

dshorthouse commented May 18, 2020

measured (concept)

Definition Determined the value of a measurement
Existing concept
Existing namespace
Existing concept identifier
Format string
Examples "measured"
Notes
@PietrH
Copy link
Member

PietrH commented May 29, 2020

Is digitization a form of measurement? What about Photogrammetry?

@dshorthouse
Copy link
Contributor Author

@PietrH Good question. The intent of this term was to align with the existing DwC term, http://rs.tdwg.org/dwc/terms/measurementDeterminedBy. Should we have a more granular definition here than that DwC term?

@PietrH
Copy link
Member

PietrH commented Jun 10, 2020

@dshorthouse I'm a bit confused, so the value of measured: would be a string of person names? or person identifiers? What is the added information of repeating this over just using measurementDeterminedBy in the MeasurementOrFact table?

The ideal solution would be if the MeasurementOrFact table could refer to identifiers in a 'people' table where all the other information can be found. As using just string such as the http://rs.tdwg.org/dwc/terms/measurementDeterminedBy example Peter Desmet | Stijn Van Hoey can still lead to ambiguity about who exactly you are referring to.

@dshorthouse
Copy link
Contributor Author

dshorthouse commented Jun 10, 2020

@PietrH – what you're commenting on here is an option for an entry in the #22 term as part of the Actions controlled vocabulary. So in your example, a partial tabular representation in the extension might look like this, with occurrenceID here the foreign key to a single entry in the core:

occurrenceID name identifier action displayOrder
1001 Peter Desmet https://orcid.org/0000-0002-8442-8025 measured 1
1001 Stijn Van Hoey https://orcid.org/0000-0001-6413-3185 measured 2

Now, what you are also touching on is the notion that we already have an Extended Measurement of Fact as an extension to Darwin Core and it too has a term, measurementDeterminedBy as does the core. This is functionally equivalent to a identifiedBy term in the Darwin Core Identification History extension where it too has exactly the same term in the core. So, what is the lateral relationship between these terms in extensions to this present draft extension and how it more granularly represents actions and agents? In a word: none. The only partial solution to this is as @matdillen suggests and use the newly minted GBIF namespaced terms like recordedByID, identifiedByID in amended versions of those other extensions and ask that there be a full complement of options for all the actions we have represented in this controlled vocabulary such as measuredByID, preparedByID, etc. That's as ugly as it sounds.

@RBGE-Herbarium
Copy link

The act of recording a measurement of or fact about an rdfs:Resource (http://www.w3.org/2000/01/rdf-schema#Resource).

This would be a direct reference to the existing TDWG term MeasurementOrFact http://rs.tdwg.org/dwc/terms/MeasurementOrFact

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

No branches or pull requests

2 participants