...

Discussion

Adam begins with API:

Base specification LVP plus base ontology but bytestreams

Possibly add transactions (suitable for web scale, not XA, JCR spec)

Thoughts about container:

• Objects plus datastreams (fedora)

• External to repo

• Esme: other objects in repo

• Andrew: question do we want to support

• Adam: has different guarantees if outside

• Adam: Need to think out ramifications for different kinds of outside items

• Dan: Could have some overlap with issues about tiered storage

• Adam: Not absolutely required for LVP, but is part of traditional Fedora

• Andrew: Member, Reference, Indirect Container (need definitions)

• Dan: Considerations of asynchronous responses (overlaps burden for remote operations)

• Andrew: Need to define proposal for tiers

• Adam: Keep core simplest possible

• Andrew: We need to review what we have, LVP, is the interaction model logical, clean, does it represent what we expect out of the repository

• Adam: Did we make a good guess for the implementation? Test on real world usage.

• Adam, Andrew: Specification with dependencies for transactions, TCK, ontology

• Andrew to Adam: Can you flesh out all the tiers?

• Adam: Will try for week from today

• Esme: Should conversation be on Fedora tech list

Performance Scenarios (Dan)

• Fixity checking
• Real-world scenarios
• Cache and no-Cache
• Look at direct REST client for Python
• Setting up environment (Scott Prater may have done some work)
• Many folks could contribute tests
• 
  

RDF and Sparql Update well underway for next period (Esme)