XEP-0164: vCard Filtering

This document specifies a mechanism for requesting specific sections of a vCard.
Daniel Henninger
© 2005 – 2005 XMPP Standards Foundation. SEE LEGAL NOTICES.


WARNING: This document has been automatically Deferred after 12 months of inactivity in its previous Experimental state. Implementation of the protocol described herein is not recommended for production systems. However, exploratory implementations are encouraged to resume the standards process.
Standards Track
0.1 (2005-11-16)
Document Lifecycle
  1. Experimental
  2. Deferred
  3. Proposed
  4. Stable
  5. Final

1. Introduction

Because XML vCards (see vcard-temp (XEP-0054) [1]) are now actively used for storing avatars (see vCard-Based Avatars (XEP-0153) [2]), the ability to retrieve only portions of a vCard has become desirable. This protocol can eliminate unnecessary bandwidth usage when larger elements of a vCard are not needed.

2. Requirements

Any entity supporting this extension MUST be prepared to accept more fields than were requested, in case the target does not support this extension. A compliant target SHOULD exclude any fields listed in the filter element. In the event that the filter element does not exist or is empty, the target MUST return the entire vCard as it would without this extension.

3. Use Cases

3.1 Retrieving Another User's vCard Without The JABBERID Element

To illustrate the functionality of this protocol, we will first request a standard vCard. As shown in XEP-0054, a user may view another user's vCard by sending an IQ of type "get" to the other user's bare JID. A compliant server MUST return the vCard to the requestor and not forward the IQ to the requestee's connected resource.

Example 1. Requesting Another User's vCard
<iq to='jer@jabber.org'
  <vCard xmlns='vcard-temp'/>

The server should then return the other user's vCard to the requestor:

Example 2. Receiving Another User's vCard
<iq from='jer@jabber.org'
  <vCard xmlns='vcard-temp'>
    <FN>Jeremie Miller</FN>

A user may request that specific portions of another user's vCard be excluded by including the requested field(s) inside a filter element qualified by the 'vcard-temp-filter' namespace, inside the vCard element.

Example 3. Requesting Another User's vCard Without the JABBERID Element
<iq to='jer@jabber.org'
  <vCard xmlns='vcard-temp'>
    <filter xmlns='vcard-temp-filter'>

The server should then return all available fields from the other user's vCard except for those listed in the filter stanza:

Example 4. Receiving Fields From Another User's vCard
<iq from='jer@jabber.org'
  <vCard xmlns='vcard-temp'>

4. Security Considerations

This document introduces no new security concerns beyond those already involved in implementation and deployment of the 'vcard-temp' protocol.

5. IANA Considerations

This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [3].

6. XMPP Registrar Considerations

The XMPP Registrar [4] shall add 'vcard-temp-filter' to its registry of official namespaces.

7. XML Schema

The schema for the 'vcard-temp-filter' namespace re-uses the element names from the DTD described in XEP-0054.

<?xml version='1.0' encoding='UTF-8'?>


  <xs:element name='filter'>
        <xs:element name='VERSION' type='empty'/>
        <xs:element name='FN' type='empty'/>
        <xs:element name='N' type='empty'/>
        <xs:element name='NICKNAME' type='empty'/>
        <xs:element name='PHOTO' type='empty'/>
        <xs:element name='BDAY' type='empty'/>
        <xs:element name='ADR' type='empty'/>
        <xs:element name='LABEL' type='empty'/>
        <xs:element name='TEL' type='empty'/>
        <xs:element name='EMAIL' type='empty'/>
        <xs:element name='JABBERID' type='empty'/>
        <xs:element name='MAILER' type='empty'/>
        <xs:element name='TZ' type='empty'/>
        <xs:element name='GEO' type='empty'/>
        <xs:element name='TITLE' type='empty'/>
        <xs:element name='ROLE' type='empty'/>
        <xs:element name='LOGO' type='empty'/>
        <xs:element name='AGENT' type='empty'/>
        <xs:element name='ORG' type='empty'/>
        <xs:element name='CATEGORIES' type='empty'/>
        <xs:element name='NOTE' type='empty'/>
        <xs:element name='PRODID' type='empty'/>
        <xs:element name='REV' type='empty'/>
        <xs:element name='SORT-STRING' type='empty'/>
        <xs:element name='SOUND' type='empty'/>
        <xs:element name='UID' type='empty'/>
        <xs:element name='URL' type='empty'/>
        <xs:element name='CLASS' type='empty'/>
        <xs:element name='KEY' type='empty'/>
        <xs:element name='DESC' type='empty'/>

  <xs:simpleType name='empty'>
    <xs:restriction base='xs:string'>
      <xs:enumeration value=''/>



Appendix A: Document Information

XMPP Standards Foundation
Standards Track
Last Updated
Approving Body
XMPP Council
XMPP Core, XEP-0054
Superseded By
Short Name
Source Control

This document in other formats: XML  PDF

Appendix B: Author Information

Daniel Henninger


This XMPP Extension Protocol is copyright © 1999 – 2024 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.

Disclaimer of Warranty

## 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. ##

Limitation of Liability

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.

IPR Conformance

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).

Visual Presentation

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.

Appendix D: Relation to XMPP

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.

Appendix E: Discussion Venue

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 <https://xmpp.org/community/> for a complete list.

Errata can be sent to <editor@xmpp.org>.

Appendix F: Requirements Conformance

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".

Appendix G: Notes

1. XEP-0054: vcard-temp <https://xmpp.org/extensions/xep-0054.html>.

2. XEP-0153: vCard-Based Avatars <https://xmpp.org/extensions/xep-0153.html>.

3. 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/>.

4. 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/>.

Appendix H: Revision History

Note: Older versions of this specification might be available at https://xmpp.org/extensions/attic/

  1. Version 0.1 (2005-11-16)
    Initial version.
  2. Version 0.0.2 (2005-11-05)
    Switched to filter out, instead of filter in.
  3. Version 0.0.1 (2005-10-22)
    First draft.

Appendix I: Bib(La)TeX Entry

  title = {vCard Filtering},
  author = {Henninger, Daniel},
  type = {XEP},
  number = {0164},
  version = {0.1},
  institution = {XMPP Standards Foundation},
  url = {https://xmpp.org/extensions/xep-0164.html},
  date = {2005-10-22/2005-11-16},