You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
SKOS vocabularies currently need at least one skos:ConceptScheme to be displayed in the UI, and hierarchy works only if skos:broader is used. While I agree the former should be used at least once when defining a vocabulary, there are instances where it's not the case, such as NVS vocabularies (https://vocab.nerc.ac.uk/) we re-distribute through the EarthPortal (example: https://earthportal.eu/ontologies/NVS_L05 with its original source https://vocab.nerc.ac.uk/collection/L05/current/) . Concerning the latter, skos:narrower being the opposite of skos:broader, I think it's logic both can contribute to build the hierarchy.
A possible way to define the root of the structure when there are no skos:ConceptScheme is to let the user define it (e.g. using the URI metadata field, or a brand new field).
The text was updated successfully, but these errors were encountered:
jonquet
changed the title
Display SKOS vocabularies regardless of their structure
Display SKOS vocabularies regardless of their structure (skos:broader or skos:narrower)
Feb 22, 2024
Thanks
This issue is well known to us and we shall address it yes. @syphax-bouazzouni Can you point here the other issues related to SKOS support in AgroPortal so that we can specify and address this point.
@galviset . Do you confirm original L05 contains a skso:ConceptScheme so we do not conflict with the other issue of dealing primarliy with collection?
Hi,
SKOS vocabularies currently need at least one skos:ConceptScheme to be displayed in the UI, and hierarchy works only if skos:broader is used. While I agree the former should be used at least once when defining a vocabulary, there are instances where it's not the case, such as NVS vocabularies (https://vocab.nerc.ac.uk/) we re-distribute through the EarthPortal (example: https://earthportal.eu/ontologies/NVS_L05 with its original source https://vocab.nerc.ac.uk/collection/L05/current/) . Concerning the latter, skos:narrower being the opposite of skos:broader, I think it's logic both can contribute to build the hierarchy.
A possible way to define the root of the structure when there are no skos:ConceptScheme is to let the user define it (e.g. using the URI metadata field, or a brand new field).
The text was updated successfully, but these errors were encountered: