-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
Maybe you wanted to say dct instead of dcterms. 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 |
|
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:
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
: merge and fix DatasetMetadata, Header, FileHeader #69The text was updated successfully, but these errors were encountered: