I agree it’s very odd. It appears to have been that way as long as svn has history for the spec file. See https://github.com/TEIC/Guidelines-TEST/blob/4a7d8e58ac5c3cd7d00a2af378975e1... <https://github.com/TEIC/Guidelines-TEST/blob/4a7d8e58ac5c3cd7d00a2af378975e1c1c2f21ce/P5/Source/Specs/langUsage.xml> So it’s been busted for at least almost a decade...
On Aug 10, 2015, at 4:24 , Lou Burnard <lou.burnard@RETIRED.OX.AC.UK> wrote:
The process of TEI content models proceeds apace and (as might be expected) is turning up a few oddities in some unfrequented corners.
For example, the content model of <langUsage> is currently (in the source)
<content> <oneOrMore xmlns="http://relaxng.org/ns/structure/1.0"> <choice> <!-- <rng:ref name="p"/>--> <ref name="language"/> </choice> </oneOrMore> </content>
Now, this is clearly nonsense : you can't have an alternation with just one option. But did we really want to remove the possibility for having a purely documentary <langUsage> such as <p>Contains various unrecognised Polynesian languages</p>?
Can anyone remember why we made this change ? I would have expected to see something like
<choice> <oneOrMore> <rng:ref name="model.pLike"/> </oneOrMore> <oneOrMore> <rng:ref name="language"/> </oneOrMore>
myself.
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived