In article <[EMAIL PROTECTED]>, "Richard Dobson" <[EMAIL PROTECTED]> wrote:
> >> For this vcard alternative stuff why dont we just use a namespaced x:data > >> payload, with sets of the standard fields registered with the jabber > >> registrar e.g. > > > > I started working on something similar late last year: > > > > http://www.saint-andre.com/jabber/jeps/profile.html > > Cool looks good. Great, I'll work to update it so that it can be submitted to the JEP Editor. ;-) > > Another approach would be to RDF, which Dominik Tomaszuk has been > > working on (he can provide a link). > > Sounds interesting but RDF just seems a bit like overkill and potensially > overly complex to me, whereas x:data just seems nice and simple and as far I > as can make out should be plenty extensible enough to last. I tend to agree. Of course, using x:data as the wire representation over XMPP would not prevent an implementation from using RDF as the backend data format. > > A third approach would be to pursue standardization of a next-generation > > format for personal profile data within the IETF (most likely as XML but > > perhaps as RDF) -- I know some IETF folks who are interested in doing > > just that, but such an effort might take longer. > > Yup certainly an option, but again would be afraid of it becoming far too > overly complex, again personally I think x:data would be fine as it would > work fine and is here now and works. Hmm, yes, I don't think I'd like to be the one writing that RFC. ;-) /psa _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
