Dave wrote: The problem is that the naming scheme will become multi-dimensional. We want to accommodate not just multiple processors, but various options about encoding and serializing. A single processor may be able to produce numbered or named entities, possibly with a different policy for different numerical ranges, and we might consider this a product feature. Rather than use an XML-parser-based comparitor and disguise the differences, we would want to check the file to see that we really got the in one case and the   in the other case. Separate policies would apply to the notorious URL encoding.
Can we accomodate the multi-dimensional nature by having separate directories for the processor options related to encoding and serializing, but each directory contains output for every processor? Oh, and the third dimension: cvs tags for different processor versions. Do you have an alternate proposal? Ilene.
