...
Agenda
- What are the issues that need resolution prior to June 20th?
- External content
- Issues: https://github.com/fcrepo/fcrepo-specification/issues?q=is%3Aissue+is%3Aopen+label%3Aexternal-content
- Needs more editorial review, also pending response to existing comments: https://github.com/fcrepo/fcrepo-specification/pull/121
- What to do with: PUT/POST with
Content-Location
:- https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-http-commons/src/main/java/org/fcrepo/http/commons/domain/ContentLocation.java
- https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-http-commons/src/main/java/org/fcrepo/http/commons/domain/ContentLocationMessageBodyReader.java
- https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-http-api/src/main/java/org/fcrepo/http/api/FedoraLdp.java#L327
- Response to list inquiry of usage of
Content-Location
ingest feature and possible migration to external/body?cache?
- Fixity section: https://github.com/fcrepo/fcrepo-specification/issues/100
- Clarify HEAD behavior https://github.com/fcrepo/fcrepo-specification/issues/103
- Clarify InboundReferences https://github.com/fcrepo/fcrepo-specification/issues/119
- Branding as Core Specification https://github.com/fcrepo/fcrepo-specification/issues/122
- Publication of Fedora ontology: https://github.com/fcrepo/fcrepo-specification/issues/108
Minutes
- We'd like to have the initial draft ready in about 2 weeks, what needs to be resolved before then?
- Andrew: There are some issues that are more conversational
- Esme: External content seems like a big one, there are several other issues that have been identified as workable
- Simeon: I'm having some doubts about the scope and how
- Ben: With the issues listed as action items, I think I could start implementing the outstanding functionality in Cavendish
- It seems like having things ready for initial implementation to further practical evaluation
- Simeon: There's a big gap between the spec and the Modeshape impl — what does that mean for e.g., Hydra and Islandora, etc.?
- Danny: Not fully implemented yet, but share the concern — the main thing is versioning, where we want to reconcile Drupal and Fedora versions
- Core CRUD is the main thing, and it's there
- Esme: Hydra uses a subset of the Modeshape impl functionality, and that subset is in the spec
- Andrew: The spec covers most of what is in the Modeshape impl, at least in functionality, even if the behavior is somewhat different
- Resolving the action items would put us in a good place for community feedback
- External content
- Esme: the PR looks good — just some technical questions and not substantive ones
- Expires issue: the mailing list thread seems resolved
- Ben: a side issue to the Content-Location issue
- Esme: not a thing we're specifying, but a good thing to note
- Andrew will make a PR to resolve the technical issues
- PUT/POST with Content-Location
- Andrew sent a message to the mailing list, and there have only been a couple of responses and there were no objections to potentially using a different mechanism
- Simeon: so we can close the issue
- Fixity
- Ben: The issue is that the fixity recommendations are all in information sections
- Andrew: So we'd need to update 5.1 to remove the reference to the removed fixity method
- And 5.2 would to be normative and refer to the 3.x sections that include Want-Digest
- Ben: I'm not sure we need to make 5.2 normative just because it refers to normative sections — there's no new testable behavior here
- Andrew: There is some new text and it should be in a normative section
- Ben: Since the spec is targeted at implementers, and we should make it as easy to read without jumping around
- Simeon: Should we move the section out of the list of requirements?
- Esme: I think that addresses Aaron's concern — it is moved out of the list of requirements because it's not normative, but remains as an informative section, since it's an important concept for Fedora
- Andrew and Danny: OK with that
- DELETE/Depth
- Andrew: This seems like a good starting point to me, but not sure what e.g, Depth: 5 means
- Esme: I agree: Depth: 0 and Depth: infinity are the ones that make sense for the Modeshape impl, and I'm happy to let other impl. find reasonable values for their impl.
- Danny: I would like to include something about emitting messages for async failures
- Simeon: This may be a rabbit-hole, should move to a separate ticket
- Danny: I want to include some language around failures
- Esme: I agree — we should definitely expect impl with immediately-consistent backends to report errors, async backends can fall back on messaging
- Clarifying HEAD headers
- We can be more explicit here, but should not need to require all Content headers
- Simeon will address this next week
- Branding
- Andrew: Important to get the branding question right
- Esme: Spec is narrower than the Modeshape impl, but don't want to imply that an impl. of the spec isn't useful
- Simeon: Want to make sure that a thing that is "a Fedora" is a useful thing
- Danny: We haven't done a very good job of specifying if the impls. aren't useful
- Andrew: We should look carefully at the spec and identify any places where we can tighten the spec to make sure an implementation
- Danny: "Core" to me still means something useful
- Andrew: The spec should be the minimal amount to call your impl. "a Fedora", and we should improve the spec if we don't think that's true
Previous Action Items
- Ben: Write up external content and redirect use cases
- Daniel Lamb / Benjamin Armintor: to review https://github.com/fcrepo/fcrepo-specification/pull/121
- Andrew Woods: to post to list inquiry of usage of
Content-Location
ingest feature - Daniel Lamb: to write intro for https://github.com/fcrepo/fcrepo-specification/issues/95 (also bring in elements of https://github.com/fcrepo/fcrepo-specification/issues/93)
- Andrew Woods: to respond to https://github.com/fcrepo/fcrepo-specification/issues/108 with suggested resolution
- Daniel Lamb: to create PR for https://github.com/fcrepo/fcrepo-specification/issues/111
- ALL: to review following three issues prepared to come to next meeting with a plan for each
- Fixity section: https://github.com/fcrepo/fcrepo-specification/issues/100
- Clarify HEAD behavior https://github.com/fcrepo/fcrepo-specification/issues/103
- Clarify InboundReferences https://github.com/fcrepo/fcrepo-specification/issues/119
- Simeon Warner: to create a github issue re: branding and spec naming → https://github.com/fcrepo/fcrepo-specification/issues/122
New Action Items
- Andrew: Move Fixity section to the end and remove reference from Section 1
- Esmé: Update Fixity section to include persistence fixity language
- Danny: will move 111 forward, and create a separate ticket for async failures