Section 7.1 of the OpenVG spec says:
"Each scissoring rectangle is specified as an integer 4-tuple of the form (minX, minY,
width, height), where minX and minY are inclusive. A rectangle with width ? 0 or height ? 0 is ignored"
Yet the A40102 conformance test will set all sorts of crazy values (including width ? 0 and height ? 0) for the scissor rect and it will fail the test if it doesn't get similar crazy results back with vgGetiv and vgGetfv. That behavior doesn't agree with "ignored" as stated above. Thus a driver must store a full set of insane scissor rect values that it can not use internally just to pass this conformance test. Where is the value in that for the API?
Would it be more useful to have the test allow for sane values to be returned? Also, from an application's standpoint, if it was sending garbage and reading back the sane number that the driver was using, it would have a way of knowing that it was sending garbage and how the driver had interpreted the numbers.