Hello,

Le lundi 14 janvier 2019, 02:41:57 CET Tedd Sterr a écrit :

> 3) Proposed XMPP Extension: Order-By - 
> https://xmpp.org/extensions/inbox/order-by.html
> 
> Georg thinks it's a very specific use case, and defines two hard-coded 
> properties (creation and modification timestamp) for ordering on, whereas it 
> would be cleaner to allow ordering by any field. Jonas and Dave point out 
> that the properties are external to the items themselves.
> Jonas wants to discuss further with the author about points already raised.
> Georg wonders why the properties couldn't be embedded in the items - Jonas 
> say servers must not modify items; Georg suggests the client could add the 
> timestamps itself, but Jonas says the author dislikes this as it would allow 
> them to be spoofed.
> Georg thinks it needs to be renamed to "PubSub MAM Retrieval Ordered by 
> Creation or Modification."
> Dave noticed that it apples to MAM but doesn't really discuss it, and 
> presumably also has an impact on RSM. Jonas says it doesn't impact RSM, but 
> the server might have to use different identifiers in RSM to work correctly; 
> Dave thinks that's worth thinking about and mentioning. Kev says it does 
> interact with RSM, but 'impact' is a matter of interpretation.
> Kev would like to see this have a little more work before being published, 
> but couldn't find a reason to veto.
> 
> Jonas: [on-list]
> Georg: [on-list] (with fallback to -1: very specific use case; requires 
> [implementation] changes to other XEPs)
> Kev: +1 (not keen on it, but it clears the bar-of-incompetence for 
> Experimental)
> Link: [on-list] (still catching up on everything)
> Dave: +0 (reserve the right to change that while others are still on-list)

For the record, I've answered to the concerns raised by the council at 
https://mail.jabber.org/pipermail/standards/2019-January/035646.html . I hope 
this helps.


Thanks
Goffi


_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to