search

inspire-eu-validation / discovery-service

Abstract Test Suite for the Technical Guidance for INSPIRE Discovery Services
Creative Commons Zero v1.0 Universal
0 stars 0 forks source link

A.1.5 #17

Open jensscheerlinck opened 8 years ago

jensscheerlinck commented 8 years ago

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685

Comment

In note 1one cannot help thinking it might be a good idea to get the two documents in question synchronized

Proposed Change

Synchronize the two documents.

jensscheerlinck commented 8 years ago

Proposed Resolution

Remove note +

Proposal to change the technical guidelines. A different list of language codes is used by the Technical Guidelines for INSPIRE metadata and Technical Guidance for INSPIRE Discovery Services. Respectively they use 24 official EU languages and the EU languages + EFTA country languages. 1 list should be chosen to be used in all technical guidelines

PeterParslow commented 8 years ago

The TG requirement for language codes is Requirement 15, which explicitly states which codes may be provided by a client, and therefore implicitly indicates which codes should be handled by a server. It explicitly references the Metadata TG. The Metadata IR requires the metadata itself to be in one of the languages of the Community (although the data can be in another language). This doesn't prevent a Discovery Service from operating in an EFTA language, but such behaviour is outside its INSPIRE functionality. Recommend: remove the values from Table 8 in the TG Recommend: create an INSPIRE "language code register", independent of Metadata TG & Network Services TGs, and reference it from each of them. Move the information from table 9 into this register. In this Discovery Service TG, amend Requirement 15 to reference the register. Alternative: remove the values from Table 8 in the TG. Retain table 9 (although it is generic to network services / OGC OWS).

jensscheerlinck commented 8 years ago

Updated proposed resolution base on comment by @PeterParslow

TG Change Request:

PeterParslow commented 8 years ago

I'd see it more as 'accepted with modification', because we've agreed to 'synchronize' the two documents, just not in the way suggested. But that really doesn't matter:)