...
Attendees
- Jared Whiklo
- Jim Coble
- Andy Wagner
- Doron Shalvi
- Yinlin ChenEsmé Cowles
- Kevin Ford
- Michael Durbin
- Andrew Woods
- David WilcoxSimeon Warner
- Benjamin Armintor
- Joshua Westgard
- Nick Ruest
- Aaron Birkland
- Daniel LambAndrew Woods
Agenda
- API Specification
- Ideally the first public draft would be published over the next couple weeks
- Moving towards a shared understanding: Purpose of the API specification
- Some of the disagreements about the details of the spec arise from differing opinions on the purpose of the spec itself
- Notes on purpose of the spec
- Two different perspectives:
- Spec defines minimal but required set of capabilities that must be implemented in order to “do Fedora”
- There are a range of capabilities, and you may or may not do all of them
- If you do any of them, here is some guidance/expectations on the behaviour
- Josh: what is the scope of the spec?
- Is the spec mainly about aligning Fedora with LDP, or should it also include things (like fixity) that are historically associated with Fedora that do not fit into an HTTP interaction model?
Does Persistence Fixity belong in the specification?
Josh: It's an important function of this kind of system, and the expectations about how it might be done need to be clear
- Danny: some discussion of back-fillability of functions
- Aaron: application concerns are different for RW apps than for RO apps, too
- 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?
- 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)
- Andrew: To what degree is substitutability reasonable or sensible?
- Nick: If we're silent on SSR, cannot promise any functional substitutability (in managing apps)
- Danny: the spec is really leading me to use the simplest interaction models, which might good, but may also be too simple
- Josh: feels strongly that it should be a refinement of LDP
- Kevin: If the purpose is interoperability with an eye toward swapping out back-ends then we should tighten the spec
- Pain point: putting RDF (e.g. an ontology) into Fedora that does not conform to Fedora’s restrictions (e.g. single subject rule) so it must be uploaded as a binary file
- Is the SSR a technical limitation or an important part of what Fedora is?
- Andrew: it is a philosophical limitation - Fedora is a digital object repository so RDF describes objects in Fedora rather than random subjects in the world
Implications of blank node redesign:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2108 - Warrants a 4.8.0 release?
- Instead of being created off to the side, these are now created as hash URIs
- Jared: Will anyone notice this change?
- Andrew: existing resources will not change, but new blank nodes will be created as hash URIs
- If administrators wanted to remediate this difference they would need to do this work (or a tool could be created)
- Nick: Do we need to release this along with a tool? What kind of release is it?
- Andrew: It is not backwards-incompatible so it is a minor release
- Aaron B: Some clients may have written code that would make this backwards incompatible
- Andrew: We could float this to the community to see if anyone is depending on the previous functionality
- Basing this on mailing list feedback is not necessarily indicative of what people are doing
- Jared: Do we define breaking change based on the repository or potential workflows?
- We should produce a tool to remediate the different ways of handling blank nodes and put out a minor release:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2423
- Suggestions from recent Fedora Leaders meetings
- Have an elected Fedora Committer join Fedora Leaders calls
- Have DuraSpace-hosted release testing infrastructure
- Interest in tighter alignment of effort and priorities between Islandora/Hydra/Fedora
- Announcement: Monday - 2017-04-17 - Import - Export Planning Meeting
- ...
Status of "in-flight" tickets
...
Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Minutes
API Spec Outstanding Issues
- #82 about ordering issues, which was largely not an API issue
- #81, a little bit of langage in the spec should clear up confusion here
- change a "may" to a "must" if a preference is applied, the fedora implementation should say so
- #80, there's some disagreement about whether fedora should redirect or proxy to external content, and once a clear consensus is achieved, the spec should reflect it
- Benjamin Armintor is the only one who has articulated a need for proxying, while presumably other stakeholders are content with redirects
- Feedback at LDCX suggested that other stakeholders minimally preferred proxied content, and in some cases required it.
- A new issue was opened for this Proxy vs. Redirect requirement in the spec.
- Benjamin Armintor is the only one who has articulated a need for proxying, while presumably other stakeholders are content with redirects
Committer's needed to close PRs
- S3 Configuration ticket needs to be merged, but someone with S3 storage should test them
- no one on the call volunteered as having S3 storage
- Esmé Cowles will contact Andrew Woods about this
A PR from Danny Bernstein to address performance of items with lots of properties
- This is almost done, but maybe a test failure is holding it back
In-Flight tickets (none?) and Bugs
...