[VCARDDAV] portable contacts
"Joseph Smarr" <jsmarr@gmail.com> Wed, 03 December 2008 01:47 UTC
Return-Path: <vcarddav-bounces@ietf.org>
X-Original-To: vcarddav-archive@optimus.ietf.org
Delivered-To: ietfarch-vcarddav-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6ACBC3A696F; Tue, 2 Dec 2008 17:47:08 -0800 (PST)
X-Original-To: vcarddav@core3.amsl.com
Delivered-To: vcarddav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91D383A685E for <vcarddav@core3.amsl.com>; Tue, 2 Dec 2008 17:37:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NzNanR8H1SWG for <vcarddav@core3.amsl.com>; Tue, 2 Dec 2008 17:37:01 -0800 (PST)
Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.191]) by core3.amsl.com (Postfix) with ESMTP id 770EE3A6A91 for <vcarddav@ietf.org>; Tue, 2 Dec 2008 17:36:34 -0800 (PST)
Received: by rn-out-0910.google.com with SMTP id j77so2768098rne.18 for <vcarddav@ietf.org>; Tue, 02 Dec 2008 17:36:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:mime-version:content-type; bh=VCc6E3RftkcSZ4nc9il0dlgEpCh9jKPVWa9N9CGEFP4=; b=Z4oiCBaiMIqFK/Xefjlm4ExoONCVgkONqATx1IZkCoRiCo/4GreUgxPDGTxzhAyt8d /ipmx/ALQ43VrAXwmCs24drBek2OEP6tCklPz+Cv5wDWwNwmcevJCLCtR1m6kcisLJFf lAvUoTqpFW6goV5am0GBap3kcCxe5OEt+sjLs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:mime-version:content-type; b=ulFdkxFVma1SFfv8X83qWNUBBkuR+PY4WiriM3LBFEryyX78Bd/asnawIjZIdZThSg 7iRR+PWLNyIvSiGvozwRjdM8Nz0oABymDMigr0YaMt8tF8SbXc3BsZ82aAZM+DW6IBCl /6YBXgEWomQtG219Md9u22JfPJ5fUCOENYNRs=
Received: by 10.100.43.10 with SMTP id q10mr7333447anq.1.1228268190123; Tue, 02 Dec 2008 17:36:30 -0800 (PST)
Received: by 10.100.109.4 with HTTP; Tue, 2 Dec 2008 17:36:29 -0800 (PST)
Message-ID: <c334d54e0812021736q4e8fa9cr1e1d1b698ff89d13@mail.gmail.com>
Date: Tue, 02 Dec 2008 17:36:29 -0800
From: Joseph Smarr <jsmarr@gmail.com>
To: vcarddav@ietf.org
MIME-Version: 1.0
Subject: [VCARDDAV] portable contacts
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: jsmarr@stanfordalumni.org
List-Id: "vCard and CardDAV Engineering List, potential WG" <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1177784961=="
Sender: vcarddav-bounces@ietf.org
Errors-To: vcarddav-bounces@ietf.org
Hi everyone, I wanted to make you aware of a community effort called Portable Contacts (http://portablecontacts.net) that shares many of the same goals as this group and has already had some promising initial success in gaining traction. Portable Contacts was created in the context of related grass-roots standards like OpenID and OAuth to provide a common, vendor-neutral schema, protocol, and workflow for letting users access their address book and friends-list info from any service, with a focus on ease of implementation and interoperability with existing standards. Our first draft spec was published in May 2008, and we've since gone through a few revisions, with active participation from individuals in the grass-roots community and from many companies including Google, Yahoo, Microsoft, MySpace, Plaxo, AOL, Sony Ericsson, and others. We've also worked with the OpenSocial community to wire-align the "accessing people data" part of the OpenSocial RESTful Protocol, so any OpenSocial container supporting those APIs is also by definition a Portable Contacts Provider (and several already are). More information about Portable Contacts (including the current rev of the draft spec) can be found at http://portablecontacts.net as well as on our mailing list http://groups.google.com/group/portablecontacts. I've also now published Portable Contacts as an IETF I-D ( http://www.ietf.org/internet-drafts/draft-smarr-vcarddav-portable-contacts-00.txt) to facilitate communication here. I recently came across the I-D to provide an XML schema for vCard as part of the vcarddav working group ( http://tools.ietf.org/id/draft-perreault-vcarddav-vcardxml-00.txt) and realized that the vcarddav community is also working on many of these same challenges. Since I think we both share the goal of creating a widespread standard for accessing contact information online, I'm sure we will both benefit from talking together and learning from the work we've each done so far. In fact, looking at the charter for vcarddav, the Portable Contacts community shares your goal of creating "An address book access protocol leveraging the vCard data format" and "An XML schema which is semantically identical to vCard in all ways and can be mechanically translated to and from vCard format without loss of data", and I think we've made great progress on both of those goals. We started with the vCard schema as the core of Portable Contacts, but expressed in JSON and XML bindings to take advantage of those developer-friendly and widely used formats, while preserving the semantic definitions of vCard. We've also added in additional contact fields to more fully represent the types of data typically describing people on modern social networking sites, thus spanning the gap between traditional address books and "social graphs". And we've specified an end-to-end workflow for discovery, authentication, and access of contact information (drawing on XRDS-Simple, HTTP Basic and/or OAuth, and a simple REST-like protocol, respectively), so that a would-be consumer of contact info can "walk up and use" any compliant provider their user wishes. I've chatted briefly so far with Marc Blanchet and Lisa Dusseault so far, but I'd love to hear from the rest of the group on how Portable Contacts does or doesn't meet the goals of this working group, and where you see opportunities for our two communities to work together, perhaps even combining some or all of our specs. I will also do my homework and learn more about the current state of CardDAV, and please send any questions/feedback you have on Portable Contacts to this list and/or the Portable Contacts mailing list, which any of you are free to join. Thanks! It's great to meet more people that are "fighting the good fight" for portable contact information! :) js -- Joseph Smarr Chief Platform Architect, Plaxo http://josephsmarr.com
_______________________________________________ VCARDDAV mailing list VCARDDAV@ietf.org https://www.ietf.org/mailman/listinfo/vcarddav
- [VCARDDAV] portable contacts Joseph Smarr
- Re: [VCARDDAV] portable contacts Helge Hess
- Re: [VCARDDAV] portable contacts Andy Mabbett
- Re: [VCARDDAV] portable contacts Joseph Smarr
- Re: [VCARDDAV] portable contacts Cyrus Daboo
- Re: [VCARDDAV] portable contacts Joseph Smarr
- Re: [VCARDDAV] portable contacts Cyrus Daboo
- Re: [VCARDDAV] portable contacts Dan Brickley
- Re: [VCARDDAV] portable contacts Joseph Smarr
- Re: [VCARDDAV] portable contacts Dan Brickley
- Re: [VCARDDAV] portable contacts Joseph Smarr
- Re: [VCARDDAV] portable contacts Joseph Smarr
- Re: [VCARDDAV] portable contacts Dan Brickley