Misplaced Pages

#45954

28-518: Reference models are often illustrated as a set of concepts with some indication of the relationships between the concepts. According to OASIS (Organization for the Advancement of Structured Information Standards) a reference model is "an abstract framework for understanding significant relationships among the entities of some environment, and for the development of consistent standards or specifications supporting that environment. A reference model

56-425: A 'reference model.' Each of these concepts is important: There are many uses for a reference model. One use is to create standards for both the objects that inhabit the model and their relationships to one another. By creating standards, the work of engineers and developers who need to create objects that behave according to the standard is made easier. Software can be written that meets a standard. When done well,

84-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

112-454: A blog post blaming Microsoft of involving people to improve and modify the accuracy of ODF and OpenXML Misplaced Pages articles. Legal Electronic Data Exchange Standard The Legal Electronic Data Exchange Standard is a set of file format specifications intended to facilitate electronic data transmission in the legal industry. The phrase is abbreviated LEDES and is usually pronounced as "leeds". The LEDES specifications are maintained by

140-1131: 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 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

168-553: A problem space into basic concepts, a reference model can be used to examine two different solutions to that problem. In doing so, the component parts of a solution can be discussed in relation to one another. For example, if a reference model describes computer systems that help track contacts between a business and their customers, then a reference model can be used by a business to decide which of five different software products to purchase, based on their needs. A reference model, in this example, could be used to compare how well each of

196-449: A problem that concerns a specific set of entities. For example, if a reference model describes a set of business measurements needed to create a balanced scorecard , then each measurement can be assigned to a specific business leader. That allows a senior manager to hold each of their team members responsible for producing high quality results. A fifth use of a reference model is to allow the comparison of different things. By breaking up

224-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

252-447: A standard can make use of design patterns that support key qualities of software, such as the ability to extend the software in an inexpensive way. Another use of a reference model is to educate. Using a reference model, leaders in software development can help break down a large problem space into smaller problems that can be understood, tackled, and refined. Developers who are new to a particular set of problems can quickly learn what

280-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

308-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

SECTION 10

#1732801142046

336-428: Is based on a small number of unifying concepts and may be used as a basis for education and explaining standards to a non-specialist. A reference model is not directly tied to any standards, technologies or other concrete implementation details, but it does seek to provide a common semantics that can be used unambiguously across and between different implementations." There are a number of concepts rolled up into that of

364-536: Is often an explicit recognition of concepts that many people already share, but when created in an explicit manner, a reference model is useful by defining how these concepts differ from, and relate to, one another. This improves communication between individuals involved in using these concepts. A fourth use of a reference model is to create clear roles and responsibilities. By creating a model of entities and their relationships, an organization can dedicate specific individuals or teams, making them responsible for solving

392-795: The LEDES Oversight Committee (LOC), which started informally as an industry-wide project led by the Law Firm and Law Department Services Group within PricewaterhouseCoopers in 1995. In 2001, the LEDES Oversight Committee was incorporated as a California mutual-benefit nonprofit corporation and is now led by a seven-member Board of Directors. The LOC maintains four types of data exchange standards for legal electronic billing (ebilling); budgeting; timekeeper attributes; and intellectual property matter management. The LOC also maintains five types of data elements in

420-608: The LEDES data exchange standards: Uniform Task-Based Management System codes, which classify the work performed by type of legal matter; activity codes, which classify the actual work performed; expense codes, which classify the type of expense incurred; timekeeper classification codes; and error codes, which assist law firms with understanding invoice validation errors. The LOC has also created an API that allows for system-to-system transmission of legal invoices from law firms and other legal vendors required by their clients to ebill, to

448-636: The candidate solutions can be configured to meet the needs of a particular business process. Instances of reference models include, among others: OASIS (organization) The Organization for the Advancement of Structured Information Standards ( OASIS ; / oʊ ˈ eɪ . s ɪ s / ) is a nonprofit consortium that works on 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

476-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

504-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

532-452: The different problems are, and can focus on the problems that they are being asked to solve, while trusting that other areas are well understood and rigorously constructed. The level of trust is important to allow software developers to efficiently focus on their work. A third use of a reference model is to improve communication between people. A reference model breaks up a problem into entities, or "things that exist all by themselves." This

560-491: The following variations: The other LEDES data exchange formats are as follows: The Uniform Task-Based Management System is a widely used system for coding legal work. In April 2006, the UTBMS Update Initiative voted to merge into the LEDES Oversight Committee. Shortly thereafter, the LEDES Oversight Committee established www.UTBMS.com as the global reference for all known UTBMS standards, regardless of

588-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

SECTION 20

#1732801142046

616-418: 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 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

644-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

672-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

700-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

728-413: The third-party ebilling systems. Other functionality is also supported in this very complex standard, which is intended to ease the burden at the law firm for managing client-required ebilling. The electronic billing data exchange format types provide a standard data format for electronically transmitted invoices, typically from a law firm to a corporate client. The LEDES e-billing format currently has

756-463: 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

784-492: 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 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

#45954