Common use of Obligations of the HTML Designer Clause in Contracts

Obligations of the HTML Designer. The semantics of a contract is divided into two parts corresponding to the obligations of the HTML designer and the programmer, respectively. We first consider the HTML designer: §1. The designer must build a template directory structure matching the con- tract directory structure, such that there is one file a/b/c/T.xml contain- ing a wellformed XML template constant for each template T with package a.b.c in the contract. §2. Each template must contain the right occurrences of gaps, fields, and forms. This means that a gap named g must occur at least once in the template if and only if the corresponding templatedeclaration contains a gap descriptor with name g . Similarly, input fields must occur according to the field descriptors and their associated FieldCardinality , and the template must contain one form for each form descriptor, such that the FormName matches the name attribute, if present. Recall that gap and field descriptors are allowed both at the same level as form descriptors and nested within them. The gaps and fields in the XML templates must adhere to the nesting structure used in the template declaration. §3. All pages that can be derived from the contract and the template constants must be valid according to the XHTML syntax. The set of pages L(P, C, T ) that can be derived from a page description P of a contract C and template constants T is defined as those pages that can be obtained by starting with a root template of P and recursively plugging all possible templates and strings into the gaps according to the contract. For example, if contractroot and templateroot denote the contract root directory and the template root directory, respectively, using the first design from the example from Section 4.1, then L(shop.inventory.MainPage, contractroot, templateroot) contains the HTML code for the first page in Figure 4, together with the in- finitely many other pages that have a Wrapper template outermost, a Main template plugged into its body gap, etc.

Obligations of the HTML Designer. The semantics of a contract is divided into two parts corresponding to the obligations of the HTML designer and the programmer, respectively. We first consider the HTML designer:: § §1. The designer must build a template directory structure matching the con- tract directory contract direc- tory structure, such that there is one file a/b/c/T.xml contain- ing containing a wellformed XML template constant for each template T with package a.b.c in the contract.. § §2. Each template must contain the right occurrences of gaps, fields, and forms. This means that a gap named g must occur at least once in the template if and only if the corresponding templatedeclaration template declaration contains a gap descriptor with name g . SimilarlySimi- larly, input fields must occur according to the field descriptors and their associated FieldCardinality FieldCardinality, and the template must contain one form for each form descriptor, such that the FormName matches the name attribute, if present. Recall that gap and field descriptors are allowed both at the same level as form descriptors and nested within them. The gaps and fields in the XML templates must adhere to the nesting structure used in the template declaration.. § §3. All pages that can be derived from the contract and the template constants must be valid according to the XHTML syntax. L The set of pages L(P(P, C, T ) that can be derived from a page description P of a contract C and template constants T is defined as those pages that can be obtained by starting with a root template of P and recursively plugging all possible templates and strings into the gaps according to the contract. For example, if contractroot and templateroot denote the contract root directory and the template root directory, respectively, using the first design from the example from Section 4.1, then L(shop.inventory.MainPage, contractroot, templateroot) contains the HTML code for the first page in Figure 4, together with the in- finitely infinitely many other pages that have a Wrapper template outermost, a Main template plugged into its body gap, etc.

Obligations of the HTML Designer. The semantics of a contract is divided into two parts corresponding to the obligations of the HTML designer and the programmer, respectively. We first consider the HTML designer: §1. The designer must build a template directory structure matching the con- tract directory structure, such that there is one file a/b/c/T.xml contain- ing a wellformed XML template constant for each template T with package a.b.c package a. b.c in the contract. §2. Each template must contain the right occurrences of gaps, fields, and forms. This means that a gap named g must occur at least once in the template if and only if the corresponding templatedeclaration template declaration contains a gap descriptor with name g . Similarly, input fields must occur according to the field descriptors and their associated FieldCardinality FieldCardinality, and the template must contain one form for each form descriptor, such that the FormName matches the name attribute, if present. Recall that gap and field descriptors are allowed both at the same level as form descriptors and nested within them. The gaps and fields in the XML templates must adhere to the nesting structure used in the template declaration. §3. All pages that can be derived from the contract and the template constants must be valid according to the XHTML syntax. The set of pages L(P(P, C, T ) that can be derived from a page description P of a contract C and template constants T is defined as those pages that can be obtained by starting with a root template of P and recursively plugging all possible templates and strings into the gaps according to the contract. For example, if contractroot and templateroot denote the contract root directory and the template root directory, respectively, using the first design from the example from Section 4.1, then L(shop.inventory.MainPage, contractroot, templateroot) contains the HTML code for the first page in Figure 4, together with the in- finitely many other pages that have a Wrapper template outermost, a Main template plugged into its body gap, etc.

Obligations of the HTML Designer. The semantics of a contract is divided into two parts corresponding to the obligations of the HTML designer and the programmer, respectively. We first consider the HTML designer: §1. The designer must build a template directory structure matching the con- tract directory contract direc- tory structure, such that there is one file a/b/c/T.xml contain- ing containing a wellformed XML template constant for each template T with package a.b.c in the contract. §2. Each template must contain the right occurrences of gaps, fields, and forms. This means that a gap named g must occur at least once in the template if and only if the corresponding templatedeclaration template declaration contains a gap descriptor with name g . SimilarlySimi- larly, input fields must occur according to the field descriptors and their associated FieldCardinality FieldCardinality, and the template must contain one form for each form descriptor, such that the FormName matches the name attribute, if present. Recall that gap and field descriptors are allowed both at the same level as form descriptors and nested within them. The gaps and fields in the XML templates must adhere to the nesting structure used in the template declaration. §3. All pages that can be derived from the contract and the template constants must be valid according to the XHTML syntax. The set of pages L(P, C, T ) that can be derived from a page description P of a contract C and template constants T is defined as those pages that can be obtained by starting with a root template of P and recursively plugging all possible templates and strings into the gaps according to the contract. For example, if contractroot and templateroot denote the contract root directory and the template root directory, respectively, using the first design from the example from Section 4.1, then L(shop.inventory.MainPage, contractroot, templateroot) contains the HTML code for the first page in Figure 4, together with the in- finitely infinitely many other pages that have a Wrapper template outermost, a Main template plugged into its body gap, etc.