This wiki has undergone a migration to Confluence found Here
Difference between revisions of "AID three year plan"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | Goals of the RIMBAA WG: | + | *Goals of the RIMBAA WG: |
*#Marketing - Public exposure of successes (of v3 implementability and the RIM itself) | *#Marketing - Public exposure of successes (of v3 implementability and the RIM itself) | ||
*#Sharing of experiences and solutions | *#Sharing of experiences and solutions | ||
Revision as of 06:41, 1 January 2010
- Goals of the RIMBAA WG:
- Marketing - Public exposure of successes (of v3 implementability and the RIM itself)
- Sharing of experiences and solutions
- Document/describe (for all possible cell transitions) how those steps could be supported/achieved.
- We focus on Patterns for Application Development. Guidance, no normative outcomes.
- Reference Implementation (Java SIG materials, extend OHT?)
- Outreach to RIMBAA implementers (especially those not present at RIMBAA meetings); publish reviews of existing RIMBAA implementations
- Education - for newbies to RIMBAA
- Standard Improvement
- Identify issues in HL7 standards during the implementation process
- Work with ITS WG on an RS XML ITS and the identification of CS-RS transition issues
- Identify issues caused by the ‘interoperability mindset’ of the RIM
- V3 constructs: Context Conduction, Update Mode, Object Versioning
- Work on SAEAF
Three year plan
- Project: create set of whitepapers (#550)
- Initial whitepaper: ORM approaches whitepaper, may 2010
- project: reference implementation (#549)
- Document design/decision process of the Java RIMBAA reference implementation, Sept 2010
- Create a reference implementation (in .net?) of Datatypes R2 (only); as well as the persistence of Datatypes R2.
- Outreach to RIMBAA implementers to get hold of experiences/best practices.
