On Wed, Jul 19, 2017 at 3:14 PM, Mark H. Wood <[email protected]> wrote: > What this says to me is that the language attribute should have a controlled > vocabulary. One should not be *allowed* to enter weird values. At the very > least it should be required to match /^[[:lower:]]{2}(_[[:upper:]]{2})?$/ > > (I'm sorry to say that I couldn't find a standard locale name for "unknown", > in case some researcher returns from the bush with literature in a > previously unknown (and thus not yet standardized) language.)
I may not be up to date on current RFCs, but BCP 47 relies on ISO 639 for the specification of language. ISO 639 has codes for several types of unknowns: special code: available to be used in a context where a code is required, but the language has no code special code: multilingual content special code: undetermined special code: no linguistic information Only for orientation purposes, taken from https://en.wikipedia.org/wiki/ISO_639#Relations_between_the_parts Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
