hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 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... |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 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... |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 3 Definition of terms, symbols and abbreviations | |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.3] and the following apply: Publicly-Trusted Certificate (PTC): certificate trusted by virtue of the fact that its corresponding Root Certificate is distributed as a trust anchor in widely-available application software NOTE 1: See ETSI EN ... |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 3.2 Symbols | Void. |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.3] and the following apply: AAL Audit Attestation Letter CA/B Forum Certification Authority and Browser Forum CAB Conformity Assessment Body CCADB Common CA DataBase NOTE: Run by Mozilla® (see https://www.ccadb.org). PTC Publicly-Tr... |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 4.1 General | PTA-4.1-01: The requirements defined in ETSI EN 319 403-1 [1] shall apply. The following clauses define additional requirements. ETSI ETSI TS 119 403-2 V1.3.1 (2023-03) 8 |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 4.2 Audit Frequency (see ETSI EN 319 403-1, clause 7.4.5) | PTA-4.2-01: A full-surveillance audit shall be conducted no less frequently than annually. PTA-4.2.02: Updated audit information shall be provided no less frequently than annually. PTA-4.2.03: Successive audits shall include an evaluation of evidence produced since the last audit. |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 4.3 Audit Attestation | PTA-4.3-01: The Audit Attestation for TSPs issuing publicly-trusted certificates shall provide sufficient details to demonstrate that the audited TSP fulfilled the requirements from ETSI EN 319 411-1 [i.9] and those from CA/Browser Forum, [i.7] and [i.8]. In particular: • PTA-4.3-02: The Audit Attestation shall be writ... |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 4.4 Audit Scope | PTA-4.4-01: The audit attestation shall list all TSP incidents documented in a public repository (e.g. Mozilla® Bugtracker) with an explanation of remediation status. NOTE: If the audit scope includes third party trust service components, such as a Registration Services as defined in ETSI EN 319 411-1 [i.9] the TSP rem... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 1 Scope | Based on a scoping study and survey with respect to long-term preservation techniques for digital signatures and general data documented in ETSI SR 019 510 [i.13], the present document and its companion document ETSI TS 119 511 [i.14] have been created. ETSI TS 119 511 [i.14] specifies policy and security requirements ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 2 References | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 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... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 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... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 3 Definition of terms, symbols and abbreviations | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.3] and the following apply: certificate status authority: authority providing certificate status information EXAMPLE: The certificate status information can be provided using the Online Certificate Status Protocol (OCSP) [i.22] or in form o... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 3.2 Symbols | Void. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.3] and the following apply: API Application Programming Interface ASN.1 Abstract Syntax Notation One AUG Augmentation BSI Bundesamt für Sicherheit in der Informationstechnik CRL Certificate Revocation List CSA Certificate Status Aut... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 4 General aspects | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 4.1 System architecture | The overall system architecture with the preservation service specified in the present document is depicted in Figure 1. Figure 1: System architecture with preservation service and related services As depicted in Figure 1, the preservation service defined in the present document provides the preservation interface as s... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 4.2 Preservation goals | A preservation service can pursue different preservation goals, which has an influence on the supported operational tasks. The present document specifies the following three goals which may be used separately or in combination: • http://uri.etsi.org/19512/goal/pgd The preservation goal "Preservation of General Data" (P... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 4.3 Storage models | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 4.3.1 Preservation with storage | In this preservation storage model, the preservation service stores the submission data objects (SubDO) as well as the preservation evidences that are produced for them by the preservation service. In this model, the preservation service supports the export and the import of preservation objects and evidences produced ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 4.3.2 Preservation with temporary storage | In this preservation storage model, the preservation service does not permanently store the SubDO, but it stores them only as long as needed to create the corresponding evidence. The preservation evidences are produced asynchronously and are stored during some time-period to allow the client to retrieve it. EXAMPLE 1: ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 4.3.3 Preservation without storage | In this preservation storage model, the preservation service does not store the SubDOs and the preservation evidences are produced synchronously. EXAMPLE: This preservation storage model can be implemented doing a continuous augmentation of CAdES signatures with archive-time-stamp-v3 attributes according to ETSI EN 319... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 4.4 Preservation schemes, profile and policies | A preservation service according to the present document may support different preservation schemes, which define the general approach for preservation. Refer to Annex F for preservation schemes defined in the present document. A preservation scheme supports at least one preservation goal (see clause 4.2) and is operat... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5 Technical Specification of Protocol | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.1 Introduction and Overview | The present document first specifies the semantics of the different calls of the protocol for the preservation protocol in a generic fashion and then specifies the concrete syntax of the conveyed data elements based on XML and JSON together with its binding to SOAP and REST respectively. This covers the following opera... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.2 Discovery of supported preservation profiles | A preservation service as specified in the present document may be operated in different operation modes (see clauses 4.2 to 4.4), which are expressed by preservation profiles as described by Profile elements as specified in clause 5.4.7. To enable a client to retrieve the set of supported preservation profiles, the pr... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3 Operation requests and responses | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.1 Basic types for requests and responses | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.1.1 Component Request | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.1.1.1 Semantics | The Request component is used as basic type within the operation requests defined in clauses 5.3.3 to 5.3.8. Below follows a list of the sub-components that may be present within this component: • The optional OptionalInputs element. If present, it shall contain a sub-component as defined in clause 4.1.8 of OASIS DSS-X... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.1.1.2 XML Syntax | The XML type RequestType shall implement the requirements defined in the Request component. The RequestType XML elements shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <complexType name="RequestType"> <sequence> <element name="OptionalInputs... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.1.1.3 JSON Syntax | The component Request is used as a base type only, not as a JSON instance. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.1.2 Component Response | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.1.2.1 Semantics | The Response component is used as basic type within the operation responses defined in clauses 5.3.3 to 5.3.9. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 22 Below follows a list of the sub-components that may be present within this component: • The optional OptionalOutputs element may be present and shall, if present, conta... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.1.2.2 XML Syntax | The XML type ResponseType shall implement the requirements defined in the Response component. The ResponseType XML type shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <complexType name="ResponseType"> <sequence> <element name="OptionalOutput... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.1.2.3 JSON Syntax | The component Response is used as a base type only, not as a JSON instance. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.2 RetrieveInfo | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.2.1 RetrieveInfo request | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.2.1.1 Semantics | The RetrieveInfo request shall extend the Request component (see clause 5.3.1.1) and shall inherit the set of sub-components. The RetrieveInfo request allows to retrieve information about the preservation profiles supported by the preservation service. As the number of preservation profiles supported by a preservation ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.2.1.2 XML Syntax | The XML type RetrieveInfoType shall implement the requirements defined in the RetrieveInfo component. The RetrieveInfoType XML element shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <complexType name="RetrieveInfoType"> <complexContent> <ext... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.2.1.3 JSON Syntax | The RetrieveInfoType JSON object shall implement in JSON syntax the requirements defined in the RetrieveInfo component. The RetrieveInfoType JSON object shall be defined as in JSON Schema file (Preservation-API.json) provided in Annex D, and is copied below for information. "pres-RetrieveInfoType": { "type": "object", ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.2.2 RetrieveInfoResponse | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.2.2.1 Semantics | The RetrieveInfoResponse shall extend the Response component (see clause 5.3.1.2) and shall inherit the set of sub-components. RetrieveInfoResponse is returned as response to invoking the RetrieveInfo operation. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 24 The RetrieveInfoResponse may contain the following sub-components: ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.2.2.2 XML Syntax | The XML type RetrieveInfoResponseType shall implement the requirements defined in the RetrieveInfoResponse component. The RetrieveInfoResponseType XML element shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <complexType name="RetrieveInfoResp... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.2.2.3 JSON Syntax | The RetrieveInfoResponseType JSON object shall be defined as in JSON Schema file (Preservation-API.json) provided in Annex D, and is copied below for information. "pres-RetrieveInfoResponseType": { "type": "object", "properties": { "optOut": { "$ref": "#/definitions/dsb-OptionalOutputsType" }, "reqId": { "type": "strin... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.3 PreservePO | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.3.1 PreservePO request | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.3.1.1 Semantics | The PreservePO request shall extend the Request component (see clause 5.3.1.1) and shall inherit the set of sub-components. It is used to submit zero or more preservation objects (PO) to the preservation service. The details how the preservation is performed is determined by the provided Profile element, which refers t... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.3.1.2 XML Syntax | The PreservePOType XML type shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <xs:complexType name="PreservePOType"> <complexContent> <extension base="pres:RequestType"> <sequence> <element name="Profile" type="anyURI"/> <element ref="pres:PO" ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.3.1.3 JSON Syntax | The PreservePOType JSON object shall be defined as in JSON Schema file (Preservation-API.json) provided in Annex D, and is copied below for information. "pres-PreservePOType": { "type": "object", "properties": { "optIn": { "$ref": "#/definitions/dsb-OptionalInputsType" }, "reqId": { "type": "string" }, "pro": { "type":... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.3.2 PreservePOResponse | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.3.2.1 Semantics | The PreservePOResponse shall extend the Response component (see clause 5.3.1.2) and shall inherit the set of sub-components. PreservePOResponse shall be returned as response to invoking the PreservePO operation. Below follows a list of the sub-components that may be present within this component: • The optional POID el... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.3.2.2 XML Syntax | The XML type PreservePOResponseType shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <xs:complexType name="PreservePOResponseType"> <complexContent> <extension base="pres:ResponseType"> <sequence> <element ref="pres:POID" minOccurs="0" maxOccu... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.3.2.3 JSON Syntax | The PreservePOResponseType JSON object shall be defined as in JSON Schema file (Preservation_API.json) provided in Annex D, and which is copied below for information. "pres-PreservePOResponseType": { "type": "object", "properties": { "optOut": { "$ref": "#/definitions/dsb-OptionalOutputsType" }, "reqId": { "type": "str... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.4 RetrievePO (Conditional) | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.4.1 RetrievePO Request | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.4.1.1 Semantics | The RetrievePO request shall extend the Request component (see clause 5.3.1.1) and shall inherit the set of sub-components. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 28 The RetrievePO operation may only be provided in preservation schemes with storage (see clause 4.3.1) or with temporary storage (see clause 4.3.2). This op... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.4.1.2 XML Syntax | The XML type RetrievePOType shall implement the requirements defined in the RetrievePO component. The RetrievePOType XML type shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <xs:complexType name="RetrievePOType"> <complexContent> <extension b... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.4.1.3 JSON Syntax | The RetrievePOType JSON object shall implement in JSON syntax the requirements defined in the RetrievePO component. The RetrievePOType JSON object shall be defined as in the JSON Schema file (Preservation-API.json) provided in Annex D, and which is copied below for information. "pres-RetrievePOType": { "type": "object"... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.4.2 RetrievePOResponse | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.4.2.1 Semantics | The RetrievePOResponse shall extend the Response component (see clause 5.3.1.2) and shall inherit the set of sub-components. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 30 RetrievePOResponse shall be returned as response to invoking the RetrievePO operation. The returned PO elements shall contain the (sequence of) preservati... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.4.2.2 XML Syntax | The XML type RetrievePOResponseType shall implement the requirements defined in the RetrievePOResponse component. The RetrievePOResponseType XML type shall be defined as in the XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <xs:complexType name="RetrievePOResponse... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.4.2.3 JSON Syntax | The RetrievePOResponseType JSON object shall implement in JSON syntax the requirements defined in the RetrievePOResponse component. The RetrievePOResponseType JSON object shall be defined as in the JSON Schema file (Preservation-API.json) provided in Annex D, and which is copied below for information. "pres-RetrievePOR... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.5 DeletePO (Conditional) | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.5.1 DeletePO Request | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.5.1.1 Semantics | The DeletePO request shall extend the Request component (see clause 5.3.1.1) and shall inherit the set of sub-components. The DeletePO request shall only be supported in the case of a preservation scheme with storage (see clause 4.3.1). In order to delete a (sequence of) preservation object(s) and corresponding metadat... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.5.1.2 XML Syntax | The XML type DeletePOType shall implement the requirements defined in the DeletePO component. The DeletePOType XML type shall be defined as in the XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 32 <xs:complexType name="DeleteP... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.5.1.3 JSON Syntax | The DeletePOType JSON object shall implement in JSON syntax the requirements defined in the DeletePO component. The DeletePOType JSON object shall be defined as in the JSON Schema file (Preservation-API.json) provided in Annex D, and which is copied below for information. "pres-DeletePOType": { "type": "object", "prope... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.5.2 DeletePOResponse | The DeletePOResponse shall extend the Response component (see clause 5.3.1.2) and shall inherit the set of sub-components. DeletePOResponse shall be returned as response to invoking the DeletePO operation. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 33 The following error codes may appear in the Result/ResultMinor component ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.6 UpdatePOC (Optional) | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.6.1 UpdatePOC Request | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.6.1.1 Semantics | The UpdatePOC request shall extend the Request component (see clause 5.3.1.1) and shall inherit the set of sub-components. The UpdatePOC request allows to update a POC in case of preservation with storage and provide a new version of it, if the preservation service and the applied POC-Format supports this feature (see ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.6.1.2 XML Syntax | The XML type UpdatePOCType shall implement the requirements defined in the UpdatePOC component. The UpdatePOCType XML type shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 34 <xs:complexType name="UpdatePO... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.6.1.3 JSON Syntax | The UpdatePOCType JSON object shall implement in JSON syntax the requirements defined in the UpdatePOC component. The UpdatePOCType JSON object shall be defined as in the JSON Schema file (Preservation-API.json)provided in Annex C, and which is copied below for information. "pres-UpdatePOCType": { "type": "object", "pr... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.6.2 UpdatePOCResponse | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.6.2.1 Semantics | The UpdatePOCResponse shall extend the Response component (see clause 5.3.1.2) and shall inherit the set of sub-components. UpdatePOCResponse shall be returned as response to invoking the UpdatePOC operation. After the internal processing of the UpdatePOC request the preservation service returns UpdatePOCResponse, whic... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.6.2.2 XML Syntax | The XML type UpdatePOCResponseType shall implement the requirements defined in the UpdatePOCResponse component. The UpdatePOCResponseType XML type shall be defined as in the XML Schema file (Preservation-API.xsd provided in Annex C, and which is copied below for information. <xs:complexType name="UpdatePOCResponseType"... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.6.2.3 JSON Syntax | The UpdatePOCResponseType JSON object shall implement in JSON syntax the requirements defined in the UpdatePOCResponse component. The UpdatePOCResponseType JSON object shall be defined as in the JSON Schema file (Preservation_API.json) provided in Annex D, and which is copied below for information. "pres-UpdatePOCRespo... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.7 RetrieveTrace (Optional) | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.7.1 RetrieveTrace request | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.7.1.1 Semantics | The RetrieveTrace request shall extend the Request component (see clause 5.3.1.1) and shall inherit the set of sub-components. The RetrieveTrace request allows to request an audit trail element, which contains information with respect to relevant events, which happened within a preservation service for a specific (set ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.7.1.2 XML Syntax | The XML type RetrieveTraceType shall implement the requirements defined in the RetrieveTrace component. The RetrieveTraceType XML type shall be defined as in the XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <xs:complexType name="RetrieveTraceType"> <complexConte... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.7.1.3 JSON Syntax | The RetrieveTraceType JSON object shall implement in JSON syntax the requirements defined in the RetrieveTrace component. The RetrieveTraceType JSON object shall be defined as in the JSON Schema file (Preservation-API.json) provided in Annex D, which and is copied below for information. "pres-RetrieveTraceType": { "typ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.7.2 RetrieveTraceResponse | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.7.2.1 Semantics | The RetrieveTraceResponse shall extend the Response component (see clause 5.3.1.2) and shall inherit the set of sub-components. RetrieveTraceResponse shall be returned as response to invoking the RetrieveTrace operation and shall contain the trace of operations corresponding to the provided POID. After the internal pro... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.7.2.2 XML Syntax | The XML type RetrieveTraceResponseType shall implement the requirements defined in the RetrieveTraceResponse component. The RetrieveTraceResponseType XML type shall be defined as in the XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <xs:complexType name="RetrieveT... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.7.2.3 JSON Syntax | The RetrieveTraceResponseType JSON object shall implement in the JSON syntax the requirements defined in the RetrieveTraceResponse component. The RetrieveTraceResponseType JSON object shall be defined as in JSON Schema file (Preservation_API.json) provided in Annex D, and which is copied below for information. "pres-Re... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.8 ValidateEvidence (Optional) | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.8.1 ValidateEvidence Request | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.8.1.1 Semantics | The ValidateEvidence request shall extend the Request component (see clause 5.3.1.1) and shall inherit the set of sub-components. The ValidateEvidence request allows to validate a provided preservation evidence (Evidence) and optionally a corresponding (set of) preservation objects (PO), which are protected by it. The ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.8.1.2 XML Syntax | The XML type ValidateEvidenceType shall implement the requirements defined in the ValidateEvidence component. The ValidateEvidenceType XML type shall be defined as in the XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <xs:complexType name="ValidateEvidenceType"> <... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.8.1.3 JSON Syntax | The ValidateEvidenceType JSON object shall implement in JSON syntax the requirements defined in the ValidateEvidence component. The ValidateEvidenceType JSON object shall be defined as in the JSON Schema file (Preservation-API.json) provided in Annex D, and which is copied below for information. "pres-ValidateEvidenceT... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.8.2 ValidateEvidenceResponse | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.8.2.1 Semantics | The ValidateEvidenceResponse shall extend the Response component (see clause 5.3.1.2) and shall inherit the set of sub-components. ValidateEvidenceResponse shall be returned as response to invoking the ValidateEvidence operation. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 40 The ValidateEvidenceResponse may contain the foll... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.8.2.2 XML Syntax | The XML type ValidatePOCResponseType shall implement the requirements defined in the ValidatePOCResponse component. The ValidatePOCResponseType XML type shall be defined as in the XML Schema file (Preservation_API.xsd) provided in Annex C, and which is copied below for information. <xs:complexType name="ValidatePOCResp... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.8.2.3 JSON Syntax | The ValidatePOCResponseType JSON object shall implement in JSON syntax the requirements defined in the ValidatePOCResponse component. The ValidatePOCResponseType JSON object shall be defined as in the JSON Schema file (Preservation-API.json) provided in Annex D, and which is copied below for information. "pres-Validate... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.9 Search (Optional) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.