Clarification of Name/Description/Subject

xep-0369.xml

@@ -41,7 +41,9 @@
     <date>2017-01-30</date>
     <initials>sek</initials>
     <remark><p>
-      Ensure all RFC 2119 keywords are capitalized and used correctly
+      Ensure all RFC 2119 keywords are capitalized and used correctly;
+      Use MAM ID to identify message;
+      Clarify use of the various channel names;
     </p></remark>
   </revision>
   <revision>
@@ -377,7 +379,7 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
       </p>
     </section3>
     <section3 topic="Messages Node" anchor="messages-node">
-      <p>Items in this node will contain a message identified by a unique ID.  A MIX implementation SHOULD NOT make messages available for retrieval from this node using pubsub and MUST NOT allow direct pubsub publishing to this node.  Messages are published by sending messages to the channel. Zero history is held in the messages node.   Message history is retrieved by use of  MAM. Users subscribe to this node to indicate that messages from the channel are to be sent to them.</p>
+      <p>Items in this node will contain a message identified by the MAM ID used for the message in the channels MAM archive.  &xep0313; rules MUST be used to ensure this ID is unique.  A MIX implementation SHOULD NOT make messages available for retrieval from this node using pubsub and MUST NOT allow direct pubsub publishing to this node.  Messages are published by sending messages to the channel. Zero history is held in the messages node.   Message history is retrieved by use of  MAM. Users subscribe to this node to indicate that messages from the channel are to be sent to them.</p>
       <p>Private Messages are not stored in the messages node.</p>
     </section3>
 
@@ -438,10 +440,13 @@ This approach  enables flexible support of multiple clients for a MIX channel pa
       </p>
       <table caption="Information Node Attributes">
         <tr><th>Name</th><th>Description</th><th>Field Type</th><th>Values</th><th>Default</th></tr>
-        <tr><td>'Name'</td><td>A short string providing a name for the channel.</td><td>text-single</td><td>-</td><td>-</td></tr>
-        <tr><td>'Description'</td><td>A longer description of the channel.</td><td>text-single</td><td>-</td><td>-</td></tr>
+        <tr><td>'Name'</td><td>A short string providing a name for the channel.  For example "The Coven".  Typical uses of this value will be to present a user with the name of this channel in a list of channels to select from or as the header of UI display of the channel.</td><td>text-single</td><td>-</td><td>-</td></tr>
+        <tr><td>'Description'</td><td>A longer description of the channel. For example "The Place where the Macbeth Witches Meet up".   A typical use would be to provide a user with more information about the channel, for example in tool tip.</td><td>text-single</td><td>-</td><td>-</td></tr>
         <tr><td>'Contact'</td><td>The JID or JIDs of the person or role responsible for the channel.</td><td>jid-multi</td><td>-</td><td>-</td></tr>
       </table>
+      <p>
+        Name and Description of the channel apply to the whole channel and are will usually be changed infrequently.   This contrasts to Subject, which is more likely to change frequently and will often reflect the topic being discussed which has narrower scope than channel as a whole.
+      </p>
       <p>The name and description values MUST contain a "text" element and MAY contain additional text elements. Where multiple text elements are provided, each MUST posses an xml:lang attribute that describes the natural language of the subject.  The format of the Information node follows &xep0004;.  This allows configuration to be updated by MIX defined commands and that the results of update commands are the same as the PubSub node.
       The following example shows the format of a item in the information node for the example coven@mix.shakespeare.example channel.
       </p>