Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand

6.1 Notification Events 

  • (tick) For every resource whose state is changed as a result of an HTTP operation, there must be a corresponding notification made available describing that change.

6.2 Notification Serialization 

  • (tick) The notification serialization must conform to the [ activitystreams-core ] specification.
  • (tick) Wherever possible, data should be expressed using the [ activitystreams-vocabulary ].
  • Each event described by a notification must contain:
    • (question)(tick)The IRI of the resource that was created, modified or deleted
    • (tick) The event type(s) corresponding to the HTTP operation
  • Each event described by a notification should contain:
    • (tick) The agent(s) that caused the change to occur
    • (tick) The RDF type(s) of the resource that was changed
    • (minus) The location of the ldp:inbox for the resource that was changed, if such an inbox link exists
  • (tick) Notifications should not contain the entire content of repository resources.

6.3 Examples

  • Non-normative section

...