[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ebxml-cppa] Updated Service/Action notes (inline,not attached this time)
Notes for Discussion Proposal Issue 30 CPPA Service and Action Tuesday, November 20, 2001 Updated on Monday, November 26, 2001 Describe the main issue Arvola Chan, Hima Mukkamala MS team says Service Element in Message Header will come from Service Element in CPA and Action in Message header comes from CPA. How are Service and Action derived from BPSS? Need unique Service and Action. Role(s). Discussion and ideas Arvola Chan, Hima Mukkamala, Brian Hayes, Dale Mobray Service = BPSS Unique Process Identifier (UUID) Request to make UUID a URN, (see the business process worksheet document) Service, in combination with CPAid (from the message header) provide further discrimination for application routing Action = Process Specification Name + Binary Collaboration Name + [Nested binary collaboration Collaboration Activity Name(s)] + Business Transaction Activity Name + Requesting or Responding Activity Name The [Collaboration Activity Name(s)] are only needed when there are nested Collaboration Activities. When there are multiple nested Collaboration Activities, there will be multiple Collaboration Activity Names in the Action. Short version and long version of action value in CPA. Make Activity Name required and unique. Use xpath semantics to uniquely identify the requesting business activity and responding business activity. [Maybe, maybe not.] For the action names to be asymmetric, the BPSS Requesting Business Activity and Responding Business Activity need to be made required. David Smiley Director of Standards Mercator Software 540.338.3355
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC