OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-cap message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [emergency-cap] CAP Issue 23 - Specify JSON serialization

If anything the character-encoding situation is a bit simpler in JSON... most things are.  However, there are validated solutions for XML internationalization as well... the problem being that many (probably most) implementers aren't fully abreast of them.  "I18N" is still viewed in many English-speaking software shops as an arcane specialty.  Programmers in other parts of the world tend, in my experience, to be a bit more cognizant.

You do raise an interesting additional question, however, which is whether it might be beneficial to specify the character encoding, optionally like the language, in the CAP message body itself.  How does ASN.1 address that, I wonder?

- Art

> On Oct 29, 2014, at 07:20, Eliot Christian <eliot.j.christian@gmail.com> wrote:
> There continue to be nasty issues cropping up in the details, especially wrt character encoding. Although not much of an issue for those whose applications just use ASCII, but it's a major pain for the rest of the world's languages. I would be surprised if applications using JSON do not have character encoding problems (indeed, such problems bedevil XML as well). Such problems may not be specific to the serialization itself, but how serialization and structure passing interacts with a programming language, a Web container, an operating system, HTML, and so forth.  

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]