The STAR organization is operated by representatives from our member organizations who vote on all major issues. Issues that do not require a member-wide vote are decided by the STAR Steering Committee, whose members are elected from within the general member organization.
STAR Release Process
STAR releases a new version of the STAR Standards on a yearly basis. New content and changes are decided on by representatives of STAR's current member organizations. Below is a description of how the STAR Standards are modified, released to the public, and the voting process amongst the members.
Process For Creating New Standards
Projects for new standards are member driven. The development of new content can be suggested by any member. Prior to any resources being expanded on the suggestion, the membership must vote to approve the project. A new request may be submitted at any time. The new content fulfillment process is as follows:
1. Member downloads and completes an XML Schema/BOD Value Statement form
2. Member creates a new issue in the issue tracking system on the STAR Member's portal and attaches the completed Value Statement form
3. STAR Data Architects will then set up a review session among the members to review and vote on the request
4. Once approved, a workgroup will be set up for all of those STAR Members wishing to participate. Workgroup members will be asked to complete use cases, sequence diagrams and data requirements.
5. STAR Data Architects will then develop the schemas that correspond to the new BOD
Process For Modification of Existing Standards
The proces for modifying and existing standard is as follows:
1. Member downloads and completes a XML Schema/BOD Modification Request form
2. Member creates a new issue in the issue tracking system on the STAR Member's portal and attaches the completed Modification Request form
3. STAR Data Architects will then set up a review session among the members to review the request
4. Once the workgroup has agreed to the requirements, STAR Data Architects will modify the specification based on the request
5. All projects and changes will be posted and made available to STAR members on the Portal in the next milestone release
STAR publishes new content once per year during the month of May. The new standards take effect on July 4th each year. Prior to publication, representatives of each member organization must vote to approve the public release of the new content.
New content is available to members throughout the year in the following forms:
1. Milestones: Snapshots of the repository that are published every two weeks.
2. Draft Releases: Draft versions of the new standards that are published four times per year. Members are permitted to implement draft versions but are cautioned that they may change between the draft and the final release in July.
3. Release Candidate: A pre-release draft of the standards used to validate the content and allow for necessary fixes and modifications
4. Final Draft: The final release of the standards to be voted on by the general membership. If approved, the specifications are released in late March.
Members may begin implementing the new standards at the time of the Final Draft release but are cautioned that changes may be made before official vote and publication.
STAR VOTING PROCESS
Voting applies to the Final Draft release only. Based on the STAR Bylaws "Resolution 2. STAR Voting Structure & Quorum Descriptions" section, STAR requires that a minimum of 50% of the active members participate in the voting process, and an affirmative vote of 75% to pass. The vote remains open for a period of no less than four weeks during the month of April, during which time the member representatives may submit their vote. Votes not received during the designated period will be counted as abstaining. The STAR Steering Committee reserves the right to reschedule the dates of the vote and subsequent publication of the new standards.