New issue: extensibility/versioning in mtom elements

Please add a new issue: what is the extensibility and versioning strategy
for mtom elements?   Do we allow extensibility of attributes and/or
elements, and if so, what is the processing model for extensions?  What is
the policy related to the miffy namespace name for future elements and/or

I have some thoughts on the right way to do this at


Received on Wednesday, 3 December 2003 13:27:19 UTC