Revise SHACL 1.2 Rules abstract #729
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -123,11 +123,21 @@ | |
| </head> | ||
| <body> | ||
| <section id="abstract"> | ||
| <p>This document defines <em>SHACL Rules</em>.</p> | ||
| <p> | ||
| SHACL, the Shapes Constraint Language, is a language for describing the structure | ||
| of RDF graphs. | ||
| SHACL may be used for a variety of purposes such as validating, inferencing, | ||
| modeling domains, generating ontologies to inform other agents, building user | ||
|
Contributor
There was a problem hiding this comment.
I know this is coming from SHACL-core, but: what other agents?!
Contributor
There was a problem hiding this comment. I picked that term for either humans or software agents such as LLMs. But since these software agents are currently changing on a weekly basis, I wanted to remain vague and not talk about AI agents.
Contributor
Author
There was a problem hiding this comment. I think "agents" will do for now. It is a WG task to craft some abstract text that can be used across all the documents. The core abstract is a good start. #729 (comment). I've created #747 for that. |
||
| interfaces, generating code, and integrating data. | ||
| </p> | ||
| <p> | ||
| SHACL Rules provides inferencing with the generation of new RDF data from a | ||
afs marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| combination of a set of rules and a base data graph. Rules can be expressed as RDF | ||
afs marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| or in the SHACL Rules Language (SRL). | ||
| <p> | ||
| This specification is published by the | ||
| <a href="https://www.w3.org/groups/wg/data-shapes/">Data Shapes Working Group</a>. | ||
| </p> | ||
| </section> | ||
|
|
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
inferencinghas long bothered me, and I am hoping it bothers others here, and maybe we can stop verbing the noun (inference) that was already a nouning of a verb (infer). Maybe we can just useinferring.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.
"Inferencing" is a technical term that is used in several fields, such as AI, and is used in the semantic web area.
e.g.
https://blog.okfn.org/2010/08/02/about-inferencing/
#215
Note: the wording for the rules abstract is based on:
https://www.w3.org/TR/shacl12-core/#abstract
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.
do we then actually need to copy SHACL Cores's abstract 1:1?
Uh oh!
There was an error while loading. Please reload this page.
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.
@simonstey -- I'm not sure which way to read your comment:
Are you saying we should take verbatim the SHACL Core?
Or that we should take none of it?
As pointed out the SHACL Core text emphases validation. It also puts that before the general text.
We don't have, yet, WG text that works for core, sparql, profiles, ui, rules, it is better to take what we can and adapt it for now. For example, it would be restructured to go put the general SHACL description in the main paragraph, then have a final short section to cover the specific document.
That will take awhile. This PR for a slightly better abstract, not the final one, given we know people are reading the live drafts.