Data Vault Ensemble Modeling

You’re a Data Modeller, so why should you be interested in JSON?

George McGeachie, Metadata Matters

Java Script Object Notation (JSON) is a simple open standard human-readable format for data. JSON is used for several purposes, such as publishing public datasets and for passing data between architectural layers and components. Sounds a bit techie to me, so why should a data modeller like me be interested in it?

The same questions were asked about XML almost 20 years ago. However, today’s technical environment is a lot different from 20 years ago, and the capabilities of modelling and design tools have also changed a lot since then. What hasn’t changed is the hierarchical data structure of XML and JSON data – does anyone remember how COBOL programs organise their data?

In this session we will discuss the reasons why data modellers need to take an interest in managing JSON-structured data, and then focus on the technicalities of managing JSON data structures in modelling tools and establishing that all-important JSON data lineage.

George is an independent information management practitioner, with 30+ years’ experience creating and managing data (and other) models in many organisations. He encourages organisations to connect and utilise their metadata islands. He is a blogger, co-author of “Data Modeling Made Simple Using PowerDesigner” with Steve Hoberman, and author of several articles on George is an established conference presenter – if you attend one of his presentations, you’ll see just how much importance he places on the use of modelling and metadata management tools. Currently, George is developing online training courses for users of SAP PowerDesigner. You can contact George at, or via his blog –