You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing IIIF Authorization Flow 2.0 specification identifies access control patterns for Content Resources including static images, video, audio, documents, 3D models, and any other Content Resource, but does not address access to IIIF API Resources such as the Presentation and Content Search APIs. The aim of this charter is to propose a new specification that will identify access control patterns for access to IIIF Presentation API resources, including Manifests, Collections, Annotation Pages, and IIIF Content Search API results. The new specification will complement the existing specification with new access patterns and will also overlap with certain areas of the existing specification to ensure interoperability.
Charter
Background and Summary
The existing IIIF Authorization Flow 2.0 specification identifies access control patterns for Content Resources including static images, video, audio, documents, 3D models, and any other Content Resource, but does not address access to IIIF API Resources such as the Presentation and Content Search APIs. The aim of this charter is to propose a new specification that will identify access control patterns for access to IIIF Presentation API resources, including Manifests, Collections, Annotation Pages, and IIIF Content Search API results. The new specification will complement the existing specification with new access patterns and will also overlap with certain areas of the existing specification to ensure interoperability.
Voting
The TRC role with respect to TSG formation is to:
So please add any comments either to the charter or in this issue. We will also hold a vote for approval so:
The text was updated successfully, but these errors were encountered: