You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wanted the acknowledge the importance of this project. My team switched our product to JSON5 to simplify data entry for complex data objects by business users (professional - without development knowledge). This has resulted in big productivity gains for us. Previously, we supported json and YAML, which resulted in lot of frustrated users. With JSON5, the number of support cases is much lower.
wanted to suggest that JSON5 will be submitted as internet standard (RFC). I believe that the productivity gains are significant to warrant this effort. Having an RFC will raise the profile of this standard and will encourage other projects to add it as an option. If tools like openapi, schema validations, etc, will adopt the tool, it will create significant synergy.
Needless to say, I do not suggest proposing this as an upgrade to the JSON standard (e.g. JSON 2.0 ). While I personally like the idea, this will be a massive effort.
The text was updated successfully, but these errors were encountered:
Wanted the acknowledge the importance of this project. My team switched our product to JSON5 to simplify data entry for complex data objects by business users (professional - without development knowledge). This has resulted in big productivity gains for us. Previously, we supported json and YAML, which resulted in lot of frustrated users. With JSON5, the number of support cases is much lower.
wanted to suggest that JSON5 will be submitted as internet standard (RFC). I believe that the productivity gains are significant to warrant this effort. Having an RFC will raise the profile of this standard and will encourage other projects to add it as an option. If tools like openapi, schema validations, etc, will adopt the tool, it will create significant synergy.
Needless to say, I do not suggest proposing this as an upgrade to the JSON standard (e.g. JSON 2.0 ). While I personally like the idea, this will be a massive effort.
The text was updated successfully, but these errors were encountered: