Automatically consider the main skos:ConceptScheme if there is only one

[galviset]

The main skos:ConceptScheme has to be defined manually in the metadata (URI field).
In the EarthPortal, most (if not all) our SKOS resources have only one scheme.
Would not it be simpler to consider the only skos:ConceptScheme the main scheme if there is only one of it in the latest submission ?

[jonquet]

Its an OWL-API issue. If the skos:ConceptScheme is not tagged owl:Ontology too we cannot extract the metadata and the OWL-API is just parsing a bunch of RDF triples.
In AgroPortal (hence EarthPortal) it works(i.e., if a thesaurus with only one skos:ConceptScheme not tagged owl:Ontology is loaded) fine in terms of parsing, but not in terms of metadata extraction.

[syphax-bouazzouni]

Its an OWL-API issue.

it's a SKOS standard issue, for not providing a way to distinguish between the main scheme and the others.

But A possible addition, on our side in the metadata extraction step, is that: If no owl:Ontology found and a unique skos:ConceptScheme found => set the URI=the unique concept scheme found. Which represents the majority of the case.

[jonquet]

@galviset Would that work for you?
I mean I am not sure about the issue here:
Is this:

1. a matter of extracting the metadata from the skos:ConceptScheme without having to tag it owl:Ontology
2. a matter of dealing with unique concept scheme ... if there is only one scheme in a file the notion of "main" does not apply.
   Can you illustrate on examples on EarthPortal? What does not work that you will expect to work...
   So we can come up to a decision about this issue?

[galviset]

Mostly number 2. We don't have vocabularies with several skos:ConceptScheme yet.
Most of our vocabularies are defined with a unique skos:ConceptScheme. The most simple decision to take here is to automatically tag it as the main one. Example: https://earthportal.eu/ontologies/SXT_TJD/?p=summary
In some specific cases like NVS vocabularies, they use skos:Collection instead of skos:ConceptScheme (EarthPortal examples use a transformed version where skos:Collection is manually changed into skos:ConceptScheme). I'm not sure if it's safe to do automation in that cas, unless we explicitly let the user choose the entity from which the metadata should be extracted (through the URI field, though making it more obvious in case of SKOS => in case of NVS vocabularies they set the skos:Collection one).

[jonquet]

@galviset on your example (SXT_TJD) what's the issue ? The unique scheme is "view as" the main one...
(there is no explict "tag" in our system). As you see here:

The rest of your point is another issue. Can you describe it in another issue and provide an example of a SKOS source file (from NVS) that contains NO sksos:ConceptScheme but only one (or several) skos:Collection.

[jonquet]

Guillaume... sur SXT_TJD... est-ce que tu as fait qq chose dessus... genre affecter l'URI du seul concept scheme a l'URI de la soumission ? Si oui... alors oui c'est qq chose qu'on devrait faire automatiquement .

[jonquet]

@syphax-bouazzouni On peut changer l'étape d'extraction de metadonnées pour extraire l'UIR d"un concept scheme p(par hasard) si pas de owl:Ontology.

[galviset]

Guillaume... sur SXT_TJD... est-ce que tu as fait qq chose dessus... genre affecter l'URI du seul concept scheme a l'URI de la soumission ? Si oui... alors oui c'est qq chose qu'on devrait faire automatiquement .

Oui, l'URI a été affectée manuellement, c'était un mauvais exemple. Un exemple plus pertinent : https://earthportal.eu/ontologies/TOZ/?p=summary
Il faudrait pouvoir le faire automatiquement lorsqu'il y a qu'un seul concept scheme.