Page History

...

1. API Specification

   1. Moving towards a shared understanding: Purpose of the API specification 

   2. Does Persistence Fixity belong in the specification?

      1. Josh: It's an important function of this kind of system, and the expectations about how it might be done need to be clear

      2. Danny: some discussion of back-fillability of functions
      3. Aaron: application concerns are different for RW apps than for RO apps, too
      4. Andrew: consider the notion of substitutable backends- seems like spec should be clear enough that an app should be able to be agnostic to some extent; what capabilities should be guaranteed? what are implementation dependent? is a key distinction for the API definition effort. What can we do?
      5. Aaron: unsure how much we can do with regard to, for example, the flexibility in the LDP approach of constraints documents and statement rejection (again mattering to RW and not to RO apps)
      6. Andrew: To what degree is substitutability reasonable or sensible?
      7. Nick: If we're silent on SSR, cannot promise any functional substitutability (in managing apps)
      8. Danny: the spec is really leading me to use the simplest interaction models, which might good, but may also be too simple
      9. Kevin: feels strongly that it should be a refinement of LDP

   3. Outstanding issues

2. Implications of blank node redesign: 

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

   1. Warrants a 4.8.0 release?
3. Suggestions from recent Fedora Leaders meetings
   1. Have an elected Fedora Committer join Fedora Leaders calls
   2. Have DuraSpace-hosted release testing infrastructure
   3. Interest in tighter alignment of effort and priorities between Islandora/Hydra/Fedora
4. Announcement: Monday - 2017-04-17 - Import - Export Planning Meeting
5. ...

6. Status of "in-flight" tickets

     Click here to expand...

...