1. C2PA Review

Neil Thomson gave some feedback on the review of the C2PA specification that he and others had been working on. 

Discussion on the risk that meta data and data can be separated and/or meta data deleted or changed. 

John Phillips suggesting that this was a deliberate design tradeoff since the C2PA designers wanted to ensure all content was accessible by all people, hence provenance (IF associated with the data) needed to be separate. There is significant concern that alternative approaches (protecting content through encryption say) would be likened to DRM. Also raised the idea that while we should be arguing for as much content as possible to be signed and to have provenance, we should expect that some content will need to be unsigned. See also https://www.linkedin.com/posts/11dot2_openai-unveils-plans-for-tackling-abuse-ahead-activity-7153502735194066944-2-Y5?utm_source=share and the associated comments/discussion.

Neil Thomson proposed that the ability to separate data from meta data presented a risk and that alternatives such as the ACDC approach provided better protections.

Neil Thomson offered to present the findings/observations at the next GATF Americas call.

2. Website update

It was agreed that the webpages update would require coordinating with Judith Fleenor and that contributors would be welcome from ToIP. Drummond Reed offered his support as did John Phillips 

John Phillips offered that he needed to clean up the files provided in the ToIP shared folders for the 3rd Gen diagram. The proposed action was

1. to create a folder called "Archive" and place previous working documents in that folder
2. Create a clean version of the presentation deck introducing the third generation diagram in light and dark themes with no side discussions on trees, targets or other distractions.
3. Share the links on slack.

3. Support the development of a ToIP guidebook

General discussion and agreement that we should use a GitHub based approach to content creation and management, allowing us to take advantage of the powerful collaboration and version control features and focus on simple markdown text formatting.

Carly Huitema offered that she would create a simple guide to using GitHub for project documentation and meetings. The design constraints for which would be:

1. As simple as possible (but no simpler). No need for content authoring/commenting participants to install code or local copies. Pure web based interaction
2. Richer presentation formats through Jekyll or similar products (Docusaurus, Plandoc etc.) might  require a content manager to produce, but this should be limited to only a few people (maybe only one). Content update through pull requests, merges etc. should lead to automatic refresh of presented content.

John Phillips suggested that we create a first cut of the structure for the guide we should draft an introduction that includes an "About this book" section. The ATB section would describe the structure of the rest of the book, how divided up and what each section aims to explain.