Radoslaw

You miss the point - again. To some extent you have an excuse in that David 
Alcock dropped a vital "was" in the title of this thread so you may be unaware 
of the context this time. It was never about language; it's about accuracy 
and, now, respect. The last time this all flared up - in June 2007 - I recall 
that 
you made similar arguments.

> This is simply part of language we use.

That'll be "misuse".

We have now established there are 3 difficulties with the misuse of "USS" and 
I'll just copy what I placed in another post:

1. "USS" is ambiguous when TELNET, possibly TN3270, is under discussion
2. "USS" can be mistaken as *only* meaning UNIX System Services
3. The risk for a maintenance query to be misrouted when "USS" is misused as 
a keyword

Last time it was 1. This time it is additionally 2 and last time 3 was 
mentioned 
in a post from Steve Thompson where the misrouting actually happened.


> Like SMS ...

An interesting and revealing choice!

>From http://www-01.ibm.com/software/globalization/terminology/index.jsp

SMS

(1) See Software Management Services.
(2) See storage management subsystem.
(3) See Short Message Service.

This shows IBM formally can cope with initials having multiple significance - 
and it doesn't apply to USS!

Chris Mason

On Wed, 29 Jul 2009 11:29:16 +0200, R.S. 
<[email protected]> wrote:

>Is it so hard to understand that acronym/abbreviation is not a thing
>that IBM or other company could establish?
>
>This is simply part of language we use. USS could mean United States
>Steel, United States Ship, Unix System Services, Unformatted System
>Services, Upload Speed Sense, UltraSonic Soldering, Ubiquitous Synergy
>Seeker and *many other* triplets of words.
>
>Like SMS: for us it's Storage Management Subsystem, but Windows people
>know other meaning and we all us SMS in our mobile phones (not to
>mention Novell SMS). None of these acronyms had to be formally accpepted
>by any company or agency.
>
>In most cases the meaning of acronym is obvious from the context, for
>exceptions it is perfectly OK to make disambiguation at the beginning -
>like "Unix System Services (USS)" or simply avoid acrynyms at all. And
>voila. No holy war is needed.
>
>
>Now I'm going to send SMS that z/OS SMS does not work with MS SMS or
>Novell Netware SMS. <g>
>--
>Radoslaw Skorupka
>Lodz, Poland

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to