On an online search approach to get nailed down how terminologies, taxonomies, classification, thesauri (etc) related to each other, I noticed the work of the post-doctoral researcher Yannis Tzitzikas of the University of Namur (F.U.N.D.P.), Belgium. His research on faceted taxonomies, especially the application of them to peer to peer networks, looks very close to my MOM/FAVA research.
Updates: none so far
Content Representation With A Twist
Saturday, March 10, 2007
Tuesday, March 06, 2007
Released v0.1.0 of the drafts of the sources
Version 0.1.0 (initial_MOM_net_framework/) of the MOM net generator is there. As the previous ones, also this one is to be considered as drafts. Nothing functional yet.
Updates: none so far
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
Updates: none so far
MOM Simple Set Core project approved
The MOM Simple Set Core project at gna.org was approved on Wednesday, 28 Feb 2007.
On Sunday, 4 March 2007, the first bunch of files was uploaded.
Since a few minutes, it also features a serious project summary.
The project's website at gna.org is sported via the source code repository. A dummy project web page was checked in, recently, but it is not yet live. Possibly, because of the repository detour.
Updates: none so far
On Sunday, 4 March 2007, the first bunch of files was uploaded.
Since a few minutes, it also features a serious project summary.
The project's website at gna.org is sported via the source code repository. A dummy project web page was checked in, recently, but it is not yet live. Possibly, because of the repository detour.
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.
Updates: none so far
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
Now, MOM will be developed publicly
Just a few minutes ago, I queued the core set engine for approval as a GPL project at gna.org.
The long description of the SSC project, I'll file soon.
Updates: none so far
The long description of the SSC project, I'll file soon.
Updates: none so far
If word processors could know the words meanings...
If complex content get be built out of atomic pieces (of content?), how should the complex content become clear, ever?
I think about a word processor. The whole document becomes built out of words, and these out of letters. There is no machine understandable content attached to the words; the words remain just strings of letters. The machine has no idea about the meaning of these strings of letters nor of the sequences of words forming sentences and the whole document.
If at least the words had concepts attached, for a machine it might become much more simple to figure out the content of the whole document. Also since the words theirselves are somewhat related to each other by the underlaying grammar.
To get at least the content of the words accessible, an approach could be to integrate a request for explanation mechanism into the spell checker framework: If the content of the word typed-in is unknown, the user should explain it.
Updates: none so far
I think about a word processor. The whole document becomes built out of words, and these out of letters. There is no machine understandable content attached to the words; the words remain just strings of letters. The machine has no idea about the meaning of these strings of letters nor of the sequences of words forming sentences and the whole document.
If at least the words had concepts attached, for a machine it might become much more simple to figure out the content of the whole document. Also since the words theirselves are somewhat related to each other by the underlaying grammar.
To get at least the content of the words accessible, an approach could be to integrate a request for explanation mechanism into the spell checker framework: If the content of the word typed-in is unknown, the user should explain it.
Updates: none so far
Tuesday, February 20, 2007
What is MOM?
MOM is the acronym for "Model of Meaning". It is founded on one basic assumption, that a notion always consists out of simpler notions or, alternatively, out of raw data -- like "light sensored"
Like ontologies, the MOM building of notions is represented as a graph, a heavily wired network, where the notions make the nodes and the edges indicate which notion consists out of which other notions. Other but common ontologies, MOM avoids edges injecting knowledge which is unreachable to a system that gets the network as its knowledge base. For example, in thesauri there are edges like "this is an antonym to that" and "this a broader term to that". And most of the thesaurus edges (called "relationships") are abstracting. So, for example a dog node may be immediately attached to a animal node. But that implies: The system cannot sense why the dog may be an animal. It fully depends on the humans who foster the network. The same in the case of antonym or even more sophisticated relationships. -- As far as I know, most ontologies tend to make use of such knowledge injecting edges.
Related to this, there is one another big difference between MOM and common classifications/thesauri (also known as "controlled vocabularies"): MOM builds upon a slightly different definition of the term "notion".
Usually, notions are thought of as a triangle of term, item, and thought of the item. MOM does not focus on the item, nor does it have any interest on the terms. (Different cultures have different terms for the same items, hence why care?) Thus, the MOM nodes in fact don't represent notions but just thoughts of items. That makes a huge difference: Relying on the traditional definition of notions, a classification or a thesaurus can validly define a motor vehicle to consist of e.g. a set of wheels, engine, body (amongst others), but validly it can not define a van to consist of a motor vehicle and other parts, since a motor vehicle, simply, is not a part of a van. MOM, on the other hand, ignores the chance that a physical item might be attached to a notion. Hence, yes, part of a van may be a motor vehicle.
This insight allowed to drop the dominating kind of relationship of traditional controlled vocabularies, the abstraction relationship. Which MOM dropped in fact. Which led to a single remaining kind of edges: The partial one. Questions?
Updates: none so far
Like ontologies, the MOM building of notions is represented as a graph, a heavily wired network, where the notions make the nodes and the edges indicate which notion consists out of which other notions. Other but common ontologies, MOM avoids edges injecting knowledge which is unreachable to a system that gets the network as its knowledge base. For example, in thesauri there are edges like "this is an antonym to that" and "this a broader term to that". And most of the thesaurus edges (called "relationships") are abstracting. So, for example a dog node may be immediately attached to a animal node. But that implies: The system cannot sense why the dog may be an animal. It fully depends on the humans who foster the network. The same in the case of antonym or even more sophisticated relationships. -- As far as I know, most ontologies tend to make use of such knowledge injecting edges.
Related to this, there is one another big difference between MOM and common classifications/thesauri (also known as "controlled vocabularies"): MOM builds upon a slightly different definition of the term "notion".
Usually, notions are thought of as a triangle of term, item, and thought of the item. MOM does not focus on the item, nor does it have any interest on the terms. (Different cultures have different terms for the same items, hence why care?) Thus, the MOM nodes in fact don't represent notions but just thoughts of items. That makes a huge difference: Relying on the traditional definition of notions, a classification or a thesaurus can validly define a motor vehicle to consist of e.g. a set of wheels, engine, body (amongst others), but validly it can not define a van to consist of a motor vehicle and other parts, since a motor vehicle, simply, is not a part of a van. MOM, on the other hand, ignores the chance that a physical item might be attached to a notion. Hence, yes, part of a van may be a motor vehicle.
This insight allowed to drop the dominating kind of relationship of traditional controlled vocabularies, the abstraction relationship. Which MOM dropped in fact. Which led to a single remaining kind of edges: The partial one. Questions?
Updates: none so far
Sunday, February 18, 2007
To Keep One's Insights Secret is the Best Chance to Get Stuck.
I am working on a model to represent content in a manner free of words. There are two other main parts tightly related to it: To recognize content by a variable set of given features. And, to reorder the stored content so that implicitly represented content becomes explicit while the already explicit part becomes more straight at the same time.
There is one main thing I avoided during my approach: black boxes. Things that base on people's believes but on proven facts. Things that are overly complex, hence may be estimated only, but not proven.
I avoided two common approaches: utilizing artificial intelligence and linguistics.
Nevertheless, I continued the quest. There is software available, nowadays, hence why to keep the chance out of mind?
Over time, I came to the insight, that notions might be constituted by sets of features, mainly. There -- I had "words" represented. More precisely: the items which are treated as the "templates" for the notions. ... I begun to develop an algorithm to recognize items by their features, varying sets of features, effectively getting rid of the need for globally unique identifier numbers, "IDs" for short. I had a peer to peer network in mind, which automatically should exchange item data sets. That demanded for a way not to identify but at least to recognize items by their features.
Since items can be part of other items -- like a wheel can be part of a car, and a car a part of a car transporter --, I switched from sets to graphs. -- To make clear that the edges used by my model are not simple graph edges, but also to differentiate them from classification/thesauri relationships, I call them "connections".
Then I noticed similarities to neurological structures, mainly neurons, axons, dendrites. Also, I noticed, the yet developed tools could not represent a simple "not", e.g. "a not red car", I begun to experiment with meaning modifying edges. Keeping in mind, that there is probably no magical higher instance providing the neurons with knowledge -- as for example knowledge about that one item is the opposite of another --, I kept away from connections injecting new content/knowledge; in this case knowledge about how to interpret an antonym relationship. I strove for the smallest set of variations of connections.
However, even without content modifying connections, the tag phenomenon common to the web could take great benefit: The connections between the items make clear which item is implication of which other(s). Applied to tagging, users would not need to mention the implications anymore: The implications would be available by the underlaying ontology. (And the ontology could be enhanced by a central site, by individual users, or by a peer to peer network of users.)
But usually, every feature points to multiple items at once. Most probably, every item a feature is pointing to is chosen reasonably, i.e. the item the feature is pointing to is neither randomly chosen nor complete trash. Thus, a simple count might be enough: How many given features point to which items? How great is the quota of features pointing to a particular item, compared to the number of total incoming feature connections? -- The number of incoming feature connections, I call stimulations.
There's one condition applied to the recognition: If one node gets a particular number of stimulations, e.g. two stimulations, that very node will be considered to be "active" itself, hence stimulating its successor nodes as well. For a basic implementation of recognition, this approach is enough. A more sophisticated kind of recognition also considers nodes stimulated only, but not activated.
However, having recognition at hand -- even at this most basic level -- would finally support the above aproach of tagging to leave alone the implications: Given only a handful of features would be enough to determine the item meant. Also, applied to online search, the search engine could determine the x most probably meant items and include them into the search.
Despite these, I see one big chance: Currently, if a person gets a physical item the individual does not know and cannot identify, she or he needs to let it recognize by someone else. Usually your vendor. Where you have to move the part to. Some parts are heavy, others cannot be moved simply. And you are hindered using common tools to identify the object: Search engines don't operate on visual appearance, and information science tools like thesauri and classifications fail completely, simple because they prefer abstraction relationships over partial ones.
Using software able to recognize items by features would overcome such issues, completely, and independently of the kind of feature: It would be equal whether the feature would be a word, i.e. name, label, or color, shape, taste, smell or other. And, other but relational databases, there were no need for another table dimension for each feature -- just a unified method to attach new features to items.
Since the chains oftenly just can be cut down, I concentrated on the cases of unidentified implicit definitions. For simplicity, I imagined a set of features pointing to sets of items. Some of the features might point to the same items in common, e.g. the features <four legs>, <body>, <head>, and <tail> in common would point to the items <cat>, <dog>, and <elephant>. You might notice, that <cat>, <dog>, and <elephant>, all are animals, and also all these animals feature a body, four legs, head, and tail. Thus, <animal> is one implication of this set of features and items. The implication is not mentioned explicitely, but it's there.
Consequently, the whole partial network could be replaced by another one, mentioning the <animal> node as well: <four legs>, <body>, <head>, and <tail> would become features of the new <animal> node, and <animal> itself would become common feature of <cat>, <dog>, and <elephant>.
By that, the network would become more straight (since the number of connections needed would reduced from number of features * number of items to only number of features + number of items), hence also more lightweight. Also, items implied would become visible.
While this approach makes the implications visible, it opens two new doors: One, the identified implications cannot be named without the help of a human -- at least not easily. (Recognition could do a honour, but I skip that here.) The second issue is, that the newly introduced node ("<animal>") conflicts with recognition: For example: If there was a another node, e.g. <meows>, directly pointing to the <cat> node, after the reorganization, a given set of <meows> and <head>, only, would not result in <cat> anymore since each of the given features would, yes, stimulate their successor nodes, but not activate. -- To actively receive stimulations from predecessor nodes could be a solution, but I am not yet quite sure. As mentioned initially, this is a work in progress.
However, reorganization would automate identification of implications. People could provide labels for the added implication nodes. -- Which induces another effect of the model.
Instead, all the items and the features (whereby "features" is just another name for items located a level below the level of items initially considered) get identified by [locally only] unique IDs. The names of the items I'd store somewhere else, so that item names in multiple languages could point to the very item. That helps in localization of the system, but also, it opens the chance to overcome an issue dictionaries cannot manage: There are languages that do not provide an immediate translation for a given word -- because the underlaying concept is different. The English "to round out" term and the German "abrunden" is such an example: In fact, the German variant considers an external point of view ("to round by taking something away"), while the English obviously takes an internal one.
Not sticking on labels but on items/notions, the model features a chance to label the appropriate, maybe even slightly dismatching, nodes: The need to label exactly the same -- but probably not exactly matching -- node is gone. -- In a word: I think, in different cultures many notions differ slightly from similar ones of other cultures, but each culture labels only their own notions, ignoring slightly different points of view of other cultures. -- This notions/labeling issue, I imagine as puddles: Each culture has its own puddles for each of its notions. From the point of view of different languages, some puddles match greatly, maybe even totally, but some feature no intersection at all. Those are the terms having no counterpart in the other language.
In the long term, I consider the approach to build upon notions/items -- but on words -- as a real chance to overcome the language barrier.
Updates: none so far
There is one main thing I avoided during my approach: black boxes. Things that base on people's believes but on proven facts. Things that are overly complex, hence may be estimated only, but not proven.
I avoided two common approaches: utilizing artificial intelligence and linguistics.
Representing The Content
On dealing with thesauri and classifications, I noticed the fact that those ontologies force abstraction relationships between mentioned notions. Therefore, I thought about the alternative, to force the partial relationship. What would result, if all the notions had to be represented as partial relationships? -- A heavily wired graph. -- Originally, thesauri and classifications were fostered manually. Therefore, it looked clear to me, noone would like to foster a densely wired graph to keep track of notions.Nevertheless, I continued the quest. There is software available, nowadays, hence why to keep the chance out of mind?
Over time, I came to the insight, that notions might be constituted by sets of features, mainly. There -- I had "words" represented. More precisely: the items which are treated as the "templates" for the notions. ... I begun to develop an algorithm to recognize items by their features, varying sets of features, effectively getting rid of the need for globally unique identifier numbers, "IDs" for short. I had a peer to peer network in mind, which automatically should exchange item data sets. That demanded for a way not to identify but at least to recognize items by their features.
Since items can be part of other items -- like a wheel can be part of a car, and a car a part of a car transporter --, I switched from sets to graphs. -- To make clear that the edges used by my model are not simple graph edges, but also to differentiate them from classification/thesauri relationships, I call them "connections".
Then I noticed similarities to neurological structures, mainly neurons, axons, dendrites. Also, I noticed, the yet developed tools could not represent a simple "not", e.g. "a not red car", I begun to experiment with meaning modifying edges. Keeping in mind, that there is probably no magical higher instance providing the neurons with knowledge -- as for example knowledge about that one item is the opposite of another --, I kept away from connections injecting new content/knowledge; in this case knowledge about how to interpret an antonym relationship. I strove for the smallest set of variations of connections.
However, even without content modifying connections, the tag phenomenon common to the web could take great benefit: The connections between the items make clear which item is implication of which other(s). Applied to tagging, users would not need to mention the implications anymore: The implications would be available by the underlaying ontology. (And the ontology could be enhanced by a central site, by individual users, or by a peer to peer network of users.)
Recognizing The Content
Having that peer to peer network in mind, I needed a way to identify items stored at untrusted remote hosts. I noticed, that collecting sets of features together which theirselves would be considered to be items, meant nothing but a definition of the items by their features. Different peers -- precisely: users of the peer software -- might define the same items by different features. Which might leave only some of the features locally known/set to match those remotely set. -- However, most time that's enough to recognize an item by its features: Some features point to a single item only. These features are valuable: They are specific for that very item. If one of these specific features is given, most probably the item, the feature is pointing to, is meant.But usually, every feature points to multiple items at once. Most probably, every item a feature is pointing to is chosen reasonably, i.e. the item the feature is pointing to is neither randomly chosen nor complete trash. Thus, a simple count might be enough: How many given features point to which items? How great is the quota of features pointing to a particular item, compared to the number of total incoming feature connections? -- The number of incoming feature connections, I call stimulations.
There's one condition applied to the recognition: If one node gets a particular number of stimulations, e.g. two stimulations, that very node will be considered to be "active" itself, hence stimulating its successor nodes as well. For a basic implementation of recognition, this approach is enough. A more sophisticated kind of recognition also considers nodes stimulated only, but not activated.
However, having recognition at hand -- even at this most basic level -- would finally support the above aproach of tagging to leave alone the implications: Given only a handful of features would be enough to determine the item meant. Also, applied to online search, the search engine could determine the x most probably meant items and include them into the search.
Despite these, I see one big chance: Currently, if a person gets a physical item the individual does not know and cannot identify, she or he needs to let it recognize by someone else. Usually your vendor. Where you have to move the part to. Some parts are heavy, others cannot be moved simply. And you are hindered using common tools to identify the object: Search engines don't operate on visual appearance, and information science tools like thesauri and classifications fail completely, simple because they prefer abstraction relationships over partial ones.
Using software able to recognize items by features would overcome such issues, completely, and independently of the kind of feature: It would be equal whether the feature would be a word, i.e. name, label, or color, shape, taste, smell or other. And, other but relational databases, there were no need for another table dimension for each feature -- just a unified method to attach new features to items.
Reorganizing The Content
Also directly related to that peer to peer network in mind, peers exchanging item data sets -- e.g. nodes plus context (connections and attached neighbor nodes) -- could result in heavy wiring, superfluous chains of single-feature-single-item definitions, and lots of unidentified implicit item definitions. That needs to be avoided.Since the chains oftenly just can be cut down, I concentrated on the cases of unidentified implicit definitions. For simplicity, I imagined a set of features pointing to sets of items. Some of the features might point to the same items in common, e.g. the features <four legs>, <body>, <head>, and <tail> in common would point to the items <cat>, <dog>, and <elephant>. You might notice, that <cat>, <dog>, and <elephant>, all are animals, and also all these animals feature a body, four legs, head, and tail. Thus, <animal> is one implication of this set of features and items. The implication is not mentioned explicitely, but it's there.
Consequently, the whole partial network could be replaced by another one, mentioning the <animal> node as well: <four legs>, <body>, <head>, and <tail> would become features of the new <animal> node, and <animal> itself would become common feature of <cat>, <dog>, and <elephant>.
By that, the network would become more straight (since the number of connections needed would reduced from number of features * number of items to only number of features + number of items), hence also more lightweight. Also, items implied would become visible.
While this approach makes the implications visible, it opens two new doors: One, the identified implications cannot be named without the help of a human -- at least not easily. (Recognition could do a honour, but I skip that here.) The second issue is, that the newly introduced node ("<animal>") conflicts with recognition: For example: If there was a another node, e.g. <meows>, directly pointing to the <cat> node, after the reorganization, a given set of <meows> and <head>, only, would not result in <cat> anymore since each of the given features would, yes, stimulate their successor nodes, but not activate. -- To actively receive stimulations from predecessor nodes could be a solution, but I am not yet quite sure. As mentioned initially, this is a work in progress.
However, reorganization would automate identification of implications. People could provide labels for the added implication nodes. -- Which induces another effect of the model.
Overcome the Language Barrier
I mentioned that I kept away from connections injecting knowledge unreachable to the software. That's not all. I strive to completely avoid any kind of content unreachable, needing any external mind/knowledge storage which would provide interpretation of such injected content/knowledge. Hence, I also avoided to operate on a basis of labels for the items.Instead, all the items and the features (whereby "features" is just another name for items located a level below the level of items initially considered) get identified by [locally only] unique IDs. The names of the items I'd store somewhere else, so that item names in multiple languages could point to the very item. That helps in localization of the system, but also, it opens the chance to overcome an issue dictionaries cannot manage: There are languages that do not provide an immediate translation for a given word -- because the underlaying concept is different. The English "to round out" term and the German "abrunden" is such an example: In fact, the German variant considers an external point of view ("to round by taking something away"), while the English obviously takes an internal one.
Not sticking on labels but on items/notions, the model features a chance to label the appropriate, maybe even slightly dismatching, nodes: The need to label exactly the same -- but probably not exactly matching -- node is gone. -- In a word: I think, in different cultures many notions differ slightly from similar ones of other cultures, but each culture labels only their own notions, ignoring slightly different points of view of other cultures. -- This notions/labeling issue, I imagine as puddles: Each culture has its own puddles for each of its notions. From the point of view of different languages, some puddles match greatly, maybe even totally, but some feature no intersection at all. Those are the terms having no counterpart in the other language.
In the long term, I consider the approach to build upon notions/items -- but on words -- as a real chance to overcome the language barrier.
Conclusion
Despite the option of dropping the custom to label different items by the same name (as thesauri tend to do to reduce foster effort) and the possible long-term chance of overcoming the language barrier, I see three main benefits for the web, mainly for tagging and online search:- Tagging could be reduced to the core tags; all implications could be left to the underlaying ontology.
- Based on the same ontology, during search, sets of keywords could be examined to "identify" the items most probably meant. The same approach could be applied by the peer to peer network to exchange item data sets.
- Finally, the reorganization would keep the ontology graph lightweight, therefore ease the fostering. Also, the auto-detection of implications would support users in keeping their tags clear and definite. That could reduce blur in tag choose, thus increase precision in search/search results.
Updates: none so far
Saturday, February 17, 2007
Elements of Semantic Web Explained in an Environment of Buzz
In Minding the Planet, on February 13, 2007, Nova Spivack makes a lot of buzz about his upcoming venture, Radar Networks. Besides, he explains some of the elements of Semantic Web he considers to be key. Mostly, his posting commends the chance of ontologies to disambiguate homonyms, and that that disambiguation can be applied to documents by markup.
Some of the concepts, the posting does not get really clear, like information, content, concept, meaning, "things", data. The posting looks less scientific but very excited about the business of its author. There are lots of repetitions.
On the web side, the posting mentions the sites Powerset, TextDigger, Metaweb and the terms OWL and REST, which might be worth a look.
On the blogging side, Nova Spivack's posting can be tracked back, but only immediately. Blogger does not support that feature, hence, currently, I am stuck with manual trackback tools like Adam Kalsey's Simpletrack or the Wizbang Standalone Trackback Pinger. But the trackbacks generated by them, Nova Spivack's blog refuses by a captcha -- and both of the tools don't show that.
Despite Nova Spivack's posting didn't boosted me with concepts I didn't know yet, I'd be interested in learn about alternative manual trackback tools (either online or available for *nix) or any great but free alternatives to blogger.com. Can you provide me with a matching hint?
Updates: none so far
Some of the concepts, the posting does not get really clear, like information, content, concept, meaning, "things", data. The posting looks less scientific but very excited about the business of its author. There are lots of repetitions.
On the web side, the posting mentions the sites Powerset, TextDigger, Metaweb and the terms OWL and REST, which might be worth a look.
On the blogging side, Nova Spivack's posting can be tracked back, but only immediately. Blogger does not support that feature, hence, currently, I am stuck with manual trackback tools like Adam Kalsey's Simpletrack or the Wizbang Standalone Trackback Pinger. But the trackbacks generated by them, Nova Spivack's blog refuses by a captcha -- and both of the tools don't show that.
Despite Nova Spivack's posting didn't boosted me with concepts I didn't know yet, I'd be interested in learn about alternative manual trackback tools (either online or available for *nix) or any great but free alternatives to blogger.com. Can you provide me with a matching hint?
Updates: none so far
Labels:
blogger.com,
Metaweb,
Nova Spivack,
OWL,
Powerset,
Radar Networks,
REST,
superfluous postings,
TextDigger,
trackback tools
Thursday, February 15, 2007
Social Software does not equal Social Networking
Radar Networks mentions:
On the other hand, social networking includes making the participants known to each other -- in some way or the other.
Updates: none so far
(note that social software is not necessarily social networking -- that is subset of social software)Quite true, like a spam filter applied by a major freemail provider: Participants can mark mails in their inboxes as spam while unknowingly marking the same mail (body) in other participants' inboxes as spam as well. Or at least, increase the chance the mail will be considered as spam at some decent point of marks pileage.
On the other hand, social networking includes making the participants known to each other -- in some way or the other.
Updates: none so far
How content providers could inform about the quality of their content
The W3C Content Label Incubator Group writes:
If a content provider gets the chance to mention whether its content fulfils certain criteria, I wonder, how that should be trustworthy in any way. Every single unreflected opinion, provided by any anonymous poster could be announced to fulfill, simply, every criteria.
I think, a self-selected claim of what the content is self offers, wouldn't work unless there's some kind of social control. Either that there's some kind of unwritten law applied or there's an immediate social control by known peers of the content provider or an indirect social control, as drafted by the popular rating systems, known e.g. from e-bay.
Alternatively, a (neutral?) software could be developed which states the fulfill of the content. Another question is, whether a piece of content fulfills the same criteria or every perceiver or if the fulfillment depends on the person who's consuming the content. -- At least for the also mentioned "content providers can inform [...] that their content [...] meets given requirements", I'd opt for the chance, that the peer actually needing to apply the information provided (by the content) probably can decide better than the content provider whether or not the content provided meets any given requirement. If that question is answerable once and for all, ever.
Updates: none so far
The diversity of material on the Web continues to grow to encompass audio, video, games and all manner of data services alongside traditional documents. The Content Label Incubator Group [WCL-XG] aims to foster ideas for how content providers can inform [...] that their content is of a certain type, fulfils certain criteria or meets given requirements.(Highlighting is mine.)
If a content provider gets the chance to mention whether its content fulfils certain criteria, I wonder, how that should be trustworthy in any way. Every single unreflected opinion, provided by any anonymous poster could be announced to fulfill, simply, every criteria.
I think, a self-selected claim of what the content is self offers, wouldn't work unless there's some kind of social control. Either that there's some kind of unwritten law applied or there's an immediate social control by known peers of the content provider or an indirect social control, as drafted by the popular rating systems, known e.g. from e-bay.
Alternatively, a (neutral?) software could be developed which states the fulfill of the content. Another question is, whether a piece of content fulfills the same criteria or every perceiver or if the fulfillment depends on the person who's consuming the content. -- At least for the also mentioned "content providers can inform [...] that their content [...] meets given requirements", I'd opt for the chance, that the peer actually needing to apply the information provided (by the content) probably can decide better than the content provider whether or not the content provided meets any given requirement. If that question is answerable once and for all, ever.
Updates: none so far
Guest Book: Your comments are appreciated!
You comments are welcome!
If you're about to comment on the blog as a whole but on a single posting, here's your place. Just make use of the comments section of this posting, consider it to be a substitute for a non-existing guest book application.
Thanks for leaving a note.
Updates: none so far
If you're about to comment on the blog as a whole but on a single posting, here's your place. Just make use of the comments section of this posting, consider it to be a substitute for a non-existing guest book application.
Thanks for leaving a note.
Updates: none so far
time to blog
Ralf told me about the evolving tags vs. semantic web vs. social web vs. web 2.0 story. I noticed, yet being late. In 2000, I begun to develop a system of language independently represent content. I evolved it far, but I focused on analysis but implementation. Also, I dropped programming as hobby in about 1997; and the (programming) language I used to prove this or that concept, was not the kind for release. Plus, I am a C refugee.
Currently, I am bringing a part project to an end, which reorders graphs of concepts ("notions") so that not explicitely mentioned concepts become visible (and accessible and reusable). I used Perl for that, but it might be largely unreadable. Nevertheless, if anyone is interested in it, I'd disclose it.
Despite tags is a topic yet behind, I decided to prepare an article on that topic. There I noticed, now even more people became interested in that field of topic. Ralf's mention confirmed that. And my impression of becoming late. Hence, now, this as a first step into public.
Original posting: dot dot dot: time to blog
Updates: none so far
Currently, I am bringing a part project to an end, which reorders graphs of concepts ("notions") so that not explicitely mentioned concepts become visible (and accessible and reusable). I used Perl for that, but it might be largely unreadable. Nevertheless, if anyone is interested in it, I'd disclose it.
Despite tags is a topic yet behind, I decided to prepare an article on that topic. There I noticed, now even more people became interested in that field of topic. Ralf's mention confirmed that. And my impression of becoming late. Hence, now, this as a first step into public.
Original posting: dot dot dot: time to blog
Updates: none so far
Tuesday, April 04, 2006
previous description of this blog
Today I change(d) the description of this blog. The prior one was:
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.
- The Model of Meaning is a knowledge representation approach that shall allow to skip the training phase of an artificial neural network. – I started research in this field of subject earlier, but I am very interested in collaboration with researchers of related fields like artificial intelligence, neurobiology etc. Software applications of findings of this project also would be very appreciated.
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.
Labels:
blogging on MOM,
get in touch,
knowledge,
neural network,
objective
Sunday, March 05, 2006
Cleaning up the confusion about thesauri and classifications
To clean up the confusion mentioned earlier, I wrote a short introductionary article on thesauri and classifications. It mainly relies on an excerpt taken from a book of a former information science teacher of mine. -- Here we go:
Methods of organizing content representation originate from the fields of library science and documentation.[2]
There are two dominant content representation methods in documentation: classification and thesaurus. "A classification is a structured representation of classes and of the notional relationships between the classes."[3] Any class is represented by a notation, whereby the notation is independent of any natural language (cf. DIN 37205, 2).[4] "Similarly, a thesaurus also is an organized compilation of terms, but in this case their natural language appellations are used (cf. DIN 1463/1, 2)."[5]
Systems of concept differentiate between two main kinds of relationship: associative and hierarchical relationship. There are two variants of the latter: the abstract and the partitive variant.[7]
Abstract relationship means that a "child" term has the same features as its parent plus at least one additional feature, the parent term does not have.[8] (The features are not stated anywhere; there is nothing but a parent term, a child term, and a relationship link between both of them, representing that very "the child term has the same features as the parent one, but at least one additional other feature, the parent term does not have". -- In fact, the relationship refers to the items not to the notations: The item referred to by the notation has the more/the less features than the item referred to by the parent/child term notation.)
Partitive relationship means that the items referred to by the child terms are part of the item referred to by the parent term.[9]
Associative relationship refers to a relationship existing between a pair of terms that cannot be related hierarchically to each other, although nevertheless there is a relationship between both of the terms. A pair of antonyms cannot be related hierarchically to each other, therefore here the matching kind of relationship is the associative one.[10]
"A classification is a system of concepts"[11] having notions as classes. The classes are labeled by notations[12], which are language independent.
[1] cf. [Stock 2000], p. 59, par. 1
[2] cf. [Stock 2000], p. 59, par. 2, sentence 1
[3] [Stock 2000], p. 59, par. 3, sentence 2: "Eine Klassifikation ist eine strukturierte Darstellung von Klassen und der zwischen den Klassen bestehenden Begriffsbeziehungen [...]."
[4] cf. [Stock 2000], p. 59, par. 3, sentence 2
[5] cf. [Stock 2000], p. 59, par. 3
[6] cf. [Stock 2000], p. 59, par. 4 (incl headline)
[7] cf. [Stock 2000], p. 60, par. 1
[8] cf. [Stock 2000], p. 61, par. 2, sentences 1–2
[9] cf. [Stock 2000], p. 61, par. 2, sentences 4–5
[10] cf. [Stock 2000], p. 62, par. 1 (incl. bullet list)
[11] [Stock 2000], p. 63, par. 1, sentence 1: "Ein Klassifikationssystem ist ein Begriffssystem [...]."
[12] cf. [Stock 2000], p. 63, par. 1, sentences 1–2
[13] cf. [Stock 2000], p. 76, no. 3.3, par. 2, sentence 2
[14] cf. [Stock 2000], pp. 81–84
[15] cf. [Stock 2000], p. 77, par. 1 (including the example in between)
[16] cf. [Stock 2000], p. 77, par. 1, sentence 2
[Stock 2000]:
Stock, Wolfgang G.
Informationswirtschaft : Management externen Wissens
number of edition unknown
Muenchen, Wien, Oldenbourg, 2000
ISBN 3-486-24897-9<<
Updates: 20070624: Tagged the posting. Updated the posting style (layout) to my current style, such as more precise word picks, better grammar.
Introduction
Base assumption is that data, information, knowledge require to be ordered. The data has to be ordered systematically. People who perform indexing on data bases -- so called "indexers" -- use order systems to make content retrievable. Thus, only if a user knows the tools used during database creation she/he can retrieve information from that very database.[1]Methods of organizing content representation originate from the fields of library science and documentation.[2]
There are two dominant content representation methods in documentation: classification and thesaurus. "A classification is a structured representation of classes and of the notional relationships between the classes."[3] Any class is represented by a notation, whereby the notation is independent of any natural language (cf. DIN 37205, 2).[4] "Similarly, a thesaurus also is an organized compilation of terms, but in this case their natural language appellations are used (cf. DIN 1463/1, 2)."[5]
Systems of Concepts
Business documentation creates an order. This order refers to notions (= concepts) an relations between these notions. "One may assume that this equals to organize business terminology [...] by a notional order."[6]Systems of concept differentiate between two main kinds of relationship: associative and hierarchical relationship. There are two variants of the latter: the abstract and the partitive variant.[7]
Abstract relationship means that a "child" term has the same features as its parent plus at least one additional feature, the parent term does not have.[8] (The features are not stated anywhere; there is nothing but a parent term, a child term, and a relationship link between both of them, representing that very "the child term has the same features as the parent one, but at least one additional other feature, the parent term does not have". -- In fact, the relationship refers to the items not to the notations: The item referred to by the notation has the more/the less features than the item referred to by the parent/child term notation.)
Partitive relationship means that the items referred to by the child terms are part of the item referred to by the parent term.[9]
Associative relationship refers to a relationship existing between a pair of terms that cannot be related hierarchically to each other, although nevertheless there is a relationship between both of the terms. A pair of antonyms cannot be related hierarchically to each other, therefore here the matching kind of relationship is the associative one.[10]
"A classification is a system of concepts"[11] having notions as classes. The classes are labeled by notations[12], which are language independent.
Main difference between Thesaurus and Classification
The main difference between thesaurus and classification is that a thesaurus selects natural language words instead of setting up cryptic notations.[13] Thus, otherwise than classifications, a thesaurus cannot be used language indepently. To avoid confusing originating from synonyms and homonyms a thesaurus applies terminological control, i.e. it keeps homonyms distinct and sets of synonyms referring to the same item constitute a class. The most common one of these synonyms gets picked up and will be treated as the descriptor of that very class, i.e. a handle for the class -- one could say "a natural language notation" or simply "a label". To ensure that any piece of information (which shall be referred to by at least one "word" of the thesaurus[14]) always gets referred by the same "word", the non-descriptor synonyms refer to the descriptor of the class they belong to. Thus, any piece of information gets referred to by descriptors only, and retrieval attempts using non-descriptor synonyms get redirected to the matching descriptors. So, the pieces of information get tagged by descriptor synonyms (for short just "descriptors") and retrievals also use descriptors, so a match between tagging "words" and retrieval "words" becomes much more probable than if allowing to choose from descriptors and non-descriptors as well.[15]Accuracy sacrified to administration convenience
Sometimes synonyms and terms referring to similar items as the other synonyms won't be/aren't kept distinct but simply added to a common class[16]. Reason for this often is to keep administration expense low.[1] cf. [Stock 2000], p. 59, par. 1
[2] cf. [Stock 2000], p. 59, par. 2, sentence 1
[3] [Stock 2000], p. 59, par. 3, sentence 2: "Eine Klassifikation ist eine strukturierte Darstellung von Klassen und der zwischen den Klassen bestehenden Begriffsbeziehungen [...]."
[4] cf. [Stock 2000], p. 59, par. 3, sentence 2
[5] cf. [Stock 2000], p. 59, par. 3
[6] cf. [Stock 2000], p. 59, par. 4 (incl headline)
[7] cf. [Stock 2000], p. 60, par. 1
[8] cf. [Stock 2000], p. 61, par. 2, sentences 1–2
[9] cf. [Stock 2000], p. 61, par. 2, sentences 4–5
[10] cf. [Stock 2000], p. 62, par. 1 (incl. bullet list)
[11] [Stock 2000], p. 63, par. 1, sentence 1: "Ein Klassifikationssystem ist ein Begriffssystem [...]."
[12] cf. [Stock 2000], p. 63, par. 1, sentences 1–2
[13] cf. [Stock 2000], p. 76, no. 3.3, par. 2, sentence 2
[14] cf. [Stock 2000], pp. 81–84
[15] cf. [Stock 2000], p. 77, par. 1 (including the example in between)
[16] cf. [Stock 2000], p. 77, par. 1, sentence 2
[Stock 2000]:
Stock, Wolfgang G.
Informationswirtschaft : Management externen Wissens
number of edition unknown
Muenchen, Wien, Oldenbourg, 2000
ISBN 3-486-24897-9<<
Updates: 20070624: Tagged the posting. Updated the posting style (layout) to my current style, such as more precise word picks, better grammar.
Saturday, March 04, 2006
Main thesis of MOM
Main thesis of MOM is, that items get represented in mind -- and can be represented in terms of data -- by features of these very items.
Furthermore, if such a decision is performed, i.e. if there is a stop of going more and more into details, then the representation cannot be complete. Thus, the represented entity does not match the real example. If so, the representation has to be treated to be invalid. -- On the other hand, if there is no stop, i.e. details barrier, the representation might have has to be as sophisticated as reality/the universe itself. In other words: It is impossible to represent things following this approach, since noone has the resources to represent the universe as a whole.
True. But on the other hand, everyone knows that humans tend to be fallible and by first hand experience most people also know that there is often one thing or another that they didn't know yet. That humans are able to learn was treated to be something special for a long spell. Additionally, most people made the experience, that children which grew up with small dogs in their neighbourhood confuse a cat with the yet known dogs, when they first experience a cat: They call the cat by dogs' common nick name ("Wau-Wau" in Germany).
Therefore I assume, the representation of an item in the first place consists of only as many details as necessary to differenciate the item from another one. A dog from a human. But, since not ever experienced, not from a cat. When experienced, more features get added to also differenciate the cat from the dog. That is: I assume, that in fact there is a details barrier, but I do not assume that it is given highanded by an external mind. Instead, I assume the details barrier is constituted by the attempt of resources saving: Every represented feature might cause a cost of resources, so any unnecessarily represented feature would cause unnecessary cost of resources. Therefore only necessary features would be stored, resulting in the details barrier.
This rises another question: Is it enough to store not all the features of an item but only the necessary ones? -- I assume: Yes, it is, since reality brings a backup: It even might be enough to represent only features an item has without to store, how these features are ordered -- if you treat a dog as head, neck, tail, torso, four legs, can bark, reality ensures that there is not a dog that has its legs and tail attached to its head and the neck and torso to the tail. So, for first this unordered composition approach suffices. Deeper insight into the Model of Meaning offers ways to represent structure as well.<<
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.
Where to stop going deeper and deeper into details
First objection against this assertion often is, that that inevitably would necessitate a highhanded decision, at what level of granularity to stop going to even more granularity: If a dog's features area head, a neck, a tail, a torso, and four legs, then its head's features are at least, that it haves two eyes, two ears, a mouth, a nose; the features of the mouth at least are: some teeth, a tongue, spittle etc. The teeth' features are enamel, root, ... and so on. So, where to stop going into more and more and more detail? -- But if an external mind has to make that decision where to make this stop, the approach has to be wrong, since there is no external mind enjoining human being's minds where to stop.Furthermore, if such a decision is performed, i.e. if there is a stop of going more and more into details, then the representation cannot be complete. Thus, the represented entity does not match the real example. If so, the representation has to be treated to be invalid. -- On the other hand, if there is no stop, i.e. details barrier, the representation might have has to be as sophisticated as reality/the universe itself. In other words: It is impossible to represent things following this approach, since noone has the resources to represent the universe as a whole.
True. But on the other hand, everyone knows that humans tend to be fallible and by first hand experience most people also know that there is often one thing or another that they didn't know yet. That humans are able to learn was treated to be something special for a long spell. Additionally, most people made the experience, that children which grew up with small dogs in their neighbourhood confuse a cat with the yet known dogs, when they first experience a cat: They call the cat by dogs' common nick name ("Wau-Wau" in Germany).
Therefore I assume, the representation of an item in the first place consists of only as many details as necessary to differenciate the item from another one. A dog from a human. But, since not ever experienced, not from a cat. When experienced, more features get added to also differenciate the cat from the dog. That is: I assume, that in fact there is a details barrier, but I do not assume that it is given highanded by an external mind. Instead, I assume the details barrier is constituted by the attempt of resources saving: Every represented feature might cause a cost of resources, so any unnecessarily represented feature would cause unnecessary cost of resources. Therefore only necessary features would be stored, resulting in the details barrier.
This rises another question: Is it enough to store not all the features of an item but only the necessary ones? -- I assume: Yes, it is, since reality brings a backup: It even might be enough to represent only features an item has without to store, how these features are ordered -- if you treat a dog as head, neck, tail, torso, four legs, can bark, reality ensures that there is not a dog that has its legs and tail attached to its head and the neck and torso to the tail. So, for first this unordered composition approach suffices. Deeper insight into the Model of Meaning offers ways to represent structure as well.<<
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.
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.
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:
- Usability problem in the widespread 'is a' approach
- From the Information Science local point of view (upgraded)
- From the Information Science local point of view
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.
Labels:
diploma thesis,
employ me,
information science,
MOM,
ontology,
thesaurus
Saturday, February 25, 2006
Approach from Tagging
ontology
Ontology is a form of classification which may be thought of as "conceptual" relationships. Whereas in a taxonomy terms may be classified together as "fruit", in an ontology the conceptual relationship may be "fruit which are used in pies" or "growing fruit for sale". Ontological relationships are inherently self-describing. Ontologies are the backbone of the semantic web, as they provide multiple links to data and therefore can support search and insightful navigation. — Source
Problem, I see: The meaning of "fruit which are used in pies" is not accessible to the machine. The machine depends on this kind of "knowledge" given to it, cannot exceed the borders resulting from that kind of knowledge. For short: The machine is unable to determine by itself whether or not a given item belongs to a "fruit which are used in pies" relationship, if nowhere is stated that this is the case. Same for different kinds of thesaurus relationships ("broader term", "narrower term", etc.), which I originally criticised.
I avoided to touch the semantic web attempt, since I feared such a kind of approach. Now, when I had to look up taxonomy, classification, terminology, etc. to avoid to mess them up, I came across the above statement, that the semantic web in fact approaches this way. Sad.
In my opinion, a machine needs a way, to get competence to decide. Knowledge to make the decision on. Knowledge on knowledge. Knowledge on knowledge to get able to verify its own knowledge. As long as there are parts of the machine's knowledge the machine cannot access, it hasn't got a chance to get independent of external minds, e.g. humans.
I don't think that the best approach to achieve that goal is to stack more and more complexity/abstraction layers on the already not-working attempts. Instead, I think, it is necessary to determine a way to make most basic knowledge accessible to the machine, in a way that the machine doesn't have to depend on externally given knowledge. I think, that if that basic goal is achieved, more complex kinds of content/knowledge can be built atop.<<
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.
Friday, February 24, 2006
Usability problem in the widespread 'is a' approach
As introduced earlier, taxonomies as thesauri and classifications organize terms in a net similar to a tree. Hierarchically, the terms get ordered mainly by is a relationships, seldom by has a ones. Also there are relationships between terms that have "something" to do with each other, but cannot be ordered validly hierarchically. Like bird and bird cage. Some taxonomies force one parent term per node, i.e. a structure that easily can be identified as being mainly a tree, with exception of some cross reference like associative relationships. Other taxonomies don't force the one parent per term rule, so that such a one might easily look more like a net but like a tree. The prior ones are called "mono-hierarchical", while the latters' label is "poly-hierarchical".
This presupposition requires that the one who's using a taxonomy already is a kind of an expert in the field organized by the taxonomy. If you're looking for a term you don't know where to look up, you're lost.
Say, some part fell from your car, and since then it doesn't move anymore. You don't know the term for that part, and the very one is too heavy, so you cannot just take it to the garage. -- Because of its primary is a nature, a taxonomy is of no use here for you. Another chance is to go to the garage without the part and attempt to explain the nature of it to a worker there. (So far, my university information science teacher guided me.)
So, the problem of a taxonomy is that it doesn't support the most straight ahead approach to identify an item -- to select the most conspicuous properties of the item the taxonomy -- broader: knowledge storage, e.g. a garage worker's memory -- already knows about.<<
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.
What's the problem?
Taxonomies don't do anything more but relating the terms to other terms. The task to define the terms they leave to dictionaries.This presupposition requires that the one who's using a taxonomy already is a kind of an expert in the field organized by the taxonomy. If you're looking for a term you don't know where to look up, you're lost.
Say, some part fell from your car, and since then it doesn't move anymore. You don't know the term for that part, and the very one is too heavy, so you cannot just take it to the garage. -- Because of its primary is a nature, a taxonomy is of no use here for you. Another chance is to go to the garage without the part and attempt to explain the nature of it to a worker there. (So far, my university information science teacher guided me.)
So, the problem of a taxonomy is that it doesn't support the most straight ahead approach to identify an item -- to select the most conspicuous properties of the item the taxonomy -- broader: knowledge storage, e.g. a garage worker's memory -- already knows about.<<
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.
Subscribe to:
Posts (Atom)