Information coding

While code lists have been used for many years, and their representations for the purposes of being validated are features of a number of constraint languages, there does not exist any standardized representation whose purposes address their interchange, documentation and management for use in any processing context. The purpose of the TC is to produce an XML interchange format for code lists. The format will support actual codes (including alternative codes and composite multi-part codes) and arbitrary related information for each code suitable for documentation and management. The format will also support the automated generation of derived code lists by providing an unambiguous specification of how a set of input code lists can be transformed into an output code list.
 
The scope of the TC is to produce a set of requirements, a W3C XML Schema, a UML model, documentation, and test examples (particularly to support the code list derivation functionality) initially based on an initial contribution to the committee, and then subsequently on evolving requirements. The creation of software to implement the work of the TC is out of scope.

The purpose of the OASIS DITA Technical Committee (TC) is to define and maintain the Darwin Information Typing Architecture (DITA) and to promote the use of the architecture for creating standard information types and domain-specific markup vocabularies.
 
DITA is specializable, which allows for the introduction of specific semantics for specific purposes without increasing the size of other DTDs, and which allows the inheritance of shared design and behavior and interchangeability with unspecialized content.

The scope of DocBook is computer hardware and software documentation. Broadly, this includes both print and online tutorial and reference documentation as well as online help, user guides, exercises and other ancillary forms of documentation.
 
This effort will deliver on the following goals:

• Evolve DocBook using the most appropriate schema languages.
• Address issues and enhancement requests that arise from experience with real-world DocBook implementations.
• Add support for features that were deferred from previous versions of DocBook.

Most requests for enhancement that are not motivated by a requirement in computer hardware or software documentation are considered out of scope for the committee. However, the committee may address needs in related domains through extensions or variants, and may commission sub-committees to focus on related domains. It is not a goal of the Technical Committee to expand the scope of DocBook to include additional, unrelated problem domains.
 
The OASIS DocBook TC is chartered to develop and maintain the DocBook family of specifications and to continue to support its ever growing user base. In particular, the XML and SGML DocBook schemas, a suite of extension modules, and a simplified authoring subset of DocBook. The Technical Committee plans to support a variety of schema languages and may develop additional modules and derived document types.

The EM-TC creates vendor-neutral and platform agnostic standards for organizations and agencies to more easily exchange emergency information. The EM-TC welcomes participation from members of the emergency management and response community, developers and implementers, and members of the public concerned with disaster management and response.
 
The Emergency Data Exchange Language (EDXL) is a broad initiative to create an integrated framework for a wide range of emergency data exchange standards to support operations, logistics, planning and finance.
 
Overview links below are provided for completed OASIS standards only. Non-linked items are works in progress. For most recent versions of all technical work see Technical Work Produced by the Committee

JTC 1/SC 22 is the international standardization subcommittee for programming languages, their environments and system software interfaces. SC 22 is oftentimes called the "portability subcommittee".

Standardization of coded representation of audio, picture, multimedia and hypermedia information - and sets of compression and control functions for use with such information - such as:

• Audio information
• Bi-level and Limited Bits-per-pixel Still Pictures
• Digital Continuous-tone Still Pictures
• Computer Graphic Images
• Moving Pictures and Associated Audio
• Multimedia and Hypermedia Information for Real-time Final Form Interchange
• Audio Visual Interactive Script ware

Excluded: Character Coding

The LegalCiteM TC develops an open standard for machine-readable tagging of legal citations based upon a formalized conceptual model, vocabulary, metadata definitions, and prescribed syntax. The goal of the standard is to support rich tagging of citations while leaving the visible text of the citation undisturbed. The markup is intended to work for a broad variety of legal content types — including court cases, legislation, regulations, parliamentary documents, and legal treatises. It supports citations as used in different countries and jurisdictions, and allows other metadata to be associated with citations for purposes beyond just linking. The TC also defines use cases, overviews, sample data sets, and such other non-normative content to help guide implementers and users in adopting the standard.
 
The TC is affiliated with the OASIS LegalXML Member Section. For more information on the LegalCiteM TC, see the TC Charter.

The initial focus of this Working Group was the development of mechanisms that provide confidentiality and authentication between DNS Clients and Iterative Resolvers (published as RFCs 7858 and 8094). With proposed standard solutions for the client-to-iterative resolvers published, the working group turns its attention to the development of documents focused on: 1) providing confidentiality to DNS transactions between Iterative Resolvers and Authoritative Servers, 2) measuring the efficacy in preserving privacy in the face pervasive monitoring attacks, and 3) defining operational, policy, and security considerations for DNS operators offering DNS privacy services. Some of the results of this working group may be experimental.There are numerous aspects that differ between DNS exchanges with an iterative resolver and exchanges involving DNS root/authoritative servers. The working group will work with
DNS operators and developers (via the DNSOP WG) to ensure that proposed solutions address key requirements.

The OASIS LegalRuleML TC defines a rule interchange language for the legal domain. The work enables modeling and reasoning that allows implementers to structure, evaluate, and compare legal arguments constructed using the rule representation tools provided.
 
The TC is affiliated with the OASIS LegalXML Member Section. For more information on LegalRuleML, see the TC Charter.

The Dynamic Host Configuration Working Group (DHC WG) has developed DHCP for automated allocation, configuration and management of IP addresses, IPv6 prefixes, IP protocol stack and other parameters. DHCPv4 is currently a Draft Standard and is documented in RFC 2131 and RFC 2132.
DHCPv6 is currently a Proposed Standard and is being updated. The WG plans to advance the DHCPv6 protocol to Internet standard. The DHC WG is responsible for defining DHCP protocol extensions. Definitions of new DHCP options that are delivered using standard mechanisms with documented semantics are not considered a protocol extension and thus are generally outside of scope for the DHC WG.

The Dynamic Host Configuration Working Group (DHC WG) has developed DHCP for automated allocation, configuration and management of IP addresses, IPv6 prefixes, IP protocol stack and other parameters. DHCPv4 is currently a Draft Standard and is documented in RFC 2131 and RFC 2132.
DHCPv6 is currently a Proposed Standard and is being updated. The WG plans to advance the DHCPv6 protocol to Internet standard. The DHC WG is responsible for defining DHCP protocol extensions. Definitions of new DHCP options that are delivered using standard mechanisms with documented semantics are not considered a protocol extension and thus are generally outside of scope for the DHC WG.

The OASIS Electronic Court Filing TC will develop specifications for the use of XML to create legal documents and to transmit legal documents from an attorney, party or self-represented litigant to a court, from a court to an attorney, party or self-represented litigant or to another court, and from an attorney or other user to another attorney or other user of legal documents.
 
The TC is affiliated with the OASIS LegalXML Member Section. For more information, see the TC Charter and FAQ