You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

197 lines
7.1 KiB

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<title>Dublin Core Infobits Mapping</title>
<abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract>
<abstract>A mapping of Dublin Core metadata terms into the Jabber Infobits protocol.</abstract>
<remark>Confined proposal to Dublin Core only.</remark>
<remark>Added more vCard mappings; specified prefixes for some infobits; defined registry submission.</remark>
<remark>Modified Dublin Core references.</remark>
<remark>Updated to track changes in XEP-0120.</remark>
<remark>Added several new info keys; further defined Dublin Core metadata elements; added internationalization considerations.</remark>
<remark>Initial version.</remark>
<section1 topic='Introduction'>
<p>&xep0120; 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 &DUBLINCORE;. Note well that this document is decidedly <em>not</em> meant to provide an exhaustive catalog of possible infobits. Future registrations, whether in XMPP Extension Protocol specifications or direct submissions to the &REGISTRAR;, will specify additional infobits.</p>
<section1 topic='Dublin Core Metadata Terms'>
<p>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 &dcmiterms; only (the canonical list of these terms is available from the Dublin Core Metadata Initiative and is included here only for explanatory purposes).</p>
<section1 topic='Examples'>
<p>The following example is borrowed from &xep0118;.</p>
<example caption='User Publishes Tune Information'><![CDATA[
<iq type='set'
<pubsub xmlns=''>
<publish node='generic/tunes/'>
<item id='current'>
<tune xmlns=''>
<info xmlns=''>
<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>
<p>The following is an example of metadata for a conference room.</p>
<example caption='Metadata Result from a Conference Room'><![CDATA[
<iq type='result'
<query xmlns=''
<info xmlns=''>
<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>
<section1 topic='Security Considerations'>
<p>This document introduces no security considerations above and beyond those already defined in XEP-0120.</p>
<section1 topic='IANA Considerations'>
<p>This document requires no interaction with &IANA;.</p>
<section1 topic='XMPP Registrar Considerations'>
<p>The following is a submission to the infobits registry called for by XEP-0120.</p>
<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=''/>
<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'/>