The SHACL for the FDP metadata in v1.2 has a few inconsistencies w.r.t. the definition in the [metadata schema table]:
missing sh:maxCount value (should be 1) actually the whole dct;hasVersion is not mentioned in the FDP table:
- ambiguity in definition of
fdp-o:metadataIdentifier property:
|
], [ |
|
sh:path fdp-o:metadataIdentifier ; |
|
sh:nodeKind sh:IRI ; |
|
sh:maxCount 1 ; |
|
sh:minCount 1 ; |
|
], [ |
vs
|
], [ |
|
sh:path fdp-o:metadataIdentifier ; |
|
sh:datatype xsd:dateTime ; |
|
sh:maxCount 1 ; |
|
sh:minCount 1 ; |
|
], [ |
the latter should probably be fdp-o:metadataModified, according to the table in 4.2.1
- wrong prefix for
conformsToFdpSpec (dct should be fdp-o):
|
sh:path dct:conformsToFdpSpec ; |
- the SHACL file defines a
FAIRDataPointContainerShape but does not use it, nor does the spec provide a clear indication of how to use it
|
:FAIRDataPointContainerShape a sh:NodeShape ; |
The "example" suggests the FDP itself is not an LDP container, and the catalog container is a completely separate resource, only connected to the FDP via the ldp:membershipResource predicate:
|
<https://purl.org/fairdatapoint/app/catalog/> a ldp:DirectContainer ; |
|
dct:title "Catalogs" ; |
|
ldp:membershipResource <https://fairdatapoint.org/app> ; |
- the SHACL shape requires at least one
fdp-o:metadataCatalog to be present, but this predicate is not mentioned at all in the [metadata schema table] (only in the LDP table). Moreover, the cardinality implies we're not allowed to create an empty FDP and would need to create a placeholder catalog instead (e.g. the reference implementation does not comply)
|
], [ |
|
sh:path fdp-o:metadataCatalog ; |
|
sh:node :CatalogShape ; |
|
sh:minCount 1; |
|
], [ |
dcat:endPointDescription is in the table but is missing from the SHACL
[metadata schema table]: https://github.com/fdp-specs/fdp-specs.github.io/blob/5e122bf192b431afe5034c71379f8522e1cbb227/src/tables/table-fdp-metadata.html
The SHACL for the FDP metadata in v1.2 has a few inconsistencies w.r.t. the definition in the [metadata schema table]:
missingactually the wholesh:maxCountvalue (should be 1)dct;hasVersionis not mentioned in the FDP table:fdp-specs.github.io/src/rdf/shacl-fdp.ttl
Line 19 in 5e122bf
fdp-o:metadataIdentifierproperty:fdp-specs.github.io/src/rdf/shacl-fdp.ttl
Lines 72 to 77 in 5e122bf
vs
fdp-specs.github.io/src/rdf/shacl-fdp.ttl
Lines 82 to 87 in 5e122bf
the latter should probably be
fdp-o:metadataModified, according to the table in 4.2.1conformsToFdpSpec(dctshould befdp-o):fdp-specs.github.io/src/rdf/shacl-fdp.ttl
Line 88 in 5e122bf
FAIRDataPointContainerShapebut does not use it, nor does the spec provide a clear indication of how to use itfdp-specs.github.io/src/rdf/shacl-fdp.ttl
Line 112 in 5e122bf
The "example" suggests the FDP itself is not an LDP container, and the catalog container is a completely separate resource, only connected to the FDP via the
ldp:membershipResourcepredicate:fdp-specs.github.io/src/rdf/example-metadataservice.ttl
Lines 21 to 23 in 5e122bf
fdp-o:metadataCatalogto be present, but this predicate is not mentioned at all in the [metadata schema table] (only in the LDP table). Moreover, the cardinality implies we're not allowed to create an empty FDP and would need to create a placeholder catalog instead (e.g. the reference implementation does not comply)fdp-specs.github.io/src/rdf/shacl-fdp.ttl
Lines 23 to 27 in 5e122bf
dcat:endPointDescriptionis in the table but is missing from the SHACL[metadata schema table]: https://github.com/fdp-specs/fdp-specs.github.io/blob/5e122bf192b431afe5034c71379f8522e1cbb227/src/tables/table-fdp-metadata.html