Content Representation With A Twist

Showing posts with label diploma thesis. Show all posts
Showing posts with label diploma thesis. Show all posts

Saturday, March 04, 2006

terms confused

In my previous posts [1] I attempted to describe the problem, approaching from the information science point of view. I developed MOM since my very first semesters of my course of studies, so that I already dropped the usual information science approaches of organizing information when I were taught these. Hence I am not strong in these. Having to research on thesauri for my diploma thesis was a problem, but to avoid to let it become a problem for the thesis' assessment I took strong web research to get the thesaurus terms and implications clear. That effort was honoured by an A (i.e. excellent) rating for the thesis. But it also leaves the gaps relating to other kinds of term organizing ontologies and terminologies.

For you readers of this blog, I attempted to guide you from any kind of term organizing ontology to MOM; but in fact I am not firm in the fields of ontologies. So, I likely confused the terms. I researched to get the terms clear, but all I found was that the terms as is are treated to be not clear yet. So my only hope to get a clear approach would be to ascertain the currently most preferred set of definitions of the terms mentioned.

But since I am seeking a job, I don't have that much time as I would like to have to perform such a research/retrieval approach. So I drop this approach for now. If you can define the terms involved, I would greatly appreciate, if you would contribute any of the definition(s) in the comments of this post or any of the previous ones!


[1] referred previous posts: <<


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.


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.

Saturday, February 18, 2006

From the Information Science local point of view

Information Science and its predecessor sciences like documentation or library science tackle one big problem in information: stay able to retrieve pieces of information once stored.

In ancient days the pieces of information mainly were material, i.e. not computer-indexable. For example, books were such a kind of material.

Common approach from the information science point of view is to associate each of the books with a set of keywords: When you want to retrieve one of them later, you go ahead, choose some of the keywords, and lookup them in a catalogue which itself refers to the books itself.

To be able to handle this all, you need at least three kinds of storage:
  1. a storage for the books, e.g. a kind of library, organized in a way to stay able to at least locate the shelf a particular book is placed in
  2. a storage for the catalogue
  3. and, most important: a storage for the keywords.
The keywords theirselves have to be stored somewhere. If you neglect this part of the task, one day you will apply this keyword to the book and another day another keyword, but both meaning the same -- i.e. are synonyms.

So, what result originates from that?

Assumed you associated two contently very similar books X and Y with two synonymuos but different keywords, A and B. One day you want to know something about a topic that is covered by both books X and Y, but you don't know about that. You directly go to the catalogue. You pick up a search keyword that accidently fell into your mind. Say B. You look up the appropriate catalogue card and find Y. -- That there's a closely related X book you don't even get aware of. So you fetch the Y book, but the X book remains in shelf. Possibly it would have been valuable to find X as well.

Therefore keywords get stored theirselves too.


The main goal of a keyword storage is similar to the other pieces of information storages: To stay able to find the wanted contents, i.e. the keywords -- and to find exactly the keywords wanted. "Keywords wanted" are those that might be applied to one or more books.

The appropriate tool for keyword or, more precisely, term (as in "search term") storage is a terminology. It mentions every word that was applied to at least one piece of information -- e.g. book -- of the pieces of information storage -- e.g. library. (In a converse, to keep administrative workload small, there's the suggest to choose only keywords already listed in the terminology, to associate books with.)


In a simple case, a terminology might be an alphabetical list of terms. For each of the terms it offers an orientation help: Usually there are broader and narrower variants of terms: a mammal is treated to be broader than a dog or cat or cow or horse or something else which is a mammal. (In fact, terminologies refer to items but list the labels of these.)

So, a terminology offers is a relationships to identify the location of a given term in the whole terminology. Less common than is a are has a relationships, like the ones applied between car and something like wheels, motor, front window, doors etc. These kinds of relationships are called hierarchical relationships.

My diploma thesis was about the thesaurus kind of terminology, so I currently I am not sure if this applies for the classification kind as well: There is at least one more kind of relationship -- the associative one. It relates terms at each other that don't belong to a hierarchical order, but somehow have something to do with each other, like bird and bird cage. (Admittedly, they might be related using a has a relationship, but I never came across such an assignment.)

Synonyms in terminologies get treated a special way


Synonyms in terminologies get treated a special way: They get collected to a single class. Each of the items of that class is (/treated to be, compare to administrators' cheats above) synonymuos with each other item of the class.

In terminologies called classification there just classes related to each other, being representative for the terms belonging to the class. In thesaurus kind of terminologies there are no such classes. During thesaurus development a sets of synonymous terms get identified. One "most significant/common" term gets chosen to be the term representatively for all the other synonyms. This "most significant/common" one is called "descriptor", while the others become non-descriptors.

Why all the fuss about the synonym details?


If you lookup a synonym you get redirected to the class or descriptor the synonym belongs to. None of the books/other pieces of information ever gets keyworded by a synonym.

That solves the problem of searching the X and Y books mentioned above one day by the and another day by the B search term: Either A points to B or B to A or both to a third term, say C. And both the books are associated by the "most significant/common" term, e.g. C. So, either if you chose A or B as your search term, you always find all the relevant pieces of information/books, e.g. X and Y.

So far the common part of terminologies.

But there is a usability problem in the widespread is a approach.

Glossary


to retrieve - to find again

class - a set of synonymous words

catalogue card - associations between keywords are stored on catalogue cards which, as a whole, make up the catalogue itself

synonym - a word meaning the same as another word
  • sometimes there is a difference between them both, but the one applying them doesn't notice
  • taxonomy administrators sometimes think it is not worth the effort to keep "very similar" terms distinct, so they merge them into a single class by claiming the very words were synonyms



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.

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.