Re: [VCARDDAV] Signed vCards

DataPacRat <datapacrat@gmail.com> Tue, 20 August 2013 20:37 UTC

Return-Path: <datapacrat@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 B9E9911E8283 for <vcarddav@ietfa.amsl.com>; Tue, 20 Aug 2013 13:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 x8Y7SnN0Wiuj for <vcarddav@ietfa.amsl.com>; Tue, 20 Aug 2013 13:37:58 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7E94911E8281 for <vcarddav@ietf.org>; Tue, 20 Aug 2013 13:37:58 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hi8so5351414wib.5 for <vcarddav@ietf.org>; Tue, 20 Aug 2013 13:37:56 -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=gwb8+3yAZOUzPUkbcBeHkSl8bVHa85T/6VYRWng2Xcs=; b=Bb9BJXzFfvm/u6kQYJ/eQ1VlmwsxwYcx+0zDAPAPGUUCjsQ2fGk1A7/qWt41TEinOE gPZCHiaXW3tmCtEEzIknhSOuOssFGlSiWdkkUo8HgFs6rHuv+SKAIro8qXNNZKlvPALV a3TT5YzrGLLUBNJ8RG3iJ4E1KdYctxHKeI0RRWXDPHjUkmSJQAIJ0TNhSexgLxasJqSO ZpSQ8pO+xbPjrz3WW8m2M/4tfd8j2RTmN8Xbk6tLlfXKFhqnhL7aLKq/OULm2YoLfNkl PhQ/G59+kYH2kTcen3BX1VMtc90bIhClrwgX3bBPmxwyfcXNepnfqnOu1hbFRSIE1UBE NwxA==
MIME-Version: 1.0
X-Received: by 10.180.183.137 with SMTP id em9mr13893810wic.29.1377031076380; Tue, 20 Aug 2013 13:37:56 -0700 (PDT)
Received: by 10.194.133.193 with HTTP; Tue, 20 Aug 2013 13:37:56 -0700 (PDT)
In-Reply-To: <CAB5WduBHej1O95X5UrFMkVJ1CQRdLzLOUjCF1AT6uz+-DTN4Ww@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>
Date: Tue, 20 Aug 2013 16:37:56 -0400
Message-ID: <CAB5WduDQ6mHgSoWpX3JghF3CAMn8F0hV+y4zSTWc+Gi8EtY8UA@mail.gmail.com>
From: DataPacRat <datapacrat@gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Content-Type: text/plain; charset="ISO-8859-1"
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: Tue, 20 Aug 2013 20:37:59 -0000
X-List-Received-Date: Tue, 20 Aug 2013 20:37:59 -0000

I know it's been a few weeks, but I'm still around, and working on an
upgrade to the vCard format in the time I have available for it.

I think I've figured out one last change worth discussing, before I
start putting everything together into a formal Internet Draft
submission: adjusting the URL property somewhat, to deal with multiple
URLs on different sites. (Or, put another way, to merge the existing
informal X-SOCIALPROFILE property into the URL property.)

An example: I am attached to the URLs of http://www.datapacrat.com/ ,
http://blog.datapacrat.com/ , http://blog.datapacrat.com/about/ ,
http://twitter.com/DataPacRat, and http://www.facebook.com/DataPacRat
, and www.facebook.com/profile.php?id=650281140 . To include them all
in a vCard, I might use:

URL:http://www.datapacrat.com/
URL:http://blog.datapacrat.com/
URL:http://blog.datapacrat.com/about/
URL:http://twitter.com/DataPacRat
URL:http://www.facebook.com/DataPacRat
URL:http://www.facebook.com/profile.php?id=650281140

Or, if I preferred them in a particular order, I might use:

URL;PREF=1:http://www.datapacrat.com/
URL;PREF=2:http://blog.datapacrat.com/
URL;PREF=3:http://blog.datapacrat.com/about/
URL;PREF=4:http://twitter.com/DataPacRat
URL;PREF=5:http://www.facebook.com/DataPacRat
URL;PREF=6:http://www.facebook.com/profile.php?id=650281140


While this gets the job done, it's not ideal, and I think there's a
fairly simple way to do better: allow the TYPE parameter to be used
for URL properties, the same way it can be for TEL. In RFC 6350,
section 6.4.1, some of the examples are:

     TEL;VALUE=uri;PREF=1;TYPE="voice,home":tel:+1-555-555-5555;ext=5555
     TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67

While "home" is explicitly described as one possibility for
type-param-tel , I would like TYPEs for URLs to be somewhat more
expandable, for future use as people keep coming up with creative
things to do online. For example:

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


It seems like there should be some discussion about which values such
a set of TYPEs should initially be seeded with - "home" and "work" are
obvious and already part of RFC 6350, but "blog", "profile", "im",
"store", and "homepage" are simply the most obvious ones to me. And
I've seen a number of vCards which already use Type parameters with
site-names such as Twitter in their X-SOCIALPROFILE properties.

And, of course, it's possible I've ended up looking at this from
entirely the wrong angle, in which case I would really want to figure
that out now, instead of after I've started writing everything up
formally.



Thank you for your time,
--
DataPacRat
"Then again, I could be wrong."