No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0007.xml 6.4KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM "xep.ent">
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Conferencing SIG</title>
  10. <abstract>A proposal for a Jabber Interest Group that will discuss the protocol for implementing many-to-many communications.</abstract>
  11. &LEGALNOTICE;
  12. <number>0007</number>
  13. <status>Obsolete</status>
  14. <type>SIG Proposal</type>
  15. <sig>Conferencing</sig>
  16. <approver>Board</approver>
  17. <dependencies/>
  18. <supersedes/>
  19. <supersededby/>
  20. <shortname>N/A</shortname>
  21. <author>
  22. <firstname>David</firstname>
  23. <surname>Waite</surname>
  24. <email>akuma@jabber.org</email>
  25. <jid>akuma@jabber.org</jid>
  26. </author>
  27. <revision>
  28. <version>1.1</version>
  29. <date>2002-05-08</date>
  30. <initials>psa</initials>
  31. <remark>Changed Status to Obsolete per approval of XEP-0019.</remark>
  32. </revision>
  33. <revision>
  34. <version>1.0</version>
  35. <date>2001-08-03</date>
  36. <initials>akuma</initials>
  37. <remark>Initial version</remark>
  38. </revision>
  39. </header>
  40. <section1 topic='Introduction'>
  41. <p>The following proposal is for the formation of a Jabber Interest Group that will create a new conferencing protocol, as well as create additional functionality and standardize communications on top of said conferencing protocol.</p>
  42. </section1>
  43. <section1 topic='Base conferencing protocol'>
  44. <p>The initial task of the Conferencing SIG will be to propose a Jabber Conferencing specification that will solve various problems which exist in the current "groupchat" specification. This specification is meant to be a foundation for additional functionality; it defines the framework needed to provide additional features, without requiring changes to the framework specification itself. There is also to be a certain amount of feature-negotiation included; the conferencing service can define what features can be declared for a room, both as optional and required client features for room participation.</p>
  45. <p>The framework's scope consists of the following minimum functionality:</p>
  46. <ul>
  47. <li>Browsing a list of public rooms</li>
  48. <li>Finding a public room based on search parameters</li>
  49. <li>Creating new rooms</li>
  50. <li>Destroying rooms</li>
  51. <li>Entering existing rooms</li>
  52. <li>Altering functionality of a room</li>
  53. <li>Querying a room for public information</li>
  54. <li>Sending and accepting invitations to a room</li>
  55. <li>Changing a participant's nickname within a room</li>
  56. <li>Discovering and changing features on a running room</li>
  57. <li>Changing a participant's status within a room</li>
  58. <li>Sending a message to a room or a specific participant within a room</li>
  59. </ul>
  60. <p>In addition to these basic functions, we can imagine numerous different types of conferencing features; for example, hidden rooms created on the fly for discussions between a Jabber user and their friends or co-workers, transports providing access to similar foreign systems such as IRC, additional client functionality such as shared-location (URL/Co-browsing) and whiteboarding, and so on. There might also be requirements for security levels (for instance, normal participant, moderator, and room admin). Additional information may also be conveyed to users about one another, such as a user's real Jabber ID. Room entry or participation within a discussion might also have restrictions on some systems.</p>
  61. <p>The framework protocol is meant to provide a basis for designing these additional features. Some features, such as co-browsing, could be implemented entirely client-side; others may require significant logic within the conferencing implementation. In addition, some features may be optional for participation within a room, while other features could be required in order for a client to participate within a room.</p>
  62. </section1>
  63. <section1 topic='Justification for new Conferencing protocol'>
  64. <p>While the current "groupchat" specification is rather simple to implement, it is rather inflexible and cannot easily be extended; specifically, it has the following disadvantages:</p>
  65. <ul>
  66. <li>There is no control over how you enter a room - for instance, you can not specify a password for entering a password-protected room.</li>
  67. <li>There is no way to create a room without entering it, and no way to tell the state of the room without being a participant within it. This means among other things that a client can not transparently use groupchat for starting multi-user chats.</li>
  68. <li>Changes in room state are often conveyed via text messages rather than XML. Among other things, this limits the display of messages to the English language and limits a client author's freedom in displaying this information.</li>
  69. <li>A Participant's entry into a room is abstracted from their real Jabber account in both the old and new protocols; however, "groupchat" provides no way of tracking users across nickname changes or across sessions within a conference room.</li>
  70. <li>The "groupchat" protocol has no way of performing feature negotiation (e.g., specifying the additional protocol elements needed to participate in a room, or optionally allowed from participants within a room). If there were participants with clients sending custom data through the room (such as XHTML or whiteboarding), you would receive that information even without your client being able to support it, and have no way of distinguishing altered behavior due to additional features of a "groupchat" implementation.</li>
  71. </ul>
  72. <p>This new conferencing protocol will be designed to solve these problems.</p>
  73. <p>Because of the prevalence of the existing "groupchat" specification for multi-user chats, a long conversion process is anticipated. A server implementation which supports both protocols will simply not allow "groupchat"-only clients to participate in rooms with required features.</p>
  74. </section1>
  75. <section1 topic='Continuing Development'>
  76. <p>As listed above, there is a fairly large number of features that could be developed on top of a well-designed framework. The Conferencing SIG will first be established to develop a framework, with features mainly being compared against the framework for feasibility of implementation. After a proposal has been formalized as a specification, the SIG will become a group for discussing and proposing new features, and for formally specifying those features.</p>
  77. </section1>
  78. </xep>