Le samedi 14 octobre 2017, 11:59:17 CEST Peter Waher a écrit : > Hello > > A year and a half ago I proposed a XEP: "Content Types in Messages" [1], > solving the issue of describing and annotating what type of content is sent > in messages. At the time, many objected, since they did not see the value > of this annotation. > > Now, the interest seems to have been awakened again, with a new proposal: > "Body Markup Hints" [2]. Both seem to be based around markdown, so there's > an obvious common interest and common ground. > > What I wonder is: Why don't we collaborate on this? There are already > implementations of [1]. It solves the issue using a paradigm that matches > what is elsewhere used on the internet (Content Types). Why invent > something new, and not renew the application of the original proposal? And > if there's something missing, the proposal can be updated, and the author > list increased. > > Best regards, > Peter Waher > > [1] https://github.com/xsf/xeps/blob/master/inbox/content-types.xml > [2] > https://github.com/xsf/xeps/pull/529/commits/4bc652eb7cefb5489f67f31a3eda20 > 21cba85783
Hi Peter, I was one of those objecting, and I wasn't objecting because I "did not see the value of this annotation", but because I thought (and I'm still thinking) that it's a terrible solution. Moving from a well working thing to an syntax is already something I'm not really supporting even if I could follow if we have a good alternative (i.e. not Markdown), but having an open bar and letting any content type like you proposed is just saying goodbye to the idea of interoperability (and the sanity of clients developers), and it was a true relief to see a veto on this one. Cheers Goffi _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
