Re: Comments and favors on YAML 1.2 spec 2009-07-21

Osamu TAKEUCHI wrote:
> Oren,
> 
> Thanks a lot for the update!
> 
>>> 3. Form feed (#x0C) in YAML 1.2 stream
>>>
>>> There is a note that "YAML 1.2 processors parsing a version 
>>> 1.1 document should therefore treat these line breaks as non-break 
>>> characters, with an appropriate warning" in Sect. 5.4. But it 
>>> seems that the form feed (#x0C), which was a line break in YAML 1.1,
>> Form feed never was a valid line break character. Not in YAML 1.1 and
>> not ever.
> 
> Then, the description in Sect 5.4 is misleading.
> I read "the above line break characters" to indicate #x0C, #x85, 
> #x2028 and #2029.
> 
>> 5.4. Line Break Characters
>>
>>  All other characters, including the form feed (#x0C), are considered 
>> to be non-break characters. Note that these include the non-ASCII 
>> line breaks: next line (#x85), line separator (#x2028) and paragraph 
>> separator (#x2029).
>>
>> YAML version 1.1 did support the above line break characters; however, 
>> JSON does not. Hence, to ensure JSON compatibility, YAML treats them 
>> as non-break characters as of version 1.2. In theory this would cause 
>> incompatibility with version 1.1; in practice these characters were 
>> rarely (if ever) used. YAML 1.2 processors parsing a version 1.1 
>> document should therefore treat these line breaks as non-break 
>> characters, with an appropriate warning.

Here is my version of how to clarify it. The trick is to stop mentioning 
characters that are not relevant to either version:

5.4. Line Break Characters

  All other characters are considered to be non-break characters.

  YAML version 1.1 defined the non-ASCII characters next line (U+0085), 
line separator (U+2028), and paragraph separator (U+2029) to be line 
break characters; however JSON does not. To ensure JSON compatibility, 
YAML treats them as non-break characters as of version 1.2. In theory 
this would cause incompatibility with version 1.1; in practice these 
characters were rarely (if ever) used. YAML 1.2 processors parsing a 
version 1.1 document should therefore treat these line breaks as 
non-break characters, with an appropriate warning.

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf