aboutsummaryrefslogtreecommitdiff
path: root/xep-0197.xml
diff options
context:
space:
mode:
authorPeter Saint-Andre <stpeter@jabber.org>2006-10-04 18:02:04 +0000
committerPeter Saint-Andre <stpeter@jabber.org>2006-10-04 18:02:04 +0000
commit2d4af4ea52eacfa32677b5b50d9049e65d4e51fe (patch)
tree013560f8dfbecbf210ebaef052292470b9f6be8e /xep-0197.xml
parent0392f0dfcb98cc5079f8d5e9d39748c251f3b5be (diff)
JEP to XEP
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@50 4b5297f7-1745-476d-ba37-a9c6900126ab
Diffstat (limited to 'xep-0197.xml')
-rw-r--r--xep-0197.xml22
1 files changed, 11 insertions, 11 deletions
diff --git a/xep-0197.xml b/xep-0197.xml
index ea98f0d..3482e47 100644
--- a/xep-0197.xml
+++ b/xep-0197.xml
@@ -1,10 +1,10 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE jep SYSTEM '../jep.dtd' [
- <!ENTITY % ents SYSTEM '../jep.ent'>
+<!DOCTYPE xep SYSTEM 'xep.dtd' [
+ <!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
-<?xml-stylesheet type='text/xsl' href='../jep.xsl'?>
-<jep>
+<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
+<xep>
<header>
<title>User Viewing</title>
<abstract>This document defines an XMPP protocol extension for communicating information about the television shows, movies, or other videos that a user watches.</abstract>
@@ -16,8 +16,8 @@
<dependencies>
<spec>XMPP Core</spec>
<spec>XMPP IM</spec>
- <spec>JEP-0060</spec>
- <spec>JEP-0163</spec>
+ <spec>XEP-0060</spec>
+ <spec>XEP-0163</spec>
</dependencies>
<supersedes/>
<supersededby/>
@@ -33,7 +33,7 @@
<version>0.1</version>
<date>2006-08-30</date>
<initials>psa</initials>
- <remark><p>Initial JEP version.</p></remark>
+ <remark><p>Initial version.</p></remark>
</revision>
<revision>
<version>0.0.1</version>
@@ -43,7 +43,7 @@
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
- <p>&jep0060; and &jep0163; can be used to publish a wide variety of "extended presence" information about users. This document specifies an extended presence payload format that communicates information about the television shows, movies, or other videos that a user watches. This information may be of interest to a user's contacts and can also be used in social networking applications (e.g., IPTV systems).</p>
+ <p>&xep0060; and &xep0163; can be used to publish a wide variety of "extended presence" information about users. This document specifies an extended presence payload format that communicates information about the television shows, movies, or other videos that a user watches. This information may be of interest to a user's contacts and can also be used in social networking applications (e.g., IPTV systems).</p>
</section1>
<section1 topic='Protocol' anchor='protocol'>
<section2 topic='Container Element and Child Elements' anchor='protocol-elements'>
@@ -144,7 +144,7 @@
<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>JEP-0060</cite> protocol, especially the subset specified in <cite>JEP-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 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>
<example caption='User Publishes Viewing Information'><![CDATA[
<iq type='set' from='stpeter@jabber.org/work' id='viewing1'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
@@ -215,7 +215,7 @@
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document requires no interaction with &IANA;.</p>
</section1>
-<section1 topic='Jabber Registrar Considerations' anchor='registrar'>
+<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='registrar-ns'>
<p>The &REGISTRAR; shall include 'http://jabber.org/protocol/viewing' in its registry of protocol namespaces.</p>
</section2>
@@ -254,4 +254,4 @@
</xs:schema>
]]></code>
</section1>
-</jep>
+</xep>