HI!
H.L. MENCKEN : “The average man does not get pleasure out of an idea because he thinks it is true ; he thinks it is true because he gets pleasure out of it”
PABPRES is absolutely right in the reading of my fundamental intent : classification.
Instead of, like the rest of us, losing sight of the forest to look only one tree, he took the “integrated view”, and that allowed him to see the broad perspective.
When I answer “knot in general” it was about the very precise starting point of this topic we are inside just now, not about my deep intent.
Defining “in abstracto” what a knot can be is in my mind only a tool to be smithed. If it were not to make a tool it would be useless words juggling.
The real objective, the work, is “classification”
PABPRES took the larger view and rightly integrated 2 topics that are not really “separated”.
Thanks Roy, you put me on the right track again : I was so occupied looking at where I was putting my foot that I lost the way, with a bit of help here and there.
A bit of history : in fact 2 topics are on “classification”
I started “can of worms : naming knots”. In it is evoked the probleme of a “knot individual file” (KIF here after - I think it was another acronym I used previuosly, will have to “clean” that) to make a sort of database.
inside this topic Dan_Lehman asked about what is a knot ?
That made me start this topic : defining knot .
Not a new thread in fact, only a paragraph following the first one, in the general topic : classifying knots. They should be read, as PABPRES seems to have done as two paragraphs in the same chapter.
I then met, thanks to Fairlead with FCB who shared his ideas which much precede mine. ( see his documentation on my web space :http://tinyurl.com/cwf3f
While trying to precise my thought I found the H & L , again only a possible tool.
That sent me on further “things to be put” in the so-called “knot individual file”
Thanks to PABPRES, I now recall what experience taught me : when one stopped “thinking” about the perfect way to do something, and actually “begin to do it”, things have a way to clarify themselves.
So I will work with a method I used with success quite a few times : "consider all problems solved and start!
If only for my amusement, I will go on, this time drafting a form for the KIF. May be I will propose it one of these days.
My current thinking starts from the point that "sameness" in knots depends on how one thinks about them. When working back stage, I frequently run into the situation where THIS knot holds up the back drop and THAT knot holds up the lights. But even though both this and that knot would have the same ABOK number, it is important that I recognize them as "not the same".
In my view you are not speaking here of what the knots “are” but what they are “used for”.
This distinction of function is more important than the difference in nature/name/whatever in the situation you speak about.
Nothing to do with the knots which here are only an “epi-phenomena” to the "rope needing to be used in view of getting “that effect”
On a different level, as I mentioned before, seeing a 3-strand Matthew Walker and a 4-strand MWK as the same is valuable at times.
They are not the same, I insist.
But I aggree that one can "view" them , momentarily and knowing it is in error, on a "practical" plane as : "they have the same recipe" Sure that is a useful "tool" to see them as such. ( See Jimbo)
My current thinking is that, given two knots A and B, consider the set {A,B}. The various relationships that {A,B} has to the rest of knotting are more important that how many elements there are in {A,B}. Those relationships change with the interests of the knotter. I realize that this sounds very stilted and incomplete. Which reflects the state of my current thinking.
If one is to tell someone "Oh no, those are different knots", it is important to include how the knots are different and why the difference is significant. In many cases, the difference can be ignored for the use to which the knots are to be put.
That was why, while FCB is thinking, (and did a real start), along the lines of a linear hierarchical classification akin to the one Linneaus created and that was used for so long, I would rather think more along the lines of “cladistic” classifying.
Allow for “fuzzyness” and “emptiness” that the linear do not allow.
About cladistics ( not heavy reading if really interested in subject):
http://www.ucmp.berkeley.edu/clad/clad1.html
…Cladistics is a particular method of hypothesizing relationships among organisms. Like other methods, it has its own set of assumptions, procedures, and limitations. Cladistics is now accepted as the best method available for phylogenetic analysis, for it provides an explicit and testable hypothesis of organismal relationships.
The basic idea behind cladistics is that members of a group share a common evolutionary history, and are “closely related,” more so to members of the same group than to other organisms. These groups are recognized by sharing unique features which were not present in distant ancestors. …
http://www.ucmp.berkeley.edu/clad/clad5.html
http://www.gwu.edu/~clade/faculty/lipscomb/Cladistics.pdf
http://www.med.nyu.edu/rcr/rcr/course/phylo-cladistic.html
http://en.wikipedia.org/wiki/Cladistics
I will NOT discuss the merits/demerits of cladistics. At this stage my thinking is not “practical”, only “theorical, on principles”.