Time/Place

• Time: 2:30pm Eastern Time US
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access:  https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php

Attendees

 (facilitator)
 (notetaker)

• Andrew Woods 
• Esmé Cowles
• Daniel Lamb 
• Simeon Warner
• Benjamin Armintor regrets

Agenda

1. External content
   1. Issues: https://github.com/fcrepo/fcrepo-specification/issues?q=is%3Aissue+is%3Aopen+label%3Aexternal-content
   2. Needs more editorial review, also pending response to existing comments: https://github.com/fcrepo/fcrepo-specification/pull/121
2. PUT-to-create: waiting on comment from Daniel Lamb and/or Benjamin Armintor: https://github.com/fcrepo/fcrepo-specification/issues/43
3. What to do with: PUT/POST with Content-Location:
   1. https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-http-commons/src/main/java/org/fcrepo/http/commons/domain/ContentLocation.java
   2. https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-http-commons/src/main/java/org/fcrepo/http/commons/domain/ContentLocationMessageBodyReader.java
   3. https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-http-api/src/main/java/org/fcrepo/http/api/FedoraLdp.java#L327
4. Which git issues are actionable? https://github.com/fcrepo/fcrepo-specification/issues
   1. Does persistence fixity belong in the spec https://github.com/fcrepo/fcrepo-specification/issues/90
   2. Add intro: https://github.com/fcrepo/fcrepo-specification/issues/93, https://github.com/fcrepo/fcrepo-specification/issues/95
   3. Publish ontology: https://github.com/fcrepo/fcrepo-specification/issues/108
   4. Depth header for delete: https://github.com/fcrepo/fcrepo-specification/issues/111
5. Which git issues need triage?
   1. Fixity section: https://github.com/fcrepo/fcrepo-specification/issues/100
   2. Clarify HEAD behavior https://github.com/fcrepo/fcrepo-specification/issues/103
   3. Clarify InboundReferences https://github.com/fcrepo/fcrepo-specification/issues/119
6. Branding: Fedora Commons/community implementation; other implementations and the API specification

Minutes

External Content

1. Action: Danny/Barmintor, need more review of PR#121
2. UPenn, Princeton, Columbia - using external content
3. Islandora users with large content will likely use external content
4. Some Hydra users will likely use proxied content

PUT-to-create

1. Merging by escowles

PUT/POST with Content-Location

1. Do we need both?
2. Action: awoods - is anyone using this feature?
   • if anyone is using it, could it be replaced with external/body?cache
   • include spec alternative in message

Which git issues are actionable?

1. Does persistence fixity belong in the spec
   • closed
2. Add intro
   • Action: Danny to write intro for issue#95 (also bring in elements of issue#93)
   • issue#93: related in that it circles back to "the purpose of the spec"
     • interest in maintaining some degree of "swappability"
     • it so happens that SSR provides for swappability... but should be revisited
     • suggestion: transpose "interoperability" for "swappability"
3. Publish ontology
4. They are different ontologies
   • Let both live in their own URL space
5. Remove overlapping term from v4 ontology with the release of Fedora 5
6. The spec ontology should be common to all impls
   • Impls can have their own ontologies as required
   • Action: awoods provide resolution to: Possibly use: fedora.info/spec
7. Depth header for delete
   • Action: Danny is moving this forward with a pull-request

Which git issues need triage?

1. Action: everyone review these three issues
   • We should come to next meeting with a plan for each

Branding

1. The spec defining "what is a Fedora" is problematic
   • Aspects of the community impl are not represented in the spec
2. Maybe call this effort the "Core API Specification"
3. Some features are not specified or are optional
   • PUT for create
   • 415 - not implemented examples
   • Batch Atomic Ops
4. Review simeon's diagram as it relates to branding/messaging
5. Need to bring barmintor into the conversation
6. Action: simeon to create a github issue

Action Items

• Andrew: Look at whether "ingest from URL" and the message/external-body PR duplicate functionality
• Ben: Write up external content proposal as a PR
• Ben: Write up external content and redirect use cases
• Esmé, Danny, and Andrew will finalize/review https://github.com/fcrepo/fcrepo-specification/pull/106
• Simeon: Review and summarize https://github.com/fcrepo/fcrepo-specification/issues/43
• Danny: Draft intro text to address https://github.com/fcrepo/fcrepo-specification/issues/93 and https://github.com/fcrepo/fcrepo-specification/issues/95
• 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