Re: [apps-discuss] [Technical Errata Reported] RFC6839 (4367)

[Ned Freed <[e-mail]>]

> On 15/05/2015 17:53, Tony Hansen wrote:
> > There is one more constraint for a file written with utf-8 to use the
> > encoding of 8bit: the lines are limited to 998 bytes in length (not
> > counting the CRLF line terminators). See RFC 2045 for details.

> I think that would be a problem for JSON - there's no way (I know of) to break
> long text strings over multiple lines, so that restriction would rule out very
> long string values.  So maybe "binary" is the right choice.

The same can be said for XML - multimegabyte XML objects containing no line
breaks at all are pretty common. And while you can in theory encode text()
nodes as CDATA, introducing line breaks into XML isn't something you can just
do and leave the semantics unchanged.

It's also the case that the line terminators in an XML or JSON object may not
always be CRLF, and thus an object may not be compatible with 7bit or 8bit on
that basis.

But the fact remains that a lot of XML and JSON objects are 8bit or even 7bit
compatible. In fact a lot of formats based on XML or JSON are by their nature
_always_ 8bit or 7bit compatible. And I see some value in pointing that out
where it's appropriate to do so.

I suppose we could insist on a full rundown of the issues in every
registration. But do you really think this is a useful thing to do, rather
than leaving it a judgement call on the part of the person constructing
the registration?

				Ned