Part 1
PLEASE Dear WebMistress if too cluttering then delete and no hard feelings on either side.
errors on knots names does not matter. Sure!
Just as punctuation is not a matter of life and death but try this one : Eats shoots and leaves.
try it with and without punctuation variations. See what I means.
Opening statements :
I am interested in knots inasmuch that they are tools.
Tools should not be mislaid/mistreated/misused/mislabeled/misclassified/mis-whatever-you-can-think-of
Philosphy ?
Naming is charting the world.
Unambiguous - Univoque naming is mandatory to avoid mistake and make the world predictable and others’s actions predictable ( well hopefully!)
Univoque : “A” imply “B” and only “B” and “B” imply “A” and only"A"
Unambiguous is the second best ( see down the about “rose” in French) for that if you cannot have univoque relation then you fix the context to try an get ambiguity out of the equation parameters.
Lineus made the world more "readable"with his classifying method.
Why not follow the same road.
Not that I count me a knot expert, not by leaps and bounds, but men like Dan_Lehman just to throw the name of someone who answer one of my post could certainly apply for he job, and I have no doubt that the ressource pool of IGKT can bring many other minds to bear to the task.
You can only usefully interact with someone that share the same “mind map”.
Or beware : Babel Tower effect as I call it is guaranteed.
If you have a different mind map from the one I hold in my mind ( that is quite enjoyable for fun purposes, but certainly not for practical purposes.) then we will be hard put to interact on or about something.
An agreed set ( fixed, but modifiable upon common agreement) frame of reference is mandatory not to be at crossed purposes.
Yes I know " A rose under any…"
Sorry but that will be half in French.
Out of hand or rather out of brain I cannot think of a working illustration in English
Rose in French invoke a sort of flower ( en fact flowerS as they are quite a lot of cultivars : rose) but also invoke the wind quarters on a compass card, it invoke a colour (pink) , it invoke a make-up powder and the devil kow what else.
If I ask you out of context to give me “la rose” ( la is female) you will immediatly know it is not “le rose” (le is male) be it the make-up or the tube of colour ( color to you Americans), but you will be hard put to know if I want the flower or the compass card.
See the necessity of the agreed frame of reference and context to offset ambiguity.
You can act with “raisonably repeatable predictability” only by strictly narrowing the “shared mind map meaning” of what wathever information ( here the concept you want to express), and that can only be done by agreeing on the “wording code to use”.
Hence the old sails Navy “manuals” insistance on the strict use of names and procedures : only by doing so could safety, security, efficeiency, repeatability, coordinated action. I have not read any of the modern days Navies manuals but I strongly suspect they are only more insistent on those points.
Yes I agree the “set of rules” were not the same from periods to periods of time, from US Navy, toRN Navy ( UK), toRN Navy ( French Navy of old, and now still nicknamed “La Royale” ( The Royal), to Spanish Navy… But inside the set of reference agreed upon the “rules” strictly applied.
Why have an IGKT
Why have an IGKT worldwide organization with all its ressources pool if not for ( among other things) setting a commonly agreed unambiguous-univoque frame of reference.
Or are we just members of another social club with not other use than pleasure and passing the time of the day or the night waiting either for Death or Santa Clauss, depending on one’s beliefs.
My interrogations
How one can hope to retrieve (fast, sure, unambiguous, repeatable retrieval) data without a pretty severe procedure?
How to be sure we are all speaking of the same thing if naming is the pleasant haphazard stratification of passed lore.
Or I am missing something?
What I feel when I find a published/public error (apply not only to knots):
When I find, in a book or on a site, a fault that I am able to diagnose, I always wonder how many more there were that I was not able to detect.
And I suspect that I am not the only one having that response to “error found” flagging.
After that I am quite like the proverbial scalded cat.
If there is only one reason to weed out errors it is because they throw discredit on the rest of data, and make it easier to throw the baby with the bath : after one or two error you cannot really feel sure that you are not reading assinine misinformation.
If only for keeping the rest of data safe, errors/mistakes must be “cleaned out” or at least “flagged”.
What I do not adhere to :
-The idea that a new use for a structurally known knot make one new knot worth of a diffrenet naming.
In my book and training that is faulty thinking on logic ground.
Ockham would not be pleased. Not the strictest economy of means.
A knot is a “structure” that can be described and indexed ( or there would be no possibility of a mathematical theory of knots). and that is this least common factor that should be indexed in an univoque manner.
You can always add whathever naming appellations after that, provide they are always linked with the “unique” identifying tag.
-That error in naming are of no consequence.
Too many great mistakes ( killing and sometimes mass-killing ones ) were made only because 2 persons were not using the same fixed and agreed frame of reference, that begining with name.
-That we should not “change one iota to the biblical knotting lore” ( not alluding to ABOK here but to the total world production concerning books, dvd, web site since the Sumerians to today!)