Simeon Warner comments

Results 108 comments of


                                            Simeon Warner

trafficstars

Define a probe service

Resolved. The IIIF Authorization Flow 2.0.0 specification was published 2023-06-02: https://iiif.io/api/search/2.0/ -- includes probe service

Support authentication for content search services for restricted content

This is really an example for the general case of Auth for IIIF Resources that is not covered in Auth 2.0.

Authentication API and internationalization

Resolved. The IIIF Authorization Flow 2.0.0 specification was published 2023-06-02: https://iiif.io/api/search/2.0/ . It now use language maps throughout, following the pattern of Presentation API 3.0

Tiered access in Auth 2

Resolved with publication of Auth 2.0. Now use `substitute` instead of `location` and see https://iiif.io/api/auth/2.0/#tiered-access

Allow provision of label for navDate, navPlace

It seems that if we opted for adding a `label` then there would be no motivation to remove the UTC requirement (#1296). It does seem like we might very quickly...

Harvard 1: Load existing, standalone OCFL object

This is the function I'm not sure about, where is the object loaded to/from?

Harvard 3: Get content/files from individual object

Current extract functionality (broken for v1.1 see https://github.com/zimeon/ocfl-py/issues/110) supports only extraction of all content: ``` ocfl-py> ./ocfl-object.py --obj fixtures/1.0/good-objects/spec-ex-full --extract v2 --dstdir /tmp/aaa INFO:ocfl.object:Extracted v2 into /tmp/aaa Extracted content for...

Harvard 2: List files in individual object

We have ``` ocfl-py> ./ocfl-object.py --show --objdir fixtures/1.1/good-objects/spec-ex-full WARNING:ocfl.object:OCFL v1.1 Object at fixtures/1.1/good-objects/spec-ex-full has VALID STRUCTURE (DIGESTS NOT CHECKED) WARNING:ocfl.object:Object tree [fixtures/1.1/good-objects/spec-ex-full] ├── 0=ocfl_object_1.1 ├── inventory.json ├── inventory.json.sha512 ├── v1...

EPIC: Properly support OCFL v1.1 as default

Start was #81, see also #87, #92, #108, #110, #112 for work so far

As a consumer of drag and drop, I want a link back to the context in which the object was originally discovered.

... so that this link can be presented as the 'source' (or something else)? Seems that likely we'd need to nail down intended use/semantics to make such information interoperable.