Add an internationalization design pattern

[zimeon]

Motivated by discussion of https://github.com/IIIF/api/issues/1759 and described in https://github.com/IIIF/api/issues/1767, the editors propose that we add a design pattern that talks about our goals of internationalization, along the lines of:

Design for Worldwide Use IIIF specifications encourage internationalization efforts by requiring that text values of properties indicate their language, to support and encourage use around the world. IIIF assumes that text values of properties may have multiple values in multiple languages, rather than this being a special case.

[scossu]

Related to #5

[azaroth42]

Summary during the call: In Edinburgh it was noted that homepage cannot have multiple versions with different languages. That led to discussion that we're trying to make IIIF useful the world over, so we should add to the design patterns that internationalization is a core principle. Editors discussed and agreed, we proposed the text above to be added.

Related question is the @none/none issue, but this is the principle of adding to the design patterns.

[azaroth42]

Clarification: Removed a note about none/@none, as actually unrelated to this issue of core principles. Suggested on TRC call by @aisaac.

[azaroth42]

Issue 2 (Add an internationalization design pattern)

+1: 37 [Siani81 ahankinson aisaac andrewgunther awead azaroth42 beaudet cubap dismorfo emulatingkat gigamorph glenrobson hadro ipf irv jbhoward-dublin jonhartzler joshuago78 jronallo jtweed julsraemy jwd kzhr markpatton mattmcgrattan mcwhitaker mejackreed mikeapp mixterj regisrob rentonsa rsinghal scossu sredick tomcrane tpendragon zimeon] 0: 0 [] -1: 0 []

Result

Super majority is in favor, issue is approved