...

1. Introductions (all)
   1. What is your current Fedora status?
   2. If you are not on F4, what are your migration/installation plans? What are your barriers?
2. Clarify distinction between NonRdfSource and its Description as one repository resource or two LDP resources
   1. Example, what are the implications of event messaging from actions on either "resource"?
3. Fedora API Specification
   1. Seeking initial agreement, followed by alignment of implementation to specification
4. ModeShape5, backend databases, and migrations
5. Atomicity in the Java kernel API
   
   1. Which methods on services and resource types are atomic and / or synchronous? This is going to matter to reimplementations that reuse the Java kernel API.)
6. Local implementations and/or implementation ideas, issues? priorities? (open forum)
   1. ...
7. <add topic here>

Minutes

Versioning

• When looking at a version that is a version of an original, is there a link to the original version?   Yes
• Most important thing is that a client understands if it a versioned resource or nor
• In the current implementation, if you look at a versioned resources, all links are to the snapshot version
  • Can be crawled by an LDP client that has no awareness of versioning mechanism
  • Links to resources in the version snapshot tree will be this way
  • Links to resources outside the versioned snapshot tree are to non-snapshot URI
    • So a client that is LDP-only client that is unaware of versioning semantics can escape the snapshot tree and not be aware of it
• The most consistent approach would be to link to canonical (current version URIs) always, have memento-aware client look for versions.
  • Could implement this using JCR in place currently
  • Representation of versioned resources and snapshots would be different
• Esme:  I thought there was some way to set versioning policy
  • Mike:  That was thrown out a year ago
• 7.2.2 is the default behavior in Fedora right now
• 7.3.3 would be the least challenging to implement right now
• Andrew:  How important are versioning to people right now
• Diego:  We need them right now, everything is incremental
• Sometimes versions can be in application logic, leave it as a separate concern from the repository.  May be dubious value to rely on repository versioning
• Different applications are going to have different notions of versioning.  Some use cases may consider different versions to be different resources entirely.
• Definitely some strong use cases for versioning as it is currently implemented now (and proposed in the spec),
• "I need the ontology (resource in the repository) that matches its state at X time in history"
• If one deletes the original version of a versioned resource, what happens to the version history?
  • Currently, If you version binary directly and delete it, you'll delete all versions.  If you if you have a binary in a container and version the container, deleting the binary will not delete the link to the binary for versions of the binary that are linked by cersions of the container (somebody please fact check and/or state this)