The OSLC Core defines essential elements of OSLC specs and offers guidance on common concerns for creating, updating, retrieving, and linking to lifecycle resources. The Core specification builds on the best practices we’ve learned as a community and on the work of the existing domain work groups. Future OSLC domain specifications can be based on this core specification, enabling other workgroups to focus more exclusively on domain-specific concerns.
The OSLC Core Workgroup defines essential technical elements of OSLC specifications and offers guidance on common concerns for creating, updating, retrieving, and linking to lifecycle resources. The Core specification builds on the best practices we've learned as a community and on the work of the existing domain work groups. Future OSLC domain specifications will be based on this core specification, enabling other workgroups to focus more exclusively on domain-specific concerns.
The Core Workgroup will produce:
- Scenarios – these will guide the priorities and specification contents within the Workgroup
- Specifications – both maintenance of existing specifications, guidance on usage and new specification
- Supporting and enabling material – on an as-needed basis to support broad adoption
Relationship to other activities and workgroups
The Core Workgroup is a cross-OSLC workgroup formed to drive the ongoing creation, maintenance, and adoption of the Core Specification. The workgroup includes the leads from the various domain workgroups and anyone else from the OSLC community who wishes to participate.
The Core Workgroup also provides overall technical direction for OSLC domain specifications and advises the OSLC Steering Committee on technical topics.
For more information, see the Workgroup Best Practices.
Target Specification Development Organizations (SDOs)
Specifications developed by this WG may be contributed to these SDOs:
This contribution to these SDOs is dependent on maturing the specifications within this WG and gaining consensus on the contribution. At that point, the WG would make a proposal to the OSLC Steering Committee for such a move. For more information, see the Workgroup Best Practices.
By agreeing to become a member of this Workgroup, this implies some amount of time and contribution to assist in the development and promotion of the specification. There is no minimal amount of time or level of participation.
It is recommended that each member should expect to:
- attend the teleconferences
- participate in off-line mailing list discussions
- contribute and review scenarios
- participate in prioritization activities
- potentially lead the Workgroup and/or meetings
- contribute specification content in the form of proposals and actual specification text
- edit and organize the specification
- address specification issues
- contribute to a test suite
- produce implementation feedback in form of implementation reports
Meetings Frequency and Communications
Meetings are conducted typically by teleconference. The frequency changes based on time of year and current cycle of specification development but should expected to be every two weeks. Additional meetings may be held by a subset of the Workgroup on a more frequent basis to work on some focused activities.
Meetings should be announced at least 48 hours in advance.
Meeting agendas should be set at least 24 hours in advance.
Mailing list and wikis should be used to capture all work and discussions. This provides Workgroup members that can’t attend meetings the ability to participate and provide feedback.
Decisions within this Workgroup are consensus driven, facilitated by the Workgroup Lead.
The Workgroup members nominate a Lead. Workgroup members work to reach consensus to select the Lead or co-Leads should be. Having more that one Workgroup Lead is preferred but not required.
Members of this Workgroup agree to this Workgroup Participation Agreement.
- Tracked Resource Set 2.0 Finalize
- Core 2.0 Final
Bit of a ghost town here