WebCGM 2.1 schedule

All --

We don't have any technical content to discuss at the Wednesday 
teleconference, except for Dave's schema contribution.  (I reckon that I 
should give longer advance notice of that as a telecon topic, so people can 
prepare.)

It might be time to start having a closer look at the schedule.  However, 
since Thierry can't attend, I think we can conduct any discussion by email 
for now.

BACKGROUND:
-----
About coordination, the W3C-OASIS MoU says...
[[[
>[...resumption of processing in OASIS...] will be made on a date
>sufficiently prior to the W3C AC [PR] review, so that any further OASIS 
>public review, revision or
>TC approval required by the OASIS TC Process is conducted during, and may 
>be completed
>prior to the end of, the W3C AC [PR] review period. Any additional changes 
>recommended during
>that OASIS process will be submitted back to W3C as AC comments...
]]]

In other words, OASIS must complete its review and endorsement of changes 
since CS (the beginning of the W3C phase) before the completion of the W3C 
PR review.  PR review starts at a time TBD after W3C CR completion.

BACKGROUND:
-----
As presently planned, I am away and unable to work on WebCGM from 20 
October through 10 November.  Thierry is unavailable until about mid-November.

SCHEDULE CONSIDERATIONS:
-----

1.) We now anticipate that it will take till 01 Nov, rather than 15 Oct, to 
finish sufficient implementation work to exit CR with the features we want.

2.) Next steps in W3C:  produce PR document, coordinate PR-end date with 
OASIS processing requirements, resolve to seek PR review and approval (AC 
vote) to progress to REC.

3.) Next steps in OASIS:  approve the changes that happened in W3C with a 
Public Review and CS vote by the TC (this would comprise the end of any 
potential changes in OASIS).
         -- 15-day public review of OASIS version of the W3C-PR document;
         -- vote for CS (no significant wait time or duration).
         -- at this point, the period for OASIS changes ends.

4.) The CR document should have very few changes:  right now, there is just 
one editorial fix that I see is needed.  Additionally, however, if any 
at-risk features fail then they will be removed before PR and the 
return-to-OASIS.

5.) Recall that OASIS has some timing rules about requesting OS ballot, 
relative to start of month etc.  (Stuart?)

ASSESSMENT:
-----
A critical path schedule dependency is indicate by the steps in #3 
above.  That in turn will depend on CR-exit -- either all tests have 
2-pass, or we decide to say "done" and drop some at-risk features.  I don't 
see how this can be done before 20 Oct., and then it will have to wait till 
mid-Nov.  So it looks like mid-Nov for coming back for OASIS public review 
and CS ballot.

Thoughts, anyone?

-Lofton.

Received on Wednesday, 7 October 2009 00:32:01 UTC