<?xml version="1.0" encoding="utf-8"?>
<xs:schema targetNamespace="http://lpis.jrc.ec.europa.eu/registry/6.4.0" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cap="http://lpis.jrc.ec.europa.eu/registry/6.4.0" elementFormDefault="qualified">
	<xs:annotation>
		<xs:documentation>
--Name--
Application schema describing LPIS QA MTS.

-- Definition --
Model of Quality assessment framework for LPIS systems. Model dedicated to perform executable test cases (derived from LCM) against MS SUT (LPIS systems).

-- Description --
The contents of an «XSDschema» package exported as a Application Schema file. It contains descriptions of abstract test cases and executable test cases (within abstract test cases). Executable test cases should be run by MS against their SUT , IUT (LPIS). Executable test case set XML file with records (minimum 68 executables test cases within 4 abstract test cases) then should be sent back to JRC.</xs:documentation>
	</xs:annotation>
	<xs:include schemaLocation="LpisCommonTypes.xsd"/>
	<xs:element name="ExecutableTestCaseSet" type="cap:ExecutableTestCaseSetType">
		<xs:annotation>
			<xs:documentation>
--Name--
Executable test case to level set.

-- Definition --
Specific test of an implementation to meet particular requirements (ISO 19105:2000).

-- Description --
Set of performed executable test cases.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="ExecutableTestCaseSetType">
		<xs:annotation>
			<xs:documentation>
--Name--
Executable test case set

-- Definition --
Specific test of an implementation to meet particular requirements (ISO 19105:2000).

-- Description --
Set of performed executable test cases.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="ExecutableTestCase" type="cap:ExecutableTestCaseType" minOccurs="1" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case type

-- Definition --
Specific test of an implementation to meet particular requirements (ISO 19105:2000).

-- Description --
In order to unambiguously define an executable test case it should be described with the attributes presented in this feature type.

NOTE. An executable test is the instantiation of an abstract test case with specific values.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
		<xs:attributeGroup ref="cap:MtsCycleReportIdentificationAttributeGroup"/>
	</xs:complexType>
	<xs:element name="ExecutableTestCase" type="cap:ExecutableTestCaseType"/>
	<xs:complexType name="ExecutableTestCaseType">
		<xs:annotation>
			<xs:documentation>
--Name--
Executable test case

-- Definition --
Specific test of an implementation to meet particular requirements (ISO 19105:2000).

-- Description --
In order to unambiguously define an executable test case it should be described with the attributes presented in this feature type.

NOTE. An executable test is the instantiation of an abstract test case with specific values.

NOTE. All unstructured descriptions should be provided in English. System component or element names (e.g. names of feature classes, attributes or codelist values) should be provided in native/original languages used during implementation of the systems.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="executableFalsificationTest" type="cap:BooleanValue" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case as a falsification test

-- Definition --
Indication whether a falsification test was used in the testing process.

-- Description --
The default testing method in LPISQA is verification test (prove that the SUT is correct). Falsification testing can only demonstrate non-conformance. In case of technical and economic reasons falsification testing can be adopted as a test method for conformance testing.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="executableTestCaseId" type="xs:string" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case identifier

-- Definition --
Unique thematic ID of executable test case.

-- Description --
Nation-wide unique alphanumerical thematic identification code of executable test case (within an abstract test case).</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="executableTestingType" type="cap:TestingTypeValue" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case testing type value

-- Definition --
Indication how the executable test case is being performed.

-- Description --
The test types can be classified as automated and manual.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="executableTestMethod" type="xs:string" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case method

-- Definition --
Method applicable for the executable test case.

-- Description --
Step by step description of the testing process including the verdict criteria.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="executableTestName" type="cap:ExecutableTestNameValue" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case name.

-- Definition --
Unique (within the MTS) name of the executable test case. 

-- Description --
The values of this attribute shall come from the ExecutableTestNameValue code list. </xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="executableTestPerformanceDate" type="xs:date" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case performance date

-- Definition --
Date when executable test case was performed.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="executableTestPurpose" type="xs:string" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case purpose

-- Definition --
Description of the purpose of the executable test.

-- Description --
It should clarify what is being tested and why.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="executableTestResult" type="cap:TestVerdictValue" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case result

-- Definition --
Verdict on the outcome on the specific executable test case.

-- Description --
Conformance result on the outcome of a specific ETS test case.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="executableTestResultDescription" type="xs:string" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Non structured evidence and result description after executable test case is performed

-- Definition --
Any record that supports the decisions during the inspection process.

-- Description --
Free-text description (statement) of the results from the test. If needed, documents (instructions, legal acts, specifications, any text), as well as auxiliary data, supporting the given statements, can be provided. </xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="executableTestType" type="cap:TestTypeValue" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Executable test case type value

-- Definition --
Indication of the test type according to ISO 19105:2000.

-- Description --
The test types can be classified as basic and capability tests.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="iacsId" type="xs:string" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
IACS identifier

-- Definition --
Universally unique identifier of object.

-- Description --
An object identifier (UUID as GlobalID) is a unique object identifier maintained by the responsible body. The identifier is an unique identifier of the object / feature within the IACS system, not an identifier of the real-world phenomenon. GlobalID is not GUID. 

NOTE 1. /* Value of iacsId shall be equal GlobalID (within CAP IACS). */
inv: self.iacsId.Symbol='GlobalID'

NOTE 2. In order to create iacsId it is possible to follow INSPIRE concept for the maintenance or URI.

NOTE 3. It can be said that within the context of the LPIS guidance (DSCG/2014/33), the GLobalID corresponds to the unique identifier, while the GUID corresponds to the thematic identifier.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="implementationUnderTestId" type="xs:string" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Implementation under test identifier

-- Definition --
Unique thematic ID of IUT for which executable test case is dedicated.

-- Description --
Nation-wide unique alphanumerical thematic identification code of IUT (LPIS).

Note 1. For the purpose of this MTS, the LPIS code enumeration from LPIS Common types, defined in ETS reporting could be used.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="modelTestSuiteId" type="xs:string" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Test suite identifier

-- Definition --
Unique thematic ID of model test suite to which the abstract and executable test cases belongs.

-- Description --
Nation-wide unique alphanumerical thematic identification (name or code) of the model test suite.

Note 1. For the purpose of this MTS, a standardized and common coding for all EU MS is proposed, based on 5 -digit number.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="referencedAbstractTestCaseId" type="xs:string" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Abstract test case identifier

-- Definition --
Unique thematic ID of abstract test case.

-- Description --
Nation-wide unique alphanumerical thematic identification code of abstract test case (within an model test suite).

Note 1. For the purpose of this MTS, a standardized and common coding for all EU MS is proposed, based on 2 -digit number.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="referencedAbstractTestCaseName" type="cap:AbstractTestNameValue" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>
--Name--
Reference abstract test case name.

-- Definition --
Reference to the abstract test suite that constitutes the basis of the executable tests. Reference to the abstract test case for which the executable test case(s) is (are) performed.

-- Description --
It might be the name, URI, or URL to the parent ATS. The values of this attribute shall come from the TestTypeMtsValue code list. To one abstract test case at least one executable test case shall correspond.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:simpleType name="BooleanValue">
		<xs:annotation>
			<xs:documentation>
--Name--
Boolean value

-- Definition --
Standard boolean values true and false.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:enumeration value="false"/>
			<xs:enumeration value="true"/>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="TestingTypeValue">
		<xs:annotation>
			<xs:documentation>
--Name--
Testing type value

-- Definition --
Testing type value list.

-- Description --
In manual testing, the specified requirements are verified by a trained operator who follows the steps described in the test method.
In automated testing, specific software is used that operates on the computer readable schema of the IUT.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:enumeration value="automated">
				<xs:annotation>
					<xs:documentation>
--Name--
Automated

-- Definition --
Automated test.

-- Description --
Automated testing may implement the required tests as a software system using either verification testing or falsification testing.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="manual">
				<xs:annotation>
					<xs:documentation>
--Name--
Manual

-- Definition --
Manual testing.

-- Description --
Manual testing may be required when automated testing is too complex and/or human judgement is required. </xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="ExecutableTestNameValue">
		<xs:annotation>
			<xs:documentation>
--Name--
Executable Test case names.

-- Definition --
Predefined executable test cases.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:enumeration value="checkReferenceParcel">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
12

--executableTestCaseId--
1210

--executableTestName--
checkReferenceParcel

--referencedAbstractTestCaseName--
featureTypeCompleteness

--executableTestPurpose--
Check availability of corresponding LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. there is a feature class named "referenceParcel".</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkReferenceParcelId">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1411

--executableTestName--
checkReferenceParcelId

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature class "referenceParcel" within GDB has attribute field "RPId" (thematic identifier or GUID).</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkReferenceArea">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1412

--executableTestName--
checkReferenceArea

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature class "referenceParcel" within GDB has attribute fields "BPS area", "NATURA 2000 area".</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkSupportSchemaType">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1413

--executableTestName--
checkSupportSchemaType

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "SupportSchema" domain in GDB with following values: "BPS", "NATURA 2000", "young farmer schema"; "small farmer schema". For a given reference parcel, there is a specific maximum eligible area value for each of the support schemes defined.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkReferenceParcelBeginLifeSpanVersion">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1414

--executableTestName--
checkReferenceParcelBeginLifeSpanVersion

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "InitialDate" attribute within "referenceParcel" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkReferenceParcelValidFrom">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1415

--executableTestName--
checkReferenceParcelValidFrom

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EfectiveDate" attribute within "referenceParcel" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkReferenceParcelValidTo">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1416

--executableTestName--
checkReferenceParcelValidTo

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EndEfectiveDate" attribute within "referenceParcel" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkReferenceParcelEndLifeSpanVersion">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1417

--executableTestName--
checkReferenceParcelEndLifeSpanVersion

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EndDate" attribute within "referenceParcel" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkReferenceParcelStatusType">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1418

--executableTestName--
checkReferenceParcelStatusType

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "Status" attribute within "referenceParcel" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkReferenceAreaValue">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
15

--executableTestCaseId--
1519

--executableTestName--
checkReferenceAreaValue

--referencedAbstractTestCaseName--
valueType

--executableTestPurpose--
Check availability of corresponding value type for attribute field in LCM ReferenceParcel element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. The values for the maximum eligible area in attribute fields "BPS area", "NATURA 2000 area" of the feature class "referenceParcel" are stored in hectares. The data type is "double". Note: The minimum information required is: (1) the type of unit used for the area values; (2) the data type of the attribute field, together with the precision if applicable.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAgriculturalLand">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
12

--executableTestCaseId--
1220

--executableTestName--
checkAgriculturalLand

--referencedAbstractTestCaseName--
featureTypeCompleteness

--executableTestPurpose--
Check availability of corresponding LCM Agriculture Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. there is a feature class named "agriculture area" within GDB (LPIS).</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAgriculturalLandGeometry">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1421

--executableTestName--
checkAgriculturalLandGeometry

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of geometric representation for the LCM Agriculture Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature class named "agriculture area" has/has not a geometry. The geometric representation used for all classes is polygon.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAgriculturalLandType">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1422

--executableTestName--
checkAgriculturalLandType

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Agriculture Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "AgriculturalArea" domain assigned to "AgriculturalAreaType" field within feature class “referenceParcel”.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAgriculturalLandTypeValue">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
13

--executableTestCaseId--
1323

--executableTestName--
checkAgriculturalLandTypeValue

--referencedAbstractTestCaseName--
extendedCodeList

--executableTestPurpose--
Check the availability, semantic correspondence and completeness of the codelist for the corresponding attribute field of LCM Agriculture Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "AgriculturalArea" domain in GDB with following values: “arable land”, "permanentCrop"; "permanentGrassland".</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAgriculturalLandArea">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1424

--executableTestName--
checkAgriculturalLandArea

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Agriculture Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature classe "referenceParcel" within GDB has attribute fields "eligible area per agriculture type".</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAgriculturalLandAreaValue">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
15

--executableTestCaseId--
1525

--executableTestName--
checkAgriculturalLandAreaValue

--referencedAbstractTestCaseName--
valueType

--executableTestPurpose--
Check availability of corresponding value type for attribute field in LCM Agriculture Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. The values for the maximum eligible area in attribute fields "eligible area per agriculture type" are stored in hectares. The data type is "double". Note: The minimum information required is: (1) the type of unit used for the area values; (2) the data type of the attribute field, together with the precision if applicable.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkNonAgriEligibleLand">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
12

--executableTestCaseId--
1221

--executableTestName--
checkNonAgriEligibleLand

--referencedAbstractTestCaseName--
featureTypeCompleteness

--executableTestPurpose--
Check availability of corresponding LCM  Non Agriculture Eligible Area  element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s)  shall be provided in test result description.

--executableTestType--
capability

--executableTestResultDescription--
Result description e.g.  there is a feature class named "non-agriculture eligible area" within GDB (LPIS)
					</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkNonAgriEligibleLandGeometry">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1425

--executableTestName--
checkNonAgriEligibleLandGeometry

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of geometric representation for the LCM  Non Agriculture Eligible Area  element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s)  shall be provided in test result description.

--executableTestType--
capability

--executableTestResultDescription--
Result description e.g. feature class named "non-agriculture eligible area" has/has not a geometry. The geometric representation used for all classes is polygon.
					</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkNonAgriEligibleLandType">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1426

--executableTestName--
checkNonAgriEligibleLandType

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM  Non Agriculture Eligible Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s)  shall be provided in test result description.

--executableTestType--
capability

--executableTestResultDescription--
Result description e.g. "NonAgriculturalEligibleArea" domain assigned to "NonAgriEligibleLandType" field within feature class “referenceParcel”.
					</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkNonAgriEligibleLandTypeValue">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
13

--executableTestCaseId--
1324

--executableTestName--
checkNonAgriEligibleLandTypeValue

--referencedAbstractTestCaseName--
extendedCodeList

--executableTestPurpose--
Check the availability, semantic correspondence and completeness of the codelist for the corresponding attribute field of LCM Non Agriculture Eligible Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s)  shall be provided in test result description.

--executableTestType--
capability

--executableTestResultDescription--
Result description e.g. "NonAgriculturalEligibleArea" domain in GDB with following values: “afforested agricultural land”, "wetland on formar agricultural land"; "set aside for AEM"
					</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkNonAgriEligibleLandArea">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1427

--executableTestName--
checkNonAgriEligibleLandArea

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM  Non Agriculture Eligible Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s)  shall be provided in test result description.

--executableTestType--
capability

--executableTestResultDescription--
Result description e.g. feature class  "referenceParcel" within GDB has attribute fields "eligible area per agriculture type"
					</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkNonAgriEligibleLandAreaValue">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
15

--executableTestCaseId--
1526

--executableTestName--
checkNonAgriEligibleLandAreaValue

--referencedAbstractTestCaseName--
valueType

--executableTestPurpose--
Check availability of corresponding value type for attribute field in LCM  Non Agriculture Eligible Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s)  shall be provided in test result description.

--executableTestType--
capability

--executableTestResultDescription--
Result description e.g. The values for the maximum eligible area in attribute fields "eligible area per agriculture type"   are stored in hectares. The data type is "double". Note: The minimum information required is: (1) the type of unit used for the area values; (2) the data type of the attribute field, together with the precision if applicable.
					</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkApplication">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
12

--executableTestCaseId--
1230

--executableTestName--
checkApplication

--referencedAbstractTestCaseName--
featureTypeCompleteness

--executableTestPurpose--
Check availability of corresponding LCM Application element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. there is a feature class named "aid application” within GDB (IACS).</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkDeclaredArea">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1431

--executableTestName--
checkDeclaredArea

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Application element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g.feature classe "aid application” within GDB has attribute field “Declared_Area”.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkDeclaredAreaValue">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
15

--executableTestCaseId--
1532

--executableTestName--
checkDeclaredAreaValue

--referencedAbstractTestCaseName--
valueType

--executableTestPurpose--
Check availability of corresponding value type for attribute field in LCM Application element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. The values for the maximum eligible area in attribute field “Declared_Area” are stored in hectares. The data type is "double". Note: The minimum information required is: (1) the type of unit used for the area values; (2) the data type of the attribute field, together with the precision if applicable.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkDeclaredSupportSchemaType">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1433

--executableTestName--
checkDeclaredSupportSchemaType

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Application element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "DeclaredSupportSchema" domain in GDB with following values: "BPS", "NATURA 2000", "young farmer schema"; "small farmer schema".</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkDeclaredAreaValidFrom">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1434

--executableTestName--
checkDeclaredAreaValidFrom

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM Application element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EffectiveDate" attribute within "aid application" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkDeclaredAreaValidTo">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1435

--executableTestName--
checkDeclaredAreaValidTo

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM Application element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EndEffectiveDate" attribute within "aid application" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeature">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
12

--executableTestCaseId--
1240

--executableTestName--
checkLandscapeFeature

--referencedAbstractTestCaseName--
featureTypeCompleteness

--executableTestPurpose--
Check availability of corresponding LCM Landscape Feature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. there is a feature class named "Landscape elements" within GDB (LPIS).</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureGeometry">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1441

--executableTestName--
checkLandscapeFeatureGeometry

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of geometric representation for the LCM Landscape Feature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature class named "landscape element" has/has not a geometry. The geometric representation: line for the following types…., and polygon for the following types.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureId">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1442

--executableTestName--
checkLandscapeFeatureId

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Landscape Feature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature class "Landscape element" within GDB has attribute field " "LFId" (thematic identifier or GUID)</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureType">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1443

--executableTestName--
checkLandscapeFeatureType

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Landscape Feature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature classe "Landscape element" within GDB has attribute field "Type".</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureTypeValue">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
13

--executableTestCaseId--
1344

--executableTestName--
checkLandscapeFeatureTypeValue

--referencedAbstractTestCaseName--
extendedCodeList

--executableTestPurpose--
Check the availability, semantic correspondence and completeness of the codelist for the corresponding attribute field of LCM Agriculture Area element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "LandscapeFeatureType" domain in GDB with following values: "ponds", "groupOfTrees", “hedges”.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureArea">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1445

--executableTestName--
checkLandscapeFeatureArea

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Landscape Feature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature classe "referenceParcel" within GDB has attribute fields "Area".</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureBeginLifeSpanVersion">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1446

--executableTestName--
checkLandscapeFeatureBeginLifeSpanVersion

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM LandscapeFeature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "InitialDate" attribute within "LandscapeFeature" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureValidFrom">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1447

--executableTestName--
checkLandscapeFeatureValidFrom

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM LandscapeFeature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EffectiveDate" attribute within "LandscapeFeature" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureValidTo">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1448

--executableTestName--
checkLandscapeFeatureValidTo

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM LandscapeFeature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EndEffectiveDate" attribute within "LandscapeFeature" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureEndLifeSpanVersion">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1449

--executableTestName--
checkLandscapeFeatureEndLifeSpanVersion

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM LandscapeFeature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EndDate" attribute within "LandscapeFeature" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkLandscapeFeatureAreaValue">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
15

--executableTestCaseId--
15491

--executableTestName--
checkLandscapeFeatureAreaValue

--referencedAbstractTestCaseName--
valueType

--executableTestPurpose--
Check availability of corresponding value type for attribute field in LCM Landscape Feature element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. The values for the maximum eligible area in attribute fields "Area" of the feature class "Landscape Feature" are stored in hectares. The data type is "double". Note: The minimum information required is: (1) the type of unit used for the area values; (2) the data type of the attribute field, together with the precision if applicable.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAnomaly">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
12

--executableTestCaseId--
1250

--executableTestName--
checkAnomaly

--referencedAbstractTestCaseName--
featureTypeCompleteness

--executableTestPurpose--
Check availability of corresponding LCM Anomaly element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. there is a feature class named "Anomalies" within GDB (IACS).</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAnomalyID">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1451

--executableTestName--
checkAnomalyID

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Anomaly element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature classe "Anomalies" within GDB has attribute field "ID" (Unique or thematic identifier).</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkCauseOfAnomaly">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1452

--executableTestName--
checkCauseOfAnomaly

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Anomaly element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature classe "Anomalies" within GDB has attribute field “Anomaly Cause”.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAnomalyStatus">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1453

--executableTestName--
checkAnomalyStatus

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding attribute field in LCM Anomaly element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. feature classe "Anomalies" within GDB has attribute field “Status”.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAnomalyBeginLifeSpanVersion">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1454

--executableTestName--
checkAnomalyBeginLifeSpanVersion

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM Anomaly element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "InitialDate" attribute within "Anomalies" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAnomalyValidFrom">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1455

--executableTestName--
checkAnomalyValidFrom

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM Anomaly element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EffectiveDate" attribute within "Anomalies" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAnomalyValidTo">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1456

--executableTestName--
checkAnomalyValidTo

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM Anomaly element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EndEffectiveDate" attribute within "Anomalies" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="checkAnomalyEndLifeSpanVersion">
				<xs:annotation>
					<xs:documentation>
--referencedAbstractTestCaseId--
14

--executableTestCaseId--
1457

--executableTestName--
checkAnomalyEndLifeSpanVersion

--referencedAbstractTestCaseName--
attributeAndAssociationCompleteness

--executableTestPurpose--
Check availability of corresponding metadata for LCM Anomaly element within SUT.

--executableTestMethod--
Perform source (LCM) target (SUT) element mapping. If there are corresponding LCM element within SUT then test will - pass. If there is no element (s) within the SUT - then test will - fail. Names of corresponding element (s) shall be provided in test result description.

--executableTestType--
Capability test

--executableTestResultDescription--
Result description e.g. "EndDate" attribute within "Anomalies" table in GDB.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="TestVerdictValue">
		<xs:annotation>
			<xs:documentation>
--Name--
Test verdict value

-- Definition --
List of values describing test verdicts.

-- Description --
List of possible test verdict values according to ISO 19105:2000.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:enumeration value="fail">
				<xs:annotation>
					<xs:documentation>
--Name--
Fail

-- Definition --
Fail verdict to indicate that SUT does not fulfil the requirements.

-- Description --
Test verdict of non-conformance . Failure to fulfil one or more requirements specified.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="pass">
				<xs:annotation>
					<xs:documentation>
--Name--
Pass

-- Definition --
Pass verdict to indicate that the tested requirements are fulfilled.

-- Description --
Test verdict of conformance.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="inconclusive">
				<xs:annotation>
					<xs:documentation>
--Name--
Inconclusive

-- Definition --
A value “inconclusive” indicates that the testing process has not yet yield a verdict.


-- Description --
Neither fail nor pass verdict can be assigned based on the test.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="TestTypeValue">
		<xs:annotation>
			<xs:documentation>
--Name--
Test type value

-- Definition --
Indication whether a test belong to the basic or the capability test type.

-- Description --
A basic test is an initial test intended to identify clear cases of non-conformance. If the ATS identifies tests to be used as basic tests, they shall be used at the start of the conformance assessment process.

Capability test is designed to determine whether an IUT conforms to a particular characteristic specified as requirements.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:enumeration value="basic">
				<xs:annotation>
					<xs:documentation>
--Name--
Basic

-- Definition --
Basic test .

-- Description --
Basic tests (BT) provide limited testing of IUT in order to establish whether or not it is appropriate to perform more thorough testing. They may be used to determine the degree of conformance prior to deciding whether or not to proceed with thorough capability testing. Basic tests are simple capability tests. Conformance clauses should identify those test cases that may be used as a basic test.

NOTE1. BT shall be used to for detecting obvious cases of non-conformity.

NOTE2. BT shall be used as a preliminary step in order to decide whether or not to run capability tests.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="capability">
				<xs:annotation>
					<xs:documentation>
--Name--
Capability

-- Definition --
Capability test.

-- Description --
Capability tests (CT), should investigate an implementation as thoroughly as it is practical over the full range of conformance requirements specified in a standard/legal act. Capability tests should be provided to check the mandatory capabilities and those optional capabilities that are identified in the ICS as being supported by the IUT.

NOTE 1. CT shall be used to check that the capabilities of the IUT are consistent with the conformance requirements, that is, to determine whether or not an implementation conforms.

NOTE 2. CT shall be used to investigate causes of failure.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="AbstractTestNameValue">
		<xs:annotation>
			<xs:documentation>
--Name--
Abstract test case values

--Definition--
Abstract test cases applicable in model based testing for LPISQA.

--Description--
These abstract test cases are applicable for conformance testing of the IUT in general. They should be further specified in the executable test cases according to the implementation choices of the MS/Regions. 


NOTE 1. In general the method for all executable test cases, is based on the conduction of source (LCM) target (IUT, and corresponding SUT) element mapping for the purpose of the data ETS and the screening. If there is corresponding LCM element within SUT, test will pass. If there is no element within the IUT, the test will fail. Names of corresponding element(s) shall be provided in test result.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:enumeration value="extendedCodeList">
				<xs:annotation>
					<xs:documentation>
--Name--
Extended code list

--Definition--
Semantic analysis of the extended elements of the code lists managed by the authorities of the MS /regions. 

--Description --
A semantic comparison of the extended code list values have to establish the relation between the extended values and the values included in the LCM. 
When "narrower" extensions are allowed the new values can restrict the semantic meaning of a value within the same code list of the LCM. The mapping between the original and extended value shall be provided.
When "any" extension is allowed that extended values must avoid semantic contradictions with the values already defined in the LCM .

NOTE 1. When "any" extension is allowed, "narrower" code list elements can be introduced too.

NOTE 2. When notification about the extension to the Commission applies, consistency between the schema and the notification shall be preserved. 

NOTE 3. This is a capability test case.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="encoding">
				<xs:annotation>
					<xs:documentation>
--Name--
Encoding

--Definition--
Encoding applicable for data exchange within LPISQA.

--Description--
The xml/gml schema should follow the standard specified by DG JRC. 

NOTE. This is a capability test case.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="featureTypeCompleteness">
				<xs:annotation>
					<xs:documentation>
--Name--
Feature type completeness

--Definition --
Completeness of the IUT in terms of feature types as compared to the LCM.

--Description--
All feature type included in the LCM shall be present in the IUT. No one to one relationship between the corresponding feature types is required. However, rules for schema mapping shall be unambiguous. 

NOTE 1. As best practice, EC services recommend the following solutions:
- one to one mapping between the feature types of the IUT and the LCM
- A feature type in the IUT is a specialisation of a feature type in the LCM.

NOTE 2. This is a capability test case.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="attributeAndAssociationCompleteness">
				<xs:annotation>
					<xs:documentation>
--Name--
Attribute and association completeness

--Definition--
Completeness of the IUT in terms of attributes and associations as compared to the LCM. Eventual omissions trigger fail verdict in the corresponding tests.

--Description--
Attributes and association roles defined in the LCM for the purpose of the data ETS are mandatory. When feature types of the IUT include more attributes than defined in the LCM, this does not influence conformity. However, the definition of these attributes should not semantically contradict with the definitions of those, already defined in the LCM. Omitted attributes/association rules found in course of testing triggers fail verdict in this test.

NOTE 1. From semantic and UML points of view attributes and associations are equivalent. Both describe the properties of the related class (feature type, or data type).

NOTE 2. Zero (0) multiplicity describes a natural state (semantic property) of the attribute/association. Therefore it should not be interpreted as indicator of optional implementation.

NOTE 3. Zero (0) multiplicity of abstract only concepts (no corresponding tangible entities in the real world) means that within a smaller their use is not required. EXAMPLE: identifiers may not be required for specific uses.

NOTE 4. This is a capability test case.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="valueType">
				<xs:annotation>
					<xs:documentation>
--Name--
Value type

--Definition--
Type of the value that a specific attribute can take.

--Description--
Value types can be specified using one of the following methods:
- selecting types of from the conceptual schema language and reference schemas (standards, INSPIRE)
- Data type specified in reference schemas or in the LCM
- Enumeration
- Code list

NOTE 1. for extensible code lists other values than specified in it can be introduced in the IUT. The extended values shall not have semantic contradiction with those values, specified in the LCM. When extension with "narrower" values is allowed, the an new value should be a semantic restriction of the parent value. For example "permanent crop" can be extended with "citrus tree".

NOTE 2. This is a capability test case.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="valueAndConstraint">
				<xs:annotation>
					<xs:documentation>
--Name--
Value and constraint

--Definition--
Range or restricted range of values that a property can take.

--Description--
Constraints are set on value type, values, and association rules in the LCM. Some of them are conditional.

NOTE 1. Unit of measure test is a specific constraint set in order to verify whether area values are expressed in the units specified in the LCM.

NOTE 2. This is a capability test case.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
</xs:schema>