hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b392cb6367becafeef785f2390da35ed | 119 461 | 8.5.1 Result of the identity proofing | ISS-8.5.1-01: The result of the identity proofing shall be delivered securely to the trust service provider, regarding the authenticity, integrity, and confidentiality of the result. EXAMPLE 1: The result can be digitally signed and encrypted at the message level or be transmitted over a properly secured communication ... |
b392cb6367becafeef785f2390da35ed | 119 461 | 8.5.2 Evidence of the identity proofing process | NOTE 1: In this clause 8.5.2, the term "evidence" means audit information for the identity proofing process as such, and not authoritative or supplementary evidence as in other clauses of the document. See also clause 7.10 of the present document. ISS-8.5.2-01: Evidence of the identity proofing process shall be gathere... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2 Use cases for identity proofing of natural person | 9.2.1 Use cases using an identity document with physical presence of the applicant |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.1.1 General requirements | [CONDITIONAL] If the identity proofing is based on the applicant's physical presence, the following requirements apply. NOTE 1: For the physical presence use cases, the same requirements apply for both Baseline and Extended LoIP. NOTE 2: The requirement for physical presence does not imply that the applicant has to be ... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.1.2 Use case for manual operation | [CONDITIONAL] If the identity proofing is based on the applicant's physical presence, and validation of evidence is manual using a physical identity document, and binding to applicant is by manual face verification, then the following requirements apply. NOTE: This is the most common use case for physical presence, whe... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.1.3 Use case for hybrid manual and automated operation | [CONDITIONAL] If the identity proofing is based on the applicant's physical presence, validation of evidence is automated using a digital identity document, and binding to applicant is by manual face verification, then the following requirements apply. NOTE 1: This use case resembles manual border control with a digita... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.1.4 Use case for automated operation | [CONDITIONAL] If the identity proofing is based on the physical presence of the applicant, validation of evidence is automated using digital identity document, and binding to applicant is by automated face biometrics, then the following requirements apply. NOTE 1: This use case requires equipment that can read and vali... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.2.1 General requirements | [CONDITIONAL] If the identity proofing is based on the remote presence of the applicant with online communication with a registration officer, the following requirements apply. NOTE 1: For the attended remote use cases, the requirements for Baseline LoIP and Extended LoIP differ in that manual validation of a physical ... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.2.2 Use case for manual operation (Baseline LoIP only) | [CONDITIONAL] If the identity proofing is based on the remote presence of the applicant with online communication with a registration officer, and validation of evidence is manual using a physical identity document, and binding to applicant is by manual face verification, then the following requirements apply. ETSI ETS... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.2.3 Use case for hybrid manual and automated operation | [CONDITIONAL] If the identity proofing is based on remote presence of the applicant with online communication with a registration officer, and validation of evidence is either automated using a digital identity document or combined automated and manual for a physical identity document, and binding to applicant is eithe... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.3.1 General requirements | [CONDITIONAL] If the identity proofing is based on the remote presence of the applicant with unattended online communication, the following requirements apply. NOTE 1: For the unattended remote use cases, manual operation, whether it is manual validation of a physical identity document or manual binding to applicant or... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.3.2 Use case for manual operation (Baseline LoIP only) | [CONDITIONAL] If the identity proofing is based on the remote presence of the applicant with unattended online communication, and validation of evidence is manual using a physical identity document, and binding to applicant is by manual face verification, then the following requirements apply. NOTE 1: The hybrid use ca... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.3.3 Use case for hybrid manual and automated operation | [CONDITIONAL] If the identity proofing is based on the remote presence of the applicant with unattended online communication, and validation of evidence is either automated using a digital identity document or combined automated and manual for physical identity document, and binding to applicant is either by manual fac... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.3.4 Use case for automated operation | [CONDITIONAL] If the identity proofing is based on the remote presence of the applicant with automated online communication, and validation of evidence is automated using a digital identity document, and binding to applicant is by automated face biometrics, then the following requirements apply. NOTE: A fully automated... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.4 Use case for identity proofing by authentication using eID means | [CONDITIONAL] If the identity proofing is based on authentication using eID means, the following requirements apply. USE-9.2.4-01: Attribute collection shall be according to the requirements of clause 8.2.2.1 of the present document. USE-9.2.4-02: Collection of evidence shall be according to the requirements in clause ... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.2.5 Use case for identity proofing using digital signature with certificate | [CONDITIONAL] If the identity proofing is based on the use of a digital signature with a certificate, the following requirements apply. USE-9.2.5-01: Attribute collection shall be according to the requirements of clause 8.2.2.1 of the present document. USE-9.2.5-02: Collection of evidence shall be according to the requ... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.3 Use case for identity proofing of legal person | [CONDITIONAL] If identity proofing is of a legal person, the following requirements apply. NOTE 1: The same requirements apply for both Baseline and Extended LoIP. NOTE 2: The present clause does not assume the involvement of an authorized natural person representing the legal person, but in reality some human involvem... |
b392cb6367becafeef785f2390da35ed | 119 461 | 9.5.1 General requirements | [CONDITIONAL] If the applicant is a natural person, including a natural person representing a legal person, and the identity of the applicant has been proven to Baseline LoIP by means of authentication using an eID, and an enhancement to Extended LoIP is required, the following requirements apply. NOTE 1: Enhancing ide... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 1 Scope | The present document specifies the semantics of a protocol for requesting to a remote server (and for receiving the corresponding response) the validation of AdES digital signatures compliant with the following ETSI deliverables: ETSI EN 319 122 [2], ETSI EN 319 132 [3], ETSI EN 319 142 [4], ETSI TS 101 733 [5], ETSI T... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 2 References | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 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... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 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... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.6], ETSI TS 119 441 [i.5] and the following apply: attachment reference container: sub-component of input documents container for transferring a reference to an underlying protocol attachment where either the signed document or the transfor... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 3.2 Symbols | Void. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CMS Cryptographic Message Syntax DSS-X Digital Signature Services eXtended DSSX, DSS-X Digital Signature Services eXtended ERS Evidence Record Syntax IETF Internet Engineering Task Force ISO International Organization for Standardization JSON ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 3.4 Terminology | The term "digest of the document", "document" being one of the documents signed by one signature submitted to a server within the request of any of the three protocols defined in the present document, is understood as indicated below: • If the document is signed by a CAdES signature, it is the digest of the signed docu... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 4.1 Main features | The main features supported by the 'validation' protocol specified in the present document, which are not supported by DSS-X core v2.0 [1] are: 1) Supports requesting the validation of one or more PAdES signatures embedded in one PDF document, if the client submits it to the server. It supports the validation of one PA... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 4.2 General requirements | The protocols specified in the present document re-use, wherever it is possible, the components specified in DSS-X core v2.0 [1]. Wherever the protocols defined in the present document require a certain component whose semantics and/or syntax is not offered by any of the components specified in DSS-X core v2.0 [1], the... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 4.3 XML protocol | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 4.3.1 Introduction | The new structures defined in the present document are contained in the XML schema file "19442xmlSchema.xsd". This file also contains the redefinition of certain structures defined in DSS-X core v2.0 [1], as shown in clause 4.3.2 of the present document. The new elements and types defined in that schema are defined wit... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 4.3.2 Redefined DSS-X types | The present document redefines three types already defined by DSS-X core v2.0 [1]. These redefinitions are contained in the XML schema file "19442xmlSchema.xsd" and are copied below for information, as well as in the clauses where these types are specified: <!—targetNamespace="http://uri.etsi.org/19442/v1.1.1#" --> <xs... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 4.4 JSON protocol | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 4.4.1 Introduction | The new structures defined in the present document are contained in the schema file "19442jsonSchema.json". This file also contains the extensions of certain structures defined in DSS-X core v2.0 [1]. These structures are listed in clause 4.4.2 of the present document. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 4.4.2 Extension of DSS-X types | The present document extends three types defined by DSS-X core v2.0 [1]. These extensions are contained in the JSON schema file "19442jsonSchema.json". The extension mechanism is implemented using the keyword "allOf" as specified in "JSON Schema Validation: A Vocabulary for Structural Validation of JSON" [15]. The type... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5 Protocol for validation of AdES signatures | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1 Request message | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.1 Component for requesting validation | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.1.1 Component semantics | The message for requesting the validation of an AdES signature to a remote server shall contain components for: 1) Submitting either the signature to be validated or a reference to the signature to be validated when this signature is enveloped within a signed document. Clause 5.1.2 specifies semantic requirements for t... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.1.2 XML component | The element that shall be the component for requesting the validation of AdES signature(s) shall be the element dss2:VerifyRequest as specified in clause 4.2.10.2 of DSS-X core v2.0 [1]. The dss2:VerifyRequest element shall be as specified in DSS-X core v2.0 [1]. The dss2:VerifyRequest element shall have one or more ds... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.1.3 JSON component | The element that shall implement the verify request message for the JSON binding of the protocol shall be the VerifyReq element. This element shall be an instance of the VerifyRequestType, defined as in JSON Schema file "19442jsonSchema.json", whose location is detailed in clause A.1, and is copied below for informatio... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.2 Component for submitting signature to be validated | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.2.1 Component semantics | The protocol shall allow including the signature in different containers according to the following rules: 1) If the signature is an embedded AdES signature, the embedding document and the signature shall be placed either: - within one sub-component of the input documents container; or - within an underlying protocol a... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.2.2 XML components | The element that shall be the component for submitting the signature(s) to be validated shall be either: a) the dss2:SignatureObject child element of the dss2:VerifyRequest root element if the signature is not embedded within the signed document(s); or b) the dss2:InputDocument child element of the dss2:VerifyRequest e... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.2.3 JSON component | The element that shall be the component for submitting the signature(s) to be validated shall be either: a) the sigObj child element of the VerifyReq root element if the signature is not embedded within the signed document(s); or b) the inDocs child element of the VerifyReq element if the signature(s) is embedded withi... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.3.1 Components semantics | The protocol shall allow including the signed document in several containers depending on its relative position regarding the signature that signs it: 1) If a non-embedded signature envelops the document, then the client shall place the enveloping signature and the enveloped signed document within the signature object ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.3.2 XML components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.3.2.1 General requirements | The dss2:SignatureObject element shall implement the signature object container for the XML binding of the protocol. The dss2:InputDocuments element shall implement the input documents container for the XML binding of the protocol. The requirements governing the presence, cardinalities, and contents of the XML componen... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.3.2.2 Additional requirements for contents of dss2:InputDocuments | 5.1.3.2.2.1 Element dss2:Document for sending original documents The dss2:Document element shall implement the document container for the XML binding of the protocol. NOTE: dss2:Base64Data child element of the dss2:Document can contain either the signed document in its dsb:Value child element, or a reference to an unde... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.3.3 JSON components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.3.3.1 General requirements | The sigObj element shall implement the signature object container for the JSON binding of the protocol. The inDocs element shall implement the input documents container for the JSON binding of the protocol. It shall be an instance of the InputDocumentsType, defined as in JSON Schema file "19442jsonSchema.json", whose l... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.3.3.2 Additional requirements for contents of inDocs | 5.1.3.3.2.1 Element doc for sending original documents Each item within the doc array shall implement a document container for the JSON binding of the protocol. NOTE: b64Data child element of one item within the doc array can contain either the signed document in its val child element, or a reference to an underlying p... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4 Optional components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.1 Container for optional components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.1.1 Component semantics | The validation request message may also contain optional components. These components may be used for requesting validation of any type of AdES signature. Below follows the list of the new components defined by the present document: 1) One component for identifying the signatures that the server is requested to validat... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.1.2 XML component | The dss2:OptionalInputs child element of dss2:VerifyRequest shall be an instance of dss2:OptionalInputsVerifyType redefined as in XML Schema file "19442xmlSchema.xsd", whose location is detailed in clause A.1. The redefinition of dss2:OptionalInputsVerifyType has been copied in clause 4.3.2 for information. The followi... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.1.3 JSON component | The optInp child element of VerifyReq shall be an instance of OptionalInputsVerifyType defined as in JSON Schema file "19442jsonSchema.json", whose location is detailed in clause A.2, and is copied below for information. "OptionalInputsVerifyType": { "type": "object", "allOf": [ {"$ref": "http://docs.oasis-open.org/dss... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.2 New components defined in the present document | 5.1.4.2.1 Component for identifying the signatures to be processed (signatures-to-process- refs container) 5.1.4.2.1.1 Introduction A validation request message may contain more than one signature; however, certain business processes may not require all of them to be processed. Consequently, requests messages need a me... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.2.2 Component for requesting validation against a certain signature policy | 5.1.4.2.2.1 Component semantics This component shall provide means for unambiguously identifying the signature validation policy against which the client requests to validate the digital signature(s). This component shall also allow the client to indicate locations where the signature validation policy can be downloade... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.2.3 Component for requesting a detailed validation report (signed or unsigned) | 5.1.4.2.3.1 Component semantics This component shall provide means for requesting to the server the generation and return of a detailed validation report for each validated signature. This component shall allow the client to identify that the validation report is conformant to a certain specification. The identifier fo... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.2.4 Component for passing proofs of existence of one or more signatures | 5.1.4.2.4.1 Component semantics This component shall have one or more tuples. Each tuple shall contain two components, namely: 1) One component whose value is a time instant value. This time instant shall be considered by the server as a proof of existence of the signature referenced in the other component of the tuple... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.3 Components re-used from DSS-X core v2.0 | 5.1.4.3.1 Component for identifying under which service policy the validation has to be conducted 5.1.4.3.1.1 Component semantics This component shall contain a non-ambiguous identifier of the service policy under which the client requests the server to validate the signature. 5.1.4.3.1.2 XML component The element that... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.3.2 Component for requesting notifications in a certain language | 5.1.4.3.2.1 Component semantics This component shall identify a language by a string-valued identifier, whose value shall be one of the identifiers built and registered as specified in IETF RFC 5646 [12]. 5.1.4.3.2.2 XML component The element that shall request the server to return notifications in a certain language s... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.3.3 Component for allowing the client to claim its identity | 5.1.4.3.3.1 Component semantics This component shall provide the identity of the client as a string-valued name. This component may include sub-components for supporting names federation. This component may include one sub-component for identifying the format of the string-valued name representing the identity of the c... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.3.4 Component for passing schemas | 5.1.4.3.4.1 Component semantics This component shall contain one or more documents, each one containing a schema. 5.1.4.3.4.2 XML component The element that shall request the server to return the identity of the signer shall be the dss2:Schemas element as specified in clause 4.3.10.2 of DSS-X core v2.0 [1]. 5.1.4.3.4.3... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.3.5 Component for requesting to set the validation time to a certain value | 5.1.4.3.5.1 Component semantics This component shall provide means for indicating to the server that the validation time is either the current time (the time when the server performs the signature validation) or a certain time in the past. 5.1.4.3.5.2 XML component The element that shall allow to set the validation tim... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.3.6 Component for requesting to return the validation time | 5.1.4.3.6.1 Component semantics This component shall provide means for requesting to the server to return within the response an indication of the validation time. 5.1.4.3.6.2 XML component The element that shall allow to request to the server to return the validation time, shall be the dss2:ReturnVerificationTimeInfo ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.3.7 Component for passing validation material to the server | 5.1.4.3.7.1 Component semantics This element shall convey any type of validation material that the client decides to pass to the server. It shall provide mechanisms for passing to the server X509 certificates, Attribute certificates, CRLs, OCSP responses, or other type of validation data. 5.1.4.3.7.2 XML component The ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.3.8 Component for requesting return of the signing time | 5.1.4.3.8.1 Component semantics This component shall provide means for requesting to the server to return within the response an indication of the signing time for each validated signature. 5.1.4.3.8.2 XML component The element that shall allow to request to the server to return an indication of the signing time shall ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.1.4.3.9 Component for requesting the server to return the identity of the signer | 5.1.4.3.9.1 Component semantics This element shall convey an indication to the server for returning the identity of the signer(s) for each validated signature. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 37 5.1.4.3.9.2 XML component The element that shall request the server to return the identity of the signer shall be the d... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2 Response message | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.1 Component for responding to a validation request | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.1.1 Component semantics | The validation response message resulting from one request of validation of AdES signature(s), shall contain one component for notifying the global validation result. The validation response message may contain one or more signature results containers. Clause 5.2.3.1 specifies this component and contains references to ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.1.2 XML component | The element that shall be the component for responding to the validation request of AdES signature(s) shall be the root element of the message dss2:VerifyResponse as specified in clause 4.2.11.2 of DSS-X core v2.0 [1], where the optOutp container of optional outputs may also include the additional components specified ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.1.3 JSON component | The element that shall implement the verify response message for the JSON binding of the protocol shall be the element VerifyResp element. This element shall be an instance of the VerifyResponseType, defined as in JSON Schema file "19442jsonSchema.json", whose location is detailed in clause A.1, and is copied below for... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.2 Component for the global validation result | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.2.1 Component semantics | This component shall contain a major result, which shall report whether the server has been able to perform its task, regardless the results obtained. This component may also contain a minor result providing additional information on the task performed by the server. For details of the values of its result major and re... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.2.2 XML component | The element that within the response shall notify the validation result shall be the dsb:Result element specified in clause 4.1.7.2 of DSS-X core v2.0 [1]. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.2.3 JSON component | The element that within the response shall notify the validation result shall be an instance of the dsb-ResultType type specified in clause 4.1.7.2 of DSS-X core v2.0 [1]. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3 Optional components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.1 Container for optional components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.1.1 Component semantics | The validation response message may also include one or more signature results containers. Each signature result container shall include one or more optional outputs resulting from the validation of the corresponding signature. Below follows the list of the new components defined by the present document: 1) The process... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.1.2 XML component | The dss2:OptionalOutputs child element of dss2:VerifyResponse shall be an instance of dss2:OptionalOutputsVerifyType defined as in XML Schema file "19442xmlSchema.xsd", whose location is detailed in clause A.1. The redefinition of dss2:OptionalOutputsVerifyType has been copied in clause 4.3.2 for information. The follo... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.1.3 JSON component | The optOutp child element of VerifyReq shall be an instance of OptionalOutputsVerifyType defined as in JSON Schema file "19442jsonSchema.json", whose location is detailed in clause A.2, and is copied below for information. "OptionalOutputsVerifyType": { "type":"object", "allOf": [ {"$ref": "http://docs.oasis-open.org/d... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.2 New components defined in the present document | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.2.1 Signature processing results container | 5.2.3.2.1.1 Component semantics This component shall have one child summarizing the result of the validation of one signature. Its contents shall be as specified in clause 8.4.3.1 of the present document. This component shall have one child for referencing the signature whose validation details it includes. This compon... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.2.2 Component for referencing the validated signature | 5.2.3.2.2.1 Component semantics This component shall be able to identify one of the signatures present in the request message, and consequently shall contain one reference to one signature. 5.2.3.2.2.2 XML component The SignatureReference component shall be an instance of etsivr:SignatureReferenceType defined in XML Sc... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.2.3 Component for notifying the signature policy applied during the validation | 5.2.3.2.3.1 Component semantics This component shall provide means for returning to the client the identifier of the signature validation policy applied by the server for validating the signature(s). This component shall appear in the response to requests of validation of digital signatures that incorporate the compone... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.2.5 Component for returning the detailed validation report (signed or unsigned) | 5.2.3.2.5.1 Component semantics This component shall contain either the signed or the unsigned detailed validation report for one or more digital signatures that the server has validated in response to one request that requested its generation (incorporating the component specified in clause 5.1.4.2.3 of the present do... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.3 Components re-used from DSS-X core v2.0 | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.3.1 Component for indicating the applied service policy | 5.2.3.3.1.1 Component semantics This component shall contain a non-ambiguous identifier of the service policy under which the client requests the server to validate the signature. 5.2.3.3.1.2 XML component The element that shall identify under which service policy the validation has to be conducted shall be the dsb:App... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.3.2 Component for indicating validation time | 5.2.3.3.2.1 Component semantics This component shall provide means for indicating to the client the validation time set by the server, which may be the current time or a certain time in the past. This component shall appear in the response to requests of validation of signatures that incorporate the component requestin... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.3.3 Component for returning the signing time of one signature | 5.2.3.3.3.1 Component semantics This component shall provide means for indicating to the client information on the signing time. This component shall appear in the response to requests of validation of signatures that incorporate the component requesting the server to return information of signing time, specified in cl... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.3.4 Component for returning signer's identity | 5.2.3.3.4.1 Component semantics This component of a response to a validation request shall return information on the signer's identity. This component shall appear in the response to requests that incorporate the component requesting the server to return these details, specified in clause 5.1.4.3.9.1 of the present doc... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 5.2.3.3.5 Component for returning the result of transforming the input document | 5.2.3.3.5.1 Component semantics This component shall appear only in the response to requests of validation of XAdES signatures that incorporate the component requesting the server to return one or more transformed input documents, specified in clause 5.1.4.3.10.1 of the present document. This component shall provide me... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6 Protocol for augmentation of AdES signatures | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1 Request message | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.1 Component for requesting augmentation of signatures | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.1.1 Component semantics | The signature augmentation request message shall allow requesting to the server the augmentation of one or more AdES signatures. The request message shall be able to submit the signatures to be augmented, following the same principles as in the validation request message, either: 1) within the signature object containe... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.1.2 XML component | The element that shall be the component for requesting the augmentation of AdES signature(s) shall be the root element of the message AugmentRequest as specified in the present clause. The AugmentRequest element shall be defined as in XML Schema file "19442xmlSchema.xsd", whose location is detailed in clause A.1, and i... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.1.3 JSON component | The element that shall be the component for requesting the validation of AdES signature(s) shall be the root element of the message AugmentRequest as specified in the present clause. The AugmentRequest element shall be defined as in JSON Schema file "19442jsonSchema.json, whose location is detailed in clause A.2, and i... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.