Since tagLinks are in their eleventh hour, and are starting to appear from otherSources, I guess it's time for me to elaborate on some of my concepts behind them. Bear with me because I haven't accumulated all the appliedTechnologies or hackedCode enough to make tagLinks work as envisioned. I'm just trying to stick my foot in the door by going on record to make it harder for someone else to lawyerUP and force me to abandon my own concepts. My intent is to leave the concept openAccess and to keep any codeProgramming openSource.
I started thinking about tagLinks as soon as I run into the concept of socialTagging. I, like most, was already familiar with the antiSocial variety gangMembers and outLaws use. I first related all this back to keyWords, like in indexes or fireFox bookMarks.
What the hell are tagLinks anyway? Well,.. they should be serial recursive digitized symbolic expressions of every possible aggregated iteration of themselves. Clear enough? How about them being selfDefined and user refined?
O.K... They're mostly words and always wordZ that are usually expressed in camelCase, but with lowerCase firstLetters likeThis toSignifyTheDifference. And work as wikiPageTitles. Words, as we all should know are essentially defined and evolve by consensus, having dictionaries, lexicons, thesauri, and encyclopedia that keep track of their meaning in context. On the other hand, tagLinks (wordZ) are intended to be symbolic of their function as a hyperLink as well as being descriptive of the content of the media they point to.
Typing "tagLinks" in this input box makes it a valid tagLink under my concept if doing a search on the combination of the symbols will return information relevent to and defining of or by the tagLink. I wanted tagLinks to be usable everywhere as names, headers, labels, variables, items, bookMarks, tags, titles, and soForth, but regrettably code syntax checking in some applications don't allow it.
tagLinks offered to you by iRobt.
