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

WordPress Trac noreply at wordpress.org
Sat Nov 9 19:54:55 UTC 2013


#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 matt):

 Atom! Haven't heard that one in a while. :) Regardless, let's try to keep
 personal swipes ("so-and-so person is hardly the best") out of Trac.

 Whatever you think of RSS 2 as a standard, the way WP produces feeds is
 probably the most widely understood and tested feed format in the world.
 It's a "good standard" in that you can look at what's in our database,
 look at the code that produces the feed, and parse it in a deterministic
 way. The "problem" with RSS produced by lots of different and non-
 transparent code may be large, but for WP it's largely non-existent.

 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.

 Imagine switching out the library you use for grabbing a feed from an
 expensive XML-based one to a lightweight JSON one, maybe changing a
 variable name or two for things that are namespaced (which doesn't make
 sense to try and duplicate, because there's no XML-style extensibility
 model we're trying to build in), and then the rest of your code runs
 exactly the same. With a callback you could even do it entirely client-
 side and cross-domain.

 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.

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


More information about the wp-trac mailing list