SCR 3-1124: PSDD Enhancement --- add Case to keywords of type CHARACTER
Problem Summary: Validation and Label Template design warrant more rigorous PSDD constructs to warn if keyword values of type CHARACTER are not PDS compliant with respect to the keyword (e.g., DATA_SET_NAME requires uppercase; DESCRIPTION requires mixed-case; PATH_NAME requires either uppercase or lowercase (but no mixed-cased). One way to accomplish the above is to replace GENERAL_DATA_TYPE = CHARACTER with multiple values: - CHARACTER-UPPERCASE - CHARACTER-LOWERCASE - CHARACTER-MIXEDCASE - CHARACTER-NOTMIXED
Update: The direction of this SCR has changed significantly during working group discussions. The essential issue involves enabling automated validation of keyword values, including values which are accepted exceptions to the PDS standards, through structural changes to the PSDD. It is now the belief of the working group that this SCR involves few, if any impacts to the Standards; rather, most of the changes are implementation issues which should be worked out internally in the Engineering Node. Given that there may be impacts to the format of the Element Definition Template and that there may be some interpretation / clarification of the existing standards required during implementation, the working group and Tech Groups should be kept informed.
Working group: R. Joyner (lead) M. Cayanan (technical advisor), L. Huber, T. King, E. Rye, D. Simpson
Standards Change Request:
- Discussion Blog
- Telecons: 2007-08-29 (HTML), 2007-09-12 (HTML), 2007-09-26 (WAV), 2007-10-17 (WAV), 2007-10-31 (HTML), 2007-11-14 (HTML), 2007-11-28 (HTML), 2008-01-09 (HTML), 2008-01-30 (HTML), 2008-02-13 (WAV), 2008-02-27 (HTML), 2008-03-19 (WAV), 2008-04-16 (WAV), 2008-05-07 (HTML)