Sounds good. But I would like to see an albeit-trivial change: OLD: "A Compliant system MUST be prepared to support a vector length of 1." NEW: ""A Compliant system MUST support a vector length of 1." I told you it was trivial, right? :^) - Marty Quoting Marvin Theimer <theimer@microsoft.com>:

Hi;

As you may recall from the discussions at the Tokyo GGF conference, it was agreed that the HPC Profile base case would be kept as simple as possible in order to make it as easy as possible to create a compliant BES service (and to forestall feature creep). Among other things, that meant that we agreed upon requiring the HPC Profile-compliant BES services would only be required to support BES vector operations of length 1. But of course we'd like to allow compliant BES services to support vectors of length greater than 1 if they so desire (which we expect to be the common case).

Enclosed is a rewording of the paragraph in section 4 of the HPC Profile specification draft that restricts vector lengths of BES operations. I've rewritten it to clarify that vector lengths greater than 1 are allowed but may result in a fault. Please let me know if you would like additional rewording to occur. If I don't hear any rewording suggestions in the next few days then I'll go ahead and insert the rewording shown into the HPC Profile document.

Reworded paragraph: The BES GetActivitiesStatus, TerminateActivities, and GetJSDLDocuments operations include a vector input parameter that specifies the set of activities that the operation should be applied to. A Compliant system MUST be prepared to support a vector length of 1. A Compliant system SHOULD support input vector lengths greater than 1 but MAY return a Not_Supported fault in response to input vector lengths greater than 1.

Thanks, Marvin.

---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

Marvin Theimer wrote:

Hi;

As you may recall from the discussions at the Tokyo GGF conference, it was agreed that the HPC Profile base case would be kept as simple as possible in order to make it as easy as possible to create a compliant BES service (and to forestall feature creep). Among other things, that meant that we agreed upon requiring the HPC Profile-compliant BES services would only be required to support BES vector operations of length 1. But of course we’d like to /allow/ compliant BES services to support vectors of length greater than 1 if they so desire (which we expect to be the common case).

Enclosed is a rewording of the paragraph in section 4 of the HPC Profile specification draft that restricts vector lengths of BES operations. I’ve rewritten it to clarify that vector lengths greater than 1 are allowed but may result in a fault. Please let me know if you would like additional rewording to occur. If I don’t hear any rewording suggestions in the next few days then I’ll go ahead and insert the rewording shown into the HPC Profile document.

Reworded paragraph:

The BES GetActivitiesStatus, TerminateActivities, and GetJSDLDocuments operations include a vector input parameter that specifies the set of activities that the operation should be applied to. A Compliant system MUST be prepared to support a vector length of 1. A Compliant system SHOULD support input vector lengths greater than 1 but MAY return a Not_Supported fault in response to input vector lengths greater than 1.

One minor correction: the latest BES spec replaces "GetActivitiesStatus" with "GetActivityStatuses" and "GetJSDLDocuments" with "GetActivityDocuments". Peter

Thanks,

Marvin.