deadpixi.software wrote:
>
>
> Hello everyone,
> Just wanted to post a message about an open source project of mine:
> Esel. Esel is a powerful query and expression language designed to
> work with JSON data (or any data exported to it from the hosting
> JavaScript application).
>
> Please check out http://www.deadpixi.com/esel
> <http://www.deadpixi.com/esel> for more information.
>
> Thanks,
> Rob
>
>
can i use  it with java?


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

I had a quick look into code and documentation.
It is a nice experiment from parser point of view but for loop a part, it
seems that at the end of the day, all code purpose is to do something like
this:

function Esel(JSON, expression){
     with(typeof JSON === "string" ? eval("(" + JSON + ")") : JSON)
         with(Math)
             return expression.replace(/\${([^\}]*)}/g, function(match,
code){
                 return eval("(" + code + ")");
             });
};

Example

var result = Esel(
// pass JSON string or an object
{
   "Image": {
     "Width": 800,
     "Height": 600,
     "Title": "View from 15th Floor",
     "Thumbnail": {
       "Url": "http://www.example.com/image/481989943",
       "Height": 125,
       "Width": "100"
     },
     "IDs": [116, 943, 234, 38793]
   }
},
'The square root of ${Image.Width} is ${sqrt(Image.Width)}.\n'+
'The length of "${Image.Thumbnail.Url}" is
${Image.Thumbnail.Url.length}.\n'+
'The value of "\\u0041" is "${\'\u0041\'}".\n'+
'The length of the "Image.IDs" array is ${Image.IDs.length}.'
);

alert(result);

Am I missing something about this Esel concept?

Good work in any case, I do like the grammar parser.

On Thu, Aug 20, 2009 at 6:00 AM, deadpixi.software <
deadpixi.software@...> wrote:

>
>
> Hello everyone,
> Just wanted to post a message about an open source project of mine: Esel.
> Esel is a powerful query and expression language designed to work with JSON
> data (or any data exported to it from the hosting JavaScript application).
>
> Please check out http://www.deadpixi.com/esel for more information.
>
> Thanks,
> Rob
>
>
>


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

Howdy,
    Esel doesn't depend on anything other than Kouprey (included with the Esel
distribution, or downloadable separately at http://www.deadpixi.com/kouprey).

    It should be possible to use Esel with Java using the JavaScript interpreter
included with Java 6, or by using Rhino on earlier versions of Java. This hasn't
been tested, but I can't think of any reason why it wouldn't work.

    If you do end up using Esel embedded in a Java application, please let me
know - I'd be very interested to hear your experiences.

    Thanks,
    Rob

--- In json@yahoogroups.com, janwen <loujianwen1986@...> wrote:
>
> deadpixi.software wrote:
> >
> >
> > Hello everyone,
> > Just wanted to post a message about an open source project of mine:
> > Esel. Esel is a powerful query and expression language designed to
> > work with JSON data (or any data exported to it from the hosting
> > JavaScript application).
> >
> > Please check out http://www.deadpixi.com/esel
> > <http://www.deadpixi.com/esel> for more information.
> >
> > Thanks,
> > Rob
> >
> >
> can i use  it with java?
>
>
> [Non-text portions of this message have been removed]
>

(My apologies if this gets multi-posted; Yahoo was having issues.)

Hello Andrea,
    Thanks for the feedback! I'm definitely interested in any observations anyone
may have. Thanks for taking the time to post this message.

     Part of the point of Esel was to avoid any use of eval() on the expression,
to help enforce safety. Not "safety" from a malicious attacker standpoint, but
so that someone entering an expression in, say, a web-based spreadsheet didn't
say something like "i = 4" and pollute the global namespace or otherwise break
something.

     This is also reflected in the ability to export a limited namespace and a
limited set of functions to the Esel environment.

     Esel was also designed to be used with another project of mine, Jenner
(http://www.deadpixi.com/jenner). Doing Jenner with evaluated JavaScript would
have been somewhat difficult and far more conceptually dirty. Jenner requires
better namespacing than native JavaScript can easily support, and also really
needs far less verbosity than would be necessary if I went the eval()'d
JavaScript route.

     The other goal was to have a language for JavaScript that filled roughly the
same role as the UEL for Java.

     Hopefully this makes sense. It's Saturday and I'm not operating on a lot of
sleep. :)

     Thanks again for your feedback. Please let me know if  you have any other
questions.

     Rob

--- In json@yahoogroups.com, Andrea Giammarchi <andrea.giammarchi@...> wrote:
>
> I had a quick look into code and documentation.
> It is a nice experiment from parser point of view but for loop a part, it
> seems that at the end of the day, all code purpose is to do something like
> this:
>
> function Esel(JSON, expression){
>     with(typeof JSON === "string" ? eval("(" + JSON + ")") : JSON)
>         with(Math)
>             return expression.replace(/\${([^\}]*)}/g, function(match,
> code){
>                 return eval("(" + code + ")");
>             });
> };
>
> Example
>
> var result = Esel(
> // pass JSON string or an object
> {
>   "Image": {
>     "Width": 800,
>     "Height": 600,
>     "Title": "View from 15th Floor",
>     "Thumbnail": {
>       "Url": "http://www.example.com/image/481989943",
>       "Height": 125,
>       "Width": "100"
>     },
>     "IDs": [116, 943, 234, 38793]
>   }
> },
> 'The square root of ${Image.Width} is ${sqrt(Image.Width)}.\n'+
> 'The length of "${Image.Thumbnail.Url}" is
> ${Image.Thumbnail.Url.length}.\n'+
> 'The value of "\\u0041" is "${\'\u0041\'}".\n'+
> 'The length of the "Image.IDs" array is ${Image.IDs.length}.'
> );
>
> alert(result);
>
> Am I missing something about this Esel concept?
>
> Good work in any case, I do like the grammar parser.
>
> On Thu, Aug 20, 2009 at 6:00 AM, deadpixi.software <
> deadpixi.software@...> wrote:
>
> >
> >
> > Hello everyone,
> > Just wanted to post a message about an open source project of mine: Esel.
> > Esel is a powerful query and expression language designed to work with JSON
> > data (or any data exported to it from the hosting JavaScript application).
> >
> > Please check out http://www.deadpixi.com/esel for more information.
> >
> > Thanks,
> > Rob
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>

(violating my own convention and replying to myself)

The other advantage of Esel over eval()'d JavaScript is Esel's text templating
abilities. For example, you can say things like this:

Hello, ${name}!

Jenner (mentioned below) extends these text templating capabilities to entire
web pages.

(okay, I'm done. No more replying to myself.)

--- In json@yahoogroups.com, "deadpixi.software" <deadpixi.software@...> wrote:
>
> (My apologies if this gets multi-posted; Yahoo was having issues.)
>
> Hello Andrea,
>    Thanks for the feedback! I'm definitely interested in any observations
anyone may have. Thanks for taking the time to post this message.
>
>     Part of the point of Esel was to avoid any use of eval() on the
expression, to help enforce safety. Not "safety" from a malicious attacker
standpoint, but so that someone entering an expression in, say, a web-based
spreadsheet didn't say something like "i = 4" and pollute the global namespace
or otherwise break something.
>
>     This is also reflected in the ability to export a limited namespace and a
limited set of functions to the Esel environment.
>
>     Esel was also designed to be used with another project of mine, Jenner
(http://www.deadpixi.com/jenner). Doing Jenner with evaluated JavaScript would
have been somewhat difficult and far more conceptually dirty. Jenner requires
better namespacing than native JavaScript can easily support, and also really
needs far less verbosity than would be necessary if I went the eval()'d
JavaScript route.
>
>     The other goal was to have a language for JavaScript that filled roughly
the same role as the UEL for Java.
>
>     Hopefully this makes sense. It's Saturday and I'm not operating on a lot
of sleep. :)
>
>     Thanks again for your feedback. Please let me know if  you have any other
questions.
>
>     Rob
>
> --- In json@yahoogroups.com, Andrea Giammarchi <andrea.giammarchi@> wrote:
> >
> > I had a quick look into code and documentation.
> > It is a nice experiment from parser point of view but for loop a part, it
> > seems that at the end of the day, all code purpose is to do something like
> > this:
> >
> > function Esel(JSON, expression){
> >     with(typeof JSON === "string" ? eval("(" + JSON + ")") : JSON)
> >         with(Math)
> >             return expression.replace(/\${([^\}]*)}/g, function(match,
> > code){
> >                 return eval("(" + code + ")");
> >             });
> > };
> >
> > Example
> >
> > var result = Esel(
> > // pass JSON string or an object
> > {
> >   "Image": {
> >     "Width": 800,
> >     "Height": 600,
> >     "Title": "View from 15th Floor",
> >     "Thumbnail": {
> >       "Url": "http://www.example.com/image/481989943",
> >       "Height": 125,
> >       "Width": "100"
> >     },
> >     "IDs": [116, 943, 234, 38793]
> >   }
> > },
> > 'The square root of ${Image.Width} is ${sqrt(Image.Width)}.\n'+
> > 'The length of "${Image.Thumbnail.Url}" is
> > ${Image.Thumbnail.Url.length}.\n'+
> > 'The value of "\\u0041" is "${\'\u0041\'}".\n'+
> > 'The length of the "Image.IDs" array is ${Image.IDs.length}.'
> > );
> >
> > alert(result);
> >
> > Am I missing something about this Esel concept?
> >
> > Good work in any case, I do like the grammar parser.
> >
> > On Thu, Aug 20, 2009 at 6:00 AM, deadpixi.software <
> > deadpixi.software@> wrote:
> >
> > >
> > >
> > > Hello everyone,
> > > Just wanted to post a message about an open source project of mine: Esel.
> > > Esel is a powerful query and expression language designed to work with
JSON
> > > data (or any data exported to it from the hosting JavaScript application).
> > >
> > > Please check out http://www.deadpixi.com/esel for more information.
> > >
> > > Thanks,
> > > Rob
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

Hi,

I'm terribly sorry if this post is inappropriate; I got an invitation from
Douglas, and I'm hoping I'm not misinterpreting his intention!

For fun I recently put together a +VERY+ lightweight JSON parser as one file of
ANSI C, with no external dependencies.

Take a look here:
https://sourceforge.net/projects/cjson/
http://cjson.svn.sourceforge.net/viewvc/cjson/

I'm certainly not going to pretend it's the most robust parser in the world (it
attempts to fail gracefully, rather than inform you of validation failure), and
it's not perfect either (no support for UTF-16 surrogates).

HOWEVER, it does have some functionality and attributes which I hope you might
find appealing:
- It's dumb, easy, quick and simple.
- It's MIT license, so you're free to do as you please with it.
- Data structure parser uses model JSON spec 1:1.
- Syntax is EXTREMELY lean for building and extracting JSON structures. One call
per value.
- Parser structured to make writing a SAX-style interface trivial.
- It's one file of ANSI C, and it compiles to a few k.
- It shares the spirit of the "fat free" idea behind JSON.
- It has NO secondary agenda. It's a JSON library. Nothing else.

I sent Douglas an email to the effect of: "is this worthy of addition to the
json.org page?". With luck, this email can be to the effect of:

Hello JSON community!
Is this useful?
Should I add/remove anything?
Does anyone have any (tiny) code that will allow me to parse the UTF16 \u tokens
with surrogates without big changes?
Is the cJSON parser sufficiently featured to be useful?
Should I be paying more attention to validation?
What do you think? :D

Many thanks in advance,

Dave.

This is the first release of Jansson, available at
http://www.digip.org/jansson/. In spite of being the first release, it's
already a full-featured JSON encoder, decoder and data model. See below
for an overview of features.

I'm eager to get comments, patches, bug reports, or any feedback!

Download source: http://www.digip.org/jansson/releases/jansson-1.0.tar.bz2
View documentation: http://www.digip.org/jansson/doc/1.0/
Browse source: http://github.com/akheron/jansson/


What is Jansson?
----------------

Jansson is a C library for encoding, decoding and manipulating JSON data.
It features:

     * Simple and intuitive API and data model
     * Comprehensive documentation
     * No dependencies on other libraries
     * Full Unicode support (UTF-8)
     * Extensive test suite

Jansson is licensed under the MIT license.

Hi Folks,

    Recently I published "Simple Remoting" (
http://sites.google.com/site/simpleremoting/home ) java open source project on
sourceforge.net . The purpose of this project is creating an alternative SOA
implementation which is lightweight, easy to use and flexible. I believe that
this project is not a challenge to webservices, but it might be more suitable in
some cases like RIA platforms, testing and projects where you have to work
against tight schedules.

    If you have time to examine It and share your ideas with me, I would be
appreciated.

Many Thanks In Advance.

Serhat Dirik

Features At A Glance
• It's lightweight and requires no additional knowledge.
• Installation is quite easy as adding one listener to your web application
configuration
• Build-in support for POJO, EJB2.1, EJB3 and Spring . Framework is expandable
so developers can implement additional locators as they need.
• No programming and modification required to expose components as services.
Simple xml declarations are enough.
• Java & Java Script client implementations are out of the box. Client
implementations are easily adaptable to .net and other popular languages
• It can work in any application server which works on JVM 1.5+
• It uses a JSON message format instead of SOAP which is more human &  software
friendly. Browsers can evaluate service responses at run time as java script
objects.
• Additional header fields can be embedded in service requests and responses.
Thus developers can post additional fields to services to apply their policies
to service calls.Message headers are accessible by interceptors and services.
Message headers are accessible by both interceptors and services.
• Service instances can be created in request, session and application contexts.
• All exposed services can be accessed through a single – multi threaded end
point implementation. Currently only a http(s) request/response end point is
implemented. But the framework is quite flexible and expandable.  Implementation
of a single simple class is enough to have additional end points. JMS and Http
Callback  implementations are planned for the further versions.
•  Transformation of all java types including complex beans are supported.
Serialization is not required, all object are supported. Custom transformers can
be easily added to the framework
• It comes with build-in security which is integrated with J2EE security. It
supports authentication, authorization & transport layer security enforcement. 
It's very easy to define different role access to a single service's operations.
• It supports idempotency of session services. Duplicate calls are prevented
• Service calls can be filtered through custom interceptors. Each step of a
service call can be controlled through interceptors.
• It has a build in Registry Query service. Service list, operation signatures
can be discovered through this service.
• It's quite flexible and expandable.It's easy to implement your own end-points,
locators or even transformers

On Fri, Aug 28, 2009 at 8:48 AM, serhat.dirik<serhat.dirik@...> wrote:
>  Hi Folks,
>
>   Recently I published "Simple Remoting" (
http://sites.google.com/site/simpleremoting/home ) java open source project on
sourceforge.net . The purpose of this project is creating an alternative SOA
implementation which is lightweight, easy to use and flexible. I believe that
this project is not a challenge to webservices, but it might be more suitable in
some cases like RIA platforms, testing and projects where you have to work
against tight schedules.
>
>   If you have time to examine It and share your ideas with me, I would be
appreciated.

How does this compare with DWR?

--
Martin Cooper


> Many Thanks In Advance.
>
> Serhat Dirik
>
> Features At A Glance
> •       It's lightweight and requires no additional knowledge.
> •       Installation is quite easy as adding one listener to your web
application configuration
> •       Build-in support for POJO, EJB2.1, EJB3 and Spring . Framework is
expandable so developers can implement additional locators as they need.
> •       No programming and modification required to expose components as
services. Simple xml declarations are enough.
> •       Java & Java Script client implementations are out of the box. Client
implementations are easily adaptable to .net and other popular languages
> •       It can work in any application server which works on JVM 1.5+
> •       It uses a JSON message format instead of SOAP which is more human &
 software friendly. Browsers can evaluate service responses at run time as java
script objects.
> •       Additional header fields can be embedded in service requests and
responses. Thus developers can post additional fields to services to apply their
policies to service calls.Message headers are accessible by interceptors and
services. Message headers are accessible by both interceptors and services.
> •       Service instances can be created in request, session and application
contexts.
> •       All exposed services can be accessed through a single – multi threaded
end point implementation. Currently only a http(s) request/response end point is
implemented. But the framework is quite flexible and expandable.  Implementation
of a single simple class is enough to have additional end points. JMS and Http
Callback  implementations are planned for the further versions.
> •        Transformation of all java types including complex beans are
supported. Serialization is not required, all object are supported. Custom
transformers can be easily added to the framework
> •       It comes with build-in security which is integrated with J2EE
security. It supports authentication, authorization & transport layer security
enforcement.  It's very easy to define different role access to a single
service's operations.
> •       It supports idempotency of session services. Duplicate calls are
prevented
> •       Service calls can be filtered through custom interceptors. Each step
of a service call can be controlled through interceptors.
> •       It has a build in Registry Query service. Service list, operation
signatures can be discovered through this service.
> •       It's quite flexible and expandable.It's easy to implement your own
end-points, locators or even transformers
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

>
> How does this compare with DWR?

   Hi Martin,

    I don't know DWR in depth but I can say that the main difference is  DWR is
focused on AJAX, but SR mainly focuses on services and SOA. SR is not only
targeting browsers, but java and other rich clients as well. Their intentions
are different.

     SR focuses on :

   * Converting server side object to services
   * Service registry & service registry query
   * Managing server side objects life cycle
   * Services security
   * Message filtering mechanisms
   * End-point implementations (currently only http is available, jms is planned
as target)
   * Messaging format (like SOAP)

Thanks.

Hi,

In a similar vein to several of the recent posts, I'd like to invite the
group to take a look at another new open source JSON parser and
generator.

Argo <http://argo.sourceforge.net>  is written in Java, and was inspired
by some of the frustrations I've experienced applying some of the other
JSON parsers to the requirements I have at work.  It provides three
parsing interfaces:

     * Document based (like DOM)
     * Pull (like StAX)
     * Push (like SAX)
The document model is also used for generating JSON.

The main frustrations I mentioned above that are addressed are:

     * Simplicitiy of API - I've tried to make the API as simple and
robust as possible for handling JSON from a source of unknown quality.
The intention is that it should be easy to check for, and pull out
arbitrary elements of a JSON document.
     * Precision of numbers - the precision of numbers in a JSON document
is preserved entirely; it's up to the user of the API to choose how to
represent those numbers if they want to perform operations on them.
This is absolutely critical for financial applicaitons, among others.
     * Type safety - as much as is possible, the compiler should be able
to tell you about mistakes with the API.  There should be no need for
any casting at all.
     * Completeness - I wanted to be able to use a single library for all
my JSON needs.  Prior to this, we seemed to have collected dependencies
on half the libraries on JSON org.

I'd be very interested to hear opinions, suggestions, criticism, etc.,
either here, or on the forums listed on the support page at
http://argo.sourceforge.net.

Thanks,

Mark



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

Hello

I've just joined this group and want to let you know about itemscript.

Itemscript describes applications, components, events and data in an open,
standard language, built on JSON, that's independent of the details of any
particular implementation. Any component can be swapped out for an independent
reimplementation. All the protocols and APIs are documented; we aim for zero
lock-in.

Itemscript Schema

Itemscript Schema is a draft specification for a simple schema language for
JSON. The goal is to be useful for any kind of JSON application as well as for
Itemscript applications.

Itemscript JAM (JSON Application Markup)

JSON Application Markup allows for rapid, declarative provisioning of web
applications.

Here's some background on what we have in mind:
  a reviewers guide http://itemscript.org/press/
  an faq  http://code.google.com/p/itemscript/wiki/itemscriptfaq

You can learn more about itemscript at http://itemscript.org and you can
download source from there.  The current build is alpha code that shows how the
declarative provisioning works.

We're building a model client (the Item Lens) that's a GWT implementation and a
server (the Item Store) built on Apache Derby.

Our implementation is in Java.  We're looking to work with interested developers
to port our work to other languages.  We're publishing this under the new BSD
license.

We like JSON.

Bill Braasch
bill@...

Jansson 1.0.1 out! This is a bugfix release. Changes:

* Fixed broken json_is_boolean()

Download source: http://www.digip.org/jansson/releases/jansson-1.0.1.tar.bz2
View documentation: http://www.digip.org/jansson/doc/1.0/
Changelog: http://www.digip.org/jansson/releases/CHANGES


What is Jansson?

Jansson is a C library for encoding, decoding and manipulating JSON data.
It features:

* Simple and intuitive API and data model
* Comprehensive documentation
* No dependencies on other libraries
* Full Unicode support (UTF-8)
* Extensive test suite

Jansson is licensed under the MIT license. For more details, see
http://www.digip.org/jansson/.


Petri Lehtinen
petri@...

Just wanted to say that the json.com website is down. We will try to get it back
up ASAP.
Please note: We consider this a CRIMINAL ACT by the hosting company since it was
done intentionally without notice and no chance to backup any files. If anyone
knows a good lawyer in CA, I would appreciate a referral.

--- In json@yahoogroups.com, "ricjohnsoniii" <RicJohnsonIII@...> wrote:
>
> Just wanted to say that the json.com website is down. We will try to get it
back up ASAP.
> Please note: We consider this a CRIMINAL ACT by the hosting company since it
was done intentionally without notice and no chance to backup any files. If
anyone knows a good lawyer in CA, I would appreciate a referral.

For what it's worth, json.org is hosted at 1&1.
I've been happy with them.

http://www.1and1.com/?k_id=10219574

Jansson 1.0.2 out! This is a bugfix release in the 1.0 release series.

Changes:

* Handle EOF correctly in decoder

Download source: http://www.digip.org/jansson/releases/jansson-1.0.2.tar.bz2
View documentation: http://www.digip.org/jansson/doc/1.0/
Changelog: http://www.digip.org/jansson/releases/CHANGES


What is Jansson?

Jansson is a C library for encoding, decoding and manipulating JSON data.
It features:

* Simple and intuitive API and data model
* Comprehensive documentation
* No dependencies on other libraries
* Full Unicode support (UTF-8)
* Extensive test suite

Jansson is licensed under the MIT license. For more details, see
http://www.digip.org/jansson/.


Petri Lehtinen
petri@...

Ok that just sucks... But as far as "backing up content" have you tried to
search out the json.com pages on google and then retrieve the cache'd pages
from there (e.g. www.json.com home page ->
http://74.125.93.132/search?q=cache:HcdW6MR3bI0J:json.com/+www.json.com&cd=1&hl=\
en&ct=clnk&gl=us
  ).
You might at least be able to get back SOME of your content.

Hope this helps.

On Mon, Sep 7, 2009 at 9:16 PM, ricjohnsoniii <RicJohnsonIII@...>wrote:

>
>
> Just wanted to say that the json.com website is down. We will try to get
> it back up ASAP.
> Please note: We consider this a CRIMINAL ACT by the hosting company since
> it was done intentionally without notice and no chance to backup any files.
> If anyone knows a good lawyer in CA, I would appreciate a referral.
>
>
>


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

Hi,
I've developed a VB.NET (Framework 2.0) version of JSON parser that convert
objects to JSON's strings and viceversa.
Yuo can view the code and download the library on my site at

http://www.pozzware.com/pozzware/Corsi/Programmazione/VB.NET/JSON%20Library.aspx

I hope this library can help all VB.NET developer that will use JSON in their
applications.

see you...

Stefano P.

Hi everyone,
    Thought y'all might be interested in another project of mine: Jenner. Jenner
is a completely in-browser template engine, using JSON as the model and Esel as
the template expression language.

     Unlike other in-browser template engines, Jenner templates are just web
pages with Esel expressions embedded anywhere. Unlike other in-browser template
engines, there is no overloading of "class" attributes or a fallback on XSLT or
anything like that. The templates are written in a very natural way.

      Not to hold you in suspense, here's a sample template:

<ul>
${for i from 0 to people.length return
     <li>${people[i].name}</li>
}
</ul>

      Putting that in a web page will render in-browser, with no modifications or
scripting languages or anything on the server-side.

      Please feel free to take a look at http://www.deadpixi.com/jenner. There
are live demos available as well - be sure to view the source of the pages, so
you can see the templates.

      Please feel free to contact me directly (contact info is available at
http://www.deadpixi.com) if you have any questions. Please especially contact me
if you find Jenner useful.

      Thanks,
      Rob

The following links appear to have died:

<a href="http://blog.beef.de/2008/01/04/tinyjson/">TinyJSON</a>.

<a
href="http://www.tom.sfc.keio.ac.jp/%7Esakai/d/data/200604/JSON.hs">JSON.hs</a>.

<a href="http://vraptor.org/ajax.html">VRaptor</a>.

They have been removed from the JSON.org page. If you own one of them, please
send me the update so that I can reinstate it.


The following links are failing:

<a href="http://www.erlang-projects.org/Public/news/ejson/view">ejson</a>.

<a
href="http://blakeseely.com/blog/archives/2006/03/29/bsjsonadditions-12/">BSJSON\
Additions</a>.

If they do not come back soon, they will be removed.

Jansson v1.0.3 out! This is a bugfix release in the 1.0 release series.

Changes since v1.0.2:

* Check for integer and real overflows and underflows in decoder
* Use the Python json module for tests, or simplejson if the json
   module is not found

Download source: http://www.digip.org/jansson/releases/jansson-1.0.3.tar.bz2
View documentation: http://www.digip.org/jansson/doc/1.0/
Changelog: http://www.digip.org/jansson/releases/CHANGES


What is Jansson?

Jansson is a C library for encoding, decoding and manipulating JSON
data. It features:

* Simple and intuitive API and data model
* Comprehensive documentation
* No dependencies on other libraries
* Full Unicode support (UTF-8)
* Extensive test suite

Jansson is licensed under the MIT license.

For more details, see http://www.digip.org/jansson/.


Petri Lehtinen
petri@...

Hello,

Is there a standard way to represent the information in following XML
snippet
as JSON output.

<attributes>
   <attribute a1="v1">value1</attribute>
   <attribute a2="v2">value2</attribute>
</attributes>

Is there an online tool that would generate this conversion?

Appreciate your response.

~S


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

On Mon, Sep 14, 2009 at 9:17 AM, Shalab Goel <goel.shalab@...> wrote:
> Hello,
>
> Is there a standard way to represent the information in following XML snippet
> as JSON output.
>
> <attributes>
>  <attribute a1="v1">value1</attribute>
>  <attribute a2="v2">value2</attribute>
> </attributes>
>
> Is there an online tool that would generate this conversion?

It depends on what you'd expect to get out of it, but I think the
answer is no: there is nothing obvious and standard.
It really depends on meaning of data above.

<rant>
personally I think it is better to convert from original data
(objects, relational data) into structurally distinct data formats
(xml and json have fundamentally differen data models, hierachic vs
struct/frame/object model... but I digress). And as such, if possible,
it's better to figure out meaning of data and then produce "native"
xml and json, without trying to convert from json to xml or vice
versa. Latter is more difficult, and data in one (... or both) of
formats will end up looking funny and somewhat unreadable
</rant>

Anyway: instead of "the" standard, there however multiple competing
standard proposals (called "mapping conventions") that do allow
converting any XML content into well-formed (if bit odd-looking and
alien-feeling :) ) JSON.
One such convention is Badgerfish (see, for example
[http://sujitpal.blogspot.com/2007/10/converting-xml-to-badgerfish-json.html]);
and there are multiple others that claim to produce natural JSON.

-+ Tatu +-

”instead of "the" standard, there however multiple competing standard proposals
[…] that do allow converting any XML content into well-formed […] JSON.”

I don’t think that’s true, and it is certainly not true for Badgerfish. All of
the mapping conventions I know of fail to correctly represent “document type”
XML such as:

<asdf>
<a>…</a>
<a>…</a>
<b>…</b>
<a>…</a>
</asdf>

This speaks to the heart of the difference between XML and JSON. In order to
represent something like this in JSON, the contents of the “asdf” element would
have to be in an array. This is not an impossible solution, but using that
convention throughout makes for very ugly JSON.

/Jakob

Fra: json@yahoogroups.com [mailto:json@yahoogroups.com] Pĺ vegne af Tatu
Saloranta
Sendt: 14. september 2009 18:51
Til: json@yahoogroups.com
Emne: Re: [json] JSON representation for XML snippet


On Mon, Sep 14, 2009 at 9:17 AM, Shalab Goel <goel.shalab@...> wrote:
> Hello,
>
> Is there a standard way to represent the information in following XML snippet
> as JSON output.
>
> <attributes>
>  <attribute a1="v1">value1</attribute>
>  <attribute a2="v2">value2</attribute>
> </attributes>
>
> Is there an online tool that would generate this conversion?

It depends on what you'd expect to get out of it, but I think the
answer is no: there is nothing obvious and standard.
It really depends on meaning of data above.

<rant>
personally I think it is better to convert from original data
(objects, relational data) into structurally distinct data formats
(xml and json have fundamentally differen data models, hierachic vs
struct/frame/object model... but I digress). And as such, if possible,
it's better to figure out meaning of data and then produce "native"
xml and json, without trying to convert from json to xml or vice
versa. Latter is more difficult, and data in one (... or both) of
formats will end up looking funny and somewhat unreadable
</rant>

Anyway: instead of "the" standard, there however multiple competing
standard proposals (called "mapping conventions") that do allow
converting any XML content into well-formed (if bit odd-looking and
alien-feeling :) ) JSON.
One such convention is Badgerfish (see, for example
[http://sujitpal.blogspot.com/2007/10/converting-xml-to-badgerfish-json.html]);
and there are multiple others that claim to produce natural JSON.

-+ Tatu +-

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

To do the XML to JSON conversion I use our XSLT (which can also go the other way
as well)

<xsl:output method=’json’/>
https://www.p6r.com/articles/2008/11/02/xsloutput-methodjson/




Mark Joseph, Ph.D.
President
P6R, Inc
408-205-0361
mark@...
Skype: markjoseph_sc
   _____

From: Jakob Kruse [mailto:kruse@...]
To: json@yahoogroups.com
Sent: Mon, 14 Sep 2009 10:38:56 -0700
Subject: SV: [json] JSON representation for XML snippet






”instead of "the" standard, there however multiple competing standard
proposals […] that do allow converting any XML content into well-formed […]
JSON.”

   I don’t think that’s true, and it is certainly not true for Badgerfish.
All of the mapping conventions I know of fail to correctly represent “document
type” XML such as:

   <asdf>
   <a>…</a>
   <a>…</a>
   <b>…</b>
   <a>…</a>
   </asdf>

   This speaks to the heart of the difference between XML and JSON. In order to
represent something like this in JSON, the contents of the “asdf” element
would have to be in an array. This is not an impossible solution, but using that
convention throughout makes for very ugly JSON.

   /Jakob

   Fra: json@yahoogroups.com [mailto:json@yahoogroups.com] PĂĄ vegne af Tatu
Saloranta
   Sendt: 14. september 2009 18:51
   Til: json@yahoogroups.com
   Emne: Re: [json] JSON representation for XML snippet


   On Mon, Sep 14, 2009 at 9:17 AM, Shalab Goel <goel.shalab@...> wrote:
   > Hello,
   >
   > Is there a standard way to represent the information in following XML
snippet
   > as JSON output.
   >
   > <attributes>
   >  <attribute a1="v1">value1</attribute>
   >  <attribute a2="v2">value2</attribute>
   > </attributes>
   >
   > Is there an online tool that would generate this conversion?

   It depends on what you'd expect to get out of it, but I think the
   answer is no: there is nothing obvious and standard.
   It really depends on meaning of data above.

   <rant>
   personally I think it is better to convert from original data
   (objects, relational data) into structurally distinct data formats
   (xml and json have fundamentally differen data models, hierachic vs
   struct/frame/object model... but I digress). And as such, if possible,
   it's better to figure out meaning of data and then produce "native"
   xml and json, without trying to convert from json to xml or vice
   versa. Latter is more difficult, and data in one (... or both) of
   formats will end up looking funny and somewhat unreadable
   </rant>

   Anyway: instead of "the" standard, there however multiple competing
   standard proposals (called "mapping conventions") that do allow
   converting any XML content into well-formed (if bit odd-looking and
   alien-feeling :) ) JSON.
   One such convention is Badgerfish (see, for example
  
[http://sujitpal.blogspot.com/2007/10/converting-xml-to-badgerfish-json.html]);
   and there are multiple others that claim to produce natural JSON.

   -+ Tatu +-

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




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

On Mon, Sep 14, 2009 at 10:38 AM, Jakob Kruse <kruse@...> wrote:
> ”instead of "the" standard, there however multiple competing standard
proposals […] that do allow converting any XML content into well-formed […]
JSON.”
>
> I don’t think that’s true, and it is certainly not true for Badgerfish. All of
the mapping conventions I know of fail to correctly represent “document type”
XML such as:
>
> <asdf>
> <a>…</a>
> <a>…</a>
> <b>…</b>
> <a>…</a>
> </asdf>
>
> This speaks to the heart of the difference between XML and JSON. In order to
represent something like this in JSON, the contents of the “asdf” element would
have to be in an array. This is not an impossible solution, but using that
convention throughout makes for very ugly JSON.

Perhaps I should have worded it as "try to allow...". And that they do
it with varying level of success -- as you point out, badgerfish fails
for that case, and others in variety of other ways. Plus even if all
nuances of XML Infoset were covered (from namespaces to processing
instructions etc), resulting JSON does look ugly. So yes, this is part
of the whole impedance part, JSON <> XML.

-+ Tatu +-

In taht way you are loosing data type.
If interested, this is not that standard but kinda an easy spec to follow
(plus a script)
http://webreflection.blogspot.com/2008/07/jxon-lossless-javascript-to-xml-object\
.html

Hope will help somehow


On Mon, Sep 14, 2009 at 5:17 PM, Shalab Goel <goel.shalab@...> wrote:

>
>
> Hello,
>
> Is there a standard way to represent the information in following XML
> snippet
> as JSON output.
>
> <attributes>
> <attribute a1="v1">value1</attribute>
> <attribute a2="v2">value2</attribute>
> </attributes>
>
> Is there an online tool that would generate this conversion?
>
> Appreciate your response.
>
> ~S
>
> [Non-text portions of this message have been removed]
>
>
>


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

er, me too in the precedent link there is a demo:
http://www.3site.eu/JXON/

I guess my spec is simple:

<element>
Boolean = <boolean>true|false</boolean>
Date = <date>YYYY-MM-DDTHH:II:SS</date>
Null = <null/>
Number = <number>N|Z</number>
String = <string>string content</string>
Array = <array><element-list/></array>
Object = <object><element-list key="element-key"/></object>

<element-list> = a list of precedent element

While the code to transform to and from XML to JSON and vice-versa is here:
http://www.devpro.it/code/193.html

A bit old, I need to rewrite some stuff, but maybe examples and the
code itself could be a hint.

Regards




On Mon, Sep 14, 2009 at 7:17 PM, Mark Joseph <mark@...> wrote:

>
>
> To do the XML to JSON conversion I use our XSLT (which can also go the
> other way as well)
>
> <xsl:output method=’json’/>
> https://www.p6r.com/articles/2008/11/02/xsloutput-methodjson/
>
> Mark Joseph, Ph.D.
> President
> P6R, Inc
> 408-205-0361
> mark@... <mark%40p6r.com>
> Skype: markjoseph_sc
> _____
>


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

On Mon, Sep 14, 2009 at 11:17 AM, Mark Joseph <mark@...> wrote:
> To do the XML to JSON conversion I use our XSLT (which can also go the other
way as well)
>
> <xsl:output method=’json’/>
> https://www.p6r.com/articles/2008/11/02/xsloutput-methodjson/

Does this (JSON -> xml events) work with any JSON input? Aside from
some cases that should be impossible (JSON content can include
character content that is illegal in XML), there are smaller questions
of what to map Arrays to... but those would be solvable. But do
require adoption some kind of convention. :-)

So, what do array markers translate to? I'm mostly asking because I
have been planning addition of some xml compatibility features for
JSON processor I am working on, and this is one of things where there
any many options. But if there are emerging (de facto) standards, it'd
be good to follow.

-+ Tatu +-

So the way the system works is that our JSON parser is called from a plugin to
our DOM parser.   That plugin calls the DOM parser API that creates nodes in the
DOM tree.
This is documented in another article:
https://www.p6r.com/articles/2008/05/06/xslt-and-xpath-for-json/

The plugin architecture is also used for XML, where a separate plugin calls our
SAX-2 XML parser so they both work the same way.

This way we convert whatever into a DOM tree and then can run full XSLT 2.0 (
not 1.0 ) and full
XPATH 2.0  on any of the data.

-Mark
P6R Inc


   _____

From: Tatu Saloranta [mailto:tsaloranta@...]
To: json@yahoogroups.com
Sent: Mon, 14 Sep 2009 12:37:39 -0700
Subject: Re: SV: [json] JSON representation for XML snippet

On Mon, Sep 14, 2009 at 11:17 AM, Mark Joseph <mark@...> wrote:
   > To do the XML to JSON conversion I use our XSLT (which can also go the other
way as well)
   >
   > <xsl:output method=’json’/>
   > https://www.p6r.com/articles/2008/11/02/xsloutput-methodjson/

   Does this (JSON -> xml events) work with any JSON input? Aside from
   some cases that should be impossible (JSON content can include
   character content that is illegal in XML), there are smaller questions
   of what to map Arrays to... but those would be solvable. But do
   require adoption some kind of convention. :-)

   So, what do array markers translate to? I'm mostly asking because I
   have been planning addition of some xml compatibility features for
   JSON processor I am working on, and this is one of things where there
   any many options. But if there are emerging (de facto) standards, it'd
   be good to follow.

   -+ Tatu +-


   ------------------------------------

   Yahoo! Groups Links





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