Talk:Parsing/Notes/Wikitext 2.0/Typed Templates

Re: "a mechanism where knowledge domain concepts from the source wiki could be mapped to identical concepts on the target wiki"

I'm not familiar with how Content Translation handles this, but I assumed it was simply via checking Wikidata's interwiki links? I believe that is how the toolforge translate tool works (you specify a source-article, and it finds equivalent in-article links in the target language).

There's also phab:T121470 to consider ("Central Global Repository for Templates, Lua modules, and Gadgets") [that's a more detailed duplicate-task of a much older task].

I haven't looked into how CX handles this right now either. But, that sounds like a reasonable approach to me. Those interwiki links will also eliminate the need for all wikis to provide taxonomy links .. i.e. one wiki can provide a link to a concept and we can leverage interwiki links to infer that concept for all other wikis.

Re: "It is possible to imagine a future application where there might benefits to a template specifying custom javascript resources or other sources that govern the behavior of that template (ex: animations?). That will require its own mechanism."

This made me think of WikiWidget:

• Example: w:es:Wikipedia:WikiWidget (in-article at w:es:Juego de la vida)
• English docs: c:Commons:WikiProject WikiWidgets (prior discussions about it are linked at the bottom there)

IIRC, the 2 main blockers for wider usage were security concerns (cf. phab:T71445) and user-bandwidth increases (i.e. mobile/dial-up users).

Thanks for the wikiwidget links -- didn't know about them. Those are orthogonal concerns. But, my observation is that insofaras those concerns can be addressed satisfactorily, this type structure can be a unified mechanism to support / accommodate that functionality without having to invent another custom mechanism for it.