Closed fennyvanegmond closed 2 months ago
This is a very good remark. The GloSIS domain model only defines code-lists for observable properties, later on ISRIC added code-lists for procedures. However in most cases users will only instantiate observations, which are not code-lists. It is not like this by chance, since INSPIRE takes a similar approach. So does the more recent work by CSIRO.
This is the main reason why I opened issue #123. I intend to reconsider the observations more carefully for release 2.0, which I expect for next winter. This could either be addressed with SKOS or with the new predicates that will be introduced in SOSA 2.0.
Another aspect to consider is the need for a GloSIS user manual, that would explain these issues in layman's terms. That work would probably benefit from some funding.
@fennyvanegmond I am closing this issue, since in #123 there is already a good gist of this question. Please continue this discussion there.
i want to understand linkage between definitions of soil properties and the procedures to assess them, as an example:
when browsing the codelists in a tool like vocprez, when searching for total phosphorus, i'd be interested to understand linkages between this item and concepts related to how to measure this soilo property, in which unit of measure it is expressed, understand the type of values (continuous or in classes), etc
for example, no linkage from PhosphorusRetentionProcedure to
total phosphorus content