Skip to content

Fixed inconsistencies in FDP SHACL#33

Open
dennisvang wants to merge 16 commits intodevelopmentfrom
fix/shacl-inconsistencies
Open

Fixed inconsistencies in FDP SHACL#33
dennisvang wants to merge 16 commits intodevelopmentfrom
fix/shacl-inconsistencies

Conversation

@dennisvang
Copy link
Copy Markdown
Contributor

@dennisvang dennisvang commented Apr 20, 2026

Fixed inconsistencies between FDP SHACL file and corresponding tables.
See commit messages below for details.

fixes #30

TODO:

@dennisvang dennisvang marked this pull request as draft April 20, 2026 06:59
@dennisvang dennisvang changed the title Fix inconsistencies in SHACL for FDP and Catalog Fix inconsistencies in SHACL for FDP Apr 20, 2026
@dennisvang dennisvang force-pushed the fix/shacl-inconsistencies branch from b14d8cf to c8e4a58 Compare April 20, 2026 10:00
@dennisvang dennisvang marked this pull request as ready for review April 20, 2026 10:02
@dennisvang
Copy link
Copy Markdown
Contributor Author

Question for future version: should we also specify that the DCAT parent classes need to be made explicit, as they are in the reference implementation?

As it is now, inference is required in order to know that an fdp-o:FairDataPoint is also an fdp-o:MetadataService, dcat:DataService, and dcat:Resource.

@dennisvang dennisvang changed the title Fix inconsistencies in SHACL for FDP Fixed inconsistencies in FDP SHACL Apr 20, 2026
@dennisvang
Copy link
Copy Markdown
Contributor Author

Replacing https://www.purl.org/fairtools/fdp/schema/0.1/ by https://purl.org/fairdatapoint/ following Luiz's changes:

dct:conformsTo <https://purl.org/fairdatapoint/app/profile/77aaad6a-0136-4c6e-88b9-07ffccd0ee4c>;

because it is not in the table
because this is in the table
that's what it should be, based on table and datatype
based on table
to match the table
for consistency and clarity

although the textual definition in SHACL, section 4.1.2, says datatype validation fails if the value node is not a literal, it is better to be explicit
this property was not mentioned in the table yet

todo: decide if cardinality should be 0..* or 1..*
todo: improve description in table
now the order matches that of the generated statement: <membership-resource> <has-member-relation> <contains>

this is also consistent with the order in the shacl file
- consistent use of prefixes
- dont mix purl with fairdatapoint.org
- rearrange to match order of shacl (for convenience)
- remove dct:description (optional)
- remove dct:hasVersion (not in shacl)
- add fdp-o:conformsToFdpSpec (required)
- add dcat:endPointURL (required)

todo:

- http://rdflicense.appspot.com does not resolve
- https://www.purl.org/fairtools/fdp/schema/0.1/ does not resolve
following Luiz's example
@dennisvang dennisvang force-pushed the fix/shacl-inconsistencies branch from 2c3f135 to 025de71 Compare April 20, 2026 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FDP SHACL inconsistencies

1 participant