Field cardinality in generated form is incorrect when using DCAT-AP 3.0.0 shapes.

[kburger]

In DCAT-AP 3.0.0 the property shape constraints are split into separate instances, where each instance defines a constraint on the target sh:path. For example, the cardinality is separated from a datatype constraint. The resulting generated form in the client is not in sync with the underlying shapes.

As an example:

<https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecordShape> a shacl:NodeShape;
  shacl:closed false;
  shacl:property <https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecordShape/1c4ac0cf94e6a9152035ed86f73590b6b516dfef>,
    <https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecordShape/4b28ec6b7000fa7ccd38127f115952dd990d7d9c>,
    <https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecordShape/8c70e4513eeeeacaf9fdbc9e2cf3df16973e24c0>;
  shacl:targetClass dcat:CatalogRecord .

<https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecordShape/1c4ac0cf94e6a9152035ed86f73590b6b516dfef> rdfs:seeAlso "https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecord.changetype";
  shacl:description "The status of the catalogue record in the context of editorial flow of the dataset and data service descriptions."@en;
  shacl:maxCount 1;
  shacl:name "change type"@en;
  shacl:path <http://www.w3.org/ns/adms#status>;
  <https://purl.eu/ns/shacl#message> "Maximally 1 values allowed for change type"@en .

<https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecordShape/4b28ec6b7000fa7ccd38127f115952dd990d7d9c> rdfs:seeAlso "https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecord.changetype";
  shacl:class skos:Concept;
  shacl:description "The status of the catalogue record in the context of editorial flow of the dataset and data service descriptions."@en;
  shacl:name "change type"@en;
  shacl:path <http://www.w3.org/ns/adms#status>;
  <https://purl.eu/ns/shacl#message> "The range of change type must be of type <http://www.w3.org/2004/02/skos/core#Concept>."@en .

<https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecordShape/8c70e4513eeeeacaf9fdbc9e2cf3df16973e24c0> rdfs:seeAlso "https://semiceu.github.io//DCAT-AP/releases/3.0.0#CatalogueRecord.changetype";
  shacl:description "The status of the catalogue record in the context of editorial flow of the dataset and data service descriptions."@en;
  shacl:name "change type"@en;
  shacl:nodeKind shacl:BlankNodeOrIRI;
  shacl:path <http://www.w3.org/ns/adms#status>;
  <https://purl.eu/ns/shacl#message> "The expected value for change type is a rdfs:Resource (URI or blank node)"@en .

Maybe shape organised this way should be merged based on sh:targetClass and sh:path? But then messages are combined as well, resulting in information loss. To counter that, maybe they could be combined with sh:and dynamically at validation time?