Hi,
i get data in JSON format, i want to validate or Parse my JSON data in
ruby.

can it be possible validate JSON data in ruby ?
is there any JSON parser for rubyonrail to parse JSON data.

I am wondering what people who know thieir json code make of this:

http://www.andyscott.id.au/index.cfm/2007/3/31/CFJsonService-01Alpha-Release

AN xml config file with the names of methods?

Is this bloat or not? Could there be some standard methods?

_________________________________________________________________
Advertisement: 10 Students. 1 Winner. You Decide
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fletsshop%2Ecom%2FCompetitions%2F\
LetsNetwork%2Ftabid%2F550%2FDefault%2Easpx&_t=754951090&_r=letsshop&_m=EXT

http://yuiblog.com/blog/2007/04/10/json-and-browser-security/

The JSON.org page is now available in Czech.

http://json.org/json-cz.html

I was having a discussion with an implementer of a JSON library, and
over time the discussion boiled down to an argument over the
interpretation of one sentence in the RFC.  That sentence is the first
one in section "3. Encoding", to wit "JSON text SHALL be encoded in
Unicode."

Hopefully this will draw a response from Douglas Crockford, since it
may be that he is the only one that really knows what he meant by what
he said in the RFC.... but opinions from others are welcome.

The implementer claims that because Unicode is not a binary encoding,
but a set of codepoints, that this sentence means that Unicode
codepoints should be used in some manner to represent characters, but
that the bitstream that represents the JSON text could use escapes for
most of the characters (reducing the size of the character
repertoire), and then be encoded in, say, EBCDIC.  While it is
possible to conceive of doing such a thing, I question if his
interpretation is valid.

My interpretation of that same sentence is that the character codes
should indeed be Unicode codepoints, and in addition, they should be
encoded in one of the 5 UTF-* Unicode encodings listed later in the
same section.  Clearly by using escapes, it is possible to reduce the
character repertoire to ASCII, or even a subset of ASCII, but ASCII is
a subset of Unicode's UTF-8 encoding, so that is valid.

So I'd welcome interpretations on exactly what encodings are legal
JSON texts.

Some following questions are:

1) Must a conformant JSON parser recognize all legal encodings?  Or
can a parser be conformant with documented restrictions on what
encodings it can accept?

2) Is a conformant JSON generator allowed to have options to generate
text that is not quite JSON conformant?  Or must it be completely
limited to producing JSON legal JSON text only?

--- In json@yahoogroups.com, "json_is_clever" <vendor@...> wrote:

> The implementer claims that because Unicode is not a binary encoding,
> but a set of codepoints, that this sentence means that Unicode
> codepoints should be used in some manner to represent characters, but
> that the bitstream that represents the JSON text could use escapes for
> most of the characters (reducing the size of the character
> repertoire), and then be encoded in, say, EBCDIC.  While it is
> possible to conceive of doing such a thing, I question if his
> interpretation is valid.

No, that is a wild misreading of the RFC. The JSON text must be
represented in Unicode, and the preferred encoding is UTF-8.

> 1) Must a conformant JSON parser recognize all legal encodings?  Or
> can a parser be conformant with documented restrictions on what
> encodings it can accept?

Parties can agree on what is acceptable and meaningful. For example,
it is reasonable for a receiver to put limits on message length or
string length or nesting depth.

> 2) Is a conformant JSON generator allowed to have options to generate
> text that is not quite JSON conformant?  Or must it be completely
> limited to producing JSON legal JSON text only?

A JSON generator may only produce valid JSON text.

I have one more question, do I need to convert unicode characters to
something like "\u12345"?

Michael


On 13 Apr 2007 15:47:13 -0700, Douglas Crockford <douglas@...>
wrote:
>
>   --- In json@yahoogroups.com <json%40yahoogroups.com>, "json_is_clever"
> <vendor@...> wrote:
>
> > The implementer claims that because Unicode is not a binary encoding,
> > but a set of codepoints, that this sentence means that Unicode
> > codepoints should be used in some manner to represent characters, but
> > that the bitstream that represents the JSON text could use escapes for
> > most of the characters (reducing the size of the character
> > repertoire), and then be encoded in, say, EBCDIC. While it is
> > possible to conceive of doing such a thing, I question if his
> > interpretation is valid.
>
> No, that is a wild misreading of the RFC. The JSON text must be
> represented in Unicode, and the preferred encoding is UTF-8.
>
> > 1) Must a conformant JSON parser recognize all legal encodings? Or
> > can a parser be conformant with documented restrictions on what
> > encodings it can accept?
>
> Parties can agree on what is acceptable and meaningful. For example,
> it is reasonable for a receiver to put limits on message length or
> string length or nesting depth.
>
> > 2) Is a conformant JSON generator allowed to have options to generate
> > text that is not quite JSON conformant? Or must it be completely
> > limited to producing JSON legal JSON text only?
>
> A JSON generator may only produce valid JSON text.
>
>
>


[Non-text portions of this message have been removed]

Douglas Crockford wrote:
>> 1) Must a conformant JSON parser recognize all legal encodings?  Or
>> can a parser be conformant with documented restrictions on what
>> encodings it can accept?
>
> Parties can agree on what is acceptable and meaningful. For example,
> it is reasonable for a receiver to put limits on message length or
> string length or nesting depth.

For example, JSON in E-0.9 accepts only Unicode characters from the "basic
multilingual plane", i.e., characters whose code point fits in 16 bits. As I
read the JSON spec, this is an allowable restriction. This restriction is
needed since E-0.9 does not support Unicode supplementary characters, i.e.,
characters whose code points are >= 2**16.

--
Text by me above is hereby placed in the public domain

      Cheers,
      --MarkM

--- In json@yahoogroups.com, "Douglas Crockford" <douglas@...> wrote:

> No, that is a wild misreading of the RFC. The JSON text must be
> represented in Unicode, and the preferred encoding is UTF-8.

Thanks for the clarification, Douglas.

--- In json@yahoogroups.com, "Michael Schwarz" <michael.schwarz@...>
wrote:
>
> I have one more question, do I need to convert unicode characters to
> something like "\u12345"?

No. The \u notation is only required for some of the control characters.

Hi,

currently I have only something like \r, \n or \t, are those chars
allowed? Which control chars are you talking about? Thanks a lot.

Michael



On 14 Apr 2007 06:45:58 -0700, Douglas Crockford <douglas@...> wrote:
> --- In json@yahoogroups.com, "Michael Schwarz" <michael.schwarz@...>
> wrote:
> >
> > I have one more question, do I need to convert unicode characters to
> > something like "\u12345"?
>
> No. The \u notation is only required for some of the control characters.
>
>


--
Best regards | Schöne Grüße
Michael

Microsoft MVP - Most Valuable Professional
Microsoft MCAD - Certified Application Developer

http://weblogs.asp.net/mschwarz/
http://www.ajaxpro.info/

WPF/E: http://groups.google.com/group/wpf-everywhere

Skype: callto:schwarz-interactive
MSN IM: passport@...

--- In json@yahoogroups.com, "Michael Schwarz" <michael.schwarz@...>
wrote:

> currently I have only something like \r, \n or \t, are those chars
> allowed? Which control chars are you talking about? Thanks a lot.

None of the control characters can appear in JSON strings. You can use
the \u convention to represent them. A few of them, such as linefeed
and tab, have more compact representations such as \n and \t. Take
your pick.

The JSON.org page is now available in Arabic.

http://json.org/json-ar.html

I've recently released a JSON converter for Perl on CPAN called
JSON::DWIW.  Most of the work is done in C for speed.  I have found it
to be faster than JSON.pm or JSON::Syck.  It currently assumes
everything is in utf-8.  I would appreciate any feedback you might have.

DWIW stands for "Do What I Want", meaning Perl objects get output as
their underlying data structures by default (except for Math::BigInt
and Math::BigFloat objects, which are output as numbers).  When
converting to JSON, the module should only return an error if a string
in the input data structure contains a bad utf-8 sequence.  When
converting from JSON, numbers that are too long for your platform get
converted to Math::BigInt or Math::BigFloat objects, if you have those
modules installed.  Otherwise, the longer numbers get converted to
strings to help prevent data loss.

You can get the module from

     http://cpan.org/authors/id/D/DO/DOWENS/JSON-DWIW-0.07.tar.gz

or

     http://perl.regexguy.com/dist/JSON-DWIW-0.07.tar.gz

or you can install it by using CPAN.pm, e.g.,

     perl -MCPAN -e 'install JSON::DWIW'

Hi All,

I have written a library to store JSON values in Cookies. It is based
on prototype.js.
http://www.lalit.org/lab/jsoncookies

Aron Newton has also ported it to the Mootools framework:
http://dev.mootools.net/browser/trunk/Remote/Cookie.Json.js

Regards,
Lalit Patel

The JSON.org page is now available in Persian.

http://json.org/json-fa.html

hi all

i want to parse the book.json and i want to make sure that the Books
class have Book , and every Book class have value.

i try using Java, and use the JSON Java

but stil cannot get the value

right now i still cannot get the values of the books, which i know have
3 book there.


this is my syntax, still error


       JSONArray jsonObject = JSONArray.fromString(responseBody);
       jsonObject.fromString("books");
       System.out.println(jsonObject.get(0));

   ----------

[{"books":[{"book":
		 {
		 "title":"JavaScript, the Definitive Guide",
		 "publisher":"O'Reilly",
		 "author":"David Flanagan",
		 "cover":"/images/cover_defguide.jpg",
		 "blurb":"Lorem ipsum dolor sit amet, consectetuer adipiscing elit."
		 }
	 },
	 {"book":
		 {
		 "title":"DOM Scripting",
		 "publisher":"Friends of Ed",
		 "author":"Jeremy Keith",
		 "cover":"/images/cover_domscripting.jpg",
		 "blurb":"Praesent et diam a ligula facilisis venenatis."
		 }
	 },
	 {"book":
		 {
		 "title":"DHTML Utopia: Modern Web Design using JavaScript & DOM",
		 "publisher":"Sitepoint",
		 "author":"Stuart Langridge",
		 "cover":"/images/cover_utopia.jpg",
		 "blurb":"Lorem ipsum dolor sit amet, consectetuer adipiscing elit."
		 }
	 }
]}]

[Non-text portions of this message have been removed]

JSONER provides open-source solution for improving your web
technologies that allow developers to easily and quickly build rich
JSON based applications.

JSONER are based on event - event handler paradigm (like SAX).
An event-based API reports parsing events directly to the application
through callbacks. An event-based API provides a simpler, lower-level
access to JSON data structure.

JSONER include the subset of useful methods, which are the following:
  - Methods for data lookup.
  - Methods for data binding.
  - Methods of populating data from HTML form to JSON and the contrary.
  - Methods for comparison JSONs.
  - Methods for transformation JSON to XML or HTML string for further
processing.
  - Methods for creating HTML forms and other components.
  - Methods for transformation array of JSONs to a MAP.
  - Methods to capturing JSON property and the contrary.

New functionality in JSONER v1.22:
  - Cross-link event added.
  - Cross-link resolver.
  - isMute - the method which defined that the property should be
excluded from traversing (thanks to DC). It allows to represent
JavaScript objects like as JSON.

To get more information, samples and documentations, please visit
JSONER web site http://www.soft-amis.com/jsoner/index.html.
And, of course, there are live working samples of JSONER in action!

JSONER' SourceForge page available too:
http://sourceforge.net/projects/jsontools

Any feedback is appreciated.

Hello All,

I am a rookie in Web Technologies and had to do a small work with
Prototype's json and Ajax.request functions.

I had problems with the json.js available in here -
http://www.json.org/json.js (Ajax.request fails). So had to use the
Prototype's json implementation.

I found out that prototype.js uses eval on the input String given. As
we all know that this is not secure is there any workaround for this
within the protoype and json libraries?

Thanks,
Pradeep

Sometime Today, Pradeep assembled some asciibets to say:

> I had problems with the json.js available in here -
> http://www.json.org/json.js (Ajax.request fails). So had to use the
> Prototype's json implementation.

It would help if you could say what problems you had with json.js

--- In json@yahoogroups.com, "Pradeep" <prad_kris@...> wrote:
> I am a rookie in Web Technologies and had to do a small work with
> Prototype's json and Ajax.request functions.
>
> I had problems with the json.js available in here -
> http://www.json.org/json.js (Ajax.request fails). So had to use the
> Prototype's json implementation.
>
> I found out that prototype.js uses eval on the input String given. As
> we all know that this is not secure is there any workaround for this
> within the protoype and json libraries?

Since you are a rookie, I'm guessing that your problem is that you are
not writing your for..in loops correctly. See
http://yuiblog.com/blog/2006/09/26/for-in-intrigue/

Hello Crawford,

I am not using any for..in loops. I went on to find the exact problem using
Script Debugger. It was reported in the Rails Bug Tracker. Please find the link
below:
http://dev.rubyonrails.org/ticket/6579

Also the information in Prototype's site acknowledges this.
(http://prototypejs.org/learn/json)

My primary need is to work with Ajax.Request and when I use the original json.js
of yours, the request doesnt get completed.

So, I decided to use Prototype's json which uses only the eval and is not
supporting parseJSON  as in your library. I was wondering there are any
workarounds for this situation without using the patches given in the Rails
tracker.

Hope its clear. Please revert for any clarification.

Thanks,
Pradeep
Douglas Crockford <douglas@...> wrote:
--- In json@yahoogroups.com, "Pradeep" <prad_kris@...> wrote:
  > I am a rookie in Web Technologies and had to do a small work with
  > Prototype's json and Ajax.request functions.
  >
  > I had problems with the json.js available in here -
  > http://www.json.org/json.js (Ajax.request fails). So had to use the
  > Prototype's json implementation.
  >
  > I found out that prototype.js uses eval on the input String given. As
  > we all know that this is not secure is there any workaround for this
  > within the protoype and json libraries?

  Since you are a rookie, I'm guessing that your problem is that you are
  not writing your for..in loops correctly. See
  http://yuiblog.com/blog/2006/09/26/for-in-intrigue/






---------------------------------
Ahhh...imagining that irresistible "new car" smell?
  Check outnew cars at Yahoo! Autos.

[Non-text portions of this message have been removed]

--- In json@yahoogroups.com, Pradeep <prad_kris@...> wrote:
> I am not using any for..in loops. I went on to find the exact
problem using Script Debugger. It was reported in the Rails Bug
Tracker. Please find the link below:
> http://dev.rubyonrails.org/ticket/6579

Interesting. Prototype contains a known bug which is trivial to fix,
and they are refusing to apply the fix. That strikes me as completely
irresponsible.

There are lots of Ajax libraries out there. I recommend that you pick
a better one.

The JSON.org page is now available in Polish.

http://json.org/json-pl.html

Sorry I didn't reply sooner. Hopefully you have already solved the
problem. If not...

I think you would want code more like this (untested!):

JSONArray outerBooksArray = JSONArray.fromString(responseBody);
JSONObject booksObject = outerBooksArray.get(0);
JSONArray innerBooksArray = booksObject.getObject("books");

JSONObject book = innerBooksArray.get(0);
JSONObject bookDetails = book.getObject("book");
System.out.println("title: " + bookDetails.getString("title"));


The code would be much simpler if your data had fewer layers. Perhaps
as simple as an array containing bookdetails jsonobjects.

Kevin


--- In json@yahoogroups.com, "Frans Thamura @ flatburger"
<flatburger@...> wrote:
>
> hi all
>
> i want to parse the book.json and i want to make sure that the Books
> class have Book , and every Book class have value.
>
> i try using Java, and use the JSON Java
>
> but stil cannot get the value
>
> right now i still cannot get the values of the books, which i know have
> 3 book there.
>
>
> this is my syntax, still error
>
>
>       JSONArray jsonObject = JSONArray.fromString(responseBody);
>       jsonObject.fromString("books");
>       System.out.println(jsonObject.get(0));
>
>   ----------
>
> [{"books":[{"book":
> 	 {
> 	 "title":"JavaScript, the Definitive Guide",
> 	 "publisher":"O'Reilly",
> 	 "author":"David Flanagan",
> 	 "cover":"/images/cover_defguide.jpg",
> 	 "blurb":"Lorem ipsum dolor sit amet, consectetuer adipiscing elit."
> 	 }
>  },
>  {"book":
> 	 {
> 	 "title":"DOM Scripting",
> 	 "publisher":"Friends of Ed",
> 	 "author":"Jeremy Keith",
> 	 "cover":"/images/cover_domscripting.jpg",
> 	 "blurb":"Praesent et diam a ligula facilisis venenatis."
> 	 }
>  },
>  {"book":
> 	 {
> 	 "title":"DHTML Utopia: Modern Web Design using JavaScript & DOM",
> 	 "publisher":"Sitepoint",
> 	 "author":"Stuart Langridge",
> 	 "cover":"/images/cover_utopia.jpg",
> 	 "blurb":"Lorem ipsum dolor sit amet, consectetuer adipiscing elit."
> 	 }
>  }
> ]}]
>
> [Non-text portions of this message have been removed]
>

The JSON.org page is now available in Indonesian.

http://json.org/json-id.html

Hi all -

First message to the group, thanks for the invitation Doug.  I recently put
together a C# library that's available at
http://code.google.com/p/jsonsharp/ and wanted to pass along some general
information about it.

Jsonsharp is an abstracted library that can be used directly or extended for
your own use.  Because of the simplicity of JSON and the Jsonsharp object
model, the same source files can be compiled for use under the Windows .Net
2.0 Framework as well as under the Mono 2.0 Framework.  Example applications
for both platforms are available (Visual Studio 2005 solution & project, and
Monodevelop solution & project).  The library was born out of a need for
writing data from a server-side application in JSON-compliant format.  I
found other libraries either overkill for what I needed to do or just
different from the way I like to work.  I'm guessing others will be in the
same boat, so I've made my library publicly available (GPL 2.0 license).

Comments are always welcome; patches always get bigger smileys.  :-)

Anyway, looking forward to participation in this forum.

cheers,
jeff rodenburg


[Non-text portions of this message have been removed]

Just a reminder about my Java-based JSON parser in the Files section
(json-lib-1_0_1.zip).
It uses the Java types to represent JSON types so there's no custom objects to
remember.
It also means there are fewer source files and methods to understand.

It also allows comments.  (Is this acceptable?)

A usage example:

     Reader myReader;
     ...initialize 'myReader'...

     JSONParser json = new JSONParser();
     Object jsonObj = json.parse(myReader);

The type mappings:

string: java.lang.String
number: java.lang.Number
object: java.util.Hashtable
array: java.util.Vector
true: java.lang.Boolean
false: java.lang.Boolean
null: null

Thanks,
         -Shawn

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the json
group.

   File        : /json-lib-1_0_1.zip
   Uploaded by : shawnsilverman <shawn@...>
   Description : A Java library for processing JSON data.

You can access this file at the URL:
http://groups.yahoo.com/group/json/files/json-lib-1_0_1.zip

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/help/us/groups/files

Regards,

shawnsilverman <shawn@...>

I'm proud to announce that MJSON v0.3 has been released!

MJSON is Maciel's JSON parser, a small light-weight library that
handles documents written in the JSON markup language. It's written in
ISO C, which means that it may run wherever there is a C compiler.

It's still in alpha stage but at the moment it is capable of parsing
every JSON example present in www.json.org.

MJSON can be found at:
http://sourceforge.net/projects/mjson


Rui Maciel