Another Word For It Patrick Durusau on Topic Maps and Semantic Diversity

January 14, 2011

Communicating Across the Academic Divide – Post

Filed under: Marketing,Semantic Diversity — Patrick Durusau @ 5:57 am

Communicating Across the Academic Divide

Myra H. Strober writes:

However, while doing research for my new book, Interdisciplinary Conversations: Challenging Habits of Thought, I found an even more fundamental barrier to interdisciplinary work: Talking across disciplines is as difficult as talking to someone from another culture. Differences in language are the least of the problems; translations may be tedious and not entirely accurate, but they are relatively easy to accomplish. What is much more difficult is coming to understand and accept the way colleagues from different disciplines think—their assumptions and their methods of discerning, evaluating, and reporting “truth”—their disciplinary cultures and habits of mind.

I rather like the line: Talking across disciplines is as difficult as talking to someone from another culture.

That is the problem in a nutshell isn’t it?

What most solution proposers fail to recognize is that solutions to the problem are cultural artifacts themselves.

There is no place to stand outside of culture.

So we are always trying to talk to people from other cultures. Constantly.

Even as we try to solve the problem of talking to people from other cultures.

Realizing that does not make talking across cultures any easier.

It may help us realize that the equivalent of talking louder, isn’t likely to assist in the talking across cultural divides.

One of the reasons why I like topic maps is that it is possible, although not easy, to capture subject identifications from different cultures.

How well a topic map does that depends on the skill of its author and those contributing information to the map.

January 13, 2011

Infosomics

Filed under: Examples,Marketing,Topic Maps — Patrick Durusau @ 7:21 pm

Reading The Newsonomics of 2011 news metrics to watch I was reminded that topic maps lack a notion of infosomics.

That is a metric, any metric, to measure the benefit that a user derives from the use of a topic map.

I have heard lots of anecdotal stories but no hard numbers.

Consider the listing of search engines you will find at: Choose the Best Search for Your Information Need.

A useful listing and no doubt similar advice exists for search appliances, but none of which results in any hard numbers.

For example, say I am responsible for tech support for a particular software package. There is a collection of prior tech support requests with answers, manuals and other materials. Not to mention tech support staff who have general support training and training on this product in particular.

What I want to know is what measurable metrics, reduced length of support calls, lack of repeated calls from the same customer (same issue), higher customer satisfaction, I can expect from using a topic map?

The same sort of metrics that I haven’t seen (overlooked?) for any of the search appliances.

The best case scenario would be to have a vendor with multiple help desk operations that were basically equivalent and to set up one office with a topic map solution and the other office uses its current solution. Use automated monitoring to derive the metrics.

I prefer that sort of metric to “…someday we will all be one giant linked graph/topic map/insert your solution” type claims.

The latter being hard to evaluate in any meaningful way.

Topic Maps – Human-oriented Semantics?
(streaming video – 14.01.2011 12:00 GMT)

Filed under: Marketing,Topic Maps — Patrick Durusau @ 5:41 am

Topic Maps – Human-oriented Semantics?

Lars Marius Garshol has a topic maps presentation tomorrow in Sogndal.

I won’t be in Norway tomorrow but there will be a streaming video of the presentation.

Despite the 7 AM start time on the East Coast of the US I plan on attending.

Lars has either authored or contributed to every aspect of the topic maps effort for the past decade.

I will find something to disagree with in his presentation, for old times sake if nothing else, but I am sure it will be an interesting presentation.

Please spread the word about this presentation.

January 6, 2011

10 Ways to be a Marketing Genius Like Lady Gaga

Filed under: Marketing — Patrick Durusau @ 3:39 pm

10 Ways to be a Marketing Genius Like Lady Gaga

Just another log for the discussion of how to market topic maps.

A very amusing slide deck that could prove to be quite useful.

I am not real sure of an equivalent for the monster claw hand as marketing for topic maps. Suggestions welcome!

January 5, 2011

Bribing Statistics

Filed under: Data Source,Marketing,Software — Patrick Durusau @ 1:03 pm

Bribing Statistics by Aleks Jakulin.

Self reporting (I paid a bribe is the name of the application) of bribery in the United States is uncommon, at least characterized as a bribe.

There are campaign finance reports and analysis that link organizations/causes to particular candidates. Not surprisingly, candidates vote in line with their major sources of funding.

The reason I mention it here is to suggest that topic maps could be used to provide a more granular mapping between contributions, office holders (or agency staff) and beneficiaries of legislation or contracts.

None of those things exist in isolation or without identity.

While one researcher might only be interested in DARPA contracts (to use a U.S. based example), the contract officers and the beneficiaries of those contracts, another researcher may be collecting data on campaign contributions that may include some of the beneficiaries of the DARPA contracts.

Topic maps are a great way to accumulate that sort of research over time.

January 3, 2011

Zotero – Software

Filed under: Bibliography,Marketing,Software — Patrick Durusau @ 2:55 pm

Zotero

I don’t remember now how I stumbled across interesting project.

Looks like fertile ground for the discussion of subject identity.

Particularly since shared bibliographies are nice but merged bibliographies would be better.

Drop in, introduce yourself and topic map thinking about subject identity.

January 1, 2011

Happy New Year! – Wikileaks

Filed under: Marketing,Topic Maps — Patrick Durusau @ 9:11 pm

Wikileaks has continued posting US diplomatic cables.

The stories read like Extra but with less attractive people.

According to Sec. of State Hillary Clinton, one counterpart said of the Wikileaks’ posting of US diplomatic cables:

Well, don’t worry about it, you should see what we say about you

It’s not clear if they meant Hillary or the United States. 😉

But I’m curious either way. Let’s see diplomatic cables from other countries.

Imagine the Guardian map with cables from multiple countries?

Or mapping relationships between the various people and current government figures?

Or mapping those relationships over careers of toleration or even encouragement of repressive or brutal regimes?

Disclosure of diplomatic cables should be encouraged.

For the same reason disclosure is feared. Accountability.

Such as judging why the United States and other countries have tolerated post WWII episodes of ethnic cleansing.

*****
PS: This would make good subject matter for a public authoring interface to invite contributions from others.

December 23, 2010

Speller Challenge II

Filed under: Marketing — Patrick Durusau @ 1:56 pm

After posting Speller Challenge, it occurred to me that the contest name is mis-leading.

It really isn’t a speller contest as much as it is a spelling-check contest.

That is a speller implies being able to correctly spell words in some language. A semester NLP or AI type project.

What is needed for this contest is a spelling-check that recognizes likely completions and reports for any given completion, all the variant spellings.

Deriving that solution would have two parts:

First, data mining to determine all the variants (and their frequency) for any given completion. With search logs it should be possible to keep track of variants by locale but the contest did not ask for that. Save that for a future refinement.

Second, the topic map part, would be to represent all the variants of a completion as an association. Such that the retrieval of any one completion includes pointers to all of its variant completions.

I would treat all the completions as variants with incidence/frequency values. That is they play the role of variant in a variant-of association.

Since we are talking about internal representation, I would not represent either the association type or the roles in the data structure. There isn’t any merging or interchange going on so optimize for speed of response.

Will still need to contend with completions that are members of different associations. That is the completion stands for a different subject.

In any given variant-of association, all the variants represent the same subject.

Will have to give some thought on how to distinguish identical completions that are members of different associations.

(more to follow)

Forbes: R is a name you need to know in 2011 – Post

Filed under: Marketing — Patrick Durusau @ 6:15 am

Forbes: R is a name you need to know in 2011

The Revolutions blog reports that Forbes has named R as a name you need to know in 2011.

I mention that story for two reasons:

First, it illustrates the importance that the business community is placing on data mining. Usefully combining the results of data mining (can you say “topic maps?”) seems like a natural next step.

Second, it sets a high water mark for the business community becoming aware of a technology. Something for us to collectively shot for in the future.

R for topic maps anyone?

November 30, 2010

Peer-to-Peer Networks?

Filed under: Marketing,Topic Maps — Patrick Durusau @ 11:49 am

Take some paper and write down your definition of a “peer-to-peer” network. No more than a paragraph and certainly not more than a page.

Then answer the following questions:

  1. Is sharing data essential to your definition?
  2. Are libraries peers if they have common users?
  3. Are books/journals peers if they have common readers?
  4. How should we deal with semantic inconsistency between peers?

Suggestion: Don’t confuse how something is done with it being done. Technique is important in terms of performance and other trade-offs but the question here is one of underlying principles. Once those are uncovered, then we can discuss how best to put them into practice.

For example, would you consider ants and bees to have social networks? Perhaps even peer-to-peer networks? Leaving aside swarm theory for the moment, just think about how you think information is conveyed in a colony/hive.

Hans Rosling: Let my dataset change your mindset

Filed under: Marketing,Topic Maps — Patrick Durusau @ 11:23 am

Hans Rosling: Let my dataset change your mindset

Not strictly relevant to topic maps per se, but it does illustrate the sort of demonstration of power that would make an excellent marketing tool for topic maps.

As a “text” person, I then to think of things I would want with a text but that isn’t likely to be exciting for the average customer for topic maps.

What about “interchangeable” mashups? People do mashups all the time (or so I am told) but re-use is about 0 unless you are wiling to simply accept the other mashup.

Even if you watch to see what is being mashed together, that doesn’t mean the same rule will be applied tomorrow. Or that your reliance on it will stop should the rule change.

Questions:

  1. What is your favorite mashup? What is the most popular mashup?
  2. What facts would you want to add to either mashup to make it re-usable? (3-5 pages, citations)
  3. How would you demonstrate graphically the impact a topic map had on your favorite mashup? (Presentation, mock-up acceptable, real time much better)

PS: If anyone is working on this, I would be more than happy to volunteer some time to assist.

PPS: More of a long term idea than an immediate project but the “Plum Book” lists all the positions that are appointed by Presidents. It is published every four (4) years and is available as HTML starting with 1996.

Thinking that presents very amusing possibilities combined with campaign finance disclosures. Could answer important questions like: Have the prices of positions, adjusted for inflation, fallen in 2014?

November 28, 2010

Ontologies, Semantic Data Integration, Mono-ontological (or not?)

Filed under: Marketing,Medical Informatics,Ontology,Semantic Web,Topic Maps — Patrick Durusau @ 10:21 am

Ontologies and Semantic Data Integration

Somewhat dated, 2005, but still interesting.

I was particularly taken with:

First, semantics are used to ensure that two concepts, which might appear in different databases in different forms with different names, can be described as truly equivalent (i.e. they describe the same object). This can be obscured in large databases when two records that might have the same name actually describe two different concepts in two different contexts (e.g. ‘COLD’ could mean ‘lack of heat’, ‘chronic obstructive lung disorder’ or the common cold). More frequently in biology, a concept has many different names during the course of its existence, of which some might be synonymous (e.g. ‘hypertension’ and ‘high blood pressure’) and others might be only closely related (e.g. ‘Viagra’, ‘UK92480’ and ‘sildenafil citrate’).

In my view you could substitute “topic map” everywhere he says ontology, well, except one.

With a topic map, you and I can have the same binding points for information about particular subjects and yet not share the same ontological structure.

Let me repeat that: With a topic map we can share (and update) information about subjects, even though we don’t share a common ontology.

You may have a topic map that reflects a political history of the United States over the last 20 years and in part it exhibits an ontology that reflects elected offices and their office holders.

For the same topic map, to which I contribute information concerning those office holders, I might have a very different ontology, involving offices in Hague.

The important fact is that we could both contribute information about the same subjects and benefit from the information entered by others.

To put it another way is the different being mono-ontological or not?

Questions:

  1. Is “mono-ontological” another way of saying “ontologically/logically” consistent? (3-5 pages, citations if you like)
  2. What are the advantages of mono-ontological systems? (3-5 pages, citations)
  3. What are the disadvantages of mono-ontological systems? (3-5 pages, citations)

November 27, 2010

Successful Data Integration Projects Require A Diverse Approach

Filed under: Data Integration,Marketing,Topic Maps — Patrick Durusau @ 9:57 pm

Successful Data Integration Projects Require A Diverse Approach (may require registration)

Apologies but even though you may have to register (free), I thought this story was worth mentioning.

If just for the observation that ETL (extract, transform, load) is “…a lot like throwing a bomb when all that’s needed is a bullet.” I have a less generous explanation but perhaps another time.

My point here is that data integration is a hot topic and topic maps can be part of the solution set.

No, I am not going to do one of those “…window of opportunity is closing…” routines because:

1) The MDM (master data management) folks haven’t cracked this nut since the 1980’s.

2) The Semantic Web effort, with a decade of hard work, has managed to re-invent the vocabulary problem in URIs. (I still think we should send the W3C a fruit basket.)

3) Every solution is itself an opportunity for subject identity integration with other solutions. (It is a self-perpetuating business opportunity. Next to having an addictive product, the best kind.)

Making topic maps relevant to data integration is going to require that we move away from the file format = topic maps approach.

Customers should understand that topic maps put them in change of managing their data, with their identifications. (With the potential to benefit from other identifications of the same subjects.)

That is the real diversity in data integration.

November 26, 2010

Publication, Publication

Filed under: Marketing,Topic Maps — Patrick Durusau @ 11:33 am

Publication, Publication is the location of Gary King’s paper by the same title, with updates to the paper and related resources.

The paper is details how to take students through replication of an existing published article. In order to teach students how produce professional quality papers by having the original and their attempt to replicate it.

I mention it because topic maps are sorely lacking in a publication record. At least in professional, trade and popular literature.

Maybe due to the lack of a marketing person, something that was mentioned recently. 😉

But, like a blog, it could not be just one piece replicated a bunch of times or just an occasional blurb.

It would have to be a steady drum beat, both theoretical (yes, I used the “T” word) as well as practical pieces.

I will be looking for takers in professional and trade literature, not in replies here.

Questions (of course there are questions, this is a topic maps class):

  1. What journal or magazine (print/online) would you suggest for a topic map article? What should that article focus on and why? (2-3 pages)
  2. What federal or state agency do you think needs a topic map? Be specific with references to resources illustrating the problem to be solved. (3-5 pages, citations)
  3. What is the most compelling story line for topic maps in general? For a specific case? Write 1 pagers for both.
  4. Replicate a paper (chosen with instructor, semester project).

November 19, 2010

“…an absolute game changer”

Filed under: Linked Data,LOD,Marketing,Semantic Web — Patrick Durusau @ 1:27 pm

Aldo Bucchi write that http://uriburner.com/c/DI463N is:

Single most powerful demo available. Really looking fwd to what’s coming next.

Let’s see how this shifts gears in terms of Linked Data comprehension.
Even in its current state, this is an absolute game changer.

I know this was not easy. My hat goes off to the team for their focus.

Now, just let me send this link out to some non-believers that have
been holding back my evangelization pipeline 😉

I may count as one of the “non-believers.” 😉

Before Aldo throws open the flood gates on his “evagenlization pipeline,” let me observe:

The elderly gentlemen appears in: Tropical grassland, Desert, Temperate grassland, Coniferous forest, Flooded grassland, Mountain grassland, Broadleaf forest, Tropical dry forest, Rainforest, Taiga, Tundra, Urban, Tropical coniferous forests, Mountains, Coastal, and Wetlands.

So he must get around a lot.

Only the BBC appears in Estuaries.

Granting that is a clever presentation of subjects that share a common locale and works fairly responsively but that hardly qualifies as a “…game changer…”

This project is a good experiment on making information more accessible.

Why aren’t the facts enough?

November 17, 2010

Maintainability, Auditability, eXtensibility – MAX Reconciliation

Filed under: Marketing,Topic Maps — Patrick Durusau @ 6:57 am

Maintainability, Auditability, eXtensibility – MAX Reconciliation

Don’t take this the wrong way, Google Refine 2.0 is a nice piece of work.

But for:

Maintainability

Auditability

eXtensibility

or MAX Reconciliation,

you are going to need something more.

I am not going to pitch an Ur data model to “bind them and in the darkness rule them.”

You and your users understand their subjects and can create the best subject identity model for their data.

I am suggesting that you leave room to make explicit the implicit knowledge that identifies your subjects.

How much of that you want to make explicit is a design choice.

The more subject identifications you do make explicit, the easier reliable reconciliation that can be audited and extended will become.

None of those may be values for your project, but if they are…, well, you know what comes next.

November 15, 2010

Extensible Reconciliation

Filed under: Marketing,Topic Maps — Patrick Durusau @ 7:34 pm

Your boss tells you another group in your company is “reconciling” data from a “different” perspective.

His boss wants both sets of data reconciled with each other. And to have the separate views as well.

How hard could it be?

You have free software in the form of Google Refine 2.0

This is beginning to sound like a Ballywood horror movie.

You have no explicit basis for reconciling your data, no documented rules* and the other project is in the same shape.

It will take endless meetings to thrash out an implicit mapping that enables the “reconciliation” of the “reconciliations.”

Which works until either group encounters new data that needs to be “reconciled.”

If you could only treat data structures as first class subjects, which have sets of key/values pairs, then reconciliation and new data would not be such a pain.

Then your reconciliation would be extensible.

Well, it is extensible now, but it is painful and error prone.

Unfortunately that thought comes as you are getting another Botox shot so you can sit through another “reconciliation” meeting.

*No documented rules. To say “When you see X, do Y.” is a recipe, not a rule. Rules imply some modicum of understanding.

Auditable Reconciliation

Filed under: Marketing,Topic Maps — Patrick Durusau @ 5:38 pm

You made it back from your down time and your employer is glad to see you back.

“Some of the “reconciled” data we have been getting looks odd. Can you audit the data to make sure it is being reconciled correctly? Thanks!”

You remember that all you have are bare tokens.

AnHai Doan’s observation about after the fact mappings:

…the manual creation of semantic mappings has long been known to be extremely laborious and error-prone. For example, a recent project at the GTE telecommunications company sought to integrate 40 databases that have a total of 27,000 elements (i.e., attributes of relational tables) [LC00]. The project planners estimated that, without the database creators, just finding and documenting the semantic mappings among the elements would take more than 12 person years.

is ringing in your ears.

Mapping and creating sets of key/values has to be an augmented process, but the existence of sets of key/values pairs enables auditing of the “reconciled data.”

Sets of key/value pairs you don’t have.

*****
PS: Sets of key/value pairs = subject proxies, with rules for “reconciliation” to use Googleease.

To say “key/value pairs” does not presume any particular methodology for storage or processing. Pick one. Let usefulness be your guide.

Maintainable Reconciliation

Filed under: Marketing,Topic Maps — Patrick Durusau @ 5:24 pm

You have downloaded Google Refine 2.0 and are busy “reconciling” data.

Say you are one of the lucky ones and this is for your employer. 😉

Now you need to work on another project or even take some downtime.

So, how do you hand off maintenance of “reconciling” data?

A reconciliation on which your employer now relies.

You recognize the data to be reconciled but there are two problems:

  1. The raw data has implied properties you are using to reconcile the data. That means there isn’t anything for you to point anyone to as a basis for reconciliation. Just as well because:
  2. The rules for reconciling the data exist only in your head. So, the properties being implicit isn’t such an issue, the rules for handling it aren’t written down either.

Flatland identity as far as the eye can see.

If you had a defined set of properties (key/value pairs) as the basis for reconciliation, you could also say how to carry out the reconciliation.

And your data would be maintainable.

Best of luck with your downtime.

*****
PS: BTW, if you think documenting the names and locations of the data you are integrating counts as documentation, think again. What happens when new data comes along? Data your boss is going to expect to be integrated.

November 12, 2010

I See What You Mean

Filed under: Authoring Topic Maps,Marketing,Topic Maps — Patrick Durusau @ 6:28 pm

A recent email from Andrew S. Townley reminded me of a story I heard from my father decades ago.

Circa rural Louisiana, USA, early 1930’s. A friend had just completed a new house and asked the local plumber to come install the “commode.” When the plumber started gathering up his tool kit, the friend protested that he didn’t need to bring “all that” with him. That he had done this many times before. The plumber persisted on the grounds it was better to be prepared so he would not have to return for additional tools.

When they arrive at the new house, the plumber finds he is to install what is known to him as a “toilet.”

Repeating the term “commode” over and over again would not have helped, nor in a modern context, would having a universal URI for “commode.”

What would help, and what topic maps offer, is a representative for the subject that both “commode” and “toilet” name. A representative that contains properties that authors thought identify the subject it represents.

That enables either party to the conversation to do two very important things:

  • Search for subjects in the way most familiar to them.
  • Examining properties of the subject to see if it is the subject they were seeking.

One more important thing, if they are editing a topic map:

  • Add additional properties that identify the subject in yet another way.

Understanding what others mean in my experience has been asking the other person to explain what they mean in different ways until I finally stumble upon one when I say: “I see what you mean!”

Topic maps are a way to bring “I see what you mean” to information systems.

*****
I am glossing over representatives containing properties of all sorts, not just those that identify a subject and that which properties identify a subject are declared.

What is critical to this post is that different people identify the same subjects differently and assign them different properties.

Intellectual credit for this post goes to Michel Biezunski. Michel and I had a conversation years ago where Michel was touting the phrase: “See What I Mean” or SWIM. I think my formulation fits the story better but you decide which phrasing works best for you.

November 8, 2010

Ambiguity and Linked Data URIs

Filed under: Ambiguity,Linked Data,Marketing,RDF,Semantic Web,Topic Maps — Patrick Durusau @ 6:14 am

I like the proposal by Ian Davis to avoid the 303 cloud while try to fix the mistake of confusing identifiers with addresses in an address space.

Linked data URIs are already known to be subject to the same issues of ambiguity as any other naming convention.

All naming conventions are subject to ambiguity and “expanded” naming conventions, such as a list of properties in a topic map, may make the ambiguity a bit more manageable.

That depends on a presumption that if more information is added and a user advised of it, the risk of ambiguity will be reduced.

But the user needs to be able to use the additional information. What if the additional information is to distinguish two concepts in calculus and the reader is innocent of even basic algebra?

That is that say ambiguity can be overcome only in particular contexts.

But overcoming ambiguity in a particular context may be enough. Such as:

  • Interchange between intelligence agencies
  • Interchange between audited entities and their auditors (GAO, SEC, Federal Reserve (or their foreign equivalents))
  • Interchange between manufacturers and distributors

None of those are the golden age of seamless knowledge sharing and universal democratization of decision making or even scheduling tennis matches sort of applications.

They are applications that can reduce incremental costs, improve overall efficiency and perhaps contribute to achievement of organizational goals.

Perhaps that is enough.

November 3, 2010

The Semantic Web Garden of Eden

Filed under: Marketing,RDF,Semantic Web,Topic Maps — Patrick Durusau @ 6:48 pm

The Garden of Eden:

[2:19] And out of the ground the LORD God formed every beast of the field, and every fowl of the air; and brought them unto Adam to see what he would call them: and whatsoever Adam called every living creature, that was the name thereof….[1]

As the number of Adams and Eves multiplied, so did the names of things.

Multiple names for the same things, different things with the same names.

Ambiguity had entered the world.

The Semantic Web Garden of Eden sought to banish ambiguity:

…by an RDF statement having…URIrefs are used to identify not only the subject of the original statement, but also the predicate and object, instead of using the words “creator” and “John Smith” [2]

As the number of URIs multipled, so did the URIs of things.

Multiple URIs for the same things, different things with the same URIs.

Ambiguity remains in the world.

******
[1] Genesis 2:19
[2] RDF Primer, 2.2 RDF Model, http://www.w3.org/TR/rdf-primer/

October 31, 2010

7. “We always know more than we can say, and we will always say more than we can write down.”

Filed under: Authoring Topic Maps,Knowledge Management,Marketing,Topic Maps — Patrick Durusau @ 7:59 pm

Knowledge Management Principle Seven of Seven (Rendering Knowledge by David Snowden)

We always know more than we can say, and we will always say more than we can write down. This is probably the most important. The process of taking things from our heads, to our mouths (speaking it) to our hands (writing it down) involves loss of content and context. It is always less than it could have been as it is increasingly codified.

Authoring a topic map always involves loss of content and context.

The same loss of content and context has bedeviled the AI community for the last 50 years.

No one can control the loss content and context or even identify it ahead of time.

Testing topic maps on users will help bring them closer to user expectations.

October 30, 2010

6. “The way we know things is not the way we report we know things.”

Filed under: Authoring Topic Maps,Knowledge Management,Marketing,Topic Maps — Patrick Durusau @ 12:14 pm

Knowledge Management Principle Six of Seven (Rendering Knowledge by David Snowden)

The way we know things is not the way we report we know things. There is an increasing body of research data which indicates that in the practice of knowledge people use heuristics, past pattern matching and extrapolation to make decisions, coupled with complex blending of ideas and experiences that takes place in nanoseconds. Asked to describe how they made a decision after the event they will tend to provide a more structured process oriented approach which does not match reality. This has major consequences for knowledge management practice.

It wasn’t planned but appropriate this should follow Harry Halpin’s Sense and Reference on the Web.

Questions:

  1. Find three examples of decision making that differs from the actual process.
  2. Of the examples reported in class, would any of them impact your design of a topic map? (3-5 pages, no citations)
  3. Of the same examples, would any of them impact your design of a topic map interface? (3-5 pages, no citations)
  4. Do you consider a topic map and its interface to be different? If so, how? If not, why not? (3-5 pages, no citations)

October 29, 2010

5. “Tolerated failure imprints learning better than success.”

Filed under: Authoring Topic Maps,Knowledge Management,Marketing,Topic Maps — Patrick Durusau @ 7:24 am

Knowledge Management Principle Five of Seven (Rendering Knowledge by David Snowden)

Tolerated failure imprints learning better than success. When my young son burnt his finger on a match he learnt more about the dangers of fire than any amount of parental instruction could provide. All human cultures have developed forms that allow stories of failure to spread without attribution of blame. Avoidance of failure has greater evolutionary advantage than imitation of success. It follows that attempting to impose best practice systems is flying in the face of over a hundred thousand years of evolution that says it is a bad thing.

Perhaps with fingers and matches, but I am not sure “failure imprints learning better than success” in knowledge management.

The perennial failure (as opposed to the perennial philosophy), the effort to create a “perfect” language, now using URIs, continues unabated.

The continuing failure to effectively share intelligence is another lesson slow in being learned.

Not that “best practices” would help in either case.

Should failure of “perfect” languages and sharing be principles of knowledge management?

October 28, 2010

4. “Everything is fragmented.”

Filed under: Authoring Topic Maps,Knowledge Management,Marketing,Topic Maps — Patrick Durusau @ 6:12 am

Knowledge Management Principle Four of Seven (Rendering Knowledge by David Snowden)

Everything is fragmented. We evolved to handle unstructured fragmented fine granularity information objects, not highly structured documents. People will spend hours on the internet, or in casual conversation without any incentive or pressure. However creating and using structured documents requires considerably more effort and time. Our brains evolved to handle fragmented patterns not information.

I would rather say that complex structures exist just beyond the objects we handle in day to day conversation.

The structures are there, if and when we choose to look.

The problem Snowden has identified is that most systems can’t have structures “appear” when they “look” for them.

Either the objects fit into some structure or they don’t from the perspective of most systems.

Making those structures, that normally appear only when we look, explicit, is the issue.

Explicit or not, none of our objects have meaning in isolation from those structures.

To make it interesting, we all bring slightly different underlying structures to those objects.

(Making assumed or transparent structures explicit is hard. Witness the experience of markup.)

October 27, 2010

3. “In the context of real need few people will withhold their knowledge.”

Filed under: Authoring Topic Maps,Knowledge Management,Marketing,Topic Maps — Patrick Durusau @ 5:58 am

Knowledge Management Principle Three of Seven (Rendering Knowledge by David Snowden)

In the context of real need few people will withhold their knowledge. A genuine request for help is not often refused unless there is literally no time or a previous history of distrust. On the other hand ask people to codify all that they know in advance of a contextual enquiry and it will be refused (in practice its impossible anyway). Linking and connecting people is more important than storing their artifacts.

I guess the US intelligence community has a “previous history of distrust” and that is why some 9 years after 9/11 effective intelligence sharing remains a fantasy.

People withhold their knowledge for all sorts of reasons. Job security comes to mind. Closely related is self-importance. Followed closely by revelation of incompetence. General insecurity, and a host of others.

Technical issues did not create the need for semantic integration. Technical solutions will not, by themselves, result in semantic integration.

October 26, 2010

2. “We only know what we know when we need to know it.”

Filed under: Authoring Topic Maps,Knowledge Management,Marketing,Topic Maps — Patrick Durusau @ 7:29 am

Knowledge Management Principle Two of Seven (Rendering Knowledge by David Snowden)

We only know what we know when we need to know it. Human knowledge is deeply contextual and requires stimulus for recall. Unlike computers we do not have a list-all function. Small verbal or nonverbal clues can provide those ah-ha moments when a memory or series of memories are suddenly recalled, in context to enable us to act. When we sleep on things we are engaged in a complex organic form of knowledge recall and creation; in contrast a computer would need to be rebooted.

An important principle both for authoring and creating useful topic maps.

A topic map for repairing a jet engine could well begin by filming the repair multiple times from different angles.

Then have a mechanic describe the process they followed without reference to the video.

The differences are things that need to be explored and captured for the map.

Likewise, a map should not stick too closely to the “bare” facts needed for the map.

People using the map will need context in order to make the best use of its information.

What seems trivial or irrelevant, may be the clue that triggers an appropriate response. Test with users!

*****

PS: Don’t forget that the context in which a topic map is *used* is also part of its context.

October 25, 2010

1. “Knowledge can only be volunteered it cannot be conscripted.”

Filed under: Knowledge Management,Marketing,Topic Maps — Patrick Durusau @ 6:39 am

Knowledge Management Principle One of Seven (Rendering Knowledge by David Snowden)

Knowledge can only be volunteered it cannot be conscripted. You can’t make someone share their knowledge, because you can never measure if they have. You can measure information transfer or process compliance, but you can’t determine if a senior partner has truly passed on all their experience or knowledge of a case.

To create successful topic maps, there must be incentives for sharing the information that forms the topic map.

Sharing of information should be rewarded, frequently and publicly, short and long term.

Example of failure to create incentives for sharing information: U.S. Intelligence Community.

If your organization, business, enterprise, government, government-in-waiting deserves better than that.

Create incentives for sharing information and start building topic maps today!

October 24, 2010

Recognizing Synonyms

Filed under: Marketing,Subject Identity,Synonymy — Patrick Durusau @ 11:04 am

I saw a synonym that I recognized the other day and started wondering how I recognized it?

The word I had in mind was “student” and the synonym was “pupil.”

Attempts to recognize synonyms:

  • spelling: student, pupil – No.
  • length: student 7 letters, pupil 5 letters – No.
  • origin: student – late 14c., from O.Fr. estudient , pupil – from O.Fr. pupille (14c.) – No. [1]
  • numerology: student (a = 1, b = 2 …) student = 19 + 20 + 21 + 4 + 5 + 14 + 20 = 69 ; pupil = 16 + 21 + 16 + 9 + 12 = 74 – No [2].

But I know “student” and “pupil” to be synonyms.[3]

I could just declare them to be synonyms.

But then how do I answer questions like:

  • Why did I think “student” and “pupil” were synonyms?
  • What would make some other term a synonym of either “student” or “pupil?”
  • How can an automated system match my finding of more synonyms?

Provisional thoughts on answers to follow this week.

Questions:

Without reviewing my answers in this series, pick a pair of synonyms and answer those three questions for that pair. (There are different answers than mine.)

*****

[1] Synonym origins from: Online Etymology Dictionary

[2] There may be some Bible code type operation that can discover synonyms but I am unaware of it.

[3] They are synonyms now, that wasn’t always the case.

« Newer PostsOlder Posts »

Powered by WordPress