-
Notifications
You must be signed in to change notification settings - Fork 39
feat: Implement sequence processing improvements for SHACL Node Expressions (Issue #484) #526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Committing for grammar remarks, but this does not visit the topic raised about whether there officially exists a "SHACL 1.1". Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
…atMap, findFirst, matchAll)
…cification and examples
… shnex:remove in spec, examples, and vocabulary
SHACL Overview, what's new
Co-authored-by: Alex Nelson <[email protected]>
* #505: Added section on Dynamic SHACL, including two examples * Apply suggestions from code review Co-authored-by: Alex Nelson <[email protected]> * Apply suggestions from code review Co-authored-by: Ted Thibodeau Jr <[email protected]> * Update shacl12-node-expr/index.html Co-authored-by: David Habgood <[email protected]> * Update shacl12-node-expr/index.html Co-authored-by: David Habgood <[email protected]> * Update shacl12-node-expr/index.html Co-authored-by: Ted Thibodeau Jr <[email protected]> --------- Co-authored-by: Alex Nelson <[email protected]> Co-authored-by: Ted Thibodeau Jr <[email protected]> Co-authored-by: David Habgood <[email protected]>
Added style.css to core too
* Define support for property paths in SHACL UI * Remove targets from the examples Apply suggestions from code review Co-authored-by: Thomas Bergwinkl <[email protected]> * Add notes on restrictions and challenges * Add shape example to "Other Complex Paths" subsection * Don't put RFC2119 keywords in bold * Replace repetitive RFC2119 keywords --------- Co-authored-by: Thomas Bergwinkl <[email protected]>
Co-authored-by: Ieben Smessaert <[email protected]>
Issue 537 UI widgets
added sh:conformanceDisallows, updated conformance-definition
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
… MatchAll expressions
…e between sh:path and shnex:pathValues
… shnex:remove in spec, examples, and vocabulary
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
|
@TallTed @HolgerKnublauch I now rebased this PR onto gh-pages (and hopefully haven't broken anything in the process of doing so) @TallTed I've applied your 3 suggestions, thx! |
|
Thanks @simonstey! The branch seems to be on the wrong base though - it displays 115 changed files and 147 commits. Maybe the easiest way forward is to create a new branch that only overwrites the node-expr doc? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, I guess that's the better approach
|
I'll close this PR in favor of #636 |
This pull request implements comprehensive changes to address Issue #484 regarding sequence processing naming inconsistencies in SHACL Node Expressions. The changes align the vocabulary and documentation with the sequence-based nature of node expression processing while maintaining backward compatibility through deprecation notices.
Problem Statement
SHACL Node Expressions are fundamentally sequence-based but were using set-style operation names, creating confusion:
unionandminussuggested set semantics despite working on ordered sequencespathproperty conflicted conceptually with constraintsh:pathSolution
1. Vocabulary Renaming for Sequence Semantics
Renamed Operations:
shnex:union→shnex:join- Emphasizes sequence concatenation with order preservationshnex:minus→shnex:remove- Clearer operation name for sequence subtractionshnex:path→shnex:pathValues- Distinguishes from constraintsh:path(needs to align with Rename shnex:path to shnex:pathValues and change its shnex:nodes to shnex:focusNode #514 )Deprecation Strategy:
shacl.ttlwith deprecation notices forsh:unionandsh:minus2. Advanced Sequence Operations
New Operations Added:
shnex:flatMap- Applies expression to each input node and flattens resultsshnex:findFirst- Returns first node conforming to a given shapeshnex:matchAll- Returns true if all nodes conform to a given shapeFiles Modified
Vocabulary Files
shacl12-vocabularies/shnex.ttlshacl12-vocabularies/shacl.ttlsh:unionandsh:minusDocumentation
shacl12-node-expr/index.htmlNew Advanced Operations:
Closes #484