Infobits (XEP-0120)XEP-0120: Infobits <https://xmpp.org/extensions/xep-0120.html>. 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)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/>.. 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 RegistrarThe 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/>., 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 TermsDublin Core Metadata Initiative: DCMI Metadata Terms <http://dublincore.org/documents/dcmi-terms/>. 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)XEP-0118: User Tune <https://xmpp.org/extensions/xep-0118.html>..
YesHeart of the SunriseYessongs3P11M26S
]]>
The following is an example of metadata for a conference room.
jdev: Jabber DevelopmentDiscussion room for Jabber developersJabberXMPP
]]>
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)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/>..
The following is a submission to the infobits registry called for by XEP-0120.