[Esip-documentation] ISO 19115-3 Codelist Usage Question

Wed Sep 6 09:41:04 EDT 2017

Hi Ted,

The XML has changed from 19139 to 19115-3 (unless I'm looking at the wrong
files).  Below is a snippet from 19139 and another from 19115-3.  They are
different.

>From http://www.isotc211.org/2005/resources/Codelist/gmiCodelists.xml
<codelistItem>
<CodeListDictionary gml:id="CI_DateTypeCode">
<gml:description>identification of when a given event occurred
</gml:description>
<gml:identifier codeSpace="ISOTC211/19115">CI_DateTypeCode</gml:identifier>
<codeEntry>
<CodeDefinition gml:id="CI_DateTypeCode_creation">
<gml:description>...</gml:description>
<gml:identifier codeSpace="ISOTC211/19115">creation</gml:identifier>
</CodeDefinition>
</codeEntry>
</CodeListDictionary>
</codelistItem>

>From http://standards.iso.org/iso/19115/resources/Codelist/cat/codelists.xml
<cat:codelistItem>
<cat:CT_Codelist id="CI_DateTypeCode">
<cat:identifier>...</cat:identifier>
<cat:name>...</cat:name>
<cat:definition>...</cat:definition>
<cat:description>...</cat:description>
<cat:codeEntry>
<cat:CT_CodelistValue id="CI_DateTypeCode_creation">
<cat:identifier>
<gco:ScopedName codeSpace="isotc211">CI_DateTypeCode_creation
</gco:ScopedName>
</cat:identifier>
<cat:definition>...</cat:definition>
</cat:CT_CodelistValue>
</cat:codeEntry>
</cat:CT_Codelist>
</cat:codelistItem>

In your example snippet (presented below) you use "creation" as the
codeListValue and value.  However, "creation" does not exist as a value in
19115-3

> <cit:dateType>
>             <cit:CI_DateTypeCode codeList="codeListLocation#CI_DateTypeCode"
> codeListValue="creation">creation</cit:CI_DateTypeCode>
> </cit:dateType>

Instead would this be the correct XML representation?
<cit:dateType>
            <cit:CI_DateTypeCode codeList="codeListLocation#CI_DateTypeCode"
codeListValue="CI_DateTypeCode_creation">CI_DateTypeCode_
creation</cit:CI_DateTypeCode>
</cit:dateType>

Cheers

On Sat, Sep 2, 2017 at 10:12 AM, Ted Habermann <thabermann at hdfgroup.org>
wrote:

> Nathan,
>
>
>
> The XML codeList implementation *has not changed* between ISO 19139 and
> 19115-3.
>
>
>
> The correct code list representation repeats the code list value as an
> attribute and as a value for the element:
>
> <cit:dateType>
>             <cit:CI_DateTypeCode codeList="codeListLocation#CI_DateTypeCode"
> codeListValue="creation">creation</cit:CI_DateTypeCode>
> </cit:dateType>
>
>
>
> I realize that this is redundant, but it also good defensive metadata
> creation. We are not sure where people and tools might be looking for these
> values, so we put it in both places.
>
>
>
> CodeLists are designed to be extended to address needs of specific
> communities, so codeListLocation can vary. You have the most convenient
> standard location (http://standards.iso.org/iso/
> 19115/resources/Codelist/cat/codelists.xml) in your example.
>
>
>
> I’m not sure what you mean in PP 3 about the XML changing and the
> reference to the gml:identifier. The gml:identifier was never used directly
> in ISO metadata. The codeSpace element is also typically not used in most
> XML implementations as the information it was meant to convey is held in
> the codeListLocation. The bit about the “language independent code” was
> deprecated many years ago. That was the original idea and early codeList
> dictionaries included a number like 007 as an identifier, but it became
> impractical and impossible to implement consistently. The English language
> version of the code list value is now the official identifier for each
> codeList concept.
>
>
>
> BTW, we noticed that you have been contributing to the ISO explorer
> <http://wiki.esipfed.org/index.php/MD_Metadata> on the ESIP wiki. Thanks
> for your help on that! Suggestions or questions about improving that
> resource are always welcome…
>
>
>
> Ted
>
>
>
> ==== Ted Habermann ========================
> Director of Earth Science, The HDF Group
> Voice: (217) 531-4202
> Email: thabermann at hdfgroup.org
> ==== HDF: Software That Powers Science ====
>
>
>
> *From: *Esip-documentation <esip-documentation-bounces at lists.esipfed.org>
> on behalf of "esip-documentation at lists.esipfed.org" <
> esip-documentation at lists.esipfed.org>
> *Reply-To: *Nathan Wilson - NOAA Affiliate <nathan.wilson at noaa.gov>
> *Date: *Tuesday, August 29, 2017 at 10:45 AM
> *To: *"esip-documentation at lists.esipfed.org" <esip-documentation at lists.
> esipfed.org>
> *Subject: *[Esip-documentation] ISO 19115-3 Codelist Usage Question
>
>
>
> Does anyone know what the correct implementation of the various codelists
> in -3 xml should look like?  Specifically, what value should be populated
> for the xs:string contents for each gco:CodeListValue_Type.
>
>
>
> <cit:CI_DateTypeCode codeList="http://standards.
> iso.org/iso/19115/resources/Codelist/cat/codelists.xml#CI_DateTypeCode
> <http://standards.iso.org/iso/19115/-3/cit/1.0/codelists.xml#CI_DateTypeCode>
> "
>
>                                      codeListValue="CI_
> DateTypeCode_creation"
>
>                                      codeSpace= "isotc211">(What goes
> here?)</cit:CI_DateTypeCode>
>
>
>
> The xml for codelists changed and <gml:identifier
> codeSpace="ISOTC211/19115">creation</gml:identifier>
> became <gco:ScopedName codeSpace="isotc211">CI_DateTypeCode_creation</gco:ScopedName>.
> So I can no longer use the content of the identifier element.
>
>
>
> In discussion of this with some folks at NOAA it was stated that the codes
> were intended to be a language independent code.  Does this mean that for
> CI_DateTypeCode_creation the value would be based on language, i.e.
> creation if english or creación if Spanish?
>
>
>
> Cheers
>
>
>
> Reference XML snippet:
>
> <cat:codeEntry>
>
> <cat:CT_CodelistValue id="CI_DateTypeCode_creation">
>
> <cat:identifier>
>
> <gco:ScopedName codeSpace="isotc211">CI_DateTypeCode_creation
> </gco:ScopedName>
>
> </cat:identifier>
>
> <cat:definition>
>
> <gco:CharacterString>
>
> date identifies when the resource was brought into existence
>
> </gco:CharacterString>
>
> </cat:definition>
>
> </cat:CT_CodelistValue>
>
> </cat:codeEntry>
>
>
>
> --
>
> Nathan S. Wilson
> Metadata Taxonomist
> Contractor
> Caelum Research Corporation
> In support of Office of Science and Technology
> National Marine Fisheries Service
> 1315 East West Highway, Room 12304
> Silver Spring, MD 20910
> Phone: (301)427-8192 <%28301%29427-8119>
> Email: nathan.wilson at noaa.gov
>

-- 
Nathan S. Wilson
Metadata Taxonomist
Contractor
Caelum Research Corporation
In support of Office of Science and Technology
National Marine Fisheries Service
1315 East West Highway, Room 12304
Silver Spring, MD 20910
Phone: (301)427-8192 <%28301%29427-8119>
Email: nathan.wilson at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-documentation/attachments/20170906/3bf8cd8c/attachment-0001.html>