Hi all around !
Yes Roy I had in mind to define
the knot
structure in a
general manner.( go back to different "mind map" in different languages)
I was not addressing this or that knot or bend or hitch ( those 2 last words are not "sense-bringer" in French for exemple).
But I understand what could have misled you, just like in English foxhunting ( you being the Fox of course) instead of the dogs taking it, it was the fox that followed that red herring ( to the confusion of the Hun): the repeated apparition of specific names.
My part in that was my proposing a method of "sequencing" with H&L and to examplify I had to specificaly evokes particular knots ( understand that in my French mind I can only use noeud/knot = knots + bend + hitches ), since it is to be applied to "real" knotS and not to "an ideal knot".
So you were not so much erring as having been mislead by, at least, some of the "how" it was argumented here and there.
But your "confusion" is to me less that the "constant" return of "loading, use/usage of knot so and so" in this particular topic.
I thought that I had made clear the following points
must have over-estimated my capacity to explain my thinking in another language than my own, so I will try one again. Sorry to be so repetitive, but I will try to keep it "short and to the point " at the risk of appearing curt and abrupt, and will not come at it again if I do not succedd this time, since I do not knos how to re-formulated it).)
- My main intention was
structure - construction - anatomy and
not function - usage - physiology - reasons for that were :
- arbitrary : my own inclination and mind map.
I tend to perceived "structure" well before I am sure of "function"
My "mind map" make me rather think that defining some "materialized" thing is rather
WHAT this thing is
first and foremost and only after ascertaining that, then I go to "what can I do with it" and "how I can" and "how does it works".
See, in French : only "knot" : structure, whereas as in English "knots, bend, hitch"....this already imply a "function"point of view as well as some aspect of structure.
- wanting to be reasonable :
- structure is usually more "apparent" and/or "evident" than function. (See history of "sciences of Life" : anatomy was knwon well before physiology, and usage of bodies in specialized tasks were in action without any physiological knowledge, just "imagined" 'how it works')
- structure is more "discriminating than "function". I mean : seing a structure you can infere more easily a function than stating a function and after infering a structure.
Or in other words : given a structure it will be easier to get several people to aggree to a function ( one among others posssible), whereas stating a function you will be more often hard put to get people to agree on one structure.
Preferences, opinions, preconceptions and so forth would be let loose, while they are "coralled" when you start with the structure.
Don't know if that comes out "clear"?
- structure being what you "get at first" is more helpfull, more discriminative, than the quite empirical"to what use it is put" which in turn is much more easier to know than the more difficult attempt at being "experimental and rigorous"
"how it works" as classification criterion
- Structure was to be only
one of many things ,not even the main heading.
That(heading) was to be something like an "identification number"to be put in what was imagined as the "personnal identification file for a knot".
That was "in the body" of the file that the "how it works" would be attended to.
- about, knots specifically, you have to "MAKE" it before "USING" it, and also you can put it to use ( not "advisededly" may be) without "KNOWING its inner working".
The time sequence of using a "materialized knot" begin with structure ; I understand that the "immaterial" part of the time sequence could very well be thinking about "function".
But in the phenomenal world the "structure" is the first to be made manifest. Or so I think.
I think ( yeah! bringing down open doors) that in "knowing a knot" there are at least two folds :
- may be a third that I put first : knowing "of" or "about" a knot
- First fold ,
structural: knowing how to lay the knot without any mistake, even dressing it properly. without fail, even under stress, as when in military training with dismantling a gun in the dark and putting it back to working order in the shortest time possible.
That small part of knowledge is what opens the door to "danger" since you can "materialize" the knot and put it to use.
- that lead me to the second fold ,
functional : knowing how, why, when, to use, not to use a knot, and in which sort of rope to cast or not to cast itand so on.
-----
- uses,
tests versus opinions or lore, internal working, how to cast the knot, different methods, different naming, indication, not-an-indication, contra-indication, in which rope to do or not to do it, remaining strenght in a rope ( to be clearly stated in nature, sizes....) with it..... were all conceived to be in the file not in the defining.
I quite understand that this individual file would be of no use if left at the defining of the structure.
But I would like the "logical planes" (structure - functionning - uses ...) be respected ( differentiated clearly) and not "opposed" one to the other(s) in "defining" THE knot.
...to be continued in next post...