RE: The hard cocktail of sequence and (node-)set (Was:

> If not corrected this "feature" alone will become a classical
> example of bad design.
>
> I have pointed out elsewhere some of the unfortunate results
> of mixing these two
> very different datatypes into one:
>
> http://aspn.activestate.com/ASPN/Mail/Message/xsl-list/908998
>

Ah yes, I remember now. All my hens will get eaten by foxes.

Dimitre, I have a great deal of respect for your opinions, and I think there
is probably a case to be argued here. In this instance I don't think you
argue it very well. I would be tempted to ask you to put together a more
careful justification of why you think the group is taking the wrong
approach, and to submit it. However, while all comments are welcome, I think
you would be wasting your time. We're now at the stage where people don't
want to reexamine the fundamental data model unless it's found to contain
very serious holes; and I think that while it isn't perfect, it is workable.

Mike Kay


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list