Knowledge Tree
Project Specification
Also known as: PS, Project Specifications
Facts (13)
Sources
Open Project Rules - OASIS Open oasis-open.org 13 facts
claimMembers of an Open Project’s Governing Board (PGB) for a project with an Implementer-Class License must irrevocably covenant not to assert patent claims licensable by them that are necessarily infringed by an implementation of a Project Specification approved by that Open Project, within the scope of its Charter, against OASIS or parties benefiting from the Applicable License.
procedureBefore an approval ballot for a Project Specification is opened, the Open Project Administrator must review and confirm the conformance of the proposed Project Specification.
claimContributors to an OASIS Open Project irrevocably covenant not to assert any patent claims licensable by them that are necessarily infringed by an implementation of their contribution, provided that the contribution is included in a Project Specification approved by the Open Project.
procedureThe Project Governing Board (PGB) is responsible for selecting and replacing Chairs, ensuring there are one or more Maintainers for any Project Repository, consulting with Maintainers on technical decisions, establishing and consulting with Technical Steering Committees (TSC), and approving Draft Project Specifications, Project Specifications, Candidates for OASIS Standards, or external submissions.
procedureOASIS Open Projects may designate specific portions of their output as official Releases, Group Releases, Project Specification Drafts, or Project Specifications, and nominate them for further advancement.
procedureA Project Specification becomes eligible for approval as an OASIS Standard after three Statements of Use referencing the specification have been presented to the Project Governing Board (PGB).
procedureThe OASIS Open Project Administrator must post every important change in project status to the official announcement list, including project formation, opening of new repositories, releases, group releases, draft project specifications, project specifications, candidate OASIS standards, and proposed external submissions.
procedureUpon the successful conclusion of a Special Majority Vote for a Project Specification, the Open Project Administrator must provide public written notice of the approval and publish the specification to the OASIS Library.
claimProject Specifications in OASIS Open may carry multiple Applicable Licenses if they are composed of Releases or Group Releases sourced from multiple Project Repositories that have different licenses.
claimProject Governing Boards (PGBs) in OASIS Open are prohibited from designating any single implementation of a Project Specification as exclusive or privileged.
claimThe Project Governing Board (PGB) cannot delegate the election or termination of PGB Chairs, the approval of Releases, Group Releases, Project Specification Drafts, Project Specifications, or the approval of Candidates for OASIS Standards or external submissions.
procedureTo advance a Release or Group Release as a Project Specification Draft (PSD) or Project Specification (PS) in an OASIS Open Project, the proposal must conform to the Project Specification template provided by the Open Project Administrator, which includes methods for identifying Designated Branches and Applicable Licenses.
procedureOnce three Statements of Use are presented, a Project Governing Board (PGB) with at least Project Approval Minimum Membership may approve a Project Specification as a candidate for an OASIS Standard, following the same requirements as those for Committee Specifications in the OASIS TC Process.