Most editorial,...
I respect the wisdom and efforts engaged to create this much volume of the document, keeping consistency with the
internals and externals.
Having said that, I will present some comments that may contribute to that.
Overall, I feel expressions and statements in the document are a bit more complex and abstract than they needed to be as
a specification of technology. Another point is the requirements are listed without discrimination if they are
preferred or baseline for every grid systems. It will help readers understand what the grid system is. The rest is a
list of specific comments.
My apologies for not being able to read through the entire document.
On page 1, the first sentence can be simpler and easier to read as below:
-----------------------------------------------------------------------------
The definition of a core set of interfaces, behaviors, resource models, and bindings is required for successful
realization of the Open Grid Services Architecture (OGSA) vision of a broadly applicable and adopted framework for
distributed system integration, virtualization, and management.
-----------------------------------------------------------------------------
On page 6, Table 1, I wanted to see a short remark for each item why it is chosen as a use case, in addition to the
description. Alternatively, a single justification for entire selection may be presented in a paragraph next to the
table. Also, the first sentence for each row should have a coherent style;some has a subject, others don't.
On page 7, the first paragraph in the section "2.1 Dynamic and Heterogeneous Environment Support", listing only J2EE and
.NET as examples of hosting environment sounds misleading, since the definition includes underlying OS and other
elements, according to the glossary.
On page 7, the second sentence in the second paragraph in the section "2.1 Dynamic and Heterogeneous Environment Support
" sounds indirect and can be simpler and easier to read as below:
-----------------------------------------------------------------------------
There are existing functions that are implemented for today's system, working stably and reliably, which need to be
modified and integrated into the Grid.
-----------------------------------------------------------------------------
On page 7, in the section "2.1 Dynamic and Heterogeneous Environment Support", beginning words of the list items are not
introduced literally in the preceding paragraphs, thus sounds abrupt even though understandable.
On page 8, the explanation of the "Metadata services" in the section "2.2 Resource Sharing Across Organizations", the
phrase "to define views on entities" is difficult to understand what it means in reality.
On page 8, the explanation of the "Site autonomy" in the section "2.2 Resource Sharing Across Organizations", the
explanation may be true, but not convincing to me for a requirement to be in this section. In my view, site autonomy is
more important to make the site itself virtualized, liberating grid users and/or administrators in higher layers from
the miscellaneous management works that are site specific.
On page 8, the explanation of the last bullet item in the section "2.2 Resource Sharing Across Organizations", the
phrase "usage information" sounds as man page like information in general. I propose "usage record" or "usage statistics
" instead.
On page 8, in the section "2.3 Optimization", the last half of the third sentence can be simpler and easier to read as
below:
-----------------------------------------------------------------------------
and leads to resource underutilization as allocated resources to address such scenarios will remain unused for long
periods.
-----------------------------------------------------------------------------
On page 8, in the section "2.3 Optimization", in the 4th sentence, I propose the word "optional" instead of "flexible".
The advance reservation is an implementation of the optional policy that may...
View Full Message