At ISRIC we've noticed an increased use of markdown oriented workflows, each using dedicated technology. We felt the need to align in technology. That's why we've migrated this repository from MKdocs to Quarto.

'Alternatively, MDME is an online visual editor for mcf files' can you load the yaml file quoted above in this editor easily? If so, can you elaborate/explain on this?
On https://ejpsoil.github.io/soildata-assimilation-guidance/cookbook/pygeometa.html

suggestion is to add a sparql example to the dcat article, the sparql query would extract any datasets that match a certain keyword

i want to try to extract some rdf from data.isric.org, to be loaded on the local virtuoso instance

https://data.isric.org/geonetwork/srv/eng/rdf.metadata.get?uuid=a6320590-0899-4b60-bf4d-f80282bbb72c

only the first day recordings are now available, can you add the others that are ok to share?

Page https://ejpsoil.github.io/soildata-assimilation-guidance/tools/virtuoso/ should be completed to contain a section on how to load data into virtuoso, we could use the glosis codelists, or some other sample

https://github.com/INSPIRE-MIF/2017.2/blob/master/template/template.qmd

Document link:
https://github.com/ejpsoil/soildata-assimilation-guidance/blob/main/docs/uri.md

Please reassign if someone else can contribute.

Document link:
https://github.com/ejpsoil/soildata-assimilation-guidance/blob/main/docs/tools/tarql.md

Please reassign if someone else can contribute.

Document link:
https://github.com/ejpsoil/soildata-assimilation-guidance/blob/main/docs/code-listsExtension.md

To complete once pull request #1 is merged.

https://github.com/INSPIRE-MIF/gp-geopackage-encodings describes on approach of providing a geopackage as encoding for a INSPIRE datamodel.

This approach would fit many of our partners, but we need to provide some guidance on how to do it and which datamodel to use

I added this placeholder for that content

https://ejpsoil.github.io/soildata-assimilation-guidance/tools/glosis-db/

One of the tools developed is a template which describes the alternative encoding, the template is here. Most substantial is the option to provide a mapping from the alternative encoding to the uml and vice versa.

Probably needs further discussion (include thorsten)

How they compare to vocabs/ontologies

add a video from first course

There currently two meta-data documents in the root:

• data-organisation.md

• metadata.md

It is probably best to merge them into a single document named Metadata. The term "data organisation" is uncanny and ambiguous.

2 options here:

• merge the 2 recipes
• keep both recipe's but consider the codelist extension a followup of the virtuoso/skosmos recipe

Currently https://ejpsoil.github.io/soildata-assimilation-guidance/tools/virtuoso/ introduces the virtuoso and skosmos software the recipe still needs to be extended on how to load a ttl on virtuosos and link it to skosmos (readers are invited to load a sample ttl into virtuoso (or create one with skos play)

The extending codelist recipe would provide more details on how the ttl is structured, not sure if skos play provides enough capabilities to indicate the hierarchy of codelists required for codelist extension

Document link:
https://github.com/ejpsoil/soildata-assimilation-guidance/blob/main/docs/tools/rml.md

Please reassign if someone else can contribute.