Categories for real time could be by section. Comments
for each summary may be organized as follows:
Bindings
typos, grammatical
user
implementor
additions
deletions
re-write
This is how lots of committees provide service to their
technical communitites and avoid going crazy from
information overload.
The "person" to contact and category can be provided on
the web.
MPI RT & MPI-3
---------------
There is a great deal of interest in MPI RT by user
communities that have applications requirements that are not
satisifed by MPI-1, and MPI-2. In addition, there are architectures
that are more frequently used in accordance with these applications.
In the future, more architectures will be "slipping" into
this category. For this reason, it is imperative that
MPI-3 be a reality to continue some of the work yet to be
done. In addition, there may be timing requirements for
document changes, turn around, etc that conflict with MPI-2
progress. All these issues must be considered when decisions are
being made with respect to the future of the standard and how
to regulate changes. There are different needs developing.
Implementors have committed to providing this product
to customers, therefore the ability to accomodate
some special requirements when needed is important.
The purpose of these requirements is not to undermine
the current effort by the standards committee, but to
accelerate the unfinished work. They call it "cutting
your losses to promote progress".
Regards, Anna
-----------------------------------------------------------------
Anna Rounbehler
SKY Computers
anna@sky.com