Difference between revisions of "TEI Tite"

From TEIWiki
Jump to navigation Jump to search
m (add link)
(updated SourceForge link to GitHub)
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category: SIG:Libraries]]
+
: ''Not to be confused with [[TEI Lite]], a customisation designed to meet "90% of the needs of 90% of the TEI user community."''
[http://www.tei-c.org/wiki/index.php/SIG:Libraries TEI in Libraries: Home]
 
  
==TEI Tite: Issues Under Consideration==
+
TEI Tite is a constrained customization of TEI designed for use when outsourcing production of TEI documents to vendors (who use some combination of OCR and keyboarding). While the canonical version is maintained by the [[Council]], a [http://accesstei.apexcovantage.com/Home/AboutTeiTite derived version] is used in the [http://accesstei.apexcovantage.com/ AccessTEI] program.
  
* [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html the official release of Tite, HTML documentation]
+
Its most drastic departure from the TEI model is its lack of header.  Its designers felt that Tite would be a format used only in a transitional state between delivery from an encoding vendor and conversion into a more suitable TEI format for archiving (perhaps using OxGarage, the [[OxGarage|web-based front end]] to [[Tei-xsl|Sebastian's stylesheets]]). That is, vendors would generally not create header metadata for encoded texts but would instead identify the texts for encoding and communicate with the customer about them using a unique identifier agreed upon by the two parties.
  
* [[Review of Tite Scheme]]
+
TEI Tite is not meant as a successor to [[TEI Lite]].  While both formats are limited subsets of the TEI and have seen adoption in libraries, they are designed for different purposes.
  
Sorry my post is somewhat belated, given the survey has already gone outBut I wanted to raise one issue with tite--not with the scheme per se, but with it possible customization.
+
Schemas and documentation for TEI Tite and all other 'standard' customisations of the TEI are available at http://www.tei-c.org/Guidelines/Customization/ See [https://github.com/TEIC/TEI/issues?q=is%3Aopen+is%3Aissue+label%3ATite bugs and feature requests] relating to Tite.
  
My understanding is that this is a tool which can be used to approach a vendor to obtain a discount for TEI members.
+
[[User:Kshawkin/My_Council_obligations/Plan_for_TEI_Tite|Further work on Tite is planned]].
  
I also understand that as it stands now, this would not be customizable.  My question is: would the discount from vendors be achievable mainly by virtue of the simplified set-up of markup, or by virtue of the (potential) size of the group?  I assume both achieve some savings.  However, when I look at work we might want to submit to such a service, we would want customization in tagging for any of those--but with significant overlap with TEI lite.  If we get (theoretically) 50% of potential savings by virtue of the group, and 50% by virtue of using a single scheme, couldn't we still achieve 80% savings by allowing for ''some'' customization?
+
[[Category:Customization]]

Latest revision as of 21:46, 8 November 2015

Not to be confused with TEI Lite, a customisation designed to meet "90% of the needs of 90% of the TEI user community."

TEI Tite is a constrained customization of TEI designed for use when outsourcing production of TEI documents to vendors (who use some combination of OCR and keyboarding). While the canonical version is maintained by the Council, a derived version is used in the AccessTEI program.

Its most drastic departure from the TEI model is its lack of header. Its designers felt that Tite would be a format used only in a transitional state between delivery from an encoding vendor and conversion into a more suitable TEI format for archiving (perhaps using OxGarage, the web-based front end to Sebastian's stylesheets). That is, vendors would generally not create header metadata for encoded texts but would instead identify the texts for encoding and communicate with the customer about them using a unique identifier agreed upon by the two parties.

TEI Tite is not meant as a successor to TEI Lite. While both formats are limited subsets of the TEI and have seen adoption in libraries, they are designed for different purposes.

Schemas and documentation for TEI Tite and all other 'standard' customisations of the TEI are available at http://www.tei-c.org/Guidelines/Customization/ . See bugs and feature requests relating to Tite.

Further work on Tite is planned.