Noria ontologies and kos lack a default namespace

[thomashassan35]

The ontology/kos files use the @base statement but do not define a default namespace with the prefix : <http://www.Example.org/> statement.
Most turtle parsers (if not all) are unable to provide the @base value as it is neither a prefix or a statement. In ontology files this has almost no implications but for the kos vocabulary this makes it impractical to determine the namespace of the vocabulary.
The kos file could have both the @base and the equivalent default namespace with no other change.

[GenEars]

The ontology/kos files use the @base statement but do not define a default namespace with the prefix : <http://www.Example.org/> statement. Most turtle parsers (if not all) are unable to provide the @base value as it is neither a prefix or a statement. In ontology files this has almost no implications but for the kos vocabulary this makes it impractical to determine the namespace of the vocabulary. The kos file could have both the @base and the equivalent default namespace with no other change.

Hello @thomashassan35, and thanks for your proposal.
Would you agree on something like what follows?

@prefix noria-kos: <https://w3id.org/noria/kos/> .

[rtroncy]

The shortname noria-kos is fine but more importantly, the default namespace should be attached to this namespace URI

[GenEars]

The shortname noria-kos is fine but more importantly, the default namespace should be attached to this namespace URI

Thanks for the remark @rtroncy.

Considering noria as the default namespace, refactoring NORIA-O would then sum to:

• Declare @prefix noria: <https://w3id.org/noria/ontology/> . in the NORIA-O's kos file.
• Modify the current base of the NORIA-O's kos file to @base <https://w3id.org/noria/ontology/kos/> .
• Rework references to kos entities, when done using URIs, in the NORIA-O ontology and RML examples.

@thomashassan35 any remark on this? considering that the underpinning idea is, beside solving the Turtle parser issue you have mentioned, you would have a single namespace to refer to both the NORIA-O core concepts and the NORIA-O controlled vocabulary.

[thomashassan35]

@GenEars thanks for the quick response and proposal.

Yes I think your proposal is a good approach, it makes more sense to have a common root namespace

[GenEars]

@GenEars thanks for the quick response and proposal.

Yes I think your proposal is a good approach, it makes more sense to have a common root namespace

Hello @thomashassan35, I have just pushed all the above-discussed modifications to https://github.com/Orange-OpenSource/noria-ontology/tree/v0.4

Could you please check if this fits your needs, then I'll make a new NORIA-O release.

[thomashassan35]

@GenEars thanks for the quick response and proposal.
Yes I think your proposal is a good approach, it makes more sense to have a common root namespace

Hello @thomashassan35, I have just pushed all the above-discussed modifications to https://github.com/Orange-OpenSource/noria-ontology/tree/v0.4

Could you please check if this fits your needs, then I'll make a new NORIA-O release.

Sorry for the delayed response.
All changes are fine.
The KOS file however would still benefit the added default prefix declaration for the parsing issue, as such:

# --- NORIA ---
@base <https://w3id.org/noria/ontology/kos/> .
@prefix : <https://w3id.org/noria/ontology/kos/> .
@prefix noria: <https://w3id.org/noria/ontology/> .

# === Basic scheme ============================================================

Do you see any issue with this ?