YAML 1.2 spec question: absence of in-flow in flow mapping entries

To the writers of the YAML 1.2 spec,

Thanks for your replies to all my questions. I'd like to reiterate my
thanks for such a lovely little data language.

I have another question, this time pertaining to rule #139,
c-flow-mapping(n,c). I think that instead of:
  “{” s-separate(n,c)?
  ns-s-flow-map-entries(n,c)? “}”

...it should be:
  “{” s-separate(n,c)?
  ns-s-flow-map-entries(n,in-flow(c))? “}”

This matches rule #136, c-flow-sequence. Without this change, all
nodes inside a flow mapping would be interpreted in whatever context
the entire mapping happens to sit in, even if it's flow-out. That
means the following document is invalid:
  {a: 1, b: 5}
...because the 1 (and the 5), as plain scalars in a flow-out context,
would consume the comma (and brace) indicators they are adjacent to.
If c-flow-sequence did not use in-flow either, it would share the same
problem.

Sincerely,
Joshua Choi

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects