[
Lists Home |
Date Index |
Thread Index
]
On Mon, 5 Jan 2004, Simon St.Laurent wrote:
> igraham@ic-unix.ic.utoronto.ca (Ian Graham) writes:
...
> >No one wants to have they app crash for lack of handling some obscure
> >content model -- and I've certainly seen that happen a lot on the
> >project I'm working on.
>
> Then write the apps so they don't crash when fed something they don't
> understand. Responding with "I don't understand this" is a good first
> step.
>
> >We need to make sure people use the 'right' approaches for processing
> >xml, so this doesn't happen. Unfortunately this is a different mindset
> >for designers and developers ...
>
> What would this "right" approach be? The semantic straitjacket?
Of course not (this is getting silly). I'm merely pointing out that
getting developers to do things 'right' means teaching them to think about
their interfaces (namely xml) in new, different ways. That's hard to do,
particularly when many of the tools (like much of the web services stuff
we're working with) don't support anything but the straitjacket. [last
sentence may be tainted by recent experience :-( ]
Which is way off topic from complexity and formalism (at least as I
interpreted it), but is interesting nevertheless.
Ian
|
