moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

Making glossary using definition lists in XEP-0130. 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2982 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Tobias Markmann 2009-04-05 14:48:35 +00:00
parent 27e4841055
commit 90be9c0ccb
1 changed files with 38 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

80
xep-0130.xml
View File

@ -175,48 +175,44 @@
<p><em>Note: The protocol defined herein is currently in use at several large service providers in Europe. Others are welcome to use the protocol.</em></p>
</section1>
<section1 topic="Glossary" anchor='glossary'>
<table caption="Terms Used">
<tr>
<th>Term</th>
<th>Definition</th>
</tr>
<tr>
<td>Contact</td>
<td>A person with whom an IM User seeks to communicate, identified by a URI such as &lt;tel:PhoneNumber&gt; (see &rfc3966;) or &lt;mailto:EmailAddress&gt; (see &rfc2368;).</td>
</tr>
<tr>
<td>Customer</td>
<td>A person who is contracted for services with a ServiceProvider.</td>
</tr>
<tr>
<td>IM User</td>
<td>Any Customer who has registered for instant messaging services.</td>
</tr>
<tr>
<td>InteropPartner</td>
<td>Any company that agrees to interoperate using the protocol defined herein.</td>
</tr>
<tr>
<td>JID</td>
<td>The unique identifier of an IM User in the XMPP protocol. Outside the context of an IM session, a JID is of the form &BAREJID; ("bare JID"); within the context of an IM session, a JID is of the form &FULLJID; ("full JID").</td>
</tr>
<tr>
<td>ServiceProvider</td>
<td>A company that provides telephony or email services to a Customer.</td>
</tr>
<tr>
<td>URI</td>
<td>A Uniform Resource Identifier as defined in &rfc3986;. Specific URI schemes that may be useful in this specification include 'tel:', 'mailto:', and 'sip:', but any URI scheme may be used.</td>
</tr>
<tr>
<td>Waiting List</td>
<td>A list of Contacts whom an entity (IM User or InteropPartner) is waiting to hear about regarding their status as instant messaging users.</td>
</tr>
<tr>
<td>WaitingListService</td>
<td>An XMPP service that maintains Waiting lists for IM Users and/or InteropPartners.</td>
</tr>
</table>
<dl>
<di>
<dt>Contact</dt>
<dd>A person with whom an IM User seeks to communicate, identified by a URI such as &lt;tel:PhoneNumber&gt; (see &rfc3966;) or &lt;mailto:EmailAddress&gt; (see &rfc2368;).</dd>
</di>
<di>
<dt>Customer</dt>
<dd>A person who is contracted for services with a ServiceProvider.</dd>
</di>
<di>
<dt>IM User</dt>
<dd>Any Customer who has registered for instant messaging services.</dd>
</di>
<di>
<dt>InteropPartner</dt>
<dd>Any company that agrees to interoperate using the protocol defined herein.</dd>
</di>
<di>
<dt>JID</dt>
<dd>The unique identifier of an IM User in the XMPP protocol. Outside the context of an IM session, a JID is of the form &BAREJID; ("bare JID"); within the context of an IM session, a JID is of the form &FULLJID; ("full JID").</dd>
</di>
<di>
<dt>ServiceProvider</dt>
<dd>A company that provides telephony or email services to a Customer.</dd>
</di>
<di>
<dt>URI</dt>
<dd>A Uniform Resource Identifier as defined in &rfc3986;. Specific URI schemes that may be useful in this specification include 'tel:', 'mailto:', and 'sip:', but any URI scheme may be used.</dd>
</di>
<di>
<dt>Waiting List</dt>
<dd>A list of Contacts whom an entity (IM User or InteropPartner) is waiting to hear about regarding their status as instant messaging users.</dd>
</di>
<di>
<dt>WaitingListService</dt>
<dd>An XMPP service that maintains Waiting lists for IM Users and/or InteropPartners.</dd>
</di>
</dl>
</section1>
<section1 topic="Requirements" anchor='reqs'>
<p>This protocol is designed so that an IM User can:</p>