Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
more manifests
git-svn-id: svn://svn.xmpp.org:7938/xmpp/trunk@1551 4b5297f7-1745-476d-ba37-a9c6900126ab
  • Loading branch information
stpeter committed Jan 9, 2008
1 parent 4052326 commit c5e63ee
Show file tree
Hide file tree
Showing 22 changed files with 39 additions and 62 deletions.
4 changes: 2 additions & 2 deletions protocols/pubsub/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>pubsub</shortname>
<longname>Publish-Subscribe</longname>
<title>Publish-Subscribe</title>
<abstract>This specification defines an XMPP protocol extension for generic publish-subscribe functionality. The protocol enables XMPP entities to create nodes (topics) at a pubsub service and publish information at those nodes; an event notification (with or without payload) is then broadcasted to all entities that have subscribed to the node. Pubsub therefore adheres to the classic Observer design pattern and can serve as the foundation for a wide variety of applications, including news feeds, content syndication, rich presence, geolocation, workflow systems, network management systems, and any other application that requires event notifications.</abstract>
<specnum>XEP-0060</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0060.html</specurl>
<status>Draft</status>
Expand Down
11 changes: 0 additions & 11 deletions protocols/rc/manifest.xml

This file was deleted.

4 changes: 2 additions & 2 deletions protocols/rosterx/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>rosterx</shortname>
<longname>Roster Item Exchange</longname>
<title>Roster Item Exchange</title>
<abstract>This specification defines an XMPP protocol extension for exchanging contact list items, including the ability to suggest whether the item is to be added, deleted, or modified in the contact list of the recipient, as well as the suggested roster group for the item.</abstract>
<specnum>XEP-0144</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0144.html</specurl>
<status>Draft</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/rsm/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>rsm</shortname>
<longname>Result Set Management</longname>
<title>Result Set Management</title>
<abstract>This specification defines an XMPP protocol extension that enables an entity to page through and otherwise manage the receipt of large result sets. The protocol can be used in the context of any XMPP protocol that might send large result sets (such as service discovery, multi-user chat, and publish-subscribe). While the requesting entity in such an interaction can explicitly request the use of result set management, an indication that result set management is in use can also be proactively included by the responding entity when returning a limited result set in response to a query.</abstract>
<specnum>XEP-0059</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0059.html</specurl>
<status>Draft</status>
Expand Down
2 changes: 1 addition & 1 deletion protocols/shim/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<title>Stanza Headers and Internet Metadata</title>
<abstract>defines an XMPP protocol extension for establishing an out-of-band bytestream between any two XMPP users, mainly for the purpose of file transfer. The bytestream can be either direct (peer-to-peer) or mediated (though a special-purpose proxy server). The typical transport protocol used is TCP, although UDP may optionally be supported as well.</abstract>
<abstract>This specification defines an XMPP protocol extension for representing non-address-related headers in an XML format that is appropriate for use in XMPP. While the protocol provides a flexible mechanism for representing many kinds of standard Internet metadata, a registry of values is defined to structure the possible range of headers, and the inital registration includes headers from email, HTTP, MIME, and SIP.</abstract>
<specnum>XEP-0131</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0131.html</specurl>
<status>Draft</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/si/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>si</shortname>
<longname>Stream Initiation</longname>
<title>Stream Initiation</title>
<abstract>This specification defines an XMPP protocol extension for initiating a data stream between any two XMPP entities. The protocol includes the ability to include metadata about the stream and provides a pluggable framework so that various profiles of stream initiation can be defined for particular use cases (such as file transfer).</abstract>
<specnum>XEP-0095</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0095.html</specurl>
<status>Draft</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/sipub/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>sipub</shortname>
<longname>Publishing Stream Initiation Requests</longname>
<title>Publishing Stream Initiation Requests</title>
<abstract>This specification defines an XMPP protocol extension that enables an XMPP entity to advertise the fact that it is willing accept a particular Stream Initiation request. The protocol is used mainly to inform other entities that a particular file is available for transfer via the File Transfer protocol defined in XEP-0096.</abstract>
<specnum>XEP-0137</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0137.html</specurl>
<status>Draft</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/soap/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>soap</shortname>
<longname>SOAP Over XMPP</longname>
<title>SOAP Over XMPP</title>
<abstract>This specification defines methods for transporting SOAP messages over XMPP. Although the protocol supports only the request-response message exchange pattern, the protocol is formally defined as a SOAP Protocol Binding in accordance with version 1.2 of the W3C SOAP specification. In addition, a WSDL definition is defined for the purpose of advertising the availability of this protocol binding.</abstract>
<specnum>XEP-0072</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0072.html</specurl>
<status>Draft</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/streams/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>streams</shortname>
<longname>XML Streams</longname>
<title>XML Streams</title>
<abstract>This specification defines the core syntax of XML streams, which provide the wrapper for all XMPP communications.</abstract>
<specnum>RFC 3920</specnum>
<specurl>http://www.ietf.org/rfc/rfc3920.txt</specurl>
<status>Proposed</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/tune/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>tune</shortname>
<longname>User Tune</longname>
<title>User Tune</title>
<abstract>This specification defines a payload format for communicating information about music to which a user is listening, including the title, track number, collection, performer, composer, and length. The payload format is typically transported using the personal eventing profile of XMPP publish-subscribe as specified in XEP-0163.</abstract>
<specnum>XEP-0118</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0118.html</specurl>
<status>Draft</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:ietf:params:xml:ns:xmpp-bind/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:ietf:params:xml:ns:xmpp-bind</shortname>
<longname>Resource Binding</longname>
<title>Resource Binding</title>
<abstract>This specification defines the method by which a connected client can negotiate or specify a resource identifier for use by an XMPP server in routing XML stanzas to the client. The protocol includes a mechanism by which the client can request a random resource identifier from the server, and also enables a client to optionally bind multiple resources to one stream if needed.</abstract>
<specnum>RFC 3920</specnum>
<specurl>http://www.ietf.org/rfc/rfc3920.txt</specurl>
<status>Proposed</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:ietf:params:xml:ns:xmpp-e2e/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:ietf:params:xml:ns:xmpp-e2e</shortname>
<longname>S/MIME Encryption</longname>
<title>S/MIME Encryption</title>
<abstract>This specification defines an XMPP protocol extension that enables an XMPP client to sign, encrypt, or encrypt-and-sign the contents of any given XML stanza using the secure MIME (S/MIME) technology defined by the IETF, typically with client-side X.509 certificates. For the sake of interoperability, the protocol encodes information in the CPIM message format before signing or encryption.</abstract>
<specnum>RFC 3923</specnum>
<specurl>http://www.ietf.org/rfc/rfc3923.txt</specurl>
<status>Proposed</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:ietf:params:xml:ns:xmpp-sasl/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:ietf:params:xml:ns:xmpp-sasl</shortname>
<longname>Simple Authentication and Security Layer</longname>
<title>Simple Authentication and Security Layer</title>
<abstract>This specification defines the core authentication method for XMPP: an application profile of the Simple Authentication and Security Layer (SASL) protocol that enables a client to authenticate with a server or for one server to authenticate with a peer server. By its nature as a SASL profile, XMPP authentication enables a server to offer a wide range of SASL mechanisms, including encrypted passwords, mutual authentication using certificates or other means, and anonymous user sessions.</abstract>
<specnum>RFC 3920</specnum>
<specurl>http://www.ietf.org/rfc/rfc3920.txt</specurl>
<status>Proposed</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:ietf:params:xml:ns:xmpp-session/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:ietf:params:xml:ns:xmpp-session</shortname>
<longname>Presence and IM Session Establishment</longname>
<title>Presence and IM Session Establishment</title>
<abstract>This specification defines a method by which a client can formally request establishment of a presence and instant messaging session.</abstract>
<specnum>RFC 3921</specnum>
<specurl>http://www.ietf.org/rfc/rfc3921.txt</specurl>
<status>Proposed</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:ietf:params:xml:ns:xmpp-stanzas/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:ietf:params:xml:ns:xmpp-stanzas</shortname>
<longname>Stanza Errors</longname>
<title>Stanza Errors</title>
<abstract>This specification defines the syntax and semantics of XMPP errors related to XML stanzas, as well as a comprehensive list of error conditions.</abstract>
<specnum>RFC 3920</specnum>
<specurl>http://www.ietf.org/rfc/rfc3920.txt</specurl>
<status>Proposed</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:ietf:params:xml:ns:xmpp-streams/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:ietf:params:xml:ns:xmpp-streams</shortname>
<longname>Stream Errors</longname>
<title>Stream Errors</title>
<abstract>This specification defines the syntax and semantics of XMPP errors related to XML streams, as well as a comprehensive list of error conditions.</abstract>
<specnum>RFC 3920</specnum>
<specurl>http://www.ietf.org/rfc/rfc3920.txt</specurl>
<status>Proposed</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:ietf:params:xml:ns:xmpp-tls/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:ietf:params:xml:ns:xmpp-tls</shortname>
<longname>Transport Layer Security</longname>
<title>Transport Layer Security</title>
<abstract>This specification defines the core channel encryption method for XMPP: an application profile of Transport Layer Security (TLS) that enables a client to encrypt its XML streams with a server or for one server to encrypt its XML streams with a peer server. By its nature as a TLS profile, XMPP channel encryption also includes the ability to compress XML streams.</abstract>
<specnum>RFC 3920</specnum>
<specurl>http://www.ietf.org/rfc/rfc3920.txt</specurl>
<status>Proposed</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:xmpp:avatar/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:xmpp:avatar</shortname>
<longname>User Avatar</longname>
<title>User Avatar</title>
<abstract>This document defines an XMPP protocol extension for exchanging user avatars, which are small images or icons associated with human users. The protocol specifies payload formats for both avatar metadata and the image data itself. The payload formats are typically transported using the personal eventing profile of XMPP publish-subscribe as specified in XEP-0163.</abstract>
<specnum>XEP-0084</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0084.html</specurl>
<status>Draft</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:xmpp:delay/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:xmpp:delay</shortname>
<longname>Delayed Delivery</longname>
<title>Delayed Delivery</title>
<abstract>This specification defines an XMPP protocol extension for communicating the fact that an XML stanza has been delivered with a delay, for example because a message has been stored on a server while the intended recipient was offline or because a message is contained in the history of a multi-user chat room.</abstract>
<specnum>XEP-0203</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0203.html</specurl>
<status>Draft</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:xmpp:ping/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:xmpp:ping</shortname>
<longname>XMPP Ping</longname>
<title>XMPP Ping</title>
<abstract>This specification defines an XMPP protocol extension for sending application-level pings over XML streams. Such pings can be sent from a client to a server, from one server to another, or end-to-end.</abstract>
<specnum>XEP-0199</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0199.html</specurl>
<status>Draft</status>
Expand Down
4 changes: 2 additions & 2 deletions protocols/urn:xmpp:receipts/manifest.xml
@@ -1,6 +1,6 @@
<manifest>
<shortname>urn:xmpp:receipts</shortname>
<longname>Message Receipts</longname>
<title>Message Receipts</title>
<abstract>This specification defines an XMPP protocol extension for message receipts, whereby the sender of a message can request notification that it has been received by the intended recipient.</abstrace>
<specnum>XEP-0184</specnum>
<specurl>http://www.xmpp.org/extensions/xep-0184.html</specurl>
<status>Draft</status>
Expand Down
12 changes: 0 additions & 12 deletions protocols/waitinglist/manifest.xml

This file was deleted.

0 comments on commit c5e63ee

Please sign in to comment.