-
Notifications
You must be signed in to change notification settings - Fork 303
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
Basic prep fix 1 #1801
Basic prep fix 1 #1801
Conversation
Using XML Date format instead of Internet Date format for Solid-PREP Notifications.
Swapped the `object` and `target`/`origin` properties in case of `Add`/`Delete` notifications respectively.
+ Notifications are identified by UUIDs. + Turtle notification template has the same fields as JSON-LD. + `notify:state` transmits Event-ID (which uniquely identifies a resource's state) and not E-Tag (which identify representations of the resource). + Parent reuses the generated Event-ID.
+ Event-ID is generated in PREP notification middleware itself. + No longer setting `Event-ID` response header upon resource mutation, thus reverting the middlewares for unsafe methods to their original state, before PREP was introduced.
Change the CI node-version to use caret range to ensure that tests are run on Node.js v20.
Values for `as:object`, `as:target` and `as:origin` predicates in the Turtle PREP-Notification template are IRI's, so they must be wrapped in angle brackets. Co-authored-by: Sarven Capadisli <[email protected]>
LGTM |
Just waiting for @csarven to check the final commit. |
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.
I don't quite understand this PR given #1800 . I reviewed it already. What's different here?
Nothing. @bourgeoa prefers it this way, as it allows him to run CTH with solidcommunity.net when the branch is in the repo. And then he merges that. |
Yes but not only. |
No description provided.