You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

I. "Simple" Use-Case: Access to versions is dictated by ACL of the original resource

Requirements:

  • The applicable ACL for a resource can be located by any of the methods described in Sec. 5 of the Fedora Specification (which relies on SOLIDWEBAC):
    • directly attached to the resource
    • determined by inheritance (via ldp:contains)
    • the repository default (if no applicable ACL is found)
    • [and possibly determined by inference? (i.e. accessToClass)]
  • When versions are created, the ACL of the parent resource applies also to the versions
  • Throughout the lifecycle of the versions, the applicable ACL continues to by the ACL of the parent
    • if the ACL itself is changed, the authorizations for the parent resource and all versions would change
    • if the ACL that applies to the parent resource changes (through any of the methods for determining the applicable ACL described above), the ACL that applies to all versions should also change

Examples:


  • No labels