Michel, Does it make sense to do a rendering of the ESI document when it was intended (based on what we've been told) to inform the BES discussion - and that we are in fact in the process of updated BES to accommodate the ESI issues? A
-----Original Message----- From: owner-ogsa-bes-wg@ggf.org [mailto:owner-ogsa-bes-wg@ggf.org] On Behalf Of Michel Drescher Sent: Friday, April 28, 2006 10:36 AM To: ogsa-bes-wg@ggf.org Subject: [ogsa-bes-wg] draft ESI 0.7 OGSA WSRF BP rendering
Folks,
I took a shot and hacked a WSDL that is OGSA WSRF Basic Profile compliant (I hope).
It is fairly incomplete with respect to a) the operations, messages and faults taken from WSRF- ResourceProperties, WSRF-ResourceLifetime and WS-Notification specifications. b) the ManagedJob interface completely missing as this in a constant flux at the moment (and will probably merge eventually with the existing BES specification)
The documents differ from the draft specification in that the resource properties that define the (POSIX) limits of a Job Factory retain the "Limit" suffix to avoid a naming conflict of the per ManagedJob limit "VirtualMemory" with the capability resource property "VirtualMemory".
As I am either not allowed or not capable otherwise to add documents to GridForge, would please one of the project admins do so for me.
Cheers, Michel