Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#249 roll Tite into TEI P5

Tite
open
Kevin Hawkins
Tite (11)
5
2012-05-06
2010-09-26
Kevin Hawkins
No

Lou and Sebastian think it would be a good idea to roll Tite-specific elements into the TEI namespace. Kevin thinks this would have the extra benefit of not having the TEI maintaining two namespaces, leading people to using a Tite schema to need to invent at least one namespace prefix in order to tell the validator where to find the elements.

Discussion

  • Kevin Hawkins
    Kevin Hawkins
    2010-09-26

    Sebastian wrote on tei-council:

    I think that Lou probably meant to say "drop some of the sillier extensions in Tite and merge in the rest". So looking at new elements

    ident="cols"
    * add
    ident="sub"
    * add
    ident="sup"
    * add
    ident="ornament"
    * add

    ident="b"
    ident="i"
    ident="smcap"
    ident="ul"

    these remain _so_ much syntactic sugar that I'd be very reluctant to add them. is it really so very hard to simply constrain <hi> to allow only these values on @rend?

     
  • The principle is sound. But, as Kevin quotes me, I find the synonyms for <hi rend='xxx'> hard to stomach. I propose instead that @rend pn <hi> be a fixed list in Tite.

     
  • Kevin Hawkins
    Kevin Hawkins
    2010-09-26

    Note that if we don't decide to merge these namespaces, it would be a good idea for Tite to mandate use of a DTD rather than other schema type by any vendor charging for delivered files by the byte.

     
  • Lou Burnard
    Lou Burnard
    2011-03-20

    I think that providing a fixed set of values for the @rend attribute on <hi> makes more sense than defining tite:smcap etc , but I can live with either or both. If I ever actually said that we might add <smcap> to the TEI namespace I was clearly raving. I don't understand the comment on "mandating use of a DTD rather than other schema type" below -- there isn't any obvious way of doing such a thing and it doesn't seem relevant to this ticket.

     
  • Lou Burnard
    Lou Burnard
    2011-03-20

    • assigned_to: nobody --> kshawkin
     
  • Lou Burnard
    Lou Burnard
    2011-03-20

    • milestone: --> Tite
     
  • Kevin Hawkins
    Kevin Hawkins
    2011-03-24

    Obviously the TEI Consortium cannot and should not attempt to restrict anyone's use of our schemas or documentation beyond the restrictions on the GNU license. However, since Tite is designed for use by vendors and discusses things such as accuracy of keyboarding, I believe it would also be appropriate for Tite to discuss things that can affect the number of characters used in the encoding: namely, the use of namespaces for TEI elements. Since vendors often charge by the byte, the size of the file can vary greatly depending on where and how namespaces are specified. To me the most sensible way to enforce uniformity and keep the byte count to a minimum is to require a vendor to use the DTD, not one of the various schema formats, avoiding namespaces entirely.

    You might say this is something for a vendor and customer to negotiate, but the point of Tite is to provide something ready to use for customers and vendors who don't want to have to go through all of this on their own.

     
  • Kevin Hawkins
    Kevin Hawkins
    2012-05-06

    • summary: roll Tite-specific elements into TEI namespace --> roll Tite into TEI P5
     
  • Kevin Hawkins
    Kevin Hawkins
    2012-05-06

    Renaming this ticket to reflect what was actually suggested: rolling relevant parts of the Tite Guidelines, not necessarily Tite-specific elements.