Open jronallo opened 7 years ago
For redaction or other cases where a particular user should not see some of the content then there need to be server side restriction for reliable access control. This could be implemented either through multiple versions (might be Choice with different Auth conditions if some users allowed full access, others not) generated either statically or on-demand.
In the case of multiple versions it will be useful to have a shared timeline between redacted and non-redacted versions (so that one set of annotations work on both for example). This might need some information to allow the client to skip over redacted portions when displaying that version.
See also #12 re. description of gaps
Description
Access restrictions: prevent replay of part of a recording, e.g. redacting. By time code. On site vs external access. Geo-locking for out of copyright in UK but still in for US.
Variation(s)
Annotation of the restriction
Proposed Solutions
pre-constructed versions, with redirects. Not a client side thing, as clients could simply ignore it. So can't expect client to not play something it has access to.
Additional Background
IIIF: Auth Source: BL workshop notes Interest: 90%