Table of Contents

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

  • Time: 11:00am Eastern Daylight Time US (UTC-4)
  • ReadyTalk:
    • U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
    • International toll free:
      • http://www.readytalk.com/intl
      • Use the above link and input 2257295 and the country you are calling from to get your  country's toll-free dial-in number
      • Once on the call, enter participant code 2257295
  • IRC:

Attendees

Agenda

  • Fedora 3.7 Test Plan
    • Windows testing volunteer?
  • Fedora 4 Current Work
    • Ontology predicates and Triplestore
    • OAI-PMH
  • Fedora 4 General Topics
    1. Object/Datastream Delete model
      • Mark as delete with state flag (PUT)
      • Purge (DELETE)
    2. Async storage
    3. General RDF responses
      1. For example, policy-driven-storage

Minutes

Fedora 3.7
  1. Scott to test Windows and Oracle
Ontology / Triplestore
  1. Updating URIs to be web accessible
  2. Adding triplestore with indexing service
    • Be able to make sparql queries similar to RI
    • Goal to allow triplestore pluggability
  3. Will be using events to update index
  4. Will also have an on-demand indexing capability
  5. No longer a distinction between rels-ext and rels-int
  6. New namespaces
  7. Is there a new predicate for parent/child relationships?
    • yes, in repository# namespace
  8. Is there a legacy functional distinction between relsext/int that may be lost?
    • maybe not, will need to see from users
  9. Request to get examples of current sparql queries
    1. Action: Scott, Jonathan, Adam (Mike D.), Greg
    2. Action: Esme to send out email requesting this input
  10. Good experiences with Sesame
    • Fuseki is also an option
  11. Suggestion to use 3.x ontology as start, to limit surprise
  12. Would like to be able to specify properties to be indexed in triplestore
    • e.g. Checksum for datastream wanted in update message
  13. Approach is to make messages clean/simple
    • Have message consumer request back into the repo for additional properties
    • Note, if there are x number of consumers, there will be x number of calls into the repo
      • This issue is likely resolvable with broker configuration
  14. It is fairly simple to create a new Message Producer
  15. Are all jcr properties contained in responses
    1. Action: investigate arbitrary properties in RDF responses
General
  1. Call for OAI-PMH participation
  2. Call for async-storage REST API participation
  3. AuthN/Z links have been added to wiki
    • Interest in spring security in populating context with principals
    • Spring security SAML also something to consider
  4. To what extent would we want to include SAML?

Actions
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels