[eml-dev] Cardinality of language

[Matt Jones]

As Ben said, I think its more effective to declare the default language for
the document and then provide explicitly-marked translations of the fields
so that display agents can provide each field in any alternate language
translation that was provided.  Let us know David if there's something that
you need that isn't possible with this internationalization support.

Matt


On Wed, Jul 10, 2013 at 8:14 AM, ben leinfelder
<leinfelder at nceas.ucsb.edu>wrote:

> Hi David,
> Have you reviewed the internationalization support we added to EML v2.1.1?
> In this update, most metadata fields allow an unbounded number of language
> translations.
> http://knb.ecoinformatics.org/software/eml/eml-2.1.1/index.html#N101A3
> http://knb.ecoinformatics.org/software/eml/eml-2.1.1/eml-211info.html
>
> This is useful for interpreting the metadata correctly and I think it is
> more specific than simply declaring that there are a few different
> languages employed somewhere in the data package (as would be the case if
> we allowed an unbounded sequence of <language> elements). We can certainly
> allow multiple <language> elements, but I wonder about the ultimate utility
> of that aside from being informational.
>
> If we did go ahead with this change it would be compatible with EML 2.1.1
> and EML 2.1.0 so we could use v2.1.2 with impunity. As with any change to
> the EML schema, the proposal would need to be put to a vote by the EML
> committee. Though I can't quite remember all the voting members at present,
> I'm sure someone can chime in with that procedure.
>
> Thanks,
> -ben
>
> On Jul 10, 2013, at 1:53 AM, David Blankman <dblankman1 at gmail.com> wrote:
>
> > ISO allows multiple languages in a data resource. The cardinality of
> <language> in resource is 0,1. We have allowed multiple languages in the
> metadata. It also seems that we should also allow multiple languages in
> <language> This came up because in LTER-Europe's implementation of DEIMS we
> allow for multiple languages. We have a few documents with multiple
> languages. For example, 7. Dataset language
> > Language:
> > English
> > Spanish; Castilian
> >
> > I know that in Israel we have data with both English and Hebrew.
> >
> > I propose that the cardinality for this element be changed to 0..∞.
> >
> > Documentation on language:
> > language       This element has no default value.
> > Content of this field:         Description of this field:
> > Type: i18nNonEmptyStringType
> > The language in which the resource is written. This can be a well-known
> language name, or one of the ISO language codes to be more precise.
> > Example(s):
> > English
> > David Blankman
> > Chair, ILTER Information Management Committee
> > Director, Information Management, Israel LTER
> >
> > 972-77-442-1951
> > 972-54-685-9345 (mobile)
> > 1-505-349-5680 (Skype)
> > dblankman (Skype)
> > _______________________________________________
> > Eml-dev mailing list
> > Eml-dev at ecoinformatics.org
> > http://lists.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/eml-dev
>
> _______________________________________________
> Eml-dev mailing list
> Eml-dev at ecoinformatics.org
> http://lists.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/eml-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20130710/7022605f/attachment.html>