From 44c696c717e54ad4395fd6be2fd21f5325a889e4 Mon Sep 17 00:00:00 2001
From: Steve Kille <Steve Kille>
Date: Fri, 2 Sep 2016 17:14:43 +0100
Subject: [PATCH] Florian's comments of 23 August and updated Abstract

---
 xep-0369.xml | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/xep-0369.xml b/xep-0369.xml
index 6ba1885f..94275949 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -8,7 +8,10 @@
 <xep>
 <header>
   <title>Mediated Information eXchange (MIX)</title>
-  <abstract>This document defines Mediated Information eXchange (MIX), an XMPP protocol extension for the exchange of information among multiple users through a mediating service. The protocol can be used to model group communication applications such as chatrooms, although with greater flexibility and extensibility than existing groupchat technologies such as Multi-User Chat (MUC). MIX supports standard groupchat features such as discussion topics and invitations, and  defines a strong access control model similar to that of MUC. MIX also enables users to participate without sharing presence, allows communication of any structured data (not only textual messages).  MIX uses Publish-Subscribe to provide flexible access and publication, and uses Message Archive Management (MAM) to provide storage and archiving. </abstract>
+  <abstract>This document defines Mediated Information eXchange (MIX), an XMPP protocol extension for the exchange of information among multiple users through a mediating service. The protocol can be used to provide human group communication and communication between non-human entities using channels, although with greater flexibility and extensibility than existing groupchat technologies such as Multi-User Chat (MUC).   MIX uses Publish-Subscribe to provide flexible access and publication, and uses Message Archive Management (MAM) to provide storage and archiving. </abstract>
+  
+
+  
   &LEGALNOTICE;
   <number>0369</number>
   <status>Experimental</status>
@@ -109,6 +112,8 @@
     <li>A user can determine which channels they participate in.</li>
     <li>Provide extensibility regarding data formats that can be sent within a channel (files, structured data, indications about media sources in multimedia conferences, etc.) as well as flexibility regarding which data formats a user wants to receive.</li>
     <li>Enable federation of a channel across multiple servers, to provide a service equivalent to "federated MUC" &xep0289;.</li>
+    <li>To enable sharing of messages on a channel without requiring sharing of presence.</li>
+    <li>To enable sharing of presence without requiring message sending.</li>
     <li>(Desirable) Make it easier to reduce duplicate traffic.</li>
  </ul>
 </section1>