Content Representation With A Twist

Showing posts with label tagging. Show all posts
Showing posts with label tagging. Show all posts

Tuesday, June 26, 2007

Reorganizing Tags -- For What Benefit?

Having in sight to get over the core MOM reorganization obstacle and get reorganization implemented, as well as having noticed a possible benefit of having only//just//at least a reorganizer at hand (i.e. without any reorganizer) [aside of the benefit of becoming able to develop a more sophisticated recognizer then], I begun thinking about whether there might be a chance to make some profit by providing the MOM reorganizer as a web service.
 

Still unknowingly about any profitable such web service, I ended up with looking up 'tagging' in wikipedia. Which might be worth a read, same so for the German variant of that very article [for those of you comfortable with that language].

      
Updates:
none so far

Sunday, June 24, 2007

Made the ancient postings accessibly by tags

Tagged the early postings of this blog to let it make provide more benefit, e.g. by enabling every reader to pick up topics by tags -- and then get all the posting on that very topic I posted here, so far.

Positive side-effect of that effort is that also for me, in future, it might become more easy for me to set up backward references to earlier posted articles and yet tackled subjects. Such as for the still under-constructional posting on obstacles of traditional notion organizing systems MOM overcomes.


      
Updates:
none so far

Monday, June 11, 2007

Tag users

Google demands its adsense users to choose some trigger keywords/phrases. If they match a search of a Google user, the advertiser's ad might get displayed.

If the user clicks any such ad, they show interest in the topic of the ad, outlined by the trigger keywords. -- So, if one (or Google itself) were after to figure the interests of a user, Google could take these keywords and tag the user with them. -- The Google cookie one gets practically everywhere in the web, expiring in 2037, provides a unique handle for the user, for a long time. (And I really wouldn't wonder if they'd track 90% of all web users, individually.)

On the other hand, whenever a user enters a page featuring Google content, the user might become identified by their cookie. If Google is about to place ads on that site, by the cookie ID, Google immediately could figure the fields of interests of the visiting user. Also, immediately, it could update the user's record, since by visiting the page Google knew another bit about that user: He's likely interested in the topics dealt with on the page just entered. -- Which either the advertising real estate provider reveals by tagging its own page or which Google might do itself by traditional information science approaches.

Then, Google could select any ad that matches the user's profile and render it to the page currently being put out/the user is waiting for that it finishes rendering.
 

Is there a way to mimic that approach to gather tags of tags?

      
Updates:
none so far

Monday, March 05, 2007

Chances of the MOM project

Despite the MOM project does not strive for helping out neither the tagging approaches nor those of the Semantic Web movement, MOM probably can help both. And, other way round, both probably could provide some good to the MOM project.


      
Updates:
none so far

Wednesday, February 21, 2007

About the Simple Set Core

The Simple Set Core project is about a set engine. Aim of this set engine is to recognize ("identify") items -- sets of features -- by only some of their features, to store these items and their features recursively as directed graphs, and to reorganize these graphs so that as well implicit items/features become visible as the graph as a whole becomes less dense, thus more easy to handle.

Background

The set engine is part of a larger project, the Model of Meaning. Its approach is that notions ("meanings") consist of smaller notions (or raw data like "light sensed"). Different but common approaches, the Model of Meaning drops the familiar "is a" relationship between things: The assumption of the model is that, despite a car is a kind of a vehicle, a vehicle is a part of the car. -- At first glance this is hard to comprehend, but isn't it so that you are just thinking of the car and the vehicle? Then, both are not physical, thus there is no physical problem of "cramming" a just imagined vehicle within a car. Which also is just imagination.

Benefit For The Web

Having the Model of Meaning in mind, the set engine alone can do the web a big service: If tags would be related to other tags by "is part of" relationships, first, the tagging folks could quit to mention implications, second, the people searching for content could get the matching content even when looking for low level implications of the very content.

Perspective

Also, if there is a way to recognize items by just parts of their features, tag graphs could be integrated with each other, automatically, simply because the items mentioned in the graphs could be recognized by their features also; and, dropping the tags, replacing them by notion identifiers ("IDs") where the tags become attached to, maybe that could overcome even the language barrier, once and for all.

      
Updates:
none so far

Monday, June 28, 2004

[Merged from (the now removed) ia: organizing notions:] If Google didn't get the idea it's just standing in front of understanding it. Using labels in GMail is a nice thing, but it results in many, many individual labels.

To apply them to mails will get quite inconveniently. Currently Google's using hot keys inside its gmail service, meaning that pressing a 'c' (for example) leads me to the "create new mail" screen. This intereferes a bit with the convenient use of a drop down box where you normally can use the first letter of an entry to navigate in the list.

To bypass that, someone could request for cascaded/stacked drop down lists, resulting in a kind of menu. There, for example, one could place all labels of interest within a bigger thread -- a mailing list for example. - But that's something Google cannot do since implementing such a concept would lead back to the monohierarchical folders concept. Therefore they have to find a way to keep such kind of menu polyhierarchically.

*snap* That's it. Then they'll get the idea.

The idea is, that a lot of things (but not all) can be identified by cascading labels -- or, further thought, features (that results in independence of language). But it has to be possible to order these features in a polyhierachical manner still. Then one can stack ideas. The name of a mailing list (or the "idea" of that mailing list) could be a feature of an individual mail sent by that list. Another feature of that mail could be the sender, cc recipients and so on.

Another case applies to the conversations, gmail is using instead of folders. One single mail can be part of different conversations - for example if one reader starts a new thread based on a mail that continues to be part of an earlier started conversation. Same problem as for the labels. -- I think, Google almost must get the idea.
 

Next obstacle: How to let gmail users access their gmail accounts by POP3 based mail readers? - One possible solution is to introduce a normally invisible field in the mail header, that contains gmail labels. Other freemail providers can adopt that principle -- then it may be used by a wide range of users. -- Maybe a possibility to fund on this to create a notion based search engine? -- I have thought about that some years, yet, but I've never had the time to really implement it. The few months between my last test and the start of research for my diploma thesis I used to just automatically generate an appropiate MySQL database. But after that I had to stop working on it, since making my diploma has a higher priority.

I'd like to hear from anyone who would be interested in implementing such an engine as an free software project with me together.<<




Updates: 20070624: Tagged the posting. Updated the posting style (layout) to my current style, such as using blockquotes when appropriate, more precise word picks, better grammar. Removed my workaround for backlinks blogger.com didn't support in earlier times. Now, backlings are there, therefore the bypass can be dropped.