hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.9.1 Search request | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.9.1.1 Semantics | The Search request shall extend the Request component (see clause 5.3.1.1) and shall inherit the set of sub-components. The Search request allows to search among the (sets of) preservation object(s), which are accessible by the client. For this purpose, the client provides a query string (Filter), which allows to searc... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.9.1.3 JSON Syntax | The SearchType JSON object shall implement in JSON syntax the requirements defined in the Search component. The SearchType 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-SearchType": { "type": "object", "properties": { "o... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.9.2 SearchResponse | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.9.2.1 Semantics | The SearchResponse shall extend the Response component (see clause 5.3.1.2) and shall inherit the set of sub-components. SearchResponse shall be returned as response to invoking the Search operation. The SearchResponse may contain the following sub-component: • Zero or more instances of the optional POID element. Each ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.9.2.2 XML Syntax | The XML type SearchResponseType shall implement the requirements defined in the SearchResponse component. The SearchResponseType 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="SearchResponseType"> <complexC... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.3.9.2.3 JSON Syntax | The SearchResponseType JSON object shall implement in JSON syntax the requirements defined in the SearchResponse component. The SearchResponseType 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-SearchResponseType": { ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4 Components for operations | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.1 Overview | The components in the present clause are provided in alphabetic ordering as shown in Table 16. Table 16 Component Clause DeletionMode 5.4.2 Event 5.4.3 Evidence 5.4.4 PO 5.4.5 PreservationStorageModel 5.4.6 Profile 5.4.7 Status 5.4.8 SubjectOfRetrieval 5.4.9 Trace 5.4.10 |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.2 Component DeletionMode | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.2.1 Semantics | The DeletionMode component specifies the details of the Mode parameter in the DeletePO request (see clause 5.3.5). The DeletionMode component shall contain the following sub-component: • The value element. It shall contain one instance of a string. Its value shall be limited to an item of the following set: - OnlySubDO... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.2.2 XML Syntax | The XML type DeletionModeType shall implement the requirements defined in the DeletionMode component. The DeletionModeType 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. <simpleType name="DeletionModeType"> <restriction base="st... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.2.3 JSON Syntax | The DeletionModeType JSON object shall implement in JSON syntax the requirements defined in the DeletionMode component. The DeletionModeType JSON object shall be defined as in the JSON Schema file (Preservation-API.xsd) provided in Annex D, and which is copied below for information. ETSI ETSI TS 119 512 V1.2.1 (2023-05... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.3 Component Event | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.3.1 Semantics | The Event component contains information about an event, which occurred within the preservation service. It is part of the Trace component (see clause 5.4.10), which can be retrieved with the RetrieveTrace operation (see clause 5.3.7). The Event component shall contain the following sub-components: • The Time element. ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.3.2 XML Syntax | The EventType 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. <complexType name="EventType"> <sequence> <element name="Time" type="dateTime"/> <element name="Subject" type="string"/> <element name="Operation" type="string"/> <ele... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.3.3 JSON Syntax | The EventType JSON object shall implement in JSON syntax the requirements defined in the Event component. The EventType JSON element shall be defined as in the JSON Schema file (Preservation-API.xsd) provided in Annex D, and which is copied below for information. "pres-EventType": { "type": "object", "properties": { "t... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.4 Component Evidence | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.4.1 Semantics | The Evidence component is used as an input element within the ValidateEvidence operation (see clause 5.3.8) to provide the preservation evidence, which is to be validated. The Evidence component shall extend the PO component (see clause 5.4.5), from which it inherits the mandatory subcomponent representing the value of... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.4.2 XML Syntax | The XML type EvidenceType shall implement the requirements defined in the Evidence component. In this case the value of the Evidence component is a choice between a base64 encoded binaryData element and an XML- based xmlData element from an arbitrary namespace. The EvidenceType XML type shall be defined as in the XML S... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.4.3 JSON Syntax | The EvidenceType JSON object shall implement in JSON syntax the requirements defined in the Evidence component. In this case the value of the Evidence component is a base64 encoded binaryData element. The EvidenceType JSON element shall be defined as in the JSON Schema file (Preservation-API.json) provided in Annex D, ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.5 Component PO | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.5.1 Semantics | The PO component is a generic container object, which is used for conveying preservation objects. This generic component is used in several operations, such as PreservePO (see clause 5.3.3), RetrievePO (see clause 5.3.4), UpdatePOC (see clause 5.3.6) and ValidateEvidence (see clause 5.3.8). The component PO shall conta... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.5.2 XML Syntax | The XML type POType shall implement the requirements defined in the PO component. In this case the value of the preservation object is a choice between a base64 encoded binaryData element and an XML-based xmlData element from an arbitrary namespace. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 49 NOTE: The technical destincti... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.5.3 JSON Syntax | The POType JSON object shall implement in JSON syntax the requirements defined in the PO component. In this case the value of the preservation object is a base64 encoded binaryData element. The POType JSON object shall be defined as in the JSON Schema file (Preservation-API.json) provided in Annex D, and is copied belo... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.6 Component PreservationStorageModel | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.6.1 Semantics | The PreservationStorageModel component specifies the storage model (see clause 4.3) of the operational profile (see clause 5.4.7) of the preservation service under consideration. The PreservationStorageModel component shall be an instance of a string, which shall be one of the following values: • WithStorage - for a pr... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.6.2 XML Syntax | The XML type PreservationStorgeModelType shall implement the requirements defined in the PreservationStorgeModel component. The PreservationStorageModelType XML element shall be defined as in XML Schema file (Preservation-API.xsd)provided in Annex C, and which is copied below for information. <simpleType name="Preserva... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.6.3 JSON Syntax | The component PreservationStorageModel is derived from the string type with the admissible values specified above. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.7 Component Profile | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.7.1 Semantics | The Profile component specifies the operational details of a preservation profile, as outlined in clause 4.4. The Profile component shall contain the following sub-components: • The ProfileIdentifier element. It shall be present and contain a URI according to IETF RFC 3986 [2], which uniquely identifies the preservatio... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.7.2 XML Syntax | The XML type ProfileType shall implement the requirements defined in the Profile component. The ProfileType XML type defined in the present document is an extension of the info:ProfileType defined in OASIS Digital Signature Service Information [6] and shall be defined as in the XML Schema file (Preservation-API.xsd) pr... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.7.3 JSON Syntax | The ProfileType JSON object shall implement in JSON syntax the requirements defined in the Profile component. The ProfileType 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-ProfileType": { "type": "object", "propertie... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.8 Component Status | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.8.1 Semantics | The Status component is used in the RetrieveInfo request (see clause 5.3.2). The Status component shall contain the following sub-components: • The value element. It shall contain one instance of a string which shall be one of the following values: - active - to indicate that only active preservation profiles shall be ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.8.2 XML Syntax | The XML type StatusType shall implement the requirements defined in the Status component. The StatusType 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. <simpleType name="StatusType"> <restriction base="string"> <enumeration valu... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.8.3 JSON Syntax | The component Status is derived from the string type with the values specified above. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.9 Component SubjectOfRetrieval | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.9.1 Semantics | The SubjectOfRetrieval component is used in the RetrievePO request to specify what should be the subject of the retrieval call. The SubjectOfRetrieval component shall contain the following sub-component: • The value element. It shall contain one instance of a string which shall be one of the following values: - PO - in... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.9.2 XML Syntax | The XML type SubjectOfRetrievalType shall implement the requirements defined in the SubjectOfRetrieval component. The SubjectOfRetrievalType 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. <simpleType name="SubjectOfRetrievalType... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.9.3 JSON Syntax | The SubjectOfRetrievalType JSON object shall implement in JSON syntax the requirements defined in the SubjectOfRetrieval component. The SubjectOfRetrievalType 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-SubjectOfRe... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.10 Component Trace | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.10.1 Semantics | The Trace component contains a sequence of Event elements (see clause 5.4.4) and is returned as response to a RetrieveTrace request (see clause 5.3.7). The Trace component may contain the following sub-component: • Zero or more instances of the Event element. Each instance of the Event element shall be according to cla... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.10.2 XML Syntax | The XML type TraceType shall implement the requirements defined in the Trace component. The TraceType 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="TraceType"> <sequence> <element ref="pres:Event" minOccurs="0" m... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.4.10.3 JSON Syntax | The TraceType JSON object shall implement in JSON syntax the requirements defined in the Trace component. The TraceType JSON object is defined in the JSON Schema file (Preservation-API.json) provided in Annex D, and which is copied below for information. "pres-TraceType": { "type": "object", "properties": { "event": { ... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5 Components for ASiC extensions | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.1 Overview and motivation | Among the preservation object containers mentioned in the present document is the ASiC-container defined in ETSI EN 319 162-1 [1] and profiled in clause A.3.1. The components defined in the present clause specify preservation-specific extensions for the ASiCManifest component (see clause 5.5.2) and the DataObjectRefere... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2 Extensions for ASiCManifest | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.1 ContainerID Extension | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.1.1 Semantics | The ContainerID extension may be used to convey the preservation service-specific identifier of a preservation object container. The following sub-component shall be present within the ContainerID component: • The POID element shall be present and indicate the Preservation Object IDentifier (POID) of the preservation o... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.1.2 Syntax | The XML type ContainerIDType shall implement the requirements defined in the ContainerID component. The ContainerID XML element shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <element name="ContainerID" type="pres:ContainerIDType" /> <comple... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.1.3 Criticality | The ContainerID extension should not be critical. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.2 PreservationPeriod Extension | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.2.1 Semantics | The PreservationPeriod extension consists of a single element, which shall indicate the preservation period of the preservation object container. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 58 |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.2.2 Syntax | The XML element PreservationPeriod shall implement the requirements defined for this component. The PreservationPeriod XML element shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <element name="PreservationPeriod" type="date" /> |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.2.3 Criticality | The PreservationPeriod extension should not be critical. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.3 PreservationSubmitter Extension | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.3.1 Semantics | The PreservationSubmitter extension consists of a single element, which shall identify the client in its role as preservation submitter. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.3.2 Syntax | The XML element PreservationSubmitter shall implement the requirements defined for this component. The PreservationSubmitter XML element shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <element name="PreservationSubmitter" type="string" /> |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.3.3 Criticality | The PreservationSubmitter extension should not be critical. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.4 IsUpdatedVersionOf Extension | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.4.1 Semantics | The IsUpdatedVersionOf extension allows to indicate that a preservation object container is indeed an update of another preservation object container. For this purpose, it shall refer to this preservation object container. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.4.2 Syntax | The XML element IsUpdatedVersionOf shall implement the requirements defined for this component. The IsUpdatedVersionOf XML element shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <element name="IsUpdatedVersionOf" type="anyURI" /> |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.4.3 Criticality | The IsUpdatedVersionOf extension should not be critical. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.5 CanonicalizationMethod Extension | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.5.1 Semantics | The CanonicalizationMethod extension allows to specify how XML data contained in a preservation object container shall be canonicalized prior to applying preservation techniques. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 59 |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.5.2 Syntax | The XML element CanonicalizationMethod shall implement the requirements defined for this component. The CanonicalizationMethod XML element shall be defined as in the XML Schema file (xmldsig-core- schema-dss-rw.xsd) provided with OASIS DSS-X Core 2.0 [5]. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.5.3 Criticality | The CanonicalizationMethod extension should be critical, because preservation evidences will appear to become invalid, if a required canonicalization method is missed to be applied. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.6 ValidationReport Extension | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.6.1 Semantics | The ValidationReport extension allows to insert a validation report, which provides the validation result for the preservation evidence and data objects referred to in the corresponding ASiCManifest element. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.6.2 Syntax | The XML element ValidationReport shall satisfy the requirements defined in clause 5.4.5. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.2.6.3 Criticality | The ValidationReport extension should not be critical. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.3 Extensions for DataObjectReference | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.3.1 IsMetaDataOf Extension | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.3.1.1 Semantics | The IsMetaDataOf extension allows to indicate that a preservation object is indeed a meta data object, which describes another data object. For this purpose, it shall refer to the preservation object of which it is a meta data information. |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.3.1.2 Syntax | The XML element IsMetaDataOf shall implement the requirements defined for this component. The IsMetaDataOf XML element shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <element name="IsMetaDataOf" type="anyURI" /> |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.5.3.1.3 Criticality | The IsMetaDataOf extension should not be critical. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 60 |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.6 Components for other preservation object formats | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.6.1 Component DigestList | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.6.1.1 Semantics | The DigestList component is conveyed as content of a single PO component (see clause 5.4.5) within the PreservePO call (see clause 5.3.3) of the preservation scheme with temporary storage as specified in clause F.2. It is only admissible to submit a single PO component with a single DigestList component within one Pres... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.6.1.2 XML Syntax | The XML type DigestListType shall implement the requirements defined in the DigestList component. The DigestListType 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="DigestListType"> <sequence> <element ref="ds-r... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 5.6.1.3 JSON Syntax | The component DigestList is not used as JSON object directly. The DigestListType JSON object shall implement in JSON syntax the requirements defined in the DigestList component. Properties of the JSON object shall implement the sub-components of DigestList using JSON-specific names mapped as shown in Table 24. Table 24... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 6 Requirements for preservation object data formats | |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 6.1 General aspects and requirements | An important property of the preservation service specified in the present document is that it is able to support different preservation schemes and preservation profiles (see clauses 4.4 and 5.4.7), which may use preservation objects in different formats. Among the preservation objects one may distinguish: • submissio... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 6.2 Specific requirements for preservation object containers | Among the additional output formats supported within the preservation profile (see clause 5.4.7) are in particular preservation object containers. For preservation object containers, the general requirements for preservation data objects (see clause 6.1) and the following requirements shall be fulfilled: 1) It shall al... |
cdd823ba984b81337eedcd223e1a6810 | 119 512 | 7 Requirements for preservation schemes | A preservation scheme (specification) shall meet the following general requirements: 1) A preservation scheme shall be documented in a permanent and readily available public specification, in sufficient detail so that interoperability between independent implementations is possible. 2) A preservation scheme shall be id... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 1 Scope | The present document builds on the general policy requirements specified in ETSI EN 319 401 [1], specifies policy and security requirements for trust service providers providing long-term preservation of digital signatures and of general data, i.e. signed data or unsigned data, using digital signature techniques. The p... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 2 References | |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 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... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 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... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.4] 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.24] or in form o... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 3.2 Symbols | Void. ETSI ETSI TS 119 511 V1.1.1 (2019-06) 13 |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.4] and the following apply: AUG Augmentation goal CSA Certificate Status Authority EUMS European Union Member State OVR Overall PDS Preservation of Digital Signatures PGD Preservation of General Data PO Preservation Object POC Prese... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 3.4 Notations | The requirements, recommendations or permissions identified in the present document include: a) requirements, recommendations or permissions applicable to any TSP conforming to the present document. Such requirements are indicated by clauses without any additional marking; b) requirements, recommendations or permission... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4 General Concepts | |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.1 Preservation storage models | |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.1.1 Overview | Three preservation storage models for the preservation service are distinguished: 1) Preservation services with storage [WST]. In this case, the data to be preserved is stored by the preservation service while the evidences and the preserved data are delivered upon request by the preservation service to the preservatio... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.1.2 Preservation service with storage [WST] | Figure 1: Functional model of a preservation service with storage [WST] The preservation protocol allows the preservation client to interact with the preservation interface. A preservation service with storage stores the SubDO and the preservation object(s) (PO(s)) derived from the SubDO(s) by augmentation or building ... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.1.3 Preservation service with temporary storage [WTS] | Figure 2: Functional model of a preservation service with temporary storage [WTS] The preservation protocol allows the preservation client to interact with the preservation interface. A preservation service with temporary storage temporarily stores one or more SubDO(s) or one or more submitted hash value(s) received by... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.1.4 Preservation service without storage [WOS] | Figure 3: Functional model of a preservation service without storage [WOS] The preservation protocol allows the preservation client to interact with the preservation interface. A preservation service without storage neither stores the data to be preserved nor a hash of the data nor evidences. It produces evidences sync... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.