From 4323107b66f906061bdc349258791e28cd35a951 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 3 Oct 2007 03:14:18 +0000 Subject: [PATCH] 0.2 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1272 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0194.xml | 24 +++++++++++------------- xep-0195.xml | 30 +++++++++++++++++------------- xep-0196.xml | 50 +++++++++++++++++++++++++++----------------------- xep-0197.xml | 50 +++++++++++++++++++++++++++----------------------- xep-0199.xml | 10 ++++++++++ 5 files changed, 92 insertions(+), 72 deletions(-) diff --git a/xep-0194.xml b/xep-0194.xml index 8d2d8e50..757b9a21 100644 --- a/xep-0194.xml +++ b/xep-0194.xml @@ -25,7 +25,7 @@ &stpeter; 0.2 - 2007-09-14 + 2007-10-03 psa

Updated in accordance with XEP-0163.

 @@ -59,7 +59,7 @@ name The name of the chatroom - jdev + Jabber Development xs:string OPTIONAL @@ -81,14 +81,14 @@

NOTE: The datatypes specified above are defined in &w3xmlschema2;.

-

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 XEP-0060 protocol, especially the subset specified in XEP-0163 (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.

+

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.

- jdev + Jabber Development xmpp:jdev@conference.jabber.org @@ -103,18 +103,17 @@ - jdev + Jabber Development xmpp:jdev@conference.jabber.org -. -. -. + +[ ... ] ]]> -

When the user exits the room, the user's client SHOULD send an empty <room/> element to the node with the same ItemID:

+

When the user exits the room, the user's client SHOULD send an empty <room/> element with the same ItemID:

@@ -136,14 +135,13 @@ -. -. -. + +[ ... ] ]]> -

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).

+

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).

This document requires no interaction with &IANA;.

diff --git a/xep-0195.xml b/xep-0195.xml index f0dece36..6dc43957 100644 --- a/xep-0195.xml +++ b/xep-0195.xml @@ -21,8 +21,14 @@ - browsing + TO BE ASSIGNED &stpeter; + + 0.2 + 2007-10-03 + psa +

Updated in accordance with XEP-0163.

 + 0.1 2006-08-30 @@ -66,7 +72,7 @@ title - The title of the web page (i.e., value of the <title/> element) + The value of the <title/> element one small voice xs:string OPTIONAL @@ -82,14 +88,14 @@

NOTE: The datatypes specified above are defined in &w3xmlschema2;.

-

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 XEP-0060 protocol, especially the subset specified in XEP-0163 (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.

+

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.

- http://www.saint-andre.com/blog/ + https://stpeter.im/ @@ -103,17 +109,16 @@ - http://www.saint-andre.com/blog/ + https://stpeter.im/ -. -. -. + +[ ... ] ]]> -

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:

+

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:

@@ -135,14 +140,13 @@ -. -. -. + +[ ... ] ]]> -

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).

+

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).

This document requires no interaction with &IANA;.

diff --git a/xep-0196.xml b/xep-0196.xml index a5d217ba..d7e6bdb4 100644 --- a/xep-0196.xml +++ b/xep-0196.xml @@ -21,8 +21,14 @@ - gaming + TO BE ASSIGNED &stpeter; + + 0.2 + 2007-10-03 + psa +

Updated in accordance with XEP-0163.

 + 0.1 2006-08-30 @@ -41,7 +47,7 @@ -

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:

+

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:

@@ -103,13 +109,13 @@

NOTE: The datatypes specified above are defined in &w3xmlschema2;.

-

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 XEP-0060 protocol, especially the subset specified in XEP-0163 (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.

+

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.

- + - + chess http://www.chesspark.com/ @@ -122,9 +128,9 @@ - + - + chess http://www.chesspark.com/ @@ -132,17 +138,16 @@ -. -. -. + +[ ... ] ]]> -

When the user stops playing the game, the user's client SHOULD send an empty <game/> element to the node with the same ItemID:

+

When the user stops playing the game, the user's client SHOULD send an empty <game/> element with the same ItemID:

- + - + @@ -151,28 +156,27 @@ - + - + -. -. -. + +[ ... ] ]]> -

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).

+

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).

This document requires no interaction with &IANA;.

 - -

The ®ISTRAR; shall include 'http://jabber.org/protocol/gaming' in its registry of protocol namespaces.

+ +

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;.

 @@ -181,8 +185,8 @@ diff --git a/xep-0197.xml b/xep-0197.xml index 5fb717a6..1c9f9f47 100644 --- a/xep-0197.xml +++ b/xep-0197.xml @@ -21,7 +21,7 @@ - viewing + TO BE ASSIGNED &stpeter; Kevin @@ -29,6 +29,12 @@ kevin.hoekman@pandora.be kevinh@jabber.org + + 0.2 + 2007-10-03 + psa +

Updated in accordance with XEP-0163.

 + 0.1 2006-08-30 @@ -47,7 +53,7 @@ -

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:

+

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:

Element
@@ -144,13 +150,13 @@

NOTE: The datatypes specified above are defined in &w3xmlschema2;.

-

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 XEP-0060 protocol, especially the subset specified in XEP-0163 (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.

+

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.

- + - -

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).

+

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).

This document requires no interaction with &IANA;.

 - -

The ®ISTRAR; shall include 'http://jabber.org/protocol/viewing' in its registry of protocol namespaces.

+ +

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;.

 @@ -226,8 +230,8 @@ diff --git a/xep-0199.xml b/xep-0199.xml index 34c9e68d..d1de9ad9 100644 --- a/xep-0199.xml +++ b/xep-0199.xml @@ -20,6 +20,9 @@ ping + + http://www.xmpp.org/schemas/ping.xsd + &stpeter; 1.0 @@ -257,6 +260,13 @@ xmlns='urn:xmpp:ping' elementFormDefault='qualified'> + + + The protocol documented by this schema is defined in + XEP-0199: http://www.xmpp.org/extensions/xep-0199.html + + +
Element