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

Mis-defined Prefixes #13

Closed
VladimirAlexiev opened this issue Sep 12, 2024 · 2 comments
Closed

Mis-defined Prefixes #13

VladimirAlexiev opened this issue Sep 12, 2024 · 2 comments
Assignees
Labels
ontology Pertains to ontology representation

Comments

@VladimirAlexiev
Copy link
Collaborator

VladimirAlexiev commented Sep 12, 2024

There are a couple of problems with prefixes:

@prefix dct      : <http://purl.org/dc/terms/> .
@prefix dcterms  : <http://purl.org/dc/terms/#> .
  • For consistency, only dct should be used (which is the more popular spelling), not dcterms

This below is an expected issue, and will cause confusion if all ontologies are used together:

  • The CIM and CGMES "business" prefixes are defined twice.
    This comes from the RDFSEd2Beta style (used for CGMES) vs RDFS2020 style (used for CGMES NC)
@prefix cim      : <http://iec.ch/TC57/CIM100#> .
@prefix cim      : <https://cim.ucaiug.io/ns#> .
@prefix eu       : <http://iec.ch/TC57/CIM100-European#> .
@prefix eu       : <https://cim.ucaiug.io/ns/eu#> .
dm: <http://iec.ch/TC57/61970-552/DifferenceModel/1#> .
dm: <https://ap-voc.cim4.eu/DatasetMetadata#> .
eumd: <https://cim4.eu/ns/Metadata-European#> .
@VladimirAlexiev VladimirAlexiev added the ontology Pertains to ontology representation label Sep 13, 2024
@griddigit-ci
Copy link
Collaborator

Maybe you wanted to say dct instead of dcterms.
We found some references where it was recommended to use dcterms instead of dct

DCAT 3 - recently W3C Recommendation refers it as dcterms https://www.w3.org/TR/vocab-dcat-3/#normative-namespaces

We only had to put # at the end for all namespaces because we have tooling issue. Once we have the spec and align the tooling we will need to use / and # as it comes from the original namespace

I understood that there is a tendency to abandon # but I see in the DCAT they kept it. I guess what we want to achieve here is to be able to do our RDFS using original namespaces by W3C and fix tooling

@VladimirAlexiev
Copy link
Collaborator Author

  • yes, I mean dcterms not dcat
  • if DCAT uses dcterms then ok, use that, and don't use dct (it's important to be consistent)
  • You absolutely must use correct external namespaces: cannot add #
  • Hash vs slash: using # for ontology terms is ok. For large collections of things you should use /

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

No branches or pull requests

3 participants