Informationsteknik, kontorsutrustning

This document specifies a transfer structure, syntax, and coding of messages and data formats when using high-capacity ADC media between trading partners (specifically between suppliers and recipients) and, where applicable, in support of carrier applications, such as bills of lading, and carrier sortation and tracking.

The data encoded according to this document include:

— data which can be used in the shipping, receiving and inventory of transport units;

— data which can be contained within supporting documentation, in paper or electronic form, related to unit loads or transport packages;

— data which can be used in the sortation and tracking of transport units.

This document describes the ISO/IEC 646 characters used for automatic data capture; it is not the controlling specification for data structures (e.g. CII) referenced in this International Standard.

This document does not supersede or replace any applicable safety or other marking or labelling requirements. It is intended to be applied in addition to any other mandated labelling requirements.

This standard describes methods for testing the environmental characteristics of RFID-enabled sporting goods. This document suggest methods for identifying the main use environments and related testing of environmental characteristics of sporting goods for indoor and outdoor sports with RFID and optionally additional advanced electronic devices like sensors. The addressed environmental characteristics cover the viewpoint of manufacturers including distribution and inventory management, as well as furthermore the aspects of consumer use of the actual RFID-enabled sports items. This standard defines methods to measure and evaluate the performance change of tags after environmental characteristic test.

ISO/IEC/IEEE 29119-5:2016 defines an efficient and consistent solution for Keyword-Driven Testing by:

giving an introduction to Keyword-Driven Testing;

providing a reference approach to implement Keyword-Driven Testing;

defining requirements on frameworks for Keyword-Driven Testing to enable testers to share their work items, such as test cases, test data, keywords, or complete test specifications;

defining requirements for tools that support Keyword-Driven Testing. These requirements could apply to any tool that supports the Keyword-Driven approach (e.g., test automation, test design and test management tools);

defining interfaces and a common data exchange format to ensure that tools from different vendors can exchange their data (e.g. test cases, test data and test results);

defining levels of hierarchical keywords, and advising use of hierarchical keywords. This includes describing specific types of keywords (e.g. keywords for navigation or for checking a value) and when to use "flat" structured keywords;

providing an initial list of example generic technical (low-level) keywords, such as "inputData" or "checkValue". These keywords can be used to specify test cases on a technical level, and may be combined to create business-level keywords as required.

NOTE This standard is applicable to all those who want to create keyword-driven test specifications, create corresponding frameworks, or build test automation based on keywords.

This standard specifies a set of definitions, rules, and steps for applying a non-functional size measurement method and provides guideline and examples of how to use the size measurements in software projects

This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines:

—    ASN.1 (data) types within the fields of EFC;

—    ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.

This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.

This document describes the transaction information requirements of the transactions used in the basic collaborations described in EN 17015-1 Electronic Public Procurement – Catalogue – Choreographies. For each transaction there is an overview, the transaction business requirements and the transaction information requirements model containing definitions of terms, usage descriptions and cardinality of the information elements. The document describes the following transactions: 1) Catalogue; 2) Catalogue Response 3) Pre-award Catalogue Request 4) Pre-award Catalogue 5) Shopping Cart How to claim compliance to a transaction is described in paragraph 6. How to claim conformance to a transaction is described in paragraph 6.

This document provides a set of terms and definitions needed to promote improved communication and understanding of this area. It provides a terminological foundation for big data-related standards.

This document provides a conceptual overview of the field of big data, its relationship to other technical areas and standards efforts, and the concepts ascribed to big data that are not new to big data.

This document provides guidance to assist organizations to: —   fulfil the requirements of ISO/IEC 27001 concerning actions to address information security risks; —   perform information security risk management activities, specifically information security risk assessment and treatment. This document is applicable to all organizations, regardless of type, size or sector.

This standard defines an object-oriented abstract information model to represent a PHD and the observations generated by a PHD. It specifies what information needs to be present and the relationships between the informational elements in the model. It models observations in a generic way by focusing on the information content contained in the presentation of health measurements. The modeling follows the practice of ISO/IEEE 11073-20601 [B12] where Unified Modeling Language (UML) is used to describe a set of objects and the relationship between the objects.7 Tables provide descriptions of the attributes in the objects. IEEE 11073-10101™ nomenclature terms are used to express clinical content. This standard provides guidance as to what an exchange protocols needs to communicate to properly represent health observations, but is not, in itself, sufficient to be an exchange protocol. However, the content model defined herein does have sufficient detail to help organizations validate that there is no loss of the semantic content induced by data exchanges in a protocol adhering to this standard. This standard does not define a security framework.

This document specifies the data structure and content of an interface that permits communication between position-providing device(s) and position-using device(s) enabling the position-using device(s) to obtain and unambiguously interpret position information and determine, based on a measure of the degree of reliability, whether the resulting position information meets the requirements of the intended use. A standardized interface for positioning allows the integration of reliable position information obtained from non-specific positioning technologies and is useful in various location-focused information applications, such as surveying, navigation, intelligent transportation systems (ITS), and location-based services (LBS).

This document outlines a quality model for AI systems and is an application-specific extension to the SQuaRE series. The characteristics and sub-characteristics detailed in the model provide consistent terminology for specifying, measuring and evaluating AI system quality. The characteristics and sub-characteristics detailed in the model also provide a set of quality characteristics against which stated quality requirements can be compared for completeness.

ISO 9241-161:2016 describes visual user-interface elements presented by software and provides requirements and recommendations on when and how to use them. This part of ISO 9241 is concerned with software components of interactive systems to make human-system interaction usable as far as the basic interaction aspects are concerned. ISO 9241-161:2016 provides a comprehensive list of generic visual user-interface elements, regardless of a specific input method, visualization, and platform or implementation technology. The guidance given in this part of ISO 9241 is intended to be used in conjunction with ISO 9241 guidance on dialogue techniques. It recognizes that additional elements can evolve. It also addresses derivates, compositions (assemblies) and states of user-interface elements. It gives requirements and recommendations on selection, usage and dependencies of user-interface elements and their application. It is applicable regardless of a fixed, portable or mobile interactive system. It does not provide detailed coverage of the methods and techniques required for design of user-interface elements. This part of ISO 9241 does not address implementation (e.g. graphical design of elements) and interaction details for specific input methods or technologies. It does not cover decorative user-interface elements that are intended to address solely aesthetic (hedonic) qualities in the user interface, e.g. background images. The information in this part of ISO 9241 is intended for use by those responsible for the selection and implementation of visual user-interface elements in interactive systems and for evaluating user interfaces. It is intended for use by those planning and managing platform specific aspects of user interface screen design. It also provides guidance for human factors/ergonomics and usability professionals involved in human-centred design. It addresses technical issues only to the extent necessary to allow users of this part of ISO 9241 to understand the relevance and importance of a consistent interface element usage and selection in the design process as a whole. Annex A provides a guide to selection of different visual user interface elements depending of their appropriate application.

This standard defines an object-oriented abstract information model to represent a PHD and the observations generated by a PHD. It specifies what information needs to be present and the relationships between the informational elements in the model. It models observations in a generic way by focusing on the information content contained in the presentation of health measurements. The modeling follows the practice of ISO/IEEE 11073-20601 [B12] where Unified Modeling Language (UML) is used to describe a set of objects and the relationship between the objects.7 Tables provide descriptions of the attributes in the objects. IEEE 11073-10101™ nomenclature terms are used to express clinical content. This standard provides guidance as to what an exchange protocols needs to communicate to properly represent health observations, but is not, in itself, sufficient to be an exchange protocol. However, the content model defined herein does have sufficient detail to help organizations validate that there is no loss of the semantic content induced by data exchanges in a protocol adhering to this standard. This standard does not define a security framework.

Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of communication is established in ISO/IEEE 11073-10421:2012 between personal telehealth peak expiratory flow monitor devices and compute engines (e.g. cell phones, personal computers, personal health appliances, and set top boxes) in a manner that enables plug-and-play interoperability. Appropriate portions of existing standards are leveraged, including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. The use of specific term codes, formats, and behaviors is specified in telehealth environments restricting optionality in base frameworks in favor of interoperability. A common core of communication functionality is defined for personal telehealth peak expiratory flow monitor devices.

This standard specifies the base set of Participant Key Purposes (PKPs) for the Service-oriented Device Connectivity (SDC) series of standards. PKPs are role-based sets of requirements for products in order to support safe, effective, and secure interoperability in medical IT networks at point-of-care environments such as the intensive care unit (ICU), operating room (OR) or other acute care settings. This standard specifies both product development process and technical requirements.

ISO/IEEE 11073-10471:2010 establishes a normative definition of the communication between independent living activity hubs and managers (e.g., cell phones, personal computers, personal health appliances and set top boxes) in a manner that enables plug-and-play (PnP) interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology and information models. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting ambiguity in base frameworks in favour of interoperability. ISO/IEEE 11073-10471:2010 defines a common core of communication functionality for independent living activity hubs. In this context, independent living activity hubs are defined as devices that communicate with simple situation monitors (binary sensors), normalize information received from the simple environmental monitors, and provide this normalized information to one or more managers. This information can be examined (for example) to determine when a person's activities/behaviour have deviated significantly from what is normal for them such that relevant parties can be notified. Independent living activity hubs will normalize information from the following simple situation monitors (binary sensors) for the initial release of the proposed standard: fall sensor, motion sensor, door sensor, bed/chair occupancy sensor, light switch sensor, smoke sensor, (ambient) temperature threshold sensor, personal emergency response system (PERS), and enuresis sensor (bed-wetting). ISO/IEEE 11073-10471:2010 addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers

Within the context of the ISO/IEEE 11073 family of standards for device communication, ISO/IEEE 11073-10472:2012 establishes a normative definition of communication between personal telehealth medication monitor devices and compute engines (e.g. cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. ISO/IEEE 11073-10472:2012 defines a common core of communication functionality for personal telehealth medication monitor devices.

This standard specifies a set of Participant Key Purposes (PKPs) pertaining to metric data exchange for the Service-oriented Device Connectivity (SDC) series of standards. PKPs are role-based sets of requirements for products in order to support safe, effective, and secure interoperability in medical IT networks at point-of-care environments such as the intensive care unit (ICU), operating room (OR) or other acute care settings. This standard specifies both product development process and technical requirements.

This standard establishes a normative definition of communication between personal health continuous glucose monitor (CGM) devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages work done in other ISO/IEEE 11073 standards including existing terminology, information profiles, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments, restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality of CGM devices. In this context, CGM refers to the measurement of the level of glucose in the body on a regular (typically 5 minute) basis through a sensor continuously attached to the person.