Re: JSON v. YAML key/value
Oren Ben-Kiki <[email protected]>
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <CADJiDhtkEZE-2J-EdJRepZrbJkTJg7Z-_f-c=18WRYe1qFagag@mail.gmail.com> |
Section 7.4.2 covers this, see example 7.18 - the space following the ":" is not needed for JSON-compatible keys. Section 2 serves just as a short preview to YAML syntax; the definite spec is in the following sections. On Thu, Sep 25, 2014 at 8:44 PM, Greg Martin <greg-cP96eOg/[email protected]> wrote: > > YAML1.2 2.1 Collections says: Mappings use a colon and space (“: ”) to > mark each key: value. > > The JSON spec only requires a ":". > > Does this mean to be valid YAML a JSON file must mark key/values as per > 2.1? > > Thanks (and greetings). > > Greg. > > > > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Yaml-core mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/yaml-core > ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Yaml-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/yaml-core