From 27e4841055d60caf58028e8016dadb7777c0f533 Mon Sep 17 00:00:00 2001 From: Tobias Markmann Date: Sun, 5 Apr 2009 10:56:22 +0000 Subject: [PATCH] Changing glossary of the pubsub XEP from table to definition list. git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2981 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0060.xml | 50 +++++++++++++++++++++++++------------------------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/xep-0060.xml b/xep-0060.xml index 41c9d448..8eeaecc6 100644 --- a/xep-0060.xml +++ b/xep-0060.xml @@ -418,31 +418,31 @@ And by opposing end them?

The following terms are used throughout this document to refer to elements, objects, or actions that occur in the context of a pubsub service. (Note: Some of these terms are specified in greater detail within the body of this document.)

- - - - - - - - - - - - - - - - - - - - - - - - -
Authorize Access ModelA node access model under which an entity can subscribe only through having a subscription request approved by a node owner (subscription requests are accepted but only provisionally) and only subscribers may retrieve items.
Address(1) A JID as defined in &xmppcore;, or (2) the combination of a JID and a &xep0030; node.
Collection NodeA type of node that contains nodes and/or other collections but no published items. Collections make it possible to represent more sophisticated relationships among nodes. Collection nodes are defined in &xep0248;.
EntityA JID-addressable Jabber entity (client, service, application, etc.).
EventA change in the state of a node.
Instant NodeA node whose NodeID is automatically generated by a pubsub service.
ItemAn XML fragment which is published to a node, thereby generating an event.
ItemIDA unique identifier for an item in the context of a specific node.
Leaf NodeA type of node that contains published items only. It is NOT a container for other nodes.
NodeA virtual location to which information can be published and from which event notifications and/or payloads can be received (in other pubsub systems, this may be labelled a "topic").
NodeIDThe unique identifier for a node within the context of a pubsub service. The NodeID is either supplied by the node creator or generated by the pubsub service (if the node creator requests an Instant Node). The NodeID MAY have semantic meaning, but such meaning is OPTIONAL.
NotificationA message sent to a subscriber informing them of an event.
OutcastAn entity that is disallowed from subscribing or publishing to a node.
OwnerThe manager of a node, of which there may be more than one; often but not necessarily the node creator.
PayloadThe full data associated with an event rather than just the event notification itself.
Open Access ModelA node access model under which any entity may subscribe and retrieve items without approval.
Personal EventingA simplified subset of Publish-Subscribe for use in the context of instant messaging and presence applications, whereby each IM user's JID is a virtual pubsub service; for details, see &xep0163;.
Presence Access ModelA node access model under which any entity that is subscribed to the owner's presence with a subscription of type "from" or "both" (see &rfc3921;) may subscribe to the node and retrieve items from the node; this access model applies mainly to instant messaging systems.
PublisherAn entity that is allowed to publish items to a node.
Pubsub ServiceAn XMPP server or component that adheres to the protocol defined herein.
Roster Access ModelA node access model under which any entity that is subscribed to the owner's presence and in the specified roster group(s) may subscribe to the node and retrieve items from the node; this access model applies mainly to instant messaging systems.
SubscriberAn entity that is subscribed to a node.
Whitelist Access ModelA node access model under which an entity may subscribe and retrieve items only if explicitly allowed to do so by the node owner (subscription requests from unauthorized entities are rejected).
+
+
Authorize Access Model
A node access model under which an entity can subscribe only through having a subscription request approved by a node owner (subscription requests are accepted but only provisionally) and only subscribers may retrieve items.
 +
Address
(1) A JID as defined in &xmppcore;, or (2) the combination of a JID and a &xep0030; node.
 +
Collection Node
A type of node that contains nodes and/or other collections but no published items. Collections make it possible to represent more sophisticated relationships among nodes. Collection nodes are defined in &xep0248;.
 +
Entity
A JID-addressable Jabber entity (client, service, application, etc.).
 +
Event
A change in the state of a node.
 +
Instant Node
A node whose NodeID is automatically generated by a pubsub service.
 +
Item
An XML fragment which is published to a node, thereby generating an event.
 +
ItemID
A unique identifier for an item in the context of a specific node.
 +
Leaf Node
A type of node that contains published items only. It is NOT a container for other nodes.
 +
Node
A virtual location to which information can be published and from which event notifications and/or payloads can be received (in other pubsub systems, this may be labelled a "topic").
 +
NodeID
The unique identifier for a node within the context of a pubsub service. The NodeID is either supplied by the node creator or generated by the pubsub service (if the node creator requests an Instant Node). The NodeID MAY have semantic meaning, but such meaning is OPTIONAL.
 +
Notification
A message sent to a subscriber informing them of an event.
 +
Outcast
An entity that is disallowed from subscribing or publishing to a node.
 +
Owner
The manager of a node, of which there may be more than one; often but not necessarily the node creator.
 +
Payload
The full data associated with an event rather than just the event notification itself.
 +
Open Access Model
A node access model under which any entity may subscribe and retrieve items without approval.
 +
Personal Eventing
A simplified subset of Publish-Subscribe for use in the context of instant messaging and presence applications, whereby each IM user's JID is a virtual pubsub service; for details, see &xep0163;.
 +
Presence Access Model
A node access model under which any entity that is subscribed to the owner's presence with a subscription of type "from" or "both" (see &rfc3921;) may subscribe to the node and retrieve items from the node; this access model applies mainly to instant messaging systems.
 +
Publisher
An entity that is allowed to publish items to a node.
 +
Pubsub Service
An XMPP server or component that adheres to the protocol defined herein.
 +
Roster Access Model
A node access model under which any entity that is subscribed to the owner's presence and in the specified roster group(s) may subscribe to the node and retrieve items from the node; this access model applies mainly to instant messaging systems.
 +
Subscriber
An entity that is subscribed to a node.
 +
Whitelist Access Model
A node access model under which an entity may subscribe and retrieve items only if explicitly allowed to do so by the node owner (subscription requests from unauthorized entities are rejected).
 +