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] Adding #wildcard element to provide extensibility


In the Messaging spec, #wildcard element content is supported in every SOAP extension as well as in all of their major repeating sub-elements.
 
To provide extensibility in the CPP/CPA structure, I think it may be useful to allow #wildcard extensions in most elements in the CPP/A schema.
 
I know RosettaNet's TPA Foundational Program would like to express message exchange requirements in terms of CPP/A. However, not enough initial work has been done to determine if there are major show stoppers. Allowing namespace qualified wildcard extensions may help industry groups like RosettaNet to adopt the use of CPP/A.
 
If there is support for this idea, I like to include such wildcard extensions in the 1.02 version of the spec.
 
Thanks,
-Arvola


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


Powered by eList eXpress LLC