Tools for Semantics - Global Sensemaking2024-03-28T19:25:10Zhttp://globalsensemaking.net/forum/topics/2052744:Topic:3506?feed=yes&xn_auth=noA sincere "thank you" for red…tag:globalsensemaking.net,2008-08-20:2052744:Comment:63652008-08-20T02:56:51.000ZAndy Streichhttp://globalsensemaking.net/profile/AndyS
A sincere "thank you" for redirecting my energy, Bob.<br />
<br />
<i>"I think we're in the discussion phase, .... I'm not sure if there are any convenient software tools for facilitating development and implementation of an online discussion agenda."</i><br />
<br />
In some sense, this is the very foundation of making sensemaking tools useful on the web. To me your phrase "convenient software tools for facilitating development and implementation of an online discussion agenda" (I'm not aware of any) is a key part of…
A sincere "thank you" for redirecting my energy, Bob.<br />
<br />
<i>"I think we're in the discussion phase, .... I'm not sure if there are any convenient software tools for facilitating development and implementation of an online discussion agenda."</i><br />
<br />
In some sense, this is the very foundation of making sensemaking tools useful on the web. To me your phrase "convenient software tools for facilitating development and implementation of an online discussion agenda" (I'm not aware of any) is a key part of the design of any significant step forward in the utility of sensemaking tools. Current discussion-oriented tools show great progress in the design, presentation, and editing capabilities of nodes (ideas/issues/positions) and connections (relationships). One gap to fill is in goal oriented behavior. We want to achieve some end (e.g. a decision or the creation of a consensus document for a given topic). How do we facilitate that? What set of behaviors are needed? What sort of software aid might guide the process?<br />
<br />
We can use our own group, GSm, and its expressed goals as a case in point. What's missing from our environment that might make us more effective as a group working to evolve better sensemaking tools and better usage/integration/federation of existing ones?<br />
<br />
Your "a" to "e" list of candidate approaches is a good set to mine.<br />
<br />
<i>"e. Better tools to better facilitate this kind of free flowing discussion."</i><br />
<br />
To me this is the big gap. Tools exist for a host of sensemaking activities including foraging, annotating, social bookmarking, tagging, even real-time face-to-face discussion mapping, etc., but really nothing that strikes me as particularly effective for facilitating and "capturing" a free flowing online discussion. Seems to me such a tool must incorporate at least your points "c" and "d" above as well as Jack's TopicSpaces. I wonder what the next best step toward such a tool might look like and note that Ning has an open API (which I've never explored).<br />
<br />
<i>"b. expert system development using repertory grid for elicitation and socio grid for comparison. Could we use these tools to make our views more explicit and compare them?</i>"<br />
<br />
A great idea for multiple reasons the first of which is exactly what you state. Beyond that these are tools that are well-defined, useful for discovering and disambiguating topics/subjects, and can be incorporated into a GSm tool suite for that purpose. (A couple days ago I re-read some of the PCP papers and finally "got" -- to some extent -- the theory behind the tools.) Scott,
I would add to your f…tag:globalsensemaking.net,2008-08-19:2052744:Comment:63412008-08-19T19:23:43.000ZAndy Streichhttp://globalsensemaking.net/profile/AndyS
Scott,<br />
<br />
I would add to your fine list:<br />
<br />
6. Ben and cohorts weren't distracted by TV, text messaging, Internet, etc. (Put negatively: what else did they have to do?) Thoughtful dialog was (grossly) analogous to American Idol (just guessing, never seen AI).<br />
<br />
7. They were face-to-face when the Junto met. I think this is the really telling point.<br />
<br />
8. Life was so very different in the 1700's. Life expectancy about half of today's (Ben himself being an outlier). Women relegated to secondary roles and…
Scott,<br />
<br />
I would add to your fine list:<br />
<br />
6. Ben and cohorts weren't distracted by TV, text messaging, Internet, etc. (Put negatively: what else did they have to do?) Thoughtful dialog was (grossly) analogous to American Idol (just guessing, never seen AI).<br />
<br />
7. They were face-to-face when the Junto met. I think this is the really telling point.<br />
<br />
8. Life was so very different in the 1700's. Life expectancy about half of today's (Ben himself being an outlier). Women relegated to secondary roles and too frequently dying in childbirth. Most people were farmers. Urban to rural ration was small. Travel of any sort arduous and communication extremely by our standards. Small minority had access to books and anything other than very basic educational resources. Etc.<br />
<br />
So the Junto offered much that was just not available in any other form in that era. An answer to resolving intell…tag:globalsensemaking.net,2008-08-19:2052744:Comment:63212008-08-19T02:23:57.000ZScotthttp://globalsensemaking.net/profile/ScottNesler
An answer to resolving intelligent arguments within a group framework is hidden in the complexities of Benjamin Franklin's Junto. What I originally glossed over as being a simple group process, now I conclude is an anomaly which has rarely been duplicated in history.<br />
<br />
Egocentricities make it difficult to form a Junto and harder to maintain over a long period of time.<br />
<br />
There are many unknowns of what contributed to the longevity and productivity for Franklin's Junto.<br />
<br />
Some guesses of what led to…
An answer to resolving intelligent arguments within a group framework is hidden in the complexities of Benjamin Franklin's Junto. What I originally glossed over as being a simple group process, now I conclude is an anomaly which has rarely been duplicated in history.<br />
<br />
Egocentricities make it difficult to form a Junto and harder to maintain over a long period of time.<br />
<br />
There are many unknowns of what contributed to the longevity and productivity for Franklin's Junto.<br />
<br />
Some guesses of what led to Franklin's success:<br />
<br />
<ol>
<li>Small group with little turn around or additions. Less time understanding the dynamics and complexities of new personalities. Respect was easier to maintain.</li>
<li>Originally, respect was anticipated as being key, but lately I've determined that anger management and a sophisticated communication process were more important.</li>
<li>The depth and mutual respect of member relationships prevented anger from becoming rooted.</li>
<li>Benjamin Franklin was in his early twenties. I'm assuming the remaining members were below 30. Younger people are less hardened, inquisitive, and open to alternative points of view. Regular meetings at this age could have contributed to a rare indepth respect.</li>
<li>The undivided attention given to a single weekly presenter provided a continual openness for each member.</li>
</ol> Here is one response to this…tag:globalsensemaking.net,2008-08-16:2052744:Comment:63012008-08-16T17:38:08.000ZRobert Parkshttp://globalsensemaking.net/profile/RobertParks
Here is one response to this discussion. First, I'm not sure we've gotten far enough in this discussion to establish a line of argument with respect to sensemaking tools. So DebateGraph, Compendium and TruthMapping may be a bit premature. My thinking on these issues would benefit from a comparison of several candidate approaches to facilitating interactions:<br />
a. open source and other software development models. What procedures from open source interactions would be good to adopt?<br />
b. expert…
Here is one response to this discussion. First, I'm not sure we've gotten far enough in this discussion to establish a line of argument with respect to sensemaking tools. So DebateGraph, Compendium and TruthMapping may be a bit premature. My thinking on these issues would benefit from a comparison of several candidate approaches to facilitating interactions:<br />
a. open source and other software development models. What procedures from open source interactions would be good to adopt?<br />
b. expert system development using repertory grid for elicitation and socio grid for comparison. Could we use these tools to make our views more explicit and compare them?<br />
c. tools for ontology development, comparison and merging. Could/should we be developing a structured vocabulary to facilitate and target the discussion?<br />
d. tools to simulate and facilitate different communication processes, rules, procedures, etc<br />
e. Better tools to better facilitate this kind of free flowing discussion.<br />
<br />
Several people have mentioned different blog/wiki/tagging/discussion tools, and their features. And some tools are being used - such as Diigo and the wiki. But we haven't decided on a method of aggregating/storing/organizing this information. I think we're in the discussion phase, but perhaps the broad agenda doesn't provide a mechanism for creating sub agendas, reporting processes, etc. We have software tools to facilitate direct interaction - such as scheduling tools and calendars. But I'm not sure if there are any convenient software tools for facilitating development and implementation of an online discussion agenda. Am I missing something?<br />
Bob Andy, you haven't looked hard…tag:globalsensemaking.net,2008-08-16:2052744:Comment:62812008-08-16T14:18:20.000ZJack Parkhttp://globalsensemaking.net/profile/JackPark
Andy, you haven't looked hard enough. NOT! You asked me to tell you that, but it's not true. You ask great questions and offer great observations; the simple fact is that any graph/logic-based implementation of knowledge engineering will only get you so far, and no farther. If humans really did use logic, we might not be having this discussion, possibly because we would all be pretty skilled at sensemaking on the fly, we would be much better anticipatory systems than we appear to be, and the…
Andy, you haven't looked hard enough. NOT! You asked me to tell you that, but it's not true. You ask great questions and offer great observations; the simple fact is that any graph/logic-based implementation of knowledge engineering will only get you so far, and no farther. If humans really did use logic, we might not be having this discussion, possibly because we would all be pretty skilled at sensemaking on the fly, we would be much better anticipatory systems than we appear to be, and the big messes du jour would be different than they are now, possibly more tractable, less wicked. Or not.<br />
<br />
We have philosophers since before the famous Greeks who have thought about the very issues you raise; not much has changed, except that we now have computers that let us run simulations of our thinking in ever more powerful ways; computational insight is coming at us faster than the speed of light, and we still do logic and semantic networks, and few people, if any, ever really take the time to figure out what <i>semantic</i> means.<br />
<br />
I once read a book, the title of which escapes me, that spoke in terms of Bayesian "logic"; it made sense that the more times one experiences various events, the more one remembers them, links them to other events, and so forth. I'm not a philosopher and never played one on TV, and so I cannot engage in any deep and profound issue mapping that uses terms like "realist", "sophist", "existentialist" and so forth; what I carry as a belief system is a jumble of intuitions based on my own interpretations of everything I experience; I have a hunch it's like that for most people (leaving "most" to be defined by readers).<br />
<br />
When one writes an ontology of relations, one is making editorial choices; knowledge engineering is like that. What I want to do is to make the smallest possible set of ontological commitments, and then facilitate further ontological choices to be made by stakeholders who use my tools. Cohere, for instance, allows you to create new relation types, but it gives you a rich and well thought out set to start with; in theory, you should be able to make your assertions from the given set of choices, but if not, press on with your own.<br />
<br />
Where things begin to fall apart might be seen to grow out of a hodge-podge of personal choices, some of which might be brilliant contributions, others of which might just be nonsense; that's all part of the game, IMHO. That's why you facilitate online discourse where the nonsense can either be wrestled into sense by the community, or some "usability" or "value" metric grows on the nonsense assertion such that it eventually falls off the radar screen.<br />
<br />
I will assert that the field hasn't progressed much. I will further assert that OWL and it's underlying representation scheme RDF don't "compete" with topic maps, for topic maps can and have been created in OWL. I will finally assert that topic maps are just good old fashioned AI frame-based representations of an indexical-relational type; they carry with them one particular discipline, if you can call it that, which entails aggressive maintenance of the co-location principle: one proxy per subject in any given map (one frame for any given concept in a knowledge base). Others, including ontologies of all kinds, are similarly free to adhere to that discipline.<br />
<br />
Here's a difference worth studying: ontology integration takes a variety of approaches, some of which are lossy. Merging topic maps simply finds proxies that represent the same subject, no matter how they do so, and merge them; the rest come along for the ride without merging. Subtle, sometime profound, sometimes not so profound differences. I did not just say that ontologies cannot be merged in the same way; they probably can.<br />
<br />
Purpose-built. That would describe the general field of knowledge engineering, including topic maps. We build topic maps for representing people, places, and things, just as you would do so with any knowledge base. In my own case, I attempt to reuse representations, to create situations in which shared representations exist. After all, one might create a topic map to engage climatologists, and a different one to engage energy sensemakers; but, the two fields co-exist and co-evolve; they cannot be separated, even though each field has its own ontology; many of those ontological classes are really the same subject, but named differently. Others are intimately related to each other in important ways, some of which we might not yet know about -- unconnected dots, as it were. A primary goal in my work is to facilitate finding and connecting dots in a sense analogous to the early periodic table of the elements which gave indications of un-discovered elements. Can that be pulled off? Watch this space. Regarding the Feigenbaum quot…tag:globalsensemaking.net,2008-08-16:2052744:Comment:62632008-08-16T08:17:00.000ZAndy Streichhttp://globalsensemaking.net/profile/AndyS
Regarding the Feigenbaum quote and my paraphrase, Jack said,<br />
<br />
<em>"I think I see two phases of GSm. Feel free to offer a correction to the vision I carry in my head: Phase 1—precisely as stated in the quote; Phase II—others, including GSm tool builders, using GSm tools, engaged in the building of a large body of codified knowledge around the issues of our times. Well, that's all I have to say about the quote; it's a beauty—it's just that I see it as half of the story."</em><br />
<br />
I agree with Jacks'…
Regarding the Feigenbaum quote and my paraphrase, Jack said,<br />
<br />
<em>"I think I see two phases of GSm. Feel free to offer a correction to the vision I carry in my head: Phase 1—precisely as stated in the quote; Phase II—others, including GSm tool builders, using GSm tools, engaged in the building of a large body of codified knowledge around the issues of our times. Well, that's all I have to say about the quote; it's a beauty—it's just that I see it as half of the story."</em><br />
<br />
I agree with Jacks' two phases and want to drive a couple of points home. Here's phase one again:<br />
<br />
<em>Gsm is the computer-facilitated cooperation of some people in the building of a small body of codified knowledge around the development and use of sensemaking tools. The vision is that dozens of sensemaking tool builders and users would cooperate.</em><br />
<br />
I'm really good at obvious things, it's a special talent. ;-)<br />
<br />
Obvious here is that getting to phase two means actually doing phase one. I know I'm a steady drum beat on this and risk becoming (or have become) background noise, but if we can create a body of knowledge around what makes a sensemaking tool a sensemaking tool and how to develop them, we can get to phase two sooner and with more gusto. I see phase one as the enabling step. If we can't create some sensemaking knowledge about sensemaking tools we likely are just, to put it crudely, pissing up a rope.<br />
<br />
How can we suggest to others they use sensemaking tools in their domains if we aren't using them in our own, if we don't understand and make sense of them? More positively, if we do create a body of knowledge about sensemaking tools, then clearly it will be easier for others to create them going forward.<br />
<br />
Remember David, Simon, and Mark K all have suggested and offered the use of Debategraph, Cohere, and Collabatorium to facilitate the work of GSm — and I think we all have Compendium on our local drives. That's four sensemaking tools getting zero uptake by a community of sensemaking experts, tool builders, and advocates to do the collaborative work of Gsm.<br />
<br />
Partly I just want to leave it there and see how people respond, but I'm not comfortable with that. I see a very positive outcome and want to express it.<br />
<br />
I remember reading in one of Mark's papers, or maybe in Revkin's article about Mark's work, how the Climate Collabatorium could or would allow a user to set up and run a climate simulation with a particular set of parameters. I found that quite inspiring. The idea of an average user kicking off execution of a climate simulation and having the initial parameters and outcome available for all seemed to me a brilliant idea from any number of perspectives.<br />
<br />
Then I discovered Debategraph and it's free service of hosting maps of arguments on any sundry topic and, through it's front page, highlighting the more interesting ones. It comes with a particularly useful argument mapping design built-in. Struck me as a good design for several important situations.<br />
<br />
Along the way I found Compendium, Cohere, and TruthMapping and thought, "Gosh, there's this wealth of knowledge representation, discussion mapping, and argumentation tools that I'd never seen before." As a commercial software developer it seemed to me to be obvious that weaving these tools together had some payoff for everyone. And this is to say nothing of WordSmyth which, as a lexicon, in some sense serves as the base for everything else.<br />
<br />
We've all had similar experiences that lead to the question, "Why doesn't everyone see what I see?"<br />
<br />
Clearly you guys don't see what I do or have your reasons for not talking about it / disagreeing with it. But, in the spirit of the Emporer has no clothes, I don't get it. Why not more explicit cooperation/interest in interoperability between tools? Is it that you don't see the benefit to the user? Don't have time to think about it? Or we haven't established a framework for talking about it? (That last seems viable to me.)<br />
<br />
Or do you think that I'm just wrong about the potential here? If so, why GSm?<br />
<br />
Can anyone shed some light? Jack,
[Your Ning UI experien…tag:globalsensemaking.net,2008-08-16:2052744:Comment:62612008-08-16T06:49:11.000ZAndy Streichhttp://globalsensemaking.net/profile/AndyS
Jack,<br />
<br />
[Your Ning UI experience is not due to FF3, same here in FF2. They don't keep a pointer to the current location in the edit pane. When you are willing, please reveal the source of your special powers in finding & pointing to interesting tools I've never heard of like <a href="http://demo.carrot2.org">http://demo.carrot2.org</a>.]<br />
<br />
Thanks for background and disambiguation regarding topic maps, concept maps and their ilk. In that regard it seems like Debategraph, through its…
Jack,<br />
<br />
[Your Ning UI experience is not due to FF3, same here in FF2. They don't keep a pointer to the current location in the edit pane. When you are willing, please reveal the source of your special powers in finding & pointing to interesting tools I've never heard of like <a href="http://demo.carrot2.org">http://demo.carrot2.org</a>.]<br />
<br />
Thanks for background and disambiguation regarding topic maps, concept maps and their ilk. In that regard it seems like Debategraph, through its constraints on relationships, offers something different because the relationships are specialized and in effect create a nontrivial map grammar, maybe similarly for IBIS style Compendium.<br />
<br />
<em>"Topic maps don't let you get away with just drawing a labeled arc between two concepts; they insist that you create an "ontology" of relation types."</em><br />
<br />
If they are "just" semantic nets that raises my concern that they are <em>no better than</em> semantic nets in that the ontology has to come from somewhere. That is, as a software developer I can see felxibility as a feature and, if necessary, can specify an ontology appropriate to my project. But that takes us back to expert systems as a cottage industry. How do I build on the work of others and incorporate it into what I'm doing? In other words, where do I find and how do I select an existing ontology? If I do that, how do I know what proprieties it has and how they might change over time? Asking this in exactly the same spirit as one might ask where do I get and how do I use an XML parser? There is still a cottage industry of sorts for XML parsers but the interface to using them has been standardized and for many cases the default parser a system offers is expected to be adequate (thinking Java standards here). And there are well known rules about how software components change.<br />
<br />
In creating an expert system I have to interview and distill the knowledge of domain experts to discover appropriate inference rules. Back in the 1980's I'd also be using that same interview information to create an appropriate semantic net to support the knowledge representation end of the system. How does the recasting of semantic nets to topic maps help me, as an engineer, create "better" systems or speed the development of equivalent systems?<br />
<br />
I know little more than there are some competing standards like OWL and RDF and if I bothered to own a personal domain I could establish "Andy Streich" as a unique ID. But what if I wanted to add that I'd been a professional ski instructor? There are people who have taught skiing, people who charged money to teach skiing, people who have been employeed by ski schools to teach skiing, and people who have passed nationally certified exams to qualify as profession ski instructors — all different types that can be easily conflated. Back when I did that sort of thing it was important to me to ensure my students knew I was in that last category, a certified professional.<br />
<br />
In a generalize topic map space how do we determine what "certifiend professional ski instructor means"? Who gets to say? And for the period that the term applied to me? The exam changed over time as did the examiners. And this was alpine as opposed to nordic.<br />
<br />
I'm not criticizing topic maps but rather trying to understand if the field has changed in a significant way since my grad school days 20 years ago. Then we were experimenting with systems where we had to specify the lexicon, the grammar, and the semantic net (every aspect of it) along with the expert system rules and whatever state it needed to maintain — and we had to handle (or more likely avoid) modifications to all these subcomponents. In short every example system was typically purpose-built from the ground up.<br />
<br />
My complaint, if you can call it that, is either that I haven't kept up or the field hasn't progressed much in the last couple of decades in a way that affects software engineering. It's got to be the former, yet I see out no obvious evidence of progress. The space still seems like a cottage industry. Please tell me I just haven't looked hard enough. Nicely stated, Andy. Particul…tag:globalsensemaking.net,2008-08-15:2052744:Comment:62512008-08-15T23:55:11.000ZJack Parkhttp://globalsensemaking.net/profile/JackPark
Nicely stated, Andy. Particularly the opportunity to listen to Ed Feigenbaum, the "father" of expert systems.<br />
<br />
Let me think outloud about this quote: <i>Gsm is "the computer-facilitated cooperation of some people in the building of a small body of codified knowledge around the development and use of sensemaking tools. The vision is that dozens of sensemaking tool builders and users would cooperate."</i><br />
<br />
I think I see two phases of GSm. Feel free to offer a correction to the vision I carry in…
Nicely stated, Andy. Particularly the opportunity to listen to Ed Feigenbaum, the "father" of expert systems.<br />
<br />
Let me think outloud about this quote: <i>Gsm is "the computer-facilitated cooperation of some people in the building of a small body of codified knowledge around the development and use of sensemaking tools. The vision is that dozens of sensemaking tool builders and users would cooperate."</i><br />
<br />
I think I see two phases of GSm. Feel free to offer a correction to the vision I carry in my head: Phase 1--precisely as stated in the quote; Phase II--others, including GSm tool builders, using GSm tools, engaged in the building of a <i>large</i> body of codified knowledge around the issues of our times. Well, that's all I have to say about the quote; it's a beauty--it's just that I see it as half of the story.<br />
<br />
Topic maps. They are semantic nets. So are concept maps, dialogue maps, mind maps, and so forth. They are symbolic representations of human thought--that which we sometimes call "knowledge", organized in a relational way; things are connected to other things, and those connections are important.<br />
<br />
Concept maps, including dialogue maps and mind maps, place less emphasis on the nature of the relationship between the represented concepts (nouns over verbs, perhaps), while mind maps don't even give you a nice way to state a relationship; whatever it is is just implied by the line connecting one thing to another, and the shape of the emerging graph: forks seem to indicate sibling relations, for instance.<br />
<br />
Topic maps don't let you get away with just drawing a labeled arc between to concepts; they insist that you create an "ontology" of relation types (called <i>associations</i> by XML topic maps, and <i>assertions</i> by the TMRM topic maps, which are also known as <i>subject maps</i>).<br />
<br />
An aside: I'm getting tired of the Ning user interface, at least as it behaves on Firefox 3: when I select a phrase and click the italics button, it jumps to the top of the screen; if I'm not paying attention, I end up wrecking whatever I said and have to start over. That's not an acceptable experience.<br />
<br />
Back to topic maps and relations. You not only need to declare an ontology of relation types, you also need to pay attention to role types: the graph that wires two concepts together through some typed relation also declares the roles played. XTM, the XML topic maps specification, requires this, though I've seen people ignore the roles. Subject maps force no such requirement: you are free to create a graph any way you wish, one that even qualifies as a concept map.<br />
<br />
Cohere just happens to allow you to specify roles together with typed relations when connecting annotations. I like that. Very topic mappish!<br />
<br />
What's different? Simply this: if you call something a topic/subject map, you are making a statement to this effect: for any given subject (defined as anything you can think of or talk about that you wish to represent symbolically), there will be one, and only one proxy (representation) for that subject in any given map. That's what's different, though it doesn't imply that concept maps couldn't say the same thing.<br />
<br />
This forces attention to subject identity; in order to guarantee a lone representation for a human who goes by the name "Jack Park", it should be abundantly clear that name-based identification will not be sufficient for a map that promises to cover all possible people with that name. I return to my earlier comment about URIs, one for each subject. The topic maps folks invented the PSI (published subject indicator), essentially the same thing as a URI. PSIs are really good, as are URIs for things we all agree on and, in general, know about. But, if they are the only way we separate subjects, what happens when someone wants to query our topic map for a particular "Jack Park" person? Like a google query, they're going to get possibly many hits. That's not acceptable; we need to, and can do better than that by allowing "keyword" searches, just as does google and all other query engines. The big difference is the potential for reduction of infoglut in query responses; a better-organized search result. To get just a tiny hint at how that works, visit the <a href="http://demo.carrot2.org/demo-stable/main">Carrot2</a> search engine and type in any query you like. I trust the flippancy was obv…tag:globalsensemaking.net,2008-08-15:2052744:Comment:62492008-08-15T22:50:11.000ZAndy Streichhttp://globalsensemaking.net/profile/AndyS
I trust the flippancy was obvious in my parenthetical comment above: "Solve a few knowledge representation problems, add a few hundred rules, and set this on top of Compendium or Debategraph and couple it with TopicSpaces and we've got a great sensemaking game."<br />
<br />
To be less flip, I was thinking about how an fairly small expert system could help a user manipulate a suite of sensemaking tools effectively, and how the construction of that rule set might shed some light on what sensemaking is and…
I trust the flippancy was obvious in my parenthetical comment above: "Solve a few knowledge representation problems, add a few hundred rules, and set this on top of Compendium or Debategraph and couple it with TopicSpaces and we've got a great sensemaking game."<br />
<br />
To be less flip, I was thinking about how an fairly small expert system could help a user manipulate a suite of sensemaking tools effectively, and how the construction of that rule set might shed some light on what sensemaking is and means.<br />
<br />
Writing in 1991 Ed <a href="http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.50.9833">Feigenbaum said</a>, "<i>These two shortcomings of expert systems of the first era — brittleness and isolation — provide shape for the next decade of knowledge-based systems research. While the technology of the first era is being inserted, improved, and applied, a second era of knowledge based systems is being invented. The thrusts of the second era research are concepts of large knowledge bases, knowledge sharing, and the interoperability of knowledge bases that are geographically distributed.</i>"<br />
<br />
My favorite line — "<i>Every expert system appears to be a custom-crafted cottage industry event!</i>" — is about something that seems to be as true today as it was then in 1991 and not just in expert systems. GSm is, I think, an attempt to move sensemaking beyond its custom-crafted cottage industry status.<br />
<br />
Later Feigenbaum says, "<i>Knowledge sharing ... means more than just the knowledge bases of several expert systems interoperating to solve a problem. Knowledge sharing also means the computer-facilitated cooperation of many people in the building of a large body of codified knowledge. The vision is that hundreds or thousands of knowledge base builders would cooperate.</i>"<br />
<br />
I wonder if GSm can be characterized by paraphrasing Feigenbaum like this: Gsm is "the computer-facilitated cooperation of some people in the building of a small body of codified knowledge around the development and use of sensemaking tools. The vision is that dozens of sensemaking tool builders and users would cooperate." Substitute Feigenbaum's statement about knowledge sharing for "sensemaking" and it's a nicely recursive definition.<br />
<br />
That aside, I agree with Jack about the need for topic maps (or some similar "ground of reference") in any such system. I have to do a little work and learn (1) how to distinguish topic maps from semantic nets and (2) how to understand a topic map as a computational unit. By the later, I mean what are their properties and how to I configure them so a topic map can be integrated into another program, say, an expert system. Continuing link repair: see J…tag:globalsensemaking.net,2008-08-15:2052744:Comment:62472008-08-15T21:34:21.000ZAndy Streichhttp://globalsensemaking.net/profile/AndyS
Continuing link repair: see <a href="http://www.globalsensemaking.net/xn/detail/2052744:Comment:6243">Jack's comment above</a>. [Sorry for the confusion and the potential of making it worse by trying to fix it!]
Continuing link repair: see <a href="http://www.globalsensemaking.net/xn/detail/2052744:Comment:6243">Jack's comment above</a>. [Sorry for the confusion and the potential of making it worse by trying to fix it!]