hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2 Additional inputs | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.1 Container for additional inputs | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.1.1 Semantics | This container shall include: 1) One component for indicating the level that the submitted signature(s) has(have) to be augmented to. Clause 6.1.2.2 defines requirements for this component. In addition, this container may also include: 1) One component for identifying the signatures that the server is requested to augm... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.1.2 XML component | The AdditionalInputs element shall be the container for additional inputs submitted to the server. It shall be an instance of dss2:OptionalInputsVerifyType type, suitably redefined in clause 5.1.4.1.2 of the present document. This element shall not contain the following children: • dsb:Other. • dss2:AddTimeStamp. • dss... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.1.3 JSON component | In the JSON protocol the additional components appear as direct children of the root node of the message as shown in clause 6.1.1.3 of the present document. 6.1.2.2 Component for identifying the level the signatures are requested to be augmented to |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.2.1 Component semantics | This component shall have as value a URI reference identifying the pre-defined level to which the server is requested to augment the signature. The value of this component shall take one of the values in Table 5 and Table 6 except the URIs identifying levels AdES-B-B, AdES-E-BES, AdES-E-EPES, AdES-B, AdES-BES, and AdES... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.2.2 XML component | The element that shall request the augmenting of the signature shall be the ReturnAugmentedSignature element. The ReturnAugmentedSignature element shall be defined as in XML Schema file "19442xmlSchema.xsd", whose location is detailed in clause A.1, and is copied below for information. <!—targetNamespace="http://uri.et... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.2.3 JSON component | The element that shall request the augmenting of the signature after its validation shall be the returnAugmentedSig component. This component shall have the value indicating the level to which the server is requested to augment the signatures. This component shall take one of the values in Table 5 and Table 6 except th... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.3.1 Component semantics | This component shall allow to identify the quality level that time-stamp tokens participating in the augmentation of the signature shall have. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.3.2 XML component | The element that shall request the quality level of the time-stamp tokens used for augmenting the signature shall be the TSTokensQualityLevel element. The TSTokensQualityLevel element shall be defined as in XML Schema file "19442xmlSchema.xsd", whose location is detailed in clause A.1, and is copied in clause 4.3.2 of ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.1.2.3.3 JSON component | The element that shall request the quality level of the time-stamp tokens used for augmenting the signature shall be the tstksQualityLevel element. The tstkQualityLevel element shall be defined as in JSON Schema file "19442jsonSchema.json", whose location is detailed in clause A.2, and is copied in clause 6.1.1.3 of th... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2 Response message | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.1 Component for responding to augmentation request | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.1.1 Component semantics | The signature augmentation response message shall allow the server to return to the client one or more AdES signatures, which shall be the result of augmenting the AdES signatures submitted by the client to the requested level. The signature augmentation response message shall have one or more signature result containe... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.1.2 XML component | The element that shall be the component for responding to a request of augmentation of AdES signature(s) shall be the root element of the message AugmentResponse as specified in the present clause. The AugmentResponse element shall be defined as in XML Schema file "19442xmlSchema.xsd", whose location is detailed in cla... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.1.3 JSON 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 AugmentResponse as specified in the present clause. The AugmentResponse element shall be an instance of AugmentResponseType, defined as in JSON Schema file "19442jsonSchema.json... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.2 Component for the global augmentation result | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.2.1 Component semantics | This component shall contain a major result, which shall report whether the protocol has been successfully executed, regardless all, or only some, or none of the signatures whose augmentation was requested, have actually been augmented or not. For details of the values of its result major and result minor, see clause 8... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.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 | 6.2.2.3 JSON component | The element that shall notify the global result shall be the result component of type dsb-ResultType specified in clause 4.1.7.1 of DSS-X core v2.0 [1]. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.3 Augment signature result container | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.3.1 Component semantics | This component shall include an element referencing the signature within the AugmentRequest message whose augmentation process details it reports. This component shall include an element for notifying the result of the augmentation process of the aforementioned referenced signature. Its contents shall be as specified i... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.3.2 XML component | The component for reporting on the augmentation of one AdES signature shall be an the element AugmentSignatureResult as specified in the present clause. The AugmentSignatureResult element shall be defined as in XML Schema file "19442xmlSchema.xsd", whose location is detailed in clause A.1, and is copied below for infor... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 6.2.3.3 JSON component | The component for reporting on the augmentation of one AdES signature shall be each of the items of augmentSigsResults array. Each item shall be an instance of AugmentSigResultType type. The AugmentSigResultType type shall be defined as in JSON Schema file "19442jsonSchema.json", whose location is detailed in clause A.... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1 Request message | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.1 Component for requesting validation and augmentation | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.1.1 Component semantics | The requirements for this component shall be the requirements specified in clause 5.1.1.1 except for the following difference: • This component shall have a component identifying one or more protocols and/or profiles that the response message is compliant with. The first one of such components shall have the following ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.1.2 XML component | The element that shall be the component for requesting the validation and augmentation of AdES signature(s) shall be the root element of the message dss2:VerifyRequest as specified in clause 5.1.1.2 with the following difference: 1) the dss2:VerifyRequest element shall have one or more dsb:Profile children elements. Th... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.1.3 JSON component | The element that shall be the component for requesting the validation and augmentation of AdES signature(s) shall be the root element of the message VerifyReq as specified in clause 5.1.1.3 of the present document with the following difference: 1) the profile array shall have one or more items. The first one shall have... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.2 Components for submitting signatures and signed documents | The components for submitting signatures and signed documents shall be the same as the components used for submitting signatures and signed documents in the request messages of the validation protocol. Requirements in clause 5.1.2.1 apply for submitting the signatures to be validated and augmented. The XML elements use... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.3 Optional components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.3.1 Container for optional components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.3.1.1 Component semantics | The requirements in clause 5.1.4.1.1 apply to this component, except for the following difference: 1) This component shall include a component for requesting the augmentation of the signatures to a certain level. NOTE: Despite the fact that this component is mandatory for the validation and augmentation protocol, it ap... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.3.1.2 XML component | The container for the optional components shall be an instance of the OptionalInputsVerifyType type specified in clause 5.1.4.1.2. All the requirements of clause 5.1.4.1.2 shall apply in the validation and augmentation request message with the following differences: 1) The ReturnAugmentedSignature element shall be pres... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.1.3.1.3 JSON component | The container for the optional components shall be an instance of the OptionalInputsVerifyType type specified in clause 5.1.4.1.3. All the requirements of clause 5.1.4.1.3 shall apply in the validation and augmentation request message with the following differences: 1) The returnAugmentedSig element shall be present. 2... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2 Response message | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.1 Component for responding to validation and augmentation request | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.1.1 Component semantics | The requirements for this component shall be the requirements specified in clause 5.2.1.1, except by the following differences: 1) This component shall have a profile identifier that shall identify the message as compliant with the "validation and augmentation" protocol specified in the present document. ETSI ETSI TS 1... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.1.2 XML component | The element that shall be the component for responding to a request of validation and augmentation of AdES signature(s) shall be the root element of the message dss2:VerifyResponse as specified in clause 5.2.1.2 with the following difference: 1) the dss2:VerifyResponse element shall have one or more dsb:Profile childre... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.1.3 JSON component | The element that shall be the component for responding to a request of validation and augmentation of AdES signature(s) shall be an instance of VerifyResp as specified in clause 5.2.1.3 of the present document with the following difference: 1) the profile array shall have one or more items. The first one shall have the... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.2 Component for the global validation and augmentation result | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.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 | 7.2.2.2 XML component | The element that shall notify the global validation and augmentation result shall be the dsb:Result element specified in clause 4.1.7.2 of DSS-X core v2.0 [1]. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.2.3 JSON component | The element that shall notify the global validation and augmentation result shall be result of type dsb-ResultType type specified in clause 4.1.7.1 of DSS-X core v2.0 [1]. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.3 Optional components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.3.1 Container for optional components | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.3.1.1 Component semantics | The requirements in clause 5.2.3.1.1 apply to the component consisting in a sequence of signature results container. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.3.1.2 XML component | The element for incorporating the sequence of signature result containers shall be an instance of OptionalOutputsVerifyType type specified in clause 5.2.3.1.2. The requirements specified in clause 5.2.3.1.2 shall apply for this element. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 62 |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.3.1.3 JSON component | The element for incorporating the sequence of signature result containers shall be the oplOutp property, instance of OptionalOutputsVerifyType type as specified in clause 5.2.3.1.3. The requirements specified in clause 5.2.3.1.3 shall apply for this element. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.3.2 Signature processing results container | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.3.2.1 Component semantics | The requirements in clause 5.2.3.2.1 shall apply to this component with the following difference: 1) It shall include the augment signature result container. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.3.2.2 XML component | The element for implementing the signature results container shall be the ResultsForOneSignature element as specified in clause 5.2.3.2.1.2. The requirements specified in clause 5.2.3.2.1.2 shall apply for this element with the following differences: 1) This element shall include the AugmentSignatureResult element. 2) ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.3.2.3 JSON component | The element for implementing the signature results container shall be the resForOneSig property as specified in clause 5.2.3.2.1.3. The requirements specified in the aforementioned clause shall apply for this element with the following differences: 1) This element shall include the augmentSigResult child. 2) The augmen... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.4 Reporting results | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.4.1 Introduction | Being the validation and the attempt to augment one signature two different processes, their results shall be reported in two different result components in the response message, as indicated below. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.4.2 Reporting results in XML protocol | The result of the validation of a certain signature shall be reported in the dsb:Result child element of the ResultsForOneSignature element reporting the processing results for that signature. The contents of this element shall be as specified in clause 8.4.3.1 of the present document. The result of the attempt to augm... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 7.2.4.3 Reporting results in JSON protocol | The result of the validation of a certain signature shall be reported in the result child element of the resForOneSig element reporting the processing results for that signature. The contents of this element shall be as specified in clause 8.4.3.1 of the present document. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 63 The re... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8 Processing models | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.1 Introduction | The present clause specifies the processing models for the three protocols defined in the present document. When the server receives a request from the client, it shall conduct the following tasks: 1) Retrieve the signature(s) that the client has requested to process. Clause 8.2 of the present document specifies models... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.2 Retrieving signature(s) | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.2.1 Retrieving XAdES signature(s) | The process for retrieving the XAdES signatures in the request messages shall be as follows: • If the request message does not include the optional input (specified in clause 5.1.4.2.1) for identifying the signatures to be processed, the server shall retrieve the XAdES signatures (built on XML signatures) as specified ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.2.2 Retrieving CAdES signature(s) | If the request message does not include the optional input (specified in clause 5.1.4.2.1) for identifying the signatures to be processed, the server shall retrieve the CMS structure as specified in step 1 of clause 6.2.1 of DSS-X core v2.0 [1]. The signerInfos set of this CMS structure may contain several items. Each ... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.2.3 Retrieving PAdES signature(s) | The process for retrieving the PAdES signatures in the request messages shall be as follows. If the request message does not include the optional input (specified in clause 5.1.4.2.1) for identifying the signatures to be processed then: • If the signature object container does enclose a pointer, the server shall retrie... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.2.4 Non retrieved signatures | In any of the three cases described in preceding clauses, for each signature reference that the server does not match with any signature in the request, the server shall generate one signature results container with only the result component, with its major result set to urn:oasis:names:tc:dss:1.0:resultmajor:Requester... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.3 Processing signature(s) | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.3.1 Validating signature(s) | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.3.1.1 Validating XAdES signature(s) | For each XAdES signature retrieved after conducting the task specified in clause 8.2.1 the server: 1) Shall conduct the sub-process 'recalculate references' as specified in clause 6.1.2 of DSS-X core v2.0 [1]. 2) Shall conduct its validation as specified in ETSI TS 119 102-1 [13]. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.3.1.2 Validating CAdES signature(s) | The server shall first retrieve either the signed document as specified in step 2 of clause 6.2.1 of DSS-X core v2.0 [1], or retrieves the document digest from the digest document container. For each CAdES signature retrieved after conducting the task specified in clause 8.2.2, the server shall conduct its validation a... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.3.1.3 Validating PAdES signature(s) | For each PAdES signature retrieved after conducting the task specified in clause 8.2.3, the server shall conduct its validation as specified in ETSI TS 119 102-1 [13]. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.3.2 Augmenting signature(s) | For each AdES signature retrieved after conducting the task specified in the sub-clause of clause 8.2 corresponding to the AdES signature type, the server shall proceed to augment it to the level indicated in the component (specified in clause 6.1.2.2 of the present document) identifying the level that the signatures h... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4 Building response message | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.1 Introduction | This task shall be affected by the optional inputs present in the request message. Clause 8.4.3 specifies how to build the new optional outputs originated by the new optional inputs specified in clauses 5.1.4.2 and 6.1.2 of the present document. Clause 8.4.5 specifies where the server shall place the different optional... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.2 Building the global result component | For the responses of any of the three protocols specified in the present document, if the server has not been able to process the request, it shall generate a result component with its result major set to a value indicating the cause of the failure, as specified in clause 4.1.7 of DSS-X core v2.0 [1]. Under these circu... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.3 Building new optional outputs | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.3.1 Building the signature processing results container | The server shall include one or more processing signature containers within the response message: • if the message is the response for a request of the 'augmentation' OR 'validation and augmentation' protocols; OR • if the messages is the response for a request of the 'validation protocol' AND: - The request message in... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.3.2 Building component for referencing the processed signature | The server shall generate this component (specified in clause 5.2.3.2.2 of the present document) if it also generates one or more instances of the component for including details corresponding to the processing of one signature. The server shall generate one component of this type for each processed signature, and shal... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.3.3 Building component for returning the (signed or unsigned) validation report | The server shall generate this component (specified in clause 5.2.3.2.5 of the present document) if the request included the optional input (specified in clause 5.1.4.2.3 of the present document) requesting the generation of a (signed or unsigned) validation report. If the server has been requested to validate a set of... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.3.5 Building component for returning the signature policies available | The server may include this component (specified in clause 5.2.3.2.4 of the present document) if the request included the optional input (specified in clause 5.1.4.2.2 of the present document) requesting that the server uses a certain signature validation policy for validating any signature AND the server could not val... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.3.6 Building the augment signature result container | The server shall build this component (specified in clause 6.2.3 of the present document) only for the response messages of the 'augmentation' and the 'validation and augmentation' protocols. The server shall build one component of this type for each signature whose augmentation has been requested by the client. The se... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.4 Building DSS-X re-used optional outputs | The building of the DSSX re-used optional outputs present in the response message shall be performed as specified in clause 6.3.3 of DSS-X core v2.0 [1]. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 70 |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 8.4.5 Building the response message | If the server has found itself in the situation of not being able to complete the request, it shall generate a response message with only one global result component. Its result major shall identify the reason that prevented the server to successfully process the request, as specified in clause 4.1.7 of DSS-X core v2.0... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9 Asynchronous processing | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.1 Asynchronous operation for the three protocols | For all the protocols specified in the present document, the server shall not send back to the client a response message that contains the results of processing only a subset of the set of signatures that the client requested to process. The asynchronous processing allows to the server sending back to the client "not y... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.2 Components for sending a pending-request | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.2.1 Components semantics | This component shall request to the server to return the response corresponding to an initial request previously sent. Requests of this type are named pending-request hereinafter. This component shall include an identifier, generated by the server and returned by the server in the response to the initial request (the f... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.2.2 XML component | The element that shall indicate to the server that the client is requesting the response corresponding to a previously sent initial request (as part of an asynchronous protocol) shall be the dss2:PendingRequest element specified in clause 4.2.12.2 of DSS-X core v2.0 [1]. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.2.3 JSON component | The element that shall indicate to the server that the client is requesting the response corresponding to a previously sent initial request (as part of an asynchronous protocol) shall be the pendingReq element. It shall be an instance of the dss2-PendingRequestType type specified in clause 4.2.12.1 of DSS-X core v2.0 [... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.3 Component for identifying the initial request | |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.3.1 Component semantics | This component shall contain a unique identifier for the initial request submitted by the client to the server. |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.3.2 XML component | The component implementing the identifier of the initial request shall be the RequestID attribute specified in clause 4.1.10.2 of DSS-X core v2.0 [1] for the "validation" protocol and the "validation and augmentation" protocol. The component implementing the identifier of the initial request shall be the RequestID attr... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.3.3 JSON component | The component implementing the identifier of the initial request shall be the reqID component specified in clause 4.1.10.1 of DSS-X core v2.0 [1] for the "validation" protocol and the "validation and augmentation" protocol. The component implementing the identifier of the initial request shall be the reqID component sp... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.4.1 Component semantics | This component shall contain a unique identifier for the initial response-pending message sent by the sender to the client. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 73 |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.4.2 XML components | The component implementing the identifier of the initial request shall be the ResponseID attribute specified in clause 4.1.11.2 of DSS-X core v2.0 [1] for the "validation" protocol and the "validation and augmentation" protocol. The component implementing the identifier of the initial request shall be the ResponseID at... |
01baa530c4a62e404e91e3569227c3a1 | 119 442 | 9.4.3 JSON component | The component implementing the identifier of the initial request shall be the respID component specified in clause 4.1.11.2 of DSS-X core v2.0 [1] for the "validation" protocol and the "validation and augmentation" protocol. The component implementing the identifier of the initial request shall be the respID component ... |
4028be74228292868d82461bedfe5a9b | 119 615 | 1 Scope | The present document specifies procedures for using and interpreting EUMS national trusted lists when validating EU qualified trust service outputs against them (e.g. validating EU qualified certificates, EU qualified time stamps, evidences created by qualified electronic registered delivery services, EU electronic sig... |
4028be74228292868d82461bedfe5a9b | 119 615 | 2 References | |
4028be74228292868d82461bedfe5a9b | 119 615 | 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... |
4028be74228292868d82461bedfe5a9b | 119 615 | 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... |
4028be74228292868d82461bedfe5a9b | 119 615 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.4] and the following apply: pivot LOTL: specific instance of a LOTL that announces changes in the LOTL signing certificates and/or LOTL location NOTE: For further explanations on the concept of pivot LOTL refer to annex A. tuple: group of m... |
4028be74228292868d82461bedfe5a9b | 119 615 | 3.2 Symbols | Void. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.