Time/Place
- Time: 2:00 PM Eastern Time US (UTC-5)
- 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
- Benjamin Armintor
- Danny Bernstein
- Aaron Birkland
- Yinlin Chen
- Unknown User (acoburn)
- Katherine Lynch
- Andrew Woods
Resources
- Fedora API Delta Document - contains currently open questions
- Draft fedora specification
- Current API documentation
Agenda
- Define scope & audience
- Determine outcomes of this effort; desired content and approach of document
- How to maintain document in response to changes to spec?
- Working environment - github? Separate repository for the delta doc?
- "published" doc - Github markdown? Wiki page?
- Create tasks and timeline
Minutes
Audience for delta doc
- Application/framework developers - Yes, primary audience for this effort
Include usage related details for clients
Links to gists could be helpful
The utility of this document may have a longer lifespan than a document with Fedora contributors as audience
Hydra/Islandora/Import-Export groups will likely also need to do their own delta analysis
- Fedora Contributors - Not target audience for this effort
- Follow-on document to help inform the creation of tickets may make sense in the near future
- Managers/stakeholders - Not target audience for this effort
Delta doc purpose
- Highlight breaking changes from current community implementation
- Highlight features in community implementation that are not in the specification, but allowable
- e.g. server-managed triples
- Highlight examples
- e.g. What does the community implementation model of versioning look like vis-a-vis Memento
- Highlight rationale for specification decisions
e.g. When a binary resource is updated, some severs-managed triples in the binary's description are updated
e.g. The specification is intentially silent on certain topics
Delta doc structure
- Organize with same sections as the Fedora API Specification
- Include sub-sections within each API Spec section for:
- Breaking Changes
- Non-specified Features
- Examples
- Rationale
- Content to be bullet list of sentences and links
Logistics
- Reside in a new GitHub repo (within the fcrepo Git organization)
- Use markdown in one main document
- Delta between Fedora 4.7.1 and the master branch of fcrepo-specification
Tasks
- Create the GitHub repo (Adopters Guide)
- Create initial outline of the delta document
- Aaron Birkland and Andrew Woods to draft initial content
- Likely starting with Fixity