<q> should be allowed in <span>

[martindholmes]

The example here:

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/AI.html#index-egXML-d53e127418

(which I reproduce below in case the ids change) shows that there is an obvious requirement to be able to identify text which is "distinguished from the surrounding text using quotation marks or a similar method" (quote from the definition of <q>). However, the content model of <span> does not allow <q>. I think it would make sense to allow it. I'm not sure what the best route to this result would be.

<s>
 <w>What</w>
 <w>did</w>
 <w>you</w>
 <w xml:id="mk01">make</w>
 <w xml:id="up01">up</w>
</s>
<span from="#mk01" to="#up01">phrasal verb "make up"</span>

[bansp]

I have to say that the example is pretty horrible, but its ugliness does not invalidate the potential need for <q> inside <span>. :-)

[martindholmes]

@bansp Do you mean semantically horrible, or that the markup is horrible?

Given that spans are frequently used for commenting on pieces of the text, it seems mad that there's no mechanism for quoting fragments of the span.

[bansp]

Martin, I mean that I more or less share your sentiment, but the example is hopeless as a case of pseudolinguistic markup. It would be better to find an example that is more sensible on its own; I'm sure there must be other use cases that would illustrate your point. BUT the example itself (or rather the fact that it enjoys full privileges inside the Guidelines) gives me an idea for a nice and feasible LingSIG project, so I'm very happy that you posted about that! :-)

[sydb]

Given that spans are frequently used for commenting on pieces of the text, it seems mad that there's no mechanism for quoting fragments of the span.

What’s wrong with <mentioned>? And if you wanted to quote a fragment you would use <quote>, not <q>, no? (Although, of course, <quote> is not allowed either.)

[alex-bia]

This ticket has been discussed by the Council on Feb 25th 2018, with the following conclusions:

The choices are: to use <mentioned> or <soCalled>, or otherwise (if these solutions will not do) to add <q> to the content model of <span>. It's not a good idea to add the whole qLike class.

[scstanley7]

F2F Tokyo: We are going to add <q> to the content model of span to address the issue originally raised in the ticket.

[scstanley7]

Sorry, this ticket ended up posing more problems than we originally anticipated, so sorry for the delay. I'm resetting this this to "needs discussion" because the question now is "do we add <q> to macro.phraseSequence.limited"

[martinascholger]

F2F Graz: this will likely get solved by #1918, so waiting for that to close or re-evaluate this.

[martindholmes]

@bansp Did you ever follow up on replacing the examples you found egregious a couple of years ago? They're here:

https://www.tei-c.org/release/doc/tei-p5-doc/en/html/AI.html#index-egXML-d53e130554

[ebeshero]

@peterstadler and @sydb need to resolve #1918 and then come back to this.

[peterstadler]

implemented by moving <q> to model.hiLike in #2008