GloSIS currently includes three principal categories of code-list (specified with SKOS):
Values of descriptive observations extracted from the FAO Guidelines for Soil Description
Physio-chemical properties associated with Layer/Horizon
Procedures associated with physio-chemical observations on Layer/Horizon
While all these are useful, end users will primarily create/use instances of sosa:Observation classes. However these cannot be readily transformed into easily browsable, homan-friendly, HTML pages, like those automatically produced by software supporting SKOS.
Should the ontology include SKOS concept schemes grouping the different Observation series? Otherwise, how can observation instances and sub-classes be made more visible.
GloSIS currently includes three principal categories of code-list (specified with SKOS):
While all these are useful, end users will primarily create/use instances of sosa:Observation classes. However these cannot be readily transformed into easily browsable, homan-friendly, HTML pages, like those automatically produced by software supporting SKOS.
Should the ontology include SKOS concept schemes grouping the different Observation series? Otherwise, how can observation instances and sub-classes be made more visible.
Update: similar discussion in issue #153.