Folks, Peter G Lane wrote:
[...]
The main thing that comes to mind is how a BES service would expose which types of credentials it can handle or which it expects. I think you’re right that the rest of it – e.g. declaring a set of standard credentials types so that interop can actually be implemented – is part of the HPC profile work.
So something akin to "I accept X509 certs and Kerberos tokens"? I'm fine with that. This sounds like another item that should be included in a GetInteropData operation that I proposed in a different email.
[...]
“Someone” will have to define all the details that are necessary to enable actual interoperability. Much of that work can be done in the HPC profile. As I said in a previous email response, I like your suggestion of defining the activity interface – NOTE: just the generic query/modify part having to do with JSDL and things like cancellation – in the same spec.
Fair enough. Have a way to get interop data but don't restrict it. I think I'm going to have to start paying attention to the HPC profile work. ;-)
even though I did only partially participate in this discussion, I think you touching exactly the right spot on interoperability. I think this is a discussion whose outcome would be invaluable input to the GIN working group. I guess we should copy these guys in here. Cheers, Michel -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834