[tei-council] encodingDesc content

Laurent Romary laurent.romary at loria.fr
Mon May 25 09:18:42 EDT 2009


+1 (changing the prose). Given the multiplicity of objects we have in  
model.encodingPart, it makes sense to put prose explanation here and  
there to justify the actual encoding choices. I would not follow SYd's  
suggestion here to put all the prose at the back.

Le 25 mai 09 à 10:07, Peter Boot a écrit :

> Lou Burnard schreef:
>> " Section 2.3 says, "The encoding description may contain paragraphs
>> of text, marked up using the p element, or it may contain more
>> specialised elements taken from the model.encodingPart class." This
>> doesn't match the content model: ( model.encodingPart | model.pLike
>> )+"
>
> I wasn't there when the decisions about P5 were taken, but I'd say  
> that
> if for some reason it's not possible to use a fully structured
> description, it is still preferable to use the specialized elements as
> far as possible. I'd rather change the prose therefore.
>
> A refinement was suggested by Syd
> (http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0709&L=TEI-L&P=R2975 
> )
>
>> element encodingDesc { att.global.attributes, (
>> model.encodingPart_sequenceOptionalRepeatable, model.pLike* ) }
>
> Peter
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council



More information about the tei-council mailing list