[tei-council] Fwd: style lang definition

[Lou Burnard]

Apologies, I had forgotten that the minutes of the Oxford meeting quite 
clearly (if elliptically) provide a better solution to this problem.

* A new element, which will be declarable, to specify the style language 
will also be created after discussion on council list.

* @scheme on <rendition> should be moved into its own class, so that the 
new element can have it.

So here's for the "discussion on council list"

I am proposing to create a new element <styleDefDecl> to specify the 
default formal language used to express rendition, and also a new 
attribute class att.styleDef. This class will supply unchanged the 
attribute @source, currently locally defined on <rendition>. The new 
element will be a member of model.encodingPart, so it will occur, 
possibly multiple times, within <encodingDesc> It will also be a member 
of att.declarable, so you can use one language in one chunk of a 
language and another in another. Nevertheless, I would like to  add some 
prose to the effect that using more than one lang in a given document is 
Not A Good Idea, since it makes the combination of rendition information 
(already possible factored across three different places) needlessly 
complicated.

Does this sound plausible?

And is there any support for my suggestion that in the absence of a 
<styleDefDecl> we assume @style values (and <rendition> contents) are in 
CSS?




-------- Original Message --------
Subject: [tei-council] style lang definition
Date: Sat, 6 Oct 2012 16:08:09 +0100
From: Lou Burnard <lou.burnard at retired.ox.ac.uk>
To: <tei-council at lists.village.Virginia.EDU>

On 05/10/12 19:35, Martin Holmes wrote:

>   > -- Where do we specify the language in which @style values are
> expressed ?
>
> There has to be an element in the header, presumably in <tagsDecl>.
> Something like this:
>
> <style scheme="css"></style>
>
> although I'm not sure we want to go with the same potential confusion as
> we've already got with <rendition> vs @rendition.

This would be OK, except that we already have <rendition scheme="css">
inside <tagsDecl> which would give us two ways of doing the same thing.
I am proposing to just use the existing mechanism, which means that we
will need to require that if @style is used anywhere there must be (at
least) one <rendition> with a @scheme attribute in the header. Unless we
want to say "if all else fails it's got to be in CSS".

I checked in a bunch of changes to CO and ST yesterday as part of this
fix, so  if you want to see how the revision is going, visit (for
example)
http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Guidelines/en/CO-CoreElements.xml?r1=10912&r2=10924


-- 
tei-council mailing list
tei-council at lists.village.Virginia.EDU
http://lists.village.Virginia.EDU/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived