[rights-requirements] preparation for upcoming F2F

[Bob Glushko <glushko@SIMS.Berkeley.EDU>]

It is clear to all of us that we have a lot of work to do to
reach some closure in the requirements, and equally clear that we are in
danger of significant schedule slippage if we don't make substantial
progress toward completion of the requirements phase at the upcoming
F2F.  Let me urge everyone to take some responsibility for closing
the schedule gap by reviewing as many of the submissions and dispositions
as possible. While the submitter is obviously well-suited to talk about
his or her submission, this doesn't mean that others don't have the right
or responsibility to review them. I have the sense that people have
concluded that they should just "take care of their own"
submission but the resulting lack of familiarity with the other ones is
causing our discussion to take longer than it should.  

In addition, we still have to make some decisions about the format in
which our requirements will be distributed for public review (we need
some repackaging, cover information, etc -- the spreadsheet format may
work internally but it is way too cryptic for outsiders) and the process
by which public comments will be reconciled with or incorporated into the
requirements that the committee turns over to the specification committee
(and I believe that information about this reconciliation process must be
part of what we send out for review).   So you should all think
about these topics as well so we don't have to start from the beginning
at the F2F to deal with them.

bob

--
Robert J. Glushko, Ph.D.
http://www.sims.berkeley.edu/~glushko
School of Information Management & Systems
102 South Hall
University of California, Berkeley CA 94720-4600