% ' FP_ASP ASP Automatically generated by a FrontPage Component. Do not Edit. On Error Resume Next Session("FP_OldCodePage") = Session.CodePage Session("FP_OldLCID") = Session.LCID Session.CodePage = 1252 Session.LCID = 1033 Err.Clear strErrorUrl = "" If Request.ServerVariables("REQUEST_METHOD") = "POST" Then If Request.Form("VTI-GROUP") = "0" Then Err.Clear Set fp_conn = Server.CreateObject("ADODB.Connection") FP_DumpError strErrorUrl, "Cannot create connection" Set fp_rs = Server.CreateObject("ADODB.Recordset") FP_DumpError strErrorUrl, "Cannot create record set" fp_conn.Open Application("comments_ConnectionString") FP_DumpError strErrorUrl, "Cannot open database" fp_rs.Open "Results", fp_conn, 1, 3, 2 ' adOpenKeySet, adLockOptimistic, adCmdTable FP_DumpError strErrorUrl, "Cannot open record set" fp_rs.AddNew FP_DumpError strErrorUrl, "Cannot add new record set to the database" Dim arFormFields0(3) Dim arFormDBFields0(3) Dim arFormValues0(3) arFormFields0(0) = "Comment" arFormDBFields0(0) = "Comment" arFormValues0(0) = Request("Comment") arFormFields0(1) = "Name" arFormDBFields0(1) = "Name" arFormValues0(1) = Request("Name") arFormFields0(2) = "Page" arFormDBFields0(2) = "Page" arFormValues0(2) = Request("Page") FP_SaveFormFields fp_rs, arFormFields0, arFormDBFields0 FP_SaveFieldToDB fp_rs, Now, "Date" If Request.ServerVariables("REMOTE_USER") <> "" Then FP_SaveFieldToDB fp_rs, Request.ServerVariables("REMOTE_USER"), "User_name" End If fp_rs.Update FP_DumpError strErrorUrl, "Cannot update the database" fp_rs.Close fp_conn.Close FP_FormConfirmation "text/html; charset=windows-1252",_ "Form Confirmation",_ "Thank you for submitting the following information:",_ "no_danglers.asp",_ "Return to the form." End If End If Session.CodePage = Session("FP_OldCodePage") Session.LCID = Session("FP_OldLCID") %>
The Rabbit and Holding Hands rules are special cases of a general principle: no danglers!
This simple argument currently has lots of danglers, in both the contention and the premises.
Two (previously hidden) co-premises have been added. Now there are no danglers; both Rabbit and Holding Hands are observed. For clarity, "Rabbit" lines have been omitted from the diagram. Notice how, now,
every significant term or concept appears in at least two different claim boxes
every claim box "holds hands" with two other claim boxes.
A dangler is something that dangles, i.e., hangs loose. A dangler is a significant word, term, phrase or concept which appears only once in a simple argument, without being "tied in" by also appearing somewhere else.
The No Danglers rule is equivalent to the Rabbit Rule and the Holding Hands rule combined. In theory you could forget the other two rules and just apply No Danglers. However we find that it works most effectively to treat them separately; first apply Rabbit, then Holding Hands.
The overall effect of applying these rules is a very tightly structured argument, in which all hidden premises have been made explicit. The No Danglers rule is a powerful tool for ensuring that we have all and only the right claims when we map a simple argument.
It is important to realize that these structure principles do not guarantee that the argument is a good one. They help make it fully explicit; whether it provides strong evidence is another question, one we can address more easily once these rules have been applied, but which brings further considerations into play.
The No Danglers Rule: every significant word, phrase or concept appearing in one claim (contention or premise) of a simple argument must also appear in another claim.
<% if 0 then %>
<% end if %>
fp_sQry="SELECT * FROM Results WHERE (Page = 'T2_no_danglers')"
fp_sNoRecords="no comments yet"
|Glossary | Contents||
Copyright © Austhink 2003-2006
Last updated 29-Nov-2006