Hi Bob,
Welcome to the list; I hope the rest of you were able to get your
message, since you don't appear to be subscribed yet.
On Jan 5, 2006, at 12:55 PM, Bob Ippolito wrote:
From what I understand, you're missing the point. The key is that
the <SCRIPT> tag can be used to load JAHAH across domains, thus the
payload absolutely must be JavaScript of some sort. JSON is the
simplest subset of JavaScript to produce, so it's the only good
choice here.
Ah, okay. One man's bug is another's feature. :-)
YAML is technically a superset of JSON these days, but YAML is
extremely difficult to parse and good parsers aren't available
everywhere. JSON is extremely simple to parse, and good parsers
are available pretty much everywhere. As far as Python goes, YAML
is pretty much dead in the water.
Interesting -- I've heard similar rumblings from the Ruby community.
So, has anyone done a JSON<->XOXO bridge?
-- Ernie P.
-bob
On Jan 5, 2006, at 10:47 AM, Dr. Ernie Prabhakar wrote:
Hi David,
Welcome to the list, and thanks for this innovative contribution!
I do have one concern, though. JSON sounds an awful lot like
YAML and (especially around here) XOXO:
http://www.yaml.org/
http://microformats.org/wiki/xoxo
http://microformats.org/discuss/mail/microformats-discuss/2005-
September/001020.html
My preference would be to use XOXO as the transport, so that *all*
intermediate data is legal HTML. Would that be possible/desirable
within the JSON metaphor? If not, why not?
Thanks,
-- Ernie P.
P.S. Hi Bob!
On Jan 5, 2006, at 5:47 AM, David Janes -- BlogMatrix wrote:
I came to this group by a slightly strange path -- I wanted a way
of providing webservices that others could load into their own
webpages. "traditional" AJAX, if there is such a beast, cannot do
this because of limitations with cross site scripting.
I mulled this over for a while and discovered at Christmas time
that one can use the SCRIPT element to dynamically load scripts
from anywhere. I had also been looking at a technology called
JSON which has huge replacement to be a widely used net transport
language, as it's much easier to deal with that XML. JSON led me
to Bob Ippolito's JSONP, which lets me combine the SCRIPT with
JSON with a callback.
Finally, looking back through my notes, I revisited AHAH which
provided an easy method for producers and consumers to use HTML
in "AJAX-y" applications.
Combining them all together, I've produced JAHAH (pronounced the
German way).
- it allows cross site scripting
- if the "jsonp" parameter is not passed to the webservice, HTML
documents are returned
- if it is, a simple JSON payload is returned with "html" holding
the HTML document; arbitrary other data can be added to the payload
I've written a deeper description here [1], the official home
(please don't like to the temporary redirect) and I'm providing
code samples, JAHAH webservices for extracting HTML from files or
looking at RSS feeds, and all my sources. If you'd like to
publicly comment or link to it on a blog, please also link to
[2]. My code also builds on Ippolito's MochiKit.
Regards, etc...
David
[1] http://www.blogmatrix.com/tools/jahah/
[2] http://blog.davidjanes.com/mtarchives/2006_01.html#003498
_______________________________________________
microformats-rest mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-rest
_______________________________________________
microformats-rest mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-rest
