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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

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


Subject: ebBP 3/10/2005: schema 2/22 "BusinessTransactionHead" Element


Another one from Sacha: More fully explain how BTs maps to patterns 
(through BusinessTransactionHead).Comments welcome on schema annotation 
update.
Sacha, please advise if an example helps explain this and if more detail 
is required.  Thanks.

Change from:
===============================================================================================================
- <#> <xsd:element name="*BusinessTransactionHead*" 
type="*BusinessTransactionType*" abstract="*true*">
- <#> <xsd:annotation>
  <xsd:documentation>The abstract superclass associated with the 
concrete set of defined Business Transaction patterns. Note, in v2.0, 
the Business Transaction Head replaces the Business Transaction element. 
A Business Transaction is a set of business information and business 
signal exchanges amongst partners that occurs in an agreed upon format 
and sequence (as supported by the patterns). In v2.0, the Business 
Transaction Head, the concrete set of BT patterns and the Data Exchange 
element (allows pattern specialization) enable business exchange through 
a defined pattern..</xsd:documentation>
  </xsd:annotation>
  </xsd:element>

===============================================================================================================
- <#> <xsd:element name="*BusinessTransactionHead*" 
type="*BusinessTransactionType*" abstract="*true*">
- <#> <xsd:annotation>
  <xsd:documentation>The abstract superclass associated with the 
concrete set of defined Business Transaction patterns. Note, in v2.0, 
the Business Transaction Head replaces the Business Transaction element. 
A Business Transaction is a set of business information and business 
signal exchanges amongst partners that occurs in an agreed upon format 
and sequence (as supported by the patterns). In v2.0, the Business 
Transaction Head, the concrete set of BT patterns and the Data Exchange 
element (allows pattern specialization) enable business exchange through 
a defined pattern. The Business Transaction Head in essence is a 
placeholder where the concrete pattern is substituted (i.e. a 
Request-Confirm is substituted and used).</xsd:documentation>
  </xsd:annotation>
  </xsd:element>




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