Ok, fine. I agree, its better since that would make sure both the XSD and the api agree with each other. Thanks your time!
On Wed, Jul 10, 2013 at 3:45 PM, Julien Danjou <[email protected]> wrote: > On Tue, Jul 09 2013, Jobin Raju George wrote: > > > The reason I initiated to contribute the XSD was most of the other > > components(nova, keystone, glance, etc.) have their XSD's in the > > repository, so assuming they were contributed by people like me(and > updated > > from time to time by the same or other fellows), I would patch this XSD > to > > the repository. > > > > However, since XSD's need to be updated as soon as the respective API's > > are, I am not sure whether they are updated by dedicated developers. > Please > > let me know if there are such restrictions. Thanks for your time! > > I think that what Doug meant, is that since our API is autogenerated > From Python code, the XSD could likely be autogenerated from this code > too, if we had the right tool. It would therefore be better to build > such a tool than to maintain an XSD file by hand, as far as brave your > hands can be. > > -- > Julien Danjou > -- Free Software hacker - freelance consultant > -- http://julien.danjou.info > -- Thanks and regards, Jobin Raju George Third Year, Information Technology College of Engineering Pune Alternate e-mail: [email protected]
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
