I keep thinking the formats op has confusing tags when determining perspective of who is reading and writing. So I wanted to suggest we change those tags to:

• receive: Marker tag if server can receive requests in this format (client can POST this format)
• send: Marker tag if server can send responses in this format (client can request the response type using the Accept header)

Or we could use request and response tags if anybody prefers that.

Anybody have problem with that change?

Sounds good to me. I think I like receive and send better than request and response.

On principle I'm also fine with the change, however I think a little bit of due diligence is called for!! :)

• Do you have a particular Use/Case in mind or is this just a matter of correcting or improving the semantics of the Op?
• Is the change necessary? In other words, if it ain't broke does it need to be fixed?
• There were some other people on the forum here from outside of the Niagara/SkySpark community who were using the Haystack protocol, how will this change affect them?
• Will you include backwards compatibility for systems that may be using the existing format? Although I grant you that there may not be that many and it might not be a real problem.
• While making this change to this Op is there any other tags or metadata that should be included?
• While making this change are there any other pending changes or proposed changes to other Ops that should be made at the same time?

I agree with Mike on the send/receive rather than request/response.

In this particular case, I think:

1. its really just to make it less confusing
2. I seriously doubt anyone is using this particular op which is why I think its probably safe to change

But I figured its still good to post a breaking change here. If no one has anything to say, then probably safe to say this isn't being used