Reconciliation

View Description Charter

This workgroup seeks to define a common set of resource definitions, properties and constraints on the values of these properties such that disparate tools can utilize to identify and reconcile their data.

Reconciliation Charter

Scope

This workgroup seeks to define a common set of resource definitions, properties and constraints on the values of these properties such that disparate tools can utilize to identify and reconcile their data.

Whenever there is a situation where one product is communicating with another product about a resource, it is important to the user using both products to identify the resource and understand if it is the "same thing" across multiple systems. For example, do a monitoring record and an asset record taken together, describe one, multiple, or different resources? The goal of this effort is to answer this category of questions, so that multiple tools can have a common understanding of their data when they integrate.

Deliverables

The Reconciliation 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

Certain specification needs may be found useful and needed by other domain workgroups and therefore may be adopted or endorsed by the Core Workgroup.

This Workgroup will be an active participant within the Core Workgroup as well. The participant will be the Workgroup Lead or delegates.

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.

Participation

By becoming a member of this Workgroup, you agree to contribute your time and effort to assist in the development and promotion of the specification. There is no required 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 is expected to be every week. 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 who cannot attend meetings the ability to participate and provide feedback.

Decision Policy

Decisions within this Workgroup are consensus driven, facilitated by the Workgroup Lead.

The Workgroup members nominate a Lead. Workgroup members work to reach consensus when selecting who the Lead ( or co-Leads ) should be.

Intellectual property

Members of this Workgroup agree to this Workgroup Participation Agreement.