<h1 itemprop="name">John Doe</h1> <p>Name: <span itemprop="name">John Doe</span></p>
I was noting that the editing would be changing both lines.
Ah- I missed the identical itemprop ;)
So far we have only considered editing of arguments actually stored in the including page, but not templates. Even arguments would initially only be inline-editable if they are expanded directly rather than passed on to other templates. For now, passed-on arguments would be stored (as wikitext or tokens) in meta elements, and would be editable only using a widget. It should be possible to improve on that later.
Yes, but a could be present in an editable form and an uneditable one. If the parser can't show the change in the uneditable one, it shouldn't allow its edition.
That is a good point- the editor view would get inconsistent if it can't identify the second use of the argument. We could perhaps revert to the sledgehammer method of re-expanding the template top-down using a call to the parser.
There are also questions around editing of 'complex' arguments (which include templates or the like). If we simply revert to WikiText editing of those, then a modification that results in unbalanced WikiText would have non-local changes when re-parsed globally. We could perhaps try to enforce well-formedness in a validation (or parsing) step.
Gabriel