[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [xml-dev] RE: Things are not what they seem
- From: "Bullard, Claude L (Len)" <firstname.lastname@example.org>
- To: "Simon St.Laurent" <email@example.com>, firstname.lastname@example.org
- Date: Fri, 21 Sep 2001 12:22:02 -0500
We need the vision. Insight is when one
can do research and get the answer first.
Vision is applied when there isn't an answer.
No one has shown me an application
of XML for which there isn't an answer
given some research. It's a matter of
knowing when to use who. An expert solves
the problem. A novice defines it.
Both are perfectly valid approaches
for the same person in different contexts.
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Simon St.Laurent [mailto:email@example.com]
For a lot of XML work, I have to agree with Len. When I'm looking for
writers on XML subjects, insight (and the ability to communicate that
insight) is the main thing I'm seeking. Similarly, if I have project
that's already well-scoped out, people with imagination for the details are
going to do great work rather than redesign everything.
At the same time, I'm worried that valuing insight over vision causes some
serious problems, perhaps especially in this (XML) community. "How to use
XML" is something we've barely begun to figure out, and preferring insight
to vision is likely to keep us on the same narrow set of paths. This isn't
a trade as well-understood as electrical work or plumbing, and electricians
and plumbers have all kinds of opinions about how best to do things.