Versions Compared

Old Version 4

changes.mady.by.user Ben Pennell

Saved on

compared with

New Version 5

changes.mady.by.user Bethany Seeger

Saved on

Key

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

...

https://tools.ietf.org/html/rfc7089#section-7


Design thoughts

Here are a few ways that ACLS and versions of resources might interact.   Ideas and use cases are welcome, especially if you have a certain way in which you might expect ACLs and Versioning to behave.

  1. Ignore any ACL on a versioned resource; instead honor the ACL that the LDPRCv has.  Essentially the versioned resource 'inherit' the ACL from the version container (LDPRCv aka. TimeMap). 
    1. If the LDPRCv has no ACL - default back to the Original Resource??  Or perhaps the LDPRCv points to some sort of default ACL?
    2. This scenario allows for the Original Resource to potentially have a separate ACL from the versions of itself. 
  2. Any versioned resource always has the same ACL as the Original Resource.  In other words, the ACL on the Original Resource always applies to all versions of the resource. If the ACL is changed or updated on the Original Resource, all the versions then have that same change/update.  The ACL would be stored and referenced from the Original Resource (not stored in the versions). 
  3. When a LDPR is versioned, honor the ACL that's on the versioned resource that was there at the time the version was created.
    1.  If the URL of the ACL pointed to never changes, then all the versions will have the same ACL restrictions as the Original Resource. 
    2.  If the URL of the ACL pointed to changes over time, then the versions may have different ACL restrictions, from both each other and the Original Resource.
    3. This scenario gets complicated quickly, especially when an ACL that's on a version, but no longer on the Original Resource, gets removed from the system.