Cart
[Home] [By Thread] [By Date] [Recent Entries]
Adding no-public-benchmark clauses to the EULA is something largely beyond the control of the Msxml team. As to be expected in a large, conservative company like Microsoft, the default is locked down, raise-your-hand-to-visit-the-restroom type wording. Anything else requires jumps through flaming hoops of legalese. The clause is there to avoid the classic problem of people disregarding all published best-practices, and write a test which shows that the product is X times slower than some other product, i.e. it helps protect against overly contrived benchmarks. I can't think of a case where the Msxml team ever blocked anyone from reporting benchmark runs, and in fact I know of at least one case where we corrected the benchmark such that it lowered Msxml's score. -derek [speaking in no legal capacity for Microsoft] -----Original Message----- From: Rick Jelliffe [mailto:ricko@a...] Sent: Tuesday, June 10, 2003 8:26 AM To: XML Dev Subject: Re: Benchmarking forbidden? There has been a no-public-benchmark clause for MSXML a while. Oracle too. It is surprising since they both are pretty good. My old "Screamathon Torture Test" results came up against this. See http://www.ascc.net/xml/schematron/1.5/conrep.html and http://www.ascc.net/xml/schematron/1.5/#conform See also http://www.ascc.net/xml/connect for a little language for hiding command-line differences. Cheers Rick Jelliffe ----------------------------------------------------------------- The xml-dev list is sponsored by XML.org <http://www.xml.org>, an initiative of OASIS <http://www.oasis-open.org> The list archives are at http://lists.xml.org/archives/xml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://lists.xml.org/ob/adm.pl>
|
