[Standards-JIG] XEP-0163: PEP updates
ian.paterson at clientside.co.uk
Wed Jan 3 13:02:22 UTC 2007
On 3 Jan 2007, at 10:12, Kevin Smith wrote:
> On 3 Jan 2007, at 03:19, Peter Saint-Andre wrote:
>> I like some of the ideas that Ian Paterson and I discussed recently
>> -- especially some way to pre-define parameters for certain NodeIDs
>> (so that we can "hardcode" that a NodeID of "storage:bookmarks" has a
>> whitelist access model, for example). We may be able to do that with
>> a registry, or there may be other approaches that would work.
> I like ... some way to pre-define parameters for certain NodeIDs I
> think this is orthogonal to the namespace/node discussion though? (On
> first glance this seems to be the kind of thing we want to encourage,
> sensible preset parameters).
It is orthogonal to the main discussion... but since Peter raised the
subject: Although I really liked the idea of pre-defining node
parameters during our IRL chat, I've since realised that (since the
server would have to know about the details of each namespace) we'd be
back to the situation where clients have to wait for servers to
implement XEPs (registry entries) before they can take advantage of the
IMO there may still be a case for allowing the client to specify
parameters for "automatic" node creation (for XEP-0060 too). See the
extract from an earlier post below.
Ian Paterson wrote on 19 November 2006:
To make PEP-based "Private Data Storage" easy for clients, we would need
to allow automatic node creation for persistent as well as transient
nodes (in addition to for any access model). For example by supporting a
<configure/> sibling of the <publish/> element (see stanza below)? The
<configure/> element would be ignored if the node already exists. This
would also be a nice short-cut for clients to use in cases other than
Private Data Storage.
<iq from='juliet at capulet.com/balcony' type='set' id='create-bookmarks'>
<url name='Complete Works of Shakespeare'
<x xmlns='jabber:x:data' type='submit'>
<field var='FORM_TYPE' type='hidden'>
More information about the Standards