Content Technologies

Standard

Darwin Information Typing Architecture (DITA) v1.3

Defines both a) a set of document types for authoring and organizing topic-oriented information; and b) a set of mechanisms for combining, extending, and constraining document types.

Produced by:

OASIS Darwin Information Typing Architecture (DITA) TC

Voting history:

Voting History for OASIS Standard, December 2015

Voting History for Approved Errata 01, October 2016

Voting History for Approved Errata 02, June 2018

Cite as:

Cite as:

[DITA-v1.3-part0-overview] Darwin Information Typing Architecture (DITA) Version 1.3 Part 0: Overview. Edited by Robert D. Anderson and Kristen James Eberlein. 17 December 2015. OASIS Standard. http://docs.oasis-open.org/dita/dita/v1.3/os/part0-overview/dita-v1.3-os-part0-overview.html. Latest version: http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-part0-overview.html.

[DITA-v1.3-part1-base] Darwin Information Typing Architecture (DITA) Version 1.3 Part 1: Base Edition. Edited by Robert D. Anderson and Kristen James Eberlein. 17 December 2015. OASIS Standard. http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/dita-v1.3-os-part1-base.html. Latest version: http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-part1-base.html.

[DITA-v1.3-part2-tech-content] Darwin Information Typing Architecture (DITA) Version 1.3 Part 2: Technical Content Edition. Edited by Robert D. Anderson and Kristen James Eberlein. 17 December 2015. OASIS Standard. http://docs.oasis-open.org/dita/dita/v1.3/os/part2-tech-content/dita-v1.3-os-part2-tech-content.html. Latest version: http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-part2-tech-content.html.

[DITA-v1.3-part3-all-inclusive] Darwin Information Typing Architecture (DITA) Version 1.3 Part 3: All-Inclusive Edition. Edited by Robert D. Anderson and Kristen James Eberlein. 17 December 2015. OASIS Standard. http://docs.oasis-open.org/dita/dita/v1.3/os/part3-all-inclusive/dita-v1.3-os-part3-all-inclusive.html. Latest version: http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-part3-all-inclusive.html.

[DITA-v1.3-errata01] Darwin Information Typing Architecture (DITA) Version 1.3 Errata 01. Edited by Robert D. Anderson and Kristen James Eberlein. 25 October 2016. OASIS Approved Errata. http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/dita-v1.3-errata01-os.html. Latest version: http://docs.oasis-open.org/dita/dita/v1.3/errata01/dita-v1.3-errata01.html.

[DITA-v1.3-errata02] Darwin Information Typing Architecture (DITA) Version 1.3 Errata 02. Edited by Robert D. Anderson and Kristen James Eberlein. 19 June 2018. OASIS Approved Errata. http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/dita-v1.3-errata02-os.html. Latest version: http://docs.oasis-open.org/dita/dita/v1.3/errata02/dita-v1.3-errata02.html.

Standard

Universal Business Language (UBL) v2.1

Defines the Universal Business Language, version 2.1.

Produced by:

OASIS Universal Business Language TC

Voting history:

November 2013

Voting History

Additional approvals

ISO/IEC 19845:2015

Cite as:

Cite as:
[UBL-2.1] Universal Business Language Version 2.1.. Edited by Jon Bosak, Tim McGrath, and G. Ken Holman. 04 November 2013. OASIS Standard. http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html. Latest version: http://docs.oasis-open.org/ubl/UBL-2.1.html.

Standard

Content Management Interoperability Services (CMIS) v1.1

Defines a domain model and Web Services, Restful AtomPub and browser (JSON) bindings that can be used by applications to work with one or more Content Management repositories/systems.
The CMIS interface is designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. It is not intended to prescribe how specific features should be implemented within those CM systems, nor to exhaustively expose all of the CM system’s capabilities through the CMIS interfaces. Rather, it is intended to define a generic/universal set of capabilities provided by a CM system and a set of services for working with those capabilities.

Produced by:

OASIS Content Management Interoperability Services (CMIS) TC

Voting history:

Voting History for OASIS Standard, May 2013

Voting History for Approved Errata 01, September 2015

Cite as:

[CMIS-v1.1]Content Management Interoperability Services (CMIS) Version 1.1. Edited by Florian Müller, Ryan McVeigh, and Jens Hübel. 23 May 2013. OASIS Standard. http://docs.oasis-open.org/cmis/CMIS/v1.1/os/CMIS-v1.1-os.html. Latest version: http://docs.oasis-open.org/cmis/CMIS/v1.1/CMIS-v1.1.html.

[CMIS-v1.1-Errata01]Content Management Interoperability Services (CMIS) Version 1.1 Errata 01. Edited by Florian Müller and Ken Baclawski. 19 September 2015. OASIS Approved Errata 01. http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1-errata01-os.html. Latest version: http://docs.oasis-open.org/cmis/CMIS/v1.1/CMIS-v1.1.html.

[CMIS-v1.1-Plus-Errata01]Content Management Interoperability Services (CMIS) Version 1.1 Plus Errata 01.
Edited by Florian Müller and Ken Baclawski. 19 September 2015.
OASIS Standard Incorporating Approved Errata 01.
http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1- errata01-os-complete.html. Latest version: http://docs.oasis-open.org/cmis/CMIS/v1.1/CMIS-v1.1.html.

Standard

Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0

Defines a framework for integrating a broad range of domain models for collaboration activities in an integrated and interoperable collaboration environment.

Produced by:

OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC

Voting history:

January 2013

Voting History

Cite as:

Cite as:
[ICOM-ics-v1.0] Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0. . Edited by Eric S. Chan and Patrick Durusau. 31 January 2013. OASIS Committee Specification 01. http://docs.oasis-open.org/icom/icom-ics/v1.0/cs01/icom-ics-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/icom/icom-ics/v1.0/icom-ics-v1.0.html.

Standard

Field Force Management Integration Interface Specification Version 1.0

Describes the Field Force Management Integration Interface (FFMII). FFMII provides a flexible interface between Enterprise Resource Management System (ERMS) and Field Force Management System (FFMS). The role of ERMS is to take a holistic view at work scheduling and resource allocation from the corporate point of view. For this purpose it needs to manage individual units of work performed without strong supervisory guidance (Field Work) in a way aligned with the business objectives of the company. The role of FFMS is to communicate with available set of workers (Field Force) and to provide individual workers (Assignees) performing Field Work with technical means of accessing information about and sending feedback on work assigned to them. While ERMS defines the structure, content and resource allocation of dispatched work, FFMS is responsible for communicating that information to the field and enforcing any specified constraints on user provided feedback. For facilitating structured communication between ERMS and FFMS in heterogeneous scenarios, FFMII defines flexible mechanisms that enable Work Request modeling (data content, workflow), exchange, work history collection, and collection of data from the field. Information carried with work requests, work request structure (work-flow, schedule) and data to be collected can all be defined dynamically ‘as data’. This data driven architecture makes FFMII very flexible and adaptable to numerous industries. Additional FFMII capabilities include Field-Initiated Requests that facilitate structured requests and reporting information outside the usual work flow, such as reporting absence, requesting additional work, or providing a sales lead. Reference Data Management provides means to establish custom data repositories with arbitrary content. This enables e.g. input value selection, content validation, or delivery of documents to Field Force. Furthermore, flexible Integration Topologies are supported. Further flexibility is provided by scalability of FFMII itself: Basic features of FFMII are mandatory, and some features are optional. This allows both simple basic implementations and a range of more complete implementations.

Produced by:

Field Force Management Integration Interface Specification Version 1.0

Voting history:

October 2012

Voting History

Cite as:

Cite as:
[FFMII-SPEC-v1.0] Field Force Management Integration Interface Specification Version 1.0. Edited by Thinh Nguyenphu. 05 October 2012. OASIS Committee Specification 01. http://docs.oasis-open.org/ffm/FFMII-SPEC/v1.0/cs01/FFMII-SPEC-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/ffm/FFMII-SPEC/v1.0/FFMII-SPEC-v1.0.html.

Standard

Election Markup Language (EML) Specification Version 7.0

Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as guidance on the constraints, extensibility, and splitting of messages.

Produced by:

OASIS Election and Voter Services TC

Voting history:

October 2011

Voting History

Cite as:

Cite as:
[EML-v7.0] Election Markup Language (EML) Specification Version 7.0. Edited by John Borras and David Webber. 27 October 2011. OASIS Committee Specification 01. http://docs.oasis-open.org/election/eml/v7.0/cs01/eml-v7.0-cs01.html. Latest version: http://docs.oasis-open.org/election/eml/v7.0/eml-v7.0.html.

Standard

Production Planning and Scheduling (PPS) Version 1.0

Deals with problems of decision-making in all manufacturing companies who want to have a sophisticated information system for production planning and scheduling. PPS specification provides XML schema and communication protocols for information exchange among manufacturing application programs in the web-services environment. The Core Elements section focuses on information model of core elements which can be used as ontology in the production planning and scheduling domain. Since the elements have been designed without particular contexts in planning and scheduling, they can be used in any specific type of messages as a building block depending on the context of application programs. The Transaction Messages section focuses on transaction messages that represent domain information sent or received by application programs in accordance with the context of the communication, as well as transaction rules for contexts such as pushing and pulling of the information required. Finally, the Profile Specifications section focuses on profiles of application programs that may exchange the messages. Application profile and implementation profile are defined. Implementation profile shows capability of application programs in terms of services for message exchange, selecting from all exchange items defined in the application profile. The profile can be used for definition of a minimum level of implementation of application programs which are involved in a community of data exchange.

Produced by:

OASIS Production Planning and Scheduling TC

Voting history:

September 2011

Voting History

Cite as:

Cite as:
[PPS] Production Planning and Scheduling (PPS) Version 1.0. Edited by Yasuyuki Nishioka and Koichi Wada. 29 September 2011. OASIS Committee Specification 01. http://docs.oasis-open.org/pps/pps/v1.0/cs01/pps-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/pps/pps/v1.0/pps-v1.0.html.

Standard

Open Document Format for Office Applications (OpenDocument) Version 1.2

This specification consists of this document as well as the following three parts:

Part 1 defines an XML schema for office applications and its semantics. The schema is suitable for office documents, including text documents, spreadsheets, charts and graphical documents like drawings or presentations, but is not restricted to these kinds of documents.

Part 2 defines a formula language to be used in OpenDocument documents.

Part 3 defines a package format to be used for OpenDocument documents.

Produced by:

OASIS Open Document Format for Office Applications (OpenDocument) TC

Voting history:

Voting History

September 2011

Additional approvals

ISO/IEC 26300-1:2015

ISO/IEC 26300-2:2015

ISO/IEC 26300-3:2015

Cite as:

Standard

The State of ODF Interoperability Version 1.0

Discusses interoperability with respect to the OASIS OpenDocument Format (ODF) and notes specific areas where implementors might focus in order to improve interoperability among ODF-supporting applications.

Produced by:

OASIS Open Document Format Interoperability and Conformance (OIC) TC

Voting history:

December 2010

Voting History

Cite as:

Cite as:
[ODF-Interop-v1.0]
The State of ODF Interoperability Version 1.0. Edited by Robert Weir. 10 December 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/oic/StateOfInterop/v1.0/cs01/StateOfInterop-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/oic/StateOfInterop/v1.0/StateOfInterop.html.

Standard

Darwin Information Typing Architecture (DITA) v1.2

Defines both a) a set of document types for authoring and organizing topic-oriented information; and b) a set of mechanisms for combining, extending, and constraining document types.

Produced by:

OASIS Darwin Information Typing Architecture (DITA) TC

Voting history:

December 2010

Voting History

Cite as:

Standard

Election Markup Language (EML) Specification Version 6.0

Describes the background and purpose of the Election Markup Language, the electoral processes from which it derives its structure and the security and audit mechanisms it is designed to support. It also provides an explanation of the core schemas used throughout, definitions of the simple and complex datatypes, plus the EML schemas themselves. It also covers the conventions used in the specification and the use of namespaces, as well as the guidance on the constraints, extendibility, and splitting of messages.

Produced by:

OASIS Election and Voter Services TC

Voting history:

August 2010

Voting History

Cite as:

Cite as:
[EML-v6.0] Election Markup Language (EML) Specification Version 6.0. Edited by John Borras and David Webber. 19 August 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/election/eml/v6.0/cs01/EML-Specification-v6.0-cs01.html. Latest version: http://docs.oasis-open.org/election/eml/v6.0/EML-Specification-v6.0.html.

Standard

Content Management Interoperability Services (CMIS) v1.0

Defines a domain model and Web Services and Restful AtomPub bindings that can be used by applications to work with one or more Content Management repositories/systems.

The CMIS interface is designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. It is not intended to prescribe how specific features should be implemented within those CM systems, not to exhaustively expose all of the CM system’s capabilities through the CMIS interfaces. Rather, it is intended to define a generic/universal set of capabilities provided by a CM system and a set of services for working with those capabilities.

Produced by:

OASIS Content Management Interoperability Services (CMIS) TC

Voting history:

May 2010

Voting History

Cite as:

No results with the selected filters