Merge pull request #919 from IIIF/annotations

Add annotations

source/_data/groups.yml

@@ -28,6 +28,16 @@
   type: community 
   notes: https://drive.google.com/drive/folders/1Q0nrQ2p1bPNgTXxK4l4kJcuwbMYARf5x
   meeting_frequency: Bimonthly on the fourth Wednesday
+- id: annotations
+  label: Annotations
+  alternate_names: 
+    - IIIF Annotations Community Group 
+    - Annotations Community Group
+  description: The annotations group is focused on undertaking user research and collaboratively developing needed cookbooks.
+  link: /community/groups/annotations 
+  type: community 
+  notes: https://drive.google.com/drive/folders/1Qwj3DSAcpSn87msF1vY0sTufIaoZWKQh?usp=drive_link
+  meeting_frequency: Monthly on the third Monday
 - id: av 
   label: A/V 
   alternate_names: 

source/community/groups/annotations/charter.md

@@ -0,0 +1,49 @@
+---
+title: "IIIF AI/ML Community Group Charter"
+layout: page
+breadcrumbs:
+ - label: "Get Involved"
+   link: /get-involved/
+ - label: "Community"
+   link: /community/
+ - label: "Groups"
+   link: /community/groups/
+---
+
+## About
+
+Though the [IIIF API specifications](https://iiif.io/api/) were not designed for machine learning applications, they have nevertheless proven valuable in recent years as applications like computer vision, classifier training, and automated tagging have become increasingly popular in the cultural heritage space. IIIF manifests and collections lend themselves to the kind of image and canvas aggregation that make it easy to feed machine learning tools, while the flexibility of the IIIF image and annotation mechanisms ([based on the Web Annotation data model](https://www.w3.org/TR/annotation-model/)) provide a compelling means of connecting images and regions therein with tags, attributes, and qualities like those often derived from machine learning processes. 
+
+Likewise, the IIIF [Content State API](https://iiif.io/api/content-state/), designed to “[provide] a way of describing a IIIF Presentation API resource, or a part of a resource, in a compact format that can be used to initialize the view of that resource in any client that implements this specification,” may prove to be a useful means of describing the outputs of some ML process, e.g., regions of interest for tagged elements.
+
+The utility of IIIF in these contexts is clear, but the best practices in this domain are less so, and awareness of the full extent of IIIF capabilities is uneven. We believe there is value in bringing together practitioners in this domain to gather and highlight use cases, align output formats, and promote interoperability more generally.
+
+
+## Goals
+
+
+* Highlight and potentially publish best practices or guidelines about how IIIF can make AI/ML projects easier or more efficient
+* Provide feedback to IIIF community and spec editors on any use cases that are not yet suitably covered by existing specifications
+* Identify any gaps in tooling or knowledge-sharing that prevent existing AI/ML-enabled tools from using IIIF and/or prevent existing IIIF-based tools (e.g., annotation apps) from being integrated into AI/ML projects
+* Consider the possibilities and implications of representing descriptive metadata gathered through AI/ML in IIIF objects
+* Promote reusability and interoperability of IIIF-related datasets and outputs
+* Raise awareness of IIIF among the machine learning community, as both a source of data and a destination for storing and publicizing the outputs of ML analyses
+* Evaluate and recommend best practices for using IIIF and annotations as an interoperable means of conveying relevant data elements in the context of image-, audio- and moving-image collections, and showcase the benefits of IIIF in these cases
+
+
+## Communication Channels
+
+
+* Monthly calls - see [IIIF Community Calendar](https://iiif.io/community/#calendar) for details
+* Virtual meetings announced on the IIIF-Discuss email list
+* General discussion on the #ai4lam IIIF Slack channel
+
+
+### Chairs
+
+
+* Emma Stanford, Stanford 
+* Peter Broadwell, Stanford 
+* Peter Leonard, Stanford
+* Giles Bergel, University of Oxford
+

source/community/groups/annotations/index.md

@@ -0,0 +1,63 @@
+---
+title: "IIIF Annotations Community Group"
+layout: page
+breadcrumbs:
+ - label: "Get Involved"
+   link: /get-involved/
+ - label: "Community"
+   link: /community/
+ - label: "Groups"
+   link: /community/groups/
+---
+
+
+## About
+
+User-created annotations are a powerful but underused part of IIIF, particularly for scholarly use-cases.  The standard robustly supports annotations, but the lack of consistent patterns for implementation has meant that the ecosystem of tooling does not yet exist to support that use case.  We believe that we could address some of the underlying barriers to a more robust infrastructure for scholarly communication by forming a community group to help identify use cases and a minimal pattern for user annotation of shared images, generate prototypes, and create a set of cookbooks for how to store, integrate, and filter annotations created by scholars and work across IIIF resources anywhere on the web—enabling image viewers, annotation stores, and annotation tools to build on a shared model for implementation.
+
+Having these patterns would enable image viewers to implement a standard protocol and user experience for integration, would allow annotation stores to provide access to multiple viewers, and would allow annotation tools to be developed in a way that promotes both scholarship and interoperability.  It would also empower the IIIF Consortium to consider ways to develop an annotation infrastructure aligned with member value.  
+We propose the creation of a community group focused on undertaking the user research and collaboratively developing the needed cookbooks.  
+
+The community group will also be responsible for producing a set of recommendations for next steps, potentially including a plan for implementing the changes across the ecosystem needed, options for developing a prototype for scholarly annotation, and/or an outreach campaign to validate the use case within the scholarly community.
+
+
+
+## Goals
+
+
+1. Refined [use cases of IIIF annotations in support of scholarship of visual culture ](https://docs.google.com/document/d/1FMDm8ow5BRNtnvo4hdTVZfE0YXpqjFG7aUDmpPKIiwk/edit#heading=h.aw0o829e7a60)presented as part of the Exec Committee’s strategic pillar
+2. A report on existing patterns used by annotation store providers and viewer developers, providing inputs for patterns that could standardize on a UX affordance for annotation integration
+3. Defined patterns for annotation usage in viewers, annotation stores, and tools
+4. UX Implementation cookbooks for implementers
+5. Written recommendations for next steps towards implementation of scholarly annotations
+6. Support the IIIF-C’s efforts to implement a hosted IIIF Annotation store
+
+
+### Chairs
+
+
+* David Newbury, Getty
+* Rashmi Singhal, Harvard University
+
+
+### Communication Channels
+
+
+* Online Zoom calls third Monday of every month at 8:00am Pacific, 11:00am Eastern, 4:00pm GMT, 5:00 CET. See[ IIIF Community Calendar](https://iiif.io/community/groups/) for details
+* Virtual meetings announced on the[ IIIF-Discuss](https://groups.google.com/forum/#!forum/iiif-discuss) email list
+* General discussion on the #annotations IIIF Slack channel
+
+
+### Call Notes and Group Documents
+
+[Shared Drive within IIIF](https://drive.google.com/drive/folders/1Qwj3DSAcpSn87msF1vY0sTufIaoZWKQh?usp=drive_link)
+
+
+
+[iiif-discuss]: https://groups.google.com/forum/#!forum/iiif-discuss "IIIF-Discuss Forum"
+[slack]: http://bit.ly/iiif-slack
+[zoom-link]: https://stanford.zoom.us/j/97082762208?pwd=w9icGF6L4dwr1bFqDbeJ7k6SS081B0.1
+[iiif-calendar]: {{ site.root_url | absolute_url }}community/groups/
+[international-zoom]: https://zoom.us/zoomconference
+[annotations]: {{ site.root_url | absolute_url }}community/groups/annotations "Annotations Community Group"
+[charter]: {{ site.root_url | absolute_url }}community/groups/annotations/charter/