published cubes don't pass validation for schema:publisher, schema:creator nor schema:contributor

[Rdataflow]

published cubes don't pass validation for schema:publisher, schema:creator nor schema:contributor applied by https://github.com/zazuko/cube-link/blob/main/validation/standalone-cube-constraint.ttl

Describe the bug

• those attributes shall be consistently defined as required by the validation https://github.com/zazuko/cube-link/blob/main/validation/standalone-cube-constraint.ttl
  • alternatively: the validation may be adapted (always WRT to be consistent with opendata-swiss)

To Reproduce
Steps to reproduce the behavior:

npx barnard59 cube fetch-metadata --cube https://environment.ld.admin.ch/foen/besch_holz_inst_einheit_weniger4/20 --endpoint https://int.lindas.admin.ch/query | npx barnard59 cube check-metadata --profile https://cube.link/latest/shape/profile-visualize | npx barnard59 shacl report-summary

Observed Violation
Violation of MinCountConstraintComponent: "cube:Cube needs an schema:publisher" with path http://schema.org/publisher at focus node https://environment.ld.admin.ch/foen/besch_holz_inst_einheit_weniger4/20 (source: _:b88_b697)
Violation of MinCountConstraintComponent: "cube:Cube needs an schema:creator" with path http://schema.org/creator at focus node https://environment.ld.admin.ch/foen/besch_holz_inst_einheit_weniger4/20 (source: _:b88_b698)
Violation of MinCountConstraintComponent: "cube:Cube needs an schema:contributor" with path http://schema.org/contributor at focus node https://environment.ld.admin.ch/foen/besch_holz_inst_einheit_weniger4/20 (source: _:b88_b706)

Expected behavior
no violations

cc @ClaudioDiGallo

[Rdataflow]

@giacomociti considering

• cube-creator until now didn't publish these metadata entries
• the topic is still WIP WRT
  • https://gitlab.ldbar.ch/bafu/visualize/-/issues/656

I'd temporarily skip theese 3 predicates by commenting them rather than enforcing them until further clarification

cc @CDiGallo feel free to add your remarks and guidance

[CDiGallo]

Hi
Can we not just decide that we want it and add it as a warning?
So we do not forget.
Also: We propose it here as "optional" -> https://gitlab.ldbar.ch/BAR/governance/-/issues/22

@Rdataflow

[CDiGallo]

or +1 what thomas said

[Rdataflow]

whichever @CDiGallo prefers.
nb: @CDiGallo we need to keep in mind the condition in opendata-swiss profile as well
https://github.com/zazuko/cube-link/blob/a9cb254ef6ddaebfdb41aa4261b020cc40e97c67/validation/profile-opendataswiss.ttl#L25-L41
that validation there would fail with the current profile for being Literal while IRI or Blank would be accpepted

[giacomociti]

not sure what is the chosen solution then

[giacomociti]

I recap my understanding of the issue:

before publishing a cube, CC checks it with standalone-constraint-constraint (sh:targetClass cube:Constraint)

The online cube validator instead checks cubes with either standalone-cube-constraint, profile-opendataswiss or profile-visualize. Each of these profiles imports standalone-constraint-constraint and adds more shapes:

standalone-cube-constraint adds a shape (sh:targetClass cube:Cube) requiring an IRI value for schema:publisher, schema:creator and schema:contributor.

profile-opendataswiss adds a shape (sh:targetClass dcat:Dataset) requiring dcterms:publisher (IRI or blank foaf:Organization)

profile-visualize additional shapes don't require (yet) any publisher, creator, or contributor.

The problem is that cubes created with CC lack such properties. CC optionally allows setting dcterms:publisher (literal) and dcterms:creator (IRI)

My understanding is that, as a short-term solution, we can treat the missing properties as warnings. Later on, we can enhance CC. But if my understanding is correct, the changes should be applied to standalone-cube-constraint in the cube.link repo.

[giacomociti]

so I changed the severity in cube schema, see it in cube validator