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-0069.xml 3.0KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
  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>Compliance SIG</title>
  10. <abstract>A proposal to form a SIG devoted to issues related to protocol compliance.</abstract>
  11. &LEGALNOTICE;
  12. <number>0069</number>
  13. <status>Deferred</status>
  14. <type>SIG Formation</type>
  15. <sig>None</sig>
  16. <dependencies/>
  17. <supersedes/>
  18. <supersededby/>
  19. <shortname>N/A</shortname>
  20. &stpeter;
  21. <revision>
  22. <version>0.1</version>
  23. <date>2003-01-29</date>
  24. <initials>psa</initials>
  25. <remark>Initial release</remark>
  26. </revision>
  27. </header>
  28. <section1 topic='Introduction'>
  29. <p>The XMPP Standards Foundation has an initiative underway to define and implement compliance testing of software that is based on XMPP and XSF-approved protocols. To date, participation in this compliance program has been limited to elected members of the XSF. However, not all matters related to the compliance program need to be limited to XSF members. In particular, it would be valuable to receive community feedback and input regarding test plans, testing software, and the like. In order to broaden participation, we propose that the XSF form a standing Jabber Interest Group devoted to compliance.</p>
  30. </section1>
  31. <section1 topic='Scope and Role'>
  32. <p>The Compliance SIG shall provide a public forum for discussion and development of systems for testing compliance with the protocols defined and accepted by the XSF. It shall not have ultimate accountability for the XSF compliance program; rather, that accountability shall rest with the members-only Compliance Team. The Compliance SIG shall act in an advisory capacity in relation to the Compliance Team. In essence, the relationship between the Compliance SIG and the Compliance Team is analagous to the relationship between the Standards SIG and the Jabber Council.</p>
  33. <p>In particular, the Compliance SIG shall work with the Compliance Team to define the processes, standards, test cases, and testing software required by the compliance program. However, the Compliance SIG shall not be privy to actual testing results, which shall be available only to the Compliance Team.</p>
  34. </section1>
  35. <section1 topic='Membership'>
  36. <p>The Compliance SIG shall be open to the public and shall not be limited to elected members of the XMPP Standards Foundation. Compliance SIG discussions shall be conducted on a dedicated mailing list &lt;compliance-jig@jabber.org&gt; as well as in the &lt;foundation@conference.jabber.org&gt; chatroom.</p>
  37. </section1>
  38. <section1 topic='Lifetime'>
  39. <p>The Compliance SIG shall be a standing SIG, and shall exist as long as the XSF compliance program is in operation.</p>
  40. </section1>
  41. <section1 topic='Deliverables'>
  42. <p>The Compliance SIG shall produce at least the following deliverables:</p>
  43. <ul>
  44. <li>Documentation of the testing process</li>
  45. <li>Compliance test plans</li>
  46. <li>Compliance testing software</li>
  47. <li>Logo requirements</li>
  48. </ul>
  49. </section1>
  50. </xep>