[wp-trac] [WordPress Trac] #25639: Implement a JSON feed using rssjs.org spec

[WordPress Trac]

#25639: Implement a JSON feed using rssjs.org spec
------------------------------------+-----------------------
 Reporter:  nacin                   |       Owner:  pento
     Type:  feature request         |      Status:  assigned
 Priority:  normal                  |   Milestone:  3.8
Component:  Feeds                   |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  dev-feedback has-patch  |
------------------------------------+-----------------------

Comment (by pento):

 Replying to [comment:19 matt]:
 > The main point of introducing a JSON style feed would be to make it
 easier for people to consume WP-generated content in a programatic way,
 hopefully leveraging code they've already written. Under that assumption
 it seems the lowest-friction thing to do for potential users of this feed
 would be to keep the content, the variables if you will, exactly the same
 as our RSS2 implementation, and just change the wrapper.

 I don't think this is a good reason to stick with RSS. It wouldn't be
 exactly the same code to handle the data coming from the JSON feed - for
 example, JSON doesn't encode HTML like the RSS feed has to. I think this
 also overestimates the time commitment in learning a new standard, both
 from a personal point of view (it takes a very small amount of time to
 read the AS1 spec and understand it), and from a global point of view
 (there are very few WordPress users who will need to learn this, so it's
 only a minor inconvenience on a global scale).

 With regards to namespacing, there are currently several different
 proposals in the [http://rssjs.org/ rss.js discussion thread] about how to
 handle this. Implementing a particular method before a decision is made
 seems to be premature, in the same way implementing AS2 before the spec is
 finished would be.

 > This is a green field thing, something we want to do because we think
 people will use it in interesting ways, not because there are existing
 implementations or demand. After launch if this picks up traction I could
 see us doing an iteration on the format adding a field or two to ease make
 it easier for people writing code using these feeds, maybe adding a
 "redundant" date field in a format easier to natively parse in pure JS. I
 could also see us adding in an Activity Streams JS feed, but personally
 would rather wait until the working group finishes 2.0.

 If this is a green field thing, why restrict ourselves to RSS? Surely we
 should choose the best-defined option, to give the developers who use it
 the most deterministic outcome, especially if they want to reuse code on
 reading JSON feeds from other services.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/25639#comment:21>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software