Hello all
> If anything we should define a small microformat that looks good
> formatted or in plain text (which could just be a specific Markdown
> flavor minus the raw HTML stuff) and mandate that all clients that
> support the spec use that one format.
Why define something new when there's a format that people like, know and want
to use?
Furthermore, leaving the format out of the XEP allows standardization of the
format to be done in other forums.
>
> So perhaps both approaches have their use cases? I don't fundamentally
> object to either, but including multiple renderings in a
> multipart/alternative style all the time just for improved handing of
> *this* seems overkill.
>
What about an approach that allows both?
Say we create a new element <content type='...'/> that we send with the
message. If it's empty, it could be considered a hint regarding the format of
the message body. If it is non-empty, it contains an alternative, a formatted
version of the plain text message body.
Would that be an approach that the council would accept?
Best regards,
Peter Waher
_______________________________________________
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
