[activitystreams] Issue: Why exclude markup from name? marked as i18n

r12a has just labeled an issue for 
https://github.com/w3c/activitystreams as "i18n":

== Why exclude markup from name? ==
Please Indicate One: 
 * [ ] Editorial
 * [x] Question
 * [ ] Feedback
 * [ ] Blocking Issue
 * [ ] Non-Blocking Issue

[This issue has support from others in the i18n WG.]

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-name

> HTML markup MUST NOT be included.

What is the reason for explicitly excluding markup from the name 
value, whereas it is allowed for other natural language values?  It 
will force people to convert to or use control characters for inline 
bidirectional controls, and will prevent inline annotation for 
language change. Why cannot implementations simply remove markup (and 
convert bidi markup to control codes where needed)?


See https://github.com/w3c/activitystreams/issues/338

Received on Friday, 8 July 2016 13:59:25 UTC