[tei-council] Should Roma be doing this?

[Martin Holmes]

First of all, I think we should get rid of it in this particular case. 
As Syd and Sebastian say, it makes no sense, especially when we're a bit 
in doubt already about what the recommended values should be.

Then I think we should look at all default values for attributes which 
are optional, at least.

Cheers,
Martin

On 13-02-06 01:42 AM, Lou Burnard wrote:
> May e we should start deprecating defaultVal ?
>
> Sent from my HTC
>
> ----- Reply message -----
> From: "Sebastian Rahtz" <sebastian.rahtz at it.ox.ac.uk>
> To: "<mholmes at uvic.ca>" <mholmes at uvic.ca>
> Cc: "TEI Council" <tei-council at lists.village.virginia.edu>
> Subject: [tei-council] Should Roma be doing this?
> Date: Wed, Feb 6, 2013 09:25
>
>
>
> The current odd processor does very little error/consistency checking of
> this kind,
> so I am not surprised that you can generate a nonsense. I suppose one could
> trap this situation fairly easily.
>
> don't get me started on the nonsense of the defaultVal for list/@type of
> "simple".
>
> --
> Sebastian Rahtz
> http://www.justgiving.com/SebastianRahtz
> Director (Research Support) of Academic IT Services
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> --
> 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

-- 
Martin Holmes
mholmes at uvic.ca
UVic Humanities Computing and Media Centre