update analysis

diff --git a/ztrans_proposal.mdwn b/ztrans_proposal.mdwn
index 148f9966a216222145aca14b906a9093f606a1bf..72a0bad058922941663bfd68f083ecfb9d8d5563 100644 (file)
--- a/ztrans_proposal.mdwn
+++ b/ztrans_proposal.mdwn
@@ -196,18 +196,14 @@ compliance with such standards, over-and-above what would otherwise be
 set by a RISC-V Standards Development Process, including both the
 software compliance and the knock-on implications that has for hardware.
 
-**The "contra"-requirements are**:
-
-* The requirements are **not** for the purposes of developing a full custom
-  proprietary GPU with proprietary firmware.
-* A full custom proprietary GPU ASIC Manufacturer *may* benefit from
-  this proposal however the fact that they typically develop proprietary
-  software that is not shared with the rest of the community likely to
-  use this proposal means that they have completely different needs.
-
-This proposal is for *sharing* of effort in reducing development costs,
-and as such needs to be entirely public, transparent, and fully integrated
-into public upstream libre-licensed libraries and toolchains.
+**Collaboration**:
+
+The case for collaboration on any Extension is already well-known.
+In this particular case, the precedent for inclusion of Transcendentals
+in other ISAs, both from Graphics and High-performance Computing, has
+these primitives well-established in high-profile software libraries and
+compilers in both GPU and HPC Computer Science divisions.  Collaboration
+and shared public compliance with those standards brooks no argument.
 
 *Overall this proposal is categorically and wholly unsuited to
 relegation of "custom" status*.