Ämnesområden: Informationsvetenskap
Kommittébeteckning: SIS/TK 115 (Språk och terminologi)
Källa: ISO
Svarsdatum: den 24 okt 2018
Se merSe mindre

The component metadata lifecycle needs a comprehensive infrastructure with systems that cooperate well together. To enable this level of cooperation this document provides in depth descriptions and definitions of what CMDI records, components and their representations in XML look like.

The scope of this document is to describe these XML representations, which enable the flexible construction of interoperable metadata schemas suitable for, but not limited to, describing language resources. The metadata schemas based on these representations can be used to describe resources at different levels of granularity (e.g. descriptions on the collection level or on the level of individual resources).

In ISO 24622-1:2015 the component metadata model has been standardized. This document is compliant with ISO 24622-1:2015, and also extends and constrains it at various places (see also the red parts in the UML class diagram below):

— support for attributes on both components and elements is added,

— a profile is limited to one root component, and

— an element always belongs to a specific component.


Kommittébeteckning: SIS/TK 544 (Fysiskt informationsbevarande)
Källa: ISO
Svarsdatum: den 21 nov 2018
Se merSe mindre

This standard provides a context for emergency planning, response and recovery for collections in light of other existing plans. This document will provide responders and other stakeholders with an outline for planning, responding and recovering. This standard does not address the causes of an incident, but the consequences and wider impacts. This standard establishes requirements for all types of archival and library collections.

It outlines a cycle for developing, exercising and reviewing a plan, and how to present a plan. It aims to encourage responders in developing their capabilities in emergency preparedness and touches on some elements of response and recovery, where relevant, by highlighting indicators of good practice.

It is not intended to be an operations manual as there is no single approach that will meet the needs of every site, nor is there one single set of organizational arrangements that will be appropriate to each and every type of emergency.