Great start! Just a couple of comments:
1) I'd prefer something like "ManagedJobFactoryResourcePropeties"
instead of "JobFactoryRPDocument". That way everything is spelled out
and it's named after the full port type name.
2) I think the unnamed complexType under the "JobFactoryRPDocument"
element should be named. Following my preference from #2, this is what I
would like to see (or something similar):
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