Re: Spec API, was: Spec schemata

2007-02-28 Thread Mike Edwards
Jeremy, I have not got around to the Java API files yet. It is my intention to publish them from www.osoa.org, probably bundled as a single zip or jar file. Haven't decided the exact url yet - suggestions welcome. I haven't given the idea of putting them on a Maven repository any thought a

Spec API, was: Spec schemata

2007-02-28 Thread Jeremy Boynes
Mike You mention Java API files - are those available as well? If so, do you intend to also distribute them through the Maven repo system? Thanks -- Jeremy On Feb 28, 2007, at 3:13 AM, Mike Edwards wrote: Folks, 1) I am arranging to publish all of the SCA spec schemas on the www.osoa.or

Re: Spec schemata

2007-02-28 Thread Mike Edwards
Folks, I can confirm that the current 1.0 spec schemas are available on http://www.osoa.org/xmlns/sca/1.0/.xsd Yours, Mike. Jeremy Boynes wrote: The sca-api module contains old versions of the schemas from 0.9 days. I think we should remove these from the jar as they are orthogonal fro

Re: Spec schemata, was: Review of spec classes wanted

2007-02-28 Thread Mike Edwards
Folks, 1) I am arranging to publish all of the SCA spec schemas on the www.osoa.org site - we've completed a site upgrade that now allows us to publish random files outside the Wiki. So, expect to see the 1.0 SCA XSDs on http://www.osoa.org/xmlns/. by the end of today. Please note that

Re: Spec schemata, was: Review of spec classes wanted

2007-02-26 Thread Jean-Sebastien Delfino
[snip] Jeremy Boynes wrote: The sca-api module contains old versions of the schemas from 0.9 days. I think we should remove these from the jar as they are orthogonal from the Java APIs. We could package them separately, on our website, or just leave them to the spec to publish (as the URIs point

Spec schemata, was: Review of spec classes wanted

2007-02-26 Thread Jeremy Boynes
The sca-api module contains old versions of the schemas from 0.9 days. I think we should remove these from the jar as they are orthogonal from the Java APIs. We could package them separately, on our website, or just leave them to the spec to publish (as the URIs point back to their website). --