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

Endorse codelists #2

Open
pvgenuchten opened this issue Mar 28, 2024 · 6 comments
Open

Endorse codelists #2

pvgenuchten opened this issue Mar 28, 2024 · 6 comments

Comments

@pvgenuchten
Copy link
Contributor

pvgenuchten commented Mar 28, 2024

Codelists are best endorsed/mandated by an authority or vivid community

How will Soilwise interact with authorities/communities to have soil codelists adopted?

Current and upcoming codelist initiatives, which may need confirmation by a EU authority

New codelists on soil health indicators

A governance model for maintenance of codelists should be available for any endorsed codelist

Codelist repositories should be persistent and standardised (SKOS)

Are current codelists compatible with definitions in legislation?

@fennyvanegmond
Copy link

I'm assuming codelists in this issue equals vocabs. Since the observable properties and procedure descriptions are actually among the most relevant ones for applications

@fennyvanegmond
Copy link

I assume the soil health (legislation) and other legislation codelists and vocabs will be registered to INSPIRE at some point. Does anyone know who is responsible for that? DG DEGIS/a responsible person within each DG (ENV, AGRI, CLIMA, DEGIS, etc)? Or a JRC INSPIRE department?

@fennyvanegmond
Copy link

I'm working with the IUSS WRB and SIS WG's to try to arrange governance on the WRB codelists and possibly GloSIS and other soil related vocabs. More news on that towards the end of May hopefully.

@pvgenuchten
Copy link
Contributor Author

Each memberstate has a national contact point for inspire, this is the typical role to submit changes to the inspire registry, for European institutions, I’m not aware of the route.

@pvgenuchten
Copy link
Contributor Author

pvgenuchten commented May 7, 2024

Vocab and codelist are not equal, vocabulary or thesaurus or glossary are a list of terms with their meaning. A code list or enumeration lists potential values of a property. Third similar type is the ontology or data model, which defines types and relations between types and can include enumerations for type properties

  • glosis ld is an ontology
  • Wrb is a set of codelists (soil types, classes for observed soil properties)
  • Inspire soil is a data model, including references to inspire registry (code lists)
  • agrivoc is a vocabulary including some definitions for items of the wrb code lists

@fennyvanegmond
Copy link

I know the difference between codelists and vocabs, but my point was that governance for both codelists and vocabs is needed and perhaps the vocabs are even more important. Many relevant soil properties are continuous, not class variables.
So if we discuss governance of the codelists, we should include the vocabs that belong to the same ontologies and classification systems as well.

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

No branches or pull requests

2 participants