The data landscape
The following figure illustrate the CIO data landscape
Basic Enterprise Architecture Management (BEAMS)
Data Structure: Data Modeling or XML?
by David C. Hay
Published: July 10, 2007
XML is a perfectly good vehicle for describing data to be transmitted from one place to another. It is not so good for describing the semantics – the nature of – the underlying data. It cannot replace data modeling and sound database design.
XML, data modeling, and database design are all ways to structure data. Each has its place. Unfortunately, our industry is somewhat confused as to what those places are. This article attempts to sort that out.
“Accurate and germane sharing of information across jurisdictions is a critical issue for justice and public safety. Although there has been significant progress in the field of information technology, the lack of standards for exchanging justice data has not only been a major obstacle to, but also the principal reason for, the high costs involved with justice information exchange.”1
So says the introduction to an XML model published by the Justice Department to promote data sharing. In response to this the Justice Department has developed the “Global Justice XML Data Model” as a “collaborative effort among local, state, tribal, and federal visionaries.”2
The problem is that, while XML is a perfectly good vehicle for describing data to be transmitted from one place to another, it is not so good for describing the semantics – the nature of – the underlying data. It cannot replace data modeling and sound database design.
This article will present this issue from two different perspectives:
The meaning and significance of different kinds of data models, and
The difference between storing data and transmitting data.
Data modeling using XML