- From: Raj Singh <rsingh@opengeospatial.org>
- Date: Tue, 4 Oct 2011 11:51:09 -0400
- To: Dan Brickley <danbri@danbri.org>
- Cc: Alex Hill <ahill@gatech.edu>, roBman@mob-labs.com, "public-poiwg@w3.org" <public-poiwg@w3.org>
Just took a look at Portable Contacts. My initial feeling is "meh". Looks OK, but why why go a little simpler and lose flexibility when there are so many good vcard/icalendar libraries out there and there's a schema for it, making parsing pretty easy: http://caldav.calconnect.org/implementations/librariestools.html I'm convincing myself more and more that vcard is the way to go. --- Raj The OGC: Making location count... http://www.opengeospatial.org/contact On Oct 4, at 11:36 AM, Dan Brickley wrote: > On 4 October 2011 17:32, Alex Hill <ahill@gatech.edu> wrote: >> There appears to be an XML schema for card: >> http://tools.ietf.org/html/draft-ietf-vcarddav-vcardxml-11 >> On Oct 4, 2011, at 10:39 AM, Raj Singh wrote: >> >> Interesting question. I'd vote for vcard only. It's not the easiest thing to >> parse, but at least developers can focus on a single format, and I don't >> think there's any standard address format that's easy to parse. > > Also consider Portable Contacts > http://portablecontacts.net/draft-spec.html (maybe not caring about > the social network properties). It's based on vCard deployment > experience, and has bindings to JSON and XML... > > Dan
Received on Tuesday, 4 October 2011 15:51:41 UTC