-
Notifications
You must be signed in to change notification settings - Fork 122
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@33 4b5297f7-1745-476d-ba37-a9c6900126ab
- Loading branch information
Peter Saint-Andre
committed
Oct 3, 2006
1 parent
462ac0b
commit 7a35010
Showing
10 changed files
with
111 additions
and
105 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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>vcard-temp</title> | ||
| <abstract>This specification provides canonical documentation of the vCard-XML format currently in use within the Jabber community.</abstract> | ||
|
|
@@ -46,7 +46,7 @@ | |
| </revision> | ||
| </header> | ||
| <section1 topic='Introduction'> | ||
| <p>This specification documents the vCard-XML format currently in use within the Jabber community. A future JEP will recommend a standards-track protocol to supersede this informational document.</p> | ||
| <p>This specification documents the vCard-XML format currently in use within the Jabber community. A future specification will recommend a standards-track protocol to supersede this informational document.</p> | ||
| <p>The basic functionality is for a user to store and retrieve an XML representation of his or her vCard using the data storage capabilities native to all existing Jabber server implementations. This is done by by sending an <iq/> of type "set" (storage) or "get" (retrieval) to one's Jabber server containing a <vCard/> child scoped by the 'vcard-temp' namespace, with the <vCard/> element containing the actual vCard-XML elements as defined by the vCard-XML DTD. Other users may then view one's vCard information.</p> | ||
| </section1> | ||
| <section1 topic='History'> | ||
|
|
@@ -161,14 +161,14 @@ | |
| <p>There are no security features or concerns related to this proposal.</p> | ||
| </section1> | ||
| <section1 topic='IANA Considerations'> | ||
| <p>This JEP requires no interaction with &IANA;.</p> | ||
| <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-protocol'> | ||
| <p>The ®ISTRAR; includes the 'vcard-temp' namespace in its registry of official namespaces (see &NAMESPACES;).</p> | ||
| </section2> | ||
| <section2 topic='URI Query Types' anchor='registrar-querytypes'> | ||
| <p>As authorized by &jep0147;, the Jabber Registrar maintains a registry of queries and key-value pairs for use in XMPP URIs (see &QUERYTYPES;).</p> | ||
| <p>As authorized by &xep0147;, the XMPP Registrar maintains a registry of queries and key-value pairs for use in XMPP URIs (see &QUERYTYPES;).</p> | ||
| <p>The "vcard" querytype is registered as a vCard-related action.</p> | ||
| <example caption='vCard Action: IRI/URI'><![CDATA[ | ||
| xmpp:[email protected]?vcard | ||
|
|
@@ -184,7 +184,7 @@ xmpp:[email protected]?vcard | |
| <name>vcard</name> | ||
| <proto>vcard-temp</proto> | ||
| <desc>enables retrieval of an entity's vCard data</desc> | ||
| <doc>JEP-0054</doc> | ||
| <doc>XEP-0054</doc> | ||
| </querytype> | ||
| ]]></code> | ||
| </section2> | ||
|
|
@@ -521,4 +521,4 @@ PARTICULAR PURPOSE. | |
| <!-- ==== --> | ||
| ]]></code> | ||
| </section1> | ||
| </jep> | ||
| </xep> | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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>Jabber Search</title> | ||
| <abstract>This specification provides canonical documentation of the 'jabber:iq:search' namespace currently in use within the Jabber community.</abstract> | ||
|
|
@@ -21,7 +21,7 @@ | |
| <supersededby/> | ||
| <shortname>iq-search</shortname> | ||
| <schemaloc> | ||
| <url>http://jabber.org/protocol/iq-search/iq-search.xsd</url> | ||
| <url>http://www.xmpp.org/schemas/iq-search.xsd</url> | ||
| </schemaloc> | ||
| &stpeter; | ||
| <revision> | ||
|
|
@@ -51,7 +51,7 @@ | |
| </header> | ||
| <section1 topic='Introduction' anchor='intro'> | ||
| <p>This specification documents a protocol currently used to search information repositories on the Jabber network. To date, the jabber:iq:search protocol has been used mainly to search for people who have registered with user directories (e.g., the "Jabber User Directory" hosted at users.jabber.org). However, the jabber:iq:search protocol is not limited to user directories, and could be used to search other Jabber information repositories (such as chatroom directories) or even to provide a Jabber interface to conventional search engines.</p> | ||
| <p>The basic functionality is to query an information repository regarding the possible search fields, to send a search query, and to receive search results. Note well that there is currently no mechanism for paging through results or limiting the number of "hits", and that the allowable search fields are limited to those defined in the XML schema; however, extensibility MAY be provided via the &jep0004; protocol, as described below.</p> | ||
| <p>The basic functionality is to query an information repository regarding the possible search fields, to send a search query, and to receive search results. Note well that there is currently no mechanism for paging through results or limiting the number of "hits", and that the allowable search fields are limited to those defined in the XML schema; however, extensibility MAY be provided via the &xep0004; protocol, as described below.</p> | ||
| </section1> | ||
| <section1 topic='Use Cases' anchor='usecases'> | ||
| <section2 topic="Searching" anchor='usecases-search'> | ||
|
|
@@ -133,7 +133,7 @@ | |
| </section1> | ||
| <section1 topic='Extensibility' anchor='extensibility'> | ||
| <p>The fields defined in the 'jabber:iq:search' namespace are strictly limited to those specified in the schema. If a host needs to gather additional information, <strong>Data Forms</strong> SHOULD be used; a host MUST NOT add new fields to the 'jabber:iq:search' namespace. Support for extensibility via <strong>Data Forms</strong> is RECOMMENDED, but is not required for compliance with this JEP.</p> | ||
| <p>The extensibility mechanism for searching makes use of a hidden FORM_TYPE field for the purpose of standardizing field names within the form, as defined in &jep0068;. Implementations supporting this extensibility mechanism SHOULD support field standardization as well.</p> | ||
| <p>The extensibility mechanism for searching makes use of a hidden FORM_TYPE field for the purpose of standardizing field names within the form, as defined in &xep0068;. Implementations supporting this extensibility mechanism SHOULD support field standardization as well.</p> | ||
| <example caption='Entity Requests Search Fields from Service'><![CDATA[ | ||
| <iq type='get' | ||
| from='[email protected]/balcony' | ||
|
|
@@ -241,13 +241,13 @@ | |
| <section1 topic='IANA Considerations' anchor='iana'> | ||
| <p>This JEP requires no interaction with &IANA;.</p> | ||
| </section1> | ||
| <section1 topic='Jabber Registrar Considerations' anchor='registrar'> | ||
| <section1 topic='XMPP Registrar Considerations' anchor='registrar'> | ||
| <p>The ®ISTRAR; shall include the following information in its registries.</p> | ||
| <section2 topic='Protocol Namespaces' anchor='registrar-namespaces'> | ||
| <p>The Jabber Registrar includes the 'jabber:iq:search' namespace in its registry of protocol namespaces.</p> | ||
| <p>The XMPP Registrar includes the 'jabber:iq:search' namespace in its registry of protocol namespaces.</p> | ||
| </section2> | ||
| <section2 topic='Field Standardization' anchor='registrar-formtypes'> | ||
| <p>The following fields are reserved for use within jabber:x:data forms scoped by a FORM_TYPE of 'jabber:iq:search'; additional fields MAY be added via the Jabber Registrar's normal registration process but are outside the scope of this JEP.</p> | ||
| <p>The following fields are reserved for use within jabber:x:data forms scoped by a FORM_TYPE of 'jabber:iq:search'; additional fields MAY be added via the XMPP Registrar's normal registration process but are outside the scope of this JEP.</p> | ||
| <code caption='Registry Submission'><![CDATA[ | ||
| <form_type> | ||
| <name>jabber:iq:search</name> | ||
|
|
@@ -289,7 +289,7 @@ | |
| <xs:annotation> | ||
| <xs:documentation> | ||
| The protocol documented by this schema is defined in | ||
| JEP-0055: http://www.jabber.org/jeps/jep-0055.html | ||
| XEP-0055: http://www.xmpp.org/extensions/xep-0055.html | ||
| </xs:documentation> | ||
| </xs:annotation> | ||
|
|
@@ -324,4 +324,4 @@ | |
| </xs:schema> | ||
| ]]></code> | ||
| </section1> | ||
| </jep> | ||
| </xep> | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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>Extended Roster</title> | ||
| <abstract>This JEP defines a way to handle extended roster items.</abstract> | ||
|
|
@@ -51,7 +51,7 @@ | |
|
|
||
|
|
||
| <section1 topic="Where to store"> | ||
| <p>Using <tt>jabber:iq:private</tt> as in JEP-0048 <note><link url='http://www.jabber.org/jeps/jep-0048.html'>http://www.jabber.org/jeps/jep-0048.html</link></note> for storing this information has one big problem: it is hard to mantain roster data in two separate places. When a client is online, then the client application can handle <tt>jabber:iq:roster</tt> changes and make similar changes in private storage, but when the user is online with a few different resources, or when he is offline, then making the information consistent is very hard task (a roster can be changed when user offline, e.g. if someone is making an account transfer).</p> | ||
| <p>Using <tt>jabber:iq:private</tt> as in &xep0048; for storing this information has one big problem: it is hard to mantain roster data in two separate places. When a client is online, then the client application can handle <tt>jabber:iq:roster</tt> changes and make similar changes in private storage, but when the user is online with a few different resources, or when he is offline, then making the information consistent is very hard task (a roster can be changed when user offline, e.g. if someone is making an account transfer).</p> | ||
| <p>But we have a place where this problem does not exist: <tt>jabber:iq:roster</tt>. We can store it in <tt><item/></tt> subtags. Existing server implementation MUST NOT remove <tt><x/></tt> tags from it. In this case all information always relates to its JID and disappears when this JID removed.</p> | ||
| </section1> | ||
|
|
||
|
|
@@ -63,7 +63,7 @@ | |
| type="text">]]></example> | ||
| </section2> | ||
| <section2 topic="Server-side information"> | ||
| <p>This information is implementation-dependent, so to provide flexibility for it, the <tt>jabber:x:data</tt> namespace defined in JEP-0004 <note><link url='http://www.jabber.org/jeps/jep-0004.html'>http://www.jabber.org/jeps/jep-0004.html</link></note> must be used. The client can set these parameters by setting this item with this form with <tt>type='submit'</tt>.</p> | ||
| <p>This information is implementation-dependent, so to provide flexibility for it, the <tt>jabber:x:data</tt> namespace defined in &xep0004; must be used. The client can set these parameters by setting this item with this form with <tt>type='submit'</tt>.</p> | ||
| <example><![CDATA[<item jid="[email protected]" | ||
| name="Romeo" | ||
| subscription="both"> | ||
|
|
@@ -179,4 +179,4 @@ | |
| </section2> | ||
| </section1> | ||
|
|
||
| </jep> | ||
| </xep> | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.