mirror of https://github.com/moparisthebest/xeps
0.2
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1272 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre
parent
97bd9b90a9
commit
4323107b66
24
xep-0194.xml
24
xep-0194.xml
|
|
@ -25,7 +25,7 @@
|
|||
&stpeter;
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2007-09-14</date>
|
||||
<date>2007-10-03</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Updated in accordance with XEP-0163.</p></remark>
|
||||
</revision>
|
||||
|
|
@ -59,7 +59,7 @@
|
|||
<tr>
|
||||
<td>name</td>
|
||||
<td>The name of the chatroom</td>
|
||||
<td>jdev</td>
|
||||
<td>Jabber Development</td>
|
||||
<td>xs:string</td>
|
||||
<td>OPTIONAL</td>
|
||||
</tr>
|
||||
|
|
@ -81,14 +81,14 @@
|
|||
<p>NOTE: The datatypes specified above are defined in &w3xmlschema2;.</p>
|
||||
</section2>
|
||||
<section2 topic='Transport Mechanism' anchor='protocol-transport'>
|
||||
<p>When a user joins a room, its client may publish that fact to a special pubsub or PEP node (if a PEP node, the NodeID is "http://www.xmpp.org/extensions/xep-0194.html#ns" &NSNOTE;). The chatting information SHOULD be communicated and transported by means of the <cite>XEP-0060</cite> protocol, especially the subset specified in <cite>XEP-0163</cite> (as shown in the following examples). Because chatroom information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the &PRESENCE; stanza type.</p>
|
||||
<p>When a user joins a room, its client may publish that fact to PEP node whose NodeID is "http://www.xmpp.org/extensions/xep-0194.html#ns" &NSNOTE; or to a generic pubsub node. Because chatroom information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the &PRESENCE; stanza type.</p>
|
||||
<example caption='User Publishes Chatting Information'><![CDATA[
|
||||
<iq type='set' from='stpeter@jabber.org/work' id='chatting1'>
|
||||
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
|
||||
<publish node='http://www.xmpp.org/extensions/xep-0194.html#ns'>
|
||||
<item id='1b395148292c0b0ab3a83bb2c22909bf83d2a80b'>
|
||||
<room xmlns='http://www.xmpp.org/extensions/xep-0194.html#ns'>
|
||||
<name>jdev</name>
|
||||
<name>Jabber Development</name>
|
||||
<uri>xmpp:jdev@conference.jabber.org</uri>
|
||||
</room>
|
||||
</item>
|
||||
|
|
@ -103,18 +103,17 @@
|
|||
<items node='http://www.xmpp.org/extensions/xep-0194.html#ns'>
|
||||
<item id='1b395148292c0b0ab3a83bb2c22909bf83d2a80b'>
|
||||
<room xmlns='http://www.xmpp.org/extensions/xep-0194.html#ns'>
|
||||
<name>jdev</name>
|
||||
<name>Jabber Development</name>
|
||||
<uri>xmpp:jdev@conference.jabber.org</uri>
|
||||
</room>
|
||||
</item>
|
||||
</items>
|
||||
</event>
|
||||
</message>
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
[ ... ]
|
||||
]]></example>
|
||||
<p>When the user exits the room, the user's client SHOULD send an empty <room/> element to the node with the same ItemID:</p>
|
||||
<p>When the user exits the room, the user's client SHOULD send an empty <room/> element with the same ItemID:</p>
|
||||
<example caption='User Publishes Exit Information'><![CDATA[
|
||||
<iq type='set' from='stpeter@jabber.org/work' id='chatting2'>
|
||||
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
|
||||
|
|
@ -136,14 +135,13 @@
|
|||
</items>
|
||||
</event>
|
||||
</message>
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
[ ... ]
|
||||
]]></example>
|
||||
</section2>
|
||||
</section1>
|
||||
<section1 topic='Security Considerations' anchor='security'>
|
||||
<p>The chat rooms that a user visits may be sensitive. A client must provide a way for a user to configure which rooms or types of rooms will not be published (e.g., via user preferences).</p>
|
||||
<p>The chat rooms that a user visits may be sensitive. A client MUST provide a way for a user to configure which rooms or types of rooms will not be published (e.g., via user preferences).</p>
|
||||
</section1>
|
||||
<section1 topic='IANA Considerations' anchor='iana'>
|
||||
<p>This document requires no interaction with &IANA;.</p>
|
||||
|
|
|
|||
30
xep-0195.xml
30
xep-0195.xml
|
|
@ -21,8 +21,14 @@
|
|||
</dependencies>
|
||||
<supersedes/>
|
||||
<supersededby/>
|
||||
<shortname>browsing</shortname>
|
||||
<shortname>TO BE ASSIGNED</shortname>
|
||||
&stpeter;
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2007-10-03</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Updated in accordance with XEP-0163.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.1</version>
|
||||
<date>2006-08-30</date>
|
||||
|
|
@ -66,7 +72,7 @@
|
|||
</tr>
|
||||
<tr>
|
||||
<td>title</td>
|
||||
<td>The title of the web page (i.e., value of the <title/> element)</td>
|
||||
<td>The value of the <title/> element</td>
|
||||
<td>one small voice</td>
|
||||
<td>xs:string</td>
|
||||
<td>OPTIONAL</td>
|
||||
|
|
@ -82,14 +88,14 @@
|
|||
<p>NOTE: The datatypes specified above are defined in &w3xmlschema2;.</p>
|
||||
</section2>
|
||||
<section2 topic='Transport Mechanism' anchor='protocol-transport'>
|
||||
<p>When a user visits a web page, its client may publish that fact to a special pubsub or PEP node (if a PEP node, the NodeID is "http://www.xmpp.org/extensions/xep-0195.html#ns" &NSNOTE;). The web page information SHOULD be communicated and transported by means of the <cite>XEP-0060</cite> protocol, especially the subset specified in <cite>XEP-0163</cite> (as shown in the following examples). Because browsing information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the &PRESENCE; stanza type.</p>
|
||||
<p>When a user visits a web page, its client may publish that fact to a PEP node whose NodeID is "http://www.xmpp.org/extensions/xep-0195.html#ns" &NSNOTE; or to a generic pubsub node. Because browsing information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the &PRESENCE; stanza type.</p>
|
||||
<example caption='User Publishes Browsing Information'><![CDATA[
|
||||
<iq type='set' from='stpeter@jabber.org/work' id='browsing1'>
|
||||
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
|
||||
<publish node='http://www.xmpp.org/extensions/xep-0195.html#ns'>
|
||||
<item id='da6abe63d1e5ed45a6de466732abff72e6fccb93'>
|
||||
<page xmlns='http://www.xmpp.org/extensions/xep-0195.html#ns'>
|
||||
<uri>http://www.saint-andre.com/blog/</uri>
|
||||
<uri>https://stpeter.im/</uri>
|
||||
</page>
|
||||
</item>
|
||||
</publish>
|
||||
|
|
@ -103,17 +109,16 @@
|
|||
<items node='http://www.xmpp.org/extensions/xep-0195.html#ns'>
|
||||
<item id='da6abe63d1e5ed45a6de466732abff72e6fccb93'>
|
||||
<page xmlns='http://www.xmpp.org/extensions/xep-0195.html#ns'>
|
||||
<uri>http://www.saint-andre.com/blog/</uri>
|
||||
<uri>https://stpeter.im/</uri>
|
||||
</page>
|
||||
</item>
|
||||
</items>
|
||||
</event>
|
||||
</message>
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
[ ... ]
|
||||
]]></example>
|
||||
<p>When the user stops browsing the page (e.g., by closing the browser window or tab), the user's client SHOULD send an empty <page/> element to the node with the same ItemID:</p>
|
||||
<p>When the user stops browsing the page (e.g., by closing the browser window or tab), the user's client SHOULD send an empty <page/> element with the same ItemID:</p>
|
||||
<example caption='User Publishes Stop Information'><![CDATA[
|
||||
<iq type='set' from='stpeter@jabber.org/work' id='browsing2'>
|
||||
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
|
||||
|
|
@ -135,14 +140,13 @@
|
|||
</items>
|
||||
</event>
|
||||
</message>
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
[ ... ]
|
||||
]]></example>
|
||||
</section2>
|
||||
</section1>
|
||||
<section1 topic='Security Considerations' anchor='security'>
|
||||
<p>The web pages that a user visits may be sensitive. A client must provide a way for a user to configure which pages or types of pages will not be published (e.g., via user preferences).</p>
|
||||
<p>The web pages that a user visits may be sensitive. A client MUST provide a way for a user to configure which pages or types of pages will not be published (e.g., via user preferences).</p>
|
||||
</section1>
|
||||
<section1 topic='IANA Considerations' anchor='iana'>
|
||||
<p>This document requires no interaction with &IANA;.</p>
|
||||
|
|
|
|||
50
xep-0196.xml
50
xep-0196.xml
|
|
@ -21,8 +21,14 @@
|
|||
</dependencies>
|
||||
<supersedes/>
|
||||
<supersededby/>
|
||||
<shortname>gaming</shortname>
|
||||
<shortname>TO BE ASSIGNED</shortname>
|
||||
&stpeter;
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2007-10-03</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Updated in accordance with XEP-0163.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.1</version>
|
||||
<date>2006-08-30</date>
|
||||
|
|
@ -41,7 +47,7 @@
|
|||
</section1>
|
||||
<section1 topic='Protocol' anchor='protocol'>
|
||||
<section2 topic='Container Element and Child Elements' anchor='protocol-elements'>
|
||||
<p>Information about games is provided by the user (or automated integration with gaming systems) and is propagated on the network by the user's client. The information container for gaming data is a <game/> element that is qualified by the 'http://jabber.org/protocol/gaming' namespace. The game information itself is provided as the XML character data of the following children of the <game/> element:</p>
|
||||
<p>Information about games is provided by the user (or automated integration with gaming systems) and is propagated on the network by the user's client. The information container for gaming data is a <game/> element that is qualified by the 'http://www.xmpp.org/extensions/xep-0196.html#ns' namespace. The game information itself is provided as the XML character data of the following children of the <game/> element:</p>
|
||||
<table caption='Child Elements'>
|
||||
<tr>
|
||||
<th>Element</th>
|
||||
|
|
@ -103,13 +109,13 @@
|
|||
<p>NOTE: The datatypes specified above are defined in &w3xmlschema2;.</p>
|
||||
</section2>
|
||||
<section2 topic='Transport Mechanism' anchor='protocol-transport'>
|
||||
<p>When a user starts playing a game, its client may publish that fact to a special pubsub or PEP node (if a PEP node, the NodeID is "http://jabber.org/protocol/gaming"). The gaming information SHOULD be communicated and transported by means of the <cite>XEP-0060</cite> protocol, especially the subset specified in <cite>XEP-0163</cite> (as shown in the following examples). Because gaming information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the &PRESENCE; stanza type.</p>
|
||||
<p>When a user starts playing a game, its client may publish that fact to PEP node whose NodeID is "http://www.xmpp.org/extensions/xep-0196.html#ns" &NSNOTE; or to a generic pubsub node. Because gaming information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the &PRESENCE; stanza type.</p>
|
||||
<example caption='User Publishes Gaming Information'><![CDATA[
|
||||
<iq type='set' from='stpeter@jabber.org/work' id='gaming1'>
|
||||
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
|
||||
<publish node='http://jabber.org/protocol/gaming'>
|
||||
<publish node='http://www.xmpp.org/extensions/xep-0196.html#ns'>
|
||||
<item id='1feea9cceec2537e1b561e66d45bc566e276f22f'>
|
||||
<game xmlns='http://jabber.org/protocol/gaming'>
|
||||
<game xmlns='http://www.xmpp.org/extensions/xep-0196.html#ns'>
|
||||
<name>chess</name>
|
||||
<uri>http://www.chesspark.com/</uri>
|
||||
</game>
|
||||
|
|
@ -122,9 +128,9 @@
|
|||
<example caption='Gaming Information is Delivered to All Subscribers'><![CDATA[
|
||||
<message from='stpeter@jabber.org' to='maineboy@jabber.org'>
|
||||
<event xmlns='http://jabber.org/protocol/pubsub#event'>
|
||||
<items node='http://jabber.org/protocol/gaming'>
|
||||
<items node='http://www.xmpp.org/extensions/xep-0196.html#ns'>
|
||||
<item id='1feea9cceec2537e1b561e66d45bc566e276f22f'>
|
||||
<game xmlns='http://jabber.org/protocol/gaming'>
|
||||
<game xmlns='http://www.xmpp.org/extensions/xep-0196.html#ns'>
|
||||
<name>chess</name>
|
||||
<uri>http://www.chesspark.com/</uri>
|
||||
</game>
|
||||
|
|
@ -132,17 +138,16 @@
|
|||
</items>
|
||||
</event>
|
||||
</message>
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
[ ... ]
|
||||
]]></example>
|
||||
<p>When the user stops playing the game, the user's client SHOULD send an empty <game/> element to the node with the same ItemID:</p>
|
||||
<p>When the user stops playing the game, the user's client SHOULD send an empty <game/> element with the same ItemID:</p>
|
||||
<example caption='User Publishes Stop Information'><![CDATA[
|
||||
<iq type='set' from='stpeter@jabber.org/work' id='gaming2'>
|
||||
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
|
||||
<publish node='http://jabber.org/protocol/gaming'>
|
||||
<publish node='http://www.xmpp.org/extensions/xep-0196.html#ns'>
|
||||
<item id='1feea9cceec2537e1b561e66d45bc566e276f22f'>
|
||||
<game xmlns='http://jabber.org/protocol/gaming'/>
|
||||
<game xmlns='http://www.xmpp.org/extensions/xep-0196.html#ns'/>
|
||||
</item>
|
||||
</publish>
|
||||
</pubsub>
|
||||
|
|
@ -151,28 +156,27 @@
|
|||
<example caption='Stop Information is Delivered to All Subscribers'><![CDATA[
|
||||
<message from='stpeter@jabber.org' to='maineboy@jabber.org'>
|
||||
<event xmlns='http://jabber.org/protocol/pubsub#event'>
|
||||
<items node='http://jabber.org/protocol/gaming'>
|
||||
<items node='http://www.xmpp.org/extensions/xep-0196.html#ns'>
|
||||
<item id='1feea9cceec2537e1b561e66d45bc566e276f22f'>
|
||||
<game xmlns='http://jabber.org/protocol/gaming'/>
|
||||
<game xmlns='http://www.xmpp.org/extensions/xep-0196.html#ns'/>
|
||||
</item>
|
||||
</items>
|
||||
</event>
|
||||
</message>
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
[ ... ]
|
||||
]]></example>
|
||||
</section2>
|
||||
</section1>
|
||||
<section1 topic='Security Considerations' anchor='security'>
|
||||
<p>The games that a user plays may be sensitive. A client must provide a way for a user to configure which games or types of games will not be published (e.g., via user preferences).</p>
|
||||
<p>The games that a user plays may be sensitive. A client MUST provide a way for a user to configure which games or types of games will not be published (e.g., via user preferences).</p>
|
||||
</section1>
|
||||
<section1 topic='IANA Considerations' anchor='iana'>
|
||||
<p>This document requires no interaction with &IANA;.</p>
|
||||
</section1>
|
||||
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
|
||||
<section2 topic='Protocol Namespaces' anchor='registrar-ns'>
|
||||
<p>The ®ISTRAR; shall include 'http://jabber.org/protocol/gaming' in its registry of protocol namespaces.</p>
|
||||
<section2 topic='Protocol Namespaces' anchor='ns'>
|
||||
<p>Until this specification advances to a status of Draft, its associated namespace shall be "http://www.xmpp.org/extensions/xep-0196.html#ns"; upon advancement of this specification, the ®ISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.</p>
|
||||
</section2>
|
||||
</section1>
|
||||
<section1 topic='XML Schema' anchor='schema'>
|
||||
|
|
@ -181,8 +185,8 @@
|
|||
|
||||
<xs:schema
|
||||
xmlns:xs='http://www.w3.org/2001/XMLSchema'
|
||||
targetNamespace='http://jabber.org/protocol/gaming'
|
||||
xmlns='http://jabber.org/protocol/gaming'
|
||||
targetNamespace='http://www.xmpp.org/extensions/xep-0196.html#ns'
|
||||
xmlns='http://www.xmpp.org/extensions/xep-0196.html#ns'
|
||||
elementFormDefault='qualified'>
|
||||
|
||||
<xs:element name='game'>
|
||||
|
|
|
|||
50
xep-0197.xml
50
xep-0197.xml
|
|
@ -21,7 +21,7 @@
|
|||
</dependencies>
|
||||
<supersedes/>
|
||||
<supersededby/>
|
||||
<shortname>viewing</shortname>
|
||||
<shortname>TO BE ASSIGNED</shortname>
|
||||
&stpeter;
|
||||
<author>
|
||||
<firstname>Kevin</firstname>
|
||||
|
|
@ -29,6 +29,12 @@
|
|||
<email>kevin.hoekman@pandora.be</email>
|
||||
<jid>kevinh@jabber.org</jid>
|
||||
</author>
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2007-10-03</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Updated in accordance with XEP-0163.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.1</version>
|
||||
<date>2006-08-30</date>
|
||||
|
|
@ -47,7 +53,7 @@
|
|||
</section1>
|
||||
<section1 topic='Protocol' anchor='protocol'>
|
||||
<section2 topic='Container Element and Child Elements' anchor='protocol-elements'>
|
||||
<p>Information about video viewing is provided by the user (or automated integration with video systems) and is propagated on the network by the user's client. The information container for video viewing data is a <video/> element that is qualified by the 'http://jabber.org/protocol/viewing' namespace. The video information itself is provided as the XML character data of the following children of the <video/> element:</p>
|
||||
<p>Information about video viewing is provided by the user (or automated integration with video systems) and is propagated on the network by the user's client. The information container for video viewing data is a <video/> element that is qualified by the 'http://www.xmpp.org/extensions/xep-0197.html#ns' namespace. The video information itself is provided as the XML character data of the following children of the <video/> element:</p>
|
||||
<table caption='Child Elements'>
|
||||
<tr>
|
||||
<th>Element</th>
|
||||
|
|
@ -144,13 +150,13 @@
|
|||
<p>NOTE: The datatypes specified above are defined in &w3xmlschema2;.</p>
|
||||
</section2>
|
||||
<section2 topic='Transport Mechanism' anchor='protocol-transport'>
|
||||
<p>When a user starts watching a video, its client may publish that fact to a special pubsub or PEP node (if a PEP node, the NodeID is "http://jabber.org/protocol/viewing"). The viewing information SHOULD be communicated and transported by means of the <cite>XEP-0060</cite> protocol, especially the subset specified in <cite>XEP-0163</cite> (as shown in the following examples). Because viewing information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the &PRESENCE; stanza type.</p>
|
||||
<p>When a user starts watching a video, its client may publish that fact to a PEP node whose NodeID is "http://www.xmpp.org/extensions/xep-0197.html#ns" &NSNOTE; or to a generic pubsub node. Because viewing information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the &PRESENCE; stanza type.</p>
|
||||
<example caption='User Publishes Viewing Information'><![CDATA[
|
||||
<iq type='set' from='stpeter@jabber.org/work' id='viewing1'>
|
||||
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
|
||||
<publish node='http://jabber.org/protocol/viewing'>
|
||||
<publish node='http://www.xmpp.org/extensions/xep-0197.html#ns'>
|
||||
<item id='8eaa8ae16651455376dab4eae45772337e9ec372'>
|
||||
<video xmlns='http://jabber.org/protocol/viewing'>
|
||||
<video xmlns='http://www.xmpp.org/extensions/xep-0197.html#ns'>
|
||||
<name>Mystery Science Theater 3000</name>
|
||||
<episode>807</episode>
|
||||
<description>Terror From The Year 5000</description>
|
||||
|
|
@ -165,9 +171,9 @@
|
|||
<example caption='Viewing Information is Delivered to All Subscribers'><![CDATA[
|
||||
<message from='stpeter@jabber.org' to='maineboy@jabber.org'>
|
||||
<event xmlns='http://jabber.org/protocol/pubsub#event'>
|
||||
<items node='http://jabber.org/protocol/viewing'>
|
||||
<items node='http://www.xmpp.org/extensions/xep-0197.html#ns'>
|
||||
<item id='8eaa8ae16651455376dab4eae45772337e9ec372'>
|
||||
<video xmlns='http://jabber.org/protocol/viewing'>
|
||||
<video xmlns='http://www.xmpp.org/extensions/xep-0197.html#ns'>
|
||||
<name>Mystery Science Theater 3000</name>
|
||||
<episode>807</episode>
|
||||
<description>Terror From The Year 5000</description>
|
||||
|
|
@ -177,17 +183,16 @@
|
|||
</items>
|
||||
</event>
|
||||
</message>
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
[ ... ]
|
||||
]]></example>
|
||||
<p>When the user stops watching the video, the user's client SHOULD send an empty <video/> element to the node with the same ItemID:</p>
|
||||
<p>When the user stops watching the video, the user's client SHOULD send an empty <video/> element with the same ItemID:</p>
|
||||
<example caption='User Publishes Stop Information'><![CDATA[
|
||||
<iq type='set' from='stpeter@jabber.org/work' id='viewing2'>
|
||||
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
|
||||
<publish node='http://jabber.org/protocol/viewing'>
|
||||
<publish node='http://www.xmpp.org/extensions/xep-0197.html#ns'>
|
||||
<item id='8eaa8ae16651455376dab4eae45772337e9ec372'>
|
||||
<video xmlns='http://jabber.org/protocol/viewing'/>
|
||||
<video xmlns='http://www.xmpp.org/extensions/xep-0197.html#ns'/>
|
||||
</item>
|
||||
</publish>
|
||||
</pubsub>
|
||||
|
|
@ -196,28 +201,27 @@
|
|||
<example caption='Stop Information is Delivered to All Subscribers'><![CDATA[
|
||||
<message from='stpeter@jabber.org' to='maineboy@jabber.org'>
|
||||
<event xmlns='http://jabber.org/protocol/pubsub#event'>
|
||||
<items node='http://jabber.org/protocol/viewing'>
|
||||
<items node='http://www.xmpp.org/extensions/xep-0197.html#ns'>
|
||||
<item id='8eaa8ae16651455376dab4eae45772337e9ec372'>
|
||||
<video xmlns='http://jabber.org/protocol/viewing'/>
|
||||
<video xmlns='http://www.xmpp.org/extensions/xep-0197.html#ns'/>
|
||||
</item>
|
||||
</items>
|
||||
</event>
|
||||
</message>
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
[ ... ]
|
||||
]]></example>
|
||||
</section2>
|
||||
</section1>
|
||||
<section1 topic='Security Considerations' anchor='security'>
|
||||
<p>The videos that a user watches may be sensitive. A client must provide a way for a user to configure which videos or types of videos will not be published (e.g., via user preferences).</p>
|
||||
<p>The videos that a user watches may be sensitive. A client MUST provide a way for a user to configure which videos or types of videos will not be published (e.g., via user preferences).</p>
|
||||
</section1>
|
||||
<section1 topic='IANA Considerations' anchor='iana'>
|
||||
<p>This document requires no interaction with &IANA;.</p>
|
||||
</section1>
|
||||
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
|
||||
<section2 topic='Protocol Namespaces' anchor='registrar-ns'>
|
||||
<p>The ®ISTRAR; shall include 'http://jabber.org/protocol/viewing' in its registry of protocol namespaces.</p>
|
||||
<section2 topic='Protocol Namespaces' anchor='ns'>
|
||||
<p>Until this specification advances to a status of Draft, its associated namespace shall be "http://www.xmpp.org/extensions/xep-0197.html#ns"; upon advancement of this specification, the ®ISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.</p>
|
||||
</section2>
|
||||
</section1>
|
||||
<section1 topic='XML Schema' anchor='schema'>
|
||||
|
|
@ -226,8 +230,8 @@
|
|||
|
||||
<xs:schema
|
||||
xmlns:xs='http://www.w3.org/2001/XMLSchema'
|
||||
targetNamespace='http://jabber.org/protocol/viewing'
|
||||
xmlns='http://jabber.org/protocol/viewing'
|
||||
targetNamespace='http://www.xmpp.org/extensions/xep-0197.html#ns'
|
||||
xmlns='http://www.xmpp.org/extensions/xep-0197.html#ns'
|
||||
elementFormDefault='qualified'>
|
||||
|
||||
<xs:element name='room'>
|
||||
|
|
|
|||
10
xep-0199.xml
10
xep-0199.xml
|
|
@ -20,6 +20,9 @@
|
|||
<supersedes/>
|
||||
<supersededby/>
|
||||
<shortname>ping</shortname>
|
||||
<schemaloc>
|
||||
<url>http://www.xmpp.org/schemas/ping.xsd</url>
|
||||
</schemaloc>
|
||||
&stpeter;
|
||||
<revision>
|
||||
<version>1.0</version>
|
||||
|
|
@ -257,6 +260,13 @@
|
|||
xmlns='urn:xmpp:ping'
|
||||
elementFormDefault='qualified'>
|
||||
|
||||
<xs:annotation>
|
||||
<xs:documentation>
|
||||
The protocol documented by this schema is defined in
|
||||
XEP-0199: http://www.xmpp.org/extensions/xep-0199.html
|
||||
</xs:documentation>
|
||||
</xs:annotation>
|
||||
|
||||
<xs:element name='ping' type='empty'/>
|
||||
|
||||
<xs:simpleType name='empty'>
|
||||
|
|
|
|||
Loading…
Reference in New Issue