#178: Serialization of natural language in data formats such as JSON [I18N]

Visit on Github.

Opened May 18, 2017

Hello TAG!

I'm requesting a TAG review of:

Further details (optional):

  • Relevant time constraints or deadlines: None specifically, but this has been a developing problem for us.

You should also know that...

The Internationalization WG has been commenting on data format specifications with increasing frequency over the past couple years in which we have noted the lack of natural language string types in formats such as JSON. We are concerned that there are internationalization gaps or, in an attempt to address our comments, non-interoperable and divergent implementation choices being made.

This issue is the result of an I18N WG action.

We would like the TAG's opinion on the problem and mooted solutions. The I18N WG chair (@aphillips) and Team contact (@r12a) can be available for consultation as needed.

We'd prefer the TAG provide feedback as (please select one):

  • open issues in our Github repo for each point of feedback
  • open a single issue in our Github repo for the entire review
  • leave review feedback as a comment in this issue and @-notify [@aphillips][@r12a]

Discussions

2018-12-04

Minutes

Bumped to next week, waiting for @dbaron

2019-01-15

Minutes

David: was discussed at TPAC (two years ago). We had hoped that Addison or Richard would write something, but we've lost the context... Perhaps I should take a pass at writing this.

Dan: Any way we can get this off the books? Can we try to resolve/close this at the next F2F?

2019-03-19

Minutes

torgo: Can we close this one?

sangwhan: Yes, actually!

sangwhan: I don't know that I have anything to add here, I think they're doing some work on it...

torgo: We have precedent for closing issues when there's ongoing work but no open questions as such. Let's close this off.

sangwhan: I volunteer.