[
Lists Home |
Date Index |
Thread Index
]
Bryan Wrote:
> Anyway I have seen specifications authored by non-programming domain
> experts...
> Just as often these specifications attempt to match the structures that
> the domain experts were used to working with before, as a general rule
> non-hierarchical structures, thus replicating many errors of "xml
> dialect design by Programmer".
>
> It seems to me that probably what one needs is for specifications to be
> authored by someone who can stand in between the worlds of the
> programmer and the domain expert, mindful of what the programmer will
> have to do to work with the new format, and capable of analyzing the
> structure of individual domains, to render them to their essence in xml.
Len Bullard Wrote:
> Being a middle ground between the deep knowledge required
> of the subject matter expert and the training of the
> programmer is what is needed...
Agreed. Whether you use a team approach or have an individual with
experience in both sides of this issue, incorporating the knowledge of both
the subject matter experts and the programmers is important. It is not an
either/or proposition. Effective communication and education on both sides
is key.
P.S. The original draft of this response included a case study to illustrate
this concept, but it got rather lengthy, so I though I would spare you. :-)
Doug Rudder drudder@drugfacts.com
|
