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.
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.