Other IT standards

Specification that describes the business processes and requirements for the ordering process.

The ordering process is used to agree on delivery and payment of goods or services between the supplier and the customer.
This document describes the process how to reach agreement. 

The design of Test Assertions (TAs) associated with a specification or standard - referred to in this charter as target specification - has the following recognized benefits: (i) it improves the quality of this specification during its design, and (ii) it reduces the lead time necessary to create a test suite for this specification.
 
A test assertion (TA), also sometimes defined as test specification, is understood in this charter with the following general meaning: A TA is an independent, complete, testable statement for requirements in the specification. A TA always refers to an item under test (IUT), which is assumed to implement all or parts of the target specification, so that this IUT is concerned with the requirements addressed by the TA. This reference is either implicit or explicit if it is necessary that the TA identifies the item under test in some unambiguous manner. A TA describes the expected output or behavior for the item under test within specific operation conditions, in a way that can be measured or tested. A TA may refer to a test harness architecture, of which a description limited to the interactions between its components and the IUT may be sufficient. Test assertions are generally different from test cases, which are more detailed and contingent to a concrete test framework: TAs are the basis to write test cases, and relate the latter to the narrative of the target specification.
 
The general objective served by this TC is to facilitate the creation and usage of test assertions by any group involved in designing a specification or standard of which software implementations are expected to be developed, with a primary focus on OASIS technical committees. The first step in achieving this is to establish a common and reusable model, metadata, methodology and representation for TAs.

The SOA Repository Artifact Model and Protocol (S-RAMP) TC defines a common data model for SOA repositories as well as an interaction protocol to facilitate the use of common tooling and sharing of data. The TC will define an ATOM binding which documents the syntax for interaction with a compliant repository for create, read, update, delete and query operations.

The OASIS Service Oriented Architecture Reference Model TC develops a reference model to encourage the continued growth of different and specialized SOA implementations whilst preserving a common layer of understanding about what SOA is.
 
The TC will:
 
-- deliver a Service Oriented Architecture Reference Model (SOA-RM) and, if it elects, ancillary materials as described under "purpose" above.
 
-- allow the commission of sub-committees to create specialized SOA models for vertical industries or technology families.
 
-- propose usage and implementation guidelines for creating specializations of the reference model, whether as a formal methodology or as best practice guidelines.

SOA End-to-End Resource Planning is a technology that optimizes deployment of services onto a SOA description of an application. The focus in EERP is on the characterization of the business characteristics of a service (called Business Quality of Service in the references listed under External Resources below), characterization and accessing the reputation of potential service providers, and Business Service-Level Agreements. See the EERP white paper approved by the committee for details and future direction.
 
The SOA-EERP Technical Committee will focus on enablers for optimization. The enablers are, for example, definitions of the framework for representing the business process service rating terms, such how to represent cost, time, value, etc. We define "optimization" as maximizing business value by enabling improved real-life eBusiness process and resource planning at both design time and run time. In particular,

• Resources are services performed by people, machines, and hardware/software applications, and represented by SOA services. Defining the qualities of such a business service will be done with metrics expressed as Business Quality of Service (BQoS). The nature of BQoS varies across industries and services.
• Business processes are optimized in order to reduce cost, improve efficiency, and otherwise improve business results. Extensions to Business Process Management Notation and execution environments such as WS-BPEL will facilitate process improvement through automatic optimization and evolution.

A major factor limiting the interoperability of telepresence systems is the lack of a standardised way to describe and negotiate the use of the multiple streams of audio and video comprising the media flows.

The CLUE WG will create specifications for SIP-based conferencing systems to enable communication of information about media streams so that a sending system, receiving system, or intermediate system can make
reasonable decisions about transmitting, selecting, and rendering media streams. This enables systems to make choices that optimise user experience.

In the context of this WG, telepresence is used in a general manner to describe systems that provide high definition, high quality audio/video enabling a "being-there" experience.

We develop standards that support the technical requirements of national and international obligations for law enforcement, including the lawful interception and retention of the communications-related data of electronic communications. Lawful Interception (LI) and Retained Data (RD) play a crucial role in helping law enforcement agencies to investigate terrorism and serious criminal activities. We have pioneered the development and maintenance of LI and RD capabilities, and its standards are being adopted around the world due to the increased efficiency and lower cost resulting from their use. Global interest in the committee’s work continues to grow, with new organizations joining in the standardization process.

We are responsible for standardization to support the development and implementation of Intelligent Transport Systems (ITS) service provision across the network, for transport networks, vehicles and transport users, including interface aspects, multiple modes of transport and interoperability between systems.

We are helping to accelerate the introduction of ITS services and applications and to maximize their benefits by developing common European standards and technical specifications to enable interoperability. TC ITS is leading the drive to achieve international standards.

We develop test specifications to test interoperability, conformance, performance and security. The methodology used is end-to-end (e2e) and includes verification of both the control and user plane. The test specifications are based on 3GPP specifications which enable network operators to test their network for services for both fixed and mobile customers.

We produce test purposes, test descriptions, and TTCN-3 test cases to enable interoperability testing of the core network elements and covering the single-network, interconnect and roaming scenarios. Use Cases and requirements specified by ETSI for Automated and Autonomic Management and Control (self- management) of Networks and Services are tested via “industry standards-anchored” Proof of Concepts (PoC) events.

This standard specifies the dimensions and location of video, audio, and tracking-control records on reference tapes for 1-in type B helical-scan video tape recorders, operating on the 525/60 monochrome or NTSC color system, as described in ANSI/SMPTE 29M.

This standard specifies test conditions, general video record system, video pole-tip locations, scanner parameters, scanner-guide locations, and the tape tension for 1-in type B helical-scan video tape reference recorders operating on the 525/60 monochrome or NTSC color systems.