These are SmallPages invoked by the LinkLanguage page.
Feel free to add to them, or break them out into their own (whole) page.
PrecisionDoesntBanishParadox
- “The idea that using a WikiWord somehow removes all ambiguity and all of the problems associated in the use of language ignores the reality of language.” – MurrayAltheim, LinkLanguage2004 (2004-05-05)
Precision does not banish the ParadoxOfExpression.
Precision can solve a paradox, perhaps even several paradoxes, but precision does not end all paradox, and there is paradox that cannot ever be resolved, no matter how much precision is applied. There is always a debatable angle.
Precision does not grant us immutable perfect forever PlatonicCategories. We may find something like them on the small scale, but that resolution can bubble up in irrelevance, like so much foam on the surface of the sea.
Don’t let the PostModern angle scare you, though – There are always things to understand, and precision and order, alternating ambiguity and chaos, is a tool of evolution – the EvolutionOfHumanity?, even. Don’t be like the people who doubt the spirit behind all thinking, and then the heart itself, and then – shrivel up and die. It’s a Darwinian cull. Let heart see and direct thoughts. Heart itself requires no explaining, though it’s amenable to conversation.
Recall the IdeasLikeStarsAndSymphonies; The process continues forever.
ComplexMessage
Is a complex message a message? It is; It’s an island of intended (or presumed) integrity and stability in a sea of chaos.
ArgumentRouting
to write
EvolutionOfHumanity
to write
NamingForLanguage
to write
WikiCoherence
to write
LinkSyntax
to write
ComputerAssistedLinking
to write
LinkLanguageCompressesToTagLanguage
Thesis…
- IF… Page names become the components of LinkLanguage and Acronyms are frequently formed from Page Names (e.g. Wiki:YagNi)
- THEN…
- Tags may evolve from compressing Page names (LinkLanguage) further to produce a (denser, yet) form of TagLanguage?.
- …
TagLanguage? considerations include…
- To become an effective language, Tags must become accepted to the point of facilitating effective communications by having commonly accepted meanings and values. Until this happens, Tag strings can easily be “over-loaded” with too many diverse meanings; making them ineffective.
- One solution is to make careful use of Tags within the relatively limited Audiences (communities) within which their meaning is recognized and well defined. Recognizing this these limited Audiences may be made up of as few as two people (an Author and a single member Audience), it becomes as simple as having the Author define the meaning of any particular Tag that is used with that specific Audience. Assuming that this simple, initial solution develops, it may quickly generate a relatively large number of Tags which will inevitably start to tax the ability of both the Author and the Audience to remember their specific meanings and uses.
- For tags sets that have reached a “significant” size, it quickly becomes apparent that…
- NameConventions? (patterns) can reduce the complexity.
- Individuals may have conflicting preferences for the personal meanings of Tags, making automated translations very desirable. One possible “limit” of this trend to “personal” tags is by definition, a single individual’s definition. However, there apparently are cases in which even personal Tag meanings are “context-sensitive”. hence, the design objective for such Tags should be to rely on Client-Side automation to infer effective meaning of a tag, based on the context-sensitive uses of both the Author and the (ideally each particular) Audience member.
- …
- …
- …