Articulate the general form of Updates about braid-spec HOT 1 OPEN

For Question 2, I'm copying the pros/cons of "Requiring Patches: 1 in Subscription Responses" from #96 here:

• In requests, Patches: N is already optional because of the existing semantics of HTTP's PATCH method
• In responses, Patches: 1 is optional but this is ambiguous in the spec at the moment we're not sure if it should be required or not

The remainder of work to decide on in this issue is whether patches: 1 is mandatory in subscriptions when a transaction contains 1 patch.

For / against:

• Make patches: 1 in subscription responses optional:
  • In some systems sending multiple patches within a transaction is invalid so they wouldn't need to implement parsing for that header
  • The network protocol is simpler and smaller (1 less header)
  • This is symmetric with the logic for PATCH requests
• Or make patches: X in subscription responses mandatory, even when only one patch is being sent
  • As Mike said, the logic for this will generally be needed anyway
  • And if that logic is implemented, requiring it will make the parser a bit simpler (since there aren't multiple modes or anything like that)

from braid-spec.