You just said it yourself: it’s easier to parse. That’s the business case.

Scott
--
R. Scott Granneman
sc...@granneman.com ~ www.granneman.com
Contact info: granneman.tel

“You must first have a lot of patience to learn to have patience.”
      ---Stanislaw Lem

On 6 Jun 2017, at 12:41, James Smits wrote:

I know this is the wrong list for this, but JSON Feed seems like as much of a joke as Feed.TXT. RSS works and has widespread adoption. As far as I
can tell there is no upside to JSON feed other than "it isn't XML".  I
don't see a business case for supporting another feed format simply because
JSON is easier to parse.

On Tue, Jun 6, 2017 at 3:25 AM, Gerald Bauer <gerald.ba...@gmail.com> wrote:

Hello,

   The structured meta data block is (simplified) YAML [1] e.g:

id:        http://therecord.co/chris-parrish
 title:     Special #1 - Chris Parrish
 url:       http://therecord.co/chris-parrish
 summary:   Brent interviews Chris Parrish, co-host of The Record and
one-half of Aged & Distilled.
 published: 2014-05-09T14:04:00-07:00
 attachments:
 - url:
http://therecord.co/downloads/The-Record-sp1e1-ChrisParrish.m4a
   mime_type:     audio/x-m4a
   size_in_bytes: 89970236,
   duration_in_seconds: 6629


   As an alternative you can use "classic" JSON or newer human
versions (e.g. SON - Simple Object Notation, JSON5 or HJSON, for
example). If you use JSON than the begin / next / end marker change
e.g.:

   |>>>      becomes    |{
   </>        becomes   }/{
   <<<|      becomes    }|

     Cheers.

[1] Good point- I know JSON is a subset of YAML and JSON is YAML but
YAML is not JSON etc.

PS: In difference to the new YAML Feed format - Feed.TXT looks like a
joke too ;-) It's easy it can't be true but it's for real e.g. all
content blocks use plain text with markdown formatting conventions ;-)
 No more need to clean the HTML for cross-site scripting etc.
_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss



_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
https://pairlist6.pair.net/mailman/listinfo/markdown-discuss

Reply via email to