Hi,
On Mar 15, 2015 19:20, "Legoktm" <legoktm.wikipedia(a)gmail.com> wrote:
Yes, this is controversial and probably needs wider
discussion outside
of this mainly technically-focused list.
agreed. has that happened?
This is something that needs community discussion on-wiki as well as
announcement on wikitech-ambassadors(a)lists.w.o
Is this intended for web too or just app?
I'm concerned with this being a slippery slope.
Part of the problem that
I see is that the content being controlled by the apps rather than
on-wiki. I don't really have any better ideas than something similar to
class="metadata" which TextExtracts removes though.
Is there a team (or even a phabricator project) responsible for tracking,
prioritizing, implementing, etc the use of standard templates, element IDs,
microformats and semantic markup?
What teams and external users need what structure?
Then maybe you can differentiate between unrelated bracket scenarios
(pronunciation vs. aka name vs. dates vs. transliteration) by the markup.
And if heuristics are absolutely necessary then there should be a way for
editors to override the heuristic for a particular case adhoc. And to later
for an editor to reset that case back to deferring to the heuristic.
There should be a way for a desktop editor to see from the desktop site
what will be hidden from or shown to app readers and mobile web readers.
-Jeremy