One document matched: draft-ietf-vcarddav-kind-app-00.xml

<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc compact="yes"?>
<?rfc strict="yes"?>
<?rfc symrefs="yes"?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<rfc category="std" docName="draft-ietf-vcarddav-kind-app-00" ipr="trust200902">

  <front>
    <title abbrev="vCard KIND:application">vCard KIND:application</title>
    <author initials="P." surname="Saint-Andre" fullname="Peter Saint-Andre">
      <organization>Cisco</organization>
      <address>
        <postal>
          <street>1899 Wyknoop Street, Suite 600</street>
          <city>Denver</city>
          <region>CO</region>
          <code>80202</code>
          <country>USA</country>
        </postal>
        <phone>+1-303-308-3282</phone>
        <email>psaintan@cisco.com</email>
      </address>
    </author>
    <date year="2011" month="July" day="27"/>
    <keyword>vCard</keyword>
    <abstract>
      <t>This document defines a value of "application" for the vCard KIND property so that vCards can be used to represent software applications.</t>
    </abstract>
  </front>

  <middle>

    <section title="Introduction" anchor="intro">
      <t>Version 4 of the vCard specification <xref target='VCARD'/> defines a new "KIND" property to specify the type of entity that a vCard represents.  During its work on the base vCard4 specification, the VCARDDAV Working Group defined values of "individual", "organization", "group", and "location" for the KIND property.  The working group considered but then removed a value of "thing" to represent any type of physical entity, machine, software application, etc., with the expectation that such a value might be defined in a vCard extension.  This document does not define a generic "thing" value, but instead defines a more narrow "application" value so that vCards can be used to represent software applications.</t>
    </section>

    <section title="Meaning" anchor="meaning">
      <t>When the KIND property has a value of "application", the vCard represents a software application such as a server, an online service (e.g., a chatroom), or an automated software bot.  More formally, an "application" is functionally equivalent to the 'applicationProcess' object class used in the Lightweight Directory Access Protocol <xref target='RFC4519'/> as derived from the Open Systems Interconnection model <xref target='X.521'/> and <xref target='X.200'/>.  As one example of the "application" KIND, vCards are currently used in the Extensible Messaging and Presence Protocol <xref target='RFC6120'/> to represent instant messaging servers that are deployed on the network.</t>
      <t>The properties included in an application's vCard apply to one of the following:</t>
      <t>
        <list style='symbols'>
          <t>The application itself (e.g., the FN property might represent the friendly name of an application service, the URL property might represent a website that contains further information about the service, and the ADR, GEO, and TZ properties might represent the physical address, geographical location, and timezone of the machine where the service is hosted).<vspace blankLines='1'/></t>
          <t>An organization or person that makes the application available on the network (e.g., the LOGO property might represent the corporate logo of a service provider).<vspace blankLines='1'/></t>
          <t>A person or role that maintains the application (e.g., the TEL, EMAIL, and IMPP properties might represent ways to contact a server administrator).</t>
        </list>
      </t>
      <t>When a property represents some aspect of the application itself, it makes no sense to include the "work" and "home" values of the TYPE parameter since software applications do not have work places and personal lives (see the definition of the TYPE parameter in Section 5.6 of <xref target='VCARD'/>).  When a property represents information about an individual associated with the application (e.g., an individual service administrator as opposed to a generic service administrator role or an associated organization), inclusion of the "work" and "home" values can be appropriate.</t>
      <t>The following base properties make sense for vCards that represent software applications (this list is not exhaustive, and other properties might be applicable as well):</t>
      <t>
        <list style='symbols'>
          <t>ADR</t>
          <t>EMAIL</t>
          <t>FN</t>
          <t>GEO</t>
          <t>IMPP</t>
          <t>KEY</t>
          <t>KIND</t>
          <t>LANG</t>
          <t>LOGO</t>
          <t>NOTE</t>
          <t>ORG</t>
          <t>PHOTO</t>
          <t>REV</t>
          <t>SOURCE</t>
          <t>TEL</t>
          <t>TZ</t>
          <t>URL</t>
        </list>
      </t>
      <t>Although it might be desirable to define a more fine-grained taxonomy of applications (e.g., a KIND of "application" with a subtype of "server" or "IM server"), such a taxonomy is out of scope for this document.</t>
    </section>

    <section title="Example" anchor="example">
      <t>The following example of an XMPP server is borrowed from <xref target='XEP-0292'/> and uses the XML representation of vCard described in <xref target='VCARDXML'/>.</t>
      <figure>
        <artwork><![CDATA[
<vcard xmlns="urn:ietf:params:xml:ns:vcard-4.0"> 
  <fn><text>jabber.org IM service</text></fn>
  <url><uri>http://www.jabber.org/</uri></url>
  <lang>
    <parameters><pref>1</pref></parameters>
    <language-tag>en</language-tag>
  </lang>
  <email><text>xmpp@jabber.org</text></email>
  <impp><uri>xmpp:jabber.org</uri></impp>
  <logo><uri>http://www.jabber.org/images/logo.png</uri></logo>
  <geo><uri>geo:42.25,-91.05</uri></geo>
  <tz><text>America/Chicago</text></tz>
  <source><uri>xmpp:jabber.org?vcard</uri></source>
  <rev><timestamp>19990104T122100Z</timestamp></rev>
  <kind><text>application</text></kind>
</vcard>
        ]]></artwork>
      </figure>
    </section>

    <section title="IANA Considerations" anchor="iana">
      <t>The IANA is requested to add "application" to the registry of property values for vCard4.  In conformance with Section 10.2.6 of <xref target='VCARD'/>, the registration is as follows, where the reference is to RFC&rfc.number;.</t>
      <t>
        <list style='hanging'>
          <t hangText='Value:'>application</t>
          <t hangText='Purpose:'>The entity represented by the vCard is a software application (e.g., a server, an online service such as a chatroom, or an automated software bot).</t>
          <t hangText='Conformance:'>This value can be used with the "KIND" property.</t>
          <t hangText='Example:'>See Section 3 of RFC&rfc.number;.</t>
        </list>
      </t>
      <t>[[NOTE TO RFC EDITOR: Please change &rfc.number; to the number assigned to this specification, and remove this paragraph on publication.]]</t>
    </section>

    <section title="Security Considerations" anchor="security">
      <t>Use of vCards to represent software applications is not envisioned to introduce security considerations beyond those specified for vCards in general as described in <xref target='VCARD'/>.</t>
    </section>

    <section title="Acknowledgements" anchor="acks">
      <t>Thanks to Cyrus Daboo, Barry Leiba, Kepeng Li, and Simon Perreault for their feedback.</t>
    </section>

  </middle>

  <back>

    <references title="Normative References">

<reference anchor='VCARD'>
<front>
<title>vCard Format Specification</title>
<author initials='S' surname='Perreault' fullname='Simon Perreault'>
    <organization />
</author>
<date month='May' day='26' year='2011' />
<abstract><t>This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).</t></abstract>
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-vcarddav-vcardrev-22' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-vcarddav-vcardrev-22.txt' />
</reference>

    </references>

    <references title="Informative References">

<reference anchor='RFC4519'>
<front>
<title>Lightweight Directory Access Protocol (LDAP): Schema for User Applications</title>
<author initials='A.' surname='Sciberras' fullname='A. Sciberras'>
<organization /></author>
<date year='2006' month='June' />
<abstract>
<t>This document is an integral part of the Lightweight Directory Access Protocol (LDAP) technical specification.  It provides a technical specification of attribute types and object classes intended for use by LDAP directory clients for many directory services, such as White Pages.  These objects are widely used as a basis for the schema in many LDAP directories.  This document does not cover attributes used for the administration of directory servers, nor does it include directory objects defined for specific uses in other documents. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name='RFC' value='4519' />
<format type='TXT' octets='64996' target='http://www.rfc-editor.org/rfc/rfc4519.txt' />
</reference>

<reference anchor='RFC6120'>
<front>
<title>Extensible Messaging and Presence Protocol (XMPP): Core</title>
<author initials='P.' surname='Saint-Andre' fullname='P. Saint-Andre'>
<organization /></author>
<date year='2011' month='March' />
<abstract>
<t>The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities.  This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability ("presence"), and request-response interactions.  This document obsoletes RFC 3920. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name='RFC' value='6120' />
<format type='TXT' octets='451942' target='http://www.rfc-editor.org/rfc/rfc6120.txt' />
</reference>

<reference anchor='VCARDXML'>
<front>
<title>vCard XML Representation</title>
<author initials='S' surname='Perreault' fullname='Simon Perreault'>
    <organization />
</author>
<date month='May' day='26' year='2011' />
<abstract><t>This document defines the XML schema of the vCard data format.</t></abstract>
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-vcarddav-vcardxml-11' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-vcarddav-vcardxml-11.txt' />
</reference>

<reference anchor="X.200">
<front>
<title>Information Technology - Open Systems Interconnection - Basic Reference Model: The Basic Model</title>
<author>
<organization>International Telecommunications Union</organization>
</author>
<date month="February" year="2001" />
</front>
<seriesInfo name="ITU-T" value="Recommendation X.521" />
<seriesInfo name="ISO" value="Standard 9594-7" />
</reference>

<reference anchor="X.521">
<front>
<title>Information Technology - Open Systems Interconnection - The Directory: Selected Object Classes</title>
<author>
<organization>International Telecommunications Union</organization>
</author>
<date month="July" year="1994" />
</front>
<seriesInfo name="ITU-T" value="Recommendation X.200" />
<seriesInfo name="ISO" value="Standard 7498-1" />
</reference>

<reference anchor="XEP-0292">
  <front>
    <title>vCard4 over XMPP</title>
    <author initials="P." surname="Saint-Andre" fullname="Peter Saint-Andre">
      <organization/>
      <address>
        <email>stpeter@jabber.org</email>
      </address>
    </author>
    <author initials="S." surname="Mizzi" fullname="Samantha Mizzi">
      <organization/>
      <address>
        <email>samizzi@cisco.com</email>
      </address>
    </author>
    <date day="10" month="July" year="2011"/>
  </front>
  <seriesInfo name="XSF XEP" value="0292"/>
  <format type="HTML" target="http://xmpp.org/extensions/xep-0292.html"/>
</reference>

    </references>

  </back>

</rfc>