The term originated with computational linguistics and AI. The last time I worked at a company that had a disambiguator, it was code that no one understood, and nobody touched. I image that it wasn’t commented.
Tagging things reduces the need for computational recognition, or disabiguating. Parsing is much easier.
The definition your link lead to said something like establishing a single semantic base of interpretation. Well, that is what is wrong with IT in general, and silo busting specificially. IT doesn’t care about meaning. They manage the blobs that move around the data as aliases for meaning.
One such blob is the content between the tags. We tag the container and make assumptions about the tagged. The tagged still has to be disambiguated.
Sure, I think it’s a perfectly useful term if you’re a computational linguist or an AI scientist. If you’re a software user, even a pretty sophisticated one on a highly specialized tool, it’s going to be one of those words that cause more trouble than they solve. That’s my beef with it, not that it’s a bad word in itself. I’m trying to train tech writers to think like users, put themselves on the other side of the glass, get out of their “expert” hat.
The term originated with computational linguistics and AI. The last time I worked at a company that had a disambiguator, it was code that no one understood, and nobody touched. I image that it wasn’t commented.
Tagging things reduces the need for computational recognition, or disabiguating. Parsing is much easier.
The definition your link lead to said something like establishing a single semantic base of interpretation. Well, that is what is wrong with IT in general, and silo busting specificially. IT doesn’t care about meaning. They manage the blobs that move around the data as aliases for meaning.
One such blob is the content between the tags. We tag the container and make assumptions about the tagged. The tagged still has to be disambiguated.
Sure, I think it’s a perfectly useful term if you’re a computational linguist or an AI scientist. If you’re a software user, even a pretty sophisticated one on a highly specialized tool, it’s going to be one of those words that cause more trouble than they solve. That’s my beef with it, not that it’s a bad word in itself. I’m trying to train tech writers to think like users, put themselves on the other side of the glass, get out of their “expert” hat.