Enquiry #2728

Localised versions of ISO code lists

Added by Ilkka Rinne over 4 years ago. Updated over 4 years ago.

Status:NewStart date:23 Mar 2016
Priority:NormalDue date:30 Mar 2016
Assignee:Ilkka Rinne% Done:

0%

Category:-
Target version:TG2.0 RC1

Description

By: Marie Lambois

Chapter/section: 2.2.3

Paragraph/table: Note 11

Type: te

Comment: Is it required to use the ISO  official codelist repository ? It might not fulfil multilingual needs (see above).

Proposal: Please consider not using shall.

 

Note the section numbers refer to version TG v2.0 RC1 (https://ies-svn.jrc.ec.europa.eu/attachments/download/1570/TG_MD_20_RC1_2016-02-29.pdf) 

History

#1 Updated by Ilkka Rinne over 4 years ago

Personally I would like to mandate linking to a non-localized version of the codelists. Localized code lists make validation more difficult.

#2 Updated by Angelo Quaglia over 4 years ago

The validation of the codeList attribute value is unnecessary and actually to be avoided when using standard ISO without extension and even in that case extensions would need to be documented elsewhere.

The official dictionary of code list values is inside 19115 and 19119.

#3 Updated by Ilkka Rinne over 4 years ago

Angelo Quaglia wrote:

The validation of the codeList attribute value is unnecessary and actually to be avoided when using standard ISO without extension and even in that case extensions would need to be documented elsewhere. The official dictionary of code list values is inside 19115 and 19119.

That may be, but the codeList attribute is mandatory by the XML Schema rules. So something must be given as the value. For documentation's sake I would require referring to a resource where the code list values are available for inspection. Not everyone has the copies of the ISO standards available. 

#4 Updated by Angelo Quaglia over 4 years ago

Ilkka Rinne wrote:

That may be, but the codeList attribute is mandatory by the XML Schema rules. So something must be given as the value. For documentation's sake I would require referring to a resource where the code list values are available for inspection. Not everyone has the copies of the ISO standards available. 

 

You do not need a copy of 19115 for that.

Codelist values relevant for INSPIRE are included in the Metadata Regulation and have been taken from ISO 19115 in agreement with ISO.

 

We must keep ISO 19139 well distinct from 19115 and 19119.

If you look carefully at the examples contained in 19139 you will understand how unreliable the value of the codeList attribute is.

The codeList attribute must be present but its value can even be an empty string. Let's leave users free to put local references or whatever they need.

I do not see the usefulness of declaring non-conformant a plain (i.e. without extensions) metadata document because of the otherwise useless codeList attribute value.

 

 

 

 

#5 Updated by Ilkka Rinne over 4 years ago

Hi Angelo, I'm open for concrete suggestions regarding the codeList attribute value. I don't have a stake here other than providing as clear and unambiguous text as possible.

If the group so decides, I will remove any text in TG Requirements for referring the the ISO 19139 code lists and their values. But in this case I would like to include information about the use of the codeList attributes and the code list values they should refer to in the INSPIRE context.

 

 

Also available in: Atom PDF