Hi Goffi,

On 8 Feb 2016, at 11:20, Goffi <go...@goffi.org> wrote:
> Le vendredi 5 février 2016, 15:52:36 XMPP Extensions Editor a écrit :
>> The XMPP Extensions Editor has received a proposal for a new XEP.
>> 
>> Title: References
>> 
>> Abstract: This document defines XMPP protocol for multi-user chat for text
>> messages and sharing other information such as images.   The protocol
>> includes core chatroom features such as room topics and invitations and
>> defines a strong room control model, including the ability to kick and ban
>> users, to name room moderators and administrators, to require membership or
>> passwords in order to join the room.  The protocol aims to maximise use of
>> standard XMPP building blocks and in particular makes use of PubSub and
>> MAM.
> 
> Why do we have the abstract of MIX here instead of the one of references ?

Incompetence (mine).

>> URL: http://xmpp.org/extensions/inbox/references.html
> 
> I think this XEP is a good move and will be usefull to complete URIs. I have 
> some points to discuss:
> 
> - the XEP talks about MIX and doesn't references it (ha-ha), a link to the 
> MIX 
> XEP would help

Fair.

> - the XEP seems to *only* talk about MIX. Being a work in progress, it would 
> be nice to show examples with other use cases (PubSub node, MUC).

Fair.

> - how do we reference something without URI ? A message stanza for instance ? 
> How do we specify the id ?

As Chris later noted, we’re likely to need to define URI schemes for the 
various things we might want to reference.

> - how begin/end attributes work when there are several bodies ? e.g.: XHTML-
> IM: how to we references XHTML body ?

A reasonable question. What do people think?

> - how do we use begin/end attributes with <iq> stanza ? e.g. XEP-0277 
> microblog ?

Same. What would you/other people suggest?

/K
_______________________________________________
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
_______________________________________________

Reply via email to