...
- Modeshape impl: supports acl:Read and acl:Write
- Spec: Also includes support for acl:Append and acl:Control
- https://github.com/fcrepo/fcrepo-specification/issues/170
- Modeshape impl: uses 'acl:agent foaf:Agent' to denote public access
- Spec: uses 'acl:agentClass foaf:Agent' to denote public access
- https://github.com/fcrepo/fcrepo-specification/issues/169
- Modeshape impl: uses acl:agentClass to reference foaf:Group containing foaf:member(s)
- Spec: uses acl:agentGroup to reference vcard:Group containing vcard:hasMember(s)
- https://github.com/fcrepo/fcrepo-specification/issues/167
- Modeshape impl: uses strings or URIs for acl:Agent objects
- Spec: uses WebIDs, but we will specify the use of URIs for acl:Agent objects
- https://github.com/fcrepo/fcrepo-specification/issues/166
- Modeshape impl: if an ACL is not defined on a given resource, the ACL on the closest parent container is applied
- Spec: has the same functionality only if an ACL on a parent is marked with acl:defaultForNew (to be changed to acl:default)
- https://github.com/fcrepo/fcrepo-specification/issues/164
Modeshape impl: uses 'acl:accessToClass' for targeting all resources with a given rdf:type valueSpec: Do not use acl:accessToClass, per the SOLIDWAC recommendation
Messaging
- Summary: The format for the messages will change to JSON-LD and message content should be extended to include more metadata about the changed resource
- https://github.com/fcrepo/fcrepo-adopters-guide/blob/master/docs/messaging.md
- Emit message for synthetic triples added/removed
- Emit message for each resource deleted in a hierarchy
- 6.3
- uses JSON-LD format for serialization
- The notification serialization must conform to the [activitystreams-core] specification.
- Wherever possible, data should be expressed using the [activitystreams-vocabulary].
- Headers will no longer be supported.
- Examples of messages:
- minimal: https://fcrepo.github.io/fcrepo-specification/#minimal-notification-example
- with additional information: https://fcrepo.github.io/fcrepo-specification/#basic-notification-example