Anomalie #22913

IGSN compatibility and encoding of the IGSN in eposb:Borehole and eposb:Sample

Ajouté par Henning Lorenz il y a plus de 7 ans.

Statut:NouveauDébut:22/03/2019
Priorité:NormalEchéance:
Assigné à:-% réalisé:

0%

Catégorie:-
Version cible:-

Description

We have a couple of IGSN related questions/issues:

1) Explicit encoding of the IGSN. We don't have an optional element for it although we strove after basic IGSN compatibility. I have mapped the IGSN to gml:descriptionReference

<gml:descriptionReference xlink:href="https://igsn.org/ICDP5054EHW1001" xlink:title="IGSN registry entry"/>

Is this how we want to do it or do we want to develop this further in the next version (eposb simple feature or maybe look at the IGSN xsd)?

2) What is a sample? (This is wider than IGSN, but particularly relevant for IGSN)
We have two concepts:
a) Samples are material sampled from the borehole (or section) by a researcher for active scientific work (this can be drill core, water samples, swab samples for microbiology, ...) [this is what I have included as eposb:Sample]
b) Of much more interest for the end user is what material is available from the borehole, i.e. the entire sample material (e.g. kms of continuous drill core vs. some hundreds of small sample in the same project, if limited to a). The hierarchy core run - section - sample reflects the entire sample material and the samples according to a). Our model would allow this and it is actually in parallel to the point we discussed with Eric and the vocabulary of UC14 in the BoreholeIE, the hierarchy of ICDP numbering concept.
Is b) of interest for us? If yes, I would give it a try when time permits ( a) is ready). But before I would like to come to a conclusion about point 1), as the two are tightly related.

Formats disponibles : Atom PDF