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

Re: Markup perspective not code (was RE: Re: URIs,

• To: "W. E. Perry" <wperry@f...>,"XML DEV" <xml-dev@l...>
• Subject: Re: Markup perspective not code (was RE: Re: URIs, concrete)
• From: "James Fuller" <james.fuller@o...>
• Date: Thu, 1 Aug 2002 23:23:58 +0100
• Organization: o-iDeveloper ltd.
• References: <015f01c239a0$bb0bab90$0200a8c0@skonnardomni> <3D49B3CD.762800F4@f...>
• Reply-to: "James Fuller" <james.fuller@o...>

----- Original Message -----
From: "W. E. Perry" <wperry@f...>
> > It would have been more accurate to say "markup users are simply using
> > pre-defined vocabularies *implemented* by programmers."
>
> In some limited circumstances, this is an OK way to begin mastering the
> skills of markup within a given domain of expertise. This technique,
> however, is never more than training wheels. Markup is a skill in its own
> right, like research or expository writing, required, or at least very
> handy indeed in the expert practice of an increasing number of domains.
> Markup is a very different skill from programming. Like basic programming,
> basic markup can be taught on simple principles, but like skilled
> programmers skilled markup practitioners have refined and mastered
> techniques through repeatedly confronting problems which yield to an
> understanding of deep patterns.
>
> Tim Bray eagerly addressed a question on this list yesterday because it
> appealed to him as a break from the usual exegesis practiced here.
> Questions of the tone, or aesthetics, of this list aside, markup is in
fact
> a branch of exegetical practice, which is where it differs fundamentally
> from programming. At the most mundane level, programming is prescriptive
> where markup is descriptive. More generally, programming is ultimately
> algorithmic where markup is taxonomic. The differences in mindset are
daily
> on display on this list, of course. Nevertheless (with all my bias
showing)
> it seems to me that xml-dev is, and should be, finally about the
> development of skilled XML--that is, markup--and much less about the
> ancillary business of implementing appropriate algorithms for  processing
> the wonderful subtleties which the markup grows to describe. Not that
there
> is not a place (and a need!) for both here. But there are many, many other
> places for programmers to whet their craft, and few if any others where
the
> expert practice of markup is understood as a profound skill.

+++1

cheers, jim fuller

• References:
  • RE: Markup perspective not code (wasRE: Re: URIs, concrete)
    • From: "Aaron Skonnard" <aarons@d...>
  • Re: Markup perspective not code (was RE: Re: URIs, concrete)
    • From: "W. E. Perry" <wperry@f...>

• Prev by Date: Re: Markup perspective not code (was RE: Re: URIs, concrete)
• Next by Date: Re: Re: URIs, concrete (was Re: Un-ask the question)
• Previous by thread: Re: Markup perspective not code (was RE: Re: URIs, concrete)
• Next by thread: RE: Markup perspective not code (was RE: Re: URIs, concrete)
• Index(es):
  • Date
  • Thread