Question MD_CharacterSetCode

[heidivanparys]

Is it correct that MD_CharacterSetCode is no longer present in the TC 211 code lists, because the latest 19115-1 refers to https://www.iana.org/assignments/character-sets instead?

I am trying to figure out how to refer to a value from MD_CharacterSetCode in the best way7. When looking through the repo, I see different ways:

• some files use <lan:MD_CharacterSetCode codeList="https://standards.iso.org/19115/-1/1/clause#B.3.14
• some files use <lan:MD_CharacterSetCode codeList="https://www.iana.org/assignments/character-sets/character-sets.xhtml"
• some files use <lan:MD_CharacterSetCode codeList="https://schemas.isotc211.org/19115/-3/lan/1.0/codelists.xml#MD_CharacterSetCode", but file https://schemas.isotc211.org/19115/-3/lan/1.0/codelists.xml does not exist
• some files use <lan:MD_CharacterSetCode codeList="http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml#MD_CharacterSetCode", that version belongs to an older ISO 19115

Any feedback or thoughts on this would be great.

[PeterParslow]

"Is it correct that MD_CharacterSetCode is no longer present in the TC 211 code lists, because the latest 19115-1 refers to https://www.iana.org/assignments/character-sets instead?" - true; I think it's been true since ISO 19115-1:2014 i.e. isn't a result of the 2018 or 2020 amendments.

How to express that in XML Schema - ISO 19139-1:2019 comes into play, setting the UML-XML Schema mapping rules that are then used by ISO 19115-3 (& others). There's no special rule in ISO 19139 for CharacterSetCodep; CodeLists are a "special case encoding" anyway - that's what gives the @codelist attribute

"The codeList attribute is intended to contain a URL that references a codeList's details, within a registry or a codelist catalogue."

So I hope I'm not alone in preferring your second option, with codeList pointing to the IANA list.

ISO 19103 of course adds the instruction / advice (for Code Sets) to set a tagged value to the location of the code list.

@ejbleys : any thoughts why the other patterns occur in the repo?

[ejbleys]

I’ll have a look at this later today EEvert Bleys4 Tudor PlaceHUGHES ACTAustraliaMob: 0411 483 876On 23 Jan 2025, at 02:09, Peter Parslow ***@***.***> wrote: "Is it correct that MD_CharacterSetCode is no longer present in the TC 211 code lists, because the latest 19115-1 refers to https://www.iana.org/assignments/character-sets instead?" - true; I think it's been true since ISO 19115-1:2014 i.e. isn't a result of the 2018 or 2020 amendments. How to express that in XML Schema - ISO 19139-1:2019 comes into play, setting the UML-XML Schema mapping rules that are then used by ISO 19115-3 (& others). There's no special rule in ISO 19139 for CharacterSetCodep; CodeLists are a "special case encoding" anyway - that's what gives the @codelist attribute "The codeList attribute is intended to contain a URL that references a codeList's details, within a registry or a codelist catalogue." So I hope I'm not alone in preferring your second option, with codeList pointing to the IANA list. ISO 19103 of course adds the instruction / advice (for Code Sets) to set a tagged value to the location of the code list. @ejbleys : any thoughts why the other patterns occur in the repo? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[ejbleys]

Hi All Thanks for the query and response. I clearly have some work to do. From IANA we can get links to their registry with representations in XML, HTML, plain text and CSV XML: https://www.iana.org/assignments/character-sets/character-sets.xml HTML: https://www.iana.org/assignments/character-sets/character-sets.xhtml Plain text: https://www.iana.org/assignments/character-sets/character-sets.txt CSV: https://www.iana.org/assignments/character-sets/character-sets-1.csv My apologies for not picking up on ISO 19139-1:2019 "The codeList attribute is intended to contain a URL that references a codeList's details, within a registry or a codelist catalogue” I will version XML files as required. I will use the XML link in the XML files, especially as it renders as HTML in a browser. Unfortunately the IANA registry does not have anchors for each code, but that is of little consequence for these codes. I suggest we DO NOT use the CSV rendering (because of my aversion to using “,” as a field delimiter). I note that TC211 does publish a version of the list of those codes in/at: https://schemas.isotc211.org/19139/-/resources/codelist/MLgmxCodelists.xml and https://schemas.isotc211.org/19139/-/resources/codelist/gmxCodelists.xml but these clearly date from the first implementation of ISO 19115:2003 As http://standards.iso.org/iso/ can no longer be managed by TC211, those will drift on into the future. The reference<lan:MD_CharacterSetCode codeList="https://standards.iso.org/19115/-1/1/clause#B.3.14” ignores the ISO 19139-12019 requirement for it to resolve, but rather references the definition - sorry - Thanks Peter for pointing it out - there will be a lot of remediation to resolve my oversight. Cheers Evert 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.*** Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.***

On 23 Jan 2025, at 02:09, Peter Parslow ***@***.***> wrote: "Is it correct that MD_CharacterSetCode is no longer present in the TC 211 code lists, because the latest 19115-1 refers to https://www.iana.org/assignments/character-sets instead?" - true; I think it's been true since ISO 19115-1:2014 i.e. isn't a result of the 2018 or 2020 amendments. How to express that in XML Schema - ISO 19139-1:2019 comes into play, setting the UML-XML Schema mapping rules that are then used by ISO 19115-3 (& others). There's no special rule in ISO 19139 for CharacterSetCodep; CodeLists are a "special case encoding" anyway - that's what gives the @codelist <https://github.com/codelist> attribute "The codeList attribute is intended to contain a URL that references a codeList's details, within a registry or a codelist catalogue." So I hope I'm not alone in preferring your second option, with codeList pointing to the IANA list. ISO 19103 of course adds the instruction / advice (for Code Sets) to set a tagged value to the location of the code list. @ejbleys <https://github.com/ejbleys> : any thoughts why the other patterns occur in the repo? — Reply to this email directly, view it on GitHub <#232 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIBGJZ6N5T2G5QPFB2FCT2L2L6YDFAVCNFSM6AAAAABVVCECGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBXGUYDGOBYGM>. You are receiving this because you were mentioned.

Heidi wrote “ I am trying to figure out how to refer to a value from MD_CharacterSetCode in the best way7. When looking through the repo, I see different ways: some files use <lan:MD_CharacterSetCode codeList="https://standards.iso.org/19115/-1/1/clause#B.3.14 some files use <lan:MD_CharacterSetCode codeList="https://www.iana.org/assignments/character-sets/character-sets.xhtml" some files use <lan:MD_CharacterSetCode codeList="https://schemas.isotc211.org/19115/-3/lan/1.0/codelists.xml#MD_CharacterSetCode", but file https://schemas.isotc211.org/19115/-3/lan/1.0/codelists.xml does not exist some files use <lan:MD_CharacterSetCode codeList="http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml#MD_CharacterSetCode", that is the version belong to an older ISO 19115

[ejbleys]

Dear Heidi Thanks for your email I’ve made a very minor start on it 6 files/58 occurrences with clause#B.3.14 but that is just the tip of the iceberg as there are 2786 occurrences of clause# in those 6 files 12 files/24 occurrences with https://schemas.isotc211.org/19115/-3/lan/1.0/codelists.xml I can’t find the references to http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml nor https://www.iana.org/assignments/character-sets/character-sets.xhtml (but this is valid) I’ll fix what I can By the way, any idea what a service request to the ISO ODP would look like as we could use the ODP as a reference for the Country codes? I can find them on the ODP but the URL it shows is not usable. (https://www.iso.org/obp/ui/#search) Cheers E Evert Bleys 4 Tudor Place HUGHES ACT 2605 Australia email: ***@***.*** Mob: +61 (0)411 483 876 Land: +61 (0)2 6281 1773 Skype: ***@***.***

…

On 23 Jan 2025, at 01:25, Heidi Vanparys ***@***.***> wrote: Is it correct that MD_CharacterSetCode is no longer present in the TC 211 code lists, because the latest 19115-1 refers to https://www.iana.org/assignments/character-sets instead? I am trying to figure out how to refer to a value from MD_CharacterSetCode in the best way7. When looking through the repo, I see different ways: some files use <lan:MD_CharacterSetCode codeList="https://standards.iso.org/19115/-1/1/clause#B.3.14 some files use <lan:MD_CharacterSetCode codeList="https://www.iana.org/assignments/character-sets/character-sets.xhtml" some files use <lan:MD_CharacterSetCode codeList="https://schemas.isotc211.org/19115/-3/lan/1.0/codelists.xml#MD_CharacterSetCode", but file https://schemas.isotc211.org/19115/-3/lan/1.0/codelists.xml does not exist some files use <lan:MD_CharacterSetCode codeList="http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml#MD_CharacterSetCode", that is the version belong to an older ISO 19115 Any feedback or thoughts on this would be great. — Reply to this email directly, view it on GitHub <#232>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIBGJZ4CCNGFCDYXMEZUTWD2L6S4XAVCNFSM6AAAAABVVCECGOVHI2DSMVQWIX3LMV43ASLTON2WKOZSHAYDINJTGMZTSMQ>. You are receiving this because you are subscribed to this thread.

[PeterParslow]

Regarding CountryCode, the "requirement" in ISO 19115 ("responsibility" in Figure 23, Domain in Table B.18.2, grammatical imperative at B.3.7) is to use ISO 3166-1 "or equivalent"!

B.3.7 references https://www.iso.org/obp/ui/#search which whilst not an API in the sense that we're used to, does at least do the job.

https://www.iso.org/obp/ui/#search/code/ has been "grabbed" to return a list of country codes (although there are many other ISO codes!). The individual codes are more "API like", e.g. https://www.iso.org/obp/ui/#iso:code:3166:AF

That's a pattern that they may or may not extend, a kind of URN: "iso:code::". But this might be overtaken by an API the SMART project is working on.

[heidivanparys]

From IANA we can get links to their registry with representations in XML, HTML, plain text and CSV XML: https://www.iana.org/assignments/character-sets/character-sets.xml HTML: https://www.iana.org/assignments/character-sets/character-sets.xhtml Plain text: https://www.iana.org/assignments/character-sets/character-sets.txt CSV: https://www.iana.org/assignments/character-sets/character-sets-1.csv My apologies for not picking up on ISO 19139-1:2019 "The codeList attribute is intended to contain a URL that references a codeList's details, within a registry or a codelist catalogue” I will version XML files as required. I will use the XML link in the XML files, especially as it renders as HTML in a browser. Unfortunately the IANA registry does not have anchors for each code, but that is of little consequence for these codes. I suggest we DO NOT use the CSV rendering (because of my aversion to using “,” as a field delimiter).

Would it be an option to use https://www.iana.org/assignments/character-sets as the value for codeList? That URL redirects to https://www.iana.org/assignments/character-sets/character-sets.xhtml. There does not seem to be any media type negotiation at present on the IANA server, but by using https://www.iana.org/assignments/character-sets, we don't indicate a preferred media type.

curl -I -i https://www.iana.org/assignments/character-sets
HTTP/1.1 302 Found
Date: Thu, 23 Jan 2025 13:04:42 GMT
Server: Apache
X-Content-Type-Options: nosniff
Vary: Accept-Encoding
Location: https://www.iana.org/assignments/character-sets/character-sets.xhtml
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Cross-Origin-Opener-Policy: same-origin
Cache-Control: public, s-maxage=1800, max-age=3600
Expires: Thu, 23 Jan 2025 14:04:42 GMT
Content-Security-Policy: upgrade-insecure-requests; default-src 'self' https://*.iana.org; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.google.com https://cse.google.com https://clients1.google.com; style-src 'self' 'unsafe-inline' https://www.google.com; child-src 'self' https://www.youtube.com https://clients1.google.com https://cse.google.com https://www.google.com/; img-src 'self' https://data.iana.org https://www.iana.org https://www.google.com https://www.googleapis.com https://clients1.google.com https://*.gstatic.com;
Age: 470
Content-Type: text/html; charset=utf-8
Strict-Transport-Security: max-age=48211200; preload

I can’t find the references to http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml nor https://www.iana.org/assignments/character-sets/character-sets.xhtml (but this is valid)

I just searched in the GitHub repo for <lan:MD_CharacterSetCode codeList=", and found those different occurrences. I repeated the search now on in a local repo, with the following results (I may have missed some variants!):

code list	count
http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml	4
https://schemas.isotc211.org/19115/-3/lan/1.0/codelists.xml	26
https://www.iana.org/assignments/character-sets/character-sets.xhtml	24
https://standards.iso.org/19115/-1/1/clause#B.3.14	78
https://schemas.isotc211.org/19115/resources/Codelist/lan/CharacterSetCode.xml	8
https://schemas.isotc211.org/19115/-1/lan/1.3/codelists.xml#MD_CharacterSetCode	7
https://schemas.isotc211.org/19115/-1/lan/2.1/codelists.xml#MD_CharacterSetCode	6
https://schemas.isotc211.org/Resources/codelists.xml#ISO19115.lan.CharacterSetCode	4
https://schemas.isotc211.org/Resources/codelists.xml#ISO19115-1.1.lan.CharacterSetCode	2

See search_results.txt for detailed search results.

[heidivanparys]

I’ll fix what I can By the way, any idea what a service request to the ISO ODP would look like as we could use the ODP as a reference for the Country codes? I can find them on the ODP but the URL it shows is not usable. (https://www.iso.org/obp/ui/#search)

During the ISO 19103 revision project, I spent quite some time on trying to find out how to properly reference the different country code sets defined by ISO. My conclusion was that those country code sets do not have any official identifiers, see also ISO 19103:2024, 7.8, example 2. No substantial comments came on that example during the enquiry phase, so there seems to be no objection to my conclusion…

I actually think it is rather problematic that those code sets do not have any official identifier, or as a minimum an unambiguous URL. I don't know whether this is something TC 211 could take up with ISO, this is not just an XMG issue.

[ejbleys]

ThanksIt seems the standard number + the code itself is the identifier, which is a bit ugly! https://www.iso.org/obp/ui/#iso:code:3166:AUCheersEvertEvert Bleys4 Tudor PlaceHUGHES ACTAustraliaMob: 0411 483 876On 24 Jan 2025, at 00:36, Heidi Vanparys ***@***.***> wrote: I’ll fix what I can By the way, any idea what a service request to the ISO ODP would look like as we could use the ODP as a reference for the Country codes? I can find them on the ODP but the URL it shows is not usable. (https://www.iso.org/obp/ui/#search) During the ISO 19103 revision project, I spent quite some time on trying to find out how to properly reference the different country code sets defined by ISO. My conclusion was that those country code sets do not have any official identifiers, see also ISO 19103:2024, 7.8, example 2. No substantial comments came on that example during the enquiry phase, so there seems to be no objection to my conclusion… I actually think it is rather problematic that those code sets do not have any official identifier, or as a minimum an unambiguous URL. I don't know whether this is something TC 211 could take up with ISO, this is not just an XMG issue. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[heidivanparys]

ThanksIt seems the standard number + the code itself is the identifier, which is a bit ugly! https://www.iso.org/obp/ui/#iso:code:3166:AU

ISO 3166-1 defines three code sets, see https://www.iso.org/iso-3166-country-codes.html

The country codes can be represented either as a two-letter code (alpha-2) which is recommended as the general-purpose code, a three-letter code (alpha-3) which is more closely related to the country name and a three-digit numeric code (numeric-3) which can be useful if you need to avoid using Latin script.

So when you create an application schema, and you want to reference the ISO 3166-1 alpha-2 country codes, https://www.iso.org/obp/ui/#iso:code:3166 is not specific enough. When interchanging data, one needs to know exactly what code set is used. Which ofAU, AUS or 036 will be used.