This evaluates: Host Schema Candidate Does the host schema use a generic structural markup model? Does the host schema define a "clause" object? Does the host schema define a paragraph level object that represents a structural or grammatical paragraph? Using the host schema, can the clause equivalent object be inserted at arbitrary levels in the document hierarchy without transformation? 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? Does the host schema provide a mechanism to add semantic information about: whole documentsdistinct objects,such as clauses, within documents? If so, is the metadata model for the host schema sufficient for contracts or will it be necessary to extend it? Does the host schema allow embedded values to be represented and semantic information to be added to these values? Does the host schema require use of a particular processing technology? Does the design of the host schema preclude use of particular currently available processing technologies? Does the host schema permit the numbering of clauses, paragraphs, lists and other objects to be represented in the markup? 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? 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? Does the host schema represent the relationship between all significant components in a way that allow high quality print and web rendition of of contact documents? Does the host schema include a mechanism for defining variables for embedded data values? If the host schema does not include such a mechanism, is there any obstacle to adding it? 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)? Is the host schema a DTD only or can it also be expressed as an XML Schema or other schema type? Does the host schema provide for the complete representation for the distinct structures commonly found in contracts? If not, does the host schema explicitly allow additional distinct structures to be added? 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? 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? Is the host schema already in widespread or general use for markup of narrative documents? Are the already developed applications that Will make it easy of for organizations to implement the TC's specification based around the host schema? Is there any reason to expect that the host schema will prove any particular advantages in gaining market support. Does the host schema provide any other advantages for use in the TC's specification? Does the host schema have any other disadvantages that make it undesirable for use in the TC's specification?