[tei-council] Styling of TEI <ident> in HTML Guidelines

Lou's Laptop lou.burnard at oucs.ox.ac.uk
Fri Jan 4 16:12:08 EST 2008


I've now done a bit of a tidy up on the values used for the @type 
attribute on <ident>.
The following usages seem worth distinguishing; their frequencies in the 
current Guidelines are as follows:

  2 ge   [general entity name]
  2 rng  [rng identifier]
  4 frag [dtd fragment identifier]
  4 macro
  5 ns   [namespace]
  7 schema
 11 pe   [parameter entity name]
 13 datatype
 22 file
 27      [unspecified]
 65 module
345 class

> Sebastian Rahtz wrote:
>   
>> I incline to James' view, keep them distinct in the CSS
>> to be on safe side.
>>
>>   
>>     
> I agree with this, to some extent. See below.
>
>   
>> Mind you, I question the usefulness of
>> distinguishing between these:
>>
>> ident-feature
>> ident-frag
>> ident-ge
>> ident-kw
>> ident-macro
>> ident-pe
>> ident-var
>>
>> a) what are pe and ge and macro? and when is a feature not a var?
>>
>>   
>>     
> pe and ge are parameter and general entity names respectively.  I think 
> a "feature" is specifically the name of a feature in the FSR chapter. I 
> can look into where these are actually used, but I think they are both 
> pretty infrequent, and inconsistently applied (i.e. I'll bet there are 
> variable identifiers which are not tagged with @type=var). The best 
> course is surely to have a default rendition for all <ident>s, 
> irrespective of @type value, and then supply specific values for the 
> most common and usefully distinguished values.
>
> Not constraining @type vallists is always going to come back and bite 
> you in the end.  
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>   

     


More information about the tei-council mailing list