Versions Compared

Key

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

...

  1. There seems to be consensus that the purpose of this effort is to provide an implementation of the Memento protocol in Fedora. Whether there would be some future extension of Memento remains an open question. Discussions are ongoing.
  2. Open issue: Whether a "versions container" is the main locus of versioning activity or whether version creation is better understood as an action against the resource being versioned itself. See section 7 of the draft.
    1. One option is to leave the interaction model open in the specification, and instead merely make the demand that a particular implementation of the spec be explicit about the model(s) being employed.
    2. No explicit objections were raised to this approach. Three possible interaction models (there could be others) under this approach might be: 
      1. Model 1: POST some change to a resource; server creates a new version resource in the versions container.
      2. Model 2: read-only versions container; POST with empty body creates a server-managed resource in that container.
      3. Model 3: provide a earlier version of a resource in the body of a request.
    3. Discoverability would be facilitated by the options feature of LDP.  There would be a need for a way to advertise whether versions/versioning are available for a particular resource.