<FORM ACTION="AuthorForm" METHOD="post">
</FORM>Of course this Form is a little boring since it has no input elements. The ACTION string, "AuthorForm", will be seen as the Form Name in the Activator Selector. After this is bound as an Activator, the Fragment will look like:
<FORM ACTION="http://cezanne/cgi-bin//ex.cgi" METHOD="post">
<INPUT TYPE="hidden" NAME="SaFormName"
VALUE="GroupBy__Fst_html">
</FORM>Sapphire/Web changed the action value to the URL of the CGI, added a hidden element with the name, "SaFormName", and a value of "GroupBy__Fst_html". The Element name is used by Sapphire/Web CGIs to lookup the value "GroupBy__Fst_html". This value is used to look up the Activator Function for the Form. The look up, registration, and dispatching are exactly the same for Anchors. Instead of "__A" sandwiched in the middle to derive the lookup string, "__F" is used. So in the same HTML file, Anchor names must be unique and Form names must be unique¯but a Form and Anchor could have the same name.
For Forms you get arguments from Input Elements. In the contrib/html and config/styles directories of Sapphire/Web there are a number of files with different kinds of HTML fragments. These files will show different Form Element Constructs and other HTML pieces.