we still haven't resolved the issue of syntax inside a
<param> ... </param> block.
Should a simple text/enriched process read blindly until
the </param>
I would think yes, I dont see any justification for an ignorant parser to
attempt to makes sense of the internal format, but I may be taking a simplistic
view, hm, if there were any possibility of nested <param>'s, (perhaps as a
result of docs within docs)
<param>....<param> ... </param> .... </param>
then we would be challanged to parse the unknown semantic
gahd, what a zoo.
Alas, I think there are good arguments both ways....
After all the previous discussion, perhaps its time for a
(hopefully succinct) restatement of positions, I will take the
liberty of posing the Q:
Why would <param> ignorable_param_data_block </param> be unfortunate?
--
dana s emery <de19(_at_)Umail(_dot_)umd(_dot_)edu>