This paper explores how to use the new [DOM Validation Interfaces] as the basis for a prompted editing tool. It looks at areas where these interfaces fall short of what may be required by such applications, and ways in which these shortfalls can be made good. It also examines ways in which implementations of these interfaces could provide support for validation against a richer variety of business rules than can be expressed in standard content model definition languages such as DTDs and XML Schema.