[tei-council] feasibly valid (again)

[James Cummings]

On 04/02/11 09:40, Sebastian Rahtz wrote:
>      3) feasible examples are given an extra CSS class, which puts a yellow
>          border around them

I asked the web designer sat next to me who said that he barely 
noticed the yellow box and that this was a bad thing.  If we want 
to highlight the difference of valid vs feasible valid (since 
we're assume we're not going to have any *invalid* examples at 
the end of this process?) then we should do so slightly more 
dramatically.

He suggests that all valid examples have a 
off-white-but-green-tinted background, with a darker version of 
the same green as border, and the feasible valid ones have an 
off-white-but-amber-tinted background, with a darker version of 
the same amber as a border.  The idea being that green means 
correct/good and amber means warning (and if we have any invalid 
ones then these should, of course, be red in a similar manner).

It might also be useful to have @title attributes on these 
indicating that this example is feasibly valid or something. 
Though to be semantically more accurate this should say "A 
feasibly valid example [of $bibliographic-entry-here]", where the 
bibliographic data that is linked to in the examples is provided 
if it exists.

I pass on the feedback in case it is useful.

-James

-- 
Dr James Cummings, Research Technologies Service
OUCS, University of Oxford