You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it is in conflict with A.01.06 where a default language should be provide anyway.
A.02.09 states that if language requested by client is NOT contained in the list of supported languages, the default language is used as defined in \inspire_common:Language
However based on 3.10 this should be equivalent to missing language parameter? -> In other words, the response should contain metadata records of several natural languages, as provided by the INSPIRE Discovery Service.
The text was updated successfully, but these errors were encountered:
See #54 , A.2.9 is not a pre-requisite as it tests the GetCapabilities operation, and this tests the GetRecords operation. It could be seen that this test case is conditional on the service containing metadata in more than one language, but this is partly described by the requirement wording ("Depending on the discovery service contents").
At A.2.9, it is correct that if no language filter is provided in the GetCapabilites request, the response will be in the default language. Here, at A.3.10, it is correct that if no language filter is provided in the GetRecords request, the response may contain records in several languages.
Proposed resolution: reject this comment.
This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
A.02.09 states that if language requested by client is NOT contained in the list of supported languages, the default language is used as defined in \inspire_common:Language
However based on 3.10 this should be equivalent to missing language parameter? -> In other words, the response should contain metadata records of several natural languages, as provided by the INSPIRE Discovery Service.
The text was updated successfully, but these errors were encountered: