Re: "CODE" representation class

[bohrer@us.ibm.com]

Dwight,
         In object modeling I have done in the past a currency value
(monetary amount) is an aggregate object including both a decimal value and
a currency code.
         The concept of "Code" sounds like an abstract class to cover any
subtype that has an explicit set of valid values. I have found in the past
that two types of "Codes" are useful, one with a "closed" set of values and
one with an "open" set of values. The open one is used where businesses
generally are free to define new valid values as a normal course of doing
business. Product classification codes might be an example. Codes like
currency codes and country codes are "closed" because their values are
defined by an ISO standard. I don't know if this helps, but it is some
background on how things have been handled in OO systems in the recent
past.

Regards,
- Kathy Bohrer
  Distinguished Engineer
  T.J. Watson Research Center
  (512)671-1932
 (512)791-3058 cell phone


Dwight Arthur <darthur@bestweb.net> on 08/20/2000 07:24:43 AM

To:   Dwight Arthur <darthur@bestweb.net>, ebxml-core@lists.ebxml.org
cc:   jie_lin@dtcc.com, jalin@dtcc.com
Subject:  "CODE" representation class



In San Jose, we discussed a set of standard representation classes for core
components. One of them was, "Code" where (if I understood correctly)
concepts like "Country Code" or "currency Code" would make use of this
representation class.

Trying to use Martin's forms to record this, we find that I cannot create
an
entity "currency code" with representation class "code" where the entity
defined "ISO standard xxxx" as the definitive enumeration of acceptable
values.

Rather, we find a need to define "currency code" as a representation class
invoking the ISO standard, and then define some other entity (e.g. monetary
amount) as represented by the currency code representation.

Either

- our list of representation classes was wrong, and should include things
like "currency code" and "country code" rather than "code"

or else

- the forms are wrong, and should allow codeset to be specified within the
entity definition rather than the representation class

or else

- I am confused again, please straighten me out?

Thank you

-Dwight