[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebxml-bp] [Fwd: Re: Anders' Numbers - OCL]
Fred, Interestingly OASIS CAM was designed specifically to meet this CCTS need - amongst many others relating to CCTS implementation. Therefore you can create usage rules for CCTS components using CAM, and using XPath within CAM for that. This is certainly much simpler and more direct than using OCL. In addition CAM supports storing these rules in an ebXML Registry, and then retrieving them for use. This is being further defined by the Registry SCM SC. And you can also use a design tool such as VisualScript to build visual models of business transactions based on CCTS components and objects - and then emit CAM templates that implement those transactions - as a pure modelling approach with CCTS that binds to XML at the implementation layer. You could also do this from a UML tool by creating production rules to CAM XML from UML of CCTS. I would therefore strongly recommend review of CAM in regard to implementing CCTS with BPSS. Thanks, DW. ----- Original Message ----- From: "Monica J. Martin" <Monica.Martin@Sun.COM> To: "ebXML BP" <ebxml-bp@lists.oasis-open.org> Cc: "Fred Blommestein, van" <f.van.blommestein@berenschot.com> Sent: Monday, July 12, 2004 7:11 PM Subject: [ebxml-bp] [Fwd: Re: Anders' Numbers - OCL] > > >van Blommestein: Find attached the proposal for collecting OCL subset requirements. Afterwards, other priorities took over in UN/CEFACT, so there was never any follow-up. > >One of the requirements, as far as I am concerned, is the ability to convert the OCL for pre- and postconditions from and into XPath statements without loosing semantics, referring either to the collection of exchanged documents or to the knowledge base built up by those documents. > > > >Would you please distribute the document and the remarks above to the list as I do not have rights to do that? Thanks. > > > >Fred > > > mm1: As a followup to our teleconference call today where we referenced > OCL. From Fred vanBlommestein. > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]