Misplaced Pages

OASIS (organization)

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

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.

#415584

67-497: 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 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

134-428: A negative or positive liberty . Due to their restrictions on distribution, not everyone considers copyleft licenses to be free. Conversely, a permissive license may provide an incentive to create non-free software by reducing the cost of developing restricted software. Since this is incompatible with the spirit of software freedom, many people consider permissive licenses to be less free than copyleft licenses. There

201-401: 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

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

335-529: A copy of the free application itself. Fees are usually charged for distribution on compact discs and bootable USB drives, or for services of installing or maintaining the operation of free software. Development of large, commercially used free software is often funded by a combination of user donations, crowdfunding , corporate contributions, and tax money. The SELinux project at the United States National Security Agency

402-561: A fee. The Free Software Foundation encourages selling free software. As the Foundation has written, "distributing free software is an opportunity to raise funds for development. Don't waste it!". For example, the FSF's own recommended license (the GNU GPL ) states that "[you] may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for

469-450: A fee." Microsoft CEO Steve Ballmer stated in 2001 that "open source is not available to commercial companies. The way the license is written, if you use any open-source software, you have to make the rest of your software open source." This misunderstanding is based on a requirement of copyleft licenses (like the GPL) that if one distributes modified versions of software, they must release

536-494: A for-profit, commercial activity or not. Some free software is developed by volunteer computer programmers while other is developed by corporations; or even by both. Although both definitions refer to almost equivalent corpora of programs, the Free Software Foundation recommends using the term "free software" rather than " open-source software " (an alternative, yet similar, concept coined in 1998), because

603-1130: 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

670-571: A significant part in the development of the Internet, the World Wide Web and the infrastructure of dot-com companies . Free software allows users to cooperate in enhancing and refining the programs they use; free software is a pure public good rather than a private good . Companies that contribute to free software increase commercial innovation . "We migrated key functions from Windows to Linux because we needed an operating system that

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

SECTION 10

#1732771890416

804-498: A small set of licenses. The most popular of these licenses are: The Free Software Foundation and the Open Source Initiative both publish lists of licenses that they find to comply with their own definitions of free software and open-source software respectively: The FSF list is not prescriptive: free-software licenses can exist that the FSF has not heard about, or considered important enough to write about. So it

871-452: 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

938-505: 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

1005-617: Is an example of a federally funded free-software project. Proprietary software, on the other hand, tends to use a different business model, where a customer of the proprietary application pays a fee for a license to legally access and use it. This license may grant the customer the ability to configure some or no parts of the software themselves. Often some level of support is included in the purchase of proprietary software, but additional support services (especially for enterprise applications) are usually available for an additional fee. Some proprietary software vendors will also customize software for

1072-466: Is biased by counting more vulnerabilities for the free software systems, since their source code is accessible and their community is more forthcoming about what problems exist as a part of full disclosure , and proprietary software systems can have undisclosed societal drawbacks, such as disenfranchising less fortunate would-be users of free programs. As users can analyse and trace the source code, many more people with no commercial constraints can inspect

1139-471: Is computer software distributed under terms that allow users to run the software for any purpose as well as to study, change, and distribute it and any adapted versions. Free software is a matter of liberty , not price; all users are legally free to do what they want with their copies of a free software (including profiting from them) regardless of how much is paid to obtain the program. Computer programs are deemed "free" if they give end-users (not just

1206-545: Is consistent with the intended meaning unlike the term "Open Source". The loan adjective " libre " is often used to avoid the ambiguity of the word "free" in the English language , and the ambiguity with the older usage of "free software" as public-domain software. ( See Gratis versus libre . ) The first formal definition of free software was published by FSF in February 1986. That definition, written by Richard Stallman ,

1273-451: Is debate over the security of free software in comparison to proprietary software, with a major issue being security through obscurity . A popular quantitative test in computer security is to use relative counting of known unpatched security flaws. Generally, users of this method advise avoiding products that lack fixes for known security flaws, at least until a fix is available. Free software advocates strongly believe that this methodology

1340-463: Is like considering the practical advantages of not being handcuffed, in that it is not necessary for an individual to consider practical reasons in order to realize that being handcuffed is undesirable in itself. The FSF also notes that "Open Source" has exactly one specific meaning in common English, namely that "you can look at the source code." It states that while the term "Free Software" can lead to two different interpretations, at least one of them

1407-419: Is not covered by copyright law, such as software in the public domain , is free as long as the source code is also in the public domain, or otherwise available without restrictions. Proprietary software uses restrictive software licences or EULAs and usually does not provide users with the source code. Users are thus legally or technically prevented from changing the software, and this results in reliance on

SECTION 20

#1732771890416

1474-495: Is not endorsed by the FSF and does not use Linux-libre, it is also a popular distribution available without kernel blobs by default since 2011. The Linux community uses the term "blob" to refer to all nonfree firmware in a kernel whereas OpenBSD uses the term to refer to device drivers. The FSF does not consider OpenBSD to be blob free under the Linux community's definition of blob. Selling software under any free-software licence

1541-601: Is not in the IT sector choose free software for their Internet information and sales sites, due to the lower initial capital investment and ability to freely customize the application packages. Most companies in the software business include free software in their commercial products if the licenses allow that. Free software is generally available at no cost and can result in permanently lower TCO ( total cost of ownership ) compared to proprietary software . With free software, businesses can fit software to their specific needs by changing

1608-415: Is permissible, as is commercial use. This is true for licenses with or without copyleft . Since free software may be freely redistributed, it is generally available at little or no fee. Free software business models are usually based on adding value such as customization, accompanying hardware, support, training, integration, or certification. Exceptions exist however, where the user is charged to obtain

1675-521: Is possible for a license to be free and not in the FSF list. The OSI list only lists licenses that have been submitted, considered and approved. All open-source licenses must meet the Open Source Definition in order to be officially recognized as open source software. Free software, on the other hand, is a more informal classification that does not rely on official recognition. Nevertheless, software licensed under licenses that do not meet

1742-644: Is still maintained today and states that software is free software if people who receive a copy of the software have the following four freedoms. The numbering begins with zero, not only as a spoof on the common usage of zero-based numbering in programming languages, but also because "Freedom 0" was not initially included in the list, but later added first in the list as it was considered very important. Freedoms 1 and 3 require source code to be available because studying and modifying software without its source code can range from highly impractical to nearly impossible. Thus, free software means that computer users have

1809-613: Is summarized at the Debian web site. It is rare that a license announced as being in-compliance with the FSF guidelines does not also meet the Open Source Definition , although the reverse is not necessarily true (for example, the NASA Open Source Agreement is an OSI-approved license, but non-free according to FSF). There are different categories of free software. Proponents of permissive and copyleft licenses disagree on whether software freedom should be viewed as

1876-756: The Apache web server; and the Sendmail mail transport agent. Other influential examples include the Emacs text editor; the GIMP raster drawing and image editor; the X Window System graphical-display system; the LibreOffice office suite; and the TeX and LaTeX typesetting systems. From the 1950s up until the early 1970s, it was normal for computer users to have the software freedoms associated with free software, which

1943-458: The GNU Project : a collaborative effort to create a freedom-respecting operating system , and to revive the spirit of cooperation once prevalent among hackers during the early days of computing. Free software differs from: For software under the purview of copyright to be free, it must carry a software license whereby the author grants users the aforementioned rights. Software that

2010-830: The GNU operating system began in January 1984, and the Free Software Foundation (FSF) was founded in October 1985. He developed a free software definition and the concept of " copyleft ", designed to ensure software freedom for all. Some non-software industries are beginning to use techniques similar to those used in free software development for their research and development process; scientists, for example, are looking towards more open development processes, and hardware such as microchips are beginning to be developed with specifications released under copyleft licenses ( see

2077-744: The Linux kernel and other device drivers motivated some developers in Ireland to launch gNewSense , a Linux-based distribution with all the binary blobs removed. The project received support from the Free Software Foundation and stimulated the creation, headed by the Free Software Foundation Latin America , of the Linux-libre kernel. As of October 2012 , Trisquel is the most popular FSF endorsed Linux distribution ranked by Distrowatch (over 12 months). While Debian

OASIS (organization) - Misplaced Pages Continue

2144-661: The OpenCores project, for instance ). Creative Commons and the free-culture movement have also been largely influenced by the free software movement. In 1983, Richard Stallman , longtime member of the hacker community at the MIT Artificial Intelligence Laboratory , announced the GNU Project, saying that he had become frustrated with the effects of the change in culture of the computer industry and its users. Software development for

2211-410: The source code was distributed to use these programs. Software was also shared and distributed as printed source code ( Type-in program ) in computer magazines (like Creative Computing , SoftSide , Compute! , Byte , etc.) and books, like the bestseller BASIC Computer Games . By the early 1970s, the picture changed: software costs were dramatically increasing, a growing software industry

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

2345-560: The EPC. The differences in interpretation had led to serious interoperability problems. To resolve these differences, OASIS identified a subset of the full CALS table model that had a high probability of successful interoperability among the OASIS vendor products. This subset is the Exchange Table Model DTD. Free software Free software , libre software , libreware sometimes known as freedom-respecting software

2412-557: The Free Software Definition cannot rightly be considered free software. Apart from these two organizations, the Debian project is seen by some to provide useful advice on whether particular licenses comply with their Debian Free Software Guidelines . Debian does not publish a list of approved licenses, so its judgments have to be tracked by checking what software they have allowed into their software archives. That

2479-631: The GNU operating system began in January 1984, and the Free Software Foundation (FSF) was founded in October 1985. An article outlining the project and its goals was published in March 1985 titled the GNU Manifesto . The manifesto included significant explanation of the GNU philosophy, Free Software Definition and " copyleft " ideas. The Linux kernel , started by Linus Torvalds , was released as freely modifiable source code in 1991. The first licence

2546-525: The Internet. Users can easily download and install those applications via a package manager that comes included with most Linux distributions . The Free Software Directory maintains a large database of free-software packages. Some of the best-known examples include Linux-libre , Linux-based operating systems, the GNU Compiler Collection and C library ; the MySQL relational database;

2613-588: The code and find bugs and loopholes than a corporation would find practicable. According to Richard Stallman, user access to the source code makes deploying free software with undesirable hidden spyware functionality far more difficult than for proprietary software. Some quantitative studies have been done on the subject. In 2006, OpenBSD started the first campaign against the use of binary blobs in kernels . Blobs are usually freely distributable device drivers for hardware from vendors that do not reveal driver source code to users or developers. This restricts

2680-440: 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

2747-453: 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

OASIS (organization) - Misplaced Pages Continue

2814-435: The developer) ultimate control over the software and, subsequently, over their devices. The right to study and modify a computer program entails that the source code —the preferred format for making changes—be made available to users of that program. While this is often called "access to source code" or "public availability", the Free Software Foundation (FSF) recommends against thinking in those terms, because it might give

2881-572: 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

2948-423: The freedom to cooperate with whom they choose, and to control the software they use. To summarize this into a remark distinguishing libre (freedom) software from gratis (zero price) software, the Free Software Foundation says: "Free software is a matter of liberty, not price. To understand the concept, you should think of 'free' as in ' free speech ', not as in 'free beer ' ". ( See Gratis versus libre . ) In

3015-412: The goals and messaging are quite dissimilar. According to the Free Software Foundation, "Open source" and its associated campaign mostly focus on the technicalities of the public development model and marketing free software to businesses, while taking the ethical issue of user rights very lightly or even antagonistically. Stallman has also stated that considering the practical advantages of free software

3082-409: The government charged that bundled software was anti-competitive . While some software might always be free, there would henceforth be a growing amount of software produced primarily for sale. In the 1970s and early 1980s, the software industry began using technical measures (such as only distributing binary copies of computer programs ) to prevent computer users from being able to study or adapt

3149-513: The impression that users have an obligation (as opposed to a right) to give non-users a copy of the program. Although the term "free software" had already been used loosely in the past and other permissive software like the Berkeley Software Distribution released in 1978 existed, Richard Stallman is credited with tying it to the sense under discussion and starting the free software movement in 1983, when he launched

3216-555: 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

3283-421: The late 1990s, other groups published their own definitions that describe an almost identical set of software. The most notable are Debian Free Software Guidelines published in 1997, and The Open Source Definition , published in 1998. The BSD -based operating systems, such as FreeBSD , OpenBSD , and NetBSD , do not have their own formal definitions of free software. Users of these systems generally find

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

3417-448: 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 50

#1732771890416

3484-468: The publisher to provide updates, help, and support. ( See also vendor lock-in and abandonware ). Users often may not reverse engineer , modify, or redistribute proprietary software. Beyond copyright law, contracts and a lack of source code, there can exist additional obstacles keeping users from exercising freedom over a piece of software, such as software patents and digital rights management (more specifically, tivoization ). Free software can be

3551-481: 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

3618-549: 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

3685-511: The same set of software to be acceptable, but sometimes see copyleft as restrictive. They generally advocate permissive free software licenses , which allow others to use the software as they wish, without being legally forced to provide the source code. Their view is that this permissive approach is more free. The Kerberos , X11 , and Apache software licenses are substantially similar in intent and implementation. There are thousands of free applications and many operating systems available on

3752-435: The shift in climate surrounding the computer world and its users. In his initial declaration of the project and its purpose, he specifically cited as a motivation his opposition to being asked to agree to non-disclosure agreements and restrictive licenses which prohibited the free sharing of potentially profitable in-development software, a prohibition directly contrary to the traditional hacker ethic . Software development for

3819-461: The software applications as they saw fit. In 1980, copyright law was extended to computer programs. In 1983, Richard Stallman , one of the original authors of the popular Emacs program and a longtime member of the hacker community at the MIT Artificial Intelligence Laboratory , announced the GNU Project , the purpose of which was to produce a completely non-proprietary Unix-compatible operating system, saying that he had become frustrated with

3886-443: The software themselves or by hiring programmers to modify it for them. Free software often has no warranty, and more importantly, generally does not assign legal liability to anyone. However, warranties are permitted between any two parties upon the condition of the software and its usage. Such an agreement is made separately from the free software license. A report by Standish Group estimates that adoption of free software has caused

3953-411: The source and use the same license. This requirement does not extend to other software from the same developer. The claim of incompatibility between commercial companies and free software is also a misunderstanding. There are several large companies, e.g. Red Hat and IBM (IBM acquired RedHat in 2019), which do substantial commercial business in the development of free software. Free software played

4020-495: The users' freedom effectively to modify the software and distribute modified versions. Also, since the blobs are undocumented and may have bugs , they pose a security risk to any operating system whose kernel includes them. The proclaimed aim of the campaign against blobs is to collect hardware documentation that allows developers to write free software drivers for that hardware, ultimately enabling all free operating systems to become or remain blob-free. The issue of binary blobs in

4087-620: Was a proprietary software licence. However, with version 0.12 in February 1992, he relicensed the project under the GNU General Public License . Much like Unix, Torvalds' kernel attracted the attention of volunteer programmers. FreeBSD and NetBSD (both derived from 386BSD ) were released as free software when the USL v. BSDi lawsuit was settled out of court in 1993. OpenBSD forked from NetBSD in 1995. Also in 1995, The Apache HTTP Server , commonly referred to as Apache,

SECTION 60

#1732771890416

4154-462: 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

4221-402: Was competing with the hardware manufacturer's bundled software products (free in that the cost was included in the hardware cost), leased machines required software support while providing no revenue for software, and some customers able to better meet their own needs did not want the costs of "free" software bundled with hardware product costs. In United States vs. IBM , filed January 17, 1969,

4288-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,

4355-476: Was released under the Apache License 1.0 . All free-software licenses must grant users all the freedoms discussed above. However, unless the applications' licenses are compatible, combining programs by mixing source code or directly linking binaries is problematic, because of license technicalities . Programs indirectly connected together may avoid this problem. The majority of free software falls under

4422-679: Was stable and reliable – one that would give us in-house control. So if we needed to patch, adjust, or adapt, we could." Official statement of the United Space Alliance , which manages the computer systems for the International Space Station (ISS), regarding their May 2013 decision to migrate ISS computer systems from Windows to Linux The economic viability of free software has been recognized by large corporations such as IBM , Red Hat , and Sun Microsystems . Many companies whose core business

4489-407: Was typically public-domain software . Software was commonly shared by individuals who used computers and by hardware manufacturers who welcomed the fact that people were making software that made their hardware useful. Organizations of users and suppliers, for example, SHARE , were formed to facilitate exchange of software. As software was often written in an interpreted language such as BASIC ,

#415584