Data technologies

The OASIS OData TC works to simplify the querying and sharing of data across disparate applications and multiple stakeholders for re-use in the enterprise, Cloud, and mobile devices. A REST-based protocol, OData builds on HTTP and JSON using URIs to address and access data feed resources. It enables information to be accessed from a variety of sources including (but not limited to) relational databases, file systems, content management systems, and traditional Web sites. OData provides a way to break down data silos and increase the shared value of data by creating an ecosystem in which data consumers can interoperate with data producers in a way that is far more powerful than currently possible, enabling more applications to make sense of a broader set of data. Every producer and consumer of data that participates in this ecosystem increases its overall value.

The OpenDocument Format (ODF) is an open XML-based document file format for office applications to be used for documents containing text, spreadsheets, charts, and graphical elements. The file format makes transformations to other formats simple by leveraging and reusing existing standards wherever possible. As an open standard under the stewardship of OASIS, OpenDocument also creates the possibility for new types of applications and solutions to be developed other than traditional office productivity applications.
 
The OpenDocument TC works closely together with the OASIS ODF Adoption Technical Committee which provide expertise and resources to educate the marketplace on the value of the OpenDocument OASIS Standard.
 
For more information, see the TC Charter and FAQ
 

The OSLC PROMCODE TC defines technical elements and guidelines for project management of Software Supply Chains. The OSLC PROMCODE TC will examine the work done by the PROMCODE consortium on exchanging project management information, and will modify/extend the work so that it fits the needs of the global community.
 
The OSLC PROMCODE TC will work to:

1. Define a model of project management information for SSC. A model should describe a minimum set of information and relationships commonly used by carriers and suppliers to manage software delivery.
2. Define a set of resources and their relationships following the OSLC framework as defined by the OSLC Core TC.
3. Create additional technical elements as required to support current and future scenarios for OSLC User Groups, OSLC MS-affiliated TCs, Subcommittees and the OSLC Member Section Steering Committee.
4. Leverage existing work, such as existing OSLC specifications, as much as possible. If gaps are identified, the OSLC PROMCODE TC will attempt to resolve them with other affiliated TCs prior to defining new concepts within PROMCODE.

The PROMCODE (Project Management of Contracted Delivery for Software Supply Chains) specifications advance a standard for exchanging project management information across organizational boundaries in support of Software Supply Chain (SSC) delivery. PROMCODE leverages other OSLC specifications which apply World Wide Web and Linked Data principles to enable products, services and other distributed network resources to interoperate successfully. TC members intend to request affiliation with the OASIS OSLC Member Section.
 
This TC is part of the OASIS OSLC Member Section. For more information on the OSLC PROMCODE TC, see the TC Charter.

Defining a common XML library of business documents (purchase orders, invoices, etc.).
 
The aims of the UBL TC shall be as follows:

1. To avert a crisis in electronic business caused by competing XML business-to-business document standards by choosing as a starting point an existing XML business document library as the basis for creating a new "Universal Business Language" that will be a synthesis of existing XML business document libraries.
2. To begin with xCBL 3.0 as the starting point and to develop the standard UBL library by mutually agreed-upon changes to xCBL 3.0 based on industry experience with other XML business libraries and with similar technologies such as Electronic Data Interchange.
3. To develop UBL in light of standards/specifications issued by UN/CEFACT, ISO, IEC, ITU, W3C, IETF, OASIS, and such other standards bodies and organizations as the UBL TC may deem relevant.
4. To harmonize UBL as far as practical with the ebXML specifications approved in Vienna (May 2001), with the work of the Joint Core Components initiative (a joint project of ANSI ASC X12 and the UN/EDIFACT Working Group), and with the work of other appropriate business information bodies.
5. To vest ownership of UBL in OASIS, a nonprofit corporation dedicated to the adoption of structured information standards, and to make it freely available to everyone without licensing or other fees.
6. Ultimately, to promote UBL to the status of an international standard for the conduct of XML-based electronic business.

VEL TC members are developing an interoperability standard that will enable the exchange of variability information among variant management tools and systems development tools. The goal is to enable the exchange of variability information among tools for variant management tools and systems development tools.
 
Variability is a widely used model for describing common and unique features of systems at all stages of the lifecycle. It describes the ability of artifacts to be used in different contexts by changing or customizing some characteristics of them, and those changeable characteristics are localized somewhere within the artifacts. VEL will eliminate the cost of building customized interfaces by defining a standard way for information to be exchanged among corresponding tools. Using VEL, a variant management tool will be able to read the variability from a development tool and pass configurations of selected system features to a development tool. By defining a common variability data interface that can be implemented by both the development tools and the variant management tools, VEL will enable a continuous development process for variable systems and more flexible use of tools.

The SNIA Cloud Storage Technologies Initiative (CSTI) is committed to the adoption, growth and standardization of storage in cloud infrastructures, including its data services, orchestration and management, and the promotion of portability of data in multi-cloud environments.  

This document provides a definition of a standard Data Format Description Language (DFDL). This language allows description of text, dense binary, and legacy data formats in a vendor- neutral declarative manner. DFDL is an extension to the XML Schema Description Language (XSDL).
 
DFDL is a language for describing data formats. A DFDL description allows data to be read from its native format and to be presented as an instance of an information set or indeed converted to the corresponding XML document. DFDL also allows data to be taken from an instance of an information set and written out to its native format.
 
DFDL achieves this by leveraging W3C XML Schema Definition Language (XSDL) 1.0.
 
An XML schema is written for the logical model of the data. The schema is augmented with special DFDL annotations. These annotations are used to describe the native representation of the data. This is an established approach that is already being used today in commercial systems.

ISO 14721:2012 defines the reference model for an open archival information system (OAIS). An OAIS is an archive, consisting of an organization, which may be part of a larger organization, of people and systems that has accepted the responsibility to preserve information and make it available for a designated community. It meets a set of such responsibilities as defined in this International Standard, and this allows an OAIS archive to be distinguished from other uses of the term "archive".

This standard was last reviewed and confirmed in 2018. Therefore this version remains current.

Standards for data management within and among local and distributed information systems environments. SC 32 provides enabling technologies to promote harmonization of data management facilities across sector-specific areas. Specifically, SC 32 standards include:

• reference models and frameworks for the coordination of existing and emerging standards;
• definition of data domains, data types, and data structures, and their associated semantics;
• languages, services, and protocols for persistent storage, concurrent access, concurrent update, and interchange of data;
• methods, languages, services, and protocols to structure, organize, and register metadata and other information resources associated with sharing and interoperability, including electronic commerce.

Standardization of generic biometric technologies pertaining to human beings to support interoperability and data interchange among applications and systems.

Generic human biometric standards include: common f ile frameworks; biometric application programming interfaces; biometric data interchange formats; related biometric profiles; application of evaluation criteria to biometric technologies; methodologies for performance testing and reporting and cross jurisdictional and societal aspects.

Excluded is the work in ISO/IEC JTC 1/SC 17 to apply biometric technologies to cards and personal identification. Excluded is the work in ISO/IEC JTC 1/SC 27 for biometric data protections techniques, biometric security testing, evaluations and evaluations methodologies.

SC 31 continues to deliver technically rigorous standards that meet user requirements. Looking ahead in 2016 SC31 will deliver three standards of note. One jointly developed with SC 17 will measure the quality of OCR Characters used on passports significantly improving the readability of the characters (ISO/IEC 30116). The second will establish the first quantitative method for test and evaluation of localization systems aiding the first responder community and public safety (ISO/IEC 18305). The third is a method for uniquely identifying devices and items touching the Internet of Things (ISO/IEC 29161). In 2016 SC31 will commence a joint effort with the ISO Conformance Assessment Organization (CASCO) focusing on use of an “eLabel” to replace traditional conformance markings on electronic devices.

The Cloud Auditing Data Federation Working Group (CADF) sets out to resolve major problems with the inconsistency, incompatibility, and even inability of existing cloud and service audit interfaces, technologies, and tools. The group focuses on standardizing audit events across all cloud and service providers, and on making audit events comprehensible, consistent, shareable, and merge-able.
 
The CADF Working Group develops the DMTF’s CADF standard. More than a format, the CADF standard defines a full event model anyone can use to fill in the essential data needed to certify, self-manage and self-audit application security in cloud environments.
 
CADF is part of the DMTF’s Cloud Management Initiative, which is focused on developing interoperable cloud infrastructure management standards and promoting the adoption of those standards in the industry.