Thanks Anne! The use-case is simply to ensure that we serve out accurate links in the version details reponse from the compute API. (I just happened to notice the broken links when poking around the v1.0->v1.1 API changes) BTW I've proposed a change with the WADL being served out of github: https://review.openstack.org/3421 but if you publish the WADL at a well-known path under docs.openstack.org, that would be much better. Cheers, Eoghan ----- Original Message ----- > From: "Anne Gentle" <anne at openstack.org> > To: "Eoghan Glynn" <eglynn at redhat.com> > Cc: openstack at lists.launchpad.net > Sent: Wednesday, 25 January, 2012 5:33:02 PM > Subject: Re: [Openstack] WADL for compute API v1.1 > > Hi Eoghan - > > We will be using that WADL for the API reference site so we've got a > vested interest in its accuracy. Not sure if Github has any policies > about serving files directly. We could copy it to docs.openstack.org > with a Jenkins job if that's helpful. We publish schemas at > http://docs.openstack.org/api/openstack-compute/1.1/xsd/ already. > > Tell us more about your use case and let's see what we can do. > > Thanks, > Anne > > On Wed, Jan 25, 2012 at 10:30 AM, Eoghan Glynn <eglynn at redhat.com> > wrote: > > > > > >> So I was wondering whether there was an intention to publish a > >> v1.1 WADL ... > > > > > > Follow up question: would it be nasty to serve out that WADL > > directly from github? > > > > e.g > > https://github.com/openstack/compute-api/blob/<essex-final-tag>/openstack-compute-api-1.1/src/os-compute-1.1.wadl > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack at lists.launchpad.net > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp >