IT-tillämpningar
- +Ämnesområden
- +Informationsteknik, kontorsutrustning (23)
- Informationsteknik: allmänt (4)
- IT-säkerhet (1)
- +Kodning av information (1)
- Programspråk (0)
- Programutveckling och systemdokumentation (2)
- +Öppna system (OSI) (0)
- Nätarkitekturer (0)
- Datorgrafik (0)
- Mikroprocessorsystem (0)
- Terminalutrustning och övrig kringutrustning (2)
- Gränssnitt och anslutningsutrustning (2)
- Molnbaserade datortjänster (0)
- +Datalagringsmedier (1)
- +IT-tillämpningar (11)
- IT-tillämpningar: allmänt (1)
- Datorstödd design (1)
- Identifieringskort och tillhörande läsarenheter (4)
- IT-tillämpningar i kontorsarbete (0)
- IT- tillämpningar inom information, dokumentation och förlagsverksamhet (1)
- IT- tillämpningar inom finansiella system (0)
- IT- tillämpningar inom industrin (1)
- IT- tillämpningar inom transport (4)
- IT-tillämpningar inom handel (1)
- IT- tillämpningar inom bygg- och anläggningsindustri (1)
- IT-tillämpningar inom jordbruk (0)
- IT- tillämpningar inom posttjänster (0)
- IT- tillämpningar inom vetenskap (2)
- Hälso- och sjukvårdsinformatik (0)
- IT- tillämpningar inom utbildning (0)
- Internettillämpningar (0)
- IT- tillämpningar inom övriga områden (1)
- Kontorsutrustning (0)
This document specifies a standardized protocol for downloading data from the equipment control box to an in-vehicle board computer to ensure interchangeability between a vehicle and different equipment that the same vehicle can carry.
It specifies the interface connection as well as variables, records and reports which permit standardized protocol to cover applications with the greatest possible variety of equipment for performing winter maintenance and road service area maintenance.
This document is intended to be used in any sector of activity. It specifies:
— contents of command-response pairs exchanged at the interface,
— means of retrieval of data elements and data objects in the card,
— structures and contents of historical bytes to describe operating characteristics of the card,
— structures for applications and data in the card, as seen at the interface when processing commands,
— access methods to files and data in the card,
— a security architecture defining access rights to files and data in the card,
— means and mechanisms for identifying and addressing applications in the card,
— methods for secure messaging,
— access methods to the algorithms processed by the card. It does not describe these algorithms.
It does not cover the internal implementation within the card or the outside world.
This document is independent from the physical interface technology. It applies to cards accessed by one or more of the following methods: contacts, close coupling and radio frequency. If the card supports simultaneous use of more than one physical interface, the relationship between what happens on different physical interfaces is out of the scope of this document.
This document defines the structure and content of a text string implementation of the abstract model for coordinate reference systems described in ISO 19111. The string defines frequently needed types of coordinate reference systems and coordinate operations in a self-contained form that is easily readable by machines and by humans. The essence is its simplicity; as a consequence there are some constraints upon the more open content allowed in ISO 19111. To retain simplicity in the well-known text (WKT) description of coordinate reference systems and coordinate operations, the scope of this document excludes parameter grouping and pass-through coordinate operations. The text string provides a means for humans and machines to correctly and unambiguously interpret and utilise a coordinate reference system definition with look-ups or cross references only to define coordinate operation mathematics. A WKT string is not suitable for the storage of definitions of coordinate reference systems or coordinate operations because it omits metadata about the source of the data and may omit metadata about the applicability of the information.
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 can 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 can include a rate of change of the parameter. The coordinate values within a dynamic and in a temporal coordinate reference system can 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, the conceptual schema allows additional descriptive information - coordinate ...
This document describes the test methods used for conformity testing, that is methods for determining whether a driving licence can be considered to comply with the requirements of the ISO/IEC 18013 series for:
— machine readable technologies (ISO/IEC 18013-2), and
— access control, authentication and integrity validation (ISO/IEC 18013-3).
The test methods described in this document are based on specifications defined in ISO/IEC 18013-2 and ISO/IEC 18013-3 and underlying normative specifications.
This document deals with test methods specific to IDL requirements. Test methods applicable to (smart) cards in general (e.g. those specified in the ISO/IEC 10373 series) are outside the scope of this document.
Hence the purpose of this document is to:
— provide IDL implementers with requirements for conformity evaluation,
— provide IDL issuing authorities with requirements for quality assurance, and
— provide test laboratories and test tool providers with test suite requirements.
The proposed revision of ISO 16739-1:2018 focusses on additions to the data schema and reference data to further support the infrastructure domains, particularly for bridges, roads, rails, ports and waterways and common foundations, such as alignment, terrain, strata and earthworks. The scope of the proposed revision is in line with the overall scope mention of ISO 16739-1:2018 “to include data definitions for infrastructure assets over their life cycle as well”. The general scope and title of ISO 16739 being an international standard for “data sharing in the construction and facility management industries” remains valid.
This document specifies interoperable application profiles for information exchanges between toll chargers (TCs) and toll service providers (TSPs), by selecting suitable options from the base standard EN ISO 12855:2022.
This document covers:
— exchange of information between back end systems of TCs and TSPs, e.g.:
— charging related data (toll declarations, billing details, payment claims, payment announcements);
— administrative data (trust objects, EFC context data, contact details for enforcement, etc.);
— user related data (exception lists, user details, abnormal OBE information, CCC event data, user complaints);
— confirmation data.
— transfer mechanisms and supporting functions;
— semantics of data elements;
— formal definitions (Annex A) of restrictions on data types w.r.t. the ASN.1 definitions in the base standard EN ISO 12855:2022 by introducing an XML Schema Definition (XSD) for each specified profile;
— implementation conformance statement proforma (Annex B), as a basis for evaluation of implementation for conformity to this document;
— an interoperability statement proforma (Annex C), as a basis for assessment of transactional interoperability of two technical implementations;
— a web service definition (Annex D) for the use of web services as communication technology.
The implementation of the underlying back end systems and their business processes is not covered. Therefore, the following aspects are outside the scope of this document:
— details about how back end systems use the authenticator data elements of the base standard to implement security;
— how to operate compliance checking and the enforcement process;
— commercial aspects;
— definition of non-functional features such as performance indicators, acceptable fault levels, availability of interfaces of TC and TSP, and reporting requirements.
This document further explains the correspondence between the European electronic toll service (EETS) legislation and this document (Annex E).
This document describes the history of biometrics and what biometrics does, the various biometric technologies in general use today (for example, fingerprint recognition, face recognition and iris recognition) and the architecture of the systems and the system processes that allow automated
recognition using those technologies. It also provides information about the application of biometrics in various business domains such as border management, law enforcement and driver licensing. And it provides information on the societal and jurisdiction considerations that are typically taken into account in biometric systems.
Additionally, this document identifies and provides guidance on the use of the international standards that underpin the use of biometric recognition systems.
This document applies to operational and performance requirements for smart applications. It is applicable for documentation, process management, connection and data collection through humanmachine interface, IoT technologies and related systems.
This document defines methods to implement smart network applications, which are open to every participant as long as they implement the requirements defined in this document.
This document describes also a smart logbook application that can be used as a supplement to ISO 21745
and thus subject to the same security requirements as there, see annex B.
NOTE Smart applications are applications for mobile devices such as smartphones and tablets which make it possible to collect confidentially data directly on board, evaluate it and control procedures.
This standard is a profile that specifies requirements for testing biometric presentation attack detection (PAD) mechanisms on mobile devices with local biometric recognition and on biometric modules integrated into mobile devices
The profile lists requirements from ISO/IEC 30107-3 specific to mobile devices. It also establishes requirements that are not present in ISO/IEC 30107-3. For each requirement, the profile defines an Approach in PAD Tests for Mobile Devices. For some requirements, numerical values or ranges are
provided in the form of best practices.
This profile is applicable to mobile devices that operate as closed systems with no access to internal results, including mobile devices with local biometric recognition as well as biometric modules for mobile devices.
Out of the scope are the following:
— mobile devices solely with remote biometric recognition
The attacks considered in this document take place at the capture device during the presentation and collection of biometric characteristics. Any other attacks are outside the scope of this document.