Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 5: Testing Conformance of extended XAdES signatures (V2.1.1)
The present document defines the sets of checks required for testing conformance of XAdES signatures against extended XAdES signatures as specified ETSI EN 319 132-2 [2]. It defines only the checks that are specific to extended XAdES signatures. The set of checks that are common to both extended and baseline XAdES signatures@ are defined in ETSI TS 119 134-4 [4]. The complete set of checks to be performed by any tool on XAdES extended signatures is the union of the sets defined within the present document and the set of common checks for testing conformance against ETSI EN 319 132-1 [1] and ETSI EN 319 132-2 [2] defined in ETSI TS 119 134-4 [4]@ as indicated in the normative clauses of the present document. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance@ it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. The only possible inferences are the ones explicitly mentioned in the second paragraph of the present clause. Checks specified by the present document are exclusively constrained to elements specified by ETSI EN 319 132-1 [1] and to certain elements specified by XMLSig [3] that are re-used in XAdES schema definition (like ds:keyInfo). Regarding XAdES properties@ the present document does not addresses the structural requirements that are defined by the XAdES XML Schema that are suitably addressed in ETSI TS 119 134-4 [4]. The present document does not address either requirements that are common to both XAdES signatures as specified in ETSI EN 319 132-1 [1] and ETSI EN 319 132-2 [2]. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by XAdES [1].