Metadata should allow non-short values (split of #1242)

[azaroth42]

Metadata is currently defined as being a label and a short descriptive text:

A list of short descriptive entries, given as pairs of human readable label and value to be displayed to the user. [...] This list of descriptive pairs should be able to be displayed in a tabular form in the user interface.

This leaves nowhere for longer texts to be described, given the semantics either current or proposed in #1242, for longer texts such as curatorial notes, bibliographies, provenance statements or similar.

The proposal is to allow these in metadata and to have a SHOULD on clients to provide a UI that can deal with them (either compacting the value with an expand function, or a tabbed interface, or something else).

[zimeon]

Since we have nowhere defined what short or long mean, I think that the current specification is pretty vague. I support the idea of striking the word short and then adding advice that clients SHOULD be ready to deal with text that is too long to fit into a particular UI pattern.

[azaroth42]

Discussion on 11/22 call: Approved.

Noted that long texts will add to the size of the manifest, but still smaller than the content

[azaroth42]

I believe this is already done: http://prezi3.iiif.io/api/presentation/3.0/#metadata

The description no longer indicates short, and the warning about long values is before the example.
Close?

[tomcrane]

Agree close.

[mikeapp]

Agree close

[zimeon]

Agree close