UNE EN ISO 21597-1:2020
Information container for linked document delivery - Exchange specification - Part 1: Container (ISO 21597-1:2020) (Endorsed by Asociación Española de Normalización in June of 2020.)
Contenedor de información para extracción de datos (ICDD). Especificación de intercambio. Parte 1: Contenedor (ISO 21597-1:2020) (Ratificada por la Asociación Española de Normalización en junio de 2020.)
| Označení normy: | UNE EN ISO 21597-1:2020 |
| Počet stran: | 51 |
| Vydáno: | 2020-06-01 |
| Status: | Norma |
UNE EN ISO 21597-1:2020
This standard defines a generic container format to store a delivered set of documents, including a means to link otherwise disconnected data. In this context, the term document refers to any digital resource that provides information about the built or natural environment, including, but not limited to, any 2D or 3D representation or model, spreadsheet, image or text-based digital resource. This standard is suitable for all parties dealing with information concerning the built environment, where there is a need to exchange multiple documents and their interrelationships, either as part of the process or as contracted deliverables. The format is intended to use resources either included in the container (such as documents) or referenced remotely (such as web resources). A key feature is that the container can include information about the relationships between the documents. Relevant use-cases reflect the need for information exchange during the entire life cycle of any built asset and may include, but is not limited to, the handover of 1. a published bidding package, 2. required project deliverables at a specific project stage, 3. shared information as background or for further development, or 4. published approval packages. The container format includes a header file and optional link files that define relationships by including references to the documents, or to elements within them. The header file uniquely identifies the container and its contractual or collaborative intention. This information is defined using the RDF and OWL semantic web standards. The header file, along with any additional RDF/OWL files or resources, forms a suite that may be directly queried by software. Where it includes link references into the content of documents that don t support standardized querying mechanisms, their resolution may depend on third party interpreters. Alternatively, the link references may be interpreted by the recipient applications, or reviewed interactively by the recipient. The format can also be used to deliver multiple versions of the same document with the ability to convey the known differences or priority between them.
