[Vobject] Mac OS X AddressBook and vobject

[Lars Immisch]

Hi Jeffrey,

> Thanks for the patch, it looks good.  I haven't done much with vCards
> yet, I'm looking forward to lots of bugs filed relating to vCards, bugs
> with patches attached are even better!
> 
> Do people think it's worth storing and serializing group information
> when parsing vCards?  RFC 2425 says grouping has presentation
> implications, but no semantic meaning.
> 
> I think the presence of a group prefix should probably be stored and
> validation should fail for iCalendar streams which are successfully
> parsed but contain groups.
> 
> Thoughts?

First off, my patch was just a rude way to get the data parsed; in the 
end the group information should be visible in the Contents. I'll have a 
look at it tonight. So yes, group information should probably stored.

Having validation fail is maybe a bit harsh. The data isn't really 
invalid, just cluttered with display hints that most people won't need 
or want.

In a nutshell: I think it's important that data from Address Book can be 
parsed. Whoever wishes to retain the group information should be able 
to, but it should also be easy to sanitize the data.

> Also, I've been planning a pretty significant change to vobject
> semantics in the next week or so.  Most properties only occur once, so
> it's really annoying to always have to add a [0] to access one property.
>  I'm considering changing the ContentLine __getattr__ and __setattr__ to
> treat component.foo as a reference to the first foo property in
> component, and component.foo_list as the full list of foo properties.
> 
> Thoughts, part two?

Sounds good to me.

I'll have a look at the test cases and add one for Address Book data. 
I'll send a patch.

- Lars