Well-designed XML Data Marcelo Arenas and Leonid Libkin University of Toronto.

Well-designed XML Data

Marcelo Arenas and Leonid Libkin

University of Toronto

Outline

Part 1 - Database Normalization from the 1970s and 1980s.

Part 2 - Classical theory revisited: normalizing XML documents.

Part 3 - Classical theory re-done: new justifications for normalization.

Part 1: Classical Normalization

Design: decide how to represent the information in a particular data model.

• Even for simple application domains there is a large number of ways of representing the data of interest.

We have to design the schema of the database.

• Set of relations.

• Set of attributes for each relation.

• Set of data dependencies.

Designing a Database: An Example

Attributes: number, title, section, room.

Data dependency: every course number is associated with only one title.

Relational Schema:

R(number, title, section, room),

number title

GOOD alternative:

S(number, title), number title

T(number, section, room),

BAD alternative:

Problems with BAD: Update Anomaly

number title section room

CSC258 Computer Organization 1 LP266

CSC258 Computer Organization 2 GB258

CSC434 Database Systems 1 GB248

Title of CSC258 is changed to Computer Organization I.

CSC258 Computer Organization 1 LP266

CSC434 Database Systems 1 GB248

Title of CSC258 is changed to Computer Organization I.

CSC258 Computer Organization I

1 LP266

2 GB258

3 GB248

CSC434 Database Systems 1 GB248Title of CSC258 is changed to Computer Organization I.The instance stores redundant information.

Deletion Anomaly

1 LP266

2 GB258

3 GB248

CSC434 Database Systems 1 GB248CSC434 is not given in this term.

Deletion Anomaly

1 LP266

2 GB258

3 GB248

CSC434 Database Systems 1 GB248CSC434 is not given in this term.

Deletion Anomaly

1 LP266

2 GB258

3 GB248

CSC434 is not given in this term.

Additional effect: all the information about CSC434 was deleted.

Insertion Anomaly

1 LP266

2 GB258

3 GB248

A new course is created: (CSC336, Numerical Methods)

Insertion Anomaly

1 LP266

2 GB258

3 GB248

Insertion Anomaly

1 LP266

2 GB258

3 GB248

CSC336 Numerical Methods ? ?A new course is created: (CSC336, Numerical Methods)The instance stores attributes that are not directly related.

Avoiding Update Anomalies

number

CSC258

Computer Organization

CSC434

Database Systems

number

section room

CSC258

1 LP266

CSC258

2 GB258

CSC258

3 GB248

CSC434

1 GB248Title of CSC258 is changed to Computer Organization I.

number

CSC258

Computer Organization

CSC434

Database Systems

number

section room

CSC258

1 LP266

CSC258

2 GB258

CSC258

3 GB248

CSC434

1 GB248Title of CSC258 is changed to Computer Organization I.

number

CSC258

Computer Organization I

CSC434

Database Systems

number

section room

CSC258

1 LP266

CSC258

2 GB258

CSC258

3 GB248

CSC434

1 GB248Title of CSC258 is changed to Computer Organization I.CSC434 is not given in this term.

The instance does not store redundant information.

number

CSC258

CSC434

Database Systems

number

section room

CSC258

1 LP266

CSC258

2 GB258

CSC258

3 GB248

CSC434

1 GB248CSC434 is not given in this term.

number

CSC258

CSC434

Database Systems

number

section room

CSC258

1 LP266

CSC258

2 GB258

CSC258

3 GB248

CSC434 is not given in this term.

The title of CSC434 is not removed from the instance.

number

CSC258

CSC434

Database Systems

number

section room

CSC258

1 LP266

CSC258

2 GB258

CSC258

3 GB248

number

CSC258

CSC434

Database Systems

CSC336

Numerical Methods

number

section room

CSC258

1 LP266

CSC258

2 GB258

CSC258

3 GB248

A new course is created: (CSC336, Numerical Methods)No information about sections has to be provided.Each relation stores attributes that are directly related.

Normalization Theory

Main idea: a normal form defines a condition that a well designed database should satisfy.

Normal form: syntactic condition on the database schema.• Defined for a class of data dependencies.

Main problems:

• How to test whether a database schema is in a particular normal form.

• How to transform a database schema into an equivalent one satisfying a particular normal form.

Normalization Theory Today

Normalization theory for relational databases was developed in the 70s and 80s.

Why do we need normalization theory today?• New data models have emerged: XML.

• XML documents can contain redundant information.

Redundant information in XML documents:• Can be discovered if the user provides semantic

information.

• Can be eliminated.

Part 2: XML and Normalization

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

name #PCDATA

grade #PCDATA

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

name #PCDATA

grade #PCDATA

</course>

</courses>

XML Document:

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

name #PCDATA

grade #PCDATA

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

name #PCDATA

grade #PCDATA

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

name #PCDATA

grade #PCDATA

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

name #PCDATA

grade #PCDATA

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

name #PCDATA

grade #PCDATA

<taken_by>

</student>

</taken_by>

</course>

</courses>

XML Document:

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

name #PCDATA

grade #PCDATA

XML Databases

D : : Two students with the same @sno value must have the same name.

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

XML Schema: (D, )

Redundancy in XML

courses

coursecourse info

@cno @cno taken_bytaken_by

student student

@snoname gradegrade name@sno

student

name@sno

“st1” “st1” “A+”“B+”

“CSC258” “CSC434”

“Fox”“Fox”

“st1” “Fox”

XML Database Normalization

DTD: Data dependency:

Two students with the same @sno value must have the same name.

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student name, grade

XML Database Normalization

, info* @sno is the identifier of info elements.

courses course*

course @cno

course taken_by

taken_by

student*

student @sno

student gradeinfo @sno

info name

Data dependency:

Two students with the same @sno value must have the same name.

A “Non-relational” Example

conf conf

title issueissue

article articlearticle

@yeartitle title @year

“ICDT”

author @yeartitleauthor“1999”

“1999”

“1999”“Dong” “2001”“Jarke”

“2001”

“. . .” “. . .” “. . .”

XNF: XML Normal Form

It eliminates two types of anomalies.

It was defined for XML functional dependencies:

DBLP.conf.@title DBLP.confDBLP.conf.issue

DBLP.conf.issue.article.@year

Problems to Address

Functional dependencies for XML.

Normal form for XML documents (XNF).

•Generalizes BCNF.

Algorithm for normalizing XML documents.

•Implication problem for functional dependencies.

Framework: Paths in DTDs

Paths(D): all paths in a DTD Dcourses.course courses.course.@cnocourses.course.student.namecourses.course.student.name.S

We distinguish three kinds of elements: attributes (@), strings (S) and element types.

FDs are defined by means of a relational representation of XML documents.

Framework: XML Trees

courses

coursecourse

“cs100”

@sno name grade @sno name grade

student student

“123” “456”

“Fox” “B+” “Smith” “A-”

S S S S

Tree Tuples

courses

course

@cno student

“cs100”

t(courses) = v0

t(courses.course) = v1

t(courses.course.@cno) = “cs100”t(courses.course.student) = v2

t(p) = , for the remaining paths

Relational representation: tree tuples - mappings

t : Paths(D) Vertices Strings {}

A tree tuple represents an XML tree:

XML Tree: set of Tree Tuples

courses

coursecourse

“cs100”

@sno name grade @sno name grade

student student

“123” “456”

“Fox” “B+” “Smith” “A-”

S S S S

courses

course

“cs100”

student

@sno name grade

“123”

“Fox” “B+”

@sno name grade

student

“456”

“Smith” “A-”

course

Functional Dependencies for XML

Expressions of the form: X Y

defined over a DTD D, where X, Y are finitenon-empty subsets of Paths(D).

XML tree T can be tested for satisfaction of X Y

X Y Paths(T) Paths(D)

T X Y if for every pair u, v of tree tuples in T:

u.X = v.X and u.X ≠ implies u.Y = v.Y

FD: Examples

University DTD: courses course*course @cno, student*student @sno, name, grade

Two students with the same @sno value must have the same name:

courses.course.student.@sno courses.course.student.name.S

Every student can have at most one grade in every course:

{ courses.course, courses.course.student.@sno }

courses.course.student.grade.S

Implication Problem for FD

Given a DTD D and a set of functional dependencies {}:

(D, ) if for any XML tree T conforming to D and satisfying , it is the case that T

(D, )+ = { | (D, ) }

Functional dependency is trivial if it is implied by the DTD alone: (D, )

XML specification: a DTD D and a set of functional dependencies .

A Relational DB is in BCNF if for every non-trivial functional dependency X Y in the specification, X is a key.

(D, ) is in XNF if:

For each non-trivial FD X p.@l or X p.S in (D, )+, X p is in (D, )+.

Back to DBLP

DBLP is not in XNF:

DBLP.conf.issue DBLP.conf.issue.article.@year (D,)+

DBLP.conf.issue DBLP.conf.issue.article

Proposed solution is in XNF.

Normalization Algorithm

The algorithm applies two transformations until theschema is in XNF.

If there is an anomalous FD of the form:

DBLP.conf.issue DBLP.conf.issue.article.@year

then apply the “DBLP example rule”.

Otherwise: choose a minimal anomalous FD and apply the “University example rule”.

Normalizing XML Documents

Theorem The decomposition algorithm terminates and outputs a specification in XNF.

Furthermore, it does not lose information:

UnnormalizedNormalizedXML document XML Document

Q1, Q2 are XQuery core queries.

Part 3: What was Missing? Justification!

What is a good database design?

• Well-known solutions: BCNF, 4NF, …

But what is it that makes a database design good?

• Elimination of update anomalies.

• Existence of algorithms that produce good designs: lossless decomposition, dependency preservation.

Previous work was specific for the relational model.

• Classical problems have to be revisited in the XML context.

Justification of Normal Forms

Problematic to evaluate XML normal forms.

• No XML update language has been standardized.

• No XML query language yet has the same “yardstick” status as relational algebra.

• We do not even know if implication of XML FDs is decidable!

We need a different approach.

• It must be based on some intrinsic characteristics of the data.

• It must be applicable to new data models.

• It must be independent of query/update/constraint issues.

Our approach is based on information theory.

Information Theory

Entropy measures the amount of information provided by a certain event.

Assume that an event can have n different outcomes with probabilities p1, …, pn.

Amount of information gained by knowing that event i occurred :Average amount of information gained (entropy) :

Entropy is maximal if each pi = 1/n :

i ii p

Entropy and Redundancies

Database schema: R(A,B,C), A B

Instance I:

Pick a domain properly containing adom(I) :

• Probability distribution: P(4) = 0 and P(a) = 1/5, a ≠ 4

• Entropy: log 5 ≈ 2.322

Pick a domain properly containing adom(I) : {1, …, 6}

• Probability distribution: P(2) = 1 and P(a) = 0, a ≠ 2

• Entropy: log 1 = 0

{1, …, 6}

Entropy and Normal Forms

Let be a set of FDs over a schema S.

Theorem (S,) is in BCNF if and only if for every instance of (S,) and for every domain properly containing adom(I), each position carries non-zero amount of information (entropy > 0).

A similar result holds for 4NF and MVDs.

This is a clean characterization of BCNF and 4NF, but the measure is not accurate enough ...

Problems with the Measure

The measure cannot distinguish between different types of data dependencies.

It cannot distinguish between different instances of the same schema:

entropy = 0

R(A,B,C), A B

entropy = 0

A General Measure

Instance I of schema R(A,B,C), A B :

A General Measure

Initial setting: pick a position p Pos(I) and pick k such that adom(I) {1, …, k}. For example, k = 7.

A General Measure

Computation: for every X Pos(I) – {p}, compute probability distribution P(a | X), a {1, …, k}.

A General Measure

P(2 | X) =

A General Measure

P(2 | X) =

A General Measure

P(2 | X) =

A General Measure

P(2 | X) =

A General Measure

P(2 | X) = 48/

A General Measure

P(2 | X) = 48/

For a ≠ 2, P(a | X) =

A General Measure

P(2 | X) = 48/

For a ≠ 2, P(a | X) =

A General Measure

P(2 | X) = 48/

For a ≠ 2, P(a | X) =

A General Measure

P(2 | X) = 48/

For a ≠ 2, P(a | X) = 42/

(48 + 6 42) = 0.16

(48 + 6 42) = 0.14

Entropy ≈ 2.8057 (log 7 ≈ 2.8073)

A General Measure

Value : we consider the average over all sets X Pos(I) – {p}.

•Average: 2.4558 < log 7 (maximal entropy)

•It corresponds to conditional entropy.

•It depends on the value of k ...35

A General Measure

Previous value:

For each k, we consider the ratio:

• How close the given position p is to having the maximum possible information content.

General measure:

)|( pInf kI

pInf kI

pInfpInf

kI log

)|(lim)|(

Basic Properties

The measure is well defined:

For every set of first order constraints defined over a schema S, every I inst(S,), and every p Pos(I): exists.

Bounds:

)|( pInf I

1)|(0 pInf I

Basic Properties

The measure does not depend on a particular representation of constraints. If 1 and 2 are equivalent:

It overcomes the limitations of the simple measure: R(A,B,C), A B

)|()|( 21 pInfpInf II

0.875 0.781

Well-Designed Databases

Definition A database specification (S,) is well-designed if for every I inst(S,) and every p Pos(I), = 1.

In other words, every position in every instance carries the maximum possible amount of information.

We would like to test this definition in the relational world ...

)|( pInf I

Relational Databases

is a set of data dependencies over a schema S:

= : (S,) is well-designed.

is a set of FDs: (S,) is well-designed if and only if (S,) is in BCNF.

is a set of FDs and MVDs: (S,) is well-designed if and only if (S,) is in 4NF.

is a set of FDs and JDs:

• If (S,) is in PJ/NF or in 5NFR, then (S,) is well-designed. The converse is not true.

• A syntactic characterization of being well-designed is given in [AL03].

Relational Databases

The problem of verifying whether a relational schema is well-designed is undecidable.

If the schema contains only universal constraints (FDs, MVDs, JDs, …), then the problem becomes decidable.

Now we would like to apply our definition in the XML world ...

XML Databases

XML schema: (D,).

• D is a DTD.

• is a set of data dependencies over D.

We would like to evaluate XML normal forms.

The notion of being well-designed extends from relations to XML.

• The measure is robust; we just need to define the set of positions in an XML tree T: Pos(T).

Positions in an XML Tree

conf conf

title issueissue

article articlearticle

@yeartitle title @year

“ICDT”

author @yeartitleauthor“1999” “1999”“Dong” “2001”“Jarke”“. . .” “. . .” “. . .”

“ICDT”

“1999” “1999”“Dong” “2001”“Jarke”“. . .” “. . .” “. . .”

Well-Designed XML Data

We consider k such that adom(T) {1, …,k}.

For each k :

We consider the ratio:

General measure:

)|( pInf kT

pInfpInf

kT log

)|(lim)|(

kpInf kT log/)|(

For arbitrary XML data dependencies:

Definition An XML specification (D,) is well-designed if for every T inst(D,) and every p Pos(T), = 1.

For functional dependencies:

Theorem An XML specification (D,) is in XNF if and only if (D,) is well-designed.

)|( pInfT

Normalization Algorithms

The information-theoretic measure can also be used for reasoning about normalization algorithms.

For BCNF and XNF decomposition algorithms:

Theorem After each step of these decomposition algorithms, the amount of information in each position does not decrease.

Future Work

We would like to consider more complex XML constraints and characterize good designs they give rise to.

We would like to characterize 3NF by using the measure developed in this paper.

• In general, we would like to characterize “non-perfect” normal forms.

We would like to develop better characterizations of normalization algorithms using our measure.

• Why is the “usual” BCNF decomposition algorithm good? Why does it always stop?

Well-designed XML Data Marcelo Arenas and Leonid Libkin University of Toronto.

Documents

Transcript of Well-designed XML Data Marcelo Arenas and Leonid Libkin University of Toronto.

Arenas Letter

University of Toronto Leonid Libkin

msarenas - Ms Arenas

Arenas posse

Database Normalization Revisited: An information-theoretic approach Leonid Libkin Joint work with Marcelo Arenas and Solmaz Kolahi.

Arenas castellanos

Leonid Yuriev - TopGun

Sport arenas

Integration arenas

Leonid Ilyich Brezhnev

Lazarus (Leonid Andreyev)

ARENAS RODRIGUEZ

Leonid Afremov - Biography

Leonid Leonid Leonid Leonid

Punta arenas

1 Inhomepages.inf.ed.ac.uk/libkin/papers/tcs-vienna.pdf · Lo w er Bounds for In v arian t Queries in Logics with Coun ting Leonid Libkin a; 1 Limso on W ong b a Dep artment of Computer

Leonid Sukhikh

Leonid Ekimov

Nelly Arenas

Knowledge Graphs and Big Data Processing978-3-030-53199...182 References 18. Arenas, M., Barcel´o, P., Libkin, L., Murlak, F.: Foundations of Data Exchange. Cambridge University Press,