Title: RE: [ebxml-msg] XML Pipeline Definition Language Version 1.0
I believe we'll need something like this as soon as we step in the area of
payload [pre or post] processing.
Two remarks:
- we'll need to be careful to not raise the bar to V3.0 conformance too high
(translate: complexity of implementation) but I think this is a more general issue
we have to address with enhanced features in 3.0. (carefully crafted conformance levels might do)
- the MSH as a "pipeline controller" woudl require processing pipeline docs,
and a must-have option would be to have these being part of MSH configuration.
(how then would these relate to BPSS, CPA? I think pipeline docs would need be reflected
in at least one of these)
Jacques
-----Original Message-----
From: Jeff Turpin [mailto:]
Sent: Wednesday, May 12, 2004 12:16 PM
To: Matthew MacKenzie; Doug Bunting
Cc: ebXML Messaging
Subject: RE: [ebxml-msg] XML Pipeline Definition Language Version 1.0
It looks pretty good to me at first glance. I would like to dig a little
deeper before I can give a thumbs up.
-----Original Message-----
From: Matthew MacKenzie [mailto:]
Sent: Wednesday, May 12, 2004 12:12 PM
To: Doug Bunting
Cc: ebXML Messaging
Subject: Re: [ebxml-msg] XML Pipeline Definition Language Version 1.0
Hmm...looks pretty generic as is.
I wouldn't mind using it, what do others think?
Doug Bunting wrote:
> Information[1] on an available language for sequencing processing of
> an XML instance. Should be possible to extend beyond XML...
>
> thanx,
> doug
>
> [1] http://www.w3.org/TR/2002/NOTE-xml-pipeline-20020228/
>
>
> To unsubscribe from this mailing list (and be removed from the roster
> of the OASIS TC), go to
>
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/members/leave_wor
kgroup.php.
>
>
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/members/leave_workgroup.php.
