Fwd: YAML simplification

--===============7053524126671668002==
Content-Type: multipart/alternative; boundary="001a114ff454ae8d980566ac660c"

--001a114ff454ae8d980566ac660c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi all,

>There are categories of change for the above: Syntax and Schema. Syntax is
an obvious concept. Schema (especially for YAML) is more >complex and
nuanced.

Well, syntax is an obvious concept. But it has non-obvious implementation.
The syntax is changed with every version. It will keep to change with every
version if every version is adding new features.
Where is the limit ?
What I want to say is that already now the syntax is overloaded. Users (the
ones which contact me) do not understand it. That is why I vote for the
radical simplification.

If we do not want to simplify the syntax then:
1. The %YAML <VERSION >directive must become mandatory
2. SCHEMA definition should not be a part of a YAML document. The context
must not be defined in the document.

P.S. It is sad that communication happens in a place which is not indexed
by search engines and it is available to a a handful participants only...

Cheers,
Andrey


On Mon, Mar 5, 2018 at 11:46 AM, Tina M=C3=BCller <[email protected]> wrote:

> On Sun, 4 Mar 2018, Ingy dot Net wrote:
>
> An interesting thing is that all the current implementations do have
>> =E2=80=9Cschemas=E2=80=9D but not in any concise doc. The schema for a g=
iven
>> implementation
>> is encoded in programming source code.
>>
>
> My YAML::PP project (perl) is schema aware, and you can already
> choose between Failsafe, JSON and Core, for loading.
> It's work in progress, though, but I wanted to mention that
> there is something going on regarding that.
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Yaml-core mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/yaml-core
>
>

--001a114ff454ae8d980566ac660c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_quote"><br><div dir=3D"ltr">Hi all=
,<br><div><span class=3D""><br><div>&gt;There are categories of change for =
the above: Syntax and Schema.=20
Syntax is an obvious concept. Schema (especially for YAML) is more=20
&gt;complex and nuanced.<br><br></div></span><div>Well, syntax is an obviou=
s concept. But it has non-obvious implementation.<br></div><div>The syntax =
is changed with every version. It will keep to change with every version if=
 every version is adding new features.<br></div><div>Where is the limit ? <=
br></div><div>What I want to say is that already now the syntax is overload=
ed. Users (the ones which contact me) do not understand it. That is why I v=
ote for the radical simplification.<br><br></div><div>If we do not want to =
simplify the syntax then:</div><div>1. The %YAML &lt;VERSION &gt;directive =
must become mandatory<br>2.  SCHEMA definition should not be a part of a YA=
ML document. The context must not be defined in the document.<br><br></div>=
<div>P.S. It is sad that communication happens in a place which is not inde=
xed by search engines and it is available to a a handful participants only.=
..<br><br></div><div>Cheers,<br></div><div>Andrey<br><br></div></div></div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><div><div class=
=3D"h5">On Mon, Mar 5, 2018 at 11:46 AM, Tina M=C3=BCller <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>=
&gt;</span> wrote:<br></div></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><di=
v class=3D"h5"><span>On Sun, 4 Mar 2018, Ingy dot Net wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
An interesting thing is that all the current implementations do have<br>
=E2=80=9Cschemas=E2=80=9D but not in any concise doc. The schema for a give=
n implementation<br>
is encoded in programming source code.<br>
</blockquote>
<br></span>
My YAML::PP project (perl) is schema aware, and you can already<br>
choose between Failsafe, JSON and Core, for loading.<br>
It&#39;s work in progress, though, but I wanted to mention that<br>
there is something going on regarding that.<br></div></div><span class=3D""=
>------------------------------<wbr>------------------------------<wbr>----=
--------------<br>
Check out the vibrant tech community on one of the world&#39;s most<br>
engaging tech sites, Slashdot.org! <a href=3D"http://sdm.link/slashdot" rel=
=3D"noreferrer" target=3D"_blank">http://sdm.link/slashdot</a><br>_________=
_____________________<wbr>_________________<br>
Yaml-core mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Yaml-c=
[email protected]<wbr>t</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/yaml-core" rel=3D"n=
oreferrer" target=3D"_blank">https://lists.sourceforge.net/<wbr>lists/listi=
nfo/yaml-core</a><br>
<br></span></blockquote></div><br></div>
</div><br></div>

--001a114ff454ae8d980566ac660c--


--===============7053524126671668002==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
--===============7053524126671668002==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Yaml-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yaml-core

--===============7053524126671668002==--