manifest with rdf action model, revised with additional tests as per …#324
Draft
manifest with rdf action model, revised with additional tests as per …#324
Conversation
afs
reviewed
Apr 16, 2026
|
|
||
| <> rdf:type mf:Manifest ; | ||
| rdfs:label "SPARQL Protocol" ; | ||
| rdfs:label "SPARQL 1.2 Protocol" ; |
Contributor
There was a problem hiding this comment.
This is in the sparql11 directory.
Author
There was a problem hiding this comment.
the 1.1 directory should not be the eventual destination.
that context just makes it easier to understand it in relation to the previous version.
Contributor
There was a problem hiding this comment.
Maybe indicate that, such as set the PR to "draft".
As it is, the PR is a proposal to change in-place.
…orm; revise acceptance to NotClassified
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
…requirements.md
this follows on to the version which i had described at the beginning of february.
the reaction then was to prefer that the test notation be uniformly rdf, rather than a combination of rdf and javascript.
in the interim gregory revised the existing 1.1 version to incorporate gregg's approach.
this version extends gragory's version.
it introduces a requirements document which was generated from the draft recommendation.
most prominent among that are test which exercise the version information.
it then add several tests which follow form those requirements.