And I can't remember ever talking Syd
out of anything, certainly not this!
@sameAs is intended for cases where the samde thing needs (for
some reason) to be marked up as if it were multiple things. The
usual example is a node in a feature structure network which
features somehow in two places at once; like Hugh, I can't see why
this shouldn't be another (and perhaps more accessible) use case.
I may have suggested to Syd that such an encoding might however be
TCBH (too clever by half) -- in the sense that very few of the
many processors for <pb/>s around would be likely to do the
right thing when they found it.
On 18/02/14 12:42, Hugh Cayless wrote:
[log in to unmask]"
Not wishing to derail the discussion, but I’m very surprised at
this. I’d have thought identifying the same page break occurring
in two different text flows (main text and footnotes, e.g.) was
precisely a use case for @sameAs. Indeed, it was about the only
time I could imagine ever using it...
The WWP uses corresp= to
align two <pb> elements that represent the
same break occurring for
two different text streams. I might prefer
sameAs=, but Lou talked
me out of it (I can't remember his objection
to sameAs= -- and I
wouldn't be surprised if he's less happy with