Nature of Defect: The ordering of the names X1 ... Xn is not specified, and
there is no natural way to specify it. Hence this 'mapping' is
undefined, and hence the CLIF semantics is undefined, for
the guarded quantifier construction.
Solution is to remove the 'guarded quantifier' construction
from the CLIF specification in Appendix A. This solution
was arrived at by a clear consensus among the technical
committee which designed the specification. The guarded
quantifier construction is currently the subject of on-going
research, is not required by the main CL spec and has not
been implemented or used by any known CLIF project.
Proposed Solution:
(a) Delete lines 4 and 5 from table A.2 on page 31
(b) In A 2.3.8, page 29: remove the words "and may be guarded;"
(c) In A 2.3.8, page 29: remove the option “[ interpretablename ]” from the first production
(d) In A.1, page 24: remove item 11.
Submitter: Pat Hayes
References in Document: p.31
Nature of Defect: The ordering of the names X1 ... Xn is not specified, and there is no natural way to specify it. Hence this 'mapping' is undefined, and hence the CLIF semantics is undefined, for the guarded quantifier construction. Solution is to remove the 'guarded quantifier' construction from the CLIF specification in Appendix A. This solution was arrived at by a clear consensus among the technical committee which designed the specification. The guarded quantifier construction is currently the subject of on-going research, is not required by the main CL spec and has not been implemented or used by any known CLIF project.
Proposed Solution: (a) Delete lines 4 and 5 from table A.2 on page 31 (b) In A 2.3.8, page 29: remove the words "and may be guarded;" (c) In A 2.3.8, page 29: remove the option “[ interpretablename ]” from the first production (d) In A.1, page 24: remove item 11.