You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Time/Place

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

Attendees

  1. Danny Bernstein
  2. Peter Eichman 
  3. Bethany Seeger 
  4. Jared Whiklo 
  5. Andrew Woods (star)
  6. Kevin Ford
  7. Ben Pennell 
  8. Aaron Birkland  
  9. Mohamed Mohideen Abdul Rasheed
  10. David Wilcox 

Agenda

  1. Announcements

  2. Sprint 2
    1. Open questions
      1. Default messaging configuration (topics? queues? disabled?)  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Move fork of jetty-plugin to fcrepo4 GitHub organization?
      3.  Handling authentication and authorized agents in CTS
        1. Requirements
          1. Required users: 
            1. read-write-control on root container
            2. second user with access controlled by acls created by the previous user
          2. CTS must know the user agent URI for each.
          3.  CTS must not depend on any particular mechanism for authenticating
        2. Approaches: 
          1. jar to be included in classpath? 
          2. ?
    2. Remaining work

      1. Tickets

      2. CTS

      3. Documentation

    3. Release Candidate
  3. <your agenda item here>

  4. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  5. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  6. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Minutes

  1. Future Agenda Topics: 


3. Open questions.

  • Properly suppressing Server Managed Triples, how do we deal with ldp:contains.
    • Meta-conversation about what are Fedora's SMTs and the workflow.
    • Updating a properties of a resource requires a special header to GET and to PUT. Do we reverse the behaviour and get back the non-SMTs by default. But you are lacking some of the useful triples (lastModified).
    • We expect that READ is a more common action than write.
    • ldp:contains should be a SMTs, which makes (for Jared) suppressing SMTs by default a less enjoyable process.
    • Having Fedora ignore SMTs included in a PUT does not seem to be a breaking change and could be done post-5.0.0 release.
    • Should be able to update SMTs if you need to.
  • How do you restore a Memento?
    • Currently need to GET a Memento, set Fedora to relaxed mode, then restart and PUT with Prefer: handling=lenient; received=minimal
    • Need to have relaxed mode on a per-request
    • Is this an authZ question? Should only certain people be able to restore versions?
    • What is the result of a restore? Do you get all the previous triples whether they are SMTs or not? That seems to be the consensus.
    • Consensus is to use a new Prefer header to allow per request overwriting the entire resource including any SMTs.
    • Will restoring a Memento result in restoring an older ACL? Consensus is NO, the Memento is separate. The link to the ACL is a static link added by the server and because the resource is not removed/re-added the current ACL will remain.
    • Discussion to occur in Slack
  • Changing interaction models?
    • Currently there is no way to change between interaction models.
    • Currently you can add types in the ldp: namespace, this should not be allowed.
  • Make all resources versionable by default?
    • Yes. Danny to create a JIRA to enable versioning. Also create JIRA to tag code that is used for enabling versioning for future review.
  • Reviewing list of SMTs that Ben created
    • Is the list full and complete?
    • What is the expected behaviour in interacting with SMTs.
    • "Anything that is created by the server" as the rule for SMTs?
    • Anything created by the server, where if they did not exist the interaction would be indetermined.
    • Any triples added to the resource as they are being generated on request. `ldp:contains` and some fixity ones. Also with RDF serialization.
    • Also make sure that on the testing side we ensure the correct behaviour of SMTs.


  • No labels