Re: Fwd: Is there a slim YAML?

mofo syne <[email protected]>
Newsgroups gmane.text.yaml.general
Message-ID <CAPJM1pdzFnFFeXiUc=hR9s-uqTCqiOVDCUYjFJQoGHjtfaBHvg@mail.gmail.com>
In terms of naming... "simple YAML" sounds... well too simple.

A nicer name might be

*CoreYAML*:
   - Aka: cYAML, C YAML
     Definition: |
                         Small fast minimally specced YAML with fast C
reference parser.
                         At the very least should be able to convert from
JSON to YAML 1-1

And yes, we do want an officially 'reduced spec' edition for embedded
systems, else we just going to fork until it exist. Maybe split the
official specification to 3 levels of increasing complexity, with each
higher edition being a subset of the more basic version.

E.g. "Core YAML" --> "Simple YAML" -->  "YAML Complete"

Where the Core YAML, is the most utterly basic and smallest parser
acceptable to run everywhere (1-1 with json), and higher version works for
more complex applications.

If it takes an implementer's guide, then so be it.. But there is an urgent
need for a common standard to stick to, when wanting a more simpler
"edition" of YAML.

Soooo yea. Get us Core YAML and we shall be a bunch of happy penguins (As
well as many people who just need a low fat no frills configuration
standard to stick to). Plus it increasing the likely hood that coreYAML
will be included in other interpreters like python as "batteries included"
:D .



On Fri, Nov 14, 2014 at 8:30 AM, Trans <[email protected]> wrote:

>
> ---------- Forwarded message ----------
> From: Trans <[email protected]>
> Date: Thu, Nov 13, 2014 at 4:30 PM
> Subject: Re: [Yaml-core] Is there a slim YAML?
> To: mofo syne <[email protected]>
>
>
>
>
> On Wed, Nov 12, 2014 at 9:01 PM, mofo syne <[email protected]> wrote:
>
>> trans,
>>
>> http://talk.commonmark.org/t/metadata-in-documents/721/37?u=mofosyne
>>
>> Regarding your current EBNF for diet-yaml
>>
>> jgm said (in link above):
>>
>> >>>
>>
>> This would not be hard to parse, but seems to lack what I think is a
>> crucial feature: the ability to specify multiline strings using |:
>>
>> > title: My Article
>> > abstract: |
>> >         This is the abstract of my
>> >          article.  It can go on and on.
>>
>> >         It can even have two paragraphs,
>> >         or a list:
>>
>> >          - one
>> >         - two
>>
>>
> Actually, though it hasn't been specified anywhere as of yet, it may be
> that Diet YAML will always use an implied `|` for multi-line strings.
>
> In any case, to be clear the EBNF given is not considered complete. It's
> just a first stab.
>
>
>
>
>
>
> --
> Sorry, says the barman, we don't serve neutrinos. A neutrino walks into a
> bar.
>
> Trans <[email protected]>
> 7r4n5.com      http://7r4n5.com
>
>
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
> _______________________________________________
> Yaml-core mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/yaml-core
>
>

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk

_______________________________________________
Yaml-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yaml-core
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.