Re:Quill – A cross browser rich text editor with an API
by andybak on Sunday October 25, 2015 @05:44PM
(#10448566)
Explain what you mean by 'semantic markup'. I find people mean the term in two ways: so trivially it's uninteresting or so unrealistic it's implausible.
[ Parent
| on HN ]
Re:Quill – A cross browser rich text editor with an API
by oneeyedpigeon on Monday October 26, 2015 @04:54AM
(#10450168)
In my experience, the most common meaning of 'semantic' is 'non-presentational'. For example:
<font color="#ff0000">hello, world</font>
is non-semantic because it's referring purely to presentation, rather than meaning. I'm not just being obtuse, this is a real-world requirement since our editors need to be able to mark things up according to meaning, but not randomly screw around with our design. I admit there's a blurry line, exemplified by the W3C's redefinition of the 'b' element.
Re:Quill – A cross browser rich text editor with an API
by andybak on Friday October 30, 2015 @04:31AM
(#10476692)
I'd concur that is a good example of 'non-semantic' but what's trickier is to agree on what 'semantic' markup looks like. Short of well-executed microdata - I've always felt that a lot of claims about markup best-practice smacked of cargo-culting.
It's always worth asking the question: "semantic for whom"? i.e. who is the consumer. That clears away a lot of fog.