hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.9 Implementation is dismissed | CONDITION: There is consensus that the implementation of the change request will not be performed. ACTION: Project members should review the request issue. OUTPUT: The label of the issue should be updated to "Propose closing". The request issue should be updated with the reasons for dismissing the implementation. |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.10 Implementation is clear after discussion | CONDITION: There is consensus on how to implement the change request. ACTION: Project members should review the request issue. If the change request comes from a contributor, he or she may be included in the discussion. OUTPUT: The label of the issue should be updated to "Needs implementation". The request issue should... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.11 Implementation starts | CONDITION: An ontology developer or contributor starts working on the implementation of the change request. ACTION: The ontology developer selects a "Needs implementation" change request to implement; alternatively, the contributor selects a "Needs implementation" change request raised by him/her to implement. The impl... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.12 Implementation ends | CONDITION: An ontology developer or contributor finishes working on the implementation of the change request. ACTION: The ontology developer or contributor should implement what is expected in the plan for implementation. A new merge request should be created from the issue branch to the development branch, as specifie... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.13 Implementation is not approved | CONDITION: There is no consensus that the implementation is approved. ACTION: Project members should review the available implementation against the implementation plan in the request issue. They should review the results of the continuous integration tests. OUTPUT: The label of the issue should be updated to "Needs di... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.14 Implementation is approved | CONDITION: There is a consensus to approve the implementation. ACTION: Project members should review the available implementation against the implementation plan in the request issue. They should review the results of the continuous integration tests. OUTPUT: The merge request shall be merged. The issue shall be closed... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.2 Proposing a new change request | Any contributor may create a new change request to a SAREF project. The contributor shall do so by creating a new issue describing the change request in the corresponding repository of the ETSI public forge. This issue is called the request issue, and is identified by its issue number. The request issue should be label... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.3 Reviewing new change requests | Any contributor may review and discuss new request issues. Periodically, the project members should review the submitted request issues. If needed, the project members may ask for clarifications to the user proposing the new request issue. The project leader should review the request issue and should make a proposal fo... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.4 Implementing change requests | Any ontology developer or contributor may start working on the implementation of a change request. A change request shall be implemented in its issue branch. The issue branch shall be created by forking the development branch of the SAREF project version. The name of the issue branch should begin with issue-, and end w... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.5 Reviewing change request implementations | Any contributor may review and discuss change request implementation in their corresponding merge request. Periodically, the project members should review the available implementation against the implementation plan in the request issue. They should review the results of the continuous integration tests, which should c... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.6 Continuous integration tests | When a commit is pushed to a develop branch or to an issue branch of the SAREF extension repository, the SAREF pipeline program should be run in develop model to check the contribution, as specified in clause 6.4.4. ETSI ETSI TS 103 673 V1.2.1 (2024-01) 24 |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8 SAREF project release workflow | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.1 Workflow | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.1.0 Introduction | The SAREF project release workflow is about ETSI TC SmartM2M to accept and trigger the generation of SAREF project releases. SAREF project versions may be new versions of SAREF core, new versions of existing SAREF extensions, or initial versions (V1.1.1) of new SAREF extensions. The project leader is responsible for pr... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.1.1 SAREF Project release is prepared | CONDITION: The project leader wants to prepare a new SAREF project release. ACTION: The project leader creates the pre-release branch for the SAREF project version by forking the development branch. Clause 8.2 specifies how to prepare a SAREF project release. OUTPUT: The pre-release branch is created for the SAREF proj... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.1.2 SAREF Project release needs improvement | CONDITION: A new change request is accepted for this SAREF project version, or the SAREF pipeline software triggers errors when run in release mode. ACTION: If a new change request is accepted, the project leader waits until the change request is closed, and merges the updated develop branch into the pre-release branch... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.1.3 Project release is improved | CONDITION: The pre-release branch is synced with the development branch, no change request is open for this SAREF project version. ACTION: The project leader requests the Steering Board to approve the triggering of the release. Clause 8.3 specifies how to review a SAREF project release. OUTPUT: The SAREF pipeline softw... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.1.4 Project release is ready | CONDITION: The SAREF pipeline software triggers no error when run in release mode. The Steering Board accepts to trigger the SAREF project release. ACTION: The project leader and the Technical Board are responsible for triggering the release. Clause 8.4 specifies how to publish SAREF project releases. OUTPUT: The relea... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.2 Preparing a project release | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.2.0 Introduction | The project leader is responsible for preparing the SAREF project release. This requires to perform the following actions: • To prepare the project release documentation. • To prepare the pre-release branch of the SAREF project version. The next clauses describe these steps in detail. |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.2.1 Preparing the project release documentation | The project leader should check that the SAREF extension is well described in the saref-portal-static project of the ETSI public forge, which hosts the static pages of the ontology portal. The file named extensions.html shall contain a description of the SAREF project version in a way similar than the other SAREF proje... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.2.2 Preparing the project version pre-release branch | The pre-release branch shall be named after the project version number of the SAREF project version. The development branch develop-vx.y.z corresponding to the target project version number vx.y.z shall be forked and given the name prerelease-vx.y.z. To achieve this step, the branch protections may need to be relaxed t... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.3 Reviewing ontology releases | The Technical Board will review all the prepared ontology releases. If needed, the Technical Board will ask for clarifications to the project leader in charge of the ontology release. The decision will be taken of publishing the ontology release when at least two members of the Technical Board have reviewed and approve... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 8.4 Publishing an ontology release | ETSI TC SmartM2M is responsible for accepting the SAREF project release. The Project leader and the Technical Board are responsible for triggering the release. The content of the SAREF public portal is generated from the release branches of SAREF projects, and from the saref-portal-static project. The release branch of... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.1 Introduction | The present clause specifies how SAREF project versions should be specified and documented in the sources of the SAREF project on the SAREF public forge. SAREF project version should be documented in an ETSI Technical Specification document, and potentially an associated ETSI Technical Report document. It is recommende... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.2 Structure of the SAREF project version directory | The directory of the different SAREF project versions shall have a homogeneous structure. There shall exist a file named README.md. This file shall contain a description of the SAREF project version in a similar way as other SAREF project versions. There shall exist a file named .gitignore. This file shall contain each... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.3 Ontology requirements | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.3.1 The requirements directory | The requirements directory should contain one file named requirements.csv. This file shall conform to the requirements specification as defined in clause 9.3.2. ETSI ETSI TS 103 673 V1.2.1 (2024-01) 28 |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.3.2 Requirements specification | The file with the requirements specification shall be a CSV (Comma-Separated Values) file encoded in UTF-8. The delimiter character used in the file shall be ';', the quote character (if needed) '"' and the end of line one "\n". The first line of the file shall be the following: Id;Category;Requirement The rest of the ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4 Ontology specification | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.1 The ontology directory | The ontology directory of the SAREF project version shall contain a file called the ontology document of the SAREF project version. If the SAREF project is SAREF core, then the ontology document shall be named saref.ttl. If the SAREF project is a SAREF extension with acronym ABCD, then the ontology document shall be na... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.2 Prefixes declaration | The ontology document may contain a list of prefixes declarations. If a prefix declaration has a prefix in the first column of Table 1, then the namespace shall be equal to the content of the second column. NOTE: In the last line of Table 1, efgh is any SAREF extension acronym as specified in clause 3.1. Table 1: List ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.3 The ontology declaration | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.3.1 Ontology IRI and Ontology Version IRI | The Ontology IRI of the ontology document of SAREF core shall be: https://saref.etsi.org/core/ The Ontology IRI of the ontology document of a SAREF extension with acronym ABCD shall be: https://saref.etsi.org/saref4abcd/ EXAMPLE 1: The ontology IRI of the ontology document of SAREF4CITY is https://saref.etsi.org/saref4... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.3.2 Documentation metadata | The ontology document shall contain at least one metadata dcterms:title. Each value for this metadata shall be a literal with datatype IRI xsd:string or rdf:langString There should be at least one value with the rdf:langString datatype and the en language. EXAMPLE: The ontology document of SAREF4CITY version v1.1.2 con... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.3.3 Creators and contributors | The ontology document shall contain at least one metadata dcterms:creator, encoding the identity of any creator. The Steering Board and Project leader are responsible for approving the set of creators. The ontology document may contain at least one metadata dcterms:contributor, encoding the identity of any contributor.... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.4 Term declarations | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.4.1 Term IRI | If the SAREF project version is SAREF core with version vx.y.z, then the ontology document declares all and only those Terms whose Term IRI have the form: https://saref.etsi.org/core/localName If the SAREF project version is a SAREF extension with acronym ABCD and version vx.y.z, then the ontology document declares all... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.4.2 Documentation metadata | Every Term declared in the ontology document shall have at least one metadata rdfs:label with the human-readable version of the Term. The value for this metadata shall be a literal with datatype IRI xsd:string or rdf:langString. There should be at least one value with the rdf:langString datatype and the en language. Ev... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.5 OWL profile, consistency, lack of pitfalls and class satisfiability | The ontology in the ontology document shall satisfy the OWL2 DL profile [2], with the exception that unknown datatypes may be used. The ontology in the ontology document shall be Consistent [4]. The ontology in the ontology document should not present ontology development pitfalls [i.18]. Every Term declared in the ont... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.4.6 Conformance to reference ontology patterns | The ontology in the ontology document of a SAREF project version shall conform to the SHACL specification of each reference ontology pattern defined in this SAREF project version (see clause 10). If the ontology in the ontology document of a SAREF project version imports an Ontology Version IRI defined in another SAREF... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.5 Ontology tests | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.5.1 The tests directory | The tests directory should contain one file named tests.csv. This file shall conform to the test specification as defined in clause 9.5.2. |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.5.2 Tests specification | The file with tests specification shall be a CSV (Comma-Separated Values) file encoded in UTF-8. The delimiter character used in the file shall be ';', the quote character (if needed) '"' and the end of line one "\n". The first line of the file shall be the following: Id;Requirement;Category;Test The rest of the lines ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.6 Ontology examples | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.6.1 The examples directory | The examples directory of the SAREF project version directory should contain at least one file. Files contained in the examples directory are called the example documents of the SAREF project version. Their goal is to illustrate how the ontology can be used in practice. Every example document shall have the extension .... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.6.2 Prefixes declaration | The present clauses specifies every example document, taking as example an example document example12.ttl. The example document example12.ttl may contain a list of prefix declarations. If a prefix declaration has a prefix in the first column of Table 2, then the namespace shall be equal to the content of the second col... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.6.3 The example declaration | If the SAREF project is SAREF core version vx.y.z, then the Dataset IRI of the example document example12.ttl shall be: https://saref.etsi.org/core/vx.y.z/example/example12# If the SAREF project is a SAREF extension with acronym ABCD and version vx.y.z, then the Dataset IRI of the example document example12.ttl shall b... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.6.4 OWL Profile, Consistency, and Satisfiability of Classes | The dataset in the example document, when augmented with an ontology declaration that imports all the ontologies the example conforms to, shall satisfy the OWL2 DL profile [2], with the exception that unknown datatypes may be used, and shall be consistent [4]. ETSI ETSI TS 103 673 V1.2.1 (2024-01) 35 |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.7 Ontology documentation | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.7.1 The documentation directory | The documentation directory of the SAREF project version directory should contain at least one file. Files contained in the documentation directory are called the documentation sources of the SAREF project version. Their goal is to provide human-readable documentation for the ontology and how it can be used in practice... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.7.2 The documentation/diagrams directory | The documentation directory of the ETSI SAREF project version directory should contain exactly one directory named diagrams, with the ontology diagrams to help the users understand the ontology conceptualization at a glance, or at least, in an easier and more comprehensive way than navigating through the individual ont... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 9.8 Vocabularies | The vocabularies directory of the SAREF project version directory should contain at least one file. Files contained in the vocabularies directory are called the vocabulary documents of the SAREF project version. Their goal is to group definitions that conform to one or more reference ontology patterns. Every vocabulary... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 10.1 Directory structure | The present clause specifies how SAREF reference ontology patterns are documented and specified. Directories contained in the patterns directory of a SAREF project version repository, or in the dedicated repository saref-patterns on the ETSI Forge, are called the SAREF reference ontology patterns. Their aim is to help ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 10.2 Documentation | The reference ontology pattern directory should contain some documentation for the pattern. In particular a README.md file and some diagrams referred to in the README.md file. |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 10.3 Ontological definition | A reference ontology pattern directory should contain a file pattern.ttl, that contains the sources of the ontological definition for this pattern. This document is called the ontological definition of the pattern. The vocabulary document shall conform to clauses 9.4.2 to 9.4.5, with the following substitutions: a) Ins... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 10.4 SHACL specification | A reference ontology pattern directory may contain a turtle document shapes.ttl, that defines a set of SHACL shapes for this pattern. This document is called the SHACL specification of the pattern. Clauses 9.4.6 and 9.8 specify which ontologies shall conform to the SHACL specification of the pattern. |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 10.5 Chowlk definition | A reference ontology pattern directory may contain a file chowlk.xml, that contains the sources of a diagrams library. This document is called the Chowlk definition of the pattern. Users may import the Chowlk definition of a pattern in a diagram editor to illustrate ontologies that use this pattern. ETSI ETSI TS 103 67... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 1 Scope | The present document specifies flexible and extensible data structures for Lawful Disclosure for use in combination with existing handover interface standards, e.g. ETSI TS 103 120 [i.1] or ETSI TS 103 462 [i.2]. Data structures are not limited to telecommunication-specific data. |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 2 References | |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 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... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 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... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 3 Definition of terms, symbols and abbreviations | |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 3.1 Terms | For the purposes of the present document, the following terms apply: Communication Service Provider (CSP): service provider who may be required to disclose data Law Enforcement Agency (LEA): organization entitled to request disclosure of data |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 3.2 Symbols | Void. |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CSP Communication Service Provider JSON JavaScript Object Notation JWA JSON Web Algorithms JWS JSON Web Signature LEA Law Enforcement Agency URL Uniform Resource Locator UTF Unicode Transformation Format UUID Universally Unique Identifier |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 4 Overview | |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 4.1 Lawful Disclosure | Lawful Disclosure is the process by which a law enforcement agency requests and receives data from an obligated service provider. A formal definition of Lawful Disclosure (or the related terms "Retained Data" or "Stored Data") is not given in the present document but can be found in any relevant applicable regulations.... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 4.2 Nature of the data | The present document considers the handover of "snapshot" information i.e. information which is created relating to a given moment in time. Snapshot information is information that can be collected, delivered and is then complete. The present document does not apply to ongoing streams of information. The type and natur... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 4.3 Structure of data | The present document provides a mechanism for formatting and encoding the results of a Lawful Disclosure request in JSON (see clause 5). The present document provides a means for the CSP to describe the structure of the data through the composition or extension of a catalogue of simple standardized data structures ("en... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 4.4 CSP-defined information | Where practical, it is helpful for the data to be structured using fully standardized structures. However, in some places the format of data can change, or it can be different for different providers. In general, where a service is based on heavily standardized practices (e.g. traditional telephony) then the data forma... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 4.5 Handover and reference model | The present document does not specify any handover interface. Instead, it only specifies data structures for use in other handover interfaces defined in other specifications, including but not limited to: • ETSI TS 103 120 [i.1]. • ETSI TS 103 462 [i.2]. Normative instructions on how data structures from the present do... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 4.6 Assurance of material (e.g. for use in court) | The present document supports external techniques for assurance of material to help its use as part of legal proceedings. Implementations may choose to digitally sign the JSON-encoded messages for security and assurance purposes. If used, the procedure described in Annex C shall be followed. |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5 Response Model | |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.1 Overview | The present document describes how a CSP may encode the results of a Lawful Disclosure request as a Response document. A Response document consists of the elements shown in Table 5.1-1. ETSI ETSI TS 103 705 V1.5.1 (2025-11) 9 Table 5.1-1: Response elements Field Cardinality Description Reference recordSetDescription 1 ... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2 recordSetDescription | |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2.1 Overview | The recordSetDescription provides information related to the Response that is necessary for the LEA to interpret the data being returned by the CSP. It consists of the elements shown in Table 5.2.1-1. Table 5.2.1-1: recordSetDescription elements Field Cardinality Description Reference etsiSchemaId 1 ID of the ETSI JSON... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2.2 etsiSchemaId | Contains the JSON schema ID of the ETSI schema against which the Response was generated i.e. the value of the "$id" field in the ETSI Response Schema (see clause 6.2). This value shall take the following form, with the placeholder value {version} replaced with the version of the schema as determined by the rules in cla... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2.3 etsiSpecificationVersion | Contains the version number of the present document against which the Response was generated. NOTE: Implementers should be aware that the etsiSpecificationVersion value may change independently of the schemaId value e.g. if there are changes to the prose of the present document but no changes to the ETSI schema. |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2.4 cspName | Contains a value that identifies the CSP that generated the Response. The choice of value is out of scope of the present document, but it is recommended to choose a value which is guaranteed to be sufficiently unique for the LEA to unambiguously identify the CSP (e.g. a domain name). ETSI ETSI TS 103 705 V1.5.1 (2025-1... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2.5 cspSchemaId | Contains a value which matches the "cspSchemaID" field in the CSP Record Schema which defines the valid set of records that may appear in the recordSet (see clause 6.2.4). |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2.6 cspSchemaVersion | Contains the version number assigned by the CSP to the CSP Record Schema identified by the cspSchemaId (see clauses 5.2.5 and 6.2.4). Shall follow the rules and encoding set out in clause 6.3. |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2.7 resultSetId | Contains a value which uniquely identifies the Response between a given CSP and LEA. Unless otherwise agreed between CSP and LEA, this shall be given as a UUIDv4 [4] chosen by the CSP at the point in time when the Response is created. |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2.8 requestReference | Contains a value which uniquely and unambiguously identifies the original disclosure request against which the Response was created. If the Response is being carried according to ETSI TS 103 120 [i.1], then it is recommended that the format and value are as indicated in Annex B. In all other cases, the format and conte... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.2.9 created | Contains a timestamp indicating when the Response was generated. Shall be given in QualifiedMicrosecondDateTime format according to ETSI TS 103 280 [1], clause 6.5. |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.3 recordSet | |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.3.1 Overview | The recordSet element consists of a list of record structures. Each record has the minimum information in it as in Table 5.3.1-1. Table 5.3.1-1: Record elements Field Cardinality Description Reference id 1 Unique identifier of the record within the recordSet. Clause 5.3.2 type 1 Identifies the type of the record. Claus... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.3.2 id | Provides a unique identifier for the record within the recordSet. The format and value may be chosen by the CSP, subject to the requirement that each id value in a given recordSet shall occur once and only once. The id value may be used by the Pointer entity as a way of relating two records in a recordSet together (see... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.3.3 type | The type field contains a value which indicates the type of the record. Shall be given as a JSON reference to the schema definition that defines the type. This in turn shall match one of the allowed values set out in the CSP Record Schema (see clause 6.2.4). ETSI ETSI TS 103 705 V1.5.1 (2025-11) 11 |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 5.4 Pointers/relationships | To facilitate the definition of flat reusable structures, the present document provides a Pointer entity (see clause A.1) to allow a record in a recordSet to refer to data in another record in the same recordSet for extra information or to indicate a relationship. |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6 Schema requirements | |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6.1 Overview | Clause 6 sets out the means by which the present document can be used to meet the requirements in clauses 4.3 and 4.4; namely that CSPs have the ability to describe their own data while also providing sufficient description of that data to allow the LEA to make sense of it. To achieve this, each CSP is required to defi... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6.2 Schema structure | |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6.2.1 General | The following JSON schema files are supplied via the ETSI TC LI Forge repository at: • https://forge.etsi.org/rep/li/schemas-definitions/-/tree/spec/103705/1.5.1/103705?ref_type=tags Table 6.2.1-1: Schema files provided with the present document File Provides Description response.schema.json ETSI Response Schema Verifi... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6.2.2 ETSI Response Schema | The Response document shall conform to the ETSI Response Schema (which includes conformance with CSP Record Schema, see clause 6.2.4), which verifies that the structure is as described in clause 5. Each schema document in the CSP schema shall follow the requirements set out in clause 6. |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6.2.3 ETSI Types Schema | The ETSI Types Schema provides a set of standard definitions that may be used as either records (i.e. referred to directly by the CSP Record Schema) or as components of a CSP-defined Record or Type schema. CSPs are encouraged to use types defined in the ETSI Types schema whenever possible (see clause 6.5). |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6.2.4 CSP Record Schema | The CSP Schema shall contain a CSP Record Schema which defines all records which may appear as part of a recordSet from that CSP. The Record Schema shall contain the following mandatory fields. ETSI ETSI TS 103 705 V1.5.1 (2025-11) 13 Table 6.2.4-1: CSP Record Schema Field Description Value $id JSON schema identifier, ... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6.2.5 CSP Supplementary Schema | The CSP Schema may contain one or more CSP Supplementary Schemas that provide additional definitions referred to from the CSP Record Schema. All definitions in a CSP Supplementary Schema shall follow the requirements given clauses 6.4 and 6.5. When choosing the value for the JSON schema ID ("$id") of a CSP Supplementar... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6.3 Versioning | The ETSI Response Schema, ETSI Types schema and the CSP Schema(s) shall each have a version assigned to it of the form <major>.<minor>.<patch>. The version number of the ETSI Response Schema and ETSI Types schema are assigned by ETSI, while the CSP Schema version is assigned by the CSP responsible for the schema. The m... |
45a87bb41ab51b3dfcae6078f30b2b36 | 103 705 | 6.4 Schema requirements |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.