Donal,
More significant point.
The definitions of EPS and CSG are at variance with what the OGSA-RSS-WG has interpreted them to mean. Of particular importance is the fact that we have identified the requirement for an abstract notion of a set of candidates for some particular activity or interaction, independent of whether that activity relates to execution management (and which is what we named a CSG). We then made an EPS into a profile of a CSG such that it is useful for execution management.
Though this is true, the Glossary is a pair of the Architecture document and the definition of EPS & CSG in version 1.5 are different from those of RSS. Since we are publishing the Glossary out of step of the Architecture document there's bound to be a discrepancy somewhere. I would prefer to minimize that discrepancy by leaving the Glossary definitions as they are and putting an issue against the Architecture document, to be fixed at the next release. Is this acceptable? Also
Entity - should mention that entities may have state.
My preference would be not to try and say too much about what 'entity' is. It's one of those terms we use when there's no other easy term to use... Andreas Donal K. Fellows wrote:
Treadwell, Jem wrote:
If you have comments please let me have them by CoB this Friday, December 7^th . If any comments are minor (e.g. typos, formatting, minor wordsmithing) I’ll incorporate them and submit the document for publication next Monday, December 10^th . If I receive more serious comments I’ll ask Hiro to schedule time for discussion on an upcoming telecon, at which we’ll agree either to address them before publication or to create trackers and defer them for the next version.
Minor points.
Attribute - should be in there, as link to 'state'.
Entity - should mention that entities may have state.
Self-management - the second paragraph sounds like an advert. Maybe this can be fixed through minor wordsmithing so that the it says that "A self-managing IT infrastructure _should be_ less complex etc."
TCP - the definition omits the important fact that this protocol provides a stream-oriented model (i.e. a sequence of bytes) of data transfer to applications.
More significant point.
The definitions of EPS and CSG are at variance with what the OGSA-RSS-WG has interpreted them to mean. Of particular importance is the fact that we have identified the requirement for an abstract notion of a set of candidates for some particular activity or interaction, independent of whether that activity relates to execution management (and which is what we named a CSG). We then made an EPS into a profile of a CSG such that it is useful for execution management.
Donal. -- ogsa-wg mailing list ogsa-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-wg