[
https://issues.apache.org/jira/browse/SIS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux closed SIS-419.
-----------------------------------
> Implement (un)marshalling of gco:Record
> ---------------------------------------
>
> Key: SIS-419
> URL: https://issues.apache.org/jira/browse/SIS-419
> Project: Spatial Information Systems
> Issue Type: New Feature
> Components: Metadata
> Affects Versions: 0.8
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Priority: Minor
> Fix For: 1.0, 1.3
>
>
> We do not support yet the XML (un)marshalling of {{gco:Record}} and
> {{gco:RecordType}} elements. One difficulty is that a {{Record}} is a kind of
> _key-value_ pairs (like a {{java.util.Map}}) and we did not found a lot of
> examples about how to represent that. Looking at [this file from
> data.gov|https://catalog.data.gov/harvest/object/d2901928-f55b-4ef3-88e9-9de7d3e30554],
> we found the following that looks like _key-description_ pairs separated by
> colon:
> {code:xml}
> <gco:Record>Alphanumeric values: Product is alphanumeric.</gco:Record>
> <gco:Record>Alphanumeric Text: Message contains alphanumeric
> text.</gco:Record>
> <gco:Record>Part A: Reflectivity presented as a tabular listing of
> alphanumerics</gco:Record>
> {code}
> But we found also code lists:
> {code:xml}
> <gco:Record>
> <gmd:CodeListValue codelist="someURL#DataQualityAssessment"
> codeListValue="intermediate">intermediate</gmd:CodeListValue>
> </gco:Record>
> {code}
> The record types examples seems similar (reformatted on many lines below for
> readability):
> {code:xml}
> <gco:RecordType>
> General Meteorological Products: General products include the baseline
> reflectivity and velocity,
> and also algorithmic graphic products spectrum width, vertical integrated
> liquid, and VAD wind profile.
> </gco:RecordType>
> {code}
> Unmarshalling implementation in Apache SIS 1.0-SNAPSHOT is:
> * For {{gco:RecordType}}, take the part on the left side of the colon as the
> member name. Part of the right side is discarded, since we currently have no
> place where to store the description of a member.
> * For {{gco:Record}}, store the text as-is (no parsing).
> We may need to revisit this naive implementation if we find more examples of
> how records are represented in XML files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)