This evaluates: TEI Lite The Text Encoding Initiative has a very large standard which can be subsetted. Unfortunately, one must pay to purchase the full standard as PDF for about ninety dollars. But, they make available the documentation for a very popular subset called TEI Litle. And, they have an HTML version of their specification on line. (Interestingly enough, the TEI consortium uses the TEI Lite for their own documentation.) They also have a "bare bones TEI" which is an even smaller subset. Does the host schema use a generic structural markup model? Yes. It supports a p tag, as wel as <div0>, <div1>, <div2>... <div n > tags. These have a type attribute. This specifies that the div element would represent "Book," "Chapter," section, etc. Or one can use div elements and nest them arbitrarily. Does the host schema define a "clause" object? One would have to use a div element with the appropriate type attribute. Does the host schema define a paragraph level object that represents a structural or grammatical paragraph? Yes, as indicated above, it supports a p for a paragraph and lists which consists of list, head and item. One could number the item's using a label or the n attribute. Using the host schema, can the clause equivalent object be inserted at arbitrary levels in the document hierarchy without transformation? There is no mention in the TEI lite documentation of being able to to put div elements inside a p tag or list tag. Review of the HTML docuemntation for the full TEI indicates that one cannot do this. In the host schema, are element names and the structure sufficiently flexible that the clause and paragraph level objects can be used for other legal and business documents? Absolutely! The user picks the naming convention they wish to use and uses this with the type attribute for the div. Does the host schema provide a mechanism to add semantic information about: whole documentsdistinct objects,such as clauses, within documents? The TEI Lite docuemtnation includes the following in the titlepage element: docTitle, docAuthor, docDate. in the Electronic Title Page projectDesc, editorialDecl and a prifileDesc which includes a creation and a Revision containging date and changes elements. If so, is the metadata model for the host schema sufficient for contracts or will it be necessary to extend it? These metatags appear insufficient for contracts. Does the host schema allow embedded values to be represented and semantic information to be added to these values? The full TEI supports symbolic values, numbers, ranges, rate of change, string values, and binary values for "features" There is also a structuring mechanism for things such as employee's, architectural descriptions, and the like. Does the host schema require use of a particular processing technology? The TEI is dependendent upon DTD's or Schema's. However, the resultant XML should be easy to work with using style sheets or Java programs. See the discussion below. Does the design of the host schema preclude use of particular currently available processing technologies? The P5 version uses XML name spaces, Relax NG, as well as DTD's It is at 0.1.1 and available on the SourceForge web site. However, the HTML documentation for P5 still refers to the DTD view. Does the host schema permit the numbering of clauses, paragraphs, lists and other objects to be represented in the markup? Yes, this is provided for with the n attribute. It is particularly needed since TEI is used to encode antiquarian and scholarly texts where it is important to refer to things by the original numbering convention. Does the host schema provide a mechanism to define the numbering schema applied to the document so that two applications could apply the same numbering, if desired? See above. Using the host schema, will it be possible for the contract author to explicitly represent all parts of the narrative contract terms or will it be necessary to imply some parts? There are tags for the textual divisions but none that would be useful for things particular to contracts such as recitals. Does the host schema represent the relationship between all significant components in a way that allow high quality print and web rendition of of contract documents? There are extensive tags for italics, emphasis, etc. Also, there are tags for marking off lines and blocks, intended for typesetting poetry or other verses. The TEI web page includes XSL style sheets, customizations for Passive Tex, and an open source tool called Anastasia. Does the host schema include a mechanism for defining variables for embedded data values? The full TEI supports symbolic values, numbers, ranges, rate of change, string values, and binary values for "features" There is also a structuring mechanism for records of such as employee's, architectural descriptions, and the like. The TEI lite does support xptr, xref, ref, ptr. However, these appear intended for cross references and not variable values. If the host schema does not include such a mechanism, is there any obstacle to adding it? See 12.2 Based on the following factors is the host schema easy for contract authors to use: Does it require authors to know only a small number of elements (positive factor)? Does it require authors make unnecessary or subtle distinctions that will be applied inconsistently (negative factor?) Does it have a clear logical structure that can be quickly explained to new users ( positive factor)? Does it allow authors to re-locate content objects within a document hierarchy with minimal or no need for transformation of markup (positive factor)? The concepts of list, p and div tags are straight forward. However, it appears that if one sets up a structure with div, it could not be moved into a list item or header. Is the host schema a DTD only or can it also be expressed as an XML Schema or other schema type? The documentation for TEI all reference DTD or SGML. However the new version, P5, is expressed in both Relax NG and W3C schema as ell. There is an application to generate "P5-compatible schemas and documentation." Note that the HTML documentation for P5 is still written in terms of DTD's and after a quick inspection, I found no reference to using the Relax NG or XML Schema versions of TEI. Does the host schema provide for the complete representation for the distinct structures commonly found in contracts? TEI Lite does not have these structures. If not, does the host schema explicitly allow additional distinct structures to be added? The full TEI has an extension mechanism. It apparently is based upon the parameter entry of DTD's and the P5 "mission statement" includes simplification of the extension mechanism. See 12.1. Does the host schema allow elements not considered necessary for contracts markup to be removed without contract documents being incompatible in a disadvantageous way with other documents using the host schema? Yes, there is a well-used and documented subsetting mechanism. If distinct contract structures are added to the host schema, will this result in contracts documents being incompatible in a disadvantageous way with other documents using the host schema? There are definite guidelines on how to extend the TEI. This includes the TEIFORM attiribute to specify that a new element is used in the role of an existing TEI XML tag. Presumably, if they are followed, one could still use the TEI software with our contracts. Is the host schema already in widespread or general use for markup of narrative documents? By viewing the Cover Pages, there appear to be many software projects to do TEI. Fifty-six organizations are members of the TEI Consortium. The TEI web page references packages for working with TEI in the following systems: Gnu Emacs oXygen (a general purpose editor) Open Office Softquad's XMetalXSLT style sheetsAnastasia (a general purpose XML publishing system and database) that is being marketed heavily at the TEI Community. It is a sourceforge open source project. a full-text search facility called PhiloLogic from the University of ChicagoThe Versioning Machine from the Maryland Institute of Technology. Specialized packages exist for converting "well-structured Word Documents" to TEI and going from TEI to latex, HTML, PDF. Are the already developed applications that Will make it easy of for organizations to implement the TC's specification based around the host schema? See above. Is there any reason to expect that the host schema will prove any particular advantages in gaining market support. The TEI standard does have some adherants with 123 projects on their web page. However, they are mostly projects concerned with traditional scholarly research and academic work. (The Cover page for the TEI is categorized under "academic.") It has been supported by the United States National Endowment for the Humanities, the European Community, the Mellon foundation, and the Social Science Humanities Research Council. Does the host schema provide any other advantages for use in the TC's specification? Norman Walsh and others reported at XML Europe 2004 on an effort to integrate TEI and Docbook. Does the host schema have any other disadvantages that make it undesirable for use in the TC's specification? There is a special charge to obtain the specification for the full TEI standard as PDF. The HTML version is less convenient.