vCard RDF compromises

Everyone,

I've been busy with other areas of my current project, but this week I'm 
officially back to the vCard RDF part. I will be implementing the new 
vCard stuff literally within days, so I'd like to get resolution on some 
of the issues. I'd really like to share W3C work, so I'm prepared to 
make compromises (see archives for earlier discussions on these issues):

VCard:N

There are a few people absolutely loathe to have any processor-based 
value-switching, and I'm loathe to cram all the name information into 
one value. In the interest of getting this done, I offer the following 
compromise: N.familyName, N.givenName, N.honorificPrefix, and 
N.honorificSuffix are all single value properties, although you can have 
multiple of them. N.additionalNames takes a value of rdf:List.

VCard:Adr

Adr.streetAddress takes a single value, but Adr.extendedAddress takes a 
value of rdf:List.

Let me know as soon as possible what people thing about these 
suggestions. Since I'm partially caving here, I'd really like to switch 
to camelCase and get an updated version of the spec soon. Comments?

Best,

Garret

Received on Tuesday, 26 June 2007 21:38:57 UTC