Informationsteknik, kontorsutrustning
- +Ämnesområden
- +Informationsteknik, kontorsutrustning (17)
- Informationsteknik: allmänt (3)
- IT-säkerhet (0)
- +Kodning av information (5)
- Programspråk (1)
- Programutveckling och systemdokumentation (2)
- +Öppna system (OSI) (0)
- Nätarkitekturer (0)
- Datorgrafik (0)
- Mikroprocessorsystem (0)
- Terminalutrustning och övrig kringutrustning (0)
- Gränssnitt och anslutningsutrustning (0)
- Molnbaserade datortjänster (0)
- +Datalagringsmedier (0)
- +IT-tillämpningar (6)
- Kontorsutrustning (0)
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).
1.1 Introduction This document defines common fundamental concepts for long term archiving and retrieval of mechanical CAD information for elementary parts and assemblies. It details the "fundamentals and concepts" of EN 9300-003:2012 in the specific context of long-term archiving of CAD mechanical models. Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features. The EN 9300-1XX family is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX family. As technology matures, additional parts will be released in order to support new requirements within the aerospace community. 1.2 In scope The present part describes: - the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information; - the document structure of the EN 9300-1XX family, and the links between all these parts; - the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file; - specifications for the preservation planning of archived CAD information; - specific functions for administration and monitoring of CAD archived mechanical models; - the definition of archive information packages for CAD data. 1.3 Out of scope The following are out of scope for this part: - long-term archiving of CAD 2D drawings; - other CAD specialization disciplines, such as electrical harnesses, composite.
ISO/IEC DIS 42005 är en standard som ger vägledning för organisationer som utför konsekvensbedömningar av AI-system. Detta inkluderar individer och samhällen som kan påverkas av ett AI-system och dess avsedda och förutsedda tillämpningar.
Dokumentet innehåller överväganden för hur och när man ska utföra sådana bedömningar och vid vilka skeden av AI-systemets livscykel. Det ger också vägledning för dokumentation av konsekvensbedömningar av AI-system.
Denna standard är avsedd att användas av organisationer som utvecklar, tillhandahåller eller använder AI-system och är tillämplig på alla organisationer, oavsett storlek, typ och karaktär.
Scope:
This document provides guidance for organizations performing AI system impact assessments for individuals and societies that can be affected by an AI system and its intended and foreseeable applications. It includes considerations for how and when to perform such assessments and at what stages of the AI system lifecycle, as well as guidance for AI system impact assessment documentation. Additionally, this guidance includes how this AI system impact assessment process can be integrated into an organization’s AI risk management and AI management system. This document is intended for use by organizations developing, providing, or using AI systems. This document is applicable to any organization, regardless of size, type and nature.
This document provides guidance for organizations performing AI system impact assessments for individuals and societies that can be affected by an AI system and its intended and foreseeable applications. It includes considerations for how and when to perform such assessments and at what stages of the AI system lifecycle, as well as guidance for AI system impact assessment documentation. Additionally, this guidance includes how this AI system impact assessment process can be integrated into an organization’s AI risk management and AI management system. This document is intended for use by organizations developing, providing, or using AI systems. This document is applicable to any organization, regardless of size, type and nature.
This document contains guidelines to be used in the process of drafting requirements of cybersecurity certification schemes for sectoral ICT services and systems. It includes all steps necessary to define, implement and maintain such requirements.
L'ISO/IEC 19762:2016 provides the general terms and definitions in the field of automatic identification techniques and data entry are based on which other specialized sections in various technical fields, as well as the essential terms that must be employed by non-technical users to communicate with specialists in automatic identification and data capture techniques.
L'ISO/IEC 19762:2016 provides the general terms and definitions in the field of automatic identification techniques and data entry are based on which other specialized sections in various technical fields, as well as the essential terms that must be employed by non-technical users to communicate with specialists in automatic identification and data capture techniques.
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 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.