Experiences with JSON and XML Transformations
[Pages:37]Experiences with JSON and XML
Transformations
IBM Submission to W3C Workshop on Data and Services Integration October 20-21 2011, Bedford, MA, USA
21 October 2011
John Boyer, Sandy Gao, Susan Malaika, Michael Maximilien, Rich Salz, Jerome Simeon
Feedback to: malaika@us.
Copyright IBM
1
Agenda
? Why Do We Want to Transform ? Friendliness vs Grotesqueness (Unfriendliness) ? Typical JSON and XML Mapping Issues
? Round-Trippability ? Friendliness ? A Use Case
? Mapping Approaches
? Overview of Approaches 1-4 ? Recommendations
? Ideas ? Some Published Mappings and References ? The Grand Finale
Copyright IBM
2
Why Do We Want To Transform?
? Trend: Javascript/Web 2.0 dominates for:
? Fast parsing of message content
? Programmer convenience
? Trend: Multiple message formats (Atom, XML, JSON, etc) are becoming common
? XML APIs and REST APIs are being extended to support JSON
? Trend: Enterprises desire validation, declarative constraints and stringency for data content, but also want the benefits of Web 2.0
? Customer demand for:
? Constraint and query features provided by XML
? Programming ease provided by JSON
Copyright IBM
3
Some Data and Metadata Standards
Metadata
Constraints
Triggers Data Exchange Serializations
Annotations
Query & CRUD Languages Query & CRUD APIs
Relational
XML
Data Definition Language (ISO)
Integrity Constraints in table definitions (ISO)
Relational triggers
XML Schema XSD (W3C) , Namespaces (W3C)
Schematron (ISO), RelaxNG (OASIS)
-
SQL standard (ISO) defines an XML serialization but it is not widely used ? There is no agreed JSON serialization. There are RDF serializations.
Not part of the relational model
Data Manipulation Language (DML), SQL, SQL/XML (ISO)
Many for various programming languages, e.g., JDBC, ODBC
XML is a syntax widely used for data exchange (W3C)
Many kinds of annotations are defined for XML schemas and for XML data XPath, XQuery (W3C) and others for CRUD Various, includes some of the relational APIs and specific APIs, e.g., XQJ
JSON
JSON Schema IETF
-
Linked Data
RDFS (RDF Schema), Ontology (W3C and elsewhere)
-
JSON is a serialized format, there are XML representations of JSON too
RIF (W3C) XML, Turtle
-
RDFa (W3C) can be used to
annotate XML
JAQL, JSONiq
SPARQL (W3C)
-
SPARQL Graph Store HTTP
Protocol ? for CRUD (W3C)
Collection
Table, View, Database (ISO) XML Collection Function
-
(W3C)
RDF Graphs (W3C)
Transformation & SQL (Tables to Tables)
XSLT (XML to text, includes JavaScript
-
Other Languages
XML); XForms
SQL XMLTABLE (XML to
relational)
Currently, the role of JSON is mainly
Some XML communities who work on query and transformation languages are
reviewing the idea of XML languages
Copyright IBM
for data exchange between JavaScript clients and servers
4
supporting JSON
Friendly XML
? Friendly XML has multiple unique paths (multiple element and attribute names) in the XML, rather than a name value pair design
? Friendliness provides
? Easy XML consumption by programmers, authors and software
? Straightforward transforms, queries, and indexing capabilities
Friendly XML Example
Armonk NY
UnFriendly XML Example
Copyright IBM
5
Friendly JSON
? Friendly JSON does not include repeating variable names
? Data types are directly associated with each variable
? Friendliness provides easy data structure consumption by JavaScript programmers, authors
Friendly JSON Example
UnFriendly JSON Example
{ "person": { "age": "40", "name": "John Smith" }
}
{ "book" : { "children : [{ "title" : { "attributes" : { "isbn": "15115115" }, "children" : [ "This book is ", { "emph" : "bold" }] } }] }
}
Copyright IBM
6
Typical JSON and XML Mapping Issues
? Round-trip transformations are challenging ? XML to JSON to XML ? JSON to XML to JSON
? General issues
? Different character mapping for names and values in JSON and XML ? Mismatch in data types between JSON and XML ? Semantic infidelity
? XML to JSON issues
? Losing XML namespaces ? Incorrectly mapping XML repeating elements ? Mishandling of relative URLs
? JSON to XML issues
? Incorrectly mapping JSON arrays ? Associating variables with data types in JSON
Copyright IBM
7
Round-trip
? Why is round-tripping important?
? Data and data type information has to be preserved
? Fidelity, to prevent data loss ? Preservation of metadata, order ? Maintain usability regardless of format ? Some details are unnecessary, depending on
use cases ? May not help "Friendliness"
Copyright IBM
8
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- create a ui for configuration with changing json schema
- create json schema from typescript interface
- json schema vs json object
- experiences with json and xml transformations
- using json schema in python
- json net schema generation
- json schema generate markdown
- understanding json schema the home of json schema