RE: xml to json converter; common ground via PSVI?

A few reactions… The following reference is likely familiar to most but nevertheless important and insightful.

• seriot.ch - Parsing JSON is a Minefield 💣
• http://seriot.ch/parsing_json.php

Curiously PSVI has always been a bit slippery to find well defined at W3C, it is not prominent.  PSVI was fundamental to the rigorous definition of EXI, reconciling multiple issues at once.

• https://en.wikipedia.org/wiki/XML_Schema_(W3C)#Post-Schema-Validation_Infoset
• “After XML Schema-based validation, it is possible to express an XML document's structure and content in terms of the data model that was implicit during validation. The XML Schema data model includes:
• The vocabulary (element and attribute names)
• The content model (relationships and structure)
• The data types
• This collection of information is called the Post-Schema-Validation Infoset (PSVI). The PSVI gives a valid XML document its "type" and facilitates treating the document as an object, using object-oriented programming (OOP) paradigms.”

• W3.org search: PSVI
• https://duckduckgo.com/?q=site%3Aw3.org+psvi&search-submit=&ia=web
• Nothing authoritative on PSVI found within first 10 searches; proceed with manual document search

• XML Schema Part 1: Structures Second Edition, W3C Recommendation 28 October 2004
• 2.1 Overview of XML Schema
• https://www.w3.org/TR/xmlschema-1/#d0e504
• Finally: “[Definition:]  We refer to the augmented infoset which results from conformant processing as defined in this specification as the post-schema-validation infoset, or PSVI.”

• Schema Validation and the PSVI, R. Alexander Milowski
• https://courses.ischool.berkeley.edu/i290-14/s05/lecture-17/allslides.html

• Efficient XML Interchange (EXI) Format 1.0 (Second Edition)
• https://www.w3.org/TR/exi

• EXI for JSON (EXI4JSON)
• https://www.w3.org/TR/exi-for-json

Meanwhile finalization of JSON Schema standardization and implementation work at IETF and elsewhere has been proceeding for years at a glacial pace.  Due diligence is good, hopefully they will converge and complete some day.

• JSON Schema
• https://json-schema.org

Potential point of general interest - have always wondered:  might PSVI be more clearly defined in order to encompass expressive power of both XML JSON as a well-scrutinized well-defined capability.  This might benefit many efforts.  Certainly the simplicity of EXI4JSON points out immense congruent overlap.

p.s.    JSON comments and skateboards are not a crime!  :0

all the best, Don
--
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman@nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman

On Fri, 2021-09-17 at 17:36 +0530, Mukul Gandhi wrote:
> Hi all,
>     I've been playing around today, with this topic and thought of
> sharing
> my findings with people here.
>
> I wrote an XML to JSON converter, using following tools,
> 1. Little bit of java programming
> 2. JAXB
> 3. jackson-databind library

You might want to compare it to the JSON support built in to XQuery and
XSLT and XPath these days. Also test  content containing [ ] " { } " '
& < > \ and / as well as element names and content containing non-ascii
characters. <ആൺകുട്ടി>....</ആൺകുട്ടി> or <ARÊT>...</ARÊT>.

Liam

--
Liam Quin, Delightful Computing
Available for XML/Document/Information Architecture/XSLT/
XSL/XQuery/Web/Text Processing/A11Y training, work & consulting.
Barefoot Web-slave, antique illustrations:  FOBO: Pictures From Old Books dot Org

_______________________________________________________________________

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.