hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.3 Asset management | OVR-7.3-01: The requirements specified in ETSI EN 319 401 [2], clause 7.3 shall apply. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.4 Access control | OVR-7.4-01: The requirements specified in ETSI EN 319 401 [2], clause 7.4 shall apply. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.5 Cryptographic controls | OVR-7.5-01: The requirements specified in ETSI EN 319 401 [2], clause 7.5 shall apply. In addition, the following particular requirements apply: OVR-7.5-02: Void. OVR-7.5-02A [CONDITIONAL]: When validation reports are signed, the SVSP public signing certificate corresponding to the SVSP private signing key shall be issued, by a trustworthy CA, in compliance with the NCP+ certificate policy as specified in ETSI EN 319 411-1 [9]. OVR-7.5-03 [CONDITIONAL]: When validation reports are signed, the SVSP private signing key shall be held and used within a secure cryptographic device which: a) Is a trustworthy system which is assured to EAL 4 or higher in accordance with ISO/IEC 15408 [4], EUCC [i.22], [i.23], or equivalent national or internationally recognized evaluation criteria for IT security. This shall be to a security target or protection profile which meets the requirements of the present document, based on a risk analysis and taking into account physical and other non-technical security measures; or b) Meets the requirements identified in ISO/IEC 19790 [5] or FIPS PUB 140-2 [6], level 3 or FIPS PUB 140-3 [7] level 3. OVR-7.5-04 [CONDITIONAL]: When validation reports are signed, the secure cryptographic device required by OVR-7.5-03 should be as per OVR-7.5-03 a). OVR-7.5-05 [CONDITIONAL]: When validation reports are signed, any backup copies of the SVSP private signing keys shall be protected to ensure its integrity and confidentiality by the secure cryptographic device before being stored outside that device. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.6 Physical and environmental security | OVR-7.6-01: The requirements specified in ETSI EN 319 401 [2], clause 7.6 shall apply. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 22 In addition the following particular requirement apply: OVR-7.6-02: The following requirement specified in ETSI TS 119 101 [1], clause 5.2 shall apply to the SVA: GSM 1.4. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.7 Operation security | OVR-7.7-01: The requirements specified in ETSI EN 319 401 [2], clause 7.7 shall apply. In addition the following particular requirements apply: OVR-7.7-02: Void. OVR-7.7-02A: The SVA shall use application environment that is maintained with up-to-date security fixes. OVR-7.7-03: The following requirements specified in ETSI TS 119 101 [1], clause 5.2 shall apply to the SVA: GSM 1.3. OVR-7.7-04: The following requirements specified in ETSI TS 119 101 [1], clause 5.2 shall apply to the SVA: GSM 2.4. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.8 Network security | OVR-7.8-01: The requirements specified in ETSI EN 319 401 [2], clause 7.8 shall apply. In addition the following particular requirements apply: OVR-7.8-02 [CONDITIONAL]: In case remote access to systems storing or processing confidential data is allowed, a policy rule within a formal policy shall be adopted, and described as part of elements required by OVR-6.3-02. OVR-7.8-03 [CONDITIONAL]: In case remote access to systems storing or processing confidential data is allowed, appropriate security measures shall be implemented to protect against the risks of remote access. NOTE: This confidential information can be subscriber related info (like preferences), or signed data that would be stored waiting further processing (e.g. if revocation status data is unavailable). |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.9 Incident management | OVR-7.9-01: The requirements specified in ETSI EN 319 401 [2], clause 7.9 shall apply. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.10 Collection of evidence | OVR-7.10-01: The requirements specified in ETSI EN 319 401 [2], clause 7.10 shall apply. In addition the following particular requirements apply: OVR-7.10-02: The SVSP shall implement event logs to capture information needed for later proofs. In particular: • OVR-7.10-03: Any signature validation shall be logged, possibly together with the identification of the subscriber when this information is known. NOTE: To log the identity of a subscriber is a business decision of the TSP. GDPR [i.15] requires a clear purpose to do so. • OVR-7.10-04: Event logs shall be marked with the time of the event. OVR-7.10-05: The frequency of processing, the (maximal) retention periods, the protection, the back-up procedures of the collection system, the archiving procedures and the vulnerability assessment of the event logs shall be documented in the SVS practice statement. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 23 OVR-7.10-06: The implementation of requirements OVR-7.10.1 to OVR-7.10.3 shall take the applicable privacy requirements into account. OVR-7.10-07: Event logs should include the type of the event, the event success or failure, and an identifier of the person and/or component at the origin for such an event. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.11 Business continuity management | OVR-7.11-01: The requirements specified in ETSI EN 319 401 [2], clause 7.11 shall apply. In addition in order to provide business continuity as specified in the terms and conditions the following particular requirements apply: OVR-7.11-02: Best reasonable efforts shall be undertaken to keep the service available in line with the Service-Level Agreement (SLA), and the necessary technical and organizational precautions shall be taken to ensure this alignment (e.g. is there a business continuity plan, a disaster recovery plan in place, etc.). OVR-7.11-03: Measures should be implemented to avoid interruption by third parties or unintentional interruptions by the user. OVR-7.11-04 [CONDITIONAL]: When validation reports are digitally signed and expected to be validated over the long term, the SVSP should select a signing certificate issued by a CA that provides guarantees on the availability of the information on the status of its certificates and that has a termination plan clearly described in its CPS. NOTE: CA that conforms to ETSI EN 319 411-1 [9] or ETSI EN 319 411-2 [i.17] implements recognized best practices. OVR-7.11-05 [CONDITIONAL]: When validation reports are digitally signed and expected to be validated over the long term, the SVSP should select trusted source(s) for proofs of existence (e.g. a qualified time stamping authority). 7.12 Signature Validation Service provisioning termination and termination plans OVR-7.12-01: The requirements specified in ETSI EN 319 401 [2], clause 7.12 shall apply. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.13 Compliance and legal requirements | OVR-7.13-01: The requirements specified in ETSI EN 319 401 [2], clause 7.13 shall apply. In addition the following particular requirements apply: OVR-7.13-02: When personal data is processed by a third party an appropriate agreement shall be made with third party processors of personal data in order to ensure that they do comply with the requirements stated in the SVSP practice statements and terms and conditions, including with regard to the implementation of technical, organizational and legal measures to protect the personal data. NOTE 1: Both the signed data and the signature may contain personal data. OVR-7.13-03: The SVSP shall NOT store the SD after processing when not necessary. NOTE 2: If the validation service works in combination of a preservation service such data may need to be kept. OVR-7.13-04: The SVSP shall have the overall responsibility for meeting the requirements defined in clauses 5 to 8 even when some or all of its functionalities are undertaken by sub-contractors. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 7.14 Supply chain | OVR-7.14-01: The requirements specified in ETSI EN 319 401 [2], clause 7.14 shall apply. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 24 |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 8 Signature validation service technical requirements | |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 8.1 Signature validation process | VPR-8.1-01: The validation process shall comply with ETSI EN 319 102-1 [3]. NOTE 1: This does not mean that the SVSP has to implement the algorithm specified in ETSI EN 319 102-1 [3], as it allows alternative implementations provided that they produce the same main status indication when given the same set of input information. In particular: • VPR-8.1-02: The minimal set of constraints requested by clause 5.1.4.1 of ETSI EN 319 102-1 [3] may be further specified, e.g. as per ETSI TS 119 172-1 [i.10] (e.g. a list of accepted commitment types). NOTE 2: The signature validation policy is not limited in size or number of constraints (see ETSI EN 319 102-1 [3]). VPR-8.1-03: The validation process shall output a signature validation status indication, one per validated signature, and a signature validation report. VPR-8.1-04: According to the algorithm specified in ETSI EN 319 102-1 [3], the signature validation status required in VPR-8.1-03 shall be TOTAL-PASSED, TOTAL-FAILED or INDETERMINATE. VPR-8.1-05: The SVS shall support at least one (or more) signature validation policy(ies) in such a way that there is always one signature validation policy available as input to the SVA. NOTE 3: A SVS may be unable to check all the constraints of a signature validation policy; the list of actually processed constraints including their result (e.g. PASSED, FAILED, INDETERMINATE) provided in the validation report represents the signature policy used. See also ETSI TS 119 102-2 [i.3]. VPR-8.1-06: The SVS may accept several sources of validation policy, including from the user. VPR-8.1-07: The validation application (SVA) shall comply with the requirements in ETSI TS 119 101 [1], clause 7.4 SIA 1 to SIA 4. VPR-8.1-08: The validation process shall ensure that the signature validation policy that is used corresponds to the strategy defined in the SVS policy and/or the terms and conditions of use of the SVS. VPR-8.1-09: The strategy defined in the SVS policy and/or the terms and conditions of use of the SVS for the selection of the signature validation policy shall at least follow the next principles: • [CONDITIONAL] When the client inputs/selects a signature validation policy the SVSP should as far as possible use the signature validation policy requested by the client. • [CONDITIONAL] When no signature validation policy is provided by the client the SVSP shall use (one of) its own signature validation policy(ies). • [CONDITIONAL] When the signature validation policy provided by the client is not complete the SVSP shall complete it with validation constraint(s) in such a way that the minimal set of validation constraints imposed by the SVSP (as per practice statement or terms and conditions) is reached. • [CONDITIONAL] When there is an indication in a specific validation constraint in the signature validation policy provided by the client conflicting with the SVSP's polices, the SVSP shall have a process to determine the precedence. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 25 NOTE 4: Nothing obliges a SVSP to consider all the constraints from a signature validation policy requested by a client as validation constraints for the signature validating process. There are different cases: the SVSP can decide to impose its signature validation policy. A second case is when the SVSP tries to use the policy referred in the signature but is not able to process it completely (either because it does not understand all or part of it (too exotic or partly not correctly formatted), or because it understands but has no tool/access to validate some elements). ETSI TS 119 442 [i.12] supports error message in the case where the signature validation policy requested by the client cannot be processed; it also supports a way to convey the list of supported signature validation policies to the client. VPR-8.1-10 [CONDITIONAL]: When it is the SVSP that computes the hash of the SD or any attribute like archival attributes, it shall confirm that the integrity of the SD (resp. attribute) has not been compromised. NOTE 5: When it is the client that computes hash(es) this cannot be ensured by the SVSP and left to the responsibility of the client (see also OVR 6.2-16). In particular, the expected hash(es) are the ones computed with the same hash functions than the ones used in the signature. VPR-8.1-11 [CONDITIONAL]: When the SVS aims to validate qualified electronic signatures or qualified electronic seals such as defined by Article 32.1, (respectively Article 40) or to validate advanced electronic signatures or seals based on qualified certificates as defined by Article 32a.1 (respectively Article 40a) of the Regulation (EU) No 910/2014 [i.1], validation process shall follow the requirements of ETSI TS 119 172-4 [8]. VPR-8.1-12: For the same input, the signature validation service shall also have the same output. NOTE 6: The signature validation policy used is part of the input (independent from its source). VPR-8.1-13: The SVS may accept different elements as proofs of existence of a signature. EXAMPLE: External inputs or inputs taken from the signature (self-claims, time-stamps, etc.). |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 8.2 Signature validation protocol | SVP-8.2-01: The protocol used by the SVSP should conform to ETSI TS 119 442 [i.12]. SVP-8.2-02 [CONDITIONAL]: When the SVS provides the option to receive a detailed report and/or to receive the validation status in the response, then the SVS shall ensure consistency between the status provided in the report and in the response. SVP-8.2-03: The signature validation response shall bear the OID of the SVS policy. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 8.3 Interfaces | |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 8.3.1 Communication channel | SVP-8.3.1-01: The communication channel between the client and the SVSP shall be secured; i.e. the SVSP shall offer a way to be authenticated by the client and the confidentiality of the data shall be ensured. SVP-8.3.1-02: The SVSP may securely authenticate the client. NOTE: The identification of the client is especially important if (s)he takes a role in the validation (calculating the hash). In particular, when only the hash is provided to the SVSP, this is a risk for the human end-user. If he receives the validation report via an intermediate that operates the validation client, the validation client could maliciously present a wrong report to the end-user, by providing a wrong hash to the SVS (e.g. deliver hash and signature of another validly signed document to the SVSP and deliver the report on that to the end-user for a malicious document). This authentication is important for traceability reasons. |
35d5677f0b53289dc364bd06ea82a8b1 | 119 441 | 8.4 Signature validation report | SVR-8.4-01: The SVS shall output a status indication and a validation report providing the details of the technical validation of each of the applicable constraints (see ETSI EN 319 102-1 [3]). SVR-8.4-02: The validation report should conform to ETSI TS 119 102-2 [i.3]. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 26 SVR-8.4-03: The signature validation report shall indicate one of the three status defined in ETSI EN 319 102-1 [3], i.e. TOTAL-PASSED, TOTAL-FAILED or INDERTERMINATE. SVR-8.4-04: The validation report shall report sub-indications as specified in ETSI EN 319 102-1 [3]. SVR-8.4-05: The signature validation report shall report on each of the validation constraints that is processed including any validation constraints that have been applied implicitly by the implementation. SVR-8.4-06 [CONDITIONAL]: When the SVS is able to validate signatures against a well identified signature validation policy, the signature validation report may bear the identifier of the signature validation policy. NOTE 1: This is done consistently with the strategy described in the SVSP documentation (see OVR-6.2-10). NOTE 2: This identifier is present in the validation response when the protocol conforms to ETSI TS 119 442 [i.12] and is present in the validation report when it conforms to ETSI TS 119 102-2 [i.3]. EXAMPLE: The referred signature validation policy can be present whether it was completely processed or not, with or without additional validation constraints, or it can only be present when it was completely processed with no additional constraints, etc. SVR-8.4-07 [CONDITIONAL]: When a signature validation policy is not completely processed by the SVS, the report in addition to reporting on validated constraints, shall report on constraints that have been ignored or overridden. SVR-8.4-08: The signature validation report shall bear the identity of the SVSP. SVR-8.4-09 [CONDITIONAL]: When ETSI TS 119 102-2 [i.3] is followed, the signature validation report shall bear the "Validator Information" as defined in ETSI TS 119 102-2 [i.3]. NOTE 3: In the case of a signature validation service, the validator is the SVSP. SVR-8.4-10: The signature validation report shall report the signer's identity. SVR-8.4-11: The signature validation report shall report on any signed attributes (e.g. commitment type). NOTE 4: In case of a non-critical signed attribute, that cannot be decoded, it might be sufficient to put just information on that the attribute is there. SVR-8.4-12: The signature validation report shall bear signature validation process information (e.g. such as defined in ETSI TS 119 102-2 [i.3]) with the following element: a) An identifier indicating the validation process (see ETSI EN 319 102-1 [3], clauses 5.3, 5.5 and 5.6.3) that has been used in validation. SVR-8.4-13 [CONDITIONAL]: When timestamps are present, the validation report should report on the quality of the timestamps (e.g. EU qualified or not). SVR-8.4-14: The validation report shall clearly indicate if the SVS did not perform the hash computation but relied on such a computation done by the client. SVR-8.4-15: The validation report shall clearly indicate the origin of each PoE (from within the signature, from the client, from the server). SVR-8.4-16: The validation report should bear a validation report signature and this should be the SVSP's digital signature. SVR-8.4-17 [CONDITIONAL]: When validation reports are signed the format and the target of the signature should conform to ETSI TS 119 102-2 [i.3]. SVR-8.4-18 [CONDITIONAL]: When validation reports are signed the signature may be in a basic form; it does not need to be time-stamped or further augmented. See also annex F. SVR-8.4-19 [CONDITIONAL]: When the validation report is presented through a webpage the SVSP shall be authenticated within a TLS session. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 27 9 Framework for definition of validation service policies built on a trust service policy defined in the present document NOTE: The TSP can use directly the trust service policies identified in clause 4.2.2 or the TSP can reference a trust service policy that is based on the policies identified in clause 4.2.2 but adds additional requirements or additional constraints to the requirements of the present document. The latter case is described as the SVS policy being built on a trust service policy defined in the present document. OVR-9-01: Void. OVR-9-01a: When building a SVS policy on a trust service policy defined in the present document, the SVS policy shall identify which of the trust service policies defined in the present document it adopts as the basis. OVR-9-02 [CONDITIONAL]: When building a SVS policy on a trust service policy defined in the present document, the policy shall identify any variances it chooses to apply. OVR-9-03 [CONDITIONAL]: When building a SVS policy on a trust service policy defined in the present document, subscribers shall be informed, as part of implementing the terms and conditions, of the ways in which the specific policy adds to or further constrains the requirements of the policy as defined in the present document. OVR-9-04 [CONDITIONAL]: When building a SVS policy on a trust service policy defined in the present document, there shall be a body (e.g. a policy management authority) with final authority and responsibility for specifying and approving the policy. OVR-9-05 [CONDITIONAL]: When building a SVS policy on a trust service policy defined in the present document, a risk assessment shall be carried out to evaluate business requirements and determine the security requirements to be included in the policy for the stated community and applicability. OVR-9-06 [CONDITIONAL]: When building a SVS policy on a trust service policy defined in the present document, the policy shall be approved and modified in accordance with a defined review process, including responsibilities for maintaining the policy. OVR-9-07 [CONDITIONAL]: When building a SVS policy on a trust service policy defined in the present document, a defined review process shall exist to ensure that the policy is supported by the practices statements. OVR-9-08 [CONDITIONAL]: When building a SVS policy on a trust service policy defined in the present document, the TSP shall make available the policies supported by the TSP to its user community. OVR-9-09 [CONDITIONAL]: When building a SVS policy on a trust service policy defined in the present document, revisions to policies supported by the TSP shall be made available to subscribers. OVR-9-10 [CONDITIONAL]: When building a SVS policy on a trust service policy defined in the present document, a unique object identifier shall be obtained for the policy (e.g. OID or URI). ETSI ETSI TS 119 441 V1.3.1 (2025-10) 28 Annex A (informative): Table of contents for signature validation service practice statements 1. Introduction 1.1 Overview 1.1.1 TSP identification 1.1.2 Supported signature validation service policy(ies) (formal OID/URI identification) 1.2 Signature Validation Service Components 1.2.1 SVS actors 1.2.2 Service architecture 1.3 Definitions and abbreviations 1.3.1 Definitions 1.3.2 Abbreviations 1.4 Policies and practices (This clause is about the TSP documentation and the service backgrounds i.e. risks assessment, Inf.Sec. Pol.) 1.4.1 Organization administrating the TSP documentation 1.4.2 Contact person 1.4.3 TSP (public) documentation applicability This clause describes the set of documents related to the validation services, their applicability, and position of the present practice statement within the documentation, their distribution points … At a minimum the following documents exist and need a short description: • the present practice statement (formal OID/URI identification should be used); • the terms and conditions; • the service policy (can be referred), one or more of the above documents identify the supported signature validation polic(ies) (with formal OID/URI identification). The supported signature validation polic(ies) are generally detailed in the signature validations service polic(ies) • risk assessment and Information security policy NOTE: The description of any business (application) domain or any transactional context described in a "signature applicability rules" document. There is no obligation for a TSP to support and publish such rules. 2. Trust Service management and operation This clause may be common to any services offered by the TSP - except for CA that should follow the IETF RFC 3647 ToC [i.21]. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 29 (Either the same clause is reproduced for each service practice statements, in which case because each service policy and security requirements adds elements specific to the services, such requirements need to be addressed in addition, OR there is a common clause that is referred to from each service practice statements.) 2.1 Internal organization 2.1.1 Organization reliability (This clause identifies the obligations of all external organizations supporting the TSP services including the applicable policies and practices (per ETSI EN 319 401 [2].) 2.1.2 Segregation of duties 2.2 Human resources 2.3 Asset management 2.3.1 General requirements 2.3.2 Media handling 2.4 Access control 2.5 Cryptographic controls 2.6 Physical and environmental security 2.7 Operation security 2.8 Network security 2.9 Incident management 2.10 Collection of evidence 2.11 Business continuity management 2.12 TSP termination and termination plans 2.13 Compliance 2.14 Supply chain 3. Signature validation service design 3.1 Signature validation process requirements This clause contains requirements, control objectives and controls in connection with clause 8.1 in ETSI TS 119 441. 3.2 Signature validation protocol requirements 3.3 Interfaces This clause contains requirements, control objectives and controls in connection with clause 8.3 in ETSI TS 119 441. 3.3.1 Communication channel 3.3.2 SVSP - other TSP 3.4 Signature validation report requirements This clause contains requirements, control objectives and controls in connection with clause 8.4 in ETSI TS 119 441. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 30 Annex B (normative): Qualified Validation Service for QES as defined by Article 33 of the Regulation (EU) No 910/2014 VPR-B-01 [CONDITIONAL]: If the SVSP is a QSVSP, all the requirements from clauses 5 to 9 shall apply. In addition: VPR-B-02 [CONDITIONAL]: If the SVSP is a QSVSP the implementation shall comply with ETSI TS 119 172-4 [8]. NOTE 1: When the signature is not fully conformant to the requirements of a Qualified Electronic Signature/Seal, the SVSP can provide complementary information about the signature or seal, e.g. if it is an advanced electronic signature/seal based on a EU qualified certificate. NOTE 2: Void. OVR-B-03 [CONDITIONAL]: If the SVSP is a QSVSP, the SVSP shall test its service to demonstrate the correct implementation of VPR-B-02 and shall describe such tests in its practice statements. OVR-B-04 [CONDITIONAL]: If the SVSP is a QSVSP, the tests in OVR-B-03 shall check different use-cases, positive and negative ones. SVR-B-05 [CONDITIONAL]: If the SVSP is a QSVSP, the validation report shall bear the digital signature of the SVSP. SVR-B-06 [CONDITIONAL]: If the SVSP is a QSVSP, the validation report shall be provided to the client in an automated manner that can be processed by a machine. NOTE 3: Complying with ETSI TS 119 442 [i.12] and with ETSI TS 119 102-2 [i.3] will allow to satisfy this requirement. SVR-B-07 [CONDITIONAL]: If the SVSP is a QSVSP, when the validation report is presented through a webpage the SVSP should be authenticated within a TLS session supported by a certificate issued by a certification authority operating under ETSI EN 319 411-2 [i.17] and conforming to ETSI EN 319 412-4 [i.18]. SVR-B-08 [CONDITIONAL]: If the SVSP is a QSVSP, when timestamps are present, the validation report shall report if the timestamp is a qualified electronic time-stamp as per Regulation (EU) No 910/2014 [i.1]. SVR-B-09 [CONDITIONAL]: If the SVSP is a QSVSP, the information requested by SVR-8.4-08 and 09 shall be under the form of a certificate that bears the name of the QSVSP such as indicated in the official statutes. OVR-B-10 [CONDITIONAL]: When the QSVSP conforms to all normative requirements of the present document including those specified in the present annex B, the QSVSP may use the specific service policy OID defined in clause 4.2.2. VPR-B-11 [CONDITIONAL]: If the SVSP is a QSVSP, the SVSP should control the hash computation (either perform the computation on the server side or control the client if it is allowed on the client side). NOTE 4: Regulation (EU) No 910/2014 [i.1] specifies that the link between the signed document and the signature is part of the conditions for an advanced electronic signature/seal (Articles 26 & 36). Article 32 explicitly requires that the validation process validate such conditions. VPR-B-12 [CONDITIONAL]: If the SVSP is a QSVSP, the signature validation policy shall clearly be identified as a validation policy for validating that a signature is a qualified electronic signature or seal as per Regulation (EU) No 910/2014 [i.1]. NOTE 5: Void. SVR-B-13 [CONDITIONAL]: If the SVSP is a QSVSP, the validation report shall indicate whether the qualified electronic signature is an EU qualified electronic signature or an EU qualified electronic seal. NOTE 6: Void. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 31 VPR-B-14 [CONDITIONAL]: If the SVSP is a QSVSP, the validation report shall allow the relying party to detect any security relevant issues. VPR-B-15 [CONDITIONAL]: If the SVSP is a QSVSP, in order to satisfy VPR-B-13 to VPR-B-14 the validation report should comply with ETSI TS 119 102-2 [i.3]. VPR-B-16 [CONDITIONAL]: When validation reports are signed, the SVSP public signing certificate corresponding to the SVSP private signing key should be issued, in compliance with an appropriate certificate policy specified in ETSI EN 319 411-2 [i.17]. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 32 Annex C (informative): Mapping of requirements to Regulation (EU) No 910/2014 The qualified validation of QES is specified by Article 33.1 of the Regulation (EU) No 910/2014 [i.1] as follows: "A qualified validation service for qualified electronic signatures may only be provided by a qualified trust service provider who: a) provides validation in compliance with Article 32(1); and b) allows relying parties to receive the result of the validation process in an automated manner, which is reliable, efficient and bears the advanced electronic signature or advanced electronic seal of the provider of the qualified validation service." For the qualified validation of qualified electronic seal the Regulation (EU) No 910/2014 [i.1], Article 40 is applicable. Article 40 states that Articles 32 and 33 "shall apply mutatis mutandis to the validation… of qualified electronic seals". Unless stated specifically, in the rest of the present annex QES will mean indifferently qualified electronic seal or qualified electronic signature. Qualified trust service provider The requirements for qualified trust service providers are provided in Article 24.2 (a) to (j) of Regulation (EU) No 910/2014 [i.1]. They are covered by the present document as follows. Article 24.2 of Regulation (EU) No 910/2014 [i.1] Requirements from present document (a) inform the supervisory body of any change in the provision of its qualified trust services and an intention to cease those activities; (This is not specified by technical standards) (b) employ staff and, if applicable, subcontractors who possess the necessary expertise, reliability, experience, and qualifications and who have received appropriate training regarding security and personal data protection rules and shall apply administrative and management procedures which correspond to European or international standards; OVR-7.2-01 OVR-7.13-04 (c) with regard to the risk of liability for damages in accordance with Article 13, maintain sufficient financial resources and/or obtain appropriate liability insurance, in accordance with national law; OVR-7.1-01 (d) before entering into a contractual relationship, inform, in a clear and comprehensive manner, any person seeking to use a qualified trust service of the precise terms and conditions regarding the use of that service, including any limitations on its use; Clause 6.2 (e) use trustworthy systems and products that are protected against modification and ensure the technical security and reliability of the processes supported by them; Clause 7.7, in particular OVR-7.7-01 Clause 8 (f) use trustworthy systems to store data provided to it, in a verifiable form so that: • (i) they are publicly available for retrieval only where the consent of the person to whom the data relates has been obtained; • (ii) only authorised persons can make entries and changes to the stored data; • (iii) the data can be checked for authenticity. Clause 7.13 OVR-7.2-01 Clause 7.5 (g) take appropriate measures against forgery and theft of data; Clauses 7.6 and 7.7 ETSI ETSI TS 119 441 V1.3.1 (2025-10) 33 Article 24.2 of Regulation (EU) No 910/2014 [i.1] Requirements from present document (h) record and keep accessible for an appropriate period of time, including after the activities of the qualified trust service provider have ceased, all relevant information concerning data issued and received by the qualified trust service provider, in particular, for the purpose of providing evidence in legal proceedings and for the purpose of ensuring continuity of the service. Such recording may be done electronically; Clauses 7.10, 7.11 (i) have an up-to-date termination plan to ensure continuity of service in accordance with provisions verified by the supervisory body under point (i) of Article 17(4); Clause 7.12 (j) ensure lawful processing of personal data in accordance with Directive 95/46/EC. Clause 7.13 Providing validation in compliance with Article 32(1) The validation of QES as specified by the Regulation (EU) No 910/2014 [i.1] requires the verification of the conditions listed in Article 32.1 of the Regulation (EU) No 910/2014 [i.1]. To ensure that all conditions required by the Regulation (EU) No 910/2014 [i.1] Articles 32.1 and 40 are verified, a correct validation algorithm is needed. It provides the same deterministic result for a signature or seal submitted to validation. The signature validation policy is crucial for this purpose. ETSI TS 119 172-4 [8], based on the validation algorithm specified in ETSI EN 319 102-1 [3] has been issued with this perspective. The combination of the two above-mentioned standards allows to confirm each element of Article 32.1 (respectively Article 40) of the Regulation (EU) No 910/2014 [i.1]. This is covered by the present document as follows. Article 32.1 of Regulation (EU) No 910/2014 [i.1] Requirements from present document Verification of the conditions listed in Article 32.1 of the Regulation (EU) No 910/2014 VPR-8.1-01, VPR-B-02, VPR-B-03 NOTE: The validation process for EU qualified electronic signature applies thus mutatis mutandis to the validation of EU qualified electronic seal, except the validation requirements relating to pseudonym that are not applicable to electronic seals. Also, the validation process for qualified electronic seal will ensure that the conditions of Article 36 are fulfilled (instead of Article 26). To this regard, the control on the seal creation data by the creator of the seal needs to be ensured, rather than the sole control. The assessment of the conformity to the Regulation (EU) No 910/2014 [i.1] Articles 32 and 40 will necessarily require to test the implementation with, e.g. a series of sample signatures and seal. The EC puts tools at disposal to do so (Connecting Europe Facility (CEF)). They can be used by the SVSP to demonstrate their service conformity and by any conformity assessment body or supervisory body. This is covered by OVR-B-04 and OVR-B-04_bis. Allowing relying parties to receive the result of the validation process as requested in Article 33.1 (b) The requirements with regard to the reception of the result of the validation process are covered by the present document as follows. Article 33.1 (b) of Regulation (EU) No 910/2014 [i.1] Requirements from present document in an automated manner; SVR-B-06 which is reliable; See note. SVR-B-07, SVR-B-09, VPR-B-12 See also below which is efficient; SVR-B-06 bears the advanced electronic signature or advanced electronic seal of the provider of the qualified validation service. SVR-B-05, OVR-7.5-02 NOTE: The reliability of the content is addressed below, in the consideration related to Article 32.2. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 34 Article 32.2 (respectively Article 40) - correct result and detection of security issues In addition, although not specifically required for a qualified validations service, to ensure that the conditions required by the Regulation (EU) No 910/2014 [i.1] Articles 32.2 and 40 are verified, the signature validation report is crucial. ETSI TS 119 102-2 [i.3] has been issued with this perspective, and is recommended as per SVR-8.4-01 and VPR-B-16. Regulation (EU) No 910/2014 [i.1] Articles 32.2 and 40 are supported by the present document as follows. Articles 32.2/40 of Regulation (EU) No 910/2014 [i.1] Requirements from present document The system used for validating the qualified electronic signature shall provide correct result of the validation process SVR-8.4-01, OVR-B-03, OVR-B-04, VPR-B-11 The system used for validating the qualified electronic signature shall allow the relying party to detect any security relevant issues OVR 6.2-13, VR-B-08, VPR-B-15 (i.e. VPR-B-13, SVR-B-14) ETSI ETSI TS 119 441 V1.3.1 (2025-10) 35 Annex D (informative): Recommendations on user interface The following recommendations are for the case that the user interface is part of the SVS. E-01 [CONDITIONAL]: If the user interface is part of the SVS, the user interface should provide the result of the verification in a clear way to the user. E-02 [CONDITIONAL]: If the user interface is part of the SVS, the user interface should be able to present, upon request from the user, a summary of the validation result to the user in a human readable form. E-03 [CONDITIONAL]: If the user interface is part of the SVS, the user interface should be able to display the validation report. E-04 [CONDITIONAL]: If the user interface is part of the SVS, the user interface should be able to present the purported signer's identity, including: a) the signer's certificate subject's distinguished name; b) any signed attributes; c) the distinguished name of the issuing CA; and d) the distinguished name of the hierarchically superior CAs. E-05 [CONDITIONAL]: If the user interface is part of the SVS, the user interface should be able to present: a) the identifier of the signature validation policy used in the validation process; b) any known commitment implied by the signature. E-06 [CONDITIONAL]: If the user interface is part of the SVS, the requirements specified in ETSI TS 119 101 [1], clause 5.1 should apply. E-07 [CONDITIONAL]: If the user interface is part of the SVS, the validation report should be displayed to the client in an 'efficient'/'user friendly'/'understandable' manner. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 36 Annex E (informative): Checklist This annex provides a checklist for self-assessment or independent conformity assessment of TSPs offering signature validation services according to ETSI EN 319 102-1 [3] and ETSI TS 119 101 [1] where applicable. It also aims to facilitate the preparatory activities the trust service provider undertakes. In case of conflict between the requirements listed in the checklist and those specified in the referenced documents, the referenced documents take precedence. The checklist is in the file "Annex-to-TS_119441_v131.xlsx" contained in archive ts_119441v010301p0.zip which accompanies the present document and is available at https://www.etsi.org/deliver/etsi_ts/119400_119499/119441/01.03.01_60/. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 37 Annex F (informative): Validation of validation report signature The validation report can be digitally signed, and the user might ask if he has to use a validation service to validate the signature of the validation report, which would lead to a chicken-and-egg problem. The value of a signature validation service is that the signatures which it is able to validate can be quite complex. The validation service is able to handle complicated scenarios, including the validation in archival format having several levels of archival attributes and handling a large variety of certificate paths to validate. In addition, the validation service can verify additional aspects, like checking if a signature is EU qualified, or if it contains a specific set of attributes. On the other hand, the signature of the validation report has a very specific purpose. It guarantees the integrity and the origin of the report; it shows that the validation was done by a specific trust service provider and that it was not changed. In general, to verify these two points it is not necessary to do a complex validation. It is sufficient to check the signing certificate and that the digital signature can be verified with the corresponding public key. For example in the case of an EU qualified validation service, the signing certificate used in the report can be used to check the trustworthiness of the service by looking it up in the European trusted list. Similar checks on the trustworthiness can be done if a set of certificates of trusted services is available. If the signing certificate is directly contained in such a trust store, it is not even necessary to create the corresponding certificate path. The validation resulting in a validation report and the one to verify the signature of the validation report are not of the same complexity and it is not needed to have a validation service to handle the second one, every basic signature validation tool is able to do this. There may be use-cases where the information provided by a SVSP is to be used as evidence for the long-term preservation of the validated signature. In particular the validation report might need to be preserved; specific solutions avoiding the chicken-and-egg issue mentioned above are specified in signature preservation services documentation and are out of the scope of the present document. ETSI ETSI TS 119 441 V1.3.1 (2025-10) 38 Annex G (informative): Change history Date Version Information about changes August 2018 1.1.1 Publication September 2023 1.1.4 Implemented CR#1: clarification of clause 9 service component policy built on the present document Updated references from ETSI TS 119 102-1 v1.2.1 to ETSI EN 319 102-1 v1.3.1 Updated the accompanying checklist Added Change history July 2025 1.2.2 Implement some small changes as agree in the WI 'RTS/ESI-0019441v131', take into account amendments of the regulation and new version of ETSI EN 319 401 August 2025 1.2.3 • move ETSI TS 119 172-4 to the normative references • adding definition of "secure cryptographic device" • change usage of "cryptographic module" to "secure cryptographic device" • HSM: add EUCC and FIPS PUB 140-3 [7] to be aligned with ETSI EN 319 411-1. • Remove the specific version number of ETSI EN 319 102-1 • OVR-6.1-03: Make the listing of the supported SVS policies in the SVS practice statement mandatory • OVR-6.3-02: Make the documentation of implemented security and privacy controls for protection of personal data mandatory in the security policy • OVR-7.7-02A: Make mandatory to maintain the application environment up to date with security fixes. • OVR-7.7-03: Make to ETSI TS 119 101 [1] GSM 1.3 mandatory ("Well-tested and reviewed implementations of standardized protocol(s) and libraries shall be used") • OVR-7.8-02: Make a formal policy mandatory in case of remote access • VPR-8.1-07: Make requirements ETSI TS 119 101 [1], clause 7.4 SIA 1 to SIA 4 on Software Integrity of the Application mandatory (SIA 1: SCA/SVA/SAA/DA components shall be protected against viruses and malicious software to ensure their integrity. SIA 2: A change-detection mechanism (for example, file-integrity monitoring tools) shall be deployed to detect unauthorized modification (including changes, additions, and deletions) of critical SCA/SVA/SAA/DA components, like for example configuration files. SIA 3: SCA/SVA/SAADA components that have been subject to viruses or malicious software attack shall be repaired or disabled until repair is possible. SIA 4: If software components of the SCA, SVA, SAA or DA are intended to be published or delivered, these components shall be securely delivered, installed and configured.) • SVP-8.2-03: Make the OID of the SVS policy mandatory in the signature validation response • Some requirements on the validation report made mandatory (not the exact format, which is still a should) • Some requirements when creating a policy based on the one described in present standard were made mandatory • OVR-B-04: make check of positive and negative tests mandatory • AVR-7.5-02A/VPR-B-16: add some requirements to the certificate used to sign the report September 2025 1.2.4 Some small changes and update of the checklist ETSI ETSI TS 119 441 V1.3.1 (2025-10) 39 History Document history V1.1.1 August 2018 Publication V1.2.1 October 2023 Publication V1.3.1 October 2025 Publication |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 1 Scope | The present document defines the set of checks to be performed for testing conformance of Trusted Lists as specified in ETSI TS 119 612 [1]. Checks specified by the present document are exclusively constrained to elements specified by ETSI TS 119 612 [1], certain elements defined in ETSI TS 101 903 [2], and certain elements specified in XMLSig [3]. Regarding XML elements, the present document explicitly differentiates between structural requirements that are defined by the different XML Schemas where the tested elements are defined, and the rest of the requirements specified by ETSI TS 119 612 [1]. 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 includes tests on the correctness of the structure of all the elements specified by the XML Schemas associated with ETSI TS 119 612 [1]. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 2 References | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 119 612 (V2.2.1): "Electronic Signatures and Infrastructures (ESI); Trusted Lists". [2] ETSI TS 101 903: "Electronic Signatures and Infrastructures (ESI); XML Advanced Electronic Signatures (XAdES)". [3] W3C Recommendation (2008): "XML-Signature Syntax and Processing (Second Edition)". [4] IETF RFC 2368: "The mailto URL scheme". [5] IETF RFC 3061: "A URN Namespace of Object Identifiers". [6] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". [7] IETF RFC 5646: "Tags for Identifying Languages". [8] ISO/IEC 10646:2014: "Information technology - Universal Coded Character Set (UCS)". [9] Recommendation ITU-T X.509: "Information technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks". [10] FIPS Publication 180-4 (2012): "Secure Hash Standard (SHS)". ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 8 |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] OASIS: "Test Assertions Model Version 1.0". |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: DER Distinguished Encoding Rules EC European Commission EUMS European Union Member State HTTP Hyper Text Transfer Protocol OCSP Online Certificate Status Protocol OID Object IDentifier TSP Trusted Service Providers URI Uniform Resource Identifier URN Uniform Resource Name XML eXtensible Markup Language XMLDSIG eXtensible Markup Language Digital SIGnature |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 4 Overview | The present clause describes the main aspects of the technical approach used for specifying the set of tests to be performed for testing conformance of Trusted Lists against ETSI TS 119 612 [1]. Several types of tests are identified, namely: 1) Tests on the Trusted List structure that are directly derived from the XML Schemas associated to ETSI TS 119 612 [1]. These tests are specified in annex A. 2) Tests on the Trusted List structure that are not defined by the XML schemas associated to ETSI TS 119 612 [1] and that in consequence may not be tested by a XML Schema validator tool. 3) Tests on values of specific elements and/or attributes that cannot be tested by a XML Schema validator tool. 4) Tests on interrelationship between different elements present in the Trusted List (URIs that point to certain elements, for instance). 5) Tests on computations reflected in the contents of the Trusted Lists (digests of certain elements of some certificates, for instance). Tests are defined as test assertions following the work produced by OASIS in "Test Assertions Model Version 1.0" [i.1]. For each Trusted List element, the present document defines a number of test assertions corresponding to the requirements specified in ETSI TS 119 612 [1]. Each test assertion includes: 1) Unique identifier for further referencing. The identifiers of the assertions start with a code identifying the set of requirements the assertion corresponds to, namely: "TL_EUMS". ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 9 2) Reference to the Normative source for the test. 3) The Target of the assertion. In the normative part, this field identifies ETSI TS 119 612 [1]. 4) Prerequisite (optional) is, according to [i.1], "a logical expression (similar to a Predicate) which further qualifies the Target for undergoing the core test (expressed by the Predicate) that addresses the Normative Statement". It is used for building test assertions corresponding to requirements that are imposed under certain conditions. 5) Predicate fully and unambiguously defining the assertion to be tested. 6) Prescription level. Three levels are defined: mandatory, preferred and permitted, whose semantics are as specified in [i.1]. 7) Tag: information on the element tested by the assertion. This indicates that Trusted Lists as specified in ETSI TS 119 612 [1] is the origin of the assertion. Unless indicated otherwise by the name of the clause where the test assertions are defined, any test assertion applies for both European Union Member States (EUMS hereinafter) Trusted Lists and non EUMS Trusted Lists. The present document also defines some specific test assertions for the European Commission (EC hereinafter) List of Lists. Table 1 shows the prefixes used in the present document associated to the URIs of the corresponding namespaces. Table 1: Prefixes used XML Namespace URI Prefix http://uri.etsi.org/02231/v2# tsl http://uri.etsi.org/02231/v2/additionaltypes# tslx http://uri.etsi.org/TrstSvc/SvcInfoExt/eSigDir-1999-93-EC-TrustedList/# sie http://www.w3.org/2000/09/xmldsig# ds http://uri.etsi.org/01903/v1.3.2# xades |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5 Testing Trusted Lists | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1 Testing auxiliary types | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.1 Testing multilingual string types | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.1.1 Testing lang attribute | TA id: TL_EUMS/MLANGSTR/1 Normative source: ETSI TS 119 612 [1], clause 5.1.4. XML Schema defined in ts_119612v020201_201601xsd.xsd. Target: European Union Member State Trusted List. Predicate: The value of the lang attribute is one of the values for European languages specified in IETF RFC 5646 [7] and in clause E.1 of ETSI TS 119 612 [1]. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.1.2 Testing tsl:NonEmptyString type | TA id: TL_EUMS/NEMPTYSTR/1 Normative source: ETSI TS 119 612 [1], clause 5.1.4. XML Schema defined in ts_119612v020201_201601xsd.xsd. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type is not empty. Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 10 |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.1.3 Testing tsl:NonEmptyNormalizedString type | For testing contents of instances of tsl:NonEmptyStringType the test assertions defined in clause 5.1.1.2, and the following test assertions shall apply: TA id: TL_EUMS/NEMPTYNORMSTR/1 Normative source: ETSI TS 119 612 [1], clause 5.1.4. XML Schema defined in ts_119612v020201_201601xsd.xsd. Target: European Union Member State Trusted List. Prerequisite: Use of combining characters is needed but it is possible not to use the combining characters listed in ISO/IEC 10646 [8], clause B.1. Predicate: The content of one instance of this type does not include any of the following whitespace characters: carriage return (#xD), line feed (#A), and tab (#9). Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.1.4 Testing tsl:MultiLangStringType type | For testing contents of instances of tsl:MultiLangStringType the test assertions defined in clauses 5.1.1.1 and 5.1.1.2, and the following test assertions shall apply: TA id: TL_EUMS/MLANGSTR/1 Normative source: ETSI TS 119 612 [1], clause E.2. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type is a string of characters from the Universal Character Set (UCS) as defined by ISO/IEC 10646 [8]. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/MLANGSTR/2 Normative source: ETSI TS 119 612 [1], clause E.2. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type is UTF-8 encoded. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/MLANGSTR/3 Normative source: ETSI TS 119 612 [1], clause E.2. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type does not contain any signature to identify the UCS. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/MLANGSTR/4 Normative source: ETSI TS 119 612 [1], clause E.2. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type does not include private-use characters from the private use zone in the Basic Multilingual Plane and from the private-use Planes 0F and 10 in Group 00. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/MLANGSTR/5 Normative source: ETSI TS 119 612 [1], clause E.2. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type does not include tag characters. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/MLANGSTR/6 Normative source: ETSI TS 119 612 [1], clause E.2. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type is plain text without any mark-up element or tag from languages as SGML, HTML, XML, XHTML, RGF, TeX and others. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/MLANGSTR/7 Normative source: ETSI TS 119 612 [1], clause E.2. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type follows the semantic rules defined by the Unicode Standard for the corresponding characters. Prescription level: preferred Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 11 TA id: TL_EUMS/MLANGSTR/8 Normative source: ETSI TS 119 612 [1], clause E.2. Target: European Union Member State Trusted List. Prerequisite: It is possible to express the content of one instance of this type without using combining characters. Predicate: The content does not use combining characters. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/MLANGSTR/9 Normative source: ETSI TS 119 612 [1], clause E.2. Target: European Union Member State Trusted List. Prerequisite: Use of combining characters is needed but it is possible not to use the combining characters listed in ISO/IEC 10646 [8], clause B.1. Predicate: The content of one instance of this type does not use the combining characters in ISO/IEC 10646 [8], clause B.1. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.1.5 Testing tsl:MultiLangNormStringType type | For testing contents of instances of tsl:MultiLangNormStringType, the test assertions defined in clauses 5.1.1.3 and 5.1.1.4 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.2 Testing tsl:InternationalNamesType type | For testing each tsl:Name child element of instances of tsl:InternationalNamesType the test assertions defined in clause 5.1.1.5, and the following test assertions shall apply: TA id: TL_EUMS/INTNAMES/1 Normative source: ETSI TS 119 612 [1], clause 5.1.4. Target: European Union Member State Trusted List. Predicate: Instances of this type contain one tsl:Name child element whose attribute lang has the value "en". Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.3 Testing tsl:InternationalNamesType type | For testing each tsl:Name child element test assertions defined in clause 5.1.1.5 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.4 Testing types for managing URIs | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.4.1 Testing tsl:NonEmptyURIType type | TA id: TL_EUMS/NEMPTYURI/1 Normative source: XML Schema defined in ts_119612v020201_201601xsd.xsd. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type is not empty. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/NEMPTYURI/2 Normative source: XML Schema defined in ts_119612v020201_201601xsd.xsd. Target: European Union Member State Trusted List. Predicate: The value of the content of one instance of this type is a valid URI Reference as specified in IETF RFC 3986 [6]. Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 12 |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.4.2 Testing tsl:NonEmptyURIListType type | For testing each tsl:URI child element of an instance of tsl:NonEmptyURIListType the test assertions of clause 5.1.4.1 shall apply. TA id: TL_EUMS/NEMPTYURI/1 Normative source: XML Schema defined in ts_119612v020201_201601xsd.xsd. Target: European Union Member State Trusted List. Predicate: The content of one instance of this type is not empty. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.4.3 Testing tsl:NonEmptyMultiLangURIType type | For testing contents of instances of tsl:NonEmptyMultiLangURIType, the test assertions defined in clause 5.1.4.1, and the following test assertion shall apply: TA id: TL_EUMS/NEMPTYMLANGURI/1 Normative source: ETSI TS 119 612 [1], clause 5.1.4. XML Schema defined in ts_119612v020201_201601xsd.xsd. Target: European Union Member State Trusted List. Predicate: The value of the lang attribute is one of the values for European languages specified in IETF RFC 5646 [7] and in clause E.1 of ETSI TS 119 612 [1]. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.4.4 Testing tsl:NonEmptyMultiLangURIListType type | For each tsl:URI child element of one instance of this type the test assertions specified in clause 5.1.4.3 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.5 Testing Country Codes | 5.1.5.1 Test assertions common to Trusted Lists from EUMS, from non EUMS, and the List of Lists from European Commission TA id: TL_COMM/CC/1 Normative source: ETSI TS 119 612 [1], clause 5.1.5. Target: European Union Member State Trusted List. Predicate: The characters of a country code are capital letters. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_COMM/CC/2 Normative source: ETSI TS 119 612 [1], clause 5.1.5. Target: European Union Member State Trusted List. Prerequisite: The value of the country code corresponds to a country Predicate: Valid country code values are as specified in ISO 3166-1 with exceptions as specified in test assertions TL_EUMS_CC/1 and TL_EUMS_CC_2. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.5.2 Test assertions for non EUMS Trusted Lists | TA id: TL_NO_EUMS/CC/1 Normative source: ETSI TS 119 612 [1], clause 5.1.5. Target: non European Union Member State Trusted List. Prerequisite: The country code value is neither one of the codes corresponding to European Union Member States, nor "EU". Predicate: The following are valid exceptional Country code values: commonly used extensions with regional scope, and another identifier recognised for identifying multi-state grouping. Prescription level: mandatory Tag: Country code value exception. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 13 |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.5.3 Test assertions for exceptions within EUMS Trusted Lists | TA id: TL_EUMS/CC/1 Normative source: ETSI TS 119 612 [1], clause 5.1.5. Target: European Union Member State Trusted List. Prerequisite: The country identified by the country code is United Kingdom Predicate: The country code value is "UK". Prescription level: mandatory Tag: Country Code value exception. TA id: TL_EUMS/CC/2 Normative source: ETSI TS 119 612 [1], clause 5.1.5. Target: European Union Member State Trusted List. Prerequisite: The country identified by the country code is Greece Predicate: The country code value is "EL". Prescription level: mandatory Tag: Country Code value exception. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.6 Testing tsl:AddressType type | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.6.1 Introduction | One instance of tsl:AddressType type is a sequence of two elements, namely tsl:PostalAddresses (instance of tsl:PostalAddressListType), and tsl:ElectronicAddress (instance of tsl:ElectronicAddressType type). For testing one instance of AddressType type the test assertions defined in clauses 5.1.6.2 and 5.1.6.3 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.6.2 Testing tsl:PostalAddressListType type | One instance of tsl:PostalAddressListType type contains one or more tsl:PostalAddress children elements. For testing each of the present tsl:StreetAddress, tsl:Locality, tsl:StateOrProvince, tsl:PostalCode, and tsl:CountryName children elements, the test assertions defined in clause 5.1.1.2 shall apply. For testing the lang attribute the test assertions defined in clause 5.1.1.1 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.1.6.3 Testing tsl:ElectronicAddressType type | One instance of tsl:ElectronicAddressType type contains one or more tsl:URI children elements. For testing each tsl:URI child element of instances of tsl:ElectronicAddressType the test assertions defined in clause 5.1.4.3 shall apply. Furthermore the following test assertions shall apply for testing the rest of the contents of instances of tsl:ElectronicAddressType: TA id: TL_EUMS/TSL/EADDR/1 Normative source: ETSI TS 119 612 [1], clause 5.3.5.2. Target: European Union Member State Trusted List. Predicate: One instance of tsl:ElectronicAddressType contains one tsl:URI child element containing a URI Reference identifying an e-mail address compliant with the URI scheme defined in IETF RFC 2368 [4] AND whose lang attribute has the value that identifies English as language. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/EADDR/2 Normative source: ETSI TS 119 612 [1], clause 5.3.5.2. Target: European Union Member State Trusted List. Predicate: One instance of tsl:ElectronicAddressType contains one or more tsl:URI child element containing a URI Reference identifying an e-mail address compliant with the URI scheme defined in IETF RFC 2368 [4] AND whose lang attribute has a value identifying a language different to English. Prescription level: permitted Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 14 TA id: TL_EUMS/TSL/EADDR/2 Normative source: ETSI TS 119 612 [1], clause 5.3.5.2. Target: European Union Member State Trusted List. Predicate: One instance of tsl:ElectronicAddressType contains one tsl:URI child element containing a URI Reference identifying the address of a web-site (with a scheme value equal to "http" or to "https") AND whose lang attribute has the value that identifies English as language. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/EADDR/2 Normative source: ETSI TS 119 612 [1], clause 5.3.5.2. Target: European Union Member State Trusted List. Predicate: One instance of tsl:ElectronicAddressType contains one or more tsl:URI child element containing a URI Reference identifying the address of a web-site (with a scheme value equal to "http" or to "https") AND whose lang attribute has a value identifying a language different to English. Prescription level: mandatory Tag: EUMS Trusted List. 5.2 Testing the elements of the XML representation of the Trusted List |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.1 Introduction | This clause defines the test assertions that apply for testing the contents of the XML representation of the Trusted List, except the test assertions directly derived from the XML Schema definitions. Each subclause defines test assertions for a certain attribute or child element of tsl:TrustServiceStatusList, the root element of the XML representation of the Trusted List. The clauses defining test assertions for children elements may contain sub-clauses defining test assertions for their descendants. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.2 Testing TSLTag attribute | TA id: TL_EUMS/TSL/TAG/1 Normative source: ETSI TS 119 612 [1], clause 5.2.1. Target: European Union Member State Trusted List. Predicate: The value of the TSLTag attribute of tsl:TrustServiceStatusList element is 'http://uri.etsi.org/19612/TSLTag'. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3 Testing tsl:SchemeInformation element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.1 Testing tsl:TSLVersionIdentifier element | TA id: TL_EUMS/TSL/VI/1 Normative source: ETSI TS 119 612 [1], clause 5.3.1. Target: European Union Member State Trusted List. Predicate: The value of the content of the tsl:TSLVersionIdentifier child element of tsl:SchemeInformation element is '5'. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.2 Testing tsl:TSLSequenceNumber element | TA id: TL_EUMS/TSL/SN/1 Normative source: ETSI TS 119 612 [1], clause 5.3.2. Target: European Union Member State Trusted List. Predicate: The value of the content of the tsl:TSLSequenceNumber child element of tsl:SchemeInformation element is not lower than '1'. Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 15 TA id: TL_EUMS/TSL/SN/2 Normative source: ETSI TS 119 612 [1], clause 5.3.1. Target: European Union Member State Trusted List. Prerequisite: The value of the content of the tsl:TSLSequenceNumber child element of tsl:SchemeInformation element is greater than '1'. Predicate: The value of the content of the tsl:TSLSequenceNumber child element of tsl:SchemeInformation element is not re-cycled to '1'. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.3 Testing tsl:TSLType element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.3.1 Test assertions for EUMS Trusted Lists | TA id: TL_EUMS/TSL/TYPE/1 Normative source: ETSI TS 119 612 [1], clause 5.3.3. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is issued by an EU Member State. Predicate: The value of the content of the tsl:TSLType child element of tsl:SchemeInformation element is "http://uri.etsi.org/TrstSvc/TrustedList/TSLType/EUgeneric". Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.3.2 Test assertions for EC List of Lists | TA id: LOL_EU/TSL/TYPE/1 Normative source: ETSI TS 119 612 [1], clause 5.3.3. Target: European Commission List of Lists. Prerequisite: The Trusted List is a List of pointers to EUMS Trusted Lists, issued by EC. Predicate: The value of the content of the tsl:TSLType child element of tsl:SchemeInformation element is "http://uri.etsi.org/TrstSvc/TrustedList/TSLType/EUlistofthelists". Prescription level: mandatory Tag: LOL EU. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.3.3 Test assertions for non EUMS Trusted Lists | TA id: TL_NO_EUMS/TSL/TYPE/1 Normative source: ETSI TS 119 612 [1], clause 5.3.3. Target: non-European Union Member State Trusted List. Prerequisite: The Trusted List is issued neither by an EUMS nor the EC. Predicate: The value of the content of the tsl:TSLType child element of tsl:SchemeInformation element follows the pattern "http://uri.etsi.org/TrstSvc/TrustedList/TSLType/[CC]list", OR is a value starting by "http://uri.etsi/org/". Prescription level: mandatory Tag: non-EUMS Trusted List. TA id: TL_NO_EUMS/TSL/TYPE/2 Normative source: ETSI TS 119 612 [1], clause 5.3.3. Target: non-European Union Member State Trusted List. Prerequisite: The Trusted List is issued neither by an EUMS nor the EC, AND the value of the content of the tsl:TSLType child element of tsl:SchemeInformation element follows the pattern "http://uri.etsi.org/TrstSvc/TrustedList/TSLType/[CC]list". Predicate: [CC] is a country code for a non-EU Member State, a commonly used extension with regional scope, or another identifier recognized for identifying multi-state grouping. Prescription level: mandatory Tag: non-EUMS Trusted List. TA id: LOL_NO_EUMS/TSL/TYPE/1 Normative source: ETSI TS 119 612 [1], clause 5.3.3. Target: non-European List of Lists. Prerequisite: The Trusted List is issued by an non-EU Member State and is a list of pointers to other trusted lists. Predicate: The value of the content of the tsl:TSLType child element of tsl:SchemeInformation element follows the pattern "http://uri.etsi.org/TrstSvc/TrustedList/TSLType/[CC]listofthelists", OR is a value starting by "http://uri.etsi/org/". Prescription level: mandatory Tag: non-EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 16 TA id: LOL_NO_EUMS/TSL/TYPE/2 Normative source: ETSI TS 119 612 [1], clause 5.3.3. Target: non-European List of Lists. Prerequisite: The Trusted List is issued neither by an EUMS nor the EC, AND value of the content of the tsl:TSLType child element of tsl:SchemeInformation element follows the pattern "http://uri.etsi.org/TrstSvc/TrustedList/TSLType/[CC]listofthelists". Predicate: [CC] is a country code for a non-EU Member State, a commonly used extension with regional scope, or another identifier recognized for identifying multi-state grouping. Prescription level: mandatory Tag: non-EUMS LOL. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.4 Testing tsl:SchemeOperatorName element | For testing this element the testing assertions defined in clause 5.1.2 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.5 Testing tsl:SchemeOperatorAddress element | This element is an instance of tsl:AddressType type. For testing this element the testing assertions defined in clause 5.1.6 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.6 Testing tsl:SchemeName element | This element is an instance of tsl:InternationalNamesType type. For testing this element the test assertions defined in clause 5.1.2 shall apply. Additionally, the test assertions defined below for each tsl:Name child element shall also apply. TA id: TL_EUMS/TSL/SCHN/1 Normative source: ETSI TS 119 612 [1], clause 5.3.6. Target: European Union Member State Trusted List. Prerequisite: The lang attribute of the tsl:Name child element has a value indicating English language. Predicate: The value of the tsl:Name child matches the following pattern: CC:EN_name_value being EN_name_value an English name. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SCHN/2 Normative source: ETSI TS 119 612 [1], clause 5.3.6. Target: European Union Member State Trusted List. Prerequisite: The lang attribute of the tsl:Name child element has a value indicating a language different than English language. Predicate: The value of the tsl:Name child matches the following pattern: CC: name_value being name_value the official translation of EN_name_value in TL_EUMS/TSL/SCHN/1 to the language indicated in lang attribute. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SCHN/3 Normative source: ETSI TS 119 612 [1], clause 5.3.6. Target: European Union Member State Trusted List. Predicate: The string CC before the ":" separator in the value of the tsl:Name child element is the same as the value of tsl:SchemeTerritory child element of tsl:TSLSchemeInformationType. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.7 Testing tsl:SchemeInformationURI element | For testing this element test assertions defined in clause 5.1.4.4 shall apply. In addition, for each tsl:URI child element the test assertion defined below shall also apply. TA id: TL_EUMS/TSL/SCHINURI/1 Normative source: ETSI TS 119 612 [1], clause 5.3.7. Target: European Union Member State Trusted List. Predicate: The value of the tsl:URI is a valid URI Reference that is the address of a site that can be remotely contacted. Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 17 |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.8 Testing tsl:StatusDeterminationApproach element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.8.1 Testing tsl:StatusDeterminationApproach for EUMS Trusted Lists | For testing this element test assertions defined in clause 5.1.4.1 shall apply. In addition to the test assertions defined in clause 5.1.4.1, the assertion defined below shall also apply. TA id: TL_EUMS/TSL/STATDA/1 Normative source: ETSI TS 119 612 [1], clause 5.3.8. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from an EU Member State. Predicate: The value of the tsl:StatusDeterminationApproach is "http://uri.etsi.org/TrstSvc/TrustedList/StatusDetn/EUappropriate". Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.8.2 Testing tsl:StatusDeterminationApproach for non-EUMS Trusted Lists | For testing this element test assertions defined in clause 5.1.4.1 shall apply. In addition to the test assertions defined in clause 5.1.4.1, the assertion defined below shall also apply. TA id: TL_NO_EUMS/TSL/STATDA/1 Normative source: ETSI TS 119 612 [1], clause 5.3.8. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from an non-EU Member State. Predicate: The value of the tsl:StatusDeterminationApproach follows the pattern "http://uri.etsi.org/TrstSvc/TrustedList/StatusDetn/CCdetermination". Prescription level: permitted Tag: EUMS Trusted List. TA id: TL_NO_EUMS/TSL/STATDA/2 Normative source: ETSI TS 119 612 [1], clauses 5.3.8 and D.3. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from an non-EU Member State. Predicate: The value of the content of the tsl:StatusDeterminationApproach element is a value starting by "http://uri.etsi/org/". Prescription level: permitted Tag: EUMS Trusted List. TA id: TL_NO_EUMS/TSL/STATDA/3 Normative source: ETSI TS 119 612 [1], clause 5.3.8. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from an non-EU Member State and the value of tsl:StatusDeterminationApproach follows the pattern "http://uri.etsi.org/TrstSvc/TrustedList/StatusDetn/CCdetermination". Predicate: The string CC before 'determination' in the value of the tsl:StatusDeterminationApproach child element is the same as the value of tsl:SchemeTerritory child element of tsl:TSLSchemeInformationType. Prescription level: permitted Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.9 Testing tsl:SchemeTypeCommunityRules element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.9.1 Introduction | For testing the tsl:SchemeTypeCommunityRules element in a EUMS Trusted List, the test assertions defined in clauses 5.1.4.4 and 5.2.3.9.2 shall apply. For testing the tsl:SchemeTypeCommunityRules element in a non EUMS Trusted List, the test assertions defined in clauses 5.1.4.4 and 5.2.3.9.4 shall apply. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 18 |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.9.2 Test assertions specific to EUMS Trusted Lists | TA id: TL_EUMS/TSL/SCHTCOMRUL/1 Normative source: ETSI TS 119 612 [1], clause 5.3.9. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from an EU Member State. Predicate: One of the URIs is "http://uri.etsi.org/TrstSvc/TrustedList/schemerules/EUcommon". Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SCHTCOMRUL/2 Normative source: ETSI TS 119 612 [1], clause 5.3.9. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from an EU Member State. Predicate: One of the URIs follows the pattern http://uri.etsi.org/TrstSvc/TrustedList/schemerules/CC, where CC is the value of tsl:SchemeTerritory element. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SCHTCOMRUL/3 Normative source: ETSI TS 119 612 [1], clause 5.3.9. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from an EU Member State. Predicate: One or more than one URIs are present under the URI that follows the pattern http://uri.etsi.org/TrstSvc/TrustedList/schemerules/CC, where CC is the value of tsl:SchemeTerritory element. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.9.3 Test assertions specific to EC List of Trusted Lists | TA id: LOL_EU/TSL/SCHTCOMRUL/1 Normative source: ETSI TS 119 612 [1], clause D.53. Target: European Union Member State Trusted List. Prerequisite: The list is the EU list of Trusted Lists (the TSL Type is "http://uri.etsi.org/TrstSvc/TrustedList/TSLType/EUlistofthelists"). Predicate: The URI is set to "http://uri.etsi.org/TrstSvc/TrustedList/schemerules/EUlistofthelists". Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.9.4 Test assertions specific to no EUMS Trusted Lists | TA id: TL_NO_EUMS/TSL/SCHTCOMRUL/1 Normative source: ETSI TS 119 612 [1], clause 5.3.9. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is not generated by a Scheme Operator from an EU Member State. Predicate: The URI is defined on purpose or registered under ETSI Identified Organization Domain. Prescription level: mandatory Tag: non-EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.10 Testing tsl:SchemeTerritory element | For testing the tsl:SchemeTerritory element in a EUMS Trusted List, the test assertions defined in clause 5.1.5 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.11 Testing tsl:PolicyOrLegalNotice element | For testing tsl:TSLPolicy children elements the test assertions defined in clause 5.1.4.4 shall apply. For testing tsl:TSLLegalNotice children elements the test assertions defined in clause 5.1.1.4 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.12 Testing HistoricalInformationPeriod element | TA id: TL_EUMS/TSL/HISTINFOP/1 Normative source: ETSI TS 119 612 [1], clause 5.3.12. Target: European Union Member State Trusted List. Predicate: The value for this element is 65535. Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 19 |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.13 Testing tsl:PointersToOtherTSL element | For testing the tsl:ServiceDigitalIdentities child element the test assertions defined in clause 5.4.3 shall apply. For testing the tsl:TSLLocation child element the test assertions defined in clause 5.1.4.1 shall apply. For testing tsl:ServiceDigitalIdentitieschildren elements the test assertions defined in clause 5.4.3 shall apply. Below follows the test assertions that shall apply for testing the content of tsl:AdditionalInformation: 1) For testing tsl:TSLType content the test assertions defined in clause 5.2.3.3 shall apply. 2) For testing tsl:SchemeOperatorName content the test assertions defined in clause 5.2.3.4 shall apply. 3) For testing tsl:SchemeTypeCommunityRulescontent the test assertions defined in clause 5.2.3.9 shall apply. 4) For testing tsl:SchemeTerritory content the test assertions defined in clause 5.2.3.10 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.14 Testing tsl:ListIssueDateTime element | TA id: TL_EUMS/TSL/LISTISSDATETIME/1 Normative source: ETSI TS 119 612 [1], clause 5.3.14. Target: European Union Member State Trusted List. Predicate: This element contains a Coordinated Universal Time (UTC) value. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.15 Testing tsl:NextUpdate element | TA id: TL_EUMS/TSL/NEXTUP/1 Normative source: ETSI TS 119 612 [1], clause 5.3.15. Target: European Union Member State Trusted List. Prerequisite: The Scheme Operator does not ceases its operations. Predicate: This element contains a Coordinated Universal Time (UTC) value. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/NEXTUP/2 Normative source: ETSI TS 119 612 [1], clause 5.3.15. Target: European Union Member State Trusted List. Prerequisite: The Scheme Operator ceases its operations. Predicate: This element has an empty value (neither text nodes nor element nodes). Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/NEXTUP/3 Normative source: ETSI TS 119 612 [1], clause 5.3.15. Target: European Union Member State Trusted List. Prerequisite: This element contains a Coordinated Universal Time (UTC) value. Predicate: The difference between the value of this element and the value of tsl:ListIssueDateTime does not exceeds 6 months. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.16 Testing tsl:DistributionPoints element | For testing the tsl:DistributionPoints element the test assertions defined in clause 5.1.4.2 and the following test assertions shall apply. TA id: TL_EUMS/TSL/DISTPTS/1 Normative source: ETSI TS 119 612 [1], clause 5.3.16. Target: European Union Member State Trusted List. Predicate: All the tsl:URI children point to the identical copies of the current Trusted List or its updated version. Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 20 |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.17 Testing tsl:SchemeExtensions element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.17.1 Test assertions for EUMS Trusted Lists | TA id: TL_EUMS/TSL/SCHEXT/1 Normative source: ETSI TS 119 612 [1], clause 5.3.17. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from an EU Member State. Predicate: This element is not present. Prescription level: mandatory Tag: EUMS Trusted List. It is out of the scope of the present document to define additional test assertions for testing contents of tsl:SchemeExtensions/Extension elements. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.2.3.17.2 Test assertions for non EUMS Trusted Lists | TA id: TL_NO_EUMS/TSL/SCHEXT/1 Normative source: ETSI TS 119 612 [1], clause 5.3.17. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from outside EU. Predicate: This element is present. Prescription level: permitted Tag: Non EUMS Trusted List. It is out of the scope of the present document to define additional test assertions for testing contents of tsl:SchemeExtensions/Extension elements. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.3 Testing tsl:TSPInformation element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.3.1 Testing tsl:TSPName element | For testing each tsl:Name child element of the tsl:TSPName element the test assertions defined in clause 5.1.2 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.3.2 Testing tsl:TSPTradeName element | For testing each tsl:Name child element of the tsl:TSPTradeName element the test assertions defined in clause 5.1.2 and the following test assertions shall apply: TA id: TL_EUMS/TSL/TSPTRNAME/1 Normative source: ETSI TS 119 612 [1], clause 5.4.2. Target: European Union Member State Trusted List. Prerequisite: The TSP is a legal person. Predicate: The value of one of the tsl:Name children elements follows the pattern XXXCC-[ID] where XXX are either "VAT" or "NTR", CC are two characters corresponding to the country code (exceptions for these values as in test assertions TL_EUMS/CC/1 and TL_EUMS/CC/2 in clause 5.1.5.3 apply), and [ID] is an identifier according to the country and identity type reference. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/TSPTRNAME/2 Normative source: ETSI TS 119 612 [1], clause 5.4.2. Target: European Union Member State Trusted List. Prerequisite: The TSP is a natural person. Predicate: The value of one of the tsl:Name children elements follows the pattern XXXCC-[ID] where XXX are either "PAS" or "IDC", or "PNO", or "TIN", YY are two characters corresponding to the country code (exceptions for these values as in test assertions TL_EUMS/CC/1 and TL_EUMS/CC/2 in clause 5.1.5.3 apply), and [ID] is an identifier according to the country and identity type reference. Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 21 |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.3.3 Testing tsl:TSPAddress element | For testing the tsl:TSPAddress element the test assertions defined in clause 5.1.6 and the following test assertions shall apply. TA id: TL_EUMS/TSL/TSPADDR/1 Normative source: ETSI TS 119 612 [1], clause 5.4.3. Target: European Union Member State Trusted List. Prerequisite: The entire set of services provided by the TSP are terminated or ceased. Predicate: The value of this element is the address that the Scheme Operator uses for enquiries about the terminated services. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.3.4 Testing tsl:TSPInformationURI element | For testing the tsl:TSPInformationURI element the test assertions defined in clause 5.1.4.4 and the following test assertions shall apply: TA id: TL_EUMS/TSL/TSPURIINFO/1 Normative source: ETSI TS 119 612 [1], clause 5.4.4. Target: European Union Member State Trusted List. Prerequisite: The entire set of services provided by the TSP are terminated or ceased. Predicate: The value of this element is the URI that the Scheme Operator uses for providing information about the terminated services. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.3.5 Testing tsl:TSPInformationExtensions element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.3.5.1 Test assertions for EUMS Trusted Lists | TA id: TL_EUMS/TSL/TSPEXT/1 Normative source: ETSI TS 119 612 [1], clause 5.4.5. Target: European Union Member State Trusted List. Prerequisite: The Trusted List is generated by a Scheme Operator from an EU Member State. Predicate: The Critical attribute of each tsl:TSPInformationExtensions/Extension is set to value "false". Prescription level: mandatory Tag: EUMS Trusted List. It is out of the scope of the present document to define additional test assertions for testing contents of tsl:TSPInformationExtensions/Extension elements. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4 Testing ServiceInformation element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.1 Testing tsl:ServiceTypeIdentifier element | For testing the tsl:ServiceTypeIdentifier element the test assertions defined in clause 5.1.4.1 and the following test assertions shall apply: TA id: TL_EUMS/TSL/SVCTYPE/1 Normative source: ETSI TS 119 612 [1], clause 5.5.1. Target: European Union Member State Trusted List. Predicate: The value of this element is one of the following values: "http://uri.etsi.org/TrstSvc/Svctype/CA/QC" "http://uri.etsi.org/TrstSvc/Svctype/Certstatus/OCSP/QC" "http://uri.etsi.org/TrstSvc/Svctype/Certstatus/CRL/QC" "http://uri.etsi.org/TrstSvc/Svctype/TSA/QTST" "http://uri.etsi.org/TrstSvc/Svctype/EDS/Q" "http://uri.etsi.org/TrstSvc/Svctype/EDS/REM/Q" "http://uri.etsi.org/TrstSvc/Svctype/PSES/Q" "http://uri.etsi.org/TrstSvc/Svctype/QESValidation/Q" "http://uri.etsi.org/TrstSvc/Svctype/RemoteQSCDManagement/Q" Prescription level: permitted Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 22 TA id: TL_EUMS/TSL/SVCTYPE/2 Normative source: ETSI TS 119 612 [1], clause 5.5.1. Target: European Union Member State Trusted List. Predicate: The value of this element is one of the following values: "http://uri.etsi.org/TrstSvc/Svctype/CA/PKC" "http://uri.etsi.org/TrstSvc/Svctype/Certstatus/OCSP" "http://uri.etsi.org/TrstSvc/Svctype/Certstatus/CRL" "http://uri.etsi.org/TrstSvc/Svctype/TSA" "http://uri.etsi.org/TrstSvc/Svctype/TSA/TSS-QC" "http://uri.etsi.org/TrstSvc/Svctype/TSA/TSS-AdESQCandQES" "http://uri.etsi.org/TrstSvc/Svctype/EDS" "http://uri.etsi.org/TrstSvc/Svctype/EDS/REM" "http://uri.etsi.org/TrstSvc/Svctype/PSES" "http://uri.etsi.org/TrstSvc/Svctype/AdESValidation" "http://uri.etsi.org/TrstSvc/Svctype/AdESGeneration" Prescription level: permitted Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCTYPE/3 Normative source: ETSI TS 119 612 [1], clause 5.5.1. Target: European Union Member State Trusted List. Predicate: The value of this element is one of the following values: http://uri.etsi.org/TrstSvc/Svctype/RA http://uri.etsi.org/TrstSvc/Svctype/RA/nothavingPKIid http://uri.etsi.org/TrstSvc/Svctype/ACA http://uri.etsi.org/TrstSvc/Svctype/SignaturePolicyAuthority http://uri.etsi.org/TrstSvc/Svctype/Archiv http://uri.etsi.org/TrstSvc/Svctype/Archiv/nothavingPKIid http://uri.etsi.org/TrstSvc/Svctype/IdV http://uri.etsi.org/TrstSvc/Svctype/IdV/nothavingPKIid http://uri.etsi.org/TrstSvc/Svctype/KEscrow http://uri.etsi.org/TrstSvc/Svctype/KEscrow/nothavingPKIid http://uri.etsi.org/TrstSvc/Svctype/PPwd http://uri.etsi.org/TrstSvc/Svctype/PPwd/nothavingPKIid http://uri.etsi.org/TrstSvc/Svctype/TLIssuer http://uri.etsi.org/TrstSvc/Svctype/NationalRootCA-QC http://uri.etsi.org/TrstSvc/Svctype/unspecified Prescription level: permitted Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.2 Testing tsl:ServiceName element | For testing the tsl:ServiceName element the test assertions defined in clause 5.1.2 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.3 Testing tsl:ServiceDigitalIdentity element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.3.1 Test assertions common to any tsl:ServiceDigitalIdentity element | TA id: TL_EUMS/TSL/SVCDIGID/COMM/1 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: No PKI technology is used. Predicate: There is only one tsl:DigitalId child element. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCDIGID/COMM/2 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: No PKI technology is used. Predicate: The content of the tsl:Digital child element is a tsl:Other child whose value is a valid URI Reference. Prescription level: mandatory Tag: EUMS Trusted List. NOTE: It is out of the scope of the present document to define test assertions for other possible values of tsl:Other element. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 23 TA id: TL_EUMS/TSL/SVCDIGID/COMM/3 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used. Predicate: The tsl:ServiceDigitalIdentity element contains one and only one tsl:DigitalId/ds:KeyInfo/ds:KeyValue element as specified in XMLDSIG [3]. Prescription level: permitted Tag: EUMS Trusted List. 5.4.3.2 Test assertions specific to tsl:ServiceDigitalIdentity child element of tsl:ServiceInformation element TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/1 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used. Predicate: The tsl:ServiceDigitalIdentity element contains one or more tsl:DigitalId children elements, each one with one tsl:X509Certificate child element (one or more tsl:DigitalId/tsl:X509Certificate elements), whose value is the base-64 encoding of one X509 DER- encoded certificate. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/2 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND the tsl:ServiceDigitalIdentity element contains more than one tsl:DigitalId/tsl:X509Certificate elements. Predicate: All the X509 certificates within the tsl:DigitalId/tsl:X509Certificate elements certify the same public key. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/3 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND the tsl:ServiceDigitalIdentity element contains more than one tsl:DigitalId/tsl:X509Certificate elements. Predicate: All the X509 certificates within the tsl:DigitalId/tsl:X509Certificate elements have the same subject names. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/4 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND there are one or more than one X509 certificates whose subject name fields satisfy the condition that their Organization attributes strictly match the value of the tsl:TSPName of the provider of the service. Predicate: The tsl:ServiceDigitalIdentity contains one or more tsl:DigitalId/tsl:X059Certificate each one encapsulating one of the certificates mentioned in the prerequisite. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/5 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND there is not any X509 certificate whose subject name field satisfies the condition that its Organization attributes strictly match the value of the tsl:TSPName of the provider of the service. Predicate: The tsl:ServiceDigitalIdentity contains one or more tsl:DigitalId/tsl:X059Certificate each one encapsulating one certificate that does not satisfy the second condition of the predicate. Prescription level: permitted Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/6 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND there is not any X509 certificate whose subject name field satisfies the condition that its Organization attributes strictly match the value of the tsl:TSPName of the provider of the service. Predicate: The Organization attribute of each certificate encapsulated within tsl:DigitalId/tsl:X059Certificate elements is listed within the tsl:TSPTradeName element of the provider of the service. Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 24 TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/7 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used. Predicate: The tsl:ServiceDigitalIdentity element contains one and only one tsl:DigitalId/tsl:X509SubjectName element whose value is a string representation of an X509 certificate subject name as specified in XMLDSIG [3], clauses 4.5.4 and 4.5.4.1. Prescription level: preferred Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/8 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND the tsl:ServiceDigitalIdentity element contains one tsl:DigitalId/tsl:X509SubjectName element. Predicate: The value of tsl:X509SubjectName child element is the string representation of the subject name of all the X509 certificates present within the tsl:DigitalId/tsl:X509Certificate elements, computed as specified in XMLDSIG [3], clauses 4.5.4 and 4.5.4.1. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/9 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND the tsl:ServiceDigitalIdentity element contains one tsl:DigitalId/ds:KeyInfo/ds:KeyValue element. Predicate: The value of the tsl:DigitalId/ds:KeyInfo/ds:KeyValue element represents the public key certified by all the X509 certificates present within the tsl:DigitalId/tsl:X509Certificate elements. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/10 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used. Predicate: The tsl:ServiceDigitalIdentity element contains one and only one tsl:DigitalId/tsl:X509SKI child element whose value is a X.509 certificate subject identifier extension. Prescription level: permitted Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCINFO/SVCDIGID/11 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND the tsl:ServiceDigitalIdentity element contains one tsl:DigitalId/ds:KeyInfo/tsl:X509SKI element. Predicate: The value of the tsl:DigitalId/ds:KeyInfo/tsl:X509SKI element represents the public key certified by all the X509 certificates present within the tsl:DigitalId/tsl:X509Certificate elements. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCDIGID/12 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND two or more services have different values within their corresponding tsl:ServiceTypeIdentifier elements for which different supervision/accreditation systems apply. Predicate: The same public key identifies the two or more services mentioned in the prerequisite. Prescription level: permitted Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCDIGID/13 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND it is not true that there are two or more services that have different values within their corresponding tsl:ServiceTypeIdentifier elements for which different supervision/accreditation systems apply. Predicate: The same public key appears within the tsl:ServiceInformation/tsl:ServiceDigitalIdentity elements corresponding to the two or more services mentioned in the prerequisite. Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 25 TA id: TL_EUMS/TSL/SVCDIGID/14 Normative source: ETSI TS 119 612 [1], clause 5.5.3. Target: European Union Member State Trusted List. Prerequisite: PKI technology is used AND it is not true that there are two or more services that have different values within their corresponding tsl:ServiceTypeIdentifier elements for which different supervision/accreditation systems apply. Predicate: The same public key appears within one and only tsl:ServiceInformation/tsl:ServiceDigitalIdentity element within the Trusted List. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.4 Testing tsl:ServiceStatus element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.4.1 Introduction | For testing the tsl:ServiceStatus element the test assertions defined in clauses 5.1.4.1, 5.4.4.2 and 5.4.4.3 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.4.2 Test assertions common to any tsl:ServiceStatus element | This clause defines test assertions that, apart from the ones defined in clause 5.1.4.1, are common to any tsl:ServiceStatus element present within the Trusted List. TA id: TL_EUMS/TSL/SVCSTAT/1 Normative source: ETSI TS 119 612 [1], clause 5.5.4. Target: European Union Member State Trusted List. Prerequisite: The value of the tsl:ServiceType element is one of the values permitted in test assertion TL_EUMS/TSL/SVCTYPE/1 Predicate: The value of this element is either "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted" or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn" Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCSTAT/2 Normative source: ETSI TS 119 612 [1], clause 5.5.4. Target: European Union Member State Trusted List. Prerequisite: The value of the tsl:ServiceType element is one of the values permitted in test assertions TL_EUMS/TSL/SVCTYPE/2 and TL_EUMS/TSL/SVCTYPE/3 Predicate: The value of this element is either "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/recognisedatnationallevel" or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/deprecatedatnationallevel" Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.4.3 Test assertions specific to tsl:ServiceStatus child element of tsl:TSPService | This clause defines test assertions that are specific only to tsl:ServiceStatus elements that are children of tsl:TSPService elements. TA id: TL_EUMS/TSL/SVCSTAT/3 Normative source: ETSI TS 119 612 [1], clause 5.5.4. Target: European Union Member State Trusted List. Prerequisite: There exists the non empty tsl:ServiceHistory element. Predicate: The transition from the value of the tsl:ServiceStatus child element of the first tsl:ServiceHistoryInstance child element of tsl:ServiceHistory element, is one of the permitted in ETSI TS 119 612 1 clause 5.5.1 Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.5 Testing tsl:StatusStartingTime element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.5.1 Test assertions common to any tsl:StatusStartingTime element | TA id: TL_EUMS/TSL/SVCSTARTTIME/1 Normative source: ETSI TS 119 612 [1], clause 5.5.5. Target: European Union Member State Trusted List. Predicate: This element contains a Coordinated Universal Time (UTC) value. Prescription level: mandatory ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 26 Tag: EUMS Trusted List. 5.4.5.2 Test assertions specific tsl:StatusStartingTime child element of tsl:TSPService TA id: TL_EUMS/TSL/SVCSTARTTIME/2 Normative source: ETSI TS 119 612 [1], clause 5.5.5. Target: European Union Member State Trusted List. Prerequisite: There exists the non empty tsl:ServiceHistory element. Predicate: The value of this element is posterior than the value of the tsl:StatusStartingTime child element of the first tsl:ServiceHistoryInstance child of tsl:ServiceHistory element. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.6 Testing tsl:SchemeServiceDefinitionURI element | For testing the tsl:SchemeServiceDefinitionURI element the test assertions defined in clause 5.1.4.4 shall apply. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.7 Testing tsl:ServiceSupplyPoints element | For each tsl:ServiceSupplyPoint child element of tsl:ServiceSupplyPoints element, the test assertions defined in clause 5.1.4.1 and the following test assertions shall apply: TA id: TL_EUMS/TSL/SVCSUPPT/1 Normative source: ETSI TS 119 612 [1], clause 5.5.7. Target: European Union Member State Trusted List. Predicate: The value of the attribute type is one of the values specified in test assertions TL_EUMS/TSL/SVCTYPE/1, TL_EUMS/TSL/SVCTYPE/2, and TL_EUMS/TSL/SVCTYPE/3. Prescription level: mandatory Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.8 Testing tsl:TSPServiceDefinitionURI element | For testing the tsl:TSPServiceDefinitionURI element the test assertions defined in clause 5.1.4.4 and the following test assertions shall apply: TA id: TL_EUMS/TSL/SVCDEFURI/1 Normative source: ETSI TS 119 612 [1], clause 5.5.8. Target: European Union Member State Trusted List. Prerequisite: The value of tsl:ServiceType element is http://uri.etsi.org/TrstSvc/Svctype/NationalRootCA-QC. Predicate: This element is present. Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SVCDEFURI/2 Normative source: ETSI TS 119 612 [1], clause 5.5.8. Target: European Union Member State Trusted List. Prerequisite: The value of tsl:ServiceType element is not http://uri.etsi.org/TrstSvc/Svctype/NationalRootCA-QC. Predicate: This element is present. Prescription level: permitted Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.9 Testing tsl:ServiceInformationExtensions element | |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.9.1 Testing tsl:ExpiredCertsRevocationInfo element | For testing the tsl:ExpiredCertsRevocationInfo element the following test assertions shall apply: TA id: TL_EUMS/TSL/SIE/EXPCERTSREVINFO/1 Normative source: ETSI TS 119 612 [1], clause 5.5.9.1. Target: European Union Member State Trusted List. Prerequisite: The value of the tsl:ServiceType qualified by this extension is one of the following: "http://uri.etsi.org/TrstSvc/Svctype/CA/PKC" "http://uri.etsi.org/TrstSvc/Svctype/CA/QC" "http://uri.etsi.org/TrstSvc/Svctype/NationalRootCA-QC" ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 27 "http://uri.etsi.org/TrstSvc/Svctype/Certstatus/OCSP" "http://uri.etsi.org/TrstSvc/Svctype/Certstatus/OCSP/QC" "http://uri.etsi.org/TrstSvc/Svctype/Certstatus/CRL" "http://uri.etsi.org/TrstSvc/Svctype/Certstatus/CRL/QC" Predicate: The tsl:ExpiredCertsRevocationInfo extension is present. Prescription level: permitted Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SIE/EXPCERTSREVINFO/2 Normative source: ETSI TS 119 612 [1], clause 5.5.9.1. Target: European Union Member State Trusted List. Prerequisite: The value of the tsl:ServiceType qualified by this extension is one defined under an scheme (different than the one defined within ETSI TS 119 612 [1]) created by an organization, identifying a suitable service Predicate: The tsl:ExpiredCertsRevocationInfo extension is present. Prescription level: permitted Tag: EUMS Trusted List. NOTE: It is out of the scope of the present document identifying values for tsl:ServiceType elements mentioned in the prerequisite of test assertion TL_EUMS/TSL/SIE/EXPCERTSREVINFO/2. TA id: TL_EUMS/TSL/SIE/EXPCERTSREVINFO/3 Normative source: ETSI TS 119 612 [1], clause 5.5.9.1. Target: European Union Member State Trusted List. Predicate: Its Critical attribute is set to "false". Prescription level: permitted Tag: EUMS Trusted List. |
f61ada9ae38a781d63da39fc9ea616a8 | 119 614-1 | 5.4.9.2 Testing sie:Qualifications element | TA id: TL_EUMS/TSL/SIE/QUALS/1 Normative source: ETSI TS 119 612 [1], clause 5.5.9.2. Target: European Union Member State Trusted List. Prerequisite: The sie:Qualifications element is an extension of a service whose type is "CA/QC" Predicate: The value of each sie:Qualifications/Qualifiers/Qualifier is one of the following: "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithSSCD" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoSSCD" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCSSCDStatusAsInCert" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithQSCD" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoQSCD" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCQSCDStatusAsInCert" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCQSCDManagedOnBehalf" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForLegalPerson" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement" Prescription level: permitted Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SIE/QUALS/2 Normative source: ETSI TS 119 612 [1], clause 5.5.9.2.3. Target: European Union Member State Trusted List. Prerequisite: The sie:Qualifications element IS NOT an extension of a service whose type is "CA/QC" Predicate: The value of each sie:Qualifications/Qualifiers/Qualifier is none of the following: "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithSSCD" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoSSCD" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCSSCDStatusAsInCert" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithQSCD" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoQSCD" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCQSCDStatusAsInCert" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCQSCDManagedOnBehalf" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForLegalPerson" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified" "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement" Prescription level: mandatory Tag: EUMS Trusted List. ETSI ETSI TS 119 614-1 V1.1.1 (2016-06) 28 For testing any sie:Qualifications/sie:CriteriaList/sie:PolicySet/sie:PolicyIdentifier element, the test assertions defined in clause A.4 of the present document and the following test assertions shall apply. TA id: TL_EUMS/TSL/SIE/POLSet/1 Normative source: [2] - clause 7.1.2. Target: European Union Member State Trusted List. Prerequisite: The policy is identified with an OID Predicate: The value of the attribute Qualifier of the xades:Identifier child element of sie:PolicyIdentifier is "OIDAsURN". Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SIE/POLSet/2 Normative source: [2] – clause 7.1.2. Target: European Union Member State Trusted List. Prerequisite: The value of the attribute Qualifier of the xades:Identifier child element of sie:PolicyIdentifier is "OIDAsURN" Predicate: The value of the xades:Identifier child element of the sie:PolicyIdentifier element is an OID encoded within an URN as specified in IETF RFC 3061 [5]. Prescription level: mandatory Tag: EUMS Trusted List. For testing any sie:Qualifications/sie:CriteriaList/sie:otherCriteriaList/tslx:CertSubjectDNAttr ibute/tslx:AttributeOID element, the test assertions defined in clause A.4 of the present document and the following test assertions shall apply. TA id: TL_EUMS/TSL/SIE/CERTSUBDN/1 Normative source: [2] – clause 7.1.2. Target: European Union Member State Trusted List. Prerequisite: The policy is identified with an OID Predicate: The value of the attribute Qualifier of the xades:Identifier child element of tslx:AttributeOID is "OIDAsURN". Prescription level: mandatory Tag: EUMS Trusted List. TA id: TL_EUMS/TSL/SIE/CERTSUBDN/2 Normative source: [2] – clause 7.1.2. Target: European Union Member State Trusted List. Prerequisite: The value of the attribute Qualifier of the xades:Identifier child element of tslx:AttributeOID is "OIDAsURN" Predicate: The value of the xades:Identifier child element of the tslx:AttributeOID element is an OID encoded within an URN as specified in IETF RFC 3061 [5]. Prescription level: mandatory Tag: EUMS Trusted List. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.