> I read the latest version of the document. 
> Overall, the document is well written and I recommend it for publication.
> 
> Nevertheless some minor comments:
> 
> 1) It should be noted for the editor that the current doc has references to 
> OGF documents which are not yet published documents. These are at least 
> JSDLHPC, HPC-U, BES10.
> As some of these are or will be in the editor pipeline shortly, I suggest that
>  this doc moves forward, but an editorial update takes place prior to 
> publication. The reference section could be updated to include the then 
> available GFD numbers. 
> As this does not change anything vital in this doc, this should not require 
> any delay or re-opening for the public comment.
> 

Yes, agreed.


> 2) Section 4, page 4 has a reference to the BES UnsupportedFeatureFault. The 
> failure model in BES is currently subject of some discussion on the BES 
> list. I suggest to carefully monitor this process and if necessary to consider
>  an update this line prior to publication. 
> 

We monitored the BES group's progress up until the end of public comment (and the response to public comment) and the 
UnsupportedFeatureFault has remained a BES fault type. So, the text in the HPCP doc need not be updated.

> 3) hyphenation of XML element names might be ambiguous and confuse some people
>  (well not really).
> However, I have no real solution how to handle this.
> But looking on page 6, line 4 or line 7 and similar occurrences later, one 
> might ask whether we could prevent some hyphenations of "bes-factory:
> FactoryResourceAttributesDocument".
> Especially the hyphenation at a "-" could create some ambiguity that needs re-
> checking with the BES spec.
> (Compare to "ContainedRe-source" hyphenation later that page.) Maybe another 
> pass with some manual editing might help to at least minimize the 
> hyphenation of these element names.
> 

Yes, we agree that this is not ideal, and we have made an editorial pass to try to minimize this, but overall we believe
 that there is not an easy solution to this issue and so much of this remains unchanged.


> Otherwise the document is fine.


Thank you for your comments.