[tei-council] List @type musings

[Lou Burnard]

I don't think you're the only one with that bit set!

(is a bit set better than a mind set?)

I think the point is that we'd like to be consistent in our own 
practice, here as elsewhere in the Guidelines, and years of experience 
has shown that the only way of achieving consistency is to enforce it 
somehow...


  On 06/08/14 18:47, Syd Bauman wrote:
> Hey, Martin --
>
> It's not that I feel @rend is not the right way to do this. Yeah, I
> have a mild preference for @rendition, or even @style, but certainly
> not a big one. I think it's that I'm nervous about the Guidelines
> making suggestions about what the values of @rend should be. I think
> I have some bit set in the back of my mind that holds that the
> Guidelines should either be recommending a complete system for
> describing how text on a page (or other TBO) looked, or leaving @rend
> as a grab-bag for projects to decide about.
>
> Yeah, that's what makes me uncomfortable with a <valList> (even an
> open one) for @rend. After all, there are *no* other <valList>s for
> @rend in the Guidelines; and I suspect there never have been.
>
> Perhaps I just need to reset that bit ...
>
>
>> I think you feel as I do, that @rend is not the way to do this; it
>> should be @rendition or @style. But we're only attempting to
>> provide a smooth migration path for users from the old system.
>>
>> One alternative is to provide these values as a suggestion in the
>> source code only, with a strong recommendation that they ONLY be
>> used for cases where a project is being migrated from @type, and
>> that all new projects should use @rendition/@style.