1) Discussion of terminology. a) selection (cf. guidelines) b) focus (cf. guidelines) c) point-of-regard. Is the selection? Or does it include focus and selection? Concern that an extra term will confuse users.

Ian: selection/focus don't occur often in this document, not worth
adding another term.

Paul: What do you want to use p.o.r for? Jon: E.g., we talk about moving
selection around and moving focus around (e.g., sequential nav). We could simplify. Focus has a specific meaning to developers.

Ian: Is the distinction useful?

Group: yes.

Ian: Not enough places in the document where are discussing "point
of regard" would be useful. Focus: a specific element that can
receive focus. Selection: may encompass several elements, even
not-continguous areas.

Ian: I hoped to remove the term DHTML from the doc. - Part of DHTML
that is not event driven - presentation is modified on the fly.

DD: Need a section in compatibility on support for DHTML. Problem: it's
not entirely based on W3C technologies. Several scripting languages
possible. W3C doesn't use the name DHTML (HTML+CSS+DOM+scripting). Which DOM (Level
0 or Level 1)? Either we discuss DHTML in the guidelines (even if not W3C-wide
definition) or we remove the term. - Say HTML under control of scripts
instead?

Ian: Yes, I want to refer to DHTML only parenthetically. Only refer to
scripts in guidelines.

DD: Probably put reference to what we mean by DHTML in compat section. -
Proposal to put in techniques document.

Jon: We need Page Authoring support as well. They have no reference to
DHTML or events in their guidelines or techniques. About all we can do now
is deal with events set explicitly on elements (and not event bubbling).

Ian: Re 4): How in the general case do you describe what happened? - This is the
problem. E.g., floating menu moves depending on what you're doing. - Add
component to browser: A narrative window. Tell authors to write scripts
that send descriptions of changes to narrative window.