[Standards-JIG] JEP-0060: 1.8pre18

Peter Saint-Andre stpeter at jabber.org
Wed Jun 14 20:57:06 UTC 2006

Hash: SHA1

Ralph Meijer wrote:
> On Wed, Jun 14, 2006 at 08:26:33AM -0600, Peter Saint-Andre wrote:
>>> [..]
>>> The way collections are setup currently is that the reference to the
>>> parent node is held in the configuration of the child node. This works
>>> great for notification, but not for top-to-bottom stuff like permission
>>> checking. In the end it is an implementation detail, of course, but I'm
>>> not sure if such application specific configuration options need to go
>>> into JEP-0060.
>> Why not just set up the default node configuration options to be what
>> you want? And what happens if you move a node from one collection to
>> another, or a node is associated with multiple collections (each of
>> which requires inheritance)? Since the need seems to be fairly
>> specialized, for now I think I'd rather leave these sticky issues up to
>> implementors. :-)
> Agreed.
> Oh, wait. I'm an implementor! :-)
>>> Note that section 3.4 of JEP-0068 (Field Standardization for Data Forms)
>>> describes how custom options (== field names) should be named. The MUST
>>> always begin with 'x-'. So in your example: 'x-inherit-perms'.
>> Sure.
> The reason I say this is because there are implementations of and/or
> suggestions for new options that don't do this and just prepend their
> custom stuff with 'pubsub#'. Maybe we should explicitely point to
> this in JEP-0068.



- --
Peter Saint-Andre
Jabber Software Foundation

Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060614/d565c761/attachment.bin>

More information about the Standards mailing list