Dawn Childress

Where a search service does not exclude stopwords, does it make sense to have a parameter that tells the client to use a specific or custom stopword list? For example,...

Now that `navPlace` is published, the Annex doc should be updated. Should this go to @thehabes or @mikeapp? I can also take a stab at it.

All good questions @thehabes! Is GeoJSON still the service? It's just used in the API via navPlace? If that's the case, I wonder if we should keep "GeoJSON" in the...

Update: will migrate GeoJson service info to Services page and update the text to say only use with v2, for v3 use navPlace and link to extension

First pass in draft PR https://github.com/IIIF/api/pull/2092

This seems to already be supported in Search 1.0 and 2.0 (searching on resources other than Canvases), so are we missing something about this ticket or should it be closed?...

@thehabes - it does provide a context! It's here: https://iiif.io/api/annex/openannotation/context.json. An updated version in a new location is coming soon. The PR is here: https://github.com/IIIF/api/pull/2231

Following up on some of the Mirador meeting questions: From the Presi 3 spec: Choice is not explicitly covered in v3, but there is the statement “Clients should process the...

Hi, @cbeer. I think we acknowledged a year ago that the spec is fuzzy on the bottom-up ordering and that we need to make that more clear in the next...

I would probably call it a DMS (data management system). Maybe we can rename the CMS/DAMS section to include DMS or something? In any case, I've not seen this before...