Esileht»Infoteenus

35 INFOTEHNOLOOGIA

Tagasi peagrupi juurde

Uued standardid


ISO/IEC 26554:2018
Hind 151,90 EUR
Information technology -- Software and systems engineering -- Tools and methods for product line testing
This document, within the methods and tools of testing for software and systems product lines: — provides the terms and definitions specific to testing for software and systems product lines; — defines processes performed during product line testing (those processes are described in terms of purpose, inputs, tasks and outcomes); — defines method capabilities to support the defined tasks of each process; and — defines tool capabilities to automate/semi-automate tasks or defined method capabilities. This document concerns processes and capabilities of testing methods and tools for a family of products, not for a single system.

ISO 7779:2018
Hind 151,90 EUR
Acoustics -- Measurement of airborne noise emitted by information technology and telecommunications equipment
This document specifies procedures for measuring and reporting the noise emission of information technology and telecommunications equipment. NOTE 1 This document is considered part of a noise test code (see 3.1.2) for this type of equipment and is based on basic noise emission standards (see 3.1.1) ISO 3741, ISO 3744, ISO 3745, ISO 9295 and ISO 11201. The basic emission quantity is the A-weighted sound power level, which can be used for comparing equipment of the same type but from different manufacturers, or for comparing different equipment. Three basic noise emission standards for determination of the sound power levels are specified in this document in order to avoid undue restriction on existing facilities and experience. ISO 3741 specifies comparison measurements in a reverberation test room; ISO 3744 and ISO 3745 specify measurements in an essentially free field over a reflecting plane. Any of these three basic noise emission standards can be selected and used exclusively in accordance with this document when determining sound power levels of a machine. The A-weighted sound power level is supplemented by the A-weighted emission sound pressure level determined at the operator position or the bystander positions, based on basic noise emission standard ISO 11201. This sound pressure level is not a level of noise immission at a work station (see 3.2.12), but it can assist in identifying any potential problems that could cause annoyance, activity interference or hearing damage to operators and bystanders. Methods for determination of whether the noise emission includes prominent discrete tones are specified in Annex D. This document is suitable for type tests and provides methods for manufacturers and testing laboratories to obtain comparable results. The methods specified in this document allow the determination of noise emission levels for a functional unit (see 3.1.4) tested individually. The procedures apply to equipment which emits broad-band noise, narrow-band noise and noise which contains discrete-frequency components, or impulsive noise. The sound power and emission sound pressure levels obtained can serve noise emission declaration and comparison purposes (see ISO 9296[3]). NOTE 2 The sound power levels and emission sound pressure levels obtained are not intended to be considered as installation noise immission levels; however, they can be used for installation planning (see ECMA TR/27[11]). If sound power levels obtained are determined for a number of functional units of the same production series, they can be used to determine a statistical value for that production series (see ISO 9296[3]).
Asendab ISO 7779:2010

ISO 16407-2:2018
Hind 49,50 EUR
Electronic fee collection -- Evaluation of equipment for conformity to ISO 17575-1 -- Part 2: Abstract test suite
The ISO 16407 series provides a suite of tests in order to assess the Front End (FE) and Back End (BE) behaviour compliancy towards the requirements listed in ISO 17575‑1. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific test purposes defined in ISO 16407‑1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).
Asendab ISO/TS 16407-2:2012

ISO 16410-2:2018
Hind 49,50 EUR
Electronic fee collection -- Evaluation of equipment for conformity to ISO 17575-3 -- Part 2: Abstract test suite
The ISO 16410 series provides a suite of tests in order to assess the Front End (FE) and Back End (BE) behaviour's compliancy towards the requirements listed in ISO 17575‑3. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific test purposes defined in ISO 16410‑1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).
Asendab ISO/TS 16410-2:2012

ISO/IEC TS 19570:2018
Hind 134,84 EUR
Programming Languages -- Technical Specification for C++ Extensions for Parallelism
This document describes requirements for implementations of an interface that computer programs written in the C++ programming language can use to invoke algorithms with parallel execution. The algorithms described by this document are realizable across a broad class of computer architectures. There is a possibility of a subset of the functionality described by this document being standardized in a future version of C++, but it is not currently part of any C++ standard. There is a possibility of some of the functionality in this document never being standardized, or of it being standardized in a substantially changed form. The goal of this document is to build widespread existing practice for parallelism in the C++ programming language. It gives advice on extensions to those vendors who wish to provide them.
Asendab ISO/IEC TS 19570:2015

ISO/IEC 21878:2018
Hind 100,70 EUR
Information technology -- Security techniques -- Security guidelines for design and implementation of virtualized servers
This document specifies security guidelines for the design and implementation of VSs. Design considerations focusing on identifying and mitigating risks, and implementation recommendations with respect to typical VSs are covered in this document. This document is not applicable to: (see also 5.3.2 Exclusions) — desktop, OS, network, and storage virtualization; and — vendor attestation. This document is intended to benefit any organization using and/or providing VSs.

ISO/IEC 14888-3:2018
Hind 168,97 EUR
IT Security techniques -- Digital signatures with appendix -- Part 3: Discrete logarithm based mechanisms
This document specifies digital signature mechanisms with appendix whose security is based on the discrete logarithm problem. This document provides — a general description of a digital signature with appendix mechanism, and — a variety of mechanisms that provide digital signatures with appendix. For each mechanism, this document specifies — the process of generating a pair of keys, — the process of producing signatures, and — the process of verifying signatures. Annex A defines object identifiers assigned to the digital signature mechanisms specified in this document, and defines algorithm parameter structures. Annex B defines conversion functions of FE2I, I2FE, FE2BS, BS2I, I2BS, I2OS and OS2I used in this document. Annex D defines how to generate DSA domain parameters.
Asendab ISO/IEC 14888-3:2016

ISO/IEC 30118-1:2018
Hind 168,97 EUR
Information technology -- Open Connectivity Foundation (OCF) Specification -- Part 1: Core specification
The OCF specifications are divided into two sets of documents: — Core Specification documents: The Core Specification documents specify the Framework, i.e., the OCF core architecture, interfaces, protocols and services to enable OCF profiles implementation for Internet of Things (IoT) usages and ecosystems. — Vertical Profiles Specification documents: The Vertical Profiles Specification documents specify the OCF profiles to enable IoT usages for different market segments such as smart home, industrial, healthcare, and automotive. The Application Profiles Specification is built upon the interfaces and network security of the OCF core architecture defined in the Core Specification. This document is the OCF Core specification which specifies the Framework and core architecture.

ISO/IEC 30118-2:2018
Hind 168,97 EUR
Information technology -- Open Connectivity Foundation (OCF) Specification -- Part 2: Security specification
This specification defines security objectives, philosophy, resources and mechanism that impacts OCF base layers of the OCF Core Specification. The OCF Core Specification contains informative security content. The OCF Security specification contains security normative content and may contain informative content related to the OCF base or other OCF specifications.

ISO/IEC 30118-3:2018
Hind 151,90 EUR
Information technology -- Open Connectivity Foundation (OCF) Specification -- Part 3: Bridging specification
This document specifies a framework for translation between OCF devices and other ecosystems, and specifies the behaviour of a translator that exposes AllJoyn producer applications to OCF clients, and exposes OCF servers to AllJoyn consumer applications. Translation of specific AllJoyn interfaces to or from specific OCF resource types is left to other specifications. Translation of protocols other than AllJoyn is left to a future version of this specification. This document provides generic requirements that apply unless overridden by a more specific document.

ISO/IEC 30118-4:2018
Hind 168,97 EUR
Information technology -- Open Connectivity Foundation (OCF) Specification -- Part 4: Resource type specification
The OCF Resource Type Specification specifies the Resources that have been defined by OCF that may be exposed by an OCF Device. Application profile device specifications (for example those created for Smart Home or Healthcare) specify device types appropriate to the profile; such specifications use Resource Type definitions from this document. This specification is built on top of the OCF Core Specification. The OCF Core Specification specifies the OCF Framework that enables the implementation of profiles for IoT usages and ecosystems. The OCF Core Framework is scalable to support simple devices (constrained device) and more capable devices (smart device).

ISO/IEC 30118-5:2018
Hind 75,10 EUR
Information technology -- Open Connectivity Foundation (OCF) Specification -- Part 5: Smart home device specification
The OCF Smart Home Device specification is an Application Profile specification. The Smart Home Device specification specifies the Smart Home devices. The Smart Home Device definitions use Resource definitions from the OCF Resource Type Specification. The Smart Home Device Specification is built on top of the Core Specification. The Core Specification specifies the core architecture, interfaces protocols and services to enable the implementation of profiles for IoT usages and ecosystems. The Core specification also defines the main architectural components of network connectivity, discovery, data transmission, device & service management and ID & security. The core architecture is scalable to support simple devices (constrained devices) and more capable devices (smart devices).

ISO/IEC 30118-6:2018
Hind 168,97 EUR
Information technology -- Open Connectivity Foundation (OCF) Specification -- Part 6: Resource to AllJoyn interface mapping specification
The OCF Resource to AllJoyn Interface Mapping specification ("this specification") provides detailed mapping information to provide equivalency between AllJoyn defined Interfaces and OCF defined Resources, This specification provides mapping for Device Types (AllJoyn to/from OCF), identifies equivalent OCF Resources for both mandatory and optional AllJoyn interfaces and for each interface defines the detailed Property by Property mapping using OCF defined extensions to JSON schema to programmatically define the mappings.

ISO/IEC 14496-14:2018
Hind 75,10 EUR
Information technology -- Coding of audio-visual objects -- Part 14: MP4 file format
This document defines the MP4 file format, as derived from the ISO Base Media File format.
Asendab ISO/IEC 14496-14:2003; ISO/IEC 14496-14:2003/Cor 1:2006; ISO/IEC 14496-14:2003/Amd 1:2010

Asendatud või tühistatud standardid


Puuduvad

Kavandite arvamusküsitlus


prEN 50980-1:2018
Tähtaeg 3.02.2019
Remote alcohol monitoring devices - Test methods and performance requirements - Part 1: Instruments for assessment programmes
The purpose of this new standard is to specify test methods and performance requirements for remotely monitored breath alcohol testing devices. It covers remote alcohol monitoring devices intended to be used by participants in programmes designed to monitor abstinence or restricted alcohol consumption.
Keel: Inglise

prEN IEC 61804-3:2018
Identne IEC 61804-3:201X; prEN IEC 61804-3:2018
Tähtaeg 3.02.2019
Function Blocks (FB) for process control and Electronic Device Description Language (EDDL) - Part 3: EDDL syntax and semantics
This part of IEC 61804 specifies the Electronic Device Description Language (EDDL) technology, which enables the integration of real product details using the tools of the engineering life cycle. This part of IEC 61804 specifies EDDL as a generic language for describing the properties of automation system components. EDDL is capable of describing • device parameters and their dependencies; • device functions, for example, simulation mode, calibration; • graphical representations, for example, menus; • interactions with control devices; • graphical representations: – enhanced user interface, – graphing system; • persistent data store. EDDL is used to create Electronic Device Description (EDD) for e.g. concrete devices, common usable profiles or libraries. This EDD is used with appropriate tools to generate an interpretative code to support parameter handling, operation, and monitoring of automation system components such as remote I/Os, controllers, sensors, and programmable controllers. Tool implementation is outside the scope of this standard. This part of IEC 61804 specifies the semantic and lexical structure in a syntax-independent manner. A specific syntax is defined in Annex A, but it is possible to use the semantic model also with different syntaxes. Part 4 of IEC 61804 specifies EDD interpretation for EDD applications and EDDs to support EDD interoperability. Part 5 of IEC 61804 specifies the EDDL Builtin library and provides the profiles of the various fieldbuses.
Keel: Inglise

prEN IEC 61804-5:2018
Identne IEC 61804-5:201X; prEN IEC 61804-5:2018
Tähtaeg 3.02.2019
Function blocks (FB) for process control and electronic device description language (EDDL) - Part 5: EDDL Builtin library
This part of IEC 61804 specifies the EDDL Builtin library and provides the profiles of the various fieldbuses.
Keel: Inglise

prEN IEC 61804-4:2018
Identne IEC 61804-4:201X; prEN IEC 61804-4:2018
Tähtaeg 3.02.2019
Function blocks (FB) for process control and electronic device description language (EDDL) - Part 4: EDD interpretation
This part of IEC 61804 specifies EDD interpretation for EDD applications and EDDs to support EDD interoperability. This document is intended to ensure that field device developers use the EDDL constructs consistently and that the EDD applications have the same interpretations of the EDD. It supplements the EDDL specification to promote EDDL application interoperability and improve EDD portability between EDDL applications.
Keel: Inglise

prEN 12896-4
Identne prEN 12896-4
Tähtaeg 3.02.2019
Public transport - Reference data model - Part 4: Operations monitoring and control
The data modules dedicated to cover most functions of the domain Operations Monitoring and Control will be specified, in particular: vehicle detecting and monitoring, events & control actions, messaging. This part will take into account SIRI and align with SIRI as far as possible. The following transport modes will be considered: bus, metro, tramway, trolleybus, ferry, coach, long distance rail. Particular attention will be drawn to the data model structure and methodology: the data model will be described in UML, in a modular form in order to facilitate the understanding and use of the model. The model will take into account a range of extension requests formulated by users, but also, in order to guarantee a coherence of the overall model (Part 1 to 8), of the domains modelled in Parts 1 to 3: Public transport - Reference data model - Part 1: Common Concepts, describing concepts shared by the different functional domains Public transport - Reference data model - Part 2: Public Transport Network, describing routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places. Public transport - Reference data model - Part 3: Timing Information and Vehicle Scheduling, describing runtimes, vehicle journeys, day type-related vehicle schedules.
Keel: Inglise

prEN 12896-5
Identne prEN 12896-5
Tähtaeg 3.02.2019
Public transport - Reference data model - Part 5: Fare management
1.1 General Scope of the Standard The main objective of the present standard is to present the Reference Data Model for Public Transport, based on: -the Reference Data Model, EN 12896, known as Transmodel V5.1; -EN 28701:2012, Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication. incorporating the requirements of -EN 15531-1 to -3 and CEN/TS 15531-4 and -5: Service interface for real-time information relating to public transport operations (SIRI); -CEN/TS 16614-1 and 2: Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation. Particular attention is drawn to the data model structure and methodology: -the data model is described in a modular form in order to facilitate the understanding and the use of the model; -the data model is entirely described in UML. The following functional domains are considered: -Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places. -Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules) -Passenger Information (planned and real-time) -Fare Management (fare structure, sales, validation, control) -Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions -Driver Management: -Driver Scheduling (day-type related driver schedules), -Rostering (ordering of driver duties into sequences according to some chosen methods), -Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance). -Management Information and Statistics (including data dedicated to service performance indicators). The data modules dedicated to cover most functions of the above domains will be specified. Several concepts are shared by the different functional domains. This data domain is called "Common Concepts". 1.2 Functional Domain Description The different functional domains (enumerated above) taken into account in the present standard, and of which the data have been represented as the reference model, are described in EN 12896-1:2016 "Public Transport Reference Data Model - Part 1: Common Concepts". 1.3 Particular Scope of this Document The present European Standard entitled "Reference Data Model for Public Transport - Part 5: Fare Management" addresses Fare Information for Public Transport and incorporates the following data packages: -Fare Structure -Access Right Assignment -Fare Pricing -Sales Description -Sales Transaction -Fare Roles -Validation and Control -Explicit Frames for Fares This document itself is composed of the following parts: - Main document (normative) representing the data model for the concepts shared by the different fare domains covered by Transmodel, - Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions, - Annex B (normative), providing a complement to the "Common Concepts" domain, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model. - Annex C (informative), indicating the data model evolutions from previous versions of Transmodel (EN 12896:2016).
Keel: Inglise

prEN 12896-6
Identne prEN 12896-6
Tähtaeg 3.02.2019
Public transport - Reference data model - Part 6: Passenger information
1.1 General scope of the standard The main objective of the present document is to present the Reference Data Model for Public Transport, based on: - the Reference Data Model, EN12896, known as Transmodel V5.1; - EN 28701:2012, Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication, incorporating the requirements of: - EN 15531-1 to −3 and CEN/TS 15531-4 and −5: Service interface for real-time information relating to public transport operations (SIRI); - CEN/TS 16614-1 and -2: Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation. Particular attention is drawn to the data model structure and methodology: - the data model is described in a modular form in order to facilitate the understanding and the use of the model; - the data model is entirely described in UML. The following functional domains are considered: - Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places; - Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules); - Passenger Information (planned and real-time); - Fare Management (fare structure, sales, validation, control); - Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions; - Driver Management: - Driver Scheduling (day-type related driver schedules), - Rostering (ordering of driver duties into sequences according to some chosen methods), - Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance); - Management Information and Statistics (including data dedicated to service performance indicators). The data modules dedicated to cover most functions of the above domains will be specified. Several concepts are shared by the different functional domains. This data domain is called "Common Concepts". 1.2 Functional Domain Description The different functional domains (enumerated above) taken into account in the present standard, and of which the data have been represented as the reference model, are described in "Public Transport Reference Data Model - Part 1: Common Concepts". 1.3 Particular Scope of this document The present European Standard entitled "Reference Data Model for Public Transport - Part 6: Passenger Information" incorporates the following main data packages: - Trip Description; - Passenger Queries. This document itself is composed of the following parts: - Main document (normative) representing the data model for the concepts shared by the different fare domains covered by Transmodel; - Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions; - Annex B (normative), providing a complement to EN12896-1:2016, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model; - Annex C (informative), indicating the data model evolutions; - Annex D (informative), indicating the high-level equivalences of the example passenger information functional requests to the capabilities of other standards; - Annex E (informative), providing an example set of commonly found passenger information functional requests and data dictionary for the elements used in the examples.
Keel: Inglise

prEN 12896-8
Identne prEN 12896-8
Tähtaeg 3.02.2019
Public transport - Reference data model - Part 8 : Management information & statistics
The data model dedicated to cover a wide range of use cases of the domain Management Information & Statistics (in particuar a subset of use cases described by the project OpRa – Operational Raw Data) will be specified, in particular: data used for statistics and registered data from which service quality indicators may be derived. The following transport modes will be considered: bus, metro, tramway, trolleybus, ferry, coach, long distance rail. Particular attention will be drawn to the data model structure and methodology: the data model will be described in UML, in a modular form in order to facilitate the understanding and use of the model. The model will take into account a range of extension requests formulated by users, but also, in order to guarantee a coherence of the overall model (Part 1 to 8), of the domains modelled in Parts 1 to 3: Public transport - Reference data model - Part 1: Common Concepts, describing concepts shared by the different functional domains Public transport - Reference data model - Part 2: Public Transport Network, describing routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places. Public transport - Reference data model - Part 3: Timing Information and Vehicle Scheduling, describing runtimes, vehicle journeys, day type-related vehicle schedules.
Keel: Inglise

prEN IEC 62443-3-3:2018
Tähtaeg 3.02.2019
Industrial communication networks - Network and system security - Part 3-3: System security requirements and security levels
This part of the IEC 62443 series provides detailed technical control system requirements (SRs) associated with the seven foundational requirements (FRs) described in IEC 62443-1-1 including defining the requirements for control system capability security levels, SL-C(control system). These requirements would be used by various members of the industrial automation and control system (IACS) community along with the defined zones and conduits for the system under consideration (SuC) while developing the appropriate control system target SL, SL-T(control system), for a specific asset. As defined in IEC 62443-1-1 there are a total of seven FRs: a) Identification and authentication control (IAC), b) Use control (UC), c) System integrity (SI), d) Data confidentiality (DC), e) Restricted data flow (RDF), f) Timely response to events (TRE), and g) Resource availability (RA). These seven requirements are the foundation for control system capability SLs, SL-C (control system). Defining security capability at the control system level is the goal and objective of this standard as opposed to target SLs, SL-T, or achieved SLs, SL-A, which are out of scope. See IEC 62443-2-1 for an equivalent set of non-technical, program-related, capability SRs necessary for fully achieving a control system target SL.
Keel: Inglise

prEN 62443-2-4
Tähtaeg 3.02.2019
Security for industrial automation and control systems - Part 2-4: Security program requirements for IACS service providers
This part of IEC 62443 specifies a comprehensive set of requirements for security capabilities for IACS service providers that they can offer to the asset owner during integration and maintenance activities of an Automation Solution. Because not all requirements apply to all industry groups and organizations, Subclause 4.1.4 provides for the development of Profiles that allow for the subsetting of these requirements. Profiles are used to adapt this document to specific environments, including environments not based on an IACS. NOTE 1 The term “Automation Solution” is used as a proper noun (and therefore capitalized) in this part of IEC 62443 to prevent confusion with other uses of this term. Collectively, the security capabilities offered by an IACS service provider are referred to as its Security Program. In a related specification, IEC 62443-2-1 describes requirements for the Security Management System of the asset owner. NOTE 2 In general, these security capabilities are policy, procedure, practice and personnel related. Figure 2 illustrates how the integration and maintenance capabilities relate to the IACS and the control system product that is integrated into the Automation Solution. Some of these capabilities reference security measures defined in IEC 62443-3-3 that the service provider must ensure are supported in the Automation Solution (either included in the control system product or separately added to the Automation Solution).
Keel: Inglise

prEN 62443-2-4/prA1
Identne IEC 62443-2-4:2015/A1:2017; prEN 62443-2-4/prA1
Tähtaeg 3.02.2019
Security for industrial automation and control systems - Part 2-4: Security program requirements for IACS service providers
Amendment for prEN 62443-2-4
Keel: Inglise

prEN IEC 62680-1-5:2018
Identne IEC 62680-1-5:201X; prEN IEC 62680-1-5:2018
Tähtaeg 3.02.2019
Universal serial bus interfaces for data and power - Part 1-5: Common components - USB Audio 3.0 Device Class Definition
The Audio Device Class Definition applies to all devices or functions embedded in composite devices that are used to manipulate audio, voice, and sound-related functionality. This includes both audio data (analog and digital) and the functionality that is used to directly control the audio environment, such as Volume and Tone Control. The Audio Device Class does not include functionality to operate transport mechanisms that are related to the reproduction of audio data, such as tape transport mechanisms or CD-ROM drive control.
Keel: Inglise

prEN IEC 62680-1-6:2018
Identne IEC 62680-1-6:201X; prEN IEC 62680-1-6:2018
Tähtaeg 3.02.2019
Universal serial bus interfaces for data and power - Part 1-6: Common components - USB Audio 3.0 Device Class Definition Basic Functions
The USB Audio Device Class Definition for Basic Audio Functions applies to all USB Audio Functions that are based on the Universal Serial Bus Device Class Definition for Audio Devices Release 3.0. It defines baseline audio functionality for all ADC 3.0 compliant Hosts and Devices.
Keel: Inglise

prEN IEC 62680-1-7:2018
Identne IEC 62680-1-7:201X; prEN IEC 62680-1-7:2018
Tähtaeg 3.02.2019
Universal serial bus interfaces for data and power - Part 1-7: Common components - USB Audio 3.0 Device Class Definition Data Formats
The intention of this document is to describe in detail all the Audio Data Formats that are supported by the Audio Device Class. This document is considered an integral part of the Audio Device Class Specification, although subsequent revisions of this document are independent of the revision evolution of the main USB Audio Specification. This is to easily accommodate the addition of new Audio Data Formats without impeding the core USB Audio Specification.
Keel: Inglise

prEN IEC 62680-1-8:2018
Identne IEC 62680-1-8:201X; prEN IEC 62680-1-8:2018
Tähtaeg 3.02.2019
Universal serial bus interfaces for data and power - Part 1-8: Common components - USB Audio 3.0 Device Class Definition Terminal Types
The Audio Device Class Definition applies to all devices or functions embedded in composite devices. All audio signals inside an audio function start at an Input Terminal, pass through some Units, and leave the function through an Output Terminal. Units can manipulate the signal in various ways. Terminals represent the connections of the function to the outside world. As part of the Terminal descriptor, the wTerminalType field specifies the vendor’s suggested use of the Terminal. For example, a pair of speakers is a more suitable target for music output than a telephone line. This feature allows a vendor to ensure that applications use the device in a consistent and meaningful way.
Keel: Inglise

prEVS-ISO/IEC 19944
Tähtaeg 3.02.2019
INFOTEHNOLOOGIA Pilvtöötlus Pilvteenused ja -seadmed: andmevoog, andmekategooriad ja andmete kasutamine
See dokument — laiendab senist ISO/IEC 17788 ja ISO/IEC 17789 pilvtöötluse sõnavara ja etalonarhitektuuri, kirjeldamaks pilvteenuseid kasutavaid seadmeid sisaldavat ökosüsteemi — kirjeldab seadmetes ja pilvtöötluse ökosüsteemis kulgevate andmete tüüpe, — kirjeldab ühendatud seadmete toimet pilvtöötluse ökosüsteemis kulgevatele andmetele , — kirjeldab andmevooge pilvteenuste, pilvteenuseklientide ja pilvteenusekasutajate vahel, — esitab alusmõisteid, sealhulgas andmete taksonoomiat, — piiritleb läbi pilvteenuseklientide seadmete ja pilvteenuste kulgevate andmete kategooriad See dokument on kohaldatav eelkõige pilvteenusetarnijaile, pilvteenuseklientidele ja pilvteenuste kasutajaile, aga ka igale seadmete ja pilvteenuste vaheliste andmevoogude õiguslikes, poliitilistes, tehnilistes või muudes aspektides osalevale isikule või organisatsioonile.
ISO/IEC 19944:2017 - extends the existing cloud computing vocabulary and reference architecture in ISO/IEC 17788 and ISO/IEC 17789 to describe an ecosystem involving devices using cloud services, - describes the various types of data flowing within the devices and cloud computing ecosystem, - describes the impact of connected devices on the data that flow within the cloud computing ecosystem, - describes flows of data between cloud services, cloud service customers and cloud service users, - provides foundational concepts, including a data taxonomy, and - identifies the categories of data that flow across the cloud service customer devices and cloud services. ISO/IEC 19944:2017 is applicable primarily to cloud service providers, cloud service customers and cloud service users, but also to any person or organization involved in legal, policy, technical or other implications of data flows between devices and cloud services.

Keel: Inglise