Cart
[Home] [By Thread] [By Date] [Recent Entries]
At the very least if you're going to allow for anything other than members of a defined set then have something defined for the undefined. Lest you get stuck with layers of cruft trying to decipher to crude attempts the operators will make attempting to do so on their own. Which will still be a problem anyway. -----Original Message----- In my work, I've often preached that a Schema/DTD should model the business process. When someone wants an "other" element or attribute value, it's almost always because the business process is ill defined, sometimes inadvertently, sometimes deliberately. So long as no one expects very much from any machine processing of the value of an "other" element or attribute (other than recording the value, for example). Yes, it's useless, but also probably harmless. Still, it's a laudable goal, Roger.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
