Here is a suggestion for proposal format: �� - An executive summary �� - A detailed proposal which should include �� � � - The problem being addressed - The approach being proposed �� � � - Pro's (why this and not another approach) �� � � - Con's (what are the issues that come up with this approach) - How does this impact other aspects of the standard - Semantics �� � � - Can this same functionality be obtained within the current �� � � � � standard, but maybe in a less convenient manner - Specific API proposal ** this would be a good point for input from others, before a lot of time is spent on implementation. ** �� � � - Discussion of the prototyping work - pointer to buildable source for the implementation Any suggestions on how to improve this ? Rich
participants (1)
-
Richard Graham