Feature 320 atid

[Ludee]

Summary of the discussion

Update the @id fields to simple "id".
The databus @id is unchanged.

Type of change (CHANGELOG.md)

Changed

• Update @id fields to id (#)

Workflow checklist

Automation

Closes #320

PR-Assignee

• 🐙 Follow the workflow in CONTRIBUTING.md
• 📝 Update the CHANGELOG.md
• 📙 Update the documentation
• 🐙 Assign a reviewer to the PR

Reviewer

• 🐙 Follow the Reviewer Guidelines
• 🐙 Provided feedback and show sufficient appreciation for the work done

[Cpprentice]

I left some comments that might need changes to the context.json file.

Also I think we have to clarify the difference between path and id on top level.

[Cpprentice]

Shouldn't we also modify this id field?

[Cpprentice]

This compares to the previous @id field in the sense that it is meant for the OEP table while the other relates to the databus?

How would this be filled for datasets that are neither on the databus nor the OEP?

[Cpprentice]

I guess we need to modify the context.json as well if we add the new path property here.

Path currently has several definitions depending on the nested context:

# review context (alias)
"path": "@id"      # this means whatever contains the path keyword gets the value as its iri


# global context (property declaration)
"path": {        # in comparison to the above comment, this defines a property whose value becomes an iri
      "@id": "dcat:accessURL",
      "@type": "@id"
    }


# resource context
"path": {
          "@id": "dct:identifier",
          "@type": "xsd:string"
}

# context of sources, sourceLicenses, and resourceLicenses
"path": {
          "@id": "dcat:accessURL",
          "@type": "xsd:anyURI"
        }

If we have at least one @id alias in the top level the entire metadata descriptor would get an IRI otherwise it is a blank node. Both are fine we should just properly think about how we handle both

"id" and "path" in that regard. I am not 100% sure what happens if we identify one of them as alias for @id and the value is not filled.

[Cpprentice]

The context.json currently only has this definition for "id" (it is in the global scope):

 "id": {
      "@id": "dct:identifier",
      "@type": "xsd:anyURI"
    }

I assume we rather need to alias it now:

"id": "@id"

Also I did not found any occurrence of a mere "id" field (without the @) in the previous schema.json so maybe the above can simply be replaced without further issues.

[Cpprentice]

I will have a look into the occurrences of path and id to see if we need more detailled disambiguation.
Updates will be pushed onto the branch for this pull request directly.

We want to use dcat:landingPage whenever possible for a path.