("Method" as the column name is actually incorrect... they're just bare C functions.)
It's pretty standard to have the function's type signature and possibly a short description in the function lists of API docs. Here's a random example:
http://ffmpeg.org/doxygen/trunk/group__lavc__fft.html#func-m...
If a function has the same name across different versions of the OpenGL API, does it also have the same type signature? If so, it would be nice to have a version of this with more details.
The docs should be just about the OpenGL functions, not about how C implements them.
I think we should start to transition to using the word function only in the connotation provided in functional programming languages, where functions are first class citizens and can be treated as values. Also, should probably prefer to imply a lack of side effects from the word function.
Method is clearly a certain function or procedure that is scoped to a class. So that leaves procedure as a name left over for the type of bare function that isn't a value, that is a statement rather than an expression.
I think subroutine and subprogram are just archaic sounding, and don't really imply anything that the others don't. Method, functions, procedures, I think that's all we need.
So, strlen, for example, is a function, and printf is a procedure.
(Yes I know prints returns an int, but it's run for it's side effects primarily.)
What you are talking about might be called a relation, which is more general.