[tei-council] span span span span span span span span glorious span

[Martin Holmes]

Hi Lou,

Your rules look good to me.

On the last question, I think there are two possible ways to mark up the 
text. Your example implies that the paragraph break is also deleted:

<p>blah<delSpan spanTo="#delEnd"/>  blah</p>
<p>blah<anchor xml:id="delEnd"/>  blah</p>

whereas if the intention was to delete only the text fragments and leave 
the paragraph boundary intact, there would be two deletions:

<p>blah<del>  blah</del></p>
<p><del>blah </del> blah</p>

Cheers,
Martin

On 11-08-19 08:29 AM, Lou Burnard wrote:
> As I said on the call, I am currently  working through tcw18 (the
> genetic editing doc) and constructing from it a proposed set of
> additions to P5. In due course you can expect to see a long list of
> requests for comment and minor clarification here, as well as the
> document itself.
>
> However. I'd like to raise here and now one specific point which I have
> just hit, since it's not one we've discussed explicitly, and which has
> fairly major implications.
>
> This is the correct usage for the attributes @target and @spanTo. A
> number of the new elements proposed in the working paper are meant to
> operate in "stand off" mode, and use these attributes to indicate the
> bits of transcript to which they apply. (examples include metaMark,
> undo, redo). The document is a bit vague about how these attributes are
> supposed to operate in combination, if at all, and the examples cited
> are mutually contradictory.
>
> I'd like to propose the following set of rules.
>
> 1. @target behaves as elsewhere in the Guidelines -- it's a URL, which
> can point to one or more whole elements, or xpath-defined substrings
>
> 2. @spanTo is also (as elsewhere) a URL., but it must point to a
> *single* element.
>
> 3. it is erroneous to supply both attributes on the same element.
>
> 4. if only @target is supplied, the passage/s affected are all the
> element content fragments indicated by the URIs supplied, treated as a
> single unit
>
> 5. if only @spanTo is supplied, the passage affected is the sequence of
> content fragments that begins immediately following the element
> concerned and finishes  immediately preceding whatever element is
> indicated by the @spanTo attribute.
>
> 6. if neither attribute is supplied, the markup is erroneous
>
> It's important to get this, if not right, at least consistent, as we
> have a number of other places where @spanTo has been invoked as The
> Solution.
>
> I'd also appreciate help with the following conundrum
>
> Suppose we find
>
> <p>blah<delSpan spanTo="#delEnd"/>  blah</p>
> <p>blah<anchor xml:id="delEnd"/>  blah</p>
>
> Clearly two of my "blah" content nodes are being deleted. What about the
> tags? In other words, if I write a processor to act upon the markup and
> produce a new XML representation of it, should it produce
>
> (a)<p>blah blah</p>
>
> or
>
> (b)<p>blah</p><p>blah</p>
>
> I am pretty sure I know the right answer, but I am not sure I know how
> to express the algorithm such a processor should apply.
>
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
> PLEASE NOTE: postings to this list are publicly archived
> .
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)