<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">On February 9, 2015 at 1:25:58 PM, Jay Pipes (<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>) wrote:</div> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>On 01/20/2015 10:54 AM, Brian Rosmaita wrote:
<br>> From: Kevin L. Mitchell [kevin.mitchell@rackspace.com]
<br>> Sent: Monday, January 19, 2015 4:54 PM
<br>>
<br>>> When we look at consistency, we look at everything else in OpenStack.
<br>>> From the standpoint of the nova API (with which I am the most familiar),
<br>>> I am not aware of any property that is ever omitted from any payload
<br>>> without versioning coming in to the picture, even if its value is null.
<br>>> Thus, I would argue that we should encourage the first situation, where
<br>>> all properties are included, even if their value is null.
<br>>
<br>> That is not the case for the Images API v2:
<br>>
<br>> "An image is always guaranteed to have the following attributes: id,
<br>> status, visibility, protected, tags, created_at, file and self. The other
<br>> attributes defined in the image schema below are guaranteed to
<br>> be defined, but is only returned with an image entity if they have
<br>> been explicitly set." [1]
<br>
<br>This was a mistake, IMHO. Having entirely extensible schemas means that
<br>there is little guaranteed consistency across implementations of the API.
<br>
<br>This is the same reason that I think API extensions are an abomination.
<br>
<br></div></div></span></blockquote><div><br></div><div>This right here! +1. +more than +1 if I get more votes on this.</div><br><blockquote type="cite" class="clean_bq"><span><div><div>Best,
<br>-jay
<br>
<br>__________________________________________________________________________
<br>OpenStack Development Mailing List (not for usage questions)
<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<br></div></div></span></blockquote></body></html>