Hmm, as always, I think it depends on your definition of ‚text‘ …
In my example of https://twitter.com/wnd_go I’d probably encode all tweets as <div> or <ab> within one <text> and then try to capture all possible connections (with <relation>?)
But that’d be a definition of text which is rather pragmatic, not reflecting any (aesthetic) reception.
Regarding the msPart/msFrag issue, I think it’s better to leave the text issue aside and concentrate on the (physical) object part. I don’t see any problems the msPart/msFrag issue creates nor solves relating to multiple texts.
Just my tuppence
> Am 13.03.2015 um 13:29 schrieb Piotr Bański <[log in to unmask]>:
> So what we've got here is, arguably, a multi-part object corresponding to several texts. I am now wondering:
> 1. Are such "one multi-part object : many texts" setups easily expressible in the current TEI?
> 1.1. Aren't we talking multiple <text>s here or would <teiCorpus> provide a convenient escape hatch?
> 1.2. Where would we place the relevant object-pointing element if we were to use teiCorpus? Shouldn't it be a sibling of <text>(s)?
> 2. Could/should the above musings influence the current msPart/msFrag debate in ? (I use the "should" for the sake of potential uniformity of the conceptual model)