...

• Danny Bernstein
• Esmé Cowles
• Jared Whiklo
• Kevin Ford 
• Longshou Situ 
• Jim Coble 
• David Wilcox
• A. Soroka
• Yinlin Chen 
• Daniel Lamb 
• Benjamin Armintor
• Karen Estlund
• Dan Coughlin
• Nick Ruest
• Michael Durbin
• Ralf Claussnitzer
• Bethany Seeger
• Mark A. Matienzo
• Unknown User (acoburn)
• Aaron Birkland
• Elliot Metsger
• Stefano Cossu
• Doron Shalvi
• Andrew WoodsSimeon Warner

Agenda

1. Introducing Cavendish
2. Introducing Trellis
3. Motion for decision: Should the subject of triples in auto-created LDP-RS (/fcr:metadata) be the LDP-RS or the LDP-NR it describes (the binary)?
   1. See: 

      Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2396

4. Open fcrepo-specification issues
5. Deprecation of RBACL and XACML authorization modules?
6. ...

7. Status of "in-flight" tickets

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13202 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

...

1. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

3. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

Minutes

Trellis

Unknown User (acoburn)'s alternate Fedora implementation.  Built to be horizontally scalable.  Here's the big differences: 

• Views FedoraResources as a stream of operations, and are stored as a journal or commit log.
• Everything is asynchronous.
• No server managed triples.  Everything that would be viewed as such are provided as HTTP headers. 
• LDP resource types are not persisted as triples.
• Audit will be done with a header, to request the audit triples for a resource.
• Versioning is automatic, and you don't create or delete them.  You can request the representation at any point in time of its history.
• Built with drop-wizard, and is containerless.
• No MOVE, or COPY operations
• No referential integrity constraints
• No tombstones
• Users/agents must be described with URIs

Look out for an 0.1.0 release.  May be less of a moving target by then and easier to get involved with.

Cavendish

Benjamin Armintor's response to peers who want to use graph stores and his own interest in LDP and the clarifications to the spec being made in Fedora.  Implements LDP and the Fedora API over Blazegraph. 

• Retrieving data is retrieving the named graph defined by the context resource.
• There is no single subject constraint.
• No binary storage yet, but possibly upcoming with some work from Esmé Cowles and possibly Trey Pendragon.
• Deployed as a stand-alone jar, piggy backing on top of Blazegraph.

It is available on Github, and can be poked and prodded if you want to get involved.

TCK

With the rise of alternate implementations, having a Test Compatibility Kit will be needed to verify that they adhere to the spec.  Possibly, a test suite based around performance would be beneficial, too.

FCREPO-2396

To address this, either the single subject rule will have to be broken, or we have triples wiht properties for binaries asserted on RDF resources.  The clock ran out on the conversation, which will get continued next week.