Date

14 Jul 2016

Attendees

Discuss project scope
- Commitment to LDP
  - Philosophical commitment to RDFSources; does that mean LDP?
  - Yes. Let's scope to LDP
  - Let's assume that we will continue to make "record" level GET and updates via LDP.
Review work plan (KriKri RDF Database Review)
- Enviornmental scan (in order of predicted implementation cost)
  - Marmotta Backends
    - Blazegraph
    - TitanDB
    - Ostrich
  - Other existing LDP implementations
    - Virtuoso
    - Carbon LDP
    - Fedora 4
    - etc... ?
    - Commercial support landscape
  - RDF::LDP (Ruby Rack server layer & domain model)
    - Possible backends?
  - Write our own server.
Begin requirements work (KriKri Datastore Requirements)
- Administrative
  - Long term support prospects
  - Community/Commercial support
  - Documentation quality & dependency trees
- Specifying acceptable performance
  - Needs for scale up/scale out
- Parallel requests
- Versioning
- Other issues?