Informationsteknik, kontorsutrustning

ISO 11783 specifies a serial data network for control and communications on forestry or agricultural tractors and mounted, semi-mounted, towed or self-propelled implements. Its purpose is to standardize the method and format of transfer of data between sensor, actuators, control elements, and information-storage and - display units, whether mounted on, or part of, the tractor or implement. The purpose of ISO 11783 is to provide an open interconnect system for electronic systems used by agriculture and forestry equipment. This part of ISO 11783 defines and describes the network’s 250 kbit/s, twisted, non-shielded, quad-cable physical layer and an alternative cable and architecture named Cost Optimized Physical Layer based on a 250 kbit/s, un-shielded, twisted pair cable network layer which is fully backward compatible to twisted quad based SOBUS machines and devices.

Where not differently specified, requirements are valid for both twisted quad and COPL physical layers.

This International Standard provides specifications for intelligent transport systems (ITS) station

management to be compliant with the ITS station reference architecture.

Local ITS station management protocols are specified by means of management processes, and data

that are exchanged between the station management entity and

— the ITS Applications entity above the API,

— the Security entity, and

— the various communication protocol layers

    — access

    — networking & transport

    — facilities

of the ITS station architecture specified in ISO 21217:2014 and illustrated in Figure 1.

This International Standard provides specifications for intelligent transport systems (ITS) station management to be compliant with the ITS station reference architecture.

Remote ITS station management is specified by means of protocol data units (PDUs) and procedures of the "Remote ITS Station Management Protocol" (RSMP) related to managed objects in an ITS station communication unit. Distinction is made between managed entities (management clients) and managing entities (management servers).

This document specifies the management service access points, i.e. the service access points of

— the interfaces between the ITS-S management entity and

    — the ITS-S access layer (MI-SAP),

    — the ITS-S networking & transport layer (MN-SAP),

    — the ITS-S facilities layer (MF-SAP);

— the interfaces between the ITS-S security entity and

    — the ITS-S access layer,

    — the ITS-S networking & transport layer,

    — the ITS-S facilities layer;

— the interface between the ITS-S management entity and the ITS-S security entity (MS-SAP)

— the interfaces between the ITS-S application entity and

    — the ITS-S management entity (MA-SAP),

    — the ITS-S security entity (SA-SAP).

This International Standard provides specifications for secure ITS station-internal management communications.

The RFID tag location, tag data content and functional requirements have been developed for application on the main line railway networks. Other networks (such as metro) may apply this standard but are outside of its scope.

This document contains:

— a description of the RFID tag installation location;

— a description of the RFID tag data content;

— a description of the functional requirements in relation to the RFID tag track side reading performance.

This document specifies ergonomic principles which apply to the user requirements, design, and procurement of the physical equipment and environment which contribute to the context of use of interactive systems.

In particular, the general principles and requirements specified in this part of ISO 9241 apply to the standards specifying functional design of furniture and equipment constituting the environment.

The principles as specified in this document utilize ergonomic knowledge (from the disciplines anthropometry, acoustics, vision, thermal environments, indoor air quality, mechanical vibrations, etc.) to design and evaluate environments that enhance usability (effectiveness, efficiency and satisfaction), accessibility, performance and well-being for organised and non-organised use of interactive systems.

The intended users of this document include:

— developers of systems, products and services;

— public and corporate purchasers;

— occupational health and safety professionals;

— architects and interior designers;

— human resource professionals;

— usability/ergonomics/human factors professionals.

This part of International Standard 81346, published jointly by IEC and ISO establishes classification schemes with defined object classes and their associated letter codes primarily intended for use in reference designations and for designation of generic types.

The classification schemes are applicable for objects in all technical disciplines and all branches of industry.

This document describes the core concepts of ISO/IEC 20000, identifying how the different parts support ISO/IEC 20000-1:2018 as well as the relationships between ISO/IEC 20000 and other International Standards and Technical Reports. This document also includes the terminology used in all parts of ISO/IEC 20000, so that organizations and individuals can interpret the concepts correctly.

This document can be used by:

a) organizations using ISO/IEC 20000-10 definitions for ISO/IEC 20000-1 and other parts;
b) organizations considering using any document and looking for guidance on how to use the different parts of ISO/IEC 20000 to achieve their goal;
c) organizations that wish to understand how ISO/IEC 20000 can be used in combination with other International Standards;
d) practitioners, auditors and other parties who wish to gain an understanding of ISO/IEC 20000.

1 This document specifies the form and establishes the interpretation of programs expressed in the base Fortran language. The purpose of this document is to promote portability, reliability, maintainability, and efficient execution of Fortran programs for use on a variety of computing systems.

2 This document specifies
     • the forms that a program written in the Fortran language may take,
     • the rules for interpreting the meaning of a program and its data,
     • the form of the input data to be processed by such a program, and
     • the form of the output data resulting from the use of such a program.

3 Except where stated otherwise, requirements and prohibitions specified by this document apply to programs rather than processors.

4 This document does not specify
     • the mechanism by which programs are transformed for use on computing systems
     • the operations required for setup and control of the use of programs on computing systems,
     • the method of transcription of programs or their input or output data to or from a storage medium,
     • the program and processor behavior when this document fails to establish an interpretation except for the processor detection and reporting requirements in items (2) to (10) of 4.2,
     • the maximum number of images, or the size or complexity of a program and its data that will exceed the capacity of any particular computing system or the capability of a particular processor,
     • the mechanism for determining the number of images of a program,
     • the physical properties of an image or the relationship between images and the computational elements of a computing system,
     • the physical properties of the representation of quantities and the method of rounding, approximating, or computing numeric values on a particular processor, except by reference to ISO/IEC/IEEE 60559:2011 under conditions specified in Clause 17,
     • the physical properties of input/output records, files, and units, or
     • the physical properties and implementation of storage.

Change third sentence as follows:

A total of eight different block ciphers are defined.

Change Table 1 as follows:

This International Standard defines the integration of KNX protocol implementations on top of Internet Protocol (IP) networks, called KNXnet/IP. It describes a standard protocol for KNX devices connected to an IP network, called KNXnet/IP devices. The IP network acts as a fast (compared to KNX Twisted Pair transmission speed) backbone in KNX installations.

Widespread deployment of data networks using the Internet Protocol (IP) presents an opportunity to expand building control communication beyond the local KNX control bus, providing:

— remote configuration;

— remote operation (including control and annunciation);

— fast interface from LAN to KNX and vice versa;

— WAN connection between KNX systems (where an installed KNX system is at least one line);

— an interface to super ordinate building management and energy management systems.

A KNXnet/IP system contains at least these elements:

— one EIB line with up to 64 (255) EIB devices;
OR
one KNX segment (KNX-TP1, KNX-RF, KNX-PL110);

— a KNX-to-IP network connection device (called KNXnet/IP server);

and typically additional

• software for remote functions residing on e.g. a workstation (may be data base application, BACnet

Building Management System, browser, etc.).

Figure 1 shows a typical scenario where a KNXnet/IP client (e.g. running ETS) accesses multiple KNX installed systems or KNX subnetworks via an IP network. The KNXnet/IP client may access one or more KNXnet/IP servers at a time. For subnetwork, routing server-to-server communication is possible.

This part of ISO/IEC 29167 defines the Rabin-Montgomery (RAMON) crypto suite for the ISO/IEC 18000 air interfaces standards for radio frequency identification (RFID) devices. Its purpose is to provide a common crypto suite for security for RFID devices that may be referred by ISO committees for air interface standards and application standards.

This part of ISO/IEC 29167 specifies a crypto suite for Rabin-Montgomery (RAMON) for air interface for RFID systems. The crypto suite is defined in alignment with existing air interfaces.

This part of ISO/IEC 29167 defines various authentication methods and methods of use for the cipher. A Tag and an Interrogator may support one, a subset, or all of the specified options, clearly stating what is supported.

This International Standard specifies a methodology for the evaluation of non-deterministic or deterministic random bit generators intended to be used for cryptographic applications. The guidelines given herein shall enable the vendor of an RBG to submit well-defined claims of security to an evaluation authority and shall enable an evaluator or a tester, for instance a validation authority, to test, certify or reject these claims.

This International Standard is implementation-agnostic. Hence, it offers no specific guidance on design and implementation decisions for random bit generators. However, design and implementation issues influence the evaluation of an RBG under document, for instance because it requires the use of a stochastic model of the random source and because any such model must be supported by technical arguments pertaining to the design of the device at hand.

Random Bit Generators as evaluated under the present International Standard will aim to output bit strings that appear evenly distributed. Depending on the distribution of random numbers required by the consuming application, however, it is worth noting that additional steps may have to be taken (and may well be critical to security) by the consuming application to transform the random bit strings produced by the RBG into random numbers of a distribution suitable to the application requirements. Such subsequent transformations are outside the scope of evaluations performed under this document.

This document defines guidelines, formats, definitions, and approaches for use when producing a mapping document that defines how industry practices map to/from the ISO/IEC 19770 family of standards.

This edition is focused solely on mappings to/from both the second edition of ISO/IEC 19770-1 that was published in 2012, or the third edition of ISO/IEC 19770-1 that was published in 2017. However, the title of this document is deliberately more general as it is expected that future editions of this standard will address other editions of 19770-1 and possibly also include mapping frameworks related to other members of the 19770 family of standards.

In this document where reference is made to "ISO/IEC 19770-1" without the specification of an edition number or a publication year, then the text applies to all editions of ISO/IEC 19770-1.

This document defines the conceptual schema for the description of referencing by coordinates. It describes the minimum data required to define coordinate reference systems. This document supports the definition of:

— spatial coordinate reference systems where coordinate values do not change with time. The system may:

     — be geodetic and apply on a national or regional basis, or

     — apply locally such as for a building or construction site, or

     — apply locally to an image or image sensor;

     — be referenced to a moving platform such as a car, a ship, an aircraft or a spacecraft. Such a coordinate reference system may be related to a second coordinate reference system which is referenced to the Earth through a transformation that includes a time element;

— spatial coordinate reference systems in which coordinate values of points on or near the surface of the earth change with time due to tectonic plate motion or other crustal deformation. Such dynamic systems include time evolution, however they remain spatial in nature;

— parametric coordinate reference systems which use a non-spatial parameter that varies monotonically with height or depth;

— temporal coordinate reference systems which use dateTime, temporal count or temporal measure quantities that vary monotonically with time;

— mixed spatial, parametric or temporal coordinate reference systems.

The definition of a coordinate reference system does not change with time, although in some cases some of the defining parameters may include a time element. The coordinate values within a dynamic and in a temporal coordinate reference system may change with time.

This document also describes the conceptual schema for defining the information required to describe operations that change coordinate values.

In addition to the minimum data required for the definition of the coordinate reference system or coordinate operation, it allows additional descriptive information - coordinate reference system metadata - to be provided.

This document is applicable to producers and users of geographic information. Although it is applicable to digital geographic data, its principles can be extended to many other forms of spatial data such as maps, charts and text documents.

This document defines GIML(Gesture Interface Markup Language). It is an XML-based markup language. It is aimed to describe gestures for interacting with ICT products, systems and services in a well-formed format. The syntax and the structure of GIML are described in this document. The XML schema of GIML is presented in

Annex A. Some examples of GIML is listed in Annex B.