Misplaced Pages

#550449

66-489: 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

132-406: A Pathways to Enable Open-Source Ecosystems (POSE) program to support open source innovation. The adoption of open-source software by industry is increasing over time. OSS is popular in several industries such as telecommunications , aerospace , healthcare , and media & entertainment due to the benefits it provides. Adoption of OSS is more likely in larger organizations and is dependent on

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

264-591: 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

330-541: A bug needs to be fixed in their project. This is established by communicating with the OSS community through avenues such as bug reporting and tracking or mailing lists and project pages. Next, OSS developers select or are assigned to a task and identify a solution. Because there are often many different possible routes for solutions in OSS, the best solution must be chosen with careful consideration and sometimes even peer feedback . The developer then begins to develop and commit

396-507: A copy of the license is provided to recipients with the code. One important legal precedent for open-source software was created in 2008, when the Jacobson v Katzer case enforced terms of the Artistic license , including attribution and identification of modifications. The ruling of this case cemented enforcement under copyright law when the conditions of the license were not followed. Because of

462-454: A new bug. Early releases : The first version of the software should be released as early as possible so as to increase one's chances of finding co-developers early. Frequent integration: Code changes should be integrated (merged into a shared code base) as often as possible so as to avoid the overhead of fixing a large number of bugs at the end of the project life cycle. Some open-source projects have nightly builds where integration

528-1111: 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

594-508: A public good as it is available to everyone and does not decrease in value for others when downloaded by one person. Open source software is unique in that it becomes more valuable as it is used and contributed to, instead of diminishing the resource. This is explained by concepts such as investment in reputation and network effects . The economic model of open-source software can be explained as developers contribute work to projects, creating public benefits. Developers choose projects based on

660-447: A similar way user scripts and custom style sheets allow for web sites, and eventually publish the modification as a fork for users with similar preferences, and directly submit possible improvements as pull requests . The Open Source Initiative 's (OSI) definition is recognized by several governments internationally as the standard or de facto definition. OSI uses The Open Source Definition to determine whether it considers

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

#1732844273551

792-592: A software license open source. The definition was based on the Debian Free Software Guidelines , written and adapted primarily by Perens . Perens did not base his writing on the "four freedoms" from the Free Software Foundation (FSF), which were only widely available later. Under Perens' definition, open source is a broad software license that makes source code available to the general public with relaxed or non-existent restrictions on

858-449: 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

924-422: A victory for OSS supporters. In open-source communities, instead of owning the software produced, the producer owns the development of the evolving software. In this way, the future of the software is open, making ownership or intellectual property difficult within OSS. Licensing and branding can prevent others from stealing it, preserving its status as a public good . Open source software can be considered

990-501: 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

1056-443: Is computer software that is released under a license in which the copyright holder grants users the rights to use, study, change, and distribute the software and its source code to anyone and for any purpose. Open-source software may be developed in a collaborative, public manner. Open-source software is a prominent example of open collaboration , meaning any capable user is able to participate online in development, making

1122-404: Is a good or service, what can be considered a modification, governance through contract vs license, ownership and right of use. While there have been developments on these issues, they often lead to even more questions. The existence of these uncertainties in regulation has a negative impact on industries involved in technologies as a whole. Within the legal history of software as a whole, there

1188-539: Is absolutely another terrific way that individuals and organizations choose to contribute to open source projects. Groups like Open Collective provide a means for individuals to contribute monthly to supporting their favorite projects. Organizations like the Sovereign Tech Fund is able to contribute to millions to supporting the tools the German Government uses. The National Science Foundation established

1254-544: Is done automatically . Several versions: There should be at least two versions of the software. There should be a buggier version with more features and a more stable version with fewer features. The buggy version (also called the development version) is for users who want the immediate use of the latest features and are willing to accept the risk of using code that is not yet thoroughly tested. The users can then act as co-developers, reporting bugs and providing bug fixes. High modularization: The general structure of

1320-404: Is innovative since open-source programs are the product of collaboration among a large number of different programmers. The mix of divergent perspectives, corporate objectives, and personal goals speeds up innovation. Moreover, free software can be developed in accordance with purely technical requirements. It does not require thinking about commercial pressure that often degrades the quality of

1386-560: Is legal variety in this definition. Some jurisdictions attempt to expand or reduce this conceptualization for their own purposes. For example, The European Court of Justice defines a computer program as not including the functionality of a program, the programing language , or the format of data files. By limiting protections of the different aspects of software, the law favors an open-source approach to software use. The US especially has an open approach to software, with most open-source licenses originating there. However, this has increased

SECTION 20

#1732844273551

1452-468: Is theoretically challenging in economic models, it is explainable as a sustainable social activity that requires resources. These resources include time, money, technology and contributions. Many developers have used technology funded by organizations such as universities and governments, though these same organizations benefit from the work done by OSS. As OSS grows, hybrid systems containing OSS and proprietary systems are becoming more common. Throughout

1518-889: The distributed version control system (DVCS) are examples of tools, often open source, that help manage the source code files and the changes to those files for a software project in order to foster collaboration. CVCS are centralized with a central repository while DVCS are decentralized and have a local repository for every user. concurrent versions system (CVS) and later Subversion (SVN) and Git are examples of CVCS. The repositories are hosted and published on source-code-hosting facilities such as GitHub . Open-source projects use utilities such as issue trackers to organize open-source software development. Commonly used bug trackers include Bugzilla and Redmine . Tools such as mailing lists and IRC provide means of coordination and discussion of bugs among developers. Project web pages, wiki pages, roadmap lists and newsgroups allow for

1584-458: The Bazaar , open-source influential contributor Eric S. Raymond suggests a model for developing OSS known as the bazaar model. Raymond likens the development of software by traditional methodologies to building a cathedral, with careful isolated work by individuals or small groups. He suggests that all software should be developed using the bazaar style, with differing agendas and approaches. In

1650-580: 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

1716-535: 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. Open source software This is an accepted version of this page Open-source software ( OSS )

1782-630: The Public Interest . Within Europe some notable organizations are Free Software Foundation Europe , open-source projects EU (OSP) and OpenForum Europe (OFE). One Australian organization is Linux Australia while Asia has Open source Asia and FOSSAsia . Free and open source software for Africa (FOSSFA) and OpenAfrica are African organizations and Central and South Asia has such organizations as FLISOL and GRUP de usuarios de software libre Peru . Outside of these, many more organizations dedicated to

1848-569: The United States has focused on national security in regard to open-source software implementation due to the perceived threat of the increase of open-source software activity in countries like China and Russia, with the Department of Defense considering multiple criteria for using OSS. These criteria include: if it comes from and is maintained by trusted sources, whether it will continue to be maintained, if there are dependencies on sub-components in

1914-473: The advancement of open-source software exist. FOSS products are generally licensed under two types of licenses: permissive licensing and copyleft licensing . Both of these types of licenses are different than proprietary licensing in that they can allow more users access to the software and allow for the creation of derivative works as specified by the terms of the specific license, as each license has its own rules. Permissive licenses allow recipients of

1980-402: The bazaar model should exhibit the following patterns: Users should be treated as co-developers: The users are treated like co-developers and so they should have access to the source code of the software. Furthermore, users are encouraged to submit additions to the software, code fixes for the software, bug reports , documentation, etc. Having more co-developers increases the rate at which

2046-414: The code. The code is then tested and reviewed by peers. Developers can edit and evolve their code through feedback from continuous integration . Once the leadership and community are satisfied with the whole project, it can be partially released and user instruction can be documented. If the project is ready to be released, it is frozen, with only serious bug fixes or security repairs occurring. Finally,

OASIS (organization) - Misplaced Pages Continue

2112-427: The company's IT usage, operating efficiencies, and the productivity of employees. Industries are likely to use OSS due to back-office functionality, sales support, research and development, software features, quick deployment, portability across platforms and avoidance of commercial license management. Additionally, lower cost for hardware and ownership are also important benefits. Organizations that contribute to

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

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

2310-467: The development and expansions of free and open-source software movements exist all over the world. These organizations are dedicated to goals such as teaching and spreading technology. As listed by a former vice president of the Open Source Initiative , some American organizations include the Free Software Foundation , Software Freedom Conservancy , the Open Source Initiative and Software in

2376-461: The distribution of project information that focuses on end users. The basic roles OSS participants can fall into multiple categories, beginning with leadership at the center of the project who have control over its execution. Next are the core contributors with a great deal of experience and authority in the project who may guide the other contributors. Non-core contributors have less experience and authority, but regularly contribute and are vital to

2442-601: The focus on patent rights within these licenses, which has seen backlash from the OSS community, who prefer other forms of IP protection. Another issue includes technological protection measures (TPM) and digital rights management (DRM) techniques which were internationally legally recognized and protected in the 1996 World Intellectual Property Organization (WIPO) Treaty . Open source software proponents disliked these technologies as they constrained end-users potentially beyond copyright law. Europe responded to such complaints by putting TPM under legal controls, representing

2508-560: 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

2574-539: 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

2640-480: The many benefits provided, a huge issue to be considered is cybersecurity . While accidental vulnerabilities are possible, so are attacks by outside agents. Because of these fears, governmental interest in contributing to the governance of software has become more prominent. However, these are the broad strokes of the issue, with each country having their own specific politicized interactions with open-source software and their goals for its implementation. For example,

2706-560: The mid 2000s, more and more tech companies have begun to use OSS. For example, Dell's move of selling computers with GNU/Linux already installed. Microsoft itself has launched a Linux-based operating system despite previous animosity with the OSS movement. Despite these developments, these companies tend to only use OSS for certain purposes, leading to worries that OSS is being taken advantage of by corporations and not given anything in return. While many governments are interested in implementing and promoting open-source software due to

OASIS (organization) - Misplaced Pages Continue

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

2838-505: The number of people employed in the IT sector. OSS can be highly reliable when it has thousands of independent programmers testing and fixing bugs of the software. Open source is not dependent on the company or author that originally created it. Even if the company fails, the code continues to exist and be developed by its users. OSS is flexible because modular systems allow programmers to build custom interfaces, or add new abilities to it and it

2904-537: The number of possible contributors indefinite. The ability to examine the code facilitates public trust in the software. Open-source software development can bring in diverse perspectives beyond those of a single company. A 2024 estimate of the value of open-source software to firms is $ 8.8 trillion, as firms would need to spend 3.5 times the amount they currently do without the use of open source software. Open-source code can be used for studying and allows capable end users to adapt software to their personal needs in

2970-435: The perceived benefits or costs, such as improved reputation or value of the project. The motivations of developers can come from many different places and reasons, but the important takeaway is that money is not the only or even most important incentivization . Because economic theory mainly focuses on the consumption of scarce resources, the OSS dynamic can be hard to understand. In OSS, producers become consumers by reaping

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

3102-404: The potential to quicken innovation and create of social value. In France for instance, a policy that incentivized government to favor free open-source software increased to nearly 600,000 OSS contributions per year, generating social value by increasing the quantity and quality of open-source software. This policy also led to an estimated increase of up to 18% of tech startups and a 14% increase in

3168-574: The project is fully released and only changed through minor bug fixes. Open source implementation of a standard can increase adoption of that standard. This creates developer loyalty as developers feel empowered and have a sense of ownership of the end product. Moreover, lower costs of marketing and logistical services are needed for OSS. OSS can be a tool to promote a company's image, including its commercial products. The OSS development approach has helped produce reliable, high quality software quickly and inexpensively. Open source development offers

3234-759: The project's development. New contributors are the least experienced but with mentorship and guidance can become regular contributors. Some possible ways of contributing to open-source software include such roles as programming , user interface design and testing, web design , bug triage , accessibility design and testing, UX design , code testing, and security review and testing. However, there are several ways of contributing to OSS projects even without coding skills. For example, some less technical ways of participating are documentation writing and editing, translation , project management , event organization and coordination, marketing, release management, community management, and public relations and outreach. Funding

3300-532: 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

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

SECTION 50

#1732844273551

3432-431: The rewards of contributing to a project. For example, a developer becomes well regarded by their peers for a successful contribution to an OSS project. The social benefits and interactions of OSS are difficult to account for in economic models as well. Furthermore, the innovation of technology creates constantly changing value discussions and outlooks, making economic model unable to predict social behavior. Although OSS

3498-490: The same license while weak copyleft licenses require the use of the same license only under certain conditions. Examples of this type of license include the GNU family of licenses , and the MPL and EPL licenses. The similarities between these two categories of licensing include that they provide a broad grant of copyright rights, require that recipients preserve copyright notices, and that

3564-500: The similarity of the Artistic license to other open-source software licenses, the ruling created a precedent that applied widely. Examples of free-software license / open-source licenses include Apache licenses , BSD licenses , GNU General Public Licenses , GNU Lesser General Public License , MIT License , Eclipse Public License and Mozilla Public License . Several gray areas exist within software regulation that have great impact on open-source software, such as if software

3630-485: The software "in any manner they see fit, without requiring that they pay the author(s) of the software a royalty or fee for engaging in the listed activities." Despite initially accepting it, Richard Stallman of the FSF now flatly opposes the term "Open Source" being applied to what they refer to as "free software". Although he agrees that the two terms describe "almost the same category of software", Stallman considers equating

3696-401: The software evolves. Linus's law states that given enough eyeballs all bugs are shallow. This means that if many users view the source code, they will eventually find all bugs and suggest how to fix them. Some users have advanced programming skills, and furthermore, each user's machine provides an additional testing environment. This new testing environment offers the ability to find and fix

3762-484: The software should be modular allowing for parallel development on independent components. Dynamic decision-making structure: There is a need for a decision-making structure, whether formal or informal, that makes strategic decisions depending on changing user requirements and other factors. Compare with extreme programming . The process of Open source development begins with a requirements elicitation where developers consider if they should add new features or if

3828-453: The software to implement the author's copyright rights without having to use the same license for distribution. Examples of this type of license include the BSD , MIT , and Apache licenses . Copyleft licenses are different in that they require recipients to use the same license for at least some parts of the distribution of their works. Strong copyleft licenses require all derivative works to use

3894-568: The software, component security and integrity, and foreign governmental influence. Another issue for governments in regard to open source is their investments in technologies such as operating systems , semiconductors , cloud , and artificial intelligence . These technologies all have implications for global cooperation, again opening up security issues and political consequences. Many countries have to balance technological innovation with technological dependence in these partnerships. For example, after China's open-source dependent company Huawei

3960-425: The software. Commercial pressures make traditional software developers pay more attention to customers' requirements than to security requirements, since such features are somewhat invisible to the customer. In open-source software development, tools are used to support the development of the product and the development process itself. Version control systems such as Centralized Version control system (CVCS) and

4026-597: The terms incorrect and misleading. Stallman also opposes the professed pragmatism of the Open Source Initiative , as he fears that the free software ideals of freedom and community are threatened by compromising on the FSF's idealistic standards for software freedom. The FSF considers free software to be a subset of open-source software, and Richard Stallman explained that DRM software, for example, can be developed as open source, despite that it does not give its users freedom (it restricts them), and thus does not qualify as free software. In his 1997 essay The Cathedral and

SECTION 60

#1732844273551

4092-514: The traditional model of development, which he called the cathedral model, development takes place in a centralized way. Roles are clearly defined. Roles include people dedicated to designing (the architects), people responsible for managing the project, and people responsible for implementation. Traditional software engineering follows the cathedral model. The bazaar model, however, is different. In this model, roles are not clearly defined. Some proposed characteristics of software developed using

4158-437: The use and modification of the code. It is an explicit "feature" of open source that it puts very few restrictions on the use or distribution by any organization or user, in order to enable the rapid evolution of the software. According to Feller et al. (2005), the terms "free software" and "open-source software" should be applied to any "software products distributed under terms that allow users" to use, modify, and redistribute

4224-455: 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

4290-404: Was much debate on whether to protect it as intellectual property under patent law , copyright law or establishing a unique regulation. Ultimately, copyright law became the standard with computer programs being considered a form of literary work, with some tweaks of unique regulation. Software is generally considered source code and object code , with both being protectable, though there

4356-552: 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,

#550449