<div dir="ltr">Sorry must have replied at the same time :)<br><div class="gmail_extra"><br><div class="gmail_quote">On 29 June 2015 at 23:50, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">I'll attempt to answer as if it's a quiz and then Russell can tell us what's right and wrong when he gets back online Aussie time. :)<br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Mon, Jun 29, 2015 at 8:03 AM, Karen Bradshaw <span dir="ltr"><<a href="mailto:kbhawkey@gmail.com" target="_blank">kbhawkey@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div dir="ltr" style="font-size:12.8000001907349px">Hi, Russell. I just started to look at this code but thought of a few questions,<div>1) How did you validate the generated swagger-json files?</div></div></div></blockquote><div><br></div></span><div>Typically you'd use the JSON schema from Swagger itself, see <a href="https://github.com/swagger-api/swagger-spec/blob/master/schemas/v2.0/schema.json" target="_blank">https://github.com/swagger-api/swagger-spec/blob/master/schemas/v2.0/schema.json</a></div><div><br></div><div>However he noted the need for a new schema, which you mention below.</div></div></div></div></blockquote><div><br></div><div>Ah, that kinda validaiton. Well standard Swagger can be validated using JSONSchema <a href="https://github.com/swagger-api/swagger-spec/blob/master/schemas/v2.0/schema.json">https://github.com/swagger-api/swagger-spec/blob/master/schemas/v2.0/schema.json</a></div><div><br></div><div>We will probably have to make our own copy of this and modify it to support our changes.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div dir="ltr" style="font-size:12.8000001907349px"><div>2) Did you create a new schema, Swagger 2.0-OpenStack? What </div><div>does it look like?</div></div></div></blockquote><div><br></div></span><div>It doesn't exist yet, so we'll need to make it.</div></div></div></div></blockquote><div><br></div><div>I'm not sure we will need many more modifications than the ones I have listed in the email sent recently. It really depends if we want to do anything fancy. But yes we should probably formally define what it is. But hopefully no one will ever have to deal with it, because it will be generated.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div dir="ltr" style="font-size:12.8000001907349px"><div>3) Can you elaborate a bit more about the tagging system?</div></div></div></blockquote><div><br></div></span><div>I think Tags in Swagger are per-route. A route is a method (like GET or POST) plus a path (like {tenant_id}/servers/detail).</div><div><br></div><div>However we have groups of Tags for say, "Servers" that has a lot of conceptual information in it: <a href="http://developer.openstack.org/api-ref-compute-v2.html#compute_servers" target="_blank">http://developer.openstack.org/api-ref-compute-v2.html#compute_servers</a> So we need a way to group Tags so that we can insert the conceptual information where it makes sense.</div></div></div></div></blockquote><div> </div><div>Spot on.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>And yes, I believe that's the "narrative doc" we talked about at the Summit. </div></div></div></div></blockquote><div><br></div><div>Now I also understand what that means. OK cool.</div></div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Cheers,<br>Russell Sim</div></div>
</div></div>