Closed VladimirAlexiev closed 2 months ago
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
dcterms
not dcat
dcterms
then ok, use that, and don't use dct
(it's important to be consistent)#
#
for ontology terms is ok. For large collections of things you should use /
There are a couple of problems with prefixes:
dcterms
is wrong (has exraneous hash), as you can see at https://prefix.cc/dcterms:dct
should be used (which is the more popular spelling), notdcterms
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) vsRDFS2020
style (used for CGMES NC)dm
is used for two different purposes. And there's alsoeumd
: https://github.com/Sveino/Inst4CIM-KG/issues/69