Misplaced Pages

#958041

26-568: The XML format used by XRDS was originally developed in 2004 by the OASIS XRI ( extensible resource identifier ) Technical Committee as the resolution format for XRIs. The acronym XRDS was coined during subsequent discussions between XRI TC members and OpenID developers at first Internet Identity Workshop held in Berkeley, CA in October 2005. The protocol for discovering an XRDS document from

52-785: A URL was formalized as the Yadis specification published by Yadis.org in March 2006. Yadis became the service discovery format for OpenID 1.1. A common discovery service for both URLs and XRIs proved so useful that in November 2007 the XRI Resolution 2.0 specification formally added the URL-based method of XRDS discovery (Section 6). This format and discovery protocol subsequently became part of OpenID Authentication 2.0. In early 2008, work on OAuth discovery by Eran Hammer-Lahav led to

78-403: A RAND clause in its policy, welcomed the initiative and supposed OASIS will not continue using that policy as other companies involved would follow. The 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, minimized the risk that a company could take advantage of

104-615: A blog post blaming Microsoft of involving people to improve and modify the accuracy of ODF and OpenXML Misplaced Pages articles. CALS Table Model The CALS Table Model is a standard for representing tables in SGML / XML . It was developed as part of the Continuous Acquisition and Life-cycle Support (CALS) initiative by the United States Department of Defense . The CALS Table Model was developed by

130-472: A sequence of XRDs within a single XRDS document to reflect a chain of metadata about linked resources. XRDS documents can assert zero or more synonyms for a resource. In this context, a synonym is another identifier (a URI or XRI ) that identifies the same target resource. For instance, the example XRDS document above asserts four synonyms: For full details of XRDS synonym support, see XRI Resolution 2.0, Section 5. The other main purpose of XRDS documents

156-448: 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) — 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

182-453: A standard to request royalties when it has been established, saying "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

208-507: A way to leverage probably their patents portfolio in the future. Hiser also attributed this RAND change to the OASIS policy to Microsoft. The RAND term could indeed 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

234-449: Is an example of an XRDS document for the fictional XRI i-name =example . This document would typically be requested from a Web server via HTTP or HTTPS using the content type application/xrds+xml . Note that the outer container <XRDS> element serves as a container for one or more <XRD> (Extensible Resource Descriptor) elements. Most simple XRDS documents have only one XRD. Other services like XRI resolution may construct

260-460: Is an open public royalty-free OASIS specification. The OASIS XRI Technical Committee has operated since its inception in 2003 under a royalty-free licensing policy as stated in its charter and IPR page. OASIS (organization) The Organization for the Advancement of Structured Information Standards ( OASIS ; / oʊ ˈ eɪ . s ɪ s / ) is a nonprofit consortium that works on

286-417: Is to assert the services associated with a resource, called service endpoints or SEPs . For instance, the example XRDS document above asserts four service endpoints for the represented resource: For full details of XRDS service endpoints, see XRI Resolution 2.0, Sections 4.2 and 13. In XRDS documents, a service is identified using a URI or XRI . Following are listings of well-known service types. XRDS

SECTION 10

#1732800710959

312-598: The Continuous Acquisition and Life-cycle Support (CALS) Industry Steering Group Electronic Publishing Committee (EPC). The EPC subcommittee, of which Harvey Bingham was co-chair and a major contributor, designed the CALS Table Model in 1989–1990. The EPC was made up of industry and military service representatives. Some represented traditional military document printing agencies. Others represented electronic publishing organizations. SGML itself

338-549: The adoption of 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. In 1998, with the movement of the 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

364-443: The consortium requires some fees to be paid, which must be renewed annually, depending on the membership category adherents want to access. Among the adherents are members from Dell , IBM , ISO/IEC , Cisco Systems , KDE e.V. , Microsoft , Oracle , Red Hat , The Document Foundation , universities, government agencies, individuals and employees from other less-known companies. Member sections are special interest groups within

390-454: The consortium that focus on specific topics. These sections keep their own distinguishable identity and have full autonomy to define their work program and agenda. The integration of the member section in the standardization process is organized via the technical committees. Active member sections are for example: Member sections may be completed when they have achieved their objectives. The standards that they promoted are then maintained by

416-472: The consortium's activities also moved from promoting adoption (as XML was getting much 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

442-475: The development of XRDS Simple, a profile of XRDS that restricts it to the most basic elements and introduces some extensions to support OAuth discovery and other protocols that use specific HTTP methods. In late 2008, XRDS Simple has been cancelled and merged back into the main XRDS specification resulting in the upcoming XRD 1.0 format. Besides XRI resolution, examples of typical XRDS usage include: Following

468-456: The development, convergence, and adoption of projects - both open standards and open source - for Computer security , blockchain , Internet of things (IoT), emergency management , cloud computing , legal data exchange , energy , content technologies , and other areas. OASIS was founded under the name "SGML Open" in 1993. It began as a trade association of Standard Generalized Markup Language (SGML) tool vendors to cooperatively promote

494-512: The former name of the Organization for the Advancement of Structured Information Standards ( OASIS ), surveyed the implementing vendors to identify differences as the initial step toward reaching a common interpretation. The next step was an updated CALS Table Model DTD and semantics. Both are now available from OASIS. As implementations of the CALS Table Model were developed, a number of ambiguities and omissions were detected and reported to

520-557: The inability for SC 34 members to participate in the maintenance of ODF." 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. He also self-published

546-449: 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. Larry Rosen, a software law expert and the leader of the reaction which rose up when OASIS quietly included

SECTION 20

#1732800710959

572-539: The relevant technical committees directly within OASIS. For example: Like many bodies producing open standards e.g. ECMA , OASIS added a Reasonable and non-discriminatory licensing (RAND) clause to its policy in February 2005. 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

598-551: 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. Controversy has rapidly arisen 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

624-729: 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 Woburn, Massachusetts , shared with other companies. In December 2020, OASIS moved to its current location, 400 TradeCenter Drive. Previous office locations include 25 Corporate Drive Suite 103 and 35 Corporate Drive, Suite 150, both in Burlington, MA. The following standards are under development or maintained by OASIS technical committees: Adhesion to

650-533: 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

676-556: Was new. At that time, the CALS intent for all their technical manuals was to use that document type definition (DTD) to achieve system-neutral interchange of content and structure. Its basis was a minimal description and example of a table from the prior Mil-M-38784B specification for producing technical manuals. The incomplete specification of the semantics associated with the table model allowed too much freedom for vendor interpretation, and resulted in problems with interchange. SGML-Open,

#958041