[WS-XMPP] Our XMPP Web Service XEP proposal

[Peter Saint-Andre]

Egon Willighagen wrote:
> On Tue, Apr 22, 2008 at 10:46 PM, Peter Saint-Andre <stpeter at stpeter.im> wrote:
>>  I suppose my questions are:
>>
>>  1. Does XEP-0050 define enough (e.g., do we need "status-check")?
> 
> Yes; sort of. XEP-0050 defines the execution of a series of commands.
> Whether these are wizard pages, or stages of some service calculation
> is irrelevant. That is, I think it's find to have a 'next' to see what
> the next page has to offer, which might be a page stating 'still
> calculating'.

OK, that makes sense.

>>  2. Does XEP-0050 define too much (is "prev" always bad)?
> 
> Generally not, I guess. But for io-data services it does not make
> sense, I think. In configuration wizard pages it likely is useful.

Agreed.

>>  3. Do we need to define "profiles" of XEP-0050 for different
>>  applications (so that "prev" or whatever is not allowed)?
> 
> I think that this is exactly what io-data is doing... an extension
> that defines a profile of possible XEP-0050 use.
> 
> XEP-0050 does offer room for more granulated definition of states
> inside 'executing'... a 'finished executing' would be nice for (web)
> services, the moment where the data is ready for download, but not
> required. More interesting, I think an 'inactive' state is actually
> missing from XEP-0050. The state where a service, form, dialog content
> is undefined. Right now, completed and canceled are close, but not
> entirely the same thing. Overall, XEP-0050 is a useful starting point,
> particularly, with the matured libraries implementing it.

Is "inactive" really a kind of "executing"?

If we need to add more states to XEP-0050, let's figure out what they
are so we can update the spec before it advances to Final...

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/ws-xmpp/attachments/20080422/26a62485/attachment-0001.bin