[wtp-dev] List of "Architecture and Design" issues

[David M Williams <david_williams@xxxxxxxxxx>]

If this lists formats at all ok, its
a list of some issues we've discussed at architecture group that need some
resolution. I won't always post all issues here on this mailing list, but
thought I would 
this time to help get the discussions
started, if there's any community comments, or community issues we haven't
discussed yet. Feel free to comment in the bugzillas or open new ones.
Our discussions tend towards issues that are "across components"
or "across projects", so I'm sure there are other inter-component
issues we haven't really captured well ... such as "is flexible project
API" adequate ... but we'll start with these. I've assigned "owners"
as best I know, but feel free to let me know if I've got that wrong. 

As always, community comments welcome.

ID	Assignee	Reporter	Summary
88009	cbridgha@xxxxxxxxxx	david_williams@xxxxxxxxxx	[arch] Should WTP "operations" be API?
88010	cbridgha@xxxxxxxxxx	david_williams@xxxxxxxxxx	[arch] should EditModel be WTP API?
88011	nitind@xxxxxxxxxx	david_williams@xxxxxxxxxx	[arch] How/When to move to base new common Undo
88012	mdelder@xxxxxxxxxx	david_williams@xxxxxxxxxx	[arch] Should extensible navigator be API?
88013	csalter@xxxxxxxxxx	david_williams@xxxxxxxxxx	[arch] Should tabbed property sheet be API
88014	csalter@xxxxxxxxxx	david_williams@xxxxxxxxxx	[arch] Should URI Resolver be WTP API
88015	csalter@xxxxxxxxxx	david_williams@xxxxxxxxxx	[arch] Is XML Catalog ready for API?
88016	deboer@xxxxxxxxxx	david_williams@xxxxxxxxxx	[arch] Should web browser (view) be in base?
88017	cbrealey@xxxxxxxxxx	david_williams@xxxxxxxxxx	[arch] Should Internet proxy settings move to base?