From 381ce85cd5c2d3414756557dbcb29e7936ceaff5 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 3 Jan 2013 15:49:00 -0700 Subject: [PATCH] 0.1 --- xep-0317.xml | 46 +++++++++++++++++++++++++++++++++++----------- 1 file changed, 35 insertions(+), 11 deletions(-) diff --git a/xep-0317.xml b/xep-0317.xml index d37a2fcb..8aed4b60 100644 --- a/xep-0317.xml +++ b/xep-0317.xml @@ -9,8 +9,8 @@ Hats This specification defines a more extensible model for roles and affiliations in Multi-User Chat rooms. &LEGALNOTICE; - xxxx - ProtoXEP + 0317 + Experimental Standards Track Standards Council @@ -23,6 +23,12 @@ NOT_YET_ASSIGNED &stpeter; + + 0.1 + 2013-01-03 + psa +

Initial published version approved for publication by the XMPP Council; clarified ad-hoc commands logic and syntax.

+
0.0.2 2012-12-09 @@ -82,6 +88,21 @@

Con: Clients won't show anything if they don't understand the custom namespace.

+

As noted, a participant can wear many hats. The following example shows a participant who is a MUC room owner and both a "host" and a "presenter" in an online meeting system.

+ + + + + + + + + + ]]>

Hats are added and removed using &xep0050;.

@@ -114,9 +135,9 @@ urn:xmpp:hats:commands - + urn:xmpp:hats:commands - - Terry + + terry.anderson@example.edu http://tech.example.edu/hats#TeacherAssistant @@ -165,6 +186,7 @@ status='completed'/> ]]> +

Note: only one hat is added at a time, and the form uses a field of type "list-single" to enforce that logic.

The following flow shows how to remove a hat.

@@ -176,7 +198,7 @@ xml:lang='en'> + node='urn:xmpp:hats:commands:doff'> urn:xmpp:hats:commands @@ -184,7 +206,9 @@ terry.anderson@example.edu - + + + @@ -196,7 +220,7 @@ type='result' xml:lang='en'> @@ -225,7 +249,7 @@ -

The concepts underlying this specification were first discussed several years ago at an XMPP Summit in Brussels, Belgium. Special thanks to Joe Hildebrand and Ralph Meijer for their contributions to those discussions. Thanks also to Kevin Smith and Matthew Wild for the feedback.

+

The concepts underlying this specification were first discussed several years ago at an XMPP Summit in Brussels, Belgium. Special thanks to Joe Hildebrand and Ralph Meijer for their contributions to those discussions. Thanks also to Matt Miller, Kevin Smith, and Matthew Wild for their feedback on the written specification.