[Standards-JIG] JEP-60 Item id for node configuration change notifications
stpeter at jabber.org
Tue May 30 19:54:43 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Ralph Meijer wrote:
> On Wed, May 10, 2006 at 01:14:34PM -0600, Peter Saint-Andre wrote:
>> I'm not sure why Peter did it that way, since that's the only reserved
>> ItemID as far as I can see. However, I don't immediately see a better
>> approach, so I think a service would in fact need to reject publication
>> requests that specify an ItemID of "configuration" (i.e., reserve that
>> ItemID for generation only by the service). I'll clarify that in the text.
> I dislike reserved ItemIDs.
I don't like them, either.
> Can't we add a <configure/> to <event/> in
> the #event namespace?
<message from='pubsub.shakespeare.lit' to='francisco at denmark.lit' id='foo'>
> Also, I'm still not sure about the access attribute to the <configure/>
> element in the other namespaces. I know it would be easier for PEP, but
> I don't know if avoiding forms there is needed/a good idea.
I don't see any great harm in the 'access' attribute, just as I don't
see any great harm in the 'type' attribute in an example like this:
from='bard at shakespeare.lit/globe'
<create node='announcements' type='collection'/>
That is, we could do that with a data form that includes the correct
value of the "pubsub#type" field. But do we gain anything by removing
the 'access' and 'type' attributes here and using data forms instead?
Jabber Software Foundation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards