Skip to content

#222, #288: Update SHACL-SHACL for general NodeExpression and SelectExpression#302

Draft
ajnelson-nist wants to merge 6 commits into
gh-pagesfrom
issues-222-288-shacl-shacl
Draft

#222, #288: Update SHACL-SHACL for general NodeExpression and SelectExpression#302
ajnelson-nist wants to merge 6 commits into
gh-pagesfrom
issues-222-288-shacl-shacl

Conversation

@ajnelson-nist

Copy link
Copy Markdown
Contributor

This PR is built on a not-currently-merged state of #297 . 297 should be merged before this.

This PR is scoped to SHACL-SHACL updates specific to #222 and #288 . A group decision is not in place on by when this should be merged, or if it blocks PRs or Issues.

This PR is also in a draft status while updates are made over 6bf5a7c, in response to comments on this commit.

HolgerKnublauch and others added 4 commits March 4, 2025 11:15
…xpression

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
…lectExpression

This patch undoes commit 8632a3e.  This was done manually instead of with `git revert`.

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
…xpression

This is a re-application of commit 8632a3e, done so it can be reviewed
in a separate Pull Request.

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>

@TallTed TallTed left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

typo

Comment thread shacl12-vocabularies/shacl.ttl Outdated
HolgerKnublauch and others added 2 commits March 6, 2025 02:30
@ajnelson-nist

Copy link
Copy Markdown
Contributor Author

@TallTed , thanks for the peek at this PR. I hadn't intended to request review yet. The PR is intentionally in draft as I think through some syntax things and review some classes.

@ajnelson-nist

Copy link
Copy Markdown
Contributor Author

@TallTed , thanks for the peek at this PR. I hadn't intended to request review yet. The PR is intentionally in draft as I think through some syntax things and review some classes.

...Actually, I'm curious - did you actually comment on this PR (302), or did you just comment once on PR 297?

I'm curious if it was actually the latter, and GitHub did an interesting propagation.

@TallTed

TallTed commented Mar 10, 2025

Copy link
Copy Markdown
Member

@ajnelson-nist — I did comment directly on #302. The typo just caught my eye.

@afs

afs commented Jan 30, 2026

Copy link
Copy Markdown
Contributor

@ajnelson-nist -- status? (this is set as a "draft").

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants