Re: Including content modes in 4.1

>>By the way, it is unwise to continue to refer to human languages as 
>>"natural" languages, no matter how well-understood that term is 
>>among the cognoscenti. Why not call them human languages?
>
>Well, if you want to get picky, HTML and XML and SMIL and C++ and 
>Perl and Visual Basic and Applesoft BASIC are all human languages 
>too.

No, they're not. No human infant grows up speaking them. Next you'll 
be telling us that pacemakers are human organs.

>As long as "natural language" is defined somewhere in a glossary, I 
>think that our use of the term makes sense,

if you intend to confuse laypeople. The Section 508 regs already had 
to explicitly tell people that "natural language" means "human 
language" (and to use lang="" codes to denote it).

>as that is the technical term used by people in the field (e.g. NPL 
>professionals),

If our audience were "NPL professionals," whoever they are, then we 
could live with this kind of jargon, which is to be discouraged 
unless there is no other way to express the concept.

>and the other folks who aren't familiar with this term really should learn it.
>Otherwise our document won't be taken seriously by the people working
>with natural/human languages.

Why should we care?

Our goal is getting real people to make accessible Web sites, not to 
show some other cadre of geeks how well-hung we are. We have to make 
our guidelines easy to understand.

>Does this argument seem eerily familiar to anyone else?

Kynn and his victim mentality. He's good at rubbing salt into wounds. 
I wonder why you all love him so much.
-- 
         Joe Clark | joeclark@joeclark.org
         Author, _Building Accessible Websites_
         (New Riders Publishing, October 2001)
         Bookpage: <http://joeclark.org/book/>
         Bookblog: <http://joeclark.org/bookblog/>

Received on Tuesday, 31 July 2001 23:34:41 UTC