Another JSON Schema in the IETF?

[Andrew Newton]

I wish to bring this to the attention of this community.

https://mailarchive.ietf.org/arch/msg/json/W5k7W204RrpErkQswys-FNeTKH4

Please keep in mind that this does not mean the IETF is moving forward
on the topic. However it is important that this community be aware of
other efforts.

-andy

[Henry Andrews]

Thanks, Andy.  We are aware of it.  It's by someone who wanted things out of JSON Schema that were against the direction of the project.  Or in some cases could be done but not RIGHT THEN THAT WEEK like he wanted.  I actually encouraged him to write his own spec; really the only thing that I have a problem with is that the name is confusingly close to ours, but he's gotten that feedback from the IETF folks as well.

I personally don't thing that his system will hold up under a broad enough range of use cases, but if it finds a home and he's willing to slog through the IETF politics he's welcome to do so.  We're focused on improving the experience of the large existing JSON Schema community, which will hopefully continue to expand.

I believe one of our editors- Austin Wright- has been keeping a closer eye on that discussion.

thanks,

-henry

--

You received this message because you are subscribed to the Google Groups "JSON Schema" group.

To unsubscribe from this group and stop receiving emails from it, send an email to json-schema+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/json-schema/CAAQiQRcYFamp%2BCb0tCuMSy1LpG28%2BKXAG3UJoSM%2BJm0C%3DiKv1A%40mail.gmail.com.

[Andrew Newton]

Henry,

Yes, the name collision is unfortunate and somewhat inappropriate. I'm
glad you are on top of this already.

take care.
-andy

On Thu, Jul 25, 2019 at 7:25 PM 'Henry Andrews' via JSON Schema
<json-...@googlegroups.com> wrote:
>
> Thanks, Andy. We are aware of it. It's by someone who wanted things out of JSON Schema that were against the direction of the project. Or in some cases could be done but not RIGHT THEN THAT WEEK like he wanted. I actually encouraged him to write his own spec; really the only thing that I have a problem with is that the name is confusingly close to ours, but he's gotten that feedback from the IETF folks as well.
>
> I personally don't thing that his system will hold up under a broad enough range of use cases, but if it finds a home and he's willing to slog through the IETF politics he's welcome to do so. We're focused on improving the experience of the large existing JSON Schema community, which will hopefully continue to expand.
>
> I believe one of our editors- Austin Wright- has been keeping a closer eye on that discussion.
>
> thanks,
> -henry
>
>
> On Thursday, July 25, 2019, 03:18:04 PM PDT, Andrew Newton <an...@hxr.us> wrote:
>
>
> I wish to bring this to the attention of this community.
>
> https://mailarchive.ietf.org/arch/msg/json/W5k7W204RrpErkQswys-FNeTKH4
>
> Please keep in mind that this does not mean the IETF is moving forward
> on the topic. However it is important that this community be aware of
> other efforts.
>
> -andy
>
> --
> You received this message because you are subscribed to the Google Groups "JSON Schema" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to json-schema...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/json-schema/CAAQiQRcYFamp%2BCb0tCuMSy1LpG28%2BKXAG3UJoSM%2BJm0C%3DiKv1A%40mail.gmail.com.
>

> --
> You received this message because you are subscribed to the Google Groups "JSON Schema" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to json-schema...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/json-schema/1429807424.790236.1564097124392%40mail.yahoo.com.