Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127897
Precedence: bulk
MIME-Version: 1.0
References: <CAEKnhAF3KOGcWZ6CYxpWkpZbNOGo79DD7p=WsAoJvqdJ5xG_Uw@mail.gmail.com>
 <9B2997E3-21C9-47D9-BB54-99C83A481ED8@php.net>
In-Reply-To: <9B2997E3-21C9-47D9-BB54-99C83A481ED8@php.net>
Date: Sat, 5 Jul 2025 01:30:02 +0200
Message-ID: <CAEKnhAFrvdX2dJ2PKPCUpGS=fP=4eMzsEJNeasX_Hy8n00piOg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] JSON Schema validation support
To: Ben Ramsey <ramsey@php.net>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003d563d063922e035"
From: bukka@php.net (Jakub Zelenka)

--0000000000003d563d063922e035
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi

On Sat, Jul 5, 2025 at 1:10=E2=80=AFAM Ben Ramsey <ramsey@php.net> wrote:

> There are 9 versions of JSON Schema and 11 Internet-Drafts, all of which
> have expired. Many of these versions are still widely used in the wild
> (draft-04, draft-05, and draft-06 come to mind as heavily used, despite
> several newer versions).
>
> Which version do you plan to target with this RFC, or will it be able to
> parse all versions, depending on what the input has specified in the
> `$schema` properties?
>

This is noted in the implementation section:

> The current status is almost complete draft 4 and 6 support. Draft 7
support is coming soon.

By almost I mean that it needs to implement dependencies (which I plan to
sort out before this goes to vote) and it didn't go through complete
regression pack which should happen before the first RC. Draft 7 is pretty
much just "if" so it should be supported as well as it's pretty similar
to dependencies. I will see about other drafts if they could make it to 8.5
but the plan to support eventually all. I will make it a bit clearer in the
RFC. Technically this is more library implementation thing but as it's
bundled it should be properly noted in the RFC as well.


>
> I think your RFC needs to address all these versions and how you plan to
> address compatibility issues between them all.
>
>
All drafts except 4 require $schema to be there so it's the way how to
currently select the version. The future scope actually lists the default
draft for schemas without $schema so it could be selected by users. We
could maybe look into some auto-identification in the future but again it
would be the future scope. I will add some note about it to the RFC.

Since all the I-Ds have expired without a formal IETF RFC being voted on
> and passing, you should probably call attention to the fact that JSON
> Schema, while not moving much right now, is still a moving target and any
> new versions will require updates to the core to support them.
>

Yeah good point I should mention that new version will be treated as
features.

Cheers

Jakub

--0000000000003d563d063922e035
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi</div><br><div class=3D"gmail_quote gmail_quote_con=
tainer"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jul 5, 2025 at 1:10=
=E2=80=AFAM Ben Ramsey &lt;<a href=3D"mailto:ramsey@php.net">ramsey@php.net=
</a>&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
There are 9 versions of JSON Schema and 11 Internet-Drafts, all of which ha=
ve expired. Many of these versions are still widely used in the wild (draft=
-04, draft-05, and draft-06 come to mind as heavily used, despite several n=
ewer versions).<br>
<br>
Which version do you plan to target with this RFC, or will it be able to pa=
rse all versions, depending on what the input has specified in the `$schema=
` properties?<br></blockquote><div><br></div><div>This is noted in the impl=
ementation section:</div><div><br></div><div>&gt;=C2=A0The current status i=
s almost complete draft 4 and 6 support. Draft 7 support is coming soon. </=
div><div><br></div><div>By almost I mean that it needs to implement depende=
ncies (which I plan to sort out before this goes to vote) and it didn&#39;t=
 go through complete regression pack which should happen before the first R=
C. Draft 7 is pretty much just &quot;if&quot; so it should be supported as =
well as it&#39;s pretty similar to=C2=A0dependencies. I will see about othe=
r drafts if they could make it to 8.5 but the plan to support eventually al=
l. I will make it a bit clearer in the RFC. Technically this is more librar=
y implementation thing but as it&#39;s bundled it should be properly noted =
in the RFC as well.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">
<br>
I think your RFC needs to address all these versions and how you plan to ad=
dress compatibility issues between them all.<br>
<br></blockquote><div><br></div><div>All drafts except 4 require $schema to=
 be there so it&#39;s the way how to currently select the version. The futu=
re scope actually lists the default draft for schemas without $schema so it=
 could be selected by users. We could maybe look into some auto-identificat=
ion in the future but again it would be the future scope. I will add some n=
ote about it to the RFC.</div><div><br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex">
Since all the I-Ds have expired without a formal IETF RFC being voted on an=
d passing, you should probably call attention to the fact that JSON Schema,=
 while not moving much right now, is still a moving target and any new vers=
ions will require updates to the core to support them.<br></blockquote><div=
><br></div><div>Yeah good point I should mention that new version will be t=
reated as features.=C2=A0</div><div><br></div><div>Cheers</div><div><br></d=
iv><div>Jakub</div></div></div>

--0000000000003d563d063922e035--