Comments on: application/atom+json http://smackman.com/2006/05/08/applicationatomjson/ Putting the smack down, one smack at a time Mon, 06 Sep 2010 10:32:58 +0000 http://wordpress.org/?v=2.0.2 by: Dennis http://smackman.com/2006/05/08/applicationatomjson/#comment-6 Fri, 12 May 2006 04:48:38 +0000 http://smackman.com/2006/05/08/applicationatomjson/#comment-6 Wordpress stripped out some of my Atom code. "Gibberish Code" Should be: <dc:subject>Gibberish</dc:subject> <dc:subject>Code</dc:subject> Hopefully this will work. Wordpress stripped out some of my Atom code.

“Gibberish
Code”

Should be:
<dc:subject>Gibberish</dc:subject>
<dc:subject>Code</dc:subject>

Hopefully this will work.

]]> by: Dennis http://smackman.com/2006/05/08/applicationatomjson/#comment-5 Fri, 12 May 2006 04:43:09 +0000 http://smackman.com/2006/05/08/applicationatomjson/#comment-5 I just spent couple of minutes and looked in the MagpieRSS source code. I see what you are talking about. This chunk of code in rss_parse.inc seems to explain the problem. // if inside an Atom content construct (e.g. content or summary) field treat tags as text elseif ($this-&#62;feed_type == ATOM and $this-&#62;incontent ) { // if tags are inlined, then flatten $attrs_str = join(' ', array_map('map_attrs', array_keys($attrs), array_values($attrs) ) ); $this-&#62;append_content( "" ); array_unshift( $this-&#62;stack, $el ); } The PHP code takes the below Atom data: Gibberish Code And turns it in to (output as JSON): "dc":{"subject":"GibberishCode"} Which I agree is not a good solution, and would go as far as saying that it is just wrong. Flattening the data structure destroys a lot of the stored information (which does not have to happen). I can see at least one solution off the top of my head, but I do not know the ramifications of the modifications without studying the library a good bit more. I just spent couple of minutes and looked in the MagpieRSS source code. I see what you are talking about.

This chunk of code in rss_parse.inc seems to explain the problem.

// if inside an Atom content construct (e.g. content or summary) field treat tags as text
elseif ($this->feed_type == ATOM and $this->incontent )
{
// if tags are inlined, then flatten
$attrs_str = join(’ ‘,
array_map(’map_attrs’,
array_keys($attrs),
array_values($attrs) ) );

$this->append_content( “” );

array_unshift( $this->stack, $el );
}

The PHP code takes the below Atom data:
Gibberish
Code

And turns it in to (output as JSON):
“dc”:{”subject”:”GibberishCode”}

Which I agree is not a good solution, and would go as far as saying that it is just wrong. Flattening the data structure destroys a lot of the stored information (which does not have to happen).

I can see at least one solution off the top of my head, but I do not know the ramifications of the modifications without studying the library a good bit more.

]]> by: steve http://smackman.com/2006/05/08/applicationatomjson/#comment-3 Tue, 09 May 2006 14:31:37 +0000 http://smackman.com/2006/05/08/applicationatomjson/#comment-3 Thanks Dennis -- Actually, it was writing the same PHP script (with Magpie and JSON, but not quite as clean as yours) that lead me to write my post. The problem with this approach is that the schema is reflective of Magpie's internal data structures which I think are lossy (they don't preserve everything from the atom feed, but convert it to a lowest common denominator of atom and rss) and are non standard. I should be able to get an atom+json feed from most sites that already support atom+xml and rely on its structure. James Snell (also at IBM) has agreed to work on this with me... hopefully we'll have an IETF draft soon. Thanks Dennis — Actually, it was writing the same PHP script (with Magpie and JSON, but not quite as clean as yours) that lead me to write my post. The problem with this approach is that the schema is reflective of Magpie’s internal data structures which I think are lossy (they don’t preserve everything from the atom feed, but convert it to a lowest common denominator of atom and rss) and are non standard. I should be able to get an atom+json feed from most sites that already support atom+xml and rely on its structure.

James Snell (also at IBM) has agreed to work on this with me… hopefully we’ll have an IETF draft soon.

]]> by: Dennis http://smackman.com/2006/05/08/applicationatomjson/#comment-2 Tue, 09 May 2006 01:43:04 +0000 http://smackman.com/2006/05/08/applicationatomjson/#comment-2 I wrote up a script to convert different feeds (RSS, Atom) to JSON. You might find it interesting. Write-up: http://www.engrowe.com/2006/05/08/how-to-convert-a-rss-feed-to-json-in-php/ Atom Example: http://www.engrowe.com/rsstojson.php?feed=http://www.engrowe.com/?feed=atom&#38;callback=rss_read I wrote up a script to convert different feeds (RSS, Atom) to JSON. You might find it interesting.

Write-up:
http://www.engrowe.com/2006/05/08/how-to-convert-a-rss-feed-to-json-in-php/

Atom Example:
http://www.engrowe.com/rsstojson.php?feed=http://www.engrowe.com/?feed=atom&callback=rss_read

]]>