Does ist make sense to define HTTP-400, 401, 403, 500 and 503 for all endpoints?
@lhess I added them here for all Attendance endpoints. I think it makes sense to add them to all endpoints, but the state atm is that other endpoints sometimes define the responses slightly differently, if not for the actual response value then maybe for the rendered description. Therefore, I'd preferably address the issue at hand rather than expanding the scope right now. Perhaps a follow-up could be an overhaul of this spec, but I have a feeling it might be a rabbit hole, so wouldn't jump into it as part of this change. Does that sound good to you?
@lhess I added them here for all Attendance endpoints. I think it makes sense to add them to all endpoints, but the state atm is that other endpoints sometimes define the responses slightly differently, if not for the actual response value then maybe for the rendered description. Therefore, I'd preferably address the issue at hand rather than expanding the scope right now. Perhaps a follow-up could be an overhaul of this spec, but I have a feeling it might be a rabbit hole, so wouldn't jump into it as part of this change. Does that sound good to you?