-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/15/12 1:44 AM, Kevin Smith wrote: > > On Sat, Oct 13, 2012 at 5:37 PM, Andreas Kuckartz > <a.kucka...@ping.de> wrote: >> According to http://xmpp.org/about-xmpp/xsf/xmpp-council/ ralphm >> is currently a member of the XMPP Council. >> >> Can someone please let me know if he has a veto right there? > > Yes - the process is described in > http://xmpp.org/extensions/xep-0001.html#approval; any Council > member can prevent advancement of a XEP indefinitely (whether this > is a good idea is up for debate, but that's the way it is). > >> If that is the case there would be no reason for me to spend a >> minute more on finding a reasonable way to add RDFa to XEP-0071. >> I generally do not participate in discussions with a >> predetermined outcome. > > Council members have been known to change their minds, but in this > case I think a significant change in scope/purpsoe of a Draft XEP > immediately before advancement to Final might be a bit extreme. > This doesn't, however, prevent proposal of a new XEP implementing > RDFa, which would seem a sensible route to take here.
Andreas, I agree with Kev -- Ralph is concerned about making major changes to the scope of XEP-0071 when it is close to a Final spec. However, developing a new spec for RDFa over XMPP makes sense. In fact, I think it would be simpler than XEP-0071 because in XEP-0071 we had to define a new Integration Set using XHTML modularization (which I found kind of confusing at the time), whereas the W3C has already defined RDFa for us using XHTML modularization, so all we need to do is define a wrapper element for sending RDFa over XMPP. In fact, I chatted with someone else about this very topic last week, so I will introduce you to him offlist in case you want to work together. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB8IdYACgkQNL8k5A2w/vxQIQCeKaEbgSDy6f7kobN/sqiAiTXb vwcAn2KYHcZSay2d5/aj8zG91vVuE2RU =pbCN -----END PGP SIGNATURE-----
