[Fwd: [ebxml-bp] [public-comment-00000] transformation from 1.05 to2.01]

[Monica J Martin <Monica.Martin@Sun.COM>]

See the working update to your post on the transformations. We're 
working it through (drafts in work). Feedback welcome. Thank you.

> Hi
>
> I somehow wrote a XSL/T for transforming BPSS 1.05 into BPSS 2.01, 
> based on Dale's work. Please review the content of the zip attached.
> Now both BPSS1.05 sample and generated BPSS2.01 sample pass schema 
> validation. This should resolve the issue raised by Simon.
>
> Some notes on this:
>
> - I took a PIP7C7 BPSS and modified it for full compliance to 1.05 and 
> easy transformation. This includes modification to 
> toBusinessState/fromBusinessState where RN used XPath notation to link 
> to other business states. Those XPaths were replaced with simple name 
> references (I hope this is okay).
>
> - I had to generate ProcessSpecification/@nameID - I don't know this 
> is meaningful.
>
> - I transformed 1.05's BusinessTransaction into 2.01's 
> LegacyBusinessTransaction
>
> - I had to define dummy Signal to be used in ReceiptAcknowledgement 
> and ReceitpAcknowledgementException.
>
> - There is no guarantee that any valid BPSS1.05 instance can be 
> transformed into 2.01 with this script. For instance, Fork/Join 
> construct cannot be transformed correctly due to non-trivial change in 
> the spec.
>
> Regards,
> Kenji Nagahashi
>

--- Begin Message ---

• From: Kenji Nagahashi <nagahashi@us.fujitsu.com>
• To: ebxml-bp@lists.oasis-open.org
• Date: Fri, 26 Aug 2005 15:21:32 -0700

Hi

I somehow wrote a XSL/T for transforming BPSS 1.05 into BPSS 2.01, based 
on Dale's work. Please review the content of the zip attached.
Now both BPSS1.05 sample and generated BPSS2.01 sample pass schema 
validation. This should resolve the issue raised by Simon.

Some notes on this:

- I took a PIP7C7 BPSS and modified it for full compliance to 1.05 and 
easy transformation. This includes modification to 
toBusinessState/fromBusinessState where RN used XPath notation to link 
to other business states. Those XPaths were replaced with simple name 
references (I hope this is okay).

- I had to generate ProcessSpecification/@nameID - I don't know this is 
meaningful.

- I transformed 1.05's BusinessTransaction into 2.01's 
LegacyBusinessTransaction

- I had to define dummy Signal to be used in ReceiptAcknowledgement and 
ReceitpAcknowledgementException.

- There is no guarantee that any valid BPSS1.05 instance can be 
transformed into 2.01 with this script. For instance, Fork/Join 
construct cannot be transformed correctly due to non-trivial change in 
the spec.

Regards,
Kenji Nagahashi

ebxmlbp-2.0.1-cd-ExampleTransformFor1.05-en.zip

--- End Message ---