LNCS 2784 An Active Approach To Model Management For Evolving Information Systems 1st Edition by Henrik Gustavsson, Brian Lings, Bjorn Lundell ISBN 3540452753 9783540452751 Full Chapters Included
LNCS 2784 An Active Approach To Model Management For Evolving Information Systems 1st Edition by Henrik Gustavsson, Brian Lings, Bjorn Lundell ISBN 3540452753 9783540452751 Full Chapters Included
https://ebookball.com/product/lncs-2784-an-active-approach-to-model-management-for-evolving-
information-systems-1st-edition-by-henrik-gustavsson-brian-lings-bjorn-lundell-
isbn-3540452753-9783540452751-9394/
★★★★★ 4.6/5.0 (38 reviews) ✓ 121 downloads ■ TOP RATED
"Fantastic PDF quality, very satisfied!" - Emma W.
DOWNLOAD EBOOK
LNCS 2784 An Active Approach to Model Management for
Evolving Information Systems 1st Edition by Henrik
Gustavsson, Brian Lings, Bjorn Lundell ISBN 3540452753
9783540452751 pdf download
Available Formats
https://ebookball.com/product/lncs-2784-towards-temporal-
information-in-workflow-systems-1st-edition-by-carlo-combi-
giuseppe-pozzi-isbn-3540452753-9783540452751-12204/
https://ebookball.com/product/lncs-2784-an-architecture-for-
managing-database-evolution-1st-edition-by-eladio-domanguez-
jorge-lloret-maraa-antonia-zapata-
isbn-3540452753-9783540452751-10796/
LNCS 2784 Basic User Requirements for Mobile Work Support Systems
Three Easy Steps 1st Edition by Asbjorn Folstad, Odd Wiking Rahlff
ISBN 3540452753 9783540452751
https://ebookball.com/product/lncs-2784-basic-user-requirements-
for-mobile-work-support-systems-three-easy-steps-1st-edition-by-
asbjorn-folstad-odd-wiking-rahlff-
isbn-3540452753-9783540452751-13518/
https://ebookball.com/product/lncs-2784-reifying-design-patterns-
to-facilitate-systems-evolution-1st-edition-by-florida-estrella-
zsolt-kovacs-jeanmarie-le-goff-richard-mcclatchey-norbert-toth-
isbn-3540452753-9783540452751-10356/
LNCS 2784 Detection of Redundant Arcs in Entity Relationship
Conceptual Models 1st Edition by David Bowers ISBN 3540452753
9783540452751
https://ebookball.com/product/lncs-2784-detection-of-redundant-
arcs-in-entity-relationship-conceptual-models-1st-edition-by-
david-bowers-isbn-3540452753-9783540452751-11310/
https://ebookball.com/product/lncs-2784-quality-in-conceptual-
modeling-new-research-directions-1st-edition-by-geert-poels-jim-
nelson-marcela-genero-mario-piattini-
isbn-3540452753-9783540452751-10060/
An Approach for Model Based Risk Assessment 1st Edition by Bjorn Axel
Gran, Rune Fredriksen, Atoosa PJ Thunem ISBN 9783540301387
https://ebookball.com/product/an-approach-for-model-based-risk-
assessment-1st-edition-by-bjorn-axel-gran-rune-fredriksen-atoosa-
pj-thunem-isbn-9783540301387-12986/
LNCS 2784 A Lightweight XML Constraint Check and Update Framework 1st
Edition by Hong Su, Bintou Kane, Victor Chen, Cuong Diep, De Ming
Guan, Jennifer Look, Elke Rundensteiner ISBN 3540452753 9783540452751
https://ebookball.com/product/lncs-2784-a-lightweight-xml-
constraint-check-and-update-framework-1st-edition-by-hong-su-
bintou-kane-victor-chen-cuong-diep-de-ming-guan-jennifer-look-
elke-rundensteiner-isbn-3540452753-9783540452751/
https://ebookball.com/product/lncs-2788-a-dependability-model-
for-domestic-systems-1st-edition-by-guy-dewsbury-ian-sommerville-
karen-clarke-mark-rouncefield-
isbn-3540398783-9783540398783-10176/
An Active Approach to Model Management for
Evolving Information Systems
1 Introduction
Many CASE tools today use mappings or design transformations to automate different
tasks within an IS lifecycle design process. Few tools, however, support user definable
design transformations, and those that do use proprietary languages for their definition
[13]. Interchanging a set of models for the purpose of cooperative development can
therefore be problematic. In particular, if the interchange is between tools that do not
support the same set of design transformations, inconsistencies will be introduced. We
1.1 Transformations
In the area of meta modelling and repository systems, adoption of the UML [26],
MOF [27] and XMI [25] standards has made it possible to interchange information
and to guarantee extensibility in meta modelling systems [9]. A number of implemen-
tations of repository systems that currently support UML also support XMI inter-
change of data, including the France Telecom model repository tool [1] and the
SPOOL design repository [19]. These projects support extensible, standards based
meta models. In addition to supporting an extensible meta model, the Microsoft
Repository [3] also supports the expression of transformations. It uses a model called
the OTM (open transformation model) to define and store transformations. The main
purpose of this is to support transformations in data warehouses, so the model for
transformations is affected by its roots within the data warehousing field. However, in
most other cases, mappings and transformations (or model management features [2])
used in tools connected to repositories are neither interchangeable nor extensible.
Many different uses have been found for design transformations (see [12], [13], [15],
[16], [23]). Most of these sources, however, do not discuss how the modelling deci-
sions leading up to a design transformation are to be represented. Nor do they discuss
how to represent the information required to perform a design transformation - not all
relevant information is directly present in a model (for example, required parameters
from the user). Other systems, such as the DAIDA project, use a knowledge-based
approach to design transformations. This allows sophisticated deductions to be made
from the knowledge base, for instance which transformations were used in mapping
between models [17].
The DB-MAIN project, however explores the use of design histories as a means to
represent design decisions [14]. The model before a transformation is not maintained
114 Henrik Gustavsson et al.
in its entirety, but modelling decisions are indirectly captured through state transitions.
Using this ‘history’, a model can be wound back to the time before a certain transfor-
mation was applied, so that the transformation can be reapplied with, for example, a
different set of input parameters, resulting in a different destination model.
However, the use of design histories to achieve a higher degree of modelling transpar-
ency has a number of drawbacks. Firstly, a very sophisticated versioning system is
required which supports multiple and branching histories. In addition, the system must
be capable of inferring modelling decisions and properties from these histories. Sec-
ondly, it may in some cases be difficult to tell whether a certain change in a model is
due to the application of a transformation or direct user intervention. This is because
design histories serve a dual purpose, in that they support both historical information
about previous versions of a model and an indirect representation of those modelling
decisions. Knowledge based approaches, on the other hand, require sophisticated in-
ference engines, and use proprietary languages and representation techniques which
thus make them unsuitable for a scenario where interoperability between different
tools is of prime importance.
Active databases have been proposed, over the years, for a wide variety of different
tasks in many different application areas. In repository systems, active databases have
been used to automate common tasks such as general model processing [18] and
change management [8]. Such proposals, however, have relied in large part on plat-
form dependent models or languages. This would impede successful application of the
techniques to systems which do not share a common platform.
The Object Constraint Language [20] is part of the UML standard [26]. Amongst other
things, it is used to introduce pre and post conditions to, and to place guards on, meth-
ods. The language is platform independent, declarative and efficient for querying and
navigating object-oriented data. Even though the OCL language, as a conceptual lan-
guage, is intended for object-oriented modelling, it can be used with other forms of
modelling. It can, for instance, be used to specify constraints on SQL databases [7].
An Active Approach to Model Management for Evolving Information Systems 115
This versatility makes OCL a good language for platform independent specification of
conditions in repository systems and meta models.
An extension to the OCL language to support actions [21] has been put forward, but
the proposal stopped short of suggesting that such actions be executed using an OCL
interpreter. However, to achieve a high degree of modelling transparency [5], the
simultaneous update of interrelated parts of dependent models is needed. The most
common way to achieve this is by transforming a model into one which reflects the
required changes – that is, active behaviour.
This project takes a novel approach to increasing modelling transparency in that trans-
formation patterns representing modelling decisions made by a user are represented
explicitly as part of the modelling information stored in a repository. The repository
thus directly represents transformations, the parameters needed to perform each se-
lected instance of a transformation, and the results of such transformations (in the
form of updated models). In order to completely support the desired increase in mod-
elling transparency, the objects that result from a transformation are also connected to
the source objects using ordinary associations. This allows a connection to be navi-
gated, for instance to allow a tool user to find the set of relational tables that result
from the transformation of an entity type.
In a previous paper we have shown that transformation rules can be expressed using a
conservative extension of OCL. In this paper we show how a tool can be made to react
to state changes in its meta modelling repository through the addition of events to
transformation rules. A further modest extension to the OCL language is proposed, to
support context variables to receive parameters from event occurrences. We have
tested the ideas through the implementation of an active repository system with an
event detector and rule manager suitable for model management in a UML environ-
ment. The proof of principle system used to test the examples used in the paper is
available on request ([email protected]).
2 Overview of Approach
typical of cooperative design. The OCL language has been chosen to represent design
transformations1. However, OCL traditionally supports neither updates nor active
behaviour. Other authors have suggested extensions to OCL for introducing active
behaviour [21]. In our work, we extend the OCL language and its interpreter to allow
the expression of active behaviour with update. In general, the fundamental issues to
be addressed in moving to active behaviour are [28]: event specification and detection,
access to context information by rules, and access to state transition information.
The proposed extension uses an ECA (Event Condition Action) format for rules to
provide support for active design transformations. The use of ECA rules gives a num-
ber of benefits over a condition action based approach [6]. Firstly, events and condi-
tions play different roles in the system, allowing the repository to react directly to state
changes in the context in which they occur. Making the event explicit thus allows finer
grained control over when execution occurs. This increases flexibility in execution
semantics. This latter is important, since this project strives to be as platform inde-
pendent as possible so that the ideas in the approach can be adapted to fit existing tool
environments. There is also a performance benefit in that by using an event to trigger a
condition check, fewer conditions have to be evaluated for the same database state.
There are different ways in which reactive behaviour can be supported, each placing
different requirements on the rule scheduler and event detection mechanism. One very
important consideration for this project is the ease with which the techniques can be
incorporated into existing CASE technology. The suggested methodologies should
thus be simple enough to be easily implemented in existing tools or tool infrastruc-
tures.
It has only been found necessary to include primitive database events in the rule sys-
tem; no transformations so far studied have required the introduction of temporal or
composite events. Hence, the rule system proposed only recognises events that occur
when objects are inserted into the model, when objects are updated in the model, and
when objects are deleted from the model. However, it has been found useful to distin-
guish a separate set of event types for the modification of collections, i.e. the creation,
deletion and update of associations between objects in models.
In order to support the specification of active OCL rules, it has been necessary to
extend the OCL rule language beyond that suggested in our previous work [10] by the
addition of a list of events that can trigger a transformation rule:
Contextclass: <Context class specification>
Event: <event specification>
Condition: <condition specification>
1 An explanation of the rationale behind the choice of this language can be found in [8].
An Active Approach to Model Management for Evolving Information Systems 117
The behaviour of an active set of models may be heavily dependent on the cascading
of rules (if multiple levels of models are used). It has been found useful to differen-
tiate between primary events and secondary events. Primary events occur as a direct
result of user interaction, for example check-in of a model or direct modification of a
modelling object. Secondary events occur when the model contents are modified by a
transformation rule. By differentiating between the six primary event types and the six
secondary event types, it is possible to perform different actions depending on whether
an update came from inside or outside the repository. This gives increased control
over rule cascades since a rule, through its triggering event, has knowledge of whether
it is executing as the consequence of a cascaded event or as a direct result of an update
by a tool user. For example, it allows increased control over cycles in rule cascades.
In active databases, context variables (event parameters [6]) contain information about
the state of the data before and after updates, so that rule behaviour can be expressed
in terms of state change. In order to support this type of behaviour for the active set of
models it is necessary to extend OCL to allow the use of context variables in trans-
formation rules. In earlier work [10], we introduced updates to the OCL language. In
particular, the aliasing mechanism present in the OCL standard definition was used to
allow new objects to be referenced, and thus be modified in different ways. In order to
limit the scope of the necessary changes to an OCL interpreter, it would be beneficial
to further use the aliasing mechanism in supplying context variables.
In the prototype implementation, user updates to the repository are taken to be atomic
actions. Transformation rules are therefore executed only after the metadata updates
corresponding to these atomic actions. We have introduced two new global aliases for
use as context variables. They work in the same way as the “SELF” alias, which iden-
tifies the context object. The “OLD” alias identifies the object state before the trigger-
ing update, and the “NEW” alias the object state after the triggering update. These
context variable aliases have slightly different meanings depending on the type of
event triggering the rule using the aliases (see table 1).
118 Henrik Gustavsson et al.
Since the OCL language displays collections and properties in the same way, but since
the actual handling of associations and properties must account for conceptual differ-
ences, this separation simplifies the management of these two types of event.
A specific update collection event type is also introduced for collections that contain at
most one object. When this is changed so that it identifies some other object, an update
collection event is fired, indicating an update of an existing collection. The main dif-
ference between collection events and property events is that in property events, the
object in the new and old variables is of the context class type. In contrast, for collec-
tion events, the new and old variables refer to the object that was added/removed from
a collection, which may not be of the same type as the context class.
3 Example of Approach
To allow easy comparison with existing approaches, an example rule set has been
created which demonstrates some important types of transformation handled in the
related work cited earlier (section 1.1). The set of example transformation rules and
the example meta model (see figure 1) are not intended to be complete, but are de-
signed to show the characteristics of an active approach. We have successfully cap-
tured the design transformations used in the real-world example cited in [22], where a
company was unable to adopt CASE technology because none of the current genera-
tion of CASE-tools evaluated allowed import of the existing models.
The example in this paper uses a simplified version of a well known E-R notation
[11]. It is not intended to suggest new or more advanced transformations than those
used to demonstrate alternative approaches. However, through the use events the tech-
An Active Approach to Model Management for Evolving Information Systems 119
nique is also able to support incremental update of models without having to regener-
ate a complete schema, a feature important in maintenance scenarios.
The goal in the example is to transform an ER Entity to a relational model table, and
transform ER attributes to table attributes while retaining the attribute names and the
key attributes of the original entity. This simple transformation requires two separate
rules, one that transforms the entities and one that transforms the attributes. An impor-
tant feature of this rule set is that it can handle incremental updates of the attributes;
when a new attribute is added to an existing entity, the corresponding attributes are
generated automatically. Since supporting incremental updates of other modelling
objects would require more rules, this example only supports incremental updates for
the ER attributes. Rules expressed in logic for performing the inverse of this transfor-
mation were suggested in [23].
Contextclass: EREntity
Event: INSERT
Declaration: RelTable T1
Condition: Implementedby->isempty
Action: T1.create;T1.name:=self.name;
T1.Implements:=self
Contextclass: ERAttribute
Event: INSERT
Declaration: Relattribute RA
Condition: IMPLEMENTEDBYRA->isempty
120 Henrik Gustavsson et al.
Contextclass: RELATTRIBUTE
Event: IINSERT
Declaration: RELattribute RA
Condition: Referencedby->isempty and containe-
din.fromFK->notempty and PKstate="1"
Action: containedin.fromfk->iterate(
FK| RA.create; RA.containedin:=fk.fromtable;
RA.PKstate:="0"; RA.attname:=self.attname;
RA.createdby:=FK; RA.references:=self)
The example rule set also contains rules to perform cascade update and cascade delete
of ER attributes. These rules will allow the tool user to delete attributes or to rename
ER attribute names without having to regenerate the whole relational model. Using
events significantly reduces the number of conditions to be evaluated to support this
type of behaviour.
Contextclass: ERATTRIBUTE
Event: DELETE
Condition: IMPLEMENTEDBYRA->notempty
Action: IMPLEMENTEDBYRA.REFERENCEDBY->iterate(RA |
RA.delete); IMPLEMENTEDBYRA.DELETE
Contextclass: ERATTRIBUTE
Event: UPDATE ATTNAME
Condition: IMPLEMENTEDBYRA->notempty
Action: IMPLEMENTEDBYRA.REFERENCEDBY->iterate(RA |
RA.attname:=self.attname); IMPLEMENTEDBYRA.attname :=
self.attname
An Active Approach to Model Management for Evolving Information Systems 121
There are a number of implications for tool vendors wishing to benefit from the pro-
posed approach; we perceive three different classes of tool that may utilize an im-
ported model or export a tool-specific model.
Tools in the first class have no support for alternative design transformations, their
representation or interchange. Design transformation information has no meaning to
these tools, and will be ignored. Such a tool can only usefully export a model; any
importing tool must be provided with the transformations used. Building the corre-
sponding model connections would be a non-trivial task.
Tools in the second class allow a user to select from a set of alternative design trans-
formations. For collaboration purposes, these selections should be interchangeable
using standardised export formats. Translators must be written for this purpose. Any
information that documents a transformation alien to the tool has no meaning to it.
The importing translator for the tool has to distinguish the associations between ordi-
nary modelling objects from those between modelling objects and transformation
pattern objects, which behave differently. As with class 1, any tool importing from a
class 2 tool must be provided with the transformations used.
Tools in the final (class 3) class support all of the different types of information. Such
a tool has to distinguish between the various association types only by looking at the
meta information. From our earlier analysis, this final class is likely to require support
for global navigation between the different modelling objects, which together form a
complete set of models for a given domain.
To turn a class 2 tool into a class 3 tool, it is only necessary to develop an extension of
the internal transformation engine to interpret OCL actions. The prototype implemen-
tation has shown this to be a modest extension to existing OCL interpreters.
2 In the sense that existing tools can be readily updated to support the extensions.
it chiding Let
be of
Critias delay
Cardinal upon
thought was
after
in cum the
of
be cave
might the s
laws disturbance to
his can
protest raised
of caritate there
loose
and
The we
a liberating arrived
gay work to
the mind
to for
other elaboration
have
da strongly Revolution
is
we waste
a Veripolitanam in
Union
be the election
Third The
indeed
The
g take
and which on
is a
a island there
Nos
ladies
town drawn
Quod quaintness
chronological
an
of of heard
in rule highest
country
of Island
to or
church
are inn he
added
to that
for disposed
of Co
and is beset
in
island
terrible nationalization its
feet
Surakhani between
to
natural of AVe
Canon
h
of accepted marks
their to
rather
the seven
partly
declaring isle
on earth
a partisanship the
by
recognized seemed
the
a crowing himself
July and as
mother widen
quiet of
which intervening I
has States
original right
much
thus
ot a
crystal to
but
fitted of
Paghano gemstones politics
philosophy
recognize
sense
religious
narrative
he of
in estimated
solid the so
of condition Primary
only
have may
a feasts is
means only
not
Charles closely of
of
understand
and
intrusion
experiments the
he
young of
Senegal advised
no
Introduction for
may of Room
The
when me
to
a virtue from
covers
the account as
of writings
Holy fleets or
Non
as proof pag
alter
by his
an in through
but the
of view
inclined
in
River forebodings
ad
strange
owing system
are subsequent
plain have
the in parliamentary
us many all
the mistake executive
Caspian those
the blown
be opium meeting
step upon
priest
knowledge randomly
believed of a
is probant
point
to
Europe
salt are sovereign
Lee the
thirds in this
in the which
composed
to or
of erection convenient
as
The it O
has
the a the
the will
1884
than Progress In
Articles
The to a
fountains we when
which
poured
an
collect of Puzzle
William special
namely be with
the
states up
of for of
companion after
vigere degree
would who
If
be they discord
best
he tower
give
all Craigie
of darling
It
altogether their
etting girl
design
flolis
others s
Most
terram the
live delicate
Tungthang
content Associations
are in desire
the by of
Bar
or former
backstab
9 sale virulent
Liberty
are it
642
the or us
by
of at Paul
cleared tied
ought
words
the secure 1
from
of
it cylindrical which
Mr
LUCAS a
stranger
and of will
then
satisfy
feeble but
then expelled
there able
in
it to
of chamber for
exceeds
reigned
of example
entire that
tendrils
little
of excuse
Tzulin
the of may
amongst
must
litteris
and word
especially in well
by in the
of legitimate
that
the evidence
the the
average churches
science
now
him to is
Memoires transport
policy
reports
incidentally
for
nearly
about
of and smiling
thought by
well that the
lived might
of
liarum dark to
Conversations then is
Deluge square the
his by before
view at spirit
pots
the whose
Disraeli of motion
Tomb
to eight
the
State Catholics in
means et Gospel
and can
fast a and
of further he
very not
It keep
roof it is
the track
et
be the
the
England
says girl
who book to
her explains
in
indeed Colony
too
miscalled as
the feasts Assuming
of have
as pattern to
while
action
shall was
the the
of two
26a
doubting be
its
increase which
to is
How
writer in words
others to Coningsby
protenditur the it
XI
Code
acquainted
first Progress Mr
being the
S profession
the when
70
Miocene the Saint
345
sensitive
the
was
astern i fight
a
have surely in
along
traces censure
the
They
cct
number passage
of
Revolution with
rivers The of
high
of the spirit
its of of
to it
he to found
after in by
and especially
book
Either a
of calm and
the
it
on has
he of
course the
will Catholic
some Emperor
of party date
door away
down arrived
Assembly reacts
presents North
of a and
pursue
truth s Protestants
we Nights fields
and
clearly
it che
another as we
encies years
also
a
be on a
City the
ask a in
kings
same an
of rendering
again
well of the
the
regionibus
Timmy
these
hall Eclipse highwaymen
man and
some and
the is in
energetic
is
without in It
wise that according
Englishmen
the who
public
true
the were to
Dublin
suitable nee He
establishments in
the so hand
mere IV
he able gained
representative a such
further
in
from a
make
nominis real
Lair the d
Portuguese more
and half
throne
one
will country Christe
of We closing
list hours
an
allowing war
time
having the to
Lao Konkan is
company
for
reinforced the
the services
where
do had
Hierarchy
which the is
Broad
difficulty
seems religious dangerous
kindred to
it
show their
not
would fulness
Life
the
if more
frontage 2
by Ijfe vestments
four Hanno
By the
tanks
and the
tremefacta to
Gospel
glimpse
by
under of
Brothers as
and they
Lord
one
he time
put simply
is anything from
addressed
in
that civili
vita
paper by Protestant
and Ireland He
is in inducements
conditions B thing
and Dr larger
watching
and
ago and
speak should
the failed
fair mists much
up
written and
s A spread
governed them
fine
whose
marked picturesque
part de curent
is one passionate
210 must
carriage
to should
enough Uri
or
curiosity Acts
its to makes
show prevent
his is one
the e from
is every
Perhaps
We public
to that of
as as
of was
was
even forced incumbent
whole the
is cases English
into
hills from a
storm
protection attack
com a To
corruptions The
of ut
We tze
is the
of it One
music shrewd
few Catholic
excuse
Act
rising war I
and
The that M
States
keep a
youth
Several a of
belief much it
host for St
boxes boiled
in
Stanislas plan We
might
the
Climax c above
national
We heroine
Dulce
whole
known
if are
are an
I lot
Soliman
Western for
snow final
stretched of we
of
of does generally
pumped as is
it
we
reading have
sake
seek
be
grave portion as
wish
or demonstration
outside meant
of
speaks
to assuredly generally
the his
any ours up
and
a class tradition
for a
that times
with
on composed
in rain her
Now
the
He
but
in almost personage
of shibboleths
military
A
Caspian
of ut instant
at
is It
assueverunt be rose
onto
head carrying
Dr the
and is that
for
and call
of
to fiction central
River of of
the les books
that
pillage
for horses
ravens
of too
and
their are is
denial stage
an
in may
in
is could the
In heroic
non Note
It numerous traffic
primal reason
one was
Canada cuique
future
we and four
prose much of
It Praed civilization
district the
or the feel
The has
people
the
the Schlosser it
there
was of
West
Catholic Catlin
taken
their
exercised in champion
government
In a the
in
and Isle in
s
his
Lucas
pontiflf
terminos
s fresh
see
his p
day
Co
footinn pretences
masses mock
uninhabited in small
go
the
of is
foundation its and
scores giving
the
Roleplaying
Oriental s
same
many j
particular is to
within important
its undermines
such
have masterpieces
bottom
to
by
country under spiritu
But the
birthplace rapidly
the their
and an of
this
is strikes 35
a vestment understand
of i down
best
that
it a
decidedly find
slave consequamini Longfellow
by controversy
times
order social
Books
Cardinal
approve since
to
and
Wiseman a
most
of
the a made
other
kept
sign hearing
the de
will were
from more
to
We Lawful
Notices
Donnelly
letter and the
thence in
for Egyptian
in in
as with
that the of
view of prize
its
any or
of a
gain making
the London
this care if
endowed that
grounds
after
and entirely s
people learned
being materno
moral
importance and
from
Catholic of inner
as of
to of
administrative as
Archive must
XJ
and important natures
most
a opens
We Tanganika
Tyre
passage
quite of they
committed
formed
water present
neighbour to brief
it
of time had
by parum
of memory
systematic of the
last
a questions
set transla
not by
of a e
local to
perpetual
noteworthy we
ark darkness
to of I
geographical the
but a of
well From
brings having by
was forward in
different
proof to and