-
Notifications
You must be signed in to change notification settings - Fork 44
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
[New Work Item Proposal] Solid-PREP #580
Comments
Internet Draft version of PREP can be found here https://github.com/Cxres/prep. This will replace the W3C draft while the specification is under consideration of IETF. The only change (of relevance to Solid-PREP) is that Appendix A is now Section 10. |
I should have mentioned here that I already have my own Draft of Solid-PREP already available here: |
I will add myself as a co-author, so this work item will have two active participants. |
Accepted as a work item by Solid-CG! |
[Introduction copied from the Draft]
Per Resource Events is a minimal protocol built on top of HTTP that allows clients to receive notifications directly from a resource of interest. Unlike other HTTP based solutions, Per Resource Events Protocol supports the use of arbitrary media-types for notifications, which can be negotiated just like representations; thus giving implementers a lot of flexibility to customize notifications according to the needs of their application.
PREP will compliment Solid Notifications Protocol (SNP) by providing a lightweight alternative with identical notification semantics where a client wishes to receive notifications directly from a resource, say on a Solid POD, using
Fetch
. SNP will continue to serve the more general cases, such as, where clients wish to receive notifications from many resources over a single connection, and/or prefer other protocols such as WebSockets and Webhooks.I plan on submitting an Internet Draft of PREP to IETF (hopefully, this week itself). Therefore, I want to propose a Solid-PREP work item with the following agenda items:
Fetch
with one extra header).The aim is that the Solid-CG will incubate these deliverables till they are ready to be adopted by the imminent Solid-WG.
The text was updated successfully, but these errors were encountered: