Difference between revisions of "Milestone 1.0M9"

Revision as of 12:13, 30 August 2007

• Original Date June 15
• Revised Date July 27
• Revised Date August 13
• Revised Date September 17

Focus is:

1. Finalize/freeze the architecture --all major interfaces defined and implemented
2. Nightly automated builds for all components
3. Improved deployment build documentation

Cross Cutting Concerns

Architecture

The expectation is that 1.0M9 (formerly "M0.9") represents finalized architecture for 1.0. (i.e. there will be no new component-level interfaces, etc.)

• IdAS Registry - finalize design
• RPPS interfaces - need to merge/harmonize IBM Zurich and Parity Ukraine branches
• CardStoreStrategy - finalize design
• Embedded CardManager - finalize design
• HBX support for H2, H3
• IE HBX (and possibly retrofitted to Firefox) to use native i-card selector (reusing code from H2 config)

Deployments

• H3 issues (we're trying to get as many as possible of these done for the June Catalyst demo)
  1. Can import MSFT CardSpace format personal cards (.crds files)
  2. Need a user friendly way of importing a .crd file --e.g. double click on .crd file
  3. Requires installation of tomcat (unacceptable complexity)
  4. Total size too large at approx 50+ MB

Components

Each Component owner should add a link to the 1.0M9 "to do list" for their component:

• HBX
• I-Card Manager
• RPPS Web app
• RPPS Core
• ISS
• Token Service TS ToDo
• IdAS: IdAS 1.0M9 tasks
• IdAS JNDI CP
• IdAS Jena CP

Links

• Milestone 1.0M8
• 1.0