This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.


Quick 3.0 links: days Meetings bubble Email archives sitetree Recon Scenarios? book Recon Specification info Examples?


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.

To join this working group

  1. Request a meeting invitation: contact Jacob Yackenovich or Tuan Dang, or send an email to the working group's mailing list admins (note: remove NOSPAM from the destination domain name).
  2. Register for the Reconciliation Workgroup mailing list


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 understand if the resource 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 purpose

Identity and reconciliation allow users to have control over the correct resource when there are multiple products in use. This is a central issue when the resources described are not themselves electronic documents, be they representations of hardware, software or other managed business entities.

The goal of this effort is to define the resources, constraints and methods useful for answering this category of questions, so that multiple tools can have a common understanding of their data when they integrate.

The approach will be to specify a number of tightly constrained scenarios, address them by drafting specifications, collect implementation experience using these drafts and then finalize the specifications. This will decrease the barrier to sharing data across multiple vendors and tools as part of the resource management life cycle. Future iterations of this process will be used to address additional scenarios.


3.0 is the first version of the documents below. The OSLC Core working group recommends that domain working groups use the specification version to indicate that they are based on the OSLC Core 3.0 specification. This working group chose to use a consistent version number for all related documents.

3.0 (Draft)

OSLC-RECON 3.0 Specifications

Document 3.0
  Link Status
Reconciliation Specification 3.0? Initial Draft

Supporting Documents

Document 3.0
  Link Status
RECON Scenarios and Use Cases 3.0? Note
RECON Vocabulary 3.0? Initial Draft
Common Resource Type Vocabulary 2.0 Proposal
Architectural Direction 3.0? Note
Examples 3.0? Note


Note: iterative specification validation will be occurring as the drafts evolve before finalization. The goal is to have at least 2 implementations of the specification before it is considered finalized.

Version Create Draft Specs Start Convergence Finalize Specs
3.0 2012-Jul-13 2012-Aug-20 2013-Mar-29


Jacob Yackenovich (co-lead)
Tuan Dang (co-lead)




How to join a working group

Meeting Agendas and Minutes

Mailing List

Register for the Reconciliation Workgroup mailing list

Reconciliation Workgroup mail archives

General OSLC Community

Edit | Attach | Print version | History: r10 | r8 < r7 < r6 < r5 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r6 - 23 Jul 2012 - 20:16:02 - JacobYackenovich
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback