All I'm saying is that a clear definition of terms is required if you would like to discuss this. Here or anywhere.

You are welcome to come up with your own terms -- perhaps you are correct in that the search for terms is political and contentious. Don't know.

I came up with my definition many years ago, because the word "terrorism" is way overloaded. I would encourage you to come up with your own. I do not care what that definition is, as long as it is consistent (And btw, once you get something, I'd love to hear it)

As technologist, I think part of our job in this entire WL issue is to be able to help the average layman understand the issues involved. So -- agreement or not -- we should all think through on our own what our analysis is. As anal as they are, semantics matter.

And no, voluntarily watching a TV news channel does not count as terrorism under my definition, unless it also includes dancing with the stars, which I think should be outlawed worldwide (wink)

I think we can separate advocacy from semantics. If not, then we're stuck in these arguments no matter what we do or try. The issue here is that technology, our bread and butter, is becoming intertwined with just about everything in the entire world. And most of the people and system is it now affecting are completely unprepared to deal with it.

I agree that definitions are important, but most people's definitions of terrorism involve something going boom. I'm not as interested in coming up with my own definition as I am in using the terms and definitions that are least likely to be misinterpreted by the largest number of people.

That in itself is a loaded topic... trying to redefine a term is usually either a losing battle (because people won't listen), or an underhanded strategy (because people won't notice). We don't always have the luxury of attaching a glossary to a conversation ;)

This has actually turned into a great technology discussion.

The first thing you have to do, if you're programming inside a business, is come to agreement on terms. The initial thing most people try is some sort of dictionary approach, but after a while you end up realizing that a critical part of a project team's work is to create working definitions of common concepts. This is called the problem domain language (insert long talk which includes Ludwig Wittgenstein here) Words mean something because of the semantic web they are presented in. They have no meaning on their own.

So "Customer" or "Account", while sounding like clear terms, are actually the same problem as "terrorism" Unless you come up with (and own) a definition, analysis will be impossible because of contradictions.

Sorry. Slipped into teacher mode.

This is just stuff I do all the time, so I don't have a problem with creating working definitions, no matter what the topic is. I'd much rather be considered an oddball with my own definitions than circling my tail trying to pin down what things like "war" or "terrorism" is. Because if I'm creating my definitions, I can ensure consistency. Can't do that when you turn that job over to somebody else. Language is extremely slippery.

I thought it was common to invent new terms or repurpose neutral ones rather than subvert common, loaded terms for your own purposes?

I would not call it "oddball", I would call it either "intentionally misleading" or - granting benefit of doubt - a "misjudgment causing more harm than good".

How about "cyberterrorism", a reasonably established term?

The word itself doesn't matter. That's the whole point.

Call it "foo". The point is that I create a symbol that has these attributes. We can then reason about this symbol.

You cannot do this by picking up an already-loaded term and working with it. It doesn't work. So by redefining "foo" or "terrorism" or "cyber-terrorism" or whatnot, you then have to go back to where the old word was used in context and see if it works. In some cases it works. In some cases it does not. You find out all sorts of interesting things by slightly formalizing your language in this manner.