Eugene Eric Kim <eekim@eekim.com>
Version
1.0
November 8, 2001
Decades of work have gone into the Open Hyperdocument System (OHS), resulting in a set of requirements, a prototype (NLS/Augment), and a considerable amount of experience. The next challenge is to define a set of technical specifications for a standard OHS infrastructure on which all OHS applications shall be built. 1A (030)
These bylaws prescribe the initial structure and procedures of the OHS Working Group (OHS-WG), whose purpose is to develop these technical specifications, and to facilitate the coevolution between the OHS and its user communities. 1B (031)
The OHS-WG shall be made up of "members" and "participants." Anyone may participate on the OHS-WG; however, only members will be eligible to vote on specifications and to nominate other members. Members and participants will consist mostly of developers of OHS candidate applications -- software that meet some or all of the stated requirements of the OHS, and that will interoperate with other OHS applications once the proper infrastructure is in place. 1C (032)
The OHS-WG must interact closely with OHS user communities. As user communities evolve the OHS requirements, the OHS-WG must evolve its technical specifications accordingly. In order to facilitate this coevolution, the OHS-WG shall be a member community of the Bootstrap Alliance, and as such, shall ultimately be directly accountable to the members of the Bootstrap Alliance. 1D (033)
The structure and procedures of the OHS-WG must also evolve, so that it may continue to meet the evolving needs of its stakeholders. The Bootstrap Alliance Core Planning Committee (CPC) may revise these bylaws as it sees fit, and will reevaluate these bylaws after six months. 1E (034)
In the near future, the OHS-WG shall incorporate a non-confidentiality agreement for those who wish to participate in discussions, and a certification process for candidate OHS specifications. 1F (035)
The Open Hyperdocument System (OHS) Working Group (OHS-WG) shall be a member community of the Bootstrap Alliance, and shall be responsible for developing the official specifications for the OHS. 2A (02)
The OHS-WG shall consist of a chair, an advisory board, members, and participants. 3A (09)
The Bootstrap Alliance Core Planning Committee (CPC) shall appoint the chair, who shall be responsible for overseeing the OHS-WG's overall operations, putting together an advisory board of non-members, and delegating tasks to other members. The chair may create other formal roles as he or she sees fit. 3B (010)
Members shall have the privilege to vote in the OHS-WG's standards process, to nominate other members, and to participate in the OHS-WG's private forums. 3C (011)
The CPC will reevaluate this governance structure after six months, with the entire structure subject to revision. 3D (012)
The initial members of the OHS-WG will be selected by the CPC. Members of the OHS-WG shall have the following attributes: 4A (014)
OHS-WG members may nominate other individuals for membership. If a nominee is seconded by one other OHS-WG member and approved by the CPC, the nominee will become a member of the OHS-WG. 4C (019)
Members and participants may propose an OHS standard. People making proposals shall: 5A (021)
Draft proposals shall undergo a cycle of feedback and revision, until they are categorized as final recommendations. Members shall have one week following the publication date of the final recommendation to vote on the proposal. The proposal shall become an official standard if two-thirds of the members voting vote in its favor. 5C (025)