Informationsteknik, kontorsutrustning

This specification contains the key requirements of a quality open source software security assurance program that establishes trust between organizations exchanging software solutions comprised of open source software.

This specification defines the C# programming language and its required library. It defines all the necessary components that are needed to implement this Suite. This Suite does not change if one or more components are updated by a new standard edition. The Suite changes only when new components are added to it and/or existing components are removed from it.

The Assessment Procedures defined in this document are intended to ensure the repeatability,
reproducibility, and objectivity of assessments against the O-TTPS. Though the primary audience for this document is the assessor, an Information Technology (IT) provider who is undergoing assessment or preparing for assessment, may also find this document useful.

ISO 17361:2017 specifies the definition of the system, classification, functions, human-machine interface (HMI) and test methods for lane departure warning systems. These are in-vehicle systems that can warn the driver of a lane departure on highways and highway-like roads. The subject system, which may utilize optical, electromagnetic, GPS or other sensor technologies, issues a warning consistent with the visible lane markings. The issuance of warnings at roadway sections having temporary or irregular lane markings (such as roadwork zones) is not within the scope of ISO 17361:2017. ISO 17361:2017 applies to passenger cars, commercial vehicles and buses. The system will not take any automatic action to prevent possible lane departures. Responsibility for the safe operation of the vehicle remains with the driver.

This document specifies the requirements for establishing, implementing, maintaining and continually improving an information security management system within the context of the organization. This document also includes requirements for the assessment and treatment of information security risks tailored to the needs of the organization. The requirements set out in this document are generic and are intended to be applicable to all organizations, regardless of type, size or nature. Excluding any of the requirements specified in Clauses 4 to 10 is not acceptable when an organization claims conformity to this document.

This document specifies the general requirements for city service platform for public health emergencies. It also specifies the requirements in terms of data, functions, security and privacy protection.

This part of ISO/IEC 29794, for any or all biometric sample types as necessary, establishes the following:
— terms and definitions that are useful in the specification and use of quality measures;
— purpose and interpretation of biometric quality scores;
— methods for developing biometric sample datasets for the purpose of quality score normalisation;
— format for exchange of quality assessment algorithm results;
— methods for aggregation of quality scores;
— methods for evaluating the efficiency of quality assessment algorithms.
The following are outside the scope of this part of ISO/IEC 29794:
— specification of minimum requirements for sample, module, or system quality scores;
— standardization of quality assessment algorithms;
— assessment of utility of biometric samples or references for human examiners.

This document gives requirements for defining format and content for library objects to support project inception, brief, design, tendering, construction, operations, use and demolition, supporting the development of information throughout the process, in connection with building information modelling
(BIM) and their organization into libraries.
This document:
— establishes requirements for defining template objects, generic objects and product objects in datadriven library and design processes;
— establishes requirements for graphical symbols and other graphic conventions for use on drawings for the built environment, giving principles and definitions for the symbolic and simplified visual presentation of objects. It also describes a rationale of symbolism which establishes rules for the
design of graphical symbols and other graphic conventions, and gives recommendations for the application of those rules and the ways in which symbolism should be used;
— covers purposes for characterizing the shape and measurement of library objects;
— covers purposes for specifying and assessing properties for library objects. It defines the information appropriate for specific uses including specification of the desired outcome (typically by designers and engineers) and the selection of identified products (typically by contractors and
subcontractors). It also gives recommendations for the application of assemblies in integrated BIM working.
This document is intended for all professionals and service providers who produce and use library objects with generic and product-specific data. This group includes, but is not limited to, product manufacturers and suppliers, library authors, designers and engineers, contractors, owners, maintainers and commissioners.

The HL7 EHR System Functional Model provides a reference list of functions that may be present in an Electronic Health Record System (EHR-S). The function list is described from a user perspective with the intent to enable
consistent expression of system functionality. This EHR-S Functional Model, through the creation of Functional Profiles for care settings, realms, services and specialties, enables a standardized description and common
understanding of functions sought or available in a given setting (e.g., intensive care, cardiology, office practice in one country or primary care in another country).

This specification describes a methodology for calculating the rate of carbon emissions for a software system; that is, its SCI score. The purpose of this score is to increase awareness and transparency of an
application's sustainability credentials. The score will help software practitioners make better, evidence-based decisions during system design, development, and deployment, that will ultimately minimize carbon emissions. A reliable, consistent, fair and comparable measure allows targets to be defined during development and progress to be tracked.

This document is part 2 of the ISO/IEC 24773 series. It contains guidance and recommendations for certification that may be used by certification or qualification bodies regarding the description of knowledge, skill and competence within their particular schemes based on ISO/IEC 24773-1:2019.
Annex A contains further explanation about the distinction between certification and professional licensure. Annex A also contains additional guidance to encourage harmonization between a certification scheme and the requirements of regulators.

This document defines the requirements for the symbology known as Aztec Code. It specifies the Aztec Code symbology characteristics including data character encodation, rules for error control encoding,
the graphical symbol structure, symbol dimensions and print quality requirements, a reference decoding algorithm, and user-selectable application parameters.

This standard establishes a normative definition of communication between personal telehealth insulin pump 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 functionality of personal telehealth insulin pump devices. In the context of personal health devices (PHDs), an insulin pump is a medical device used for the administration of insulin in the treatment of diabetes mellitus, also known as continuous subcutaneous insulin infusion (CSII) therapy. This standard provides the data modeling according to ISO/IEEE 11073-20601 and does not specify the measurement method.

1.1 Field of application
This document is applicable to a VSE and introduces the major concepts required to understand and use the ISO/IEC 29110 series. It introduces the characteristics and requirements of a VSE, and clarifies
the rationale for VSE-specific profiles, documents, profile specifications and guidelines.
The life cycle processes described in the ISO/IEC 29110 series are not intended to preclude nor discourage their use by an entity that is larger than a VSE.
1.2 Target Audience
This document is targeted both at the general audience wishing to understand the ISO/IEC 29110 series of documents, and more specifically, at users of the ISO/IEC 29110 series. It should be read first when initially exploring VSE profile documents. While there is no specific prerequisite to read this document, it will be helpful to the user in understanding the other parts.
The life cycle processes defined in the ISO/IEC 29110 series can be used by a VSE when developing, acquiring and using, as well as when creating and supplying systems, having hardware and software elements. They can be applied at any level in a systems development, software’s structure and at any stage in the life cycle. The life cycle processes defined in the ISO/IEC 29110 series are not intended to preclude or discourage the use of additional processes that a VSE finds useful.

This document defines the common terms, abbreviations and references used through the EN 9300 series of standard parts.

This document defines an ontology for city-level concepts defined using terms specified in ISO/IEC 5087-1. City-level concepts are used to represent data that is shared across multiple services and stakeholders in the city. City-level concepts are distinguished by their data being read and updated by multiple city services and stakeholders.

This document defines data structures and basic operations on property graphs. It provides capabilities for creating, accessing, querying, maintaining, and controlling property graphs and the data they comprise.
This document specifies the syntax and semantics of a data management language for specifying and modifying the structure of property graphs and collections thereof. This document provides a vehicle for portability of data definitions and manipulation among GQL-implementations.
Implementations of this document may exist in environments that also support application programming languages, end-user query facilities, and various tools for database design, data administration, and performance optimization.

This document provides the concepts and structure for standardization for georegulation in the marine space.
This document addresses the information structures related to management of legal spaces, such as the international maritime limits and boundaries, marine living and non-living resources management areas, marine conservation areas, etc. and their related rights and obligations.
This document establishes the common elements and basic schema to structure marine georegulation information system. It builds upon the common components defined in ISO 19152-1 — Generic
Conceptual Model.

This document sets out terminology and use cases for data use, sharing and exchange. This document can  be used in the development of other International Standards and in support of communications among
 diverse stakeholders and other interested parties. This document is applicable to all types of organizations (including commercial enterprises, government agencies, not-for-profit organizations).
 Users of this document can find ISO/IEC 5212 helpful in providing additional guidance during the decision-making process for the use, sharing and exchange of data.