OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] XML design for converting to and from JSON?

JSONx was defined jointly by DB2 and DataPower groups within IBM.
Reason was there was (and is) no standard for representing JSON in XML.
Each approach has its own advantages and disadvantages.

JSONx became available in DataPower firmware in 2009.
It was submitted as internet draft as well, but timed out:

Because for processing JSON there is no best way DataPower provided
JSONiq with its XQuery 1.0 processor in 6.0.0 firmware in 6/2013 as well.

And with 7.0.0 firmware in 6/2014 the appliance provides with GatewayScript
a Javascript flavor on the box as well.

Processors can be mixed if wanted in actions for processing a transaction.
XSLT 1.0 processor even allows to "call out" to XQuery processor allowing
to have XPath 1.0 and XPath 2.0 in a single (concat) statement:

Mit besten Gruessen / Best wishes,

Hermann Stamm-Wilbrandt
Level 3 support for XML Compiler team & Fixpack team lead
IBM DataPower Gateways
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

  From:       Peter Hunsberger <peter.hunsberger@gmail.com>            
  To:         "Costello, Roger L." <costello@mitre.org>, "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
  Date:       12/15/2014 10:21 PM                                      
  Subject:    Re: [xml-dev] XML design for converting to and from JSON?

IBM has a hardware accelerated edge device that goes by the name of
Datapower.  Among other things it has a facility for doing exactly this.
The XML format is known as JSONX., Basic docs are here:


On Mon Dec 15 2014 at 10:44:36 AM Costello, Roger L. <costello@mitre.org>
  Hi Folks,

  The ability to easily convert XML-formatted data into JSON-formatted data
  and vice versa is a good thing, I think.

  If you were setting out to design some XML with a design goal that the
  XML can be easily converted to JSON, how would you design the XML?

  Are there some features of XML that might inhibit its easy conversion to
  JSON? What about these features:

          - Namespaces?
          - Mixed content?
          - Processing instructions?
          - Comments?
          - Attributes?
          - DOCTYPE declaration?
          - Entities?
          - Other things?

  Perhaps you have already created guidelines for XML design to enable easy
  conversion to JSON? If so, would you share your guidelines please?



  XML-DEV is a publicly archived, unmoderated list hosted by OASIS
  to support XML implementation and development. To minimize
  spam in the archives, you must subscribe before posting.

  [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
  Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
  subscribe: xml-dev-subscribe@lists.xml.org
  List archive: http://lists.xml.org/archives/xml-dev/
  List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS