OASIS (organization)

The Organization for the Advancement of Structured Information Standards (OASIS) is a global nonprofit consortium that works on the development, convergence, and adoption of open standards for security, Internet of Things, energy, content technologies, emergency management, and other areas.

FocusOpen standard


OASIS was founded under the name "SGML Open" in 1993. It began as a trade association of SGML tool vendors to cooperatively promote the adoption of the Standard Generalized Markup Language (SGML) through mainly educational activities, though some amount of technical activity was also pursued including an update of the CALS Table Model specification and specifications for fragment interchange and entity management.[2]

In 1998, with the movement of the high tech industry to XML, "SGML Open" changed its emphasis from SGML to XML, and changed its name to OASIS Open to be inclusive of XML and reflect an expanded scope of technical work and standards. The focus of the consortium's activities also moved from promoting adoption (as XML was getting lots of attention on its own) to developing technical specifications. In July 2000 a new technical committee process was approved. With the adoption of the process the manner in which technical committees were created, operated, and progressed their work was regularized. At the adoption of the process there were five technical committees; by 2004 there were nearly 70.

During 1999, OASIS was approached by UN/CEFACT, the committee of the United Nations dealing with standards for business, to jointly develop a new set of specifications for electronic business. The joint initiative, called "ebXML" and which first met in November 1999, was chartered for a three-year period. At the final meeting under the original charter, in Vienna, UN/CEFACT and OASIS agreed to divide the remaining work between the two organizations and to coordinate the completion of the work through a coordinating committee. In 2004 OASIS submitted its completed ebXML specifications to ISO TC154 where they were approved as ISO 15000.

The consortium has its headquarters in Burlington, Massachusetts, shared with other companies. On September 4, 2014, the consortium moved from 25 Corporate Drive Suite 103 to 35 Corporate Dr Suite 150, still on the same loop route.[3]

Standards under development

The following standards are under development by OASIS technical committees:

  • AMQPAdvanced Message Queuing Protocol, an application layer protocol for message-oriented middleware.
  • BCM — Business Centric-Methodology, BCM is a comprehensive approach and proven techniques that enable a service-oriented architecture (SOA) and support enterprise agility and interoperability.
  • CAMContent Assembly Mechanism, is a generalized assembly mechanism for using templates of XML business transaction content and the associated rules. CAM templates augment schema syntax and provide implementers with the means to specify interoperable interchange patterns.
  • CAMPCloud Application Management for Platforms, is an API for managing public and private cloud applications.
  • CAPCommon Alerting Protocol, is an XML-based data format for exchanging public warnings and emergencies between alerting technologies.
  • CMISContent Management Interoperability Services, is a domain model and Web services standard for working with Enterprise content management repositories and systems.
  • CIQCustomer Information Quality, is an XML Specifications for defining, representing, interoperating and managing party information (e.g. name, address).
  • DocBookDocBook, a markup language for technical documentation. It was originally intended for authoring technical documents related to computer hardware and software but it can be used for any other sort of documentation.
  • DITADarwin Information Typing Architecture, a modular and extensible XML-based language for topic-based information, such as for online help, documentation, and training.
  • EMLElection Markup Language, End to End information standards and processes for conducting democratic elections using XML-based information recording.
  • EDXLEmergency Data Exchange Language, Suite of XML-based messaging standards that facilitate emergency information sharing between government entities and the full range of emergency-related organizations
  • GeoXACMLGeospatial eXtensible Access Control Markup Language, a geo-specific extension to XACML Version 2.0, mainly the geometric data-type urn:ogc:def:dataType:geoxacml:1.0:geometry and several geographic functions such as topological, bag, set, geometric and conversion functions.
  • KMIP — The Key Management Interoperability Protocol tries to establish a single, comprehensive protocol for the communication between enterprise key management systems and encryption systems.
  • Legal XML LegalDocumentML (Akoma Ntoso), LegalRuleML, Electronic Court Filing, and eNotarization standards.
  • MQTTMessage Queuing Telemetry Transport, a client-server, publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in machine to machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
  • oBIXopen Building Information Exchange, an extensible XML specification for enterprise interaction with building-based (or other) control systems, including HVAC, Access Control, Intrusion Detection, and many others.
  • ODataOpen Data Protocol (OData), Simplifying data sharing across disparate applications in enterprise, Cloud, and mobile devices.
  • OpenDocumentOASIS Open Document Format for Office Applications, an open document file format for saving office documents such as spreadsheets, memos, charts, and presentations.
  • OSLCOpen Services for Lifecycle Collaboration, (OSLC) develops standards that make it easy and practical for software lifecycle tools to share data with one another. See the OSLC community web site (http://open-services.net) for more details.
  • SAMLSecurity Assertion Markup Language, a standard XML-based framework for the secure exchange of authentication and authorization information.
  • SDDSolution Deployment Descriptor, a standard XML-based schema defining a standardized way to express software installation characteristics required for lifecycle management in a multi-platform environment.
  • SPMLService Provisioning Markup Language, a standard XML-based protocol for the integration and interoperation of service provisioning requests.
  • TOSCATopology and Orchestration Specification for Cloud Applications, a Standard to describe cloud services, the relationships between parts of the service, and the operational behavior of the services.
  • UBLUniversal Business Language, the international effort to define a royalty-free library of standard electronic business documents (purchase order, invoice, waybill, etc.) in XML. UBL 2.1 was approved as ISO/IEC 19845:2015. UBL serves as the basis for numerous electronic commerce networks and implementations worldwide.
  • UDDIUniversal Description Discovery and Integration, a platform-independent, XML-based registry for companies and individuals to list Web Services.
  • VirtIOVirtual I/O, a standard for paravirtualized devices.
  • WebCGMWeb Computer Graphics Metafile, a profile of Computer Graphics Metafile (CGM), which adds Web linking and is optimized for Web applications in technical illustration, electronic documentation, geophysical data visualization, and similar fields.
  • WS-BPELWeb Services Business Process Execution Language
  • WSDMWeb Services Distributed Management
  • XACMLeXtensible Access Control Markup Language, a standard XML-based protocol for access control policies.
  • XDIXRI Data Interchange, a standard for sharing, linking, and synchronizing data ("dataweb") across multiple domains and applications using XML documents, eXtensible Resource Identifiers (XRIs), and a new method of distributed data control called a link contract.
  • XLIFFXML Localization Interchange File Format, a XML-based format created to standardize localization.
  • XRIeXtensible Resource Identifier, a URI-compatible scheme and resolution protocol for abstract identifiers used to identify and share resources across domains and applications.


Adhesion to the consortium requires some fees to be paid, which must be renewed annually, depending on the membership category adherents want to access.[4] Among the adherents are members from American Bar Association, Collabora, Dell, EclecticIQ, General Motors, IBM, ISO/IEC, KDE e.V., Microsoft, Novell, Oracle, Redhat, The Document Foundation, universities, government agencies, individuals and employees from other less-known companies.[5][6]

Patent disclosure controversy

Like many bodies producing open standards e.g. ECMA,[7] OASIS added a Reasonable and non-discriminatory licensing (RAND) clause to its policy in February 2005.[6] That amendment required participants to disclose intent to apply for software patents for technologies under consideration in the standard. Contrary to the W3C, which requires participants to offer royalty-free licenses to anyone using the resulting standard, OASIS offers a similar Royalty Free on Limited Terms mode, along with a Royalty Free on RAND Terms mode and a RAND (reasonable and non-discriminatory) mode for its committees. Compared to W3C, OASIS is less restrictive regarding obligation to companies to grant a royalty-free license to the patents they own.[8]

Controversy has rapidly arisen[9] because this licensing was added silently and allows publication of standards which could require licensing fee payments to patent holders. This situation could effectively eliminate the possibility of free/open source implementations of these standards. Further, contributors could initially offer royalty-free use of their patent, later imposing per-unit fees, after the standard has been accepted.

On April 11, 2005, The New York Times reported IBM committed for free, all of its patents to the OASIS group.[10] Larry Rosen, a software law expert and the leader of the reaction which rose up when OASIS quietly included a RAND clause in its policy, welcomed the initiative and supposed OASIS will not continue using that policy as other companies involved would follow. History proved him wrong, as that RAND policy has still not been removed and other commercial companies have not published such a free statement towards OASIS.

Patrick Gannon, president and CEO of OASIS from 2001 to 2008,[11] minimized the risk that a company could take advantage of a standard to request royalties when it has been established: "If it's an option nobody uses, then what's the harm?".

Sam Hiser, former marketing lead of the now defunct OpenOffice.org, explained that such patents towards an open standard are counterproductive and inappropriate. He also argued that IBM and Microsoft were shifting their standardization efforts from the W3C to OASIS, in a way to leverage probably their patents portfolio in the future. Hiser also attributed this RAND change to the OASIS policy to Microsoft.[12]

The RAND term could indeed theoretically allow any company involved to leverage their patent in the future. But that amendment was probably added in a way to attract more companies to the consortium, and encourage contributions from potential participants. Big actors like Microsoft could have indeed applied pressure and made a sine-qua-non condition to access the consortium, and possibly jeopardize/boycott the standard if such a clause was not present.


Doug Mahugh — while working for Microsoft (a promoter of Office Open XML, a Microsoft document format competing with OASIS's ISO/IEC 26300, i.e. ODF v1.0) as a Senior Product Manager specializing in Office client interoperability — claimed that "many countries have expressed frustration about the pace of OASIS's responses to defect reports that have been submitted on ISO/IEC 26300 and the inability for SC 34 members to participate in the maintenance of ODF."[13] However, Rob Weir, co-chair of the OASIS ODF Technical Committee noted that at the time, "the ODF TC had received zero defect reports from any ISO/IEC national body other than Japan". He added that the submitter of the original Japanese defect report, Murata Mokoto, was satisfied with the preparation of the errata.[14] He also self-published a blog post blaming Microsoft of involving people to improve and modify the accuracy of ODF and OpenXML Wikipedia articles, trying to make ODF sound risky to adopt.[15]

See also


  1. "Staff". Retrieved August 10, 2015.
  2. "About Us". Retrieved August 10, 2015.
  3. "OASIS Headquarters Moving". Retrieved August 10, 2015.
  4. "Categories and Dues | OASIS". Retrieved August 10, 2015.
  5. "OASIS OASIS Open Document Format for Office Applications (OpenDocument) TC Technical Committee". Retrieved August 10, 2015.
  6. "Larry Rosen et al. vs. OASIS on licensing". 22 February 2005. Retrieved 10 August 2015.
  7. "Ecma Code of Conduct in Patent Matters". 1 December 2009. Retrieved 10 August 2015.
  8. "Intellectual Property Rights (IPR) Policy | OASIS". OASIS.
  9. Sheriff, Lucy (February 23, 2005). "OASIS open standards not open enough · The Register".
  10. "No RAND in OASIS". 5 April 2005. Retrieved 10 August 2015.
  11. "Bio –Patrick J. Gannon" (PDF). 1 May 2012. Retrieved 10 August 2015.
  12. Lyman, Jay (May 24, 2005). "Linux.com :: OASIS: Meaningful open standards or mirage?".
  13. Mahugh, Doug (October 1, 2008). "SC 34 Plenary, Jeju, Korea - Doug Mahugh - Site Home - MSDN Blogs". Retrieved June 27, 2013.
  14. "Further comment on ODF_1.0_Errata_draft_3". Retrieved August 10, 2015.
  15. Weir, Robert (June 9, 2009). "ODF Lies and Whispers". Retrieved June 27, 2013.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.