P. 1
JCR or RDBMS: why, when, how?

JCR or RDBMS: why, when, how?

4.93

|Views: 11,986|Likes:
Published by day-software
This paper compares java content repositories (JCR) and relational database management systems (RDBMS). The choice between these technologies is often made arbitrarily. The aim is to clarify why this choice should be discussed, when one technology should be selected instead of an other and how the selected technology should be used. Four levels (Data model, Specification, Project, Product) are analyzed to show the impact of this choice on different scopes. Follow a discussion on the best choice depending on the context. This defines the foundations of a decision framework.
This paper compares java content repositories (JCR) and relational database management systems (RDBMS). The choice between these technologies is often made arbitrarily. The aim is to clarify why this choice should be discussed, when one technology should be selected instead of an other and how the selected technology should be used. Four levels (Data model, Specification, Project, Product) are analyzed to show the impact of this choice on different scopes. Follow a discussion on the best choice depending on the context. This defines the foundations of a decision framework.

More info:

Published by: day-software on Jan 23, 2009
Copyright:Attribution

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF or read online from Scribd
See more
See less

04/23/2014

pdf

Designing a JCR semantic can be made with different approaches. If a development process is used, the
semantic will be obtained by translating the applications diagrams. The approach proposed here consists of six
steps which can be iteratively be executed and which result in a semantic blueprint which can be implemented in
a repository.

Input

Output

Activity

Step 1

Identifying the semantic
items

Existing semantic
Requirement

Semantic items

Identifying the concepts which relate to
the requirement and which have to be
localized in the repository.

Step 2

Identifying the inheritance
relationships

Existing semantic
Requirement
Semantic items

Inheritance semantic

Identifying inheritance relationships
between the semantic items.

Step 3

Identifying the hierarchical
relationships

Existing semantic
Requirement
Semantic items

Hierarchical semantic

Identifying hierarchical relationships
between the semantic items.
Thinking in term of composition.

Step 4

Identifying the horizontal
relationships

Existing semantic
Requirement
Semantic items

Horizontal semantic

Identifying horizontal relationships
between semantic items.

Identifying relationship’s types.

Thinking in term of association or
aggregation.

Step 5

Defining cool structure
artifacts

Existing semantic
Requirement
Hierarchical semantic
Horizontal semantic

Organizational semantic

Identifying the patterns which link
hierarchical semantic items.

Step 6

Carefully defining the
integrity rules

Existing semantic
Requirement
Semantic items
Inheritance semantic
Hierarchical semantic
Horizontal semantic
Organizational semantic

New semantic

Only if necessary, declaring in the
semantic the level of coherence which
has to be preserved at a repository
level.

University of Lausanne & Day Software AG
JCR or RDBMS 45

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->