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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-cppa message

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


Subject: [ebxml-cppa] CPP and CPA element documentation changes


Attached are some options for changes to 
CPP and CPA reflecting recent discussions.

Marty Sachs and others have proposed dropping
the version element.

Chris Ferris reminded us of a use of version as
indicating the version of the CPPA specification
that the documents were governed by (this version
is distinct from any versioning of a schema, as
is done with XSLT.)

Here is how to assemble the variants.

The "CPP CPA element core language.doc" is the baseline,
with the version attributes omitted.

To get the full Ferris option, add in the text from
"CPA version of specification.doc" and "CPP version of
specification.doc" to the core. 

To get a variant in which a version attribute is retained
for CPA, and that has a role in Negotiation, add in
"CPA version for negotiation.doc" to the core.

I did not supply a variant for versioning the CPP because 
I have not been able to think of a simple way to explain how
CPP versioning would work. Unlike the CPA, where apparently
users might wish to maintain their cpaid in a new agreement,
CPP versioning does not have a use case currently. 

Please comment on these on the list, 
indicating rankings for the variants, or new ones 
if you want to add your own language.
We will seek to obtain a consensus on this
Monday.

Thanks, Dale Moberg

CPP CPA element core language.doc

CPA version for negotiation.doc

CPA version of specification.doc

CPP version of specification.doc



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


Powered by eList eXpress LLC