define v3 service profiles in a context / registry

[christopher-johnson]

service profiles are not defined in the v3 context. client deserializers (e.g. manifesto) need to be able to reference a registry of supported values/terms/URIs. It looks like this document specifies that intention:
http://iiif.io/api/annex/registry/services/ though it is not implemented as a context.

I opened an issue in manifesto for this: IIIF-Commons/manifesto#34 . For example, "level2" is not a known reference.

[edsilv]

I think for now the best thing would be to add entries to https://github.com/IIIF-Commons/manifesto/blob/master/src/ServiceProfile.ts

I'd really like to change this and other enums to use TypeScript String Enums too: https://blog.mariusschulz.com/2017/10/27/typescript-2-4-string-enums

This would have pretty far-reaching side-effects in manifold and UV, but I think probably an afternoon's work updating all references.

Perhaps we could then spin these enums out into a separate reusable npm module?

[azaroth42]

They are indeed not defined. When we had separate contexts, they were, and when we combined them, they got lost. Thanks for the catch!

[edsilv]

woops, posted my reply on the wrong repo!

[azaroth42]

The profiles defined here: https://iiif.io/api/presentation/3.0/#service

Are in the context here: https://github.com/IIIF/api/blob/master/source/api/presentation/3/combined-context.json#L269-L345

(As seen at: http://iiif.io/api/presentation/3/combined-context.json)

Closing, already done