This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Creation of a Set of AID Whitepapers"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
Line 7: | Line 7: | ||
==Planning== | ==Planning== | ||
*[[Software Implementation of CDA]], October 2010 | *[[Software Implementation of CDA]], October 2010 | ||
− | **Nov | + | **Nov 2011: for RE-approval |
− | * | + | *[[RIM Based Persistence]], September 2011 |
− | *LDM/PDM approaches, May | + | **Nov 2011: for initial approval |
+ | *LDM/PDM approaches, May 2012 | ||
Candidate topics: | Candidate topics: | ||
*v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability. | *v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability. |
Revision as of 17:49, 13 July 2011
The Creation of a Set of RIMBAA Whitepapers project was established to manage the process of creating a set of whitepapers.
- Note: This is project #550 in the Project Insight tool. Project approved by FTSD on its call of 2010-10-19. Project approved by TSC on its call on 2010-11-08.
Scope
This is a long running (maintenance type) project to create a set of whitepapers with the consensus based findings of the RIMBAA WG as to what the v3 implementation best practices (or: v3 implementation patterns) are.
Planning
- Software Implementation of CDA, October 2010
- Nov 2011: for RE-approval
- RIM Based Persistence, September 2011
- Nov 2011: for initial approval
- LDM/PDM approaches, May 2012
Candidate topics:
- v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability.