[tei-council] Proposal <idno> coverage -SF 2493417

[Peter Boot]

Sebastian Rahtz schreef:
> Peter Boot wrote:
>>
>> As a way to sidestep these ramifications, couldn't we introduce a 
>> schematron rule that says something like: if an <author> has an <idno> 
>> child, it must also have one name|persName|orgName child and can't 
>> have text children. This would remove the mixed content problems.
> 
> You could do that in the schema, never mind schematron, if
> that's what is decided. 

Yes, you're right.

> It seems bad to special-case <idno>
> like this, though, or to dictate that it must come first
> in an <author>
> 
> But if you say there are two forms of <author>, one
> with structure and one without, 

That's more or less the logical consequence of my suggestion, yes, but I 
wanted to avoid having to reach agreement about the whole content model 
of a structured author/authorStruct before we could settle the idno issue.

> isn't it actually easier to add <authorStruct>....?
 >
> is it going to stop here, though? presumably
> <editor> has exactly the same issues? will <publisher>
> be next?

editor, yes, I'm not sure about publisher