Infobits (XEP-0120) [1] defines a protocol for capturing granular information (or "infobits") about users, servers, services, rooms, nodes, commands, files, and other phenomena on the Jabber/XMPP network; however, that document defines the protocol only, not the infobits themselves. This document specifies how to encapsulate one sort of metadata in infobits: the common metadata elements defined by the Dublin Core Metadata Initiative (DCMI) [2]. Note well that this document is decidedly not meant to provide an exhaustive catalog of possible infobits. Future registrations, whether in XMPP Extension Protocol specifications or direct submissions to the XMPP Registrar [3], will specify additional infobits.
The Dublin Core Metadata Initiative defines a number of common elements and element refinements that can be used to specify metadata about entities (especially but not exclusively publications). The semantics of any Dublin Core term can be represented as a Jabber infobit, where the infobit keyname consists of the term name (not label) prepended by a 'DC' prefix and a '.' separator character. Thus "DC.creator" is a valid infobit name and can be used to describe, for example, an IM user's relationship to the URI identifying the user's homepage or weblog. Infobit keynames beginning with the 'DC' prefix are reserved for DCMI Metadata Terms [4] only (the canonical list of these terms is available from the Dublin Core Metadata Initiative and is included here only for explanatory purposes).
The following example is borrowed from User Tune (XEP-0118) [5].
<iq type='set'
from='stpeter@jabber.org/work'
to='pubsub.jabber.org'
id='tunes123'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<publish node='generic/tunes/stpeter@jabber.org'>
<item id='current'>
<tune xmlns='http://jabber.org/protocol/tunes'>
<info xmlns='http://jabber.org/protocol/infobits'>
<bit key='DC.creator'>Yes</bit>
<bit key='DC.title'>Heart of the Sunrise</bit>
<bit key='DC.source'>Yessongs</bit>
<bit key='DC.identifier'>3</bit>
<bit key='DC.extent'>P11M26S</bit>
</info>
</tune>
</item>
</publish>
</pubsub>
</iq>
The following is an example of metadata for a conference room.
<iq type='result'
from='jdev@conference.jabber.org'
id='mdata'>
<query xmlns='http://jabber.org/protocol/disco#info'
node='metadata'>
<info xmlns='http://jabber.org/protocol/infobits'>
<bit key='DC.title'>jdev: Jabber Development</bit>
<bit key='DC.description'>Discussion room for Jabber developers</bit>
<bit key='DC.subject'>Jabber</bit>
<bit key='DC.subject'>XMPP</bit>
</info>
</query>
</iq>
This document introduces no security considerations above and beyond those already defined in XEP-0120.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [6].
The following is a submission to the infobits registry called for by XEP-0120.
<bit key='DC.title'/> <bit key='DC.creator'/> <bit key='DC.subject'/> <bit key='DC.description'/> <bit key='DC.publisher'/> <bit key='DC.contributor'/> <bit key='DC.date'/> <bit key='DC.type'/> <bit key='DC.format'/> <bit key='DC.identifier'/> <bit key='DC.source'/> <bit key='DC.language'/> <bit key='DC.relation'/> <bit key='DC.coverage'/> <bit key='DC.rights'/> <bit key='DC.audience'/> <bit key='DC.alternative'/> <bit key='DC.tableOfContent'/> <bit key='DC.abstract'/> <bit key='DC.created'/> <bit key='DC.valid'/> <bit key='DC.available'/> <bit key='DC.issued'/> <bit key='DC.modified'/> <bit key='DC.extent'/> <bit key='DC.medium'/> <bit key='DC.isVersionOf'/> <bit key='DC.hasVersion'/> <bit key='DC.isReplacedBy'/> <bit key='DC.replaces'/> <bit key='DC.isRequiredBy'/> <bit key='DC.requires'/> <bit key='DC.isPartOf'/> <bit key='DC.hasPart'/> <bit key='DC.isReferencedBy'/> <bit key='DC.references'/> <bit key='DC.isFormatOf'/> <bit key='DC.hasFormat'/> <bit key='DC.conformsTo'/> <bit key='DC.spatial'/> <bit key='DC.temporal'/> <bit key='DC.mediator'/> <bit key='DC.dateAccepted'/> <bit key='DC.dateCopyrighted'/> <bit key='DC.dateSubmitted'/> <bit key='DC.educationLevel'/> <bit key='DC.accessRights'/> <bit key='DC.bibliographicCitation'/> <bit key='DC.LCSH'/> <bit key='DC.MESH'/> <bit key='DC.DDC'/> <bit key='DC.LCC'/> <bit key='DC.UDC'/> <bit key='DC.DCMIType'/> <bit key='DC.IMT'/> <bit key='DC.ISO639-2'/> <bit key='DC.RFC1766'/> <bit key='DC.URI'/> <bit key='DC.Point'/> <bit key='DC.ISO3166'/> <bit key='DC.Box'/> <bit key='DC.TGN'/> <bit key='DC.Period'/> <bit key='DC.W3CDTF'/> <bit key='DC.RFC3066'/> <bit key='DC.Collection'/> <bit key='DC.Dataset'/> <bit key='DC.Event'/> <bit key='DC.Image'/> <bit key='DC.InteractiveResource'/> <bit key='DC.Service'/> <bit key='DC.Software'/> <bit key='DC.Sound'/> <bit key='DC.Text'/> <bit key='DC.PhysicalObject'/> <bit key='DC.StillImage'/> <bit key='DC.MovingImage'/>
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF).
Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.
This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).
The HTML representation (you are looking at) is maintained by the XSF. It is based on the YAML CSS Framework, which is licensed under the terms of the CC-BY-SA 2.0 license.
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <editor@xmpp.org>.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
1. XEP-0120: Infobits <https://xmpp.org/extensions/xep-0120.html>.
2. The Dublin Core Metadata Initiative (DCMI) is an organization dedicated to promoting the widespread adoption of interoperable metadata standards. For further information, see <http://www.dublincore.org/>.
3. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>.
4. Dublin Core Metadata Initiative: DCMI Metadata Terms <http://dublincore.org/documents/dcmi-terms/>.
5. XEP-0118: User Tune <https://xmpp.org/extensions/xep-0118.html>.
6. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/
END