And, having looked it up, I think Lou's right that we should be using @decls to set the default (though I still think we need the ability to set element level exceptions to the default scheme).
I said the ODD only because you'd raised the issue. Header is good for me. Also could we set a list of possible values for @rendscheme? It seems to me it would be an encoding benefit if the list of possible values could be constrained.
From: Sebastian Rahtz [[log in to unmask]]
Sent: March-23-12 9:16
To: O'Donnell, Dan
Cc: [log in to unmask]
Subject: Re: CSS in @rend (was Re: Why no space, etc. in DIV's @type?)
On 23 Mar 2012, at 15:06, O'Donnell, Dan wrote:
> I think we could eliminate some of this if we did a couple of other things:
> 1) made rendscheme optional when it doesn't differ from the default (which for reasons of neutrality and backwards compat., rather than convenience, I'd recommend be "token"). So your example would now be
> <p rendscheme="css" rend="font-size: 11pt;"> <hi rend="bold italic">hello</hi></p>
no, because @rendscheme would naturally be inherited, surely?
> 2) allowed users set their own default either in the header or just as part of the ODD (so people could set the value of rend to CSS rather than token, which I think is probably the most common case): I think in general people /will/ want to set this, because I suspect most projects will have a usual style language they mostly use and only the occasional exception.
i'd worry a bit about it being in the ODD, as thats not so easily accessible to an interoperability validator.
Head of Information and Support Group
Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
Sólo le pido a Dios
que el futuro no me sea indiferente