The current area of work for JTC 1/SC 24 consists of:
The purpose of the OASIS ebXML Messaging Services TC is to develop and recommend technology for the transport, routing and packaging of business transactions using standard Internet technologies.
The ebXML Core TC maintains ebXML specifications transitioned from other Technical Committees. TCs eligible for maintenance by the ebXML Core TC are ebXML Messaging, ebXML CPPA, ebXML ebBP, ebXML IIC, and ebXML RegRep. The ebXML Core TC manages clarifications, modifications, and enhancements for the specifications through the OASIS standards process.
This subcommittee of SCC20 is responsible for the Artificial Intelligence Exchange and Service Tie to All Test Environments (AI-ESTATE) standard, the Testability and Diagnosability Characteristics and Metrics standard, and the Software Interface to Maintenance Information Collection and Analysis (SIMICA).
The common theme through all of the DMC standards is to provide formal specifications to support exchange and analysis of information in system test and diagnosis.
Primary activities involve the development and support of the Signal and Test Definition (STD) standard and its User Guide, together with some of the ATML standards. The ATML standards that are maintained by TAD are Test Description (IEEE 1671-1) and Instrument Description (IEEE 1671-2).
Members come from a wide range of test related disciplines, including military, aviation, commercial equipment manufacturers and users. Most of the work is carried out remotely with some face to face meetings.
The group is open to anyone with an interest in the development of test related standards.
The 2030 Smart Grid standards share the common goal of interoperability supported by interrelated and complementary technologies.
Interoperability: the capability of two or more networks, systems, devices, applications, or components to externally exchange & readily use information securely & effectively. (Std 2030).
Smart Grid: the integration of power, communications, & information technologies for an improved electric power infrastructure serving loads while providing for an ongoing evolution of end-use applications. (Std 2030).
The IEEE standards development process is open and voluntary and operates under a consensus process. The best way to participate in standards development is to attend working group (WG) meetings. All WG meetings are open meetings. Information on upcoming WG meetings can be found on the individual WG sites.
The significant growth in content delivered over IP networks, existing CDN providers are scaling up their infrastructure and many Network Service Providers and Enterprise Service Providers are deploying their own CDNs. Work in IETF focuses on meeting the need to interconnect (previously) standalone CDNs to that can interoperate and collectively behave as a single delivery infrastructure.
The goal of the Content Delivery Networks Interconnection (CDNI) WG is to allow the interconnection of separately administered CDNs in support of the end-to-end delivery of content from CSPs through multiple CDNs and ultimately to end users (via their respective User Agents). The CDNI WG aims at delivering a targeted, deployable solution in a short timeframe as needed by the industry. It is expected that the CDNI interfaces will be realised using existing IETF protocols for transport and message exchange, and using existing object notation grammars/languages for the definition of CDNI objects and semantics.
In the event that protocol extensions or new protocols are deemed necessary by the WG, the WG will recharter in mid-June 2020.
Using existing work done by the development communities of Matroska, FFV1, and FLAC, the IETF Working Group on Codec for LossLess Archiving and Realtime Transmission (CELLAR) will formalise specifications for these open and lossless formats. In order to provide authoritative, standardised specifications for users and developers, the Working Group will seek consensus throughout the process of refining and formalising these standards.
This WG fills gaps in terms of standardising open, transparent, self-descriptive, lossless formats as an important mission to be undertaken by the open source community. Work addresses concerns about the sustainability and credibility of existing specifications for the long-term use of these formats through a broader review and formalisation encourage widespread adoption.
The Working Group will seek consensus and refinements for specifications for both FFV1 and Matroska in order to provide authoritative, standardized specifications for users and developers. Backward compatibility with existing versions 0-3 of the FFV1 and Matroska specifications will be an important goal, while also reviewing and refining the current version 4 under active development.
The definition of a CMDB in the context of this specification is based on the definition described in the IT Infrastructure Library (ITIL): a database that tracks and records configuration items associated with the IT infrastructure and the relationships between them. Strictly speaking, the ITIL CMDB contains a record of the expected configuration of the IT environment, as authorized and controlled through the change management and configuration management processes. The federated CMDB in this specification extends this base definition to federate any management information that complies with the specification’s patterns, schema, and interfaces, such as the discovered actual state in addition to the expected state. Typically, an administrator selects the data to be included in a CMDB by configuring the tool that implements the CMDB.
This International Standard provides a definition of Internet of Things along with a set of terms and definitions. This International Standard is a terminology foundation for the Internet of Things.
This document describes the extent and limits of the business process within the information chain being described in this document. The class diagram of the data exchange proxy is developed such as way that it specifies all information of data exchange proxy given by the agricultural party, reusable business information entities.
Business Requirement Specification for the sourcing of Market Survey results, using the UN/CEFACT Modelling Methodology (UMM) approach and Unified Modelling Language to describe and detail the business processes and transactions involved.
A Market Research project typically initiated in a setting where the need for certain information is identified, either by a MR company, by a producer or marketer of goods or services, or by an official institution, university etc. This starts a process of more exact definition of the information needs.
The definition process is often iterative, and may involve many parties. The responsible party for the process is appointed (own organization or sub-contractor When this process is concluded, the information search process starts, i.e. the Sourcing of Marker Survey Information. This may involve different search methods. The results of the search process are evaluated.
