daniel added a comment.
@Yurik that was actually what I had in mind originally. We called it multi-part content, like the MIME encoding for emails. The problem is that it is not backwards compatible. It would break everything that expects to be able to edit text via the action=editpage interface, or find text in the <text> tags in an XML dump. It's not transparent - all code processing content has to know about the new multi-part model. That would probably be acceptable for newly introduces types of pages, but we cannot use the multi-part approach with article pages, or talk pages, or file descriptions - all the client code would break. When discussing this issue with James (and I think Roan) in Lyon, we came up with the multi-content revision approach. Multi-content revisions are not only backwards compatible, they are also a more powerful concept. For example, it supports updating derived content slots. TASK DETAIL https://phabricator.wikimedia.org/T107595 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: daniel Cc: RobLa-WMF, Yurik, ArielGlenn, APerson, TomT0m, Krenair, intracer, Tgr, Tobi_WMDE_SW, Addshore, Lydia_Pintscher, cscott, PleaseStand, awight, Ricordisamoa, GWicke, MarkTraceur, waldyrious, Legoktm, Aklapper, Jdforrester-WMF, Ltrlg, brion, Spage, MZMcBride, daniel, D3r1ck01, Izno, Wikidata-bugs, aude, jayvdb, fbstj, Mbch331, Jay8g, bd808 _______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
