Content Technologies
StandardOpen Document Format v1.1 Accessibility Guidelines Version 1.0
A guide for Office Applications, that support version 1.1 of the OpenDocument format, to promote and preserve accessible ODF documents. This guide is not a comprehensive guide for content mapping to platform accessibility APIs.
Open Document Format v1.1 Accessibility Guidelines Version 1.0
A guide for Office Applications, that support version 1.1 of the OpenDocument format, to promote and preserve accessible ODF documents. This guide is not a comprehensive guide for content mapping to platform accessibility APIs.
Produced by:
OASIS Open Document Format for Office Applications (OpenDocument) TCVoting history:
May 2008
OASIS Standard:
Cite as:
Cite as:
[ODF-Access-Guidelines-v1.0] Open Document Format v1.1 Accessibility Guidelines Version 1.0. Edited by Peter Korn and Rich Schwerdtfeger. 01 May 2008. OASIS Committee Specification 01. http://docs.oasis-open.org/office/office-accessibility/v1.0/cs01/ODF_Accessibility_Guidelines-v1.0.html. Latest version: http://docs.oasis-open.org/office/office-accessibility/v1.0/cd01/ODF_Accessibility_Guidelines-v1.0.html.
StandardExtensible Resource Identifier (XRI) Resolution Version 2.0
Defines a simple generic format for resource description (XRDS documents), a protocol for obtaining XRDS documents from HTTP(S) URIs, and generic and trusted protocols for resolving Extensible Resource Identifiers (XRIs) using XRDS documents and HTTP(S) URIs. These protocols are intended for use with both HTTP(S) URIs as defined in [RFC2616] and with XRIs as defined by Extensible Resource Identifier (XRI) Syntax Version 2.0 [XRISyntax] or higher.
Extensible Resource Identifier (XRI) Resolution Version 2.0
Defines a simple generic format for resource description (XRDS documents), a protocol for obtaining XRDS documents from HTTP(S) URIs, and generic and trusted protocols for resolving Extensible Resource Identifiers (XRIs) using XRDS documents and HTTP(S) URIs. These protocols are intended for use with both HTTP(S) URIs as defined in [RFC2616] and with XRIs as defined by Extensible Resource Identifier (XRI) Syntax Version 2.0 [XRISyntax] or higher.
Produced by:
OASIS Extensible Resource Identifier (XRI) TCVoting history:
April 2008
OASIS Standard:
Cite as:
Cite as:
[XRI-Res]
Extensible Resource Identifier (XRI) Resolution Version 2.0. Edited by Gabe Wachob, Drummond Reed, Les Chasen, William Tan, and Steve Churchill. 12 April 2008. OASIS Committee Specification 01. http://docs.oasis-open.org/xri/xri-resolution/2.0/specs/cs01/xri-resolution-V2.0-cs-01.html. Latest version: http://docs.oasis-open.org/xri/2.0/specs/xri-resolution-V2.0.html
StandardXML Localisation Interchange File Format (XLIFF) v1.2
Defines the XML Localization Interchange File Format (XLIFF). The purpose of this vocabulary is to store localizable data and carry it from one step of the localization process to the other, while allowing interoperability between tools.
XML Localisation Interchange File Format (XLIFF) v1.2
Defines the XML Localization Interchange File Format (XLIFF). The purpose of this vocabulary is to store localizable data and carry it from one step of the localization process to the other, while allowing interoperability between tools.
Produced by:
OASIS XML Localisation Interchange File Format (XLIFF) TCVoting history:
February 2008
StandardCode List Representation (Genericode) Version 1.0
Describes the OASIS Code List Representation model and W3C XML Schema, known collectively as “genericode”.
Code List Representation (Genericode) Version 1.0
Describes the OASIS Code List Representation model and W3C XML Schema, known collectively as “genericode”.
Produced by:
OASIS Code List Representation Technical CommitteeVoting history:
December 2007
OASIS Standard:
Cite as:
Cite as:
[genericode-v1.0] Code List Representation (Genericode) Version 1.0. Edited by Anthony B. Coates. 28 December 2007. OASIS Committee Specification 01. http://docs.oasis-open.org/codelist/cs-genericode-1.0/doc/oasis-code-list-representation-genericode.html. Latest version: http://docs.oasis-open.org/codelist/cs-genericode-1.0/doc/oasis-code-list-representation-genericode.html.
StandardDarwin Information Typing Architecture (DITA) v1.1
Defines both a) a set of document types for authoring and organizing topic-oriented information; and b) a set of mechanisms for combining and extending document types using a process called specialization.
Darwin Information Typing Architecture (DITA) v1.1
Defines both a) a set of document types for authoring and organizing topic-oriented information; and b) a set of mechanisms for combining and extending document types using a process called specialization.
StandardContent Assembly Mechanism (CAM) v1.1
Provides an open XML based system for using business rules to define, validate and compose specific business documents from generalized schema elements and structures.
The core role of the OASIS CAM specifications is to provide a generic standalone content assembly mechanism that extends beyond the basic structural definition features in XML and schema to provide a comprehensive system with which to define dynamic e-business interoperability.
Content Assembly Mechanism (CAM) v1.1
Provides an open XML based system for using business rules to define, validate and compose specific business documents from generalized schema elements and structures.
The core role of the OASIS CAM specifications is to provide a generic standalone content assembly mechanism that extends beyond the basic structural definition features in XML and schema to provide a comprehensive system with which to define dynamic e-business interoperability.
StandardeContracts Version 1.0
Describes the generic hierarchical structure of a wide range of contract documents. The TC envisages that the primary use of the eContracts Schema will be to facilitate the maintenance of precedent or template contract documents and contract terms by persons who wish to use them to create new contract documents with automated tools. Use cases covered include negotiated business contracts, ticket contracts, standard form business and consumer contracts and click-through agreements.
eContracts Version 1.0
Describes the generic hierarchical structure of a wide range of contract documents. The TC envisages that the primary use of the eContracts Schema will be to facilitate the maintenance of precedent or template contract documents and contract terms by persons who wish to use them to create new contract documents with automated tools. Use cases covered include negotiated business contracts, ticket contracts, standard form business and consumer contracts and click-through agreements.
Produced by:
OASIS LegalXML eContracts TCVoting history:
April 2007
OASIS Standard:
Cite as:
Cite as:
[econtracts-v1.0] eContracts Version 1.0. Edited by Laurence Leff and Peter Meyer. 27 April 2007. OASIS Committee Specification. http://docs.oasis-open.org/legalxml-econtracts/CS01/legalxml-econtracts-specification-1.0.html. Persistent version: http://docs.oasis-open.org/legalxml-econtracts/CS01/legalxml-econtracts-specification-1.0.html.
StandardDigital Signature Services v1.0
Defines XML request/response protocols for signing and verifying XML documents and other data. It also defines an XML timestamp format, and an XML signature property for use with these protocols. Finally, it defines transport and security bindings for the protocols.
Digital Signature Services v1.0
Defines XML request/response protocols for signing and verifying XML documents and other data. It also defines an XML timestamp format, and an XML signature property for use with these protocols. Finally, it defines transport and security bindings for the protocols.
Produced by:
OASIS Digital Signature Services TCVoting history:
April 2007
OASIS Standard:
DSS Core Protocols, Elements, and Bindings v1.0
HTML PDF DOC Schema
DSS German Signature Law Profile
HTML PDF DOC
DSS Advanced Electronic Signature Profiles
HTML PDF DOC Schema
DSS Asynchronous Processing Abstract Profile
HTML PDF DOC Schema
DSS J2ME Code-Signing Profile
HTML PDF DOC Schema
DSS Abstract Code-Signing Profile
HTML PDF DOC Schema
DSS Electronic PostMark (EPM) Profile
HTML PDF DOC Schema
DSS Entity Seal Profile
HTML PDF DOC Schema
DSS Signature Gateway Profile
HTML PDF DOC
DSS XML Timestamping Profile
HTML PDF DOC Schema
Cite as:
StandardOpen Document Format for Office Applications (OpenDocument) Specification v1.1
An open, XML-based file format for office applications, based on OpenOffice.org XML [OOo].
Open Document Format for Office Applications (OpenDocument) Specification v1.1
An open, XML-based file format for office applications, based on OpenOffice.org XML [OOo].
Produced by:
OASIS Open Document Format for Office Applications (OpenDocument) TCVoting history:
Voting History for OASIS Standard, February 2007
Voting History for Approved Errata 01, July 2013
OASIS Standard:
HTML also available as a zip archive
Related Schemas:
Schema
Manifest Schema
Strict Schema
OASIS Standard incorporating Approved Errata 01
ODT
HTML
PDF
Related Schemas:
Schema Errata 01
Manifest Schema
Strict Schema Errata 01
Cite as:
StandardUniversal Business Language (UBL) v2.0
Defines the Universal Business Language, version 2.0.
Universal Business Language (UBL) v2.0
Defines the Universal Business Language, version 2.0.
StandardDocBook v4.5
DocBook is a general purpose [XML] schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications).d
DocBook v4.5
DocBook is a general purpose [XML] schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications).d
StandardExtensible Resource Identifier (XRI) Syntax V2.0
This is the normative technical specification for XRI generic syntax. For a non-normative introduction to the uses and features of XRIs, see Introduction to XRIs [XRIIntro].
Extensible Resource Identifier (XRI) Syntax V2.0
This is the normative technical specification for XRI generic syntax. For a non-normative introduction to the uses and features of XRIs, see Introduction to XRIs [XRIIntro].
Produced by:
OASIS Extensible Resource Identifier (XRI) TCVoting history:
November 2005
OASIS Standard:
Cite as:
Cite as:
[XRI]
Extensible Resource Identifier (XRI) Syntax V2.0. Edited by Drummond Reed and Dave McAlpin. 14 November 2005. OASIS Committee Specification 01. http://docs.oasis-open.org/xri/xri-syntax/2.0/specs/cs01/xri-syntax-V2.0-cs.html. Latest version: http://docs.oasis-open.org/xri/2.0/specs/xri-syntax-V2.0.html
No results with the selected filters