[Council] a start on vCard++

Peter Saint-Andre stpeter at jabber.org
Fri Nov 12 09:20:34 CST 2004

Well, sure this is just the mapping of various profile elements to 
x:data. We'll need containers of some kind, which might just be pubsub 
collections so that one can have fine-grained control over who has 
access to what information.


On Nov 12, 2004, at 7:25 AM, Matthew A. Miller wrote:

> First, I offer my apologies; I won't be able to make it to today's 
> meeting.  What can I say other than, "things come up" (-:
> Second, this JEP is a good start...as a registry.  But I don't think 
> it covers the actual use-cases.  I don't think it's enough to say 
> "here's how you map <"legacy" infoset> to x:data".  It needs to go 
> further into why we find vCard less-than-adequate (e.g. not extensible 
> in and of itself, requires a custom renderer/processor), and how it 
> plays nice in places it is likely to be used (e.g. pubsub, disco, 
> etc.).
> However, since this is the last item on the agenda, I very much doubt 
> we'll really be discussing this today (-;  I can go into more detail 
> either here or at the meeting we actually go over it (-:
> Sorry!
> -  LW
> Peter Saint-Andre wrote:
>> Last night I wrote up the beginnings of a proto-JEP for vCard++ (it
>> still needs more work, but you get the basic idea):
>> http://www.jabber.org/~stpeter/jeps/profile.html
>> Let's discuss this in tomorrow's meeting if we get that far in the
>> agenda:
>> http://www.jabber.org/council/meetings/agendas/2004-11-12.html
>> Peter
> _______________________________________________
> Council mailing list
> Council at jabber.org
> http://mail.jabber.org/mailman/listinfo/council

More information about the Council mailing list