Yeah, there&#x27;s lots of places where &quot;value&quot; is a well-accepted, clear, domain-specific language for a specific component of a construct, and thus using &quot;value&quot; is an <i>excellent</i> variable name.<p>(Similarly with data: lots of times, I&#x27;ve seen specs where a composite structure had a part called &quot;data&quot;. Whether or not that is good naming <i>in the spec</i>, if I&#x27;m implementing the spec, using &quot;data&quot; for the element in the program corresponding to that part of the composite in the spec is clearly the exactly right thing to do.)