To be clear here, I don't mean we shouldn't include what new APIs will be created, I think that is essential. But rather, remove the need to specifically spell out the request and response blocks.
Personally, I find it redundant for a few reasons:
1) We already have identity-api, which will need to be updated once the spec is completed anyway.
2) It's easy to get bogged down in the spec review as it is, I don't want to have to point out mistakes in the request/response blocks too (as I'll need to do that when reviewing the identity-api patch anyway).
3) Come time to propose the identity-api patch, there might be differences in what was proposed in the spec.
Personally I'd be OK with just stating the HTTP method and the endpoint. Thoughts?
Many apologies in advance for my pedantic-ness!
Regards,
Steve Martinelli
Software Developer - Openstack
Keystone Core Member
|
| |
| Phone:
1-905-413-2851 E-mail: [email protected] |
8200 Warden Ave Markham, ON L6G 1C7 Canada |
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
