Skip to content

ci(shacl): add shape validation for sample data#59

Open
arcangelo7 wants to merge 2 commits into
skg-if:mainfrom
arcangelo7:main
Open

ci(shacl): add shape validation for sample data#59
arcangelo7 wants to merge 2 commits into
skg-if:mainfrom
arcangelo7:main

Conversation

@arcangelo7

Copy link
Copy Markdown

No description provided.

@rduyme

rduyme commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator

@vicding-mi do you have time to check the PR ? see also #58 for context.

@vicding-mi vicding-mi Jun 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure whether the submodule can trigger the action pipeline. Please kindly elaborate. The push or pr would update the pointer in the parent repository, but files in sub-folder might not be enough to trigger the pipeline.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. What about filtering on the gitlink path itself, data-model, instead of the sub-folder? A push/PR that bumps the pointer changes exactly that path, so the workflow fires (tested here https://github.com/orgs/community/discussions/66060).

That means validation runs whenever we bump the submodule here, which is the moment we actually want to re-check the sample data against the new shapes. It won't run if the shapes change upstream without a pointer bump.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file does not need the api spec (yaml) to run. It checks sample data against shacl.ttl (which is included as git submodule). Is shacl.ttl derivation of the openapi specs? Am I missing some context?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OpenAPI check and SHACL check are two separate jobs in this workflow. I added the SHACL step leaving the preexisting OpenAPI job untouched

@vicding-mi

Copy link
Copy Markdown
Contributor

@rduyme I checked the code base with @arcangelo7 . Can you please take over and proceed? I have read-only access, cannot approve the merge.

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.

3 participants