On 18.10.2017 17:59, Jonas Wielicki wrote:
> On Mittwoch, 18. Oktober 2017 17:28:31 CEST Jonas Wielicki wrote:
>> On Montag, 16. Oktober 2017 18:38:46 CEST Jonas Wielicki wrote:
>>> The XMPP Extensions Editor has received a proposal for a new XEP.
>>>
>>> Title: Body Markup Hints
>>> Abstract:
>>> This document specifies hints about the markup language used in
>>> elements.
>>>
>>> URL: https://xmpp.org/extensions/inbox/bmh.html
>>
>> So, I don’t like this.
> 
> Two points I’d like to add to my arguments:
> 
> 1. Discovery doesn’t work in modern IM. It doesn’t work in MUC (with MSN), it 
> doesn’t scale for MIX, it doesn’t work for one-on-one chats (due to Carbons 
> and MAM). So it is not relevant for any applicability of the spec where 
> normal 
> IM clients are on the receiving end.

Discovery is really just a goodie I wanted to take along. I could also
remove it without impacting the purpose of BMH in any way.

> 2. Putting textual markup in the <body/> is an accessibility problem, more so 
> if the markup gets more complex (I can imagine that common markdown flavours  
> (if used well! no inline URLs for example) would work well, because a11y 
> tools 
> might be used to such content from emails, but reStructuredText and 
> CommonMark 
> could be challenging). I mention that specifically because I’ve heard "Jabber 
> clients are not accessible" from affected people more than once as a reason 
> against using Jabber. We shouldn’t make it harder.

Accessibility is hard. And yes, plain text would be ideal. But sometimes
you don't have a plain text version. I think BMH would be mostly used
when we expose data which is already formatted using some markup language.

So quite contrary I believe BMH improve the accessibility. Because the
client could perform some optimization regarding accessibility when he
knows the used markup language.

Again: The assumption is that there is a lot of markup'd data,
especially CommonMark, out there. And the amount flowing through the
XMPP network will increase over time.

- Florian

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to