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

CIM WG Maintenance Request - Support DCAT3 #47

Open
Sveino opened this issue Jun 19, 2023 · 4 comments
Open

CIM WG Maintenance Request - Support DCAT3 #47

Sveino opened this issue Jun 19, 2023 · 4 comments
Labels
DCAT3 Chanegs realted to transition to DCAT version 3

Comments

@Sveino
Copy link
Collaborator

Sveino commented Jun 19, 2023

Description of issue:
Dataset version handling is very important. This is now addressed in DCAT-3 and our Metadata specification should rely on DCAT-3 so that we can easier implement support for Common Energy Data Space.
This change request is addressing the particular need from CSA and are therefor just adding the additional attributes that is needed without evaluating other elements.

Proposed resolution

  • Suggest to make the following updates:

  • Update line 161 to refer to DCAT-3.

  • Update Figure 3 by removing time (it is no longer used) and update the diagram with the changes done on the attributes.

  • Update Figure 7 based on the update done on the attribues

  • Update the following attributes in Table 2:

    • Change hasCurrentVersion from String to IRI and it shall be serielized as rdf:resource.
    • Change isVersionOf from String to IRI and it shall be serielized as rdf:resource.
    • Change previousVersion from String to IRI and it shall be serielized as rdf:resource.
    • Change wasGeneratedBy form 0..n to 0..1
    • Should considere changing the following from String to stringIRI and it shall be serilized as literal.
      • dcterms:license
      • dcterms:rights
      • dcterms:rightHolder
  • Add the following attributes:

    • All IRI shall be serielized as rdf:resource
name mult type description
issued 0..1 Date
title 0..1 String
spartial 0..1 IRI

Need to add the addtional fields.

@Sveino
Copy link
Collaborator Author

Sveino commented Jun 19, 2023

Must update the Header and metadata list.xlsx (entsoe.eu)

@Sveino
Copy link
Collaborator Author

Sveino commented Jul 3, 2023

For the item:

Should consider changing the following from String to stringIRI and it shall be serialized as literal.
dcterms:license
dcterms:rights
dcterms:rightHolder

DIGIN is proposing the following:

    "dcterms:rights": "© 2023 Copyright",
    "dcterms:rightsHolder": "DIGIN",
    "dcterms:license": {
        "@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/",
        "dcterms:title": "CC BY-NC-SA 4.0"
    },

Since JSON-LD support compound we can include both the "dcterms:title": "CC BY-NC-SA 4.0" and "@id": "https://creativecommons.org/licenses/by-nc-sa/4.0/"

dcterms:license could be exchange as:

    <dcterms:license>
      <rdf:Description rdf:about="https://creativecommons.org/licenses/by-nc-sa/4.0/">
        <dcterms:title rdf:datatype="http://www.w3.org/2001/XMLSchema#string">CC BY-NC-SA 4.0</dcterms:title>
      </rdf:Description>
    </dcterms:license>

I propose that we have String for rights and rightsHolder and stringIRII for License and we only include the URI.

@Haigutus Haigutus added the DCAT3 Chanegs realted to transition to DCAT version 3 label Jul 3, 2023
@Haigutus
Copy link
Owner

Haigutus commented Jul 3, 2023

Relevant links from DCAT3:
https://www.w3.org/TR/vocab-dcat-3/#license-rights
https://www.w3.org/TR/vocab-dcat-3/#Property:resource_license
https://www.w3.org/TR/vocab-dcat-3/#Property:distribution_license

DCAT3 recommendation is to use IRI, witch can tehn be URN or URL. This would mean:

  1. In case of open licence, use URL defined here https://creativecommons.org/about/cclicenses/
  2. In case custom/internal licence/contract, create a unique URN on internal URL

Resolvability:
In case of IRI, the resource is not expected to be available within the same resource, will be dangling reference in most cases
In case it is URL, it does not need to resolvable

Serialization:
Shall be IRI. Meaning in case of RDF/XML it is in the xml object with tag rdf:resource and in case of JSONLD @id

@Haigutus
Copy link
Owner

Haigutus commented Jul 3, 2023

Comment on using Compounds:

  1. Help users to get access to most relevant information of a resource without resolving it
  2. The main source is still available at the source ID
  3. Compound may not be up to date
  4. Compound may contain only some of the original resource attributes (usually only the ones that are most relevant to receiver)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DCAT3 Chanegs realted to transition to DCAT version 3
Projects
None yet
Development

No branches or pull requests

2 participants