Informationsteknik, kontorsutrustning

This Part of this International Standard defines structures and data elements for biometric information records (BIRs).

This Part of this International Standard defines the concept of a domain of use to establish the applicability of a standard or specification that complies with CBEFF requirements.

This Part of this International Standard defines the concept of a CBEFF patron format, which is a published BIR format specification that complies with CBEFF requirements, specified by a CBEFF patron.

This Part of this International Standard defines the abstract values (and associated semantics) of a set of CBEFF data elements to be used in the definition of CBEFF patron formats.

This Part of this International Standard specifies the use of CBEFF data elements by a CBEFF patron to define the content and encoding of a standard biometric header (SBH) to be included in a biometric information record (i.e., the definition of a CBEFF patron format).

This Part of this International Standard provides the means for identification of the formats of the BDBs in a BIR, but the standardization and interoperability of BDB formats is not in the scope of this Part of this International Standard. It also provides a means (the security block) for BIRs to carry information about the encryption of a BDB in the BIR and about integrity mechanisms applied to the BIR as a whole; the structure and content of security blocks is not in the scope of this Part of this International Standard. Further, the specification of encryption mechanisms for BDBs and of integrity mechanisms for BIRs is not in the scope of this Part of this International Standard.

This Part of this International Standard specifies transformations from one CBEFF patron format to a different CBEFF patron format.

The encoding of the abstract values of CBEFF data elements to be used in the specification of CBEFF patron formats is not in the scope of this Part of this International Standard.

Protection of the privacy of individuals from inappropriate dissemination and use of biometric data is not in the scope of this International Standard, but may be subject to national regulation.

ISO/IEC 19785-2 specifies the procedures for the operation of the Biometric Registration Authority (which is identified on the webpage www.iso.org/mara). ISO/IEC 19785-3 specifies several patron formats for which ISO/IEC JTC 1 SC 37 is the CBEFF patron. ISO/IEC 19785-4 specifies several Security Block formats for which ISO/IEC JTC 1 SC 37 is the CBEFF patron.

The proposed standard will specify an interface of a BioAPI Java framework and BioAPI Java BSP, which will mirror the corresponding components, specified in ISO/IEC 30106-1. The semantic equivalent of this standard is maintained in this document.

The proposed standard will specify an interface of a BioAPI C# framework and BioAPI C# BSP which will mirror the corresponding components specified in ISO/IEC 30106-1.The semantic equivalence of this standard will be maintained with ISO/IEC 30106-2 (Java implementation). In spite of the differences in actual parameters passed between functions, the names and interface structure are the same.

This document is intended to apply to the user interface design of the information and communication (ICT) devices which have a function for setting the appropriate language environment when an end-user wants to initiate its operation.

This document specifies mechanisms to choose between the keyboard groups specified in other ISO/IEC 9995 parts, national keyboards standards, or other keyboard definitions.

These mechanisms primarily become useful when the stipulated marking on the key top can be displayed by technology such as OLED.

This International Standard addresses:

— requirements for planning, executing and reporting the influence of user interaction on biometric system performance based on scenario test methodologies, considering three kinds of factors:

o Factors related to the design, position or condition of the capture device

o Factors depending on users and user attributes

o Factors depending on the interaction of users with the biometric system

— specifications for the definition, establishment and measurement of conditions needed for evaluation, including that relating to equipment,

— requirements for establishing a reference evaluation condition and target evaluation condition(s) to compare the influence of user interaction factors,

— a specification of the biometric evaluation including requirements for test population, test protocols, data to record, test results, and

— procedures for carrying out the overall evaluation.

This standard does not

— determine which parameters should be analysed for a specific biometric modality. This is currently covered in 19795:2007[1],

— specify requirements to perform a vulnerability analysis modifying user interaction influence factors, or

— include procedures for performing usability testing.

It is important to differentiate between "usability testing" and "user interaction influence in performance". Usability testing relates to "the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use" (ISO/IEC 9241-11:1998[3]). Usability testing involves the measurement of "how usable" a specific system or product is. Standards covering usability testing include to ISO/IEC TR 25060:2010.

This amendment modifies certain parts of the ISO/IEC 14496-22:2019 "Open Font Format" (4th edition) toclarify implementation details for SVG-based color font technology and implement other changes and updates.

This document specifies the conformance and reference software implementing the normative clauses of ISO/IEC 23093-3. The information provided is applicable for determining the reference software modules available for ISO/IEC 23093-3, understanding the functionality of the available reference software modules, and utilizing the available reference software modules.

Furthermore, this part of ISO/IEC 23093 provides means for conformance testing, i.e. bit-streams – XML descriptions – that conform or do not conform to the normative clauses of ISO/IEC 23093-3 and informative descriptions thereof.

This document provides fundamental terminology for blockchain and distributed ledger technologies.

The Network-Based Media Processing framework defines the interfaces including both data formats and

APIs among the entities connected through the digital networks for media processing. Users can access

and configure their operations remotely for efficient intelligent processing. It describes and manages

workflows to be applied to the media data. This process includes uploading of media data to the network,

instantiation of the media processing tasks, and configuration of the tasks. The framework enables

dynamic creation of media processing pipelines, access of processed media data and metadata in realtime

or in a deferred way. The media and metadata formats used between the Media Source, Workflow

Manager and Media Processing Entities in a media processing pipeline are also within the scope.

This European Standard (EN 16157 series) specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.

The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.

This European Standard is applicable to:

— Traffic and travel information which is of relevance to road networks (non-urban and urban),

— Public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service),

— Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).

This European Standard establishes specifications for data exchange between any two instances of the following actors:

— Traffic Information Centres (TICs),

— Traffic Control Centres (TCCs),

— Service Providers (SPs),

Use of this European Standard may be applicable for use by other actors.

This European Standard series covers, at least, the following types of informational content:

— Road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment,

— Operator initiated actions,

— Road traffic measurement data, status data, and travel time data,

— Travel information relevant to road users, including weather and environmental information,

— Road traffic management information and instructions relating to use of the road network.

This part of the CEN/TS 16157 series specifies the informational structures, relationships, roles, attributes and associated data types required for publishing variable message sign information within the Datex II framework. This is specified in two publications, a DATEX II VMS Table Publication sub-model and a VMS Publication sub-model, which are part of the DATEX II platform independent model, but this part excludes those elements that relate to:

— location information which are specified in EN 16157-2,

— common information elements, which are specified in EN 16157-7,

— situation information which are specified in EN 16157-3.

The VMS Table Publication supports the occasional exchange of tables containing generally static reference information about deployed VMS which enable subsequent efficient references to be made to pre-defined static information relating to those VMS. The VMS Publication supports the exchange of the graphic and textual content of one or several VMS plus any status information on device configuration that aid the comprehension of the informational content. This content is potentially subject to rapid change.

These publications are not intended to support the control or configuration of VMS equipment. Each is part of the DATEX II platform independent model.

The ISO/IEC 21122 standard, also known under the term JPEG XS, specifies a low-latency, lightweight image compression system offering compression tools for high-speed, ultra-low online compression of images and image sequences.

This document contains the reference software of JPEG XS. Its purpose is to act as a guideline for implementations and as a reference for conformance testing. It has been successfully compiled and tested on Linux and WindowsTM operating systems at the time of writing.

This document specifies the JPEG Pleno Framework architecture and its instantiation via a generic file format for storage of plenoptic modalities as well as associated metadata descriptors.

This document specifies a coded codestream format for storage of light field modalities as well as associated metadata descriptors that are light field modality specific. This document also provides also non-normative information on the encoding tools.

This part of ISO 12967 specifies the fundamental characteristics of the information model to be implemented by a specific architectural layer (i.e. the service architecture) of the information system to provide a comprehensive and integrated storage of the common enterprise data and to support the fundamental business processes of the healthcare organization, as defined in ISO 12967-1.

The information model is specified without any explicit or implicit assumption on the physical technologies, tools or solutions to be adopted for its physical implementation in the various target scenarios. The specification is nevertheless formal, complete and non-ambiguous enough to allow implementers to derive an efficient design of the system in the specific technological environment that will be selected for the physical implementation.

This specification does not aim at representing a fixed, complete, specification of all possible data that can be necessary for any requirement of any healthcare enterprise. It specifies only a set of characteristics, in terms of overall organization and individual information objects, identified as fundamental and common to all healthcare organizations, and that is satisfied by the information model implemented by the service architecture.

Preserving consistency with the provisions of this part of ISO 12967, physical implementations allow extensions to the standard information model in order to support additional and local requirements. Extensions include both the definition of additional attributes in the objects of the standard model, and the implementation of entirely new objects.

Also, this standard specification is extensible over time according to the evolution of the applicable standardization initiatives.

The specification of extensions is carried out according to the methodology defined in ISO 12967-1:2019, Clause 7, "Methodology for extensions".

HISA specifies fundamental requirements for 'information infrastructure' and healthcare specific ‘service architecture’.

This part of ISO 12967 specifies the fundamental characteristics of the computational model to be implemented by a specific architectural layer of the information system (i.e. the service architecture) to provide a comprehensive and integrated interface to the common enterprise information and to support the fundamental business processes of the healthcare organization, as defined in ISO 12967-1. The computational model is specified without any explicit or implicit assumption about the physical technologies, tools or solutions to be adopted for its physical implementation in the various target scenarios. The specification is nevertheless formal, complete and non-ambiguous enough to allow implementers to derive an efficient design of the system in the specific technological environment which will be selected for the physical implementation.

The computational model provides the basis for ensuring consistency between different engineering and technology specifications (including programming languages and communication mechanisms) since they must be consistent with the same computational object model. This consistency allows open inter-working and portability of components in the resulting implementation.

This specification does not aim at representing a fixed, complete, specification of all possible interfaces that may be necessary for any requirement of any healthcare enterprise. It specifies only a set of characteristics – in terms of overall organization and individual computational objects, identified as fundamental and common to all healthcare organizations, and that are satisfied by the computational model implemented by the service architecture.

Preserving consistency with the provisions of this part of ISO 12967, physical implementations shall allow extensions to the standard computational model in order to support additional and local requirements. Extensions shall include both the definition of additional properties in the objects of the standard model and the implementation of entirely new objects.

Also, this standard specification shall be extendable over time according to the evolution of the applicable standardization initiatives. The specification of extensions shall be carried out according to the methodology defined in Clause 7 of ISO 12967-1:2019, which identifies a set of healthcare common information services, describing their need and the methodology through which they will be used.

These information services are only the minimal set identifiable according to the needs of the healthcare enterprise, and constituting the service architecture (i.e. the integration platform) to serve as the basis for healthcare applications, e.g. EHR or patient administration.

This international standard (IS) establishes the Reference Standards Portfolio for the Clinical Imaging Domain (as defined in Section 4).

The Clinical Imaging RSP lists the principle health information technology (HIT) standards that should form the basis of implementing and deploying interoperable applications. These standards have been selected as being mature, fit for purpose and the most appropriate to clinical imaging.

The Clinical Imaging RSP includes a description of the domain, a normative list of standards, and an informative framework for mapping the standards to example deployment use cases.

This work reflects the experience and learning of the international community in developing interoperability standards in clinical imaging domain, including representatives of:

•DICOM (Digital Imaging and Communication in Medicine)

•IHE Radiology (Integrating the Healthcare Enterprise)

•ISO/TC215 Health Informatics.

The primary target audience for this document is policy makers (governmental or organizational), regulators, project planners and HIT managers. The Clinical Imaging RSP will also be of interest to other stakeholders such as equipment and HIT vendors, clinical and health information management (HIM) professionals and standards developers.

The intended usage of this document is to inform decisions about selecting the standards that will form the basis of integration projects in geographic regions or healthcare organizations. For example:

•What standards to use for capturing/encoding/exchanging certain types of information

•What standards to use for interfaces between the devices and information systems that supportinformation capture, management, exchange, processing and use

•What standards to use for specific use cases/deployment scenarios

The selected standards, and/or corresponding RSP sections, may be useful when drafting project specifications.

It should be noted, however, that achieving full interoperability within a given environment or set of systems is a large endeavor of which the selection of underlying standards is an important component, but just one component. Additional guidance may be found in the Process section of the TR on IHE Global Standards Adoption [2].

This RSP was developed based on concepts and methodology described in the Healthcare Informatics – Reference Standards Portfolio (RSP): Development Framework. RSPs are an evolution of past work, such as that done by the Board of Directors of the American Medical Informatics Association [2].

This part of ISO/IEC 15408 establishes the general concepts and principles of IT security evaluation and specifies the general model of evaluation given by various parts of the standard which in its entirety is meant to be used as the basis for evaluation of security properties of IT products.

Part one provides an overview of all parts of ISO/IEC 15408 standard. It describes the various parts of the standard; defines the terms and abbreviations to be used in all parts of the standard; establishes the core concept of a Target of Evaluation (TOE); the evaluation context and describes the audience to which the evaluation criteria are addressed. An introduction to the basic security concepts necessary for evaluation of IT products is given.

It defines the various operations by which the functional and assurance components given in ISO/IEC 15408-2 and ISO/IEC 15408-3 may be tailored through the use of permitted operations.

The key concepts of protection profiles (PP), packages of security requirements and the topic of conformance are specified and the consequences of evaluation, evaluation results are described. This part of ISO/IEC 15408 gives guidelines for the specification of Security Targets (ST) and provides a description of the organization of components throughout the model. General information about the evaluation methodology are given in ISO/IEC 18045 and the scope of evaluation schemes is provided.

This part of ISO/IEC 15408 defines the required structure and content of security functional components for the purpose of security evaluation. It includes a catalogue of functional components that will meet the common security functionality requirements of many IT products.