Dr. Nakata,

First of all, thank you very much for your efforts and contributions to give us numbers of comments, along with 
suggestions including language issues. They all gave us substantial base of improvement of the specification. Although 
all of the editorial/language suggestions are taken by us and applied in the draft, please let us skip mentioning each 
of them and reply to those that we came up with our solutions.

### Page : 4 ###
### 3 Cementer : nakata : Note Date : 2006/03/09 14:22:38
What is the difference between proprietary and nonpublic?
### Page : 5 ###
### 20 Cementer : nakata : Note Date : 2006/03/09 14:33:34
Sorry I don't understand what you mean by "which makes reference with
OGSA architecture"
-> Replaced above phrase with "which follows OGSA architecture"
### Page : 6 ###
### 36 Cementer : nakata : Note Date : 2006/03/09 14:40:10
In a comment to WS-Agreement Spec. It was pointed out that using square brackets for two purposes (document citation and
 abstract properties) is confusing. We compromised by using bold font + underlines as well as square brackets for 
document citation.
-> We understand your point. However, we decided to keep original notation, since it is common practice and should be 
reasonably understandable to readers. We removed the first sentence in the section 1.3 below:
When describing abstract data models, this specification uses the notational convention used by the [XML Infoset].

### 43 Cementer : nakata : Note Date : 2006/03/09 14:41:53
I think there is a newer spec for wsrf-bf, rp and -r.
-> Updated the namespace listed.
### 44 Cementer : nakata : Note Date : 2006/03/09 17:20:27
How about Namespaces of WS-Notification?
-> Updated the namespace and referenced document title.
### Page : 8 ###
### 45 Cementer : nakata : Note Date : 2006/03/09 14:55:39
do we need to restrict it to just CDL?
-> Changed description as below:
..., such as CDL.

### 50 Cementer : nakata : Note Date : 2006/03/09 15:01:00
Is this life cycle of an Application archive or a life cycle of an
application?
-> Changed to the phrase to "the application" in two place.

### Page : 9 ###
### 57 Cementer : nakata : Note Date : 2006/03/09 15:15:22
I think this is sort of a meta-specification for the specification itself. I am not sure whether it is appropriate to 
include this section in the spec.
-> We understand your point. However, we decided that requirements for the specification itself can be mentioned here. 
The containing chapter is declared as non-normative.

### Page : 10 ###
### 72 Cementer : nakata : Note Date : 2006/03/09 15:20:29
ARI has not been explained yet
-> Changed description as below so that it doesn't contain forward reference:
ACS should allow implementers of data transport mechanisms to select their own protocol.
### Page : 11 ###
### 80 Cementer : nakata : Note Date : 2006/03/09 15:26:47
Chapter 3 is a tricky one. It might be better to go directly to normative specification as sometimes, one needs to 
understand some of the normative spec in order to understand this chapter. Or have it as a separate primer.
-> We understand your point. However, we decided to keep original structure to keep normative text minimum in size, 
while providing useful information in the non-normative chapters.
### 87 Cementer : nakata : Note Date : 2006/03/09 15:27:34
concept of AA instance has not been introduced yet.
-> Changed the word AA to "Application Archive (AA)" so as to it is understandable what it means.
### 88 Cementer : nakata : Note Date : 2006/03/09 15:38:37
Application Content has not been introduced yet
-> Changed the phrase to "a granularity of a file", to avoid not-explained expression.
### 94 Cementer : nakata : Note Date : 2006/03/09 15:35:39
"ARI" should be explicitly written within this figure.
-> Added the text "ARI" in the figure.
### 96 Cementer : nakata : Note Date : 2006/03/09 16:24:58
I can imagine what Get Contents operations is but it has not been introduced...