Re: [MACCAWS] alt tags? valid code?
Chris Kaminski <[email protected]>
| Newsgroups | gmane.comp.web.vkit |
|---|---|
| Message-ID | <[email protected]> |
On Monday, July 22, 2002, at 10:34 AM, [email protected] wrote: > So how about, instead of code or markup for (X)HTML os CSS that we > use some non-specific word like *write*. The use of the word code > for this activity is incorrect, as we've all been told, although > that's what the majority of our customer call it, but markup has a > meaning in, say, retail where you mark up prices - i.e. not a > universally understood meaning of the word. A non-specific generic > term like *write* would seem to cover it and get the message > across, at least initially. <shrug /> It's as good a verb as any, AFAIC. > And then we have to look at other jargon. Any views? Only that there will be those who will nit-pick anything the group says or does to death. It's just the nature of some individuals to find fault. They can be invaluable for finding weaknesses in whatever you're doing, but they can also become counter-productive. Dave Winer refers to them as 'weiner boys,' a term much more polite than the ones I typically use. Terminology aside, the best method I've seen for dealing with them is to pick a single, consistent position and lay it out in an FAQ. When one of them starts winging, politely inform them that the issue has been settled and point them at the FAQ. If they persist, a reminder that the topic is currently closed for discussion is in order along with a gentle warning that further attempts to re-open the topic will be viewed as off-topic and appropriate action taken. The debate about 'code,' 'write,' 'mark-up,' etc. is prime fodder for weiner boys, and should be kept as short as possible lest it bog the group down. The terminology decision should be made by the SC, and the rest of the group (including myself, of course) should then be grown-ups about letting it stand. chris.kaminski { functionNewMedia :: <http://www.function.de> }