Checking the Designer’s XHTML Sample Clauses

Checking the Designer’s XHTML. When the designer has created a template directory T , it may be checked against a given contract directory C. First, some simple local checks are performed: • corresponding to §1, the template directory must have the same structure as the contract directory, and each template file must contain a wellformed XML document; and Main inventory buyform Inventory Selection items ε items Product price items

Checking the Designer’s XHTML. ‌ When the designer has created a template directory T , it may be checked against a given contract directory C. First, some simple local checks are performed: • corresponding to §1, the template directory must have the same structure Main inventory buyform Inventory Selection items ε items Product price items <AnyString> <AnyString> as the contract directory, and each template file must contain a wellformed XML document; and corresponding to 2, each template file must contain the gaps, forms, and fields that are mandated by the contract. What remains is the global check that all pages P conform to the XHTML 1.0 specification, corresponding to 3. This is done by constructing a summary graph GP,C,T such that L(GP,C,T )= L(P, C, T ) and using JWIG to check validity against the appropriate DSD2 schema. The construction is straightforward, since contracts are essentially abstract summary graphs. We simply use the designer’s templates as summary graph nodes, the edges and roots are read directly from the contract, and gaps that are marked by “?” in the contract become potentially open in the summary graph. As an example, the product inventory page contract from Figure 2 is con- verted into the summary graph shown in Figure 6. In this figure, we omit the template constants that are associated with the nodes; one of the three different sets of template constants shown in Section 4.1 could be used here.