A.01.04.language.parameter

[jensscheerlinck]

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

Comment

IR N2 reference should be part A and not part B
XPATH expression is missing

Proposed Change

Update reference to IR N2

Add XPATH reference

[PeterParslow]

In addition, add a list of the language tags which are allowed - i.e. the default language has to be on of these. This should be the list of Community languages as specified in Metadata TG (see requirement 15). See #17 , #31,

[PeterParslow]

This test case is a summary case, which should consist of a number of sub test cases. Because requirement 24 is the general requirement. One group (requirements 6,7,8,23,25-29) tests the 'language' functionality of the Get Discovery Service Metadata operation; another group (requirements 9-12,20, 30-32) tests the language functionality of the Discover Metadata operation; a third group could check that the functionality is advertised correctly in the metadata.

Several requirements appear to be generic if read in isolation, but are clearly assigned to a specific section of the TG, and should therefore be specific to that operation.

Conversely, requirement 25 is in the generic section, but explicitly applies to the Get Discovery Service Metadata operation. And more importantly, the list of language codes (requirement 23) is explicitly associated with the metadata (GetCapabilities response), but implicitly controls the languages that may be supported by the Discover Metadata operation!

In order to automate the test sequence, it is likely that this third group needs to be checked first & then the service tested against its description in the metadata. For example:

• Get the service metadata in default language (which itself has multiple scenarios); check whether the service claims to be multi-lingual (i.e. supports more than one language) (A.01.05 and A.01.05.iso-639.codes #32)
• test whether the Get Discovery Service Metadata (GetCapabilities) supports the language parameter (see A.02.02 and A.02.02.additional.language.parameter #35; A.02.08 and A.02.08.natural.languages #41; A.02.09 and A.02.09.response.language #42; A.02.10 and A.02.10.supported.languages #43; A.02.11 and A.02.11.xml.schema #60):
  ** try a supported but not default language
  ** try an unsupported language (A.01.06 and A.01.06.unsupported.languages #33, A.1.6 #18)
• test whether the Discover Metadata (GetRecords) operation supports filtering by language (A.03.03 and A.03.03.language.search.attribute #46; A.03.08 A.03.08.language.search.criteria #51; A.03.10 A.03.10.missing.language.filter #53; A.03.11 A.03.11.language.filter #54; A.03.12 and A.03.12.invalid.request #55 )
  Note: the service need not advertise the languages of the records within it, so it is difficult to tell whether this test passes without already knowing what records are contained in the service under test.

Recommendation: include an overall description of language testing in this test case.