Has there been any thought yet on creating an API for ws-commons XmlSchema, separate from the implementation (e.g. as interfaces in separate packages). This would allow some other project's API to expose XmlSchema as an API, without being tied to the ws-commons implementation.
This may not be an issue for most Apache WS projects, but Woden for example will define a WSDL 2.0 API and implementation separately to cater for users who may wish to re-implement bits themselves. For example, if we could expose XML schema through the Woden API using a ws-commons XmlSchema API, then when Eclipse uses Woden it may choose to provide its own EMF-based implementation of XmlSchema. I'm not expecting someone else to do all the work, just getting your feedback initially. John Kaputin IBM
