sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <>
Subject [jira] [Created] (SIS-154) Allow references to multi-lingual metadata resources
Date Tue, 17 Dec 2013 01:12:07 GMT
Martin Desruisseaux created SIS-154:

             Summary: Allow references to multi-lingual metadata resources
                 Key: SIS-154
             Project: Spatial Information Systems
          Issue Type: Improvement
          Components: Metadata
    Affects Versions: 0.3
            Reporter: Martin Desruisseaux
            Priority: Minor

Files on are provided in
two versions: {{gmxCodelists.xml}} and {{ML_gmxCodelists.xml}} where "ML" stands for "multilingual".
Apache SIS writes references to those files when marshalling a {{org.opengis.util.CodeList}}
or some other objects like {{java.util.Locale}}. The files are selected as below:

 * SIS 0.3 uses a hard-coded mix of the two versions.
 * SIS 0.4 consolidated all code lists to the unlocalized versions for now, for the reason
explained below.

We assume that the following assumptions hold:

 * All code lists defined in a {{ML_gmxCodelists.xml}} file exist also in {{gmxCodelists.xml}}.
 * The converse of above point is not necessarily true: the {{ML_gmxCodelists.xml}} file may
contain only a subset of {{gmxCodelists.xml}}.
 * All English descriptions in {{ML_gmxCodelists.xml}} file are strictly identical to the
ones in {{gmxCodelists.xml}}.
 * Descriptions in other languages than English exist only in {{ML_gmxCodelists.xml}}.

We presume that the same assumptions hold also for the {{resources/uom/gmxUom.xml}} file and
its localized variant.

Problem is that the multilingual variant does not contain all code list defined in the unlocalized
variant. Consequently is we wanted to marshal a valid document, strictly speaking we should
probably take in account which code lists are internationalized and which one are not. As
of Apache SIS 0.4, we avoid this problem for now be referencing only the unlocalized variant.

We may want to reference multilingual files in some circumstance in a future SIS version,
maybe depending on user's locale. This issue is for tracking such potential need.

This message was sent by Atlassian JIRA

View raw message