Lists Home |
Date Index |
I don't know if it was autotranslated, or someone
thinks it's a good idea, but the folks who have
to write XSLT for it hate it. The point being that
structurallly, there is no need to carry the names
deeper into the tree. Every piece of code after
that translation carries the pain forward and
once out into the world, it is almost impossible
to fix. Viral marketing and viral diseases have
much in common.
Training outs. OOPisms are not necessarily the best
way to code markup. Schools training CS grads should
rethink some articles of faith.
From: Thomas B. Passin [mailto:firstname.lastname@example.org]
One place you see this is in automatic translations from code or IDL. I had
to work with some xml that was automatically created from the java objects
created for CORBA messages, and they were pretty awful, about what you show.
The IDL developers rightly create readable element names according to
notions of naming conventions, but those names aren't intended to be
instantiated in the message instance. It's not so easy to get good element
names from such IDL by machine.