[Standards-JIG] JEP-0060: open issues

Boyd Fletcher boyd.fletcher at je.jfcom.mil
Tue Jun 13 19:06:27 UTC 2006


For item (2) we will volunteer to update the JEP document if you would like.

boyd
 


On 6/13/06 2:23 PM, "Peter Saint-Andre" <stpeter at jabber.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I have been shooting to get 1.8 published in time to submit an updated
> "Atom Over XMPP" draft to the IETF Secretariat before the I-D cutoff
> date for IETF 66 (June 26). The more we add to 1.8, the less likely that
> is. The Council will discuss these open issues in its meeting tomorrow
> and we'll figure out a schedule for modifications. I'd just as soon
> reach agreement on what we're adding to the spec and then put all that
> in 1.8 if possible, but that can work only if (1) people stop requesting
> new features, (2) I make the time to modify the text real soon now, and
> (3) the Council meets again next week to approve 1.8 (since it won't be
> able to do so tomorrow). I think we can make that happen, but I have
> something else to crank out today so I won't have time to look at pubsub
> more until tomorrow.
> 
> Peter
> 
> Boyd Fletcher wrote:
>> hopefully we can get Ordered Items/Nodes and Permissions Inheritance into
>> version 1.8 of specification. The whiteboarding work we are doing needs both
>> of those capabilities to support safe multiple user access to the
>> whiteboard. 
>> 
>> I think both functions will have a near term positive impact on projects
>> wanting to use PubSub.
>> 
>> Since there has been no negative feedback on the list to either of the
>> above, other than time, is there any reason they shouldn't be added to 1.8
>> vice 1.9?
>> 
>> 
>> boyd
>> 
>> On 6/12/06 4:45 PM, "Peter Saint-Andre" <stpeter at jabber.org> wrote:
>> 
>> In the interest of gaining consensus and moving JEP-0060 along, here is
>> a summary of the open issues regarding version 1.8 of JEP-0060. Let me
>> know if I've missed anything.
>> 
>> Oh, and one "meta-issue" is whether to address these open issues in 1.8
>> or in 1.9:
>> 
>> http://mail.jabber.org/pipermail/council/2006-June/001874.html
>> 
>> ******
>> 
>> 1. Data Forms
>> 
>> Get rid of 'access' attribute on <configure/> element?
>> 
>> Also get rid of 'type' attribute on <create/> element?
>> 
>> Force use of node configuration data form in both cases or just for
>> access model (create 'type' was in 1.7)?
>> 
>> http://mail.jabber.org/pipermail/standards-jig/2006-June/011496.html
>> 
>> ******
>> 
>> 2. 'node' attribute for <items/> element
>> 
>> What should the value of the 'node' attribute be for <items/> elements
>> in event notifications received from collection nodes? Specifically,
>> should it be the NodeID of the collection node (current policy) or
>> sometimes (in the case of transient, notification-only nodes as the
>> generator of the notification) the NodeID of the generating node?
>> 
>> http://mail.jabber.org/pipermail/standards-jig/2006-June/011497.html
>> 
>> ******
>> 
>> 3. Handling of configuration-required subscriptions
>> 
>> When a subscription to a node must be configured in order to take
>> effect, should we return (1) a success-with-configuration-request
>> (current policy) or (2) a <not-acceptable/> error?
>> 
>> Should we recommend (1) but allow (2)?
>> 
>> http://mail.jabber.org/pipermail/standards-jig/2006-June/011546.html
>> 
>> ******
>> 
>> 4. Subscription retrieval
>> 
>> Should we define a way to retrieve all subscriptions (with full
>> configuration information) in one request?
>> 
>> http://mail.jabber.org/pipermail/standards-jig/2006-June/011546.html
>> 
>> ******
>> 
>> 5. Ordered nodes
>> 
>> Should we define a way to enforce order on the items published at a node?
>> 
>> http://mail.jabber.org/pipermail/standards-jig/2006-June/011509.html
>> http://mail.jabber.org/pipermail/standards-jig/2006-June/011547.html
>> 
>> (And also, it seems, to enforce order on the nodes within a collection,
>> though what that means is unclear to me.)
>> 
>> ******
>> 
>> 6. Configuration inheritance
>> 
>> Should we define a way to enforce inheritance of node configuration options?
>> 
>> http://mail.jabber.org/pipermail/standards-jig/2006-June/011557.html
>> 
>> ******
>> 
>> 7. Paging through published items
>> 
>> Should we define a way to set the "start item" for items retrieval?
>> 
>> http://mail.jabber.org/pipermail/standards-jig/2006-June/011558.html
>> 
>> And further, should we get rid of 'max_items' attribute and do "paging"
>> using JEP-0059?
>> 
>> http://mail.jabber.org/pipermail/standards-jig/2006-June/011563.html
>> 
>> ******
>> 
>> Peter
>> 
> 
> - --
> Peter Saint-Andre
> Jabber Software Foundation
> http://www.jabber.org/people/stpeter.shtml
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFEjwK5NF1RSzyt3NURAgVWAKCPf6cWuvsCs55Ye+IW6DwT90L17gCfc3Lb
> DTIeyoid+wXtBysU2R+D+6A=
> =bFAY
> -----END PGP SIGNATURE-----



More information about the Standards mailing list