[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: "Smart ASCII" -> XML for authoring?

• To: <xml-dev@l...>
• Subject: Re: "Smart ASCII" -> XML for authoring?
• From: Michael Smith <smith@x...>
• Date: Mon, 4 Feb 2002 08:09:46 -0600
• In-reply-to: "Rick Jelliffe"'s message of "Sun, 3 Feb 2002 13:29:30 +1100"
• References: <PLYXVRWRE0GECBRO3VQM8273GCPNMGSP.3c5c2bc3@MChamp><3C5C4327.3060601@b...><005001c1ac5a$9bdb5000$4bc8a8c0@A...>
• User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1

"Rick Jelliffe" <ricko@a...> writes:

> From: "Bill Lindsey" <bill@b...>
> 
> [...]
> 
> > I don't expect the casual user to ever become comfortable
> > with angle brackets, 
> 
> But is XML used by "casual users"?    Or is XML more like 
> programming languages, where there is arguably no such thing
> as a "casual programmer" (i.e., someone who starts
> programming without any specific knowledge of what they are
> doing)  in the way that there is a casual user of a bus (who only 
> needs the skill of sitting down). [...]

I think that's a nice analogy, and maybe the problem isn't with
"casual users" needing to learn XML per se, but with needing to learn
a markup vocabulary that offers more explicit structure and logical
distinctions between of bits of content than they're accustomed to.

In the case of documentation authoring, most writers have been able to
get by using authoring systems that don't require them to think much
about their content's structure or logical distinctions, or to make
those distinctions explicit.

And now that many writers are being asked to learn how to mark up
their content in such a way that the structure/logical distinctions
are explicit, maybe some believe they'll find a simple-text or WYSIWYG
system that will add the structure and logical distinctions for them.

But if programmers don't expect to find simple systems to hand-hold
them through the process of writing code for complex applications --
things to add logic to their code for them where there was none
before-- why should writers expect simple-text or WYSIWYG authoring
systems to hand-hold them through the process of writing documentation
for those applications -- magic things to add logical distinctions to
their information for them, where there was none before?


-- 
Michael Smith, Tokyo, Japan    http://sideshowbarker.net
&#x30DE;&#x30A4;&#x30AF;

Both flowers and weeds spring when the sun is warm,
And great men do great good or else great harm.

  --John Webster (The White Devil, ca. 1610)

• Follow-Ups:
  • Re: "Smart ASCII" -> XML for authoring?
    • From: Ronald Bourret <rpbourret@r...>

• References:
  • "Smart ASCII" -> XML for authoring?
    • From: Mike Champion <mc@x...>
  • Re: "Smart ASCII" -> XML for authoring?
    • From: Bill Lindsey <bill@b...>
  • Re: "Smart ASCII" -> XML for authoring?
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: Re: "Smart ASCII" -> XML for authoring?
• Next by Date: RE: What am I overlooking...? (namespaces, validation, & xsv)
• Previous by thread: Re: "Smart ASCII" -> XML for authoring?
• Next by thread: Re: "Smart ASCII" -> XML for authoring?
• Index(es):
  • Date
  • Thread