From ea7d5986decc44eb129c904260bc53bfb2a6164e Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 18 Oct 2007 20:52:37 +0000 Subject: [PATCH] 1.1pre4 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1298 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0048.xml | 94 +++++++++++++++++++++++++++++++++++++++++----------- 1 file changed, 75 insertions(+), 19 deletions(-) diff --git a/xep-0048.xml b/xep-0048.xml index 8866d1b4..824bb9c2 100644 --- a/xep-0048.xml +++ b/xep-0048.xml @@ -7,7 +7,7 @@
Bookmarks - This document defines an XML data format for storing bookmarks to XMPP conference rooms and HTTP URLs. + This document defines an XML data format for storing bookmarks to chat rooms and web pages in XMPP. &LEGALNOTICE; 0048 Proposed @@ -33,10 +33,10 @@ &pgmillard; &stpeter; - 1.1pre3 - in progress, last updated 2007-09-27 + 1.1pre4 + in progress, last updated 2007-10-18 psa -

Specified use of publish-subscribe private information nodes as the preferred storage mechanism.

 +

For security reasons, actively discouraged use of the password element; specified use of publish-subscribe private information nodes as the preferred storage mechanism; cleaned up the text and examples.

 1.0 @@ -65,37 +65,96 @@
-

For ease-of-use in a Jabber client, it is desirable to have a way to store shortcuts to various services and resources (such as conference rooms and web pages) as 'bookmarks' that can be displayed in the user's client. Several Jabber clients have already agreed on and implemented a method to provide this service; that informal agreement is documented and expanded upon in this document. In particular, we introduce the 'storage' element (qualified by the 'storage:bookmarks' namespace) as a container for this sort of this data. While the <storage/> element can be stored using any XML storage mechanism, this document describes two such methods that are specific to XMPP.

+

For ease-of-use in a Jabber client, it is desirable to have a way to store shortcuts to various services and resources (such as conference rooms and web pages) as "bookmarks" that can be displayed in the user's client. Several Jabber clients have already agreed on and implemented a method to provide this service; that informal agreement is documented and expanded upon in this document. In particular, we introduce the <storage/> element (qualified by the 'storage:bookmarks' namespace) as a container for this sort of this data. While bookmarks data can be stored using any XML storage mechanism, this document recommends one method that is specific to XMPP.

 -

A storage element marked by the storage:bookmarks namespace will contain a collection of child elements, each representing a 'bookmark' to be displayed in the client. At present, only two sub-elements are defined, 'conference' for conference rooms and 'url' for normal URLs.

-

All elements under storage MUST allow a 'name' tag, which is the friendly name by which they will be displayed in the client. If an element lacks a 'name' tag, the client SHOULD generate an appropriate substitution based on the other available data.

+

A storage element qualified by the 'storage:bookmarks' namespace may contain a collection of child elements, each representing a bookmark to be displayed in a client. At present, only two sub-elements are defined: <conference/> for bookmarking of &xep0045; rooms and <url/> for bookmarking of web pages.

+

All child elements allow a 'name' attribute, which is the friendly name by which they will be displayed in the client. If an element lacks a 'name' attribute, the client SHOULD generate an appropriate substitution based on the other available data.

-

One of the most common uses of bookmarks will likely be to bookmark conference rooms on various Jabber servers. It is this aspect of the bookmark system which is used today by existing clients. In addition to the required 'jid' attribute, the conference element also possesses an 'autojoin' attribute, which determines whether or not the client should automatically join that conference room on login; this attribute is of type xs:boolean (see &w3xmlschema2;) and the default value is "false". &BOOLEANNOTE;

-

The conference element MAY also contain 'nick' and 'password' sub-elements; the XML character data from these elements should be used when joining the room from the bookmark. Password is, of course, important for joining potentially password-protected &xep0045; rooms.

+

A common use case is bookmarking of multi-user chat rooms. A room is bookmarked using the <conference/> child element. The syntax is as follows.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Element or AttributeDefinitionDatatypeInclusion
'autojoin' attributeWhether the client should automatically join the conference room on login.boolean defaulting to false &BOOLEANNOTE;OPTIONAL
'jid' attributeThe JabberID of the chat room.stringREQUIRED
'name' attributeA friendly name for the bookmark.stringRECOMMENDED
<nick/> elementThe user's preferred roomnick for the chatroom.stringOPTIONAL
<password/> elementUnencrypted string for the password needed to enter a password-protected room. Use of this element is now deprecated for security reasons.stringDEPRECATED
+

Note: The datatypes are as defined in &w3xmlschema2;.

Puck - titania ]]> -

This bookmark would be displayed as 'Council of Oberon' and, if activated, would attempt to join the conference room 'council@conference.underhill.org' with nickname 'Puck' and password 'titania'. A bookmark set may contain any number of conference rooms.

+

This bookmark would be displayed as 'Council of Oberon' and, if activated, would attempt to join the conference room 'council@conference.underhill.org' with nickname 'Puck'.

+

Note: A bookmark set may contain any number of conference rooms.

 -

URLs are fairly simple, as they only need to store a URL and a title, and the client then can simply launch the appropriate browser.

-

A URL element therefore only needs a 'url' tag in addition to the required 'name'.

- The <url/> element is designed for bookmarking web pages, i.e., HTTP or HTTPS URLs. The syntax is as follows.

+ + + + + + + + + + + + + + + + + + + +
AttributeDefinitionDatatypeInclusion
'name' attributeA friendly name for the bookmark.stringRECOMMENDED
'url' attributeThe HTTP or HTTPS URL of the web page.anyURIREQUIRED
+

When the user chooses a URL bookmark, the client should launch an appropriate browser or load the URL directly in the client (if the client is a web-client or includes web browsing functionality).

+ ]]> -

This bookmark would be displayed in the client as 'Complete Works of Shakespeare' and would take the user to http://the-tech.mit.edu/Shakespeare/ if activated. A bookmark set can contain any number of urls.

+

This bookmark would be displayed in the client as 'Complete Works of Shakespeare' and would take the user to <http://the-tech.mit.edu/Shakespeare/> when selected.

+

Note: A bookmark set can contain any number of URLs.

 @@ -113,7 +172,6 @@ autojoin='true' jid='theplay@conference.shakespeare.lit'> JC - Gl0b3 @@ -153,7 +211,6 @@ autojoin='true' jid='theplay@conference.shakespeare.lit'> JC - Gl0b3 @@ -203,7 +260,6 @@ autojoin='true' jid='theplay@conference.shakespeare.lit'> JC - Gl0b3 @@ -216,6 +272,7 @@

Security considerations related to object persistent via publish-subscribe are described in XEP-0060 and XEP-0223.

+

As noted, use of the <password/> child of the <conference/> element is deprecated and discouraged, since the password could be discovered by a third party, e.g. an eavedropper (if channel encryption is not used) or a server administrator.

 @@ -256,7 +313,6 @@ -