xmas feature wishes ;-)

Sunday, 16 December 2012 · 3 messages
MG
Maximilian Gärber16 Dec 2012 10:01 #
Hi, will there be a JSONiq package under the tree (or anytime soon)? Regards, Max
-- Maximilian Gärber axxepta solutions GmbH Postfach 51 02 38 13362 Berlin Tel +49 (0)30 499 147 66 Fax +49 (0)30 499 147 67 Mail gaerber at axxepta.de
CG
Christian Grün16 Dec 2012 16:40 #
Hi Max,
Quoted text · Maximilian Gärber · 1 line
> will there be a JSONiq package under the tree (or anytime soon)?
I’m afraid it won’t be part of this year’s release, unless anyone in our team gety very very busy within the next few days… From a conceptual perspective, there are some features within JSONiq that compete with our current and the official XQ30 implementation, such as the way how maps are represented internally. However, it’s good to know that JSONiq is a requested feature, and I agree it’s quite a promising approach for both the XML and JSON communities. Maybe we’ll provide a more flexible JSON parsing/serialization concept in BaseX in near future? JsonML, while somewhat standardized, has turned out not to be very well readable. I remember one link you mentioned some time ago, which lists various approaches to serialize XML to JSON [1]. Next, other XQuery processors provide their own, custom solutions (eg [2,3,4]). We could extend our output options to support more than the two existing serializers, eg as follows..
  declare option output:method "json";
  declare option output:version "gdata";
  <xml>hi there</xml>
MG
Maximilian Gärber16 Dec 2012 21:27 #
Hi, 2012/12/16 Christian Grün <christian.gruen at gmail.com>
Quoted text · Christian Grün · 12 lines
> Hi Max, > > > will there be a JSONiq package under the tree (or anytime soon)? > > I’m afraid it won’t be part of this year’s release, unless anyone in > our team gety very very busy within the next few days… > From a conceptual perspective, there are some features within JSONiq > that compete with our current and the official XQ30 implementation, > such as the way how maps are represented internally. However, it’s > good to know that JSONiq is a requested feature, and I agree it’s > quite a promising approach for both the XML and JSON communities. >
I think integrating JSON is the way to go and a really distinctive feature over any other NoSQL DB.
Quoted text · Christian Grün · 14 lines
> Maybe we’ll provide a more flexible JSON parsing/serialization concept > in BaseX in near future? JsonML, while somewhat standardized, has > turned out not to be very well readable. I remember one link you > mentioned some time ago, which lists various approaches to serialize > XML to JSON [1]. Next, other XQuery processors provide their own, > custom solutions (eg [2,3,4]). We could extend our output options to > support more than the two existing serializers, eg as follows.. > > declare option output:method "json"; > declare option output:version "gdata"; > <xml>hi there</xml> > > ..and use our own parser/serializer as default. >
This sounds like a good approach. The current default json serializer does not handle XML attributes, so there's no round-tripping. Personally, I like the gdata version. Regards, Max
Quoted text · Christian Grün · 10 lines
> > What do, or everyone else, think? > Christian > > [1] > http://onwebdevelopment.blogspot.com/2008/05/converting-xml-to-json.html > [2] http://xqilla.sourceforge.net/ExtensionFunctions > [3] http://www.zorba-xquery.com/html/modules/zorba/data-converters/json > [4] http://atomic.exist-db.org/blogs/eXist/JSONSerializer >
-- Maximilian Gärber axxepta solutions GmbH Postfach 51 02 38 13362 Berlin Tel +49 (0)30 499 147 66 Fax +49 (0)30 499 147 67 Mail gaerber at axxepta.de

⚡Generated with XQuery