Feature #773

Resource language compliant with INSPIRE directive

Added by Magoni Bruno about 5 years ago. Updated over 4 years ago.

Status:AcceptedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:CATALOG
Target version:Unplanned
Sponsor: Ergonomic impact:
Functional impact:

Description

Regarding INSPIRE implementation rules (V1.3), there are two ways of inserting the language

Examples of XML encoding:
1) Most interoperable: the element value repeats the codeListValue
<gmd:language>
<gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="eng">eng</gmd:LanguageCode>
</gmd:language>
2) Most compliant: the element value is the name of the codeListValue expressed in the
default language of the Metadata
<gmd:language>
<gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/ " codeListValue="eng">English</gmd:LanguageCode>
</gmd:language>

  • most compliant: the element value is the name of the codeListValue expressed in the default language of the metadata (ej: if the metadata is filled in English, the values should be English, Spanish, French…)
  • most interoperable: the element value repeats the codeListValue (ej: eng for English, spa for Spanish, fre for French…)

Such option should be proposed in easySDI CATALOG configuration as many catalogues are implementing such feature in a different ways. Per default behaviour could be the most compliant way...

History

#1 Updated by Mérour Xavier almost 5 years ago

  • Assignee set to Magoni Bruno

@Bruno
I do not find the XML sample ? Can you attach it again please ?

#2 Updated by Magoni Bruno almost 5 years ago

  • Description updated (diff)

#3 Updated by Magoni Bruno almost 5 years ago

  • Assignee changed from Magoni Bruno to Steering Committee

Hi Xavier,

Sorry for missing copy-paste samples. it's done inside updated feature's description.

#4 Updated by Magoni Bruno almost 5 years ago

  • Assignee changed from Steering Committee to Technical Committee

#5 Updated by Magoni Bruno almost 5 years ago

  • Status changed from Request For Comments to Request For Votes

Need to communicate which manipulation should be done on already saved metadata regarding implementation of such feature.
Accepted by everyone...

#6 Updated by Magoni Bruno almost 5 years ago

  • Assignee changed from Technical Committee to Steering Committee

#7 Updated by Teixeira Jérôme almost 5 years ago

+ 1

#8 Updated by Mérour Xavier almost 5 years ago

+1

#9 Updated by Magoni Bruno almost 5 years ago

+1

#10 Updated by Magoni Bruno almost 5 years ago

  • Status changed from Request For Votes to Accepted
  • Assignee deleted (Steering Committee)

#11 Updated by Magoni Bruno over 4 years ago

  • Target version set to Unplanned

#12 Updated by Magoni Bruno over 4 years ago

  • Target version deleted (Unplanned)

#13 Updated by Magoni Bruno over 4 years ago

  • Target version set to Unplanned

Also available in: Atom PDF