Re: [VCARDDAV] Signed vCards

Michael Angstadt <mike.angstadt@gmail.com> Sat, 24 August 2013 21:25 UTC

Return-Path: <mike.angstadt@gmail.com>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6319B11E818C for <vcarddav@ietfa.amsl.com>; Sat, 24 Aug 2013 14:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-NBZSt2slh3 for <vcarddav@ietfa.amsl.com>; Sat, 24 Aug 2013 14:25:49 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5398111E8189 for <vcarddav@ietf.org>; Sat, 24 Aug 2013 14:25:49 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so1985270pab.13 for <vcarddav@ietf.org>; Sat, 24 Aug 2013 14:25:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4O8w1r8zf7o67kQCgnBYbW5tmGbvUPMEjYWRgD8/bgo=; b=LMpoIMnebYMJsepAEDUcqYBxDID6tn4V/JSri2KVPJ+Gx8wwc/jHdLqdixYKfRkyzm MSyxj33fiJP7cZKFXq4pmEGFJf1Vtr05G0YIxvFazAQXNVoQQYHgIi6fc5zNC8VzWq5H iFyqISiBwN5bv9RA6/sGMJMyoM47Ej6+tRNnOxkE+UdoP9ZTCH/dXWz/AmBdsLInprYa mjSHe3FSr6C//WC4zTcd8paR9Osfagt4a99GI31BrKwnUgneTLUtVA4MqIoDFD8vDMS7 DPQ5LiqH2B5wCj3H+UwvghulTxwjLodK2kZQDw26WwbaYIvb/VY+drmJKCrisL9jvlHg G6bg==
MIME-Version: 1.0
X-Received: by 10.66.171.204 with SMTP id aw12mr6087590pac.7.1377379547674; Sat, 24 Aug 2013 14:25:47 -0700 (PDT)
Received: by 10.68.240.5 with HTTP; Sat, 24 Aug 2013 14:25:47 -0700 (PDT)
In-Reply-To: <CAB5WduAMy+UTrhKT6+dBh86iSCgcOtBEmkYctCUOzCOwxEo13w@mail.gmail.com>
References: <CAB5WduA09GVZ7j2q4e9aM-CYBj27_deKT=VHhVL0+gzG1yRq0A@mail.gmail.com> <CAD6ztsqqQwbN_-yv9+-tHuh8X1MfBRKEqF6ugH=0avHTuKxzWA@mail.gmail.com> <CAB5WduCO7mNPAqgqYWXmceog3wVNox5reUAjsCQRUXRQB0Wftw@mail.gmail.com> <51D18BC4.5030300@cisco.com> <CAB5WduAJSiqEjsw+DUo4Emy-Tw30nTw1WA2MshxJAfHN1sh0WA@mail.gmail.com> <51D1A52C.6000806@viagenie.ca> <CAB5WduDEe+tC21L6AbW0HRzTf5Z6L0oCA+M4X8_p1ERK0rFPtA@mail.gmail.com> <51D570F4.1020204@cisco.com> <CAB5WduC9OQDknwZj5PHQ0t8Y4V1vtpafeJuZXsnhrWKSmDfwFQ@mail.gmail.com> <CAB5WduC-m-TH9a1WrFY6QX8cQ2bJ8EgOD8+swEwpVxM7my42UA@mail.gmail.com> <CAB5WduBgpkQO+-4iNDspxR7X7JKeFU3UfjfiPd7qWWr7QRY3ew@mail.gmail.com> <CAB5WduCG356V5bHH8-7PYUtF3VqW5VRM-e=N0h7rbAJN51sSuA@mail.gmail.com> <51E42D85.4060806@viagenie.ca> <CAB5WduBJEXSsV5T-1MA+05wkQ6CZs8PySwUaQaAHew0E7dErbQ@mail.gmail.com> <CAB5WduBHej1O95X5UrFMkVJ1CQRdLzLOUjCF1AT6uz+-DTN4Ww@mail.gmail.com> <CAB5WduDQ6mHgSoWpX3JghF3CAMn8F0hV+y4zSTWc+Gi8EtY8UA@mail.gmail.com> <CAJNb_g1A64NWkpBqZsKsoLShB41Gqq3q21QnvDEdhENUYSi3XA@mail.gmail.com> <CAB5WduB4NMfLi_iYaTzivHWnV98rQbHMVWU4PEs6uO03uhJucA@mail.gmail.com> <CAB5WduAMy+UTrhKT6+dBh86iSCgcOtBEmkYctCUOzCOwxEo13w@mail.gmail.com>
Date: Sat, 24 Aug 2013 17:25:47 -0400
Message-ID: <CAJNb_g3trtyUjWikmTVBPoeVwzexL-DLx4=kfaWczuv6zGA-Lw@mail.gmail.com>
From: Michael Angstadt <mike.angstadt@gmail.com>
To: DataPacRat <datapacrat@gmail.com>
Content-Type: multipart/alternative; boundary="047d7bd6aceaa9012404e4b82aa4"
Cc: "vcarddav@ietf.org" <vcarddav@ietf.org>
Subject: Re: [VCARDDAV] Signed vCards
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Aug 2013 21:25:50 -0000

Perhaps a whole new property could be created that's similar in nature to
the IMPP property.  IMPP allows for an instant messenger handle to be
specified in the form of a URI.  No individual IM protocols are mentioned
in the specs, so it is open-ended as to what its value can be.  For
example, the following defines an AOL Instant Messenger handle:

IMPP:aim:goim?screenname=JohnDoe

The SOCIALMEDIA property could be similarly open-ended.  Its TYPE parameter
could contain the categories that the particular property value adheres to.
 The default data type for the property would be a URI, but TEXT could also
be used specifying things like Twitter handles and Facebook names (shown
below).

SOCIALMEDIA;TYPE="homepage":http://www.datapacrat.com/
SOCIALMEDIA;TYPE="blog":http://blog.datapacrat.com/
SOCIALMEDIA;TYPE="profile":http://blog.datapacrat.com/about/
SOCIALMEDIA;TYPE="twitter,blog,im";VALUE=text:@DataPacRat
SOCIALMEDIA;TYPE="facebook,profile,blog,im";PREF=1;VALUE=text:DataPacRat
SOCIALMEDIA;TYPE="facebook,profile,blog,im";PREF=2:
http://www.facebook.com/profile.php?id=650281140

Just throwing ideas out there.


On Sat, Aug 24, 2013 at 3:27 PM, DataPacRat <datapacrat@gmail.com> wrote:

> On Wed, Aug 21, 2013 at 1:42 PM, DataPacRat <datapacrat@gmail.com> wrote:
> > On Wed, Aug 21, 2013 at 9:12 AM, Michael Angstadt
> > <mike.angstadt@gmail.com> wrote:
>
> > Perhaps in addition to allowing the URL property to accept TYPE
> > parameters, a new parameter could be defined, such as SOCIALMEDIA,
> > which allows for a relatively freeform text string as its value, to do
> > the job. (I'm picking that suggested name to ease the transition from
> > the current practice of using an X-SOCIALMEDIA property.)
>
> If no more feedback is forthcoming, then I'll go with the SOCIALMEDIA
> parameter as a comma-separated list of values, which aren't limited to
> a particular list, but can include "blog", "profile", "im", the names
> of particular services, and so on.
>
>
> Assuming that that's settled, I expect the next step will be for me to
> put together a first draft of something to submit as an Internet
> Draft. I'll start working on that next week. Once I have it fully
> written out, should I post it here for further feedback, or just go
> straight to the submission page at tools.ietf.org?
>
>
>
> Thank you for your time,
> --
> DataPacRat
> "Then again, I could be wrong."
>