[tei-council] pdf version of guidelines, fonts

[Lou Burnard]

Just for the record, I entirely agree with Sebastian's view here, and 
this was the reason why I proposed a much simpler and shorter valList in 
an earlier version of this spec. But Syd chose to reinstate the long 
list we now have, and I did not have the time or energy at the time to 
dispute the issue.

Equally, while I agree that it is worth noting that W3C datatypes have 
different possibilities with respect to ISO datatypes, the place to make 
such observations is probably in the discussion of the datatypes, not here.

Sebastian Rahtz wrote:
>
>>
>>  (because we have adopted W3C
>> datatypes) the datatype has a limited range of numbers that can be
>> expressed in scientific notation. Such an admission of the limitations
>> of the system is extremely important, and needs to be expressed.
> I am not entirely sure you are right. The relevant
> bit is a <vaList type="semi"> applying to @unit in att.measurement.
> Since it's only "semi", it is purely advisory, not normative.
>
> Anyone who wants to know what a "kibibyte" is
> will go look it up. Describing it as "1024 bytes"
> doesn't tell me anything, since we don't define "byte"
> anywhere!
>
> The text says
> Wherever appropriate, a recognised SI unit name should be
> used (see further <ptr target="http://www.bipm.org/en/si/"/>
> which is fine. Personally, I'd leave it as is and forget
> the whole <valList>. Partially summarizing international standards
> seems like an odd thing to do.
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>