|
I think a realistic approach would be to first get the W3C to publish a few notes on transport dependent methods of compressing and sending data.
For HTTP it is clear that using things such as gzip transfer encoding is a reality, there are other compression options for most other transport formats.
this would refine the use case for binary xml,
I would propose to nominate at least one person who has implementation exp from each of the following activities to be in the W3c group resp for the generation of spec;
- XML signature/encryption
- XSLT Compiler
- ASF BCEL (aka javaclass )
The reason to use binary xml is simple and clear, its an optimisation step....the group responsible for generating a spec *needs* to have implementation exp with a vast range of xml technoligies.
Lastly, if a binary format is required then it should have a royalty free license and usable in all open source scenarios.
|