[clsc] The Meaning of CLSC

[Chin Chee-Kai <cheekai@softml.net>]

Hi CLSC Folks,

Defined as finite sets of discrete values, code lists are
nothing new.  However, the actual rendition, verification
and error handling of code values in terms of physical,
real systems are different for different technology and
application contexts.

Rendition includes the lexical form of code values, 
lexical range of all codes, domain range in which the
lexical range sits, and all sorts of serialization issues
pertaining to how the code values are written out into a 
byte stream.  

Verification includes the process of reading back and 
interpreting the code values, checking and validating the
read-in value against a given/expected code list representation,
and determining unambiguously that a code value is or is not
acceptable.

Error handling includes the manner in which processing 
should/must act whenever the verification stage signals
unambiguously that a code value is not acceptable. 
In this case, proper treatment of error handling is
important.  A silent ignorance of such error condition
can lead to very different downstream outcomes as opposed
to a replacement of specification-provided default value,
or as opposed to a specification-mandated signaling of 
error to the user.

A consistent and systematic treatment of the 3 aspects
above would result in a more usable and dependable 
transfer of meanings encoded within code values that
lead to expected behavior and actions by sending and
receiving systems.

Just some thoughts;  I believe they are not new, just
repeating them here to generate some starting thoughts.



Best Regards,
Chin Chee-Kai
SoftML
Tel: +65-6820-2979
Fax: +65-6743-7875
Email: cheekai@SoftML.Net
http://SoftML.Net/