problem-oriented IS development with (meta)data
object adequacy maintenance throughout the entire
lifecycle.
On the basis of multi-parameter functional
F = F ((v), (e), …) (s) (p),
where respective values in brackets represent
client interface parameters, data access device
parameters, user personal preferences and user
registration status, a problem-oriented object portal
personalization model has been built, based on
functional ⎢⎢F ⎢⎢ evaluation.
Abstract machine for content management
(AMCM) (Zykov, 2005) is suggested as an ECM IS
model, improving categorical abstract machine
(Cousineau, 1987). At any given moment AMCM is
determined by its state; dynamics of its work cycle
can be formalized by explicit enumeration of
possible state changes.
From the formal model viewpoint, when portal
page templates are mapped into the pages, variable
binding evaluates the variables that represent
template elements and their values, i.e. portal page
elements.
AMCM semantics can be described in terms of
semantic domain theory (Scott, 1982):
1) Standard (most commonly used within the
model framework) domains are defined;
2) Finite (containing explicitly enumerable
elements) domains are defined;
3) Domain constructors (operations building
new domains out of the existing ones) are defined;
Complex domains are built out of the standard
ones using constructors, which include functional
space [D
1
→
D
2
], Cartesian product [D
1
×
D
2
×
…
×
D
n
],
disjunctive sum [D
1
+ D
2
+… +D
n
] and sequence D
*
.
Let us collect all possible language identifiers
into Ide domain, commands – into Com domain, and
expressions – into Exp domain. AMCM language
contain environment model is constructed as
follows:
St = Mem
×
In
×
Out;
Mem = Ide
→
[Val + {unbound}];
In = Val*;
Out = Val*;
Value = T
1
+ T
2
+ ….
AMCM state is defined by “memory” state
including input values (i.e. content) and output
values (i.e. web pages) of the abstract machine.
Therewith, under memory a mapping from identifier
domain into value domain is implied, which is
similar to lambda calculus variable binding. For
correct exception handling, unbound element should
be added to the domains. Value domain is formed by
disjunctive sum of domains, which contain content
types of AMCM language.
Semantic statements describe denotates (i.e.
correct constructions) of AMCM (meta)data object
manipulation language.
Semantic statements for basic AMCM language
commands and expressions are presented in (Zykov,
2005).
Constant denotates are their respective values in
a form of ordered pair of <variable, value>, while
program state remains unchanged.
Identifier denotates are identifiers bound with
their values (if binding is possible) in a form of
ordered tuples of <variable_in_memory, identifier,
state>, while the state remains unchanged (an error
message is generated if the binding is impossible).
Thus, ECM IS template binding with the content
may result in AMCM state change and in a number
of limited, predefined cases (particularly, under
template and content type incompatibility) – in error
generation.
Semantic statement for an AMCM command,
which assigns content to template element, results in
state change with substitution of content value by
the identifier in memory.
3 CUSTOMIZING THE ECM
Let us apply the computational models introduced to
the target ECM IS and the portal.
The problem domain model is based on two-
level compression (Wolfengagen, 1999), which is
interpreted here as establishing relationships
between data object classes C of the integrated
problem domain D:
C = Iw:[D]
∀
v:D (w(v)
↔
∆
) = {v:D |
∆
},
where C and D are in a relation of partial order
with each other (C ISA D), and
∆
is a condition of
data object w belonging to class C (according to a
problem domain expert).
Complex, “multi-dimensional” data objects are
modeled as n-arity data object relationship:
R
n
= Iw: [V
1
,..,V
n
]
∀
v
1
:V
1
…
∀
v
n
:V
n
(w [v
1
,…,v
n
]
↔
Γ
) = {[ v
1
:V
1
,…,v
n
:V
n
] |
Γ
}.
Frame representation is given in (Zykov,2005).
Thus, any class of data objects is a collection of
ordered pairs (v
i
:V
i
), where v
i
is i-th attribute of the
class, and V
i
is type of the class.
However, class attributes contain not only data,
but also metadata (e.g., object dimensions, integrity
constraints, and a bit mask), defining class object
access rights in ECM IS templates.
WEBIST 2006 - WEB INTERFACES AND APPLICATIONS
466