Re: what will be the nature of yaml 2.0 eyaml

I made "specs" for these 2 concepts over the past years:

   - Yadda <https://github.com/ingydotnet/yadda#readme> A YAML like config
   file language.
   - JSYNC <http://jsync.org/> A JSON full serialization language

Note that they are both heavily YAML influenced but neither is a direction
for YAML.

Until this past week, only a handful of people have ever talked about the
YAML2 wiki. I started it in 2011 as a place to work on new YAML with a
focus on making it simpler based on real world experience.

I don't endorse eYAML. It was written by someone last year who was new to
YAML and wanted to see it simplified. He added a lot of content to the
wiki. It should be groomed.

I'm not yet certain whether or not a reduced, minimal grammar should be
considered. It is certainly possible, but I think its a slippery slope once
you go that way.
YAML::Tiny <https://metacpan.org/pod/YAML::Tiny#YAML-TINY-SPECIFICATION> is
a mature project that has served the Perl community pretty well.

On Sun, Mar 6, 2016 at 11:33 AM, Oren Ben-Kiki <[email protected]> wrote:

> There are two possible intermediate points between YAML and JSON.
>
> One is to keep the JSON data model and the YAML syntax (that is, no tags,
> no directives, but allow block styles).
>
> Another is to keep the YAML data model (specifically, tags) and JSON
> syntax (with minimal extensions - that is, tags again).
>
> You want the first. The thing is, you can have it today. It is trivial to
> load a JSON file into YAML (JSON is valid YAML after all) and dump it again
> with improved formatting (using block styles). Likewise, it is trivial to
> load a YAML file that has no tags or directives and dump it as JSON.
>
> I'm not certain why you'd need YAML 2.0 (or 1.3) for this...
>
>
> On Sun, Mar 6, 2016 at 9:12 PM, Britton Kerin <[email protected]>
> wrote:
>
>> I hope for a fixed JSON really.  The noise syntax gone as much as
>> possible in favor of indentation.  Spreading strings across lines and
>> having the newlines magically go away might be nice if it could be
>> done dead simple.  I have no interest or trust in anything more
>> complex.
>>
>> I think something like this could be pretty successful especially if
>> it started out with javascript and shell to_JSON from_JSON
>> methods/programs.
>>
>> I can't quite tell if this is part of the plan or not?
>>
>> Britton
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Yaml-core mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/yaml-core
>>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Yaml-core mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/yaml-core
>
>

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval

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