codelist XML

[amilan17]

I downloaded the zip file and am looking the codelists.xml in this directory: ..\19115\resources\Codelist\cat\codelists.xml

I'd like to request differences between the id and the scopedName for each codeEntry. Such that 'CI_DateTypeCode_publication' is just 'publication' at //cat:codeEntry/cat:CT_CodelistValue/cat:identifier/gco:ScopedName or //cat:codeEntry/cat:CT_CodelistValue/@id Xpaths.

If there a place on github where these codelists are managed - I can register the issue there instead.

Thanks!

[smrgeoinfo]

There is a problem here-- e.g. the gml codelist implementation has DateType codes with @id values like CI_DateTypeCode_creation, the same as the cat:identifier:gco:ScopedName values, but the gml codelists (e.g. CI_DateTypeCode.xml) has opaque @gml:id values like '_12378_18857', and identifier strings that are like 'creation'.

The gml identifiers are consistent with what shows up in instance data (codeListValue='creation'), ALSO-- the codespace uri's are not consistent in the codelists.xml file (some are 'isotc211', others are http://standards.iso.org/iso/19115), and in the gml codelist file they're like http://www.isotc211.org/namespace/cit/1.0/2014-07-11/CI_DateTypeCode)

Here's what I think they should look like: gml dictionary:

<dictionaryEntry>
    <Definition gml:id:="CI_DateTypeCode_publication">
      <description>date identifies when resource was published</description>
      <identifier codeSpace="http://standards.iso.org/iso/19115/resources/Codelist/-1/CI_DateTypeCode#"
        >publication</identifier>
    </Definition>
  </dictionaryEntry>

the 19115-3 codelist catalog:

        <cat:codeEntry>
            <cat:CT_CodelistValue id="CI_DateTypeCode_publication">
               <cat:identifier>
                  <gco:ScopedName codeSpace="http://standards.iso.org/iso/19115/resources/Codelist/-1/CI_DateTypeCode#"
                     >publication</gco:ScopedName>
               </cat:identifier>
               <cat:definition>
                  <gco:CharacterString>date identifies when the resource was issued
                   </gco:CharacterString>
               </cat:definition>
            </cat:CT_CodelistValue>
         </cat:codeEntry>

The codespace on the gco:ScopedName and the gml:identifier is a URI for the codelist. We'd need some kind of rewrite to get what I suggest above to dereference, but the directory structure at standards.iso.org right now isn't set up for versioning and different formats from a single URI. The gco:ScopeName and gml:identifier element values are what should show up as codeListValues in instances. The @id and @gml:id's are local to the document, and include the codelist name and the codelist value in case codelist values are duplicated in the document; they shouldn't be used externally.

[smrgeoinfo]

Still an open issue, needs fixing. Don't know when I can get to it....

[amilan17]

Hi -- any follow up on this reformatting of the codelist structure?

[ebleys]

I've had a crack at the ISO19115 codelists as defined in -1 (attached) In the case of CI_DateTypeCode I have added (non-definitive) names for French and Dutch as examples of where that could go I am unsure of what the most appropriate codeSpaces are but have suggested that there is a need to separate those for the names (preferable also by language)

There remains the question of whether or not the codelists should each reside in their own file: allow specific codes to be picked up in other environments without the baggage of all the codes for the donor standard. it would mean that the ' id="CodeList_code" ' would revert to ' id="code" ' Cheers ISO191152014Codelist.txt

[dr-shorthair]

Codelists better not encoded in XML. GML 3.3 has something to say about this in the introduction to Cluase 11 -

"best-practice is to generally use URIs for referring to items in vocabularies, and RDF (OWL, SKOS) for encoding their descriptions"

For example: http://registry.it.csiro.au/def/isotc211/CI_DateTypeCode

[ebleys]

Thanks Simon That is really helpful as a template I realise I’m just not seeing it but, in the code you provided, where is the URI ? title=http://registry.it.csiro.au/def/isotc211/CI_DateTypeCode/_adopted ? Is the use of “_adopted” indicative of an abstract concept or some other pattern? Is the use of “cI date type code” intentional or a short cut to either “Citation, date type code” or “CI_DateTypeCode”?

Cheers Evert

From the 1st row in the table “

adopted adopted date identifies when resource was adopted Concept , cI date type code experimental

”

[dr-shorthair]

Look at each item separately. For example http://registry.it.csiro.au/def/isotc211/CI_DateTypeCode/adopted makes it clear URI: http://registry.it.csiro.au/def/isotc211/CI_DateTypeCode/adopted

Also note that the data can be downloaded in various formats (using HTTP conneg)

[ebleys]

Thanks How do we progress these SKOS formed vocabs into TC211? How do we progress these into tools like GeoNetwork (maybe its already in V3.4)? Evert

From: Simon Cox [mailto:notifications@github.com] Sent: Tuesday, 14 November 2017 8:16 PM To: ISO-TC211/XML Cc: Bleys, Evert; Comment Subject: Re: [ISO-TC211/XML] codelist XML (#115) [Marketing Mail] [SEC=UNCLASSIFIED]

Look at each item separately. For example http://registry.it.csiro.au/def/isotc211/CI_DateTypeCode/adopted makes it clear URI: http://registry.it.csiro.au/def/isotc211/CI_DateTypeCode/adopted

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/ISO-TC211/XML/issues/115#issuecomment-344193341, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANpKILOjL62LGXLhhJ_oLrm8LOQTqhGUks5s2VpegaJpZM4FPbsA.

---

IMPORTANT - This email and any attachments have been issued by the Australian Government Department of Agriculture and Water Resources. The material transmitted is for the use of the intended recipient only and may contain confidential, legally privileged, copyright or personal information. You should not copy, use or disclose it without authorisation from the Department. It is your responsibility to check any attachments for viruses and defects before opening or forwarding them.

If you are not an intended recipient, please contact the sender of this email at once by return email and then delete both messages. Unintended recipients must not copy, use, disclose, rely on or publish this email or attachments. The Department of Agriculture and Water Resources is not liable for any loss or damage resulting from unauthorised use or dissemination of, or any reliance on, this email or attachments.

If you have received this e-mail as part of a valid mailing list and no longer want to receive a message such as this one, advise the sender by return e-mail accordingly. This notice should not be deleted or altered

[fxprunayre]

How do we progress these into tools like GeoNetwork (maybe its already in V3.4)?

ISO19115-3 is available in the schema plugin repository here https://github.com/metadata101/iso19115-3 (mainly supported for coming 3.4 version). Codelists are still stored in one XML file per language eg. https://github.com/metadata101/iso19115-3/blob/develop/src/main/plugin/iso19115-3/loc/eng/codelists.xml

[ebleys]

François Unfortunately no, github is a development space, and not the authoritative source The authoritative source should be http://standards.iso.org/... BUT the codelist.xml file that is/was there is not appropriate, hence the traffic on this thread Simon COX has suggested that the source should be in SKOS form, fine but: That implies an abandonment of the cat; package provided in ISO19115-3 The toolsets that have been developed need to be remediated No longer cat: but SKOS

Cheers

e BLEYS Evert Mr Data Manager Australian Bureau of Agricultural and Resource Economics and Sciences Department of Agriculture and Water Resources GPO Box 858 Canberra City ACT Australia 2601 Ph: +61 (0)2 6272 5627 Email: Evert.Bleys@agriculture.gov.aumailto:Evert.Bleys@agriculture.gov.au

From: François Prunayre [mailto:notifications@github.com] Sent: Wednesday, 15 November 2017 5:56 PM To: ISO-TC211/XML Cc: Bleys, Evert; Comment Subject: Re: [ISO-TC211/XML] codelist XML (#115) [Marketing Mail] [SEC=UNCLASSIFIED]

How do we progress these into tools like GeoNetwork (maybe its already in V3.4)?

ISO19115-3 is available in the schema plugin repository here https://github.com/metadata101/iso19115-3 (mainly supported for coming 3.4 version). Codelists are still stored in one XML file per language eg. https://github.com/metadata101/iso19115-3/blob/develop/src/main/plugin/iso19115-3/loc/eng/codelists.xml

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/ISO-TC211/XML/issues/115#issuecomment-344502806, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANpKIMqAw1FX91F3FYHGotfYS6HKSVeQks5s2or3gaJpZM4FPbsA.

---

IMPORTANT - This email and any attachments have been issued by the Australian Government Department of Agriculture and Water Resources. The material transmitted is for the use of the intended recipient only and may contain confidential, legally privileged, copyright or personal information. You should not copy, use or disclose it without authorisation from the Department. It is your responsibility to check any attachments for viruses and defects before opening or forwarding them.

If you are not an intended recipient, please contact the sender of this email at once by return email and then delete both messages. Unintended recipients must not copy, use, disclose, rely on or publish this email or attachments. The Department of Agriculture and Water Resources is not liable for any loss or damage resulting from unauthorised use or dissemination of, or any reliance on, this email or attachments.

If you have received this e-mail as part of a valid mailing list and no longer want to receive a message such as this one, advise the sender by return e-mail accordingly. This notice should not be deleted or altered

[tedhabermann]

Many of these codelist problems were addressed in a pull request during 2017 (https://github.com/ISO-TC211/XML/pull/178) and are described in the wiki (https://github.com/ISO-TC211/XML/wiki/CodeLists). I have not had any comments on those updates.