RE: [ebxml-cppa] 8 February 2008 Teleconference, 8 AM Pacific, ebXML CPPA

["David RR Webber \(XML\)" <david@drrw.info>]

Pim,

Like where you are heading with this and the XSD definition.

BTW - don't forget in addition to referencing a schema in the partner agreement, you can also reference a CAM template to manage the information exchange context, content, and rules.

Here's the one I just did for EDXL.

DW

>XML sample -
>
> http://www.drrw.net/CAM/samples/EDXL/EDXL-sample-small-hospital.xml
>
>CAM template -
>
> http://www.drrw.net/CAM/samples/EDXL/EDXL-subset-template.cam
>
>Rules documentation -
>
> http://www.drrw.net/CAM/samples/EDXL/content-usage-report.html
>
>XSLT -
>
> http://www.drrw.net/CAM/samples/EDXL/EDXL-report.xsl
>
>Final resulting report -
>
> http://www.drrw.net/CAM/samples/EDXL/results.html
>
>Hope this helps people putting together their own implementation examples.

> -------- Original Message --------
> Subject: RE: [ebxml-cppa] 8 February 2008 Teleconference, 8 AM Pacific,
> ebXML CPPA
> From: "Pim van der Eijk" <pvde@sonnenglanz.net>
> Date: Fri, February 08, 2008 11:15 am
> To: "'David RR Webber \(XML\)'" <david@drrw.info>,  "'ebxml-cppa'"
> <ebxml-cppa@lists.oasis-open.org>
> Cc: "'Moberg Dale'" <dmoberg@axway.com>
> 
> Yes, this new contribution is a follow-on from work I did around the same
> time. 
> 
> http://www.oasis-open.org/archives/ebxml-cppa/200609/msg00004.html
> http://www.oasis-open.org/archives/ebxml-cppa/200606/msg00011.html
> 
> That work is now used in a production deployment. My attempt with the new
> schema is to generalize it so it has a broader applicability.
> 
> -----Original Message-----
> From: David RR Webber (XML) [mailto:david@drrw.info] 
> Sent: 08 February 2008 15:45
> To: Pim van der Eijk
> Cc: 'Moberg Dale'; 'ebxml-cppa'
> Subject: RE: [ebxml-cppa] 8 February 2008 Teleconference, 8 AM Pacific,
> ebXML CPPA
> 
> Pim,
> 
> In this regard - see the XSLT here:
> 
>  
> http://www.oasis-open.org/committees/download.php/20095/CPA-config-using-xsl
> t.zip
> 
> Good to see progress in these areas - long overdue.
>  
> Not sure if you have interest in using Excel worksheets as the template
> interface for this - for users.  Then export XML from Excel and consume that
> via xslt to configure CPA and more...I have some prototypes in that area
> too.
> 
> DW
> 
> > -------- Original Message --------
> > Subject: RE: [ebxml-cppa] 8 February 2008 Teleconference, 8 AM 
> > Pacific, ebXML CPPA
> > From: "Pim van der Eijk" <pvde@sonnenglanz.net>
> > Date: Thu, February 07, 2008 4:50 pm
> > To: "'Moberg Dale'" <dmoberg@axway.com>,  "'ebxml-cppa'"
> > <ebxml-cppa@lists.oasis-open.org>
> > 
> > Hello,
> >  
> > Here is some input for our discussion tomorrow.  I have been working 
> > on the concept of an XML language to describe how partner agreement 
> > documents are formed. It describes the parameter values that partners 
> > need to provide to form the agreement documents. It intends to cover 
> > multiple partner agreement document types and multiple methods for
> establishing these agreements.
> > Agreement document types include XML schemas and ebXML Collaboration 
> > Protocol Agreements. Agreement formation methods including editing XML 
> > template documents or specialized methods like intersecting two 
> > Collaboration Protocol Profiles.
> >  
> > A single formation description document can describe multiple 
> > agreement documents (e.g. customizing an XML schema, and using that 
> > customized schema in a CPA or WSDL). It can cover cases with any 
> > number of participant roles, and reuse of parameter values across
> agreement documents.
> >  
> > Attached are an XML schema and three sample documents for XML Schema 
> > customization, CPA templating and CPP intersection.
> >  
> > A special case (and the initial reason for working on this) is that 
> > this notation can describe the formation of a single CPA from a 
> > template using parameters supplied by two partners.  I am working on a 
> > proof-of-concept compiler that generates an XSLT stylesheet to 
> > transform the template into a partner pair specific CPA based on 
> > provided parameters.  The compiler itself is an XSLT stylesheet, 
> > unfortunately it needs more work before I can post it. (It is derived 
> > from a similar compiler that is used in a real-life ebXML deployment
> project).
> >  
> > N.B. This is all work in progress, but it gives an idea of where this 
> > is going to ..
> >  
> > Pim
> >  
> >  
> > 
> >   _____
> > 
> > From: Moberg Dale [mailto:dmoberg@axway.com]
> > Sent: 30 January 2008 00:26
> > To: ebxml-cppa
> > Subject: [ebxml-cppa] 8 February 2008 Teleconference, 8 AM Pacific, 
> > ebXML CPPA
> > 
> > 
> > 
> >  
> > 
> > 866 383 5205
> > 
> > 144286#
> > 
> >  
> > 
> > Agenda
> > 
> >  
> > 
> > 1. Pim presentation on profile and agreement services.
> > 
> > 2. Status of version 3.0.
> > 
> > 3. Planning for 
> > transition.<hr>-------------------------------------------------------
> > -------------- To unsubscribe from this mail list, you must leave the 
> > OASIS TC that generates this mail.  You may a link to this group and 
> > all your TCs in OASIS
> > at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php