%ents; ]>
Body Markup Hints This document specifies hints about the markup language used in &BODY; elements. &LEGALNOTICE; xxxx ProtoXEP Standards Track Standards Council XMPP Core bmh &flow; 0.0.1 2017-10-14 fs

First draft.

This document specifies hints about the markup language used in &BODY; elements found in &MESSAGE; stanzas. It also specifies a mechanism to discover support of various markup dialects

This list is not comprehensive and not meant to be.

Language Identifier Name Specification Link
urn:xmpp:bmh:commonmark:0 CommonMark http://spec.commonmark.org/
urn:xmpp:bmh:rst:0 reStructuredText http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html

TODO: Shall we define your own subset of e.g. CommonMark, XMPPMark? :)

If the &BODY; element contains text which is "formatted" with a markup language, then the sending client MAY adds a <body-markup-hint/> element qualified by the 'https://xmpp.org/extensions/bmh/0/' namespace with the 'language' attribute set to the Language Identifier of the used markup language.

1. Ingredients - spaghetti - marinara sauce - salt 2. Cooking Bring water to boil, add a pinch of salt and spaghetti. Cook until pasta is **tender**. 3. Serve Drain the pasta on a plate. Add heated sauce. > No man is lonely eating spaghetti; it requires so much attention. *Bon appetit!* ]]>

It is RECOMMENDED that entities announce the supported body markup languages in its service discovery information as specified in &xep0030;. Every markup language is announced as a <feature/> element with the 'var' attribute set to the language identifier of the supported language.

... ... ]]>

There MUST be only one <body-markup-hint/> per &MESSAGE; stanza, and it applies to all &BODY; elements within the same stanza.

TODO: Discuss.

This document requires no interaction with &IANA;.

TODO: Is it sensible to establish a registry for this?

TODO: Add after the XEP leaves the 'experimental' state.

Thanks to everyone who provided feedback.