# Terminology issues Dear @JonathanGregory et al. (@AndersMS @davidhassell @oceandatalab @ajelenak) Concerning terminology, following discussion in the group, these terms seem good candidates:
- At tie-point level: "subsampled dimension", "non-interpolated dimension" - At reconstituted level: "interpolated dimension", "non-interpolated dimension" "non-interpolated dimension" is repeated because it is shared across the 2 domains. Would this be an improvement in your view? # Computational precision `computational_precision` This attribute should be mandatory for data producers to specify the precision in which interpolation should take place. This means that there should be no default value; the creator specifies it. It is up to the user to interpret that and using a precision that deviates from the recommendation would not prompt an arrest through the CF police but would mean that they might have deviations in the interpolated data. This should be clearly described so that the reader of the Conventions understands the potential impacts (no need to wax eloquent here though). # Actionees! - @AndersMS will update the draft with regards to the terminology issues - @oceandatalab will propose a paragraph regarding computational precision in this issue and @AndersMS will integrate it into the document after we've agreed it here -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/327*issuecomment-870574025__;Iw!!G2kpM7uM-TzIFchu!kGgEAKsB-Hu_FZ2RBoRAraz_VHPZzWIZkfL_i3P7du4GueaRSM_VIiKAhr43UwYDkN-Jy9I_Ilo$ This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
