Automatic External Categorization

I like categories, ItWorks. - Since the idea exists that a person's information can be most useful, when personally and properly managed, it follows that a template for this management will necessarily be highly personalized. With the number of InformationConsumers? numbering in the Billions, it is further unlikely that a site, a series of sites, or the internet as a whole will contain, organize and store the information in such a personalized form. A comprehensive, individual information management schema and the mechanics for Building and Maintaining Information within it will most efficiently be done External to the Site Servers. While General Categorization and a site organization might already exist, how to make each the site additionally and alternatively useful for groups of users can also be done at another UserLocale?.

Using HyperTextTechnology?, the combination of ManualCategorization?, ExistingCategorization? and AutomaticCategorization? based on content and context, and the establishment HyperTextualStructures? which can be utilized via procedures, processes or programs existing at the UsersDeskTop? is not only feasible, but imperative. In my case, tools to do this are being constructed as the accumulation is in progress.

Much of the frustration of finding pertinent information can then be minimized.

Not that I had a problem with it, but this sounds somewhat like WoodenLanguage.

External (to wiki, to internet) categorization and storage of an individual's information, by an individual, on an individual's own computer, created with a feature allowing it to be shared with others, is PolarOpposite? to that described by "WoodenLanguage". It is bottom up, not top-down. If it must be classified, let it be a part of WoolenLanguage, a WorkingSeries?. It is presently in the process of creation and utilization, non.FinishedGoods?, using Artifacts, Artifactories, WikiWords, WordLinks?, and IdeaSpaces?, written in the English language.


RE: Since the idea exists that a person's information can be useful, and must be managed, it follows that a template for this management will be highly personalized.

Q: How does that follow? The information may be personal, but I don't see how that implies the management of that person's data will be personalized even a little bit (much less 'highly').

A: firstly It is not implied, it is PersonallyOrganized?: (work is involved)

A: secondly A: thirdly RE: First, Secondly, Thirdly...

I still don't see how any of this is implied. InformationUnits? could just as easily be AutomaticallyOrganized?, GenericallySelectable?, have common solutions for security and composition and accessibility, and focus on Automatic Placement (AutomaticVsManualPlacement) with little support for customization other than, possibly, stylistic composition (akin to CSS or XSLT transforms). I tend to see these options as highly preferable (in terms of computation properties for composition, common implementations of browsers, common support for subscription and level-of-detail, ability to share data and views of data, etc.) to PersonallyOrganized?, PersonallySelectable?, and fully customizable display of data.

A: It is not implied! it involves either personal work or the use of applications (either third-party, or personally-developed) to make it so ItWorks!


The idea of automation and externalization of categories and many, if not all other components and attributes of the StoredInformation?, is to allow for its becoming personalized, according to a personally derived organization.


RE: it is further unlikely that a site, a series of sites, or the internet as a whole will contain, organize and store the information in such a personalized form

I must disagree with this assumption. I believe that it is very likely that sites, series of sites, and the Internet as-a-whole will eventually be tooled to support multi-directional mobile code (both from browser->server and server->browser), which in turn will result in a whole new approach to portals, mashups, and web-applications. The use of mobile code will give rise to 'agents' in the cloud that subscribe to, maintain, and organize data for individual users, and have this data prepared for rapid access even across sessions and disruptions. These 'views' will likely be composable in design, such that one can create new views from older ones, inheriting the filters, compositions, stylizations, and so on. This allows primitive data sources to become automatically organized into many personal and shared views, and also allows views (personal or otherwise) to be shared in a standard manner. (Related: DocumentDefinitions.)

Will be tooled to support suggests methods, structures, and mechanisms a person may use, being highly and strictly structured requiring the user to apply techniques and machinery designed, maintained and controlled by others in a "cloud" environment, which can and will be changing and changeable by others and which may not be counted on to serve in the way the person intends.

Inheriting the filters, compositions, stylizations, suggests that they will fit the filtering, composition and style needs of the individual using them. Personalization and personality are unique, not general. Since such a system is dependent on a design created to store, organize, and contain data to be shared in a standard manner presumes knowledge and context the server assumes to be personalized. Assumption when it comes to personal items, does not equal intention. Assumption will be found to provide the user with what has been said and not what is now intended. (Don't do what I say, Do what I mean)

In a personalized system, the user may choose, as I have on occasion, to store personally and potentially interesting items in other forms and formats than those in which it is served. One has but to look at the source of a web page to see why such conversion and interpretation is required. The page is formatted primarily to affect its presentation, not necessarily what it contains a person may find of informative use and desires to store and maintain is a personally designed and structured base.

{I'd like to see that sites and the internet as a whole [...] will be tooled to support multi-directional code. But I fear that is a long way off. So until that point is reached a personalized local store would prove useful. But even then will local storage of artifacts (caching), local indexing of sites and artifacts and in general local optimization of access paths for the user bring enormous processing benefits. Call it partial evaluation of the users usage patterns. A site cannot do that efficiently alone.}


I had a thought about this again today : Why not use AEC as a component of the WoolenLanguage on your desktop to ''organize, characterize and categorize your own take in a WorkingSeries?, on things related by creating shortcuts within personally named and organized folders and subfolders. In this way you can not only categorize, but also sub-categorize pages, not only from wiki, but from most other sites on the internet.

-- DonaldNoyes.ReVisited?.20100918.20121030.20131001.20140828


Related:


CategoryInformationManagement CategoryCollaboration CategoryOrganization


EditText of this page (last edited August 28, 2014) or FindPage with title or text search