[Pgi-wg] Profiling vs new specs

[Balazs Konya]

hi,

Andrew Grimshaw wrote:
> It turns out that my memory is not as good as I thought. 
> 
> First, the state model already includes Pending, and example profiles (but
> not formal profiles) for file staging, and suspend resume, are already in
> the document. 

yes, those state examples caused some confusion, some groups though that those 
example states are actual BES recommendations :)

I think the state model needs fixing (or call it extension) in order to be 
suitable for PGI.

> Note that the createActivity takes an ActivityDocument which
> contains the JSDL, and has an extensibility point (element) that we could
> profile to include something like HOLD_PENDING (note that this is also where
> the document recommends subscriptions go as well.) 

this is the kind of approach i don't really like: instead of introducing a clean 
extra input parameter you propose to squeeze everything into an extension of the 
ActivityDocument which i thought initially was just the "JSDL".

There is a very similar approach all over BES. Things are not treated in a clean 
manner, there is quite an ambiguity around the ActivityDocument.

bye,
Balazs Konya