OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [ebxml-dev] ebXML core components derivation by restriction


<Duane>Would this not be served by an iterative process according to the
methodology itself?  For example, a Health Insurance Policy Contract is
a specialized (in context(s)) instance of the type Contract, in itself a
specialization of "Agreement".  Through iterative revision, the high
level "contract" should have a notion of "type" with an enumerated list.
 The enumerated list may be conditionally validated [1] against other
qualifiers (something that XML schema cannot currently do) and "Health
Insurance Policy" is merely a type of contract.</Duane>

<Fred>I agree with the mechanism, but CCTS does not support it.
Enumeration is only supported at the lowest level, for data types, not for
aggregates. Conditions can be stored in the "usage rule" of a CC/BIE, but
that is free text for the moment. I would be in favour of defining an OCL
profile/subset for such rules, that also would be 1:1 translatable to

If you agree with the mechanism and CCTS does not currently support it, is
there any reason that CCTS could not be changed and support it in the

Ron Schuldt
Senior Staff Systems Architect
Lockheed Martin Enterprise Information Systems
11757 W. Ken Caryl Ave.
#F521 Mail Point DC5694
Littleton, CO 80127

<<attachment: winmail.dat>>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]