From 8b8d7e2f7f99b08dd2695a48fe89a2f4af652487 Mon Sep 17 00:00:00 2001 From: Kurt Zeilenga Date: Fri, 30 Jul 2010 13:11:53 -0700 Subject: [PATCH] Extend catalogs to support * restrictive catalogs * default items * empty items --- xep-0258.xml | 56 +++++++++++++++++++++++++++++++++------------------- 1 file changed, 36 insertions(+), 20 deletions(-) diff --git a/xep-0258.xml b/xep-0258.xml index 1eedf209..3fabd2fe 100644 --- a/xep-0258.xml +++ b/xep-0258.xml @@ -38,9 +38,9 @@ 0.6 - 2010-07-20 + 2010-07-30 kdz -

Minor editorial changes.

+

Extend catalog handling. Minor editorial changes.

0.5 @@ -221,7 +221,7 @@

A client can request a catalog for a particular JID by sending - an catalog discovery request to the client's server. Where the JID + a catalog discovery request to the client's server. Where the JID is hosted by some other server, the client's server is expected to produce a suitable catalog (or fail the request). The client's server may, as needed, query catalogs from other servers in order to @@ -234,6 +234,14 @@ JID.

It is RECOMMENDED the server publish catalogs of security label for use by clients.

+

If catalog is restrictive, as indicated by the restrictive attribute + with value of true, the client SHOULD use one of the labels + (or no label) offered by the catalog.

+

One and only one of the items may have a default attribute with + value of true. The client should default to this item in cases + where the user has not selected an item.

+

An item may have no label. Such an item offers a choice of + sending a stanza without a label.

Each catalog provided should only contain labels for which the client is allowed to use (based upon the user's authorization) in a particular context (such as in chatroom). A catalog may not be include the @@ -248,7 +256,7 @@ servers should advertise and clients should perform appropriate discovery lookups on a per service basis.

To indicate the support for label catalog discovery, a server - advertises the urn:xmpp:sec-label:catalog:1 feature. + advertises the urn:xmpp:sec-label:catalog:2 feature. The following pair of examples illustrates this feature discovery.

Each item in the catalog may contain a selector attribute. The value of this attribute represents the item's placement in a @@ -281,7 +289,7 @@ selector-value = ("|")* id='disco1'> ... - + ... @@ -291,15 +299,16 @@ selector-value = ("|")* - + ]]> - + desc='an example set of labels' + restrictive='false'> SECRET @@ -318,7 +327,7 @@ selector-value = ("|")* - + RESTRICTED - - - UNCLASSIFIED - - - + ]]> @@ -756,7 +757,7 @@ And by opposing end them? @@ -796,12 +797,25 @@ And by opposing end them? + + + Restrictive + + + + User input selector + + + Default Item + + + A Catalog of Labels @@ -809,12 +823,13 @@ And by opposing end them? - + + @@ -823,6 +838,7 @@ And by opposing end them? +