[tei-council] let's sort out the <w> problem first...

[James Cummings]

Lou Burnard wrote:
> I think it might be better to partition model.segLike into those which 
> can reasonably be expected within a word (<m> and (possibly) <c>) and 
> those which cannot (<cl>, <phr>), I'm unsure about <seg>.

Ok, that's a solution I could buy into.  In would be in favour of 
including <seg> because otherwise it isn't really being an 'arbitrary 
segment' if I can't use it to say something about part of a word. And 
this could then be used for legacy conversions where someone has 
(perhaps unadvisably) used some of the other segLike elements.  (Though, 
reading seg's desc it could maybe stand some rewriting since referring 
to 'chunk' level things might not be the clearest way of expressing it 
-- though I've no helpful suggestions.)

-James

-- 
Dr James Cummings, Research Technologies Service, University of Oxford
James dot Cummings at oucs dot ox dot ac dot uk