Dear Yves and all, Thanks for your pointing out. I revised the document accordingly.
"* Definition of a specific data structure to be used for GridRPC arguments in middleware." -> maybe use "for arguments in GridRPC middleware"?
Fixed.
"* Definition of a "grpc_arg" data type to be used in conjunction with the argument data structure." -> If we use a name for the data type, maybe we can use the one that we use in the document "grpc_data_t" or we do not call it. In consequence, we have to adapt later in "* Definition of mechanisms.."
I changed the first sentence to * Definition of the data type to be used in conjunction with the argument data structure. and the second sentence to * Definition of mechanisms for handling persistent data, e.g., definition and use of a concept such as "data handles" (which might be the same as or similar to a grpc_data_t data type).
Cosmetics: "e.g." -> e.g., ; "Grid-RPC"->GridRPC
Fixed.
"Of the four GridRPC-like tools available today, NetSolve is widely deployed and used." -> This sentence does not have any sens, since there is no comparison. Maybe we can remove it, or at least, reformulate it. As it begins the presentation of the NetSolve Grid middleware, I suggest either to remove it or replace it by "NetSolve is widely deployed and used".
I replaced it by "NetSolve is widely deployed and used".
Typo "number of download is"-> number of downloads is
Fixed.
Dear Yusuke,
Here are the small comments that we have on the document. Except those ones, the document is perfect. Thank you for your work.
"* Definition of a specific data structure to be used for GridRPC arguments in middleware." -> maybe use "for arguments in GridRPC middleware"?
"* Definition of a "grpc_arg" data type to be used in conjunction with the argument data structure." -> If we use a name for the data type, maybe we can use the one that we use in the document "grpc_data_t" or we do not call it. In consequence, we have to adapt later in "* Definition of mechanisms.."
Cosmetics: "e.g." -> e.g., ; "Grid-RPC"->GridRPC
"Of the four GridRPC-like tools available today, NetSolve is widely deployed and used." -> This sentence does not have any sens, since there is no comparison. Maybe we can remove it, or at least, reformulate it. As it begins the presentation of the NetSolve Grid middleware, I suggest either to remove it or replace it by "NetSolve is widely deployed and used".
Typo "number of download is"-> number of downloads is
Best Regards.
.Yves.
Le Tuesday 10 June 2008 02:42:37 Yusuke Tanimura, vous avez $BqD(Brit?:
Dear all,
We discussed about the recharter at the session in OGF 23. Thanks for all participants! Attachment is a revised version according to our discussion.
* Download statistics of NetSolve/GridSolve is updated. * Document type of "Data Management API within the GridRPC" is changed from Recommendation to Informational. * A new planned recommendation document, "A GridRPC Model and API v2," is added to our deliverables.
It is really time to finalize and send the document to the area director. Please give us any further comments within a week if you have.
Best regards,
----------------------------------------------------- Yusuke Tanimura <yusuke.tanimura@aist.go.jp> Information Technology Research Institute, AIST 1-1-1 Umezono, Tsukuba Central 2 Tsukuba City 305-8568, Japan TEL: +81-29-862-6703 / FAX: +81-29-862-6601
-- Yves Caniou Associate Professor at Universit$Bq(BLyon 1, Member of the team project INRIA GRAAL, LIP / ENS-Lyon 46 All$BqF(B d'Italie 69364 LYON Cedex 07 tel: +33 4 37 28 76 48 http://graal.ens-lyon.fr/~ycaniou/
----------------------------------------------------- Yusuke Tanimura <yusuke.tanimura@aist.go.jp> Information Technology Research Institute, AIST 1-1-1 Umezono, Tsukuba Central 2 Tsukuba City 305-8568, Japan TEL: +81-29-862-6703 / FAX: +81-29-862-6601