Hi Randy, > That's a reasonable rationale, and might even make a good CLR if > adopted from the very beginning, but given the ability of model > designers to read too much (or too little) into names, > perhaps one might consider the possibility of eliminating this > particular source of confusion altogether? > > date -> date-with-zone > date-no-zone -> date-no-zone > time -> time-with-zone > time-no-zone -> time-no-zone
This looks like my option 'e' in the other thread. It's good because it makes it a conscious decision either way. > Randy K. _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
