hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
094ea52cbab75af19142b66f618387fa | 121 111 | 5.5 Data integrity of signalling elements | ................................................................................................................ 10 |
094ea52cbab75af19142b66f618387fa | 121 111 | 5.6 User identity confidentiality | ............................................................................................................................. 10 |
094ea52cbab75af19142b66f618387fa | 121 111 | 5.7 Length of security parameters | .......................................................................................................................... 10 |
094ea52cbab75af19142b66f618387fa | 121 111 | 6 Logical issues | ......................................................................................................................................... 10 |
094ea52cbab75af19142b66f618387fa | 121 111 | 6.1 Application selection | ........................................................................................................................................ 10 |
094ea52cbab75af19142b66f618387fa | 121 111 | 6.2 Simultaneous access | ......................................................................................................................................... 10 |
094ea52cbab75af19142b66f618387fa | 121 111 | 7 Service Requirements | ............................................................................................................................. 10 |
094ea52cbab75af19142b66f618387fa | 121 111 | 7.1 Void | .................................................................................................................................................................. 10 |
094ea52cbab75af19142b66f618387fa | 121 111 | 7.2 Data transfer | ..................................................................................................................................................... 10 |
094ea52cbab75af19142b66f618387fa | 121 111 | 7.3 Application execution environment | ................................................................................................................. 11 |
094ea52cbab75af19142b66f618387fa | 121 111 | 7.4 Profile exchange | ............................................................................................................................................... 11 |
094ea52cbab75af19142b66f618387fa | 121 111 | 7.5 Version identification | ....................................................................................................................................... 11 |
094ea52cbab75af19142b66f618387fa | 121 111 | 8 Physical Characteristics | .......................................................................................................................... 11 |
094ea52cbab75af19142b66f618387fa | 121 111 | 8.1 Void | .................................................................................................................................................................. 11 |
094ea52cbab75af19142b66f618387fa | 121 111 | 8.2 Void | .................................................................................................................................................................. 11 |
094ea52cbab75af19142b66f618387fa | 121 111 | 9 Electrical characteristics and transmission protocols | ............................................................................. 11 |
094ea52cbab75af19142b66f618387fa | 121 111 | 9.1 Void | .................................................................................................................................................................. 12 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10 Contents of the Elementary Files | ........................................................................................................... 12 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.1 USIM information storage requirements | .......................................................................................................... 12 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.2 Phone Book | ...................................................................................................................................................... 13 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.2.1 Support of two name fields per entry | .......................................................................................................... 13 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.2.2 Support of multiple phone numbers per entry | ............................................................................................. 13 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.2.3 Support of email address | ............................................................................................................................. 13 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.2.4 Support of user definable groupings | ........................................................................................................... 13 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.2.5 Support of hidden entries | ............................................................................................................................ 13 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.2.6 Number of entries | ....................................................................................................................................... 13 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.2.7 Void | ............................................................................................................................................................ 13 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.3 Storage of call details | ....................................................................................................................................... 13 |
094ea52cbab75af19142b66f618387fa | 121 111 | 10.4 Void | .................................................................................................................................................................. 14 |
094ea52cbab75af19142b66f618387fa | 121 111 | 11 3G/GSM interworking | ............................................................................................................................ 14 |
094ea52cbab75af19142b66f618387fa | 121 111 | 11.1 Void | .................................................................................................................................................................. 14 ETSI ETSI TS 121 111 V18.0.0 (2024-05) 4 3GPP TS 21.111 version 18.0.0 Release 18 |
094ea52cbab75af19142b66f618387fa | 121 111 | 11.2 3G subscribers in a GSM network | .................................................................................................................... 14 |
094ea52cbab75af19142b66f618387fa | 121 111 | 12 Contact Manager | .................................................................................................................................... 14 Annex A (informative): Change history ............................................................................................... 17 History .......................................... |
4a787b7c525a610372b043194adf518c | 119 441 | 1 Scope | The present document, based on the general policy requirements specified in ETSI EN 319 401 [2], specifies policy and security requirements for signature validation services operated by a TSP. NOTE 1: Beside signature validation, other signature services, like signature creation, signature augmentation or signature pre... |
4a787b7c525a610372b043194adf518c | 119 441 | 2 References | |
4a787b7c525a610372b043194adf518c | 119 441 | 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 a... |
4a787b7c525a610372b043194adf518c | 119 441 | 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 i... |
4a787b7c525a610372b043194adf518c | 119 441 | 3 Definitions, abbreviations and notation | |
4a787b7c525a610372b043194adf518c | 119 441 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI EN 319 401 [2], in ETSI TR 119 001 [i.2] and the following apply: applicability checking: determination whether a signature conform to signature applicability rules NOTE 1: The applicability checking is a broader concept than validation a... |
4a787b7c525a610372b043194adf518c | 119 441 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI EN 319 401 [2], in ETSI TR 119 001 [i.2] and the following apply: DA Driving Application OVR OVeRall PoE Proof of Existence QES Qualified Electronic Signature or Qualified Electronic Seal (Q)SCD (Qualified) Signature Creation Device QSVSP Qualifi... |
4a787b7c525a610372b043194adf518c | 119 441 | 3.3 Notation | The requirements identified in the present document include: a) requirements applicable to any TSP conforming to the present document. Such requirements are indicated by clauses without any additional marking; b) requirements applicable under certain conditions. Such requirements are indicated by clauses marked by "[CO... |
4a787b7c525a610372b043194adf518c | 119 441 | 4 General concepts | |
4a787b7c525a610372b043194adf518c | 119 441 | 4.1 General policy requirements concepts | The present document is structured in line with ETSI EN 319 401 [2]. It incorporates ETSI EN 319 401 [2] requirements by reference and adds requirements relevant for a SVSP. See ETSI EN 319 401 [2], clause 4 for guidance on general policy requirements. ETSI ETSI TS 119 441 V1.1.1 (2018-08) 13 |
4a787b7c525a610372b043194adf518c | 119 441 | 4.2 Signature Validation Service applicable documentation | |
4a787b7c525a610372b043194adf518c | 119 441 | 4.2.1 Signature Validation Service Practice Statements | The SVSP develops, implements, enforces, and updates a SVS practice statements which is a trust service practice statement such as defined in ETSI EN 319 401 [2], instantiated for a signature validation service. See clause 6.1. The SVS practice statements describe how the SVSP operates its service and is owned by the S... |
4a787b7c525a610372b043194adf518c | 119 441 | 4.2.2 Signature Validation Service Policy | A SVS policy describes what is offered and can contain diverse information beyond the scope of the present document to indicate the applicability of the service. The recipients of the service policy can be the subscribers and the relying parties. The present document can be referred by such SVS policy to provide inform... |
4a787b7c525a610372b043194adf518c | 119 441 | 4.2.3 Terms and conditions | In addition to the SVS practice statements and, when issued by the SVSP, the signature validation service policy, the SVSP also issues terms and conditions, see clause 6.2. The terms and conditions are specific to a SVSP. The recipients of the terms and conditions can be the subscribers and the relying parties. NOTE: T... |
4a787b7c525a610372b043194adf518c | 119 441 | 4.2.4 Other documents associated with signature validation | The SVA works on the basis of a signature validation policy as input, i.e. a signature validation is always done against a signature validation policy. Such signature validation policy, which is the set of signature validation constraints processed or to be processed by the SVA, can be issued as a human readable docume... |
4a787b7c525a610372b043194adf518c | 119 441 | 4.3 Signature Validation Service components | |
4a787b7c525a610372b043194adf518c | 119 441 | 4.3.1 Signature Validation Service actors | The two main actors are the SVSP, which is a Trust Service Provider (TSP) and its subscriber. A SVSP can offer one or more signature validation services. Within a subscriber's umbrella, user(s) request signature validation. NOTE: A signature validation service can be combined with a signature augmentation service. The ... |
4a787b7c525a610372b043194adf518c | 119 441 | 4.3.2 Architecture | The validation services are broken down into the following components: • The signature validation client is a component or a piece of software that implements the signature validation protocol on the user's side. In particular it: - Requests a signature validation to the signature validation service server (SVSServ); N... |
4a787b7c525a610372b043194adf518c | 119 441 | 4.3.3 Process | Figure 1: Validation process The communication channel between the client and the SVSServ transports the signature validation request (1.) and the response (3.). It can be synchronous or asynchronous. It covers the authentication of the SVSP, to avoid false reports, and it can support client authentication. The communi... |
4a787b7c525a610372b043194adf518c | 119 441 | 5 Risk assessment | OVR-5-01 The requirements specified in ETSI EN 319 401 [2], clause 5 shall apply. |
4a787b7c525a610372b043194adf518c | 119 441 | 6 Policies and practices | |
4a787b7c525a610372b043194adf518c | 119 441 | 6.1 Signature Validation Service practice statement | OVR-6.1-01 The requirements specified in ETSI EN 319 401 [2], clause 6.1 shall apply. In addition the following particular requirements apply: OVR-6.1-02 The SVS practice statement should be structured as per annex A. OVR-6.1-03 The SVS practice statement should list or make reference to (e.g. through OIDs), and briefl... |
4a787b7c525a610372b043194adf518c | 119 441 | 6.2 Terms and Conditions | OVR-6.2-01 The requirements specified in ETSI EN 319 401 [2], clause 6.2 shall apply. NOTE 1: With regard to REQ-6.2-02 k) in ETSI EN 319 401 [2]; the SVSP can provide a notice that the SLA and also the signature validation status and the signature validation report can be affected by the practices, policies and SLAs o... |
4a787b7c525a610372b043194adf518c | 119 441 | 6.3 Information security policy | OVR-6.3-01 The requirements specified in ETSI EN 319 401 [2], clause 6.3 shall apply. In addition the following particular requirements apply: OVR-6.3-02 The security policy should document the security and privacy controls implemented to protect personal data. NOTE: If the SVSP has access to signed data this can conta... |
4a787b7c525a610372b043194adf518c | 119 441 | 7.1 Internal organization | OVR-7.1-01 The requirements specified in ETSI EN 319 401 [2], clause 7.1 shall apply. |
4a787b7c525a610372b043194adf518c | 119 441 | 7.2 Human resources | OVR-7.2-01 The requirements specified in ETSI EN 319 401 [2], clause 7.2 shall apply. |
4a787b7c525a610372b043194adf518c | 119 441 | 7.3 Asset management | OVR-7.3-01 The requirements specified in ETSI EN 319 401 [2], clause 7.3 shall apply. |
4a787b7c525a610372b043194adf518c | 119 441 | 7.4 Access control | OVR-7.4-01 The requirements specified in ETSI EN 319 401 [2], clause 7.4 shall apply. |
4a787b7c525a610372b043194adf518c | 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 [CONDITIONAL] When validation reports are signed the SVSP should select a signing certificate issued by a trustworthy CA that implements ETSI EN 319 411-1 [i.16] or ... |
4a787b7c525a610372b043194adf518c | 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. 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. |
4a787b7c525a610372b043194adf518c | 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 The following requirements specified in ETSI TS 119 101 [1], clause 5.2 should apply to the SVA: GSM 1.2. OVR-7.7-03 The following requirements specified in ETSI TS 1... |
4a787b7c525a610372b043194adf518c | 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 In case remote access to systems storing or processing confidential data is allowed, a formal policy should be adopted, and described as part of elements required by ... |
4a787b7c525a610372b043194adf518c | 119 441 | 7.9 Incident management | OVR-7.9-01 The requirements specified in ETSI EN 319 401 [2], clause 7.9 shall apply. ETSI ETSI TS 119 441 V1.1.1 (2018-08) 22 |
4a787b7c525a610372b043194adf518c | 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... |
4a787b7c525a610372b043194adf518c | 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 ... |
4a787b7c525a610372b043194adf518c | 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. ETSI ETSI TS 119 441 V1.1.1 (2018-08) 23 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 per... |
4a787b7c525a610372b043194adf518c | 119 441 | 8 Signature validation service technical requirements | 8.1 Signature validation process VPR-8.1-01 The validation process shall comply with ETSI TS 119 102-1 [3]. NOTE 1: This does not mean that the SVSP has to implement the algorithm specified in ETSI TS 119 102-1 [3], as it allows alternative implementations provided that they produce the same main status indication when... |
4a787b7c525a610372b043194adf518c | 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 especiall... |
4a787b7c525a610372b043194adf518c | 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 TS 119 102-1 [3]). SVR-8.4-02 The validation report should conform to ETSI TS 119 102-2 [i.3]. SVR-8.4-03 The signature validation report shall in... |
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 ele... |
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 a... |
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 i... |
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 Identif... |
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 ... |
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 o... |
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... |
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 Membe... |
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... |
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: Ins... |
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 Sc... |
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 ... |
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 Unio... |
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. Prescriptio... |
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: ... |
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... |
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 ap... |
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... |
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 con... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.