Re: [ebxml-bp] [Fwd: [ebxml-bp-comment] Public Comment]

["David RR Webber" <david@drrw.info>]

Duane,

I suspect that your reply relies way too much on insider ebXML
and CCTS speak!

Here's what I think is really going on in sorta plain english.

1) The BPSS can reference to logical documents that are interchanged in a
     process step that are part of a process action - typically an initiate
     and reponse document pair - and  the BPSS schema
     contains the necessary syntax  to capture this logic and settings.

2) A logical document such as "goods billing invoice" is then resolved to a
     physical transaction instance at runtime - typically this will be an
EDI or
     XML definitions - such as an XSD file and an associated specification
     document (MS Word or Excel).  The ebXML CPA that configures the
     messaging needs to reference these exact document types and headers
     - so they can be checked by the ebMS service to ensure they pass
     messaging authorization during sending and receiving.  One partner may
     send EDI, another XML, and their CPA settings will tell you this.

3) Moves are afoot to automate this transaction mapping - principally the
     OASIS CAM specification allows you to map the logical document
     to a complete set of structure, content, context and business use rules
     that ensure the correct use and exchange of information occurs for
     the particular business step.  The structure of the transaction can
also
     be built using pre-constructed chunks that are core components
      compatible - see CCTS - using CAM assembly templates.
     Typically though for legacy transactions the pre-built chunks will
     correspond to an industry's already existing
     noun dictionary and "core components" - such as EDI, RosettaNet,
     and OAGi.   The CAM templates therefore hold the details of these
     legacy transactions formats.

Thanks, DW

----- Original Message ----- 
From: "Duane Nickull" <dnickull@adobe.com>
To: "Monica J. Martin" <Monica.Martin@Sun.COM>
Cc: "ebXML BP" <ebxml-bp@lists.oasis-open.org>; <zhuxia2002@hotmail.com>
Sent: Monday, March 08, 2004 4:44 AM
Subject: Re: [ebxml-bp] [Fwd: [ebxml-bp-comment] Public Comment]


> >
> >
> >5.4   How to design collaborations and transactions, re-using at design
time
> >
> At design time, an assembly metadata (collection of data elements) is
> referred to as the payoad.  At Runtime, the value is over written by the
> CPA by referencing the token name of the transaction payload with an
> actual schema.
>
> >5.4.2   Specify a binary collaboration
> >
> Not quite sure what the question is but it may be by using a combination
> of BPSS, CPA and payload documents.  Can be represented in UML or XML.
>
> >
> >
> >
> >5.4.2.1  Key Semantics of a Binary Collaboration
> >
> The BPSS specification should provide the semantics for each element,
> attribute used in a BPSS instance.  The semantics of the payloads are
> defined by deriving a BIE from a core component, constraining it by 8
> context category classifications.
>
> >When performing a Binary Collaboration within a Binary Collaboration
there is an implicit relationship between the roles at the two levels.
Assume that Binary Collaboration X is performing Binary Collaboration Y
through Collaboration Activity Q. Binary Collaboration X has Authorized
roles Customer and Vendor. In Collaboration Activity Q we assign Customer to
be the initiator, and Vendor to be the responder. Binary Collaboration X has
Authorized roles Buyer and Seller and a Business Transaction Activity where
Buyer is the initiator and Seller the responder. We have now established a
role relationship between the roles Customer and Buyer because they are both
initiators in activities in the related performing and performed Binary
Collaborations.
> >
> See my comments from 2001 regarding establishing role limits.  This was
> a problem with 1.01.
>
> >7.  ebXML Business Process Specification Schema &#8211; (DTD)
> >
> ????
>
> >
> >
> >
> >7.1  Documentation for the DTD
> >
> THe specification????
>
> >[DN] everything from here down is deprecated since 2001.
> >
> >
> >l.) DTD Declaration:
> >
> ><!ELEMENT BusinessDocument  (Documentation*) >
> >
> >/* the elementname here may be changed into DocumentSubstitution*/
> >
> ><!ATTLIST DocumentSubstitution
> >
> >originalBusinessDocument CDATA #IMPLIED
> >
> >originalBusinessDocumentID IDREF #IMPLIED
> >
> >substituteBusinessDocument CDATA #IMPLIED
> >
> >substituteBusinessDocumentId IDREF #IMPLIED
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >To unsubscribe from this list, send a post to
ebxml-bp-comment-unsubscribe@lists.oasis-open.org, or visit
http://www.oasis-open.org/mlmanage/.
> >
> >
> >
>
> -- 
> Senior Standards Strategist
> Adobe Systems, Inc.
> http://www.adobe.com
>
>
>
>