Open Source ESBs in Action 1st Edition Tijs Rademakers
Open Source ESBs in Action 1st Edition Tijs Rademakers
Open Source ESBs in Action 1st Edition Tijs Rademakers
Open Source ESBs in Action 1st Edition Tijs Rademakers
1. Download the full version and explore a variety of ebooks
or textbooks at https://ebookultra.com
Open Source ESBs in Action 1st Edition Tijs
Rademakers
_____ Tap the link below to start your download _____
https://ebookultra.com/download/open-source-esbs-in-
action-1st-edition-tijs-rademakers/
Find ebooks or textbooks at ebookultra.com today!
2. We have selected some products that you may be interested in
Click the link to download now or visit ebookultra.com
for more options!.
Activiti in Action Executable business processes in BPMN 2
0 Tijs Rademakers
https://ebookultra.com/download/activiti-in-action-executable-
business-processes-in-bpmn-2-0-tijs-rademakers/
Practical Arduino Cool Projects for Open Source Hardware
Technology in Action 1st Edition. Edition Jonathan Oxer
https://ebookultra.com/download/practical-arduino-cool-projects-for-
open-source-hardware-technology-in-action-1st-edition-edition-
jonathan-oxer/
Open source SOA 1st Edition Jeff Davis
https://ebookultra.com/download/open-source-soa-1st-edition-jeff-
davis/
Open Source Intelligence in a Networked World 1st Edition
Anthony Olcott
https://ebookultra.com/download/open-source-intelligence-in-a-
networked-world-1st-edition-anthony-olcott/
3. Open by design the transformation of the cloud through
open source and open governance First Edition Davis
https://ebookultra.com/download/open-by-design-the-transformation-of-
the-cloud-through-open-source-and-open-governance-first-edition-davis/
Open Source Software Implementation and Management 1st
Edition Paul Kavanagh
https://ebookultra.com/download/open-source-software-implementation-
and-management-1st-edition-paul-kavanagh/
Open Source Development with CVS 3rd Edition Moshe Bar
https://ebookultra.com/download/open-source-development-with-cvs-3rd-
edition-moshe-bar/
Computer Networks An Open Source Approach 1st Edition
Ying-Dar Lin
https://ebookultra.com/download/computer-networks-an-open-source-
approach-1st-edition-ying-dar-lin/
Open Source Approaches in Spatial Data Handling Advances
in Geographic Information Science 1st Edition Brent Hall
https://ebookultra.com/download/open-source-approaches-in-spatial-
data-handling-advances-in-geographic-information-science-1st-edition-
brent-hall/
5. Open Source ESBs in Action 1st Edition Tijs Rademakers
Digital Instant Download
Author(s): Tijs Rademakers, Jos Dirksen
ISBN(s): 1933988215
Edition: 1
File Details: PDF, 6.18 MB
Year: 2008
Language: english
11. v
brief contents
PART 1 UNDERSTANDING ESB FUNCTIONALITY..........................1
1 ■ The world of open source ESBs 3
2 ■ Architecture of Mule and ServiceMix 42
3 ■ Setting up the Mule and ServiceMix environments 72
4 ■ The foundation of an integration solution 111
PART 2 USING ESB CORE FUNCTIONALITIES ..........................153
5 ■ Working with messages 155
6 ■ Connectivity options 194
7 ■ Web services support 243
8 ■ Implementing enterprise-quality message flows 280
PART 3 ESB CASE STUDIES.....................................................317
9 ■ Implementing a case study using patterns 319
10 ■ Managing and monitoring the ESB 358
11 ■ Implementing a process engine in the ESB 393
13. vii
contents
foreword xiii
foreword xvii
preface xix
acknowledgments xxi
about this book xxiii
PART 1 UNDERSTANDING ESB FUNCTIONALITY................1
1 The world of open source ESBs 3
1.1 Why do you need an ESB? 4
Benefits of an ESB 5 ■
Using an ESB from an
application perspective 8
1.2 Explaining the core functionalities of an ESB 12
Location transparency 13 ■
Transport protocol
conversion 14 ■
Message transformation 15
Message routing 16 ■
Message enhancement 17
Security 18 ■
Monitoring and management 19
Core functionality overview 20
1.3 Researching the open source ESB market 21
Demystifying the open source ESB 21 ■
Overview of
open source ESBs 23
14. CONTENTS
viii
1.4 Why did we choose Mule and ServiceMix? 30
Defining selection criteria 30 ■
Assessing the open
source ESBs 31
1.5 Hello world with Mule and ServiceMix 33
Taking a donkey ride with Mule 34 ■ Taking a
JBI dive with ServiceMix 37
1.6 Summary 40
2 Architecture of Mule and ServiceMix 42
2.1 Mule architecture and components 43
Mule components overview 43 ■
Mule endpoints 46
Transformers 48 ■
Routers 50 ■
Component 53
Mule deployment models 54 ■
Mule wrap-up 55
2.2 JBI, the foundation for ServiceMix 56
Service engines and binding components 57
Services and endpoints 59 ■
Normalized message router 60
Service description, invocation, and message exchanges 62
Service unit and service assembly 64 ■
JBI wrap-up 65
2.3 ServiceMix architecture and components 65
ServiceMix overview 65 ■ Routing and transformations
in ServiceMix 67 ■ ServiceMix deployment models 70
ServiceMix wrap-up 71
2.4 Summary 71
3 Setting up the Mule and ServiceMix environments 72
3.1 Three technologies enhancing the ESB functionality 73
Using Spring as an object container 73 ■
XML marshaling
with JiBX 81 ■
Using JMS with the ActiveMQ broker 89
3.2 Preparing the development environment 94
Setting up ESBs, tools, and required libraries 94
Running examples from Eclipse 96
3.3 Inaugurate the Mule environment 98
Writing and configuring the Mule components 99
Running the Mule example 102
3.4 Inaugurate the ServiceMix environment 103
Select the necessary JBI components 103 ■ Configuring
the ServiceMix example implementation 104 ■ Running the
ServiceMix example 109
3.5 Summary 110
15. CONTENTS ix
4 The foundation of an integration solution 111
4.1 Implementing integration logic with Mule 112
Creating a logging solution with Mule 112 ■
Developing a
custom transformer with Mule 115 ■
Integrating Mule
and Spring 117
4.2 Implementing integration logic with ServiceMix 120
Creating a logging service assembly for ServiceMix 120
Creating service units and a service assembly 121
Integrating ServiceMix and Spring 125
4.3 Constructing message flows with an ESB 127
What is a message flow? 128 ■
A message flow case study 130
4.4 Implementing a message flow with Mule 131
Implementing the request flow with Mule 132 ■
Implementing
the response flow with Mule 133
4.5 Implementing a message flow with ServiceMix 138
Implementing the request flow with ServiceMix 138
Implementing the response flow with ServiceMix 142
4.6 Interlude: Spring Integration 148
A quick example with Spring Integration 149
4.7 Summary 151
PART 2 USING ESB CORE FUNCTIONALITIES ................153
5 Working with messages 155
5.1 Routing messages 156
Fixed router 156 ■
Content-based router 158
5.2 Validating messages 170
Validating messages with Mule 171 ■
Validating messages
with ServiceMix 175 ■
An alternative way to perform message
validation using Synapse 180
5.3 Transforming messages 182
Implementing message transformation in Mule 182
Implementing message transformation in ServiceMix 188
5.4 Summary 193
16. CONTENTS
x
6 Connectivity options 194
6.1 File connectivity 196
Mule File transport 196 ■
ServiceMix file transport 198
6.2 Connecting to JMS 202
Connecting Mule to JMS 203 ■
Connecting
ServiceMix to JMS 206
6.3 Connecting to a database using JDBC 209
Connecting Mule to JDBC 210 ■
Connecting ServiceMix
to JDBC 213
6.4 Connecting to mail servers 222
Connecting Mule to POP3 and SMTP 223 ■
Connecting
ServiceMix to POP3 and SMTP 225
6.5 FTP connectivity 229
FTP and Mule 230 ■
FTP and ServiceMix 233
6.6 Connecting to EJB 3 234
Using EJB 3 from Mule 237 ■
EJB 3 and ServiceMix 239
6.7 Summary 242
7 Web services support 243
7.1 Top-down approach web service 244
Java implementation of the web service 250 ■ Implementing a
top-down web service using Mule 252 ■ Implementing a
top-down web service using ServiceMix 256
7.2 Bottom-up approach 259
Bottom-up approach using Mule 260 ■
Bottom-up
approach using ServiceMix 260
7.3 Consuming web services 263
Consuming web services with Mule 263 ■
Consuming web
services using ServiceMix 264
7.4 Web service standards 266
WS-Security 267 ■
Using WS-Security with Mule 267
Using WS-Security with ServiceMix 272 ■
WS-Addressing 274
Using WS-Addressing in Mule 275 ■
Using WS-Addressing
in ServiceMix 277
7.5 Summary 279
17. CONTENTS xi
8 Implementing enterprise-quality message flows 280
8.1 Handling errors in your message flow 281
Error handling with Mule 281 ■
Error handling
in ServiceMix 284
8.2 Securing the ESB environment 288
Authentication and authorization with Mule 288
Authentication and authorization with ServiceMix 302
8.3 Making your message flows transactional 307
Implementing transactional message flows in Mule 309
Implementing transactional message flows in ServiceMix 312
8.4 Summary 316
PART 3 ESB CASE STUDIES...........................................317
9 Implementing a case study using patterns 319
9.1 Introducing a design approach for integration
projects 320
Introducing the Enterprise Integration patterns 320
Analyzing a pattern-based design approach 322
9.2 Introducing a restaurant table reservation case study 324
9.3 Designing the restaurant table reservation solution 325
Designing a publish-subscribe message flow 325 ■ Designing a
filtering and routing message flow 327
9.4 Implementing the case study with Mule and
ServiceMix 328
The Spring and Hibernate building blocks 328 ■
Implementing
the Mule message flow 332 ■
Implementing the ServiceMix
message flow 339
9.5 Testing and deploying the integration solution 352
Using JUnit to test the Mule and ServiceMix flows 352
Deploying an integration solution to a production
environment 356
9.6 Summary 357
18. CONTENTS
xii
10 Managing and monitoring the ESB 358
10.1 System-management Enterprise Integration patterns 359
The Wire Tap pattern 359 ■
The Message Store pattern 363
The Detour pattern 368
10.2 Monitoring using JMX 375
Using JMX to administer Mule 376 ■
Monitoring Mule
using MC4J 380 ■
Mule Galaxy and Mule HQ 382
Using JMX to administer ServiceMix 386 ■
Monitoring
ServiceMix using MC4J 388
10.3 Summary 391
11 Implementing a process engine in the ESB 393
11.1 Introducing the process engine 394
The execution environment for processes 395 ■ Designing
processes for a process engine 397
11.2 A process engine case study: booking a day of scuba
diving 400
11.3 Diving into the messages and services 402
Designing the case study message definitions 403 ■
Serializing
the case study messages to XML with JiBX 405 ■
Setting the
stage for the case study implementation 406
11.4 Implementing a process engine with jBPM and jPDL 411
Orchestrating services with jPDL 411 ■
Implementing the
case study with jBPM and Mule 415
11.5 Implementing a process engine with Apache ODE and
WS-BPEL 426
Orchestrating services with WS-BPEL 426 ■
Implementing the
case study with Apache ODE and ServiceMix 429
11.6 Summary 435
appendix A: ServiceMix 4.0 436
appendix B: Differences between Mule 1.4.x and Mule 2.0.x 441
appendix C: Graphical tool support 445
appendix D: Mule component overview 452
appendix E: ServiceMix component overview 469
appendix F: The Swing test client 477
appendix G: Overview of tools and libraries 481
index 484
19. xiii
foreword
Getting different applications to work together has never been fun. It’s not sexy, the
rewards are limited, and there is no glory. Throughout my career, it seemed as if a stigma
was associated with integration—that it was a dirty job, and you pulled the short straw
if you were working in this area. Personally, I always enjoyed working in integration,
and because enterprises never throw anything away, getting different applications to
work together has become an increasingly essential element of IT.
Things really became interesting when the enterprise service bus (ESB) made its debut.
The concepts on which the ESB is founded have changed over time. Since IBM first
released MQSeries, enterprises have been sold on the benefits of decoupling systems
using point-to-point message queues. When TIBCO brought Rendezvous to the mar-
ket, it expanded the horizons of messaging by introducing the publish-subscribe
model. The Java Message Service (JMS)—born through Sun’s Java Community Process
(JCP)—set out to unify the point-to-point and publish-subscribe messaging models. It
wasn’t long before enterprises required more than just messaging; they also needed a
way to orchestrate messages between systems and perform transformations.
To address this need, major vendors such as IBM, Oracle, and Microsoft built enter-
prise application integration (EAI) brokers that added message brokering and central-
ized transformation engines on top of their existing messaging servers. The problem
with the EAI approach was that it adopted a hub-and-spoke architecture where all data
had to flow through the EAI broker. Although this worked for many applications,
enterprises were soon pushing the boundaries of these systems; it became clear that
something more flexible, scalable, and distributed was required. Enterprises needed
20. FOREWORD
xiv
connectivity, transaction management, security, and message routing, and they needed
to host services that operated on data moving around their systems. The industry
needed the ESB.
With the advance of service-oriented architecture (SOA) in the last several years,
we’ve seen confusion unfold about what SOA really is. One affirmation that has reso-
nated well in the industry is that the ESB is the foundation of SOA. The term SOA cov-
ers a much broader topic than just technology, but we need technologies like ESBs to
realize the benefits of what service orientation has to offer. The ESB provides an
anchor point for many enterprises that are braving the nebulous ocean of SOA mar-
keting, vendor claims, and vaporware. The ESB bridges the gap between old and new.
It acts as a mediator between application integration and service orientation, enabling
enterprises to build new applications and processes from existing technology.
The ESB has gained in popularity because there is a general understanding of what
an ESB is; but if you’re still confused, this book will definitely provide clarity. The
notion of an ESB involves a common messaging bus that is used to communicate
between different systems within an enterprise. Typically, there is a shared messaging
format on the bus, and adapters between the bus and back-end applications translate
data from the proprietary data formats to the shared message bus format. The power
of this model is that applications can share information while being totally decoupled
from one another. Additionally, the ESB provides a common platform for handling
security, transformations, message routing, transactions, and monitoring. This book
does a great job of covering each of these topics and dives deep into the detail of how
to apply these features in the real world.
I founded the Mule project in 2003 because I was frustrated by the proprietary
nature of products available for building ESB solutions. In 2001, I was working as an
architect for a tier-1 investment bank. I was tasked with building a custom ESB-like
solution to integrate hundreds of legacy and custom applications. Back then, the term
enterprise service bus hadn’t been coined (although by 2002, Sonic Software, Fiorano,
and SpiritSoft all staked claim to the term), but what we built was in fact an ESB. At the
time, the technology choices were limited; you used either an application server or a
heavyweight EAI solution that required a huge upfront investment in infrastructure,
money, and human resources. We wanted something lightweight and easy to deploy
and manage. Like many enterprises at the time, we built our own abstraction on top of
JMS. We discovered early on that building our own was an extreme undertaking and a
huge burden on our developers. After that experience, I realized that the industry
needed an open source solution built on open standards.
The open source model is the perfect choice for developing an ESB. More accu-
rately, open source is perfect for integration. After all, ESBs are about surfacing,
manipulating, and moving data between applications. Application integration is com-
plex on many levels. The permutations of applications, protocols, message formats,
environment restrictions, and nuances in the way an application (or even a standard)
has been implemented cause system integrators an unholy amount of grief. No single
22. the pre-existence of a Phœnician or Egyptian colony here before the
Roman times?
214. As a matter of fact, 12th century would be more exact;
nearly all the chief problems of pointed arch construction in
intersecting vaulting having been worked out before the close of that
century.
215. [The domical construction of the vaults of the two great
cisterns erected by Constantine, the Binbirderek, or thousand-and-
one columns, and the Yeri Batan Seraï, both in Constantinople,
suggests that there already existed in the East a method of vaulting
entirely different from that which obtained in Rome, and which may
have been a traditional method handed down even from Assyrian
times.—Ed.]
216. ‘Syrie Centrale: Architecture civile et religieuse du Ier
au VIIme
Siècle. Par le Comte Melchior de Vogüé.’
217. ‘Byzantine Architecture,’ by Texier and Pullan. Folio, London,
1864.
218. De Vogüé, ‘Églises de la Terre Sainte,’ p. 101.
219. For a careful analytical description of the church, see
Professor Willis, ‘Architectural History of the Holy Sepulchre,’ London,
1849.
220. The particulars for these churches are taken from Texier and
Pullan’s splendid work on Byzantine architecture published by Day,
1864.
221. Another very small church, that of Moudjeleia, though under
50 ft. square, seems to have adopted the same hypæthral
arrangement.
23. 222. A great deal of very irrelevant matter has been written about
these “giant cities of Bashan,” as if their age were a matter of doubt.
There is nothing in the Hauran which can by any possibility date
before the time of Roman supremacy in the country. The very
earliest now existing are probably subsequent to the destruction of
Jerusalem by Titus.
223. The constructive dimensions of the porch at Chillambaram (p.
353. History of Indian and Eastern Architecture, 1876.) are very
similar to those of this church: both have flat stone roofs, but in the
Indian, though a much more modern example, there is no arch.
224. These are all given in colours in Texier and Pullan’s beautiful
work on Byzantine architecture, from which all the particulars
regarding this church are taken.
225. A wayside retreat or shelter.
226. A restoration of the church from Procopius’s description, ‘De
Ædificiis,’ lib. i. ch. iv., will be found in Hübsch, ‘Altchristliche
Baukunst,’ pls. xxxii. and xxxiii.
227. See vol. iii., in chapter on Indian Saracenic Architecture.
228. The Renaissance dome which fits best to the church on
which it is placed is that of Sta. Maria at Florence; but, strange to
say, it is neither the one originally designed for the place, nor
probably at all like it. All the others were erected as designed by the
architects who built the churches, and none fit so well.
229. [The apses on each side of central apse are said to be
additions to the original structure. The triple apses in Greek churches
are found, according to Dr. Freshfield (‘Archæologia,’ vol. 44), only in
churches erected subsequent to Justin II. In St. Simeon Stylites and
St. Sergius at Bosra the side apses have been added afterwards.—
Ed.]
24. 230. Strictly speaking, circular with flattened sides, for the
pendentive has a longer radius than half the diagonal of the square.
231. The two eastern cupolas have been raised in Arab times, and
a cylindrical drum inserted with windows pierced in them to give
more light to the interior.
232. There are numerous examples of this class of structure in
North Syria, but whether they are memorials or tombs is not known.
See ‘Reisen Kleinasien und Nord Syria’ by Karl Humann and Otto
Puchstein.
233. [This rule cannot be made a hard and fast one. Procopius
states that in the central dome of the Church of the Apostles,
Constantinople, “the circular building standing above the arches is
pierced with windows, and the spherical dome which over-arches it
seems to be suspended in the air.” In the church of St. Sergius at
Constantinople the walls of the octagon, which are pierced with
windows, are carried up to the vault, and in the church of Sta.
Sophia at Thessalonica the windows are pierced in an upright dome
cylindrical internally. In all these cases, however, there is a marked
distinction between these examples and those of the lofty cylindrical
drums which were employed in the Neo-Byzantine churches. Mr.
Fergusson’s rule, therefore, with these exceptions, may be taken as
absolute.—Ed.]
234. They are found in the Mustaphapacha mosque at
Constantinople dating from 430 A.D., but rebuilt in the 13th century.
235. [It is now considered that the Church of the Holy Apostles
was the original model. This church, rebuilt by Justinian, was pulled
down in 1464 A.D. by Mohammad II. to furnish a site for his mosque.
—Ed.]
236. [This work has lately been undertaken by Messrs. Barnsley
and Schultz, who are preparing their drawings for publication, and
25. hope to follow up the task with a survey of the more important
churches in Mount Athos.—Ed.]
237. ‘Die Kunst in den Athos Kirchen,’ Leipzig, 1890.
238. ‘Athos; or, the Mountain of the Monks,’ by Athelstan Riley,
M.A., 1887.
239. See the photogravure of the interior of the Catholicon at
Dochiariu.
240. ‘Églises Byzantines en Grèce.’
241. ‘Expédition scientifique de la Morée.’
242. There would seem however to have been a revival in the
11th century, possibly a reflex of that which was taking place in West
Europe. And it was during this period that the churches of St. Luke
in Phoeis, the church at Daphné and the churches of St. Nicodemus
and St. Theodore in Athens were erected.
243. C. Texier, ‘Arménie et la Perse.’ 2 vols. folio. Paris.
244. Dubois de Montpereux, ‘Voyage autour du Caucase.’ 6 vols.
8vo. Paris, 1839, 1841.
245. Brosset, ‘Voyage Archéologique dans la Georgie et l’Arménie.’
St. Pétersbourg, 1849.
246. D. Grimm, ‘Monuments d’Architecture en Georgie et Arménie.’
St. Pétersbourg, 1864.
247. Texier gives three dates to this church. In the ‘Byzantine
Architecture,’ p. 174, it is said to be of the 7th, and at p. 4, of the
9th century. In the ‘L’Arménie et la Perse,’ at p. 120, the date is
given as 1243. My conviction is that the first is correct.
248. Flandin and Coste, ‘Voyage en Perse,’ pls. 214, 215.
26. 249. Texier and Pullan, ‘Byzantine Architecture,’ pp. lix., lx.
250. I am a little doubtful regarding the scales of these two
buildings. They are correctly reduced from M. Brosset’s plates. But
are these to be depended upon?
251. Even if it should be asserted that this is no proof that the
inhabitants of these countries were Buddhists in those days, it seems
tolerably certain that they were tree-worshippers, which is very
nearly the same thing. Procopius tells us that “even in his day these
barbarians worshipped forests and groves, and in their barbarous
simplicity placed the trees among their gods.” (‘De Bello Gotico,’
Bonn, 1833, ii. 471.)
252. The principal part of the information regarding these
excavations is to be found in the work of Dubois de Montpereux,
passim.
253. [See paper by Mr. Wm. Simpson in R. I. B. A. Transactions,
vol. vii., 1891.—Ed.]
254. All the plans and information regarding the churches at Kief
are obtained from a Russian work devoted to the subject, procured
for me on the spot by Mr. Vignoles, C.E.
255. The first bay, as shown on plan (Woodcut No. 382), is the
narthex; the five domes come beyond it.
256. The particulars and illustrations of this church are taken from
a paper by Heinrich Keissenberger, in the ‘Jahrbuch der K. K.
Commission für Enthaltung der Baudenkmale,’ 1860. A model of it,
full size, was exhibited at the Paris Exhibition of 1867.
257. [It has been assumed that the Roman basilicas were taken
possession of by the early Christians for their own religious services,
but as Mr. G. G. Scott points out in his ‘Essay on the History of
English Church Architecture,’ “there is no well-authenticated instance
27. of the conversion of any Pagan basilica into a Christian church,
whilst there are abundant examples of Pagan temples converted into
Christian sanctuaries” (see Texier and Pullan’s ‘Byzantine
Architecture,’ pp. 75, 103). Indeed, it is, as Mr. Scott observes, “on
the face of it improbable, if we reflect that the conversion of the
government to Christianity had no tendency to render the existing
basilicas less necessary for legal business, after the peace of the
church, than they had been before that event. Christianity,
unfortunately, could not abolish the litigious instincts of our nature,
and after fifteen centuries of the gospel the legal profession still
flourishes.” The buildings which were rendered useless by the official
recognition of the new faith were not the basilicas but the temples,
the fact being that the class of building known as a basilica (a term
never used by either the writers or architects of Byzantine times),
with its wide central nave and aisles with galleries over them lighted
by clerestory or side windows, and covered with a timber roof,
constituted the simplest and most economical building of large size
which could be constructed to hold a vast assembly of worshippers;
especially as the only features which can be looked upon as having
any architectural pretensions, viz., the columns and their capitals,
could be taken wholesale from temples and other Roman buildings.
The semicircular apse, which alone in the Roman basilica served as a
court of law, became the tribune for the bishop and presbyters.
Mr. Scott is even inclined to assign an earlier and more
independent origin for the basilican form. According to his theory the
germ of the Christian basilica was a simple oblong aisleless room
divided by a cross arch, beyond which lay an altar detached from the
wall. This germ was developed by the addition of side aisles, and
sometimes an aisle returned across the entrance, and over these
upper aisles were next constructed and transepts added, together
with the oratories or chapels in various parts of the building. Mr.
Butler, in his work on ‘The Ancient Coptic Churches of Egypt,’ accepts
this theory, as the churches of Egypt are rich in evidence that
favours it. At the same time, the first great basilica erected by
Constantine, viz., the Vatican (St. Peter’s), and the Lateran, (St. John
28. Lateran), are of too great importance to warrant the suggestion that
their origin should be sought for in the very small though possibly
earlier examples in Egypt or the East.—Ed.]
258. This probably refers to its foundation, for M. Cattaneo, in his
work ‘L’architecture en Italie, 1890,’ judging by its ornamental detail,
places the church in the second half of the seventh century.
259. ‘Antiquités,’ vol. i. pl. 97.
260. Eodem, vol. iv. pl. 67.
261. Mr. Alfred J. Butler’s work, already referred to, has thrown
considerable light on the subject, though, as he was unable to visit
any of the Coptic churches up the Nile, we are still left in doubt as to
the age of the convent near Siout and other buildings. From
comparison of the plans and descriptions given in Denon, Curzon
and Pococke of these buildings, with those in Cairo and Old Cairo,
Mr. Butler ascribes them to the fourth century, that which in fact is
claimed for them as having been founded by Sta. Helena. On this
subject he says, p. 365: “Were there no more of evidence besides to
determine the truth of this tradition, the plan of the Haikal (the
central of the three chapels in a Coptic church) would decide it
beyond question. The persistence with which certain churches are
ascribed to Sta. Helena by a people utterly ignorant of history and
architecture is in itself remarkable, and it is still more remarkable to
find that these churches are always marked by a particular form of
Haikal. Indeed, so regular is the coincidence, that a deep apsidal
haikal with recesses all round it and columns close against the wall
may be almost infallibly dated from the age of Sta. Helena.”
262. The older church has been so altered and ruined by the
subsequent rebuildings that it is extremely difficult to make out its
history. It seems, however, to have been built originally above the
site of an old Mithraic temple, which has recently been cleared out,
and probably before the time of Gregory the Great. It was
29. apparently rebuilt, or nearly so, by Adrian I., 772, and burnt by
Robert Guiscard, 1084. The upper church seems to have been
erected by Paschal, 1099-1118. The question is, to what age do the
frescoes found on the walls of the older church belong? Some of the
heads and single figures may, I fancy, be anterior even to the time
of Adrian; but the bulk of the paintings seem certainly to have been
added between his age and 1084, and nearer the latter than the
former date. If it had not been entirely ruined in 1084 Paschal would
not have so completely obliterated it a century afterwards. A
considerable quantity of the materials of the old church were used in
the new, which tends further to confuse the chronology.
263. Gutensohn and Knapp, ‘Die Basiliken des Christlichen Roms.’
264. Cicero de Legg., ii. 24; Festus, s. v.; Smith’s ‘Dictionary of
Classical Antiquities.’
265. The dates here given generally refer to the building now
existing or known, and not always to the original foundation.
[Mr. G. G. Scott, in his work before referred to (p. 506), after
giving a full quotation from Eusebius of Constantine’s basilica at
Jerusalem, in which he points out that the orientation of primitive
times is the reverse of that which has become general in later times,
continues his enquiry into the evidence afforded by the numerous
early basilicas in Rome itself. Of about fifty churches of early date, in
forty of them the sanctuary is placed at the western end, and of the
remaining ten (one of which is the great church of St. Paolo fuori le
Mura), there are only seven which appear to have retained their
original form, and which have an eastward sanctuary.
The exact orientation of the sanctuary in each case has been
added to the list.—Ed.]
266. ‘Il Vaticano discritto da Pistolesi,’ vol. ii. pls. xxiv. xxv.
267. The new church which superseded this one is described in
the History of the Modern Styles of Architecture, vol. i., page 111,
30. woodcut 45.
268. It should be observed that the dosseret is first found in Italy
in the Church of St. Stefano Rotondo, built 468-482, and is there of
similar design to examples in Thessalonica.
269. ‘L’architecture en Italie du vie au xie
siècle.’ Venice, 1891.
270. ‘Altchristlichen Kirchen nach Baudenkmalen und alteren
Beschreibungen,’ von D. Hubsch. Carlsruhe, 1862.
271. These piers were built in the 12th century, taking the place of
the columns of the original Basilican church of the 9th century, and
the arches date from the same period (Cattaneo).
272. It is now called S. Martino in Cielo d’Oro, from its having
been decided in the twelfth century that the other church in Classe
possessed the true body of the saint to which both churches were
dedicated.
273. A. F. von Quast, ‘Die Altchristlichen Bauwerke von Ravenna.’
274. The basilica Pudenziana at Rome has similar arcades
externally.
275. The twenty-four marble columns are said to have been
brought over from Constantinople, but they were probably obtained
from Greek quarries.
276. [The narthex as shown in Woodcut No. 409 is of much later
date than the church, and has been partially rebuilt on two or three
occasions. It is now (1892) being taken down, and the removal of
the central portion has uncovered the triple window which originally
lighted the nave.—Ed.]
277. “La basilica di San Marco in Venezia,” by Cattaneo, continued
by Boito. Venezia, 1890.
31. 278. Probably owing to its having been utilized to receive the relics
of St. Mark, which were temporarily hidden there.
279. This church, built by Justinian, no longer exists, having been
pulled down in 1464 by Mohammed II. to make way for his mosque.
From the description of it, however, given by Procopius, the plan was
similar to that adopted in St. Mark, being that of a Greek Cross with
central and four other domes. Procopius speaks of the church being
surrounded within by columns placed both above and below,
probably referring to galleries similar to those in St. Sophia of
Constantinople. In St. Mark’s the columns exist in one storey only,
and the main wall is carried up at the back of the aisles to give
increased size inside.
280. Originally, according to M. Cattaneo, his was the vestibule to
the atrium from the south, but it is now blocked up by an altar.
281. [They are shown in the mosaic of the doorway of St. Alipe,
executed at the end of the 13th century, as also the filling in of the
great west window.—Ed.]
282. ‘Dalmatia, the Quarnero and Istria,’ by T. G. Jackson, M.A.
Oxford, 1887.
283. In support of this statement he points out that twice during
Christian times it had been found necessary to raise the floor of the
church. The nave floor, which in 1857 was two steps below that of
the aisles, was raised in 1881 to the same level; but two feet nine
inches below the nave floor before it was raised there existed,
according to Prof. Eitelberger, another mosaic pavement, which must
have been the floor of the first basilica erected, and which was
pulled down by Bishop Euphrasius in 543. This lower pavement
extended also under the three chapels of the confessio, which
suggests that these are part of the first basilica.
284. The same polygonal form is found in the apses of St. Agatha,
St. Apollinare in Classe, St. Apollinare in Nuovo, St. Spirito, and St.
32. Vitale, all in Ravenna, and St. Fosca, Torcello.
285. The apses of two churches, of the 4th and 6th century
respectively, in the island of Paros, are similarly fitted with marble
seats: in the 6th century church there are eight rows, so that the
apse looks like a small amphitheatre.
286. That is on the supposition that the word kirk is derived from
the Latin word “circus,” “circular,” as the French term it, “cirque.” My
own conviction is that this is certainly the case. The word is only
used by the Barbarians as applied to a form of buildings they derived
from the Romans. Why the Germans should employ κυρίου οἶκος,
when neither the Greeks nor the Latins used that name, is a mystery
which those who insist on these very improbable names have as yet
failed to explain.
287. The Tholos at Epidaurus seems to be an exception to this
rule.
288. Isabelle, ‘Édifices Circulaires,’ plates 26 and 27.
289. M. Cattaneo states that it was built by Pope St. Simplice,
468-482.
290. Above the capitals are impost blocks or dosserets, the
earliest known examples of that feature in Italy.
291. [The Vaults over the outer aisle of St. Stefano Rotondo were
built with hollow pots, the remains of which can still be traced in the
outer walls of the 2nd aisle.
Prof. Middleton points out also the existence of rings of earthen
pots in the vault of the tomb of Sta. Helena (Woodcut No. 227), and
also in the vaults of the Circus of Maxentius, on the Via Appia.—Ed.]
292. In this building they now show a sarcophagus of ancient
date, said to be that of Galla Placidia, daughter of Theodosius. She,
however, was certainly buried at Ravenna; but it may be of her time,
33. and in these ages it is impossible to distinguish between baptisteries
and tombs.
293. Frederick Von Osten, ‘Bauwerke in der Lombardei.’
Darmstadt, 1852.
294. By an oversight of the engraver, the vault of the nave, which
ought to be made hexapartite, is drawn as quadripartite. [The nave
was so completely restored in the 14th century as to render doubtful
the original existence of a vault.—Ed.]
295. Étude de l’Architecture Lombarde,’ par F. de Dartein. Paris,
1878.
296. These are incorrectly shown on woodcut. The central pier is
nearly 4 feet wide and carried a transverse rib of the same size and
of two orders.
297. Ferrario, ‘Monumenti Sacri e Profani dell’ I. R. Basilica di S.
Ambrogio,’ Milan, 1824.
298. “Quid dicamus columnarum junceam proceritatem? Moles
illas sublimissimas quasi quibusdam erectis hastilibus contineri
substantiæ qualitate concavis canalibus excavatas vel magis ipsas
æstimes esse transfusas. Ceris judices factum quod metallis
durissimis videas expolitum. Marmorum juncturas venas dicas esse
genitales, ubi dum falluntur oculi laus probatur crevisse miraculis.” In
the above, metallum does not seem to mean metal as we now use
the word, but any hard substance dug out of the ground.
(Cassiodorus, Variorum, lib. vii. ch. 15.)
299. See vol. i. p. 372.
300. ‘The Land of Moab,’ by Dr. Tristram (Murray, 1873), pp. 376
et seqq. [The small triangular marble panels referred to in Murano
are of a very elementary character in their carving, and have
scarcely the importance attached to them by Mr. Fergusson. Besides,
34. the same wall decoration in brickwork is found in the apse of St.
Fosca, Torcello (c. 1008), where, however, the triangular recesses
are simply covered with stucco and painted; being closer to the eye
in Murano, they filled the spaces with incised marble slabs: in other
words, it seems more probable that the slabs were made for the
triangular panels than the converse, which is suggested by Mr.
Fergusson.—Ed.]
301. The typical example of this class is the San Giorgio at Venice,
though it is not by any means the one most like St. Pietro; many
attempts were made before it became so essentially classical as this
(see Woodcut No. 39, Vol. I. in the ‘History of Modern Architecture’).
302. From the boldness of the construction, M. Cattaneo is
induced to place the erection of the building at the end of the 11th
or beginning of the 12th century.
303. The four square towers of San Lorenzo, Milan, and the
circular campanile by the side of the cathedral of Ravenna, are the
earliest examples known, the latter dating from the commencement
of the 5th century.
304. [The tower of St. Satiro at Milan (879 A.D.), is considered by
Cattaneo to be the most ancient campanile known in which the wall
surface is broken up with flat pilasters or vertical bands in relief, and
divided into storeys by horizontal string courses, with ranges of small
blind arches below, carried on corbels, and may be regarded as the
prototype of the most characteristic Lombard towers.—Ed.]
305. ‘History of Medieval Art,’ by Dr. F. M. Reber, translated by J. T.
Clarke. New York, 1887.
306. ‘Dalmatia, the Quarnero and Istria,’ by T. G. Jackson, A.R.A.
Oxford, 1887.
307. Schultz, ‘Denkmäler der Kunst der Mittelalters in Unter-
Italien.’ Folio, 1860.
35. 308. The polygonal form given to the apse externally shows the
direct influence of Byzantine art.
309. The cornice projects 1 ft. 10 in., and consequently overhangs
the base by 13 ft.
310. The present cathedral is only a portion, viz. the transept of a
much vaster edifice which was never completed; but the beautiful
unfinished south front and portions of the gigantic nave and aisles
still exist on the western side of the present cathedral, and the
drawings of it are preserved in the archives of the Duomo.
311. [Since this was written the façade has been completed to
harmonize with the rest, but not in accordance with the original
design, if we may judge by the painting in Sta. Maria Novella, which
shows side gablets similar to those of the cathedral of Siena.—Ed.]
312. If we may trust Wiebeking, the first two bays of the nave
from the front were vaulted in 1588, but the work was suspended till
1647, and completed only in 1659. Yet no difference can be
perceived in the details of the design.
313. The plan and section being taken from two different writers,
there is a slight discrepancy between the scales. I believe the plan to
be the more correct of the two, though I have no means of being
quite certain on the point.
314. ‘Dispareri d’Architettura.’
315. Within the last few years a façade has been added to Sta.
Croce, but about which the less said the better. It is wretched in
design.
36. Transcriber’s Notes
This book often uses inconsistent spelling, particularly
with respect to accents. These were left as printed unless
the author showed a clear preference for one form.
Some presumed printer’s errors have been corrected,
including normalizing punctuation. Page number references
in the Table of Contents were corrected where errors were
found. Further corrections are listed below with the original
text (top) and the corrected text (bottom).
37. every pains has been taken
every pain has been taken p. xxii
progres
progress p. 48
cotemporary
contemporary p. 50
formula
formulæ p. 77
Sedinag
Sedinga Illustration 27.
longed ceased
long ceased p. 219
Nor is is
Nor is it p. 247
ines
lines p. 372
Roumeia
Roumeïa p. 372
Nimes
Nîmes p. 385
Vogüe
Vogüé p. 423
neo-Byzantine
Neo-Byzantine p. 455
iconicon
icon p. 460
38. orginally
originally p. 538
turned the
turned to the p. 558
100 ft. to
100 ft. to 1 in. Illustration 451.
467. Illustration 467 (missing number added)
next
next to p. 596
39. *** END OF THE PROJECT GUTENBERG EBOOK A HISTORY OF
ARCHITECTURE IN ALL COUNTRIES, VOLUME 1, 3RD ED. ***
Updated editions will replace the previous one—the old editions
will be renamed.
Creating the works from print editions not protected by U.S.
copyright law means that no one owns a United States
copyright in these works, so the Foundation (and you!) can copy
and distribute it in the United States without permission and
without paying copyright royalties. Special rules, set forth in the
General Terms of Use part of this license, apply to copying and
distributing Project Gutenberg™ electronic works to protect the
PROJECT GUTENBERG™ concept and trademark. Project
Gutenberg is a registered trademark, and may not be used if
you charge for an eBook, except by following the terms of the
trademark license, including paying royalties for use of the
Project Gutenberg trademark. If you do not charge anything for
copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such
as creation of derivative works, reports, performances and
research. Project Gutenberg eBooks may be modified and
printed and given away—you may do practically ANYTHING in
the United States with eBooks not protected by U.S. copyright
law. Redistribution is subject to the trademark license, especially
commercial redistribution.
START: FULL LICENSE
41. PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK
To protect the Project Gutenberg™ mission of promoting the
free distribution of electronic works, by using or distributing this
work (or any other work associated in any way with the phrase
“Project Gutenberg”), you agree to comply with all the terms of
the Full Project Gutenberg™ License available with this file or
online at www.gutenberg.org/license.
Section 1. General Terms of Use and
Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand,
agree to and accept all the terms of this license and intellectual
property (trademark/copyright) agreement. If you do not agree
to abide by all the terms of this agreement, you must cease
using and return or destroy all copies of Project Gutenberg™
electronic works in your possession. If you paid a fee for
obtaining a copy of or access to a Project Gutenberg™
electronic work and you do not agree to be bound by the terms
of this agreement, you may obtain a refund from the person or
entity to whom you paid the fee as set forth in paragraph 1.E.8.
1.B. “Project Gutenberg” is a registered trademark. It may only
be used on or associated in any way with an electronic work by
people who agree to be bound by the terms of this agreement.
There are a few things that you can do with most Project
Gutenberg™ electronic works even without complying with the
full terms of this agreement. See paragraph 1.C below. There
are a lot of things you can do with Project Gutenberg™
electronic works if you follow the terms of this agreement and
help preserve free future access to Project Gutenberg™
electronic works. See paragraph 1.E below.
42. 1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright
law in the United States and you are located in the United
States, we do not claim a right to prevent you from copying,
distributing, performing, displaying or creating derivative works
based on the work as long as all references to Project
Gutenberg are removed. Of course, we hope that you will
support the Project Gutenberg™ mission of promoting free
access to electronic works by freely sharing Project Gutenberg™
works in compliance with the terms of this agreement for
keeping the Project Gutenberg™ name associated with the
work. You can easily comply with the terms of this agreement
by keeping this work in the same format with its attached full
Project Gutenberg™ License when you share it without charge
with others.
1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside
the United States, check the laws of your country in addition to
the terms of this agreement before downloading, copying,
displaying, performing, distributing or creating derivative works
based on this work or any other Project Gutenberg™ work. The
Foundation makes no representations concerning the copyright
status of any work in any country other than the United States.
1.E. Unless you have removed all references to Project
Gutenberg:
1.E.1. The following sentence, with active links to, or other
immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project
Gutenberg™ work (any work on which the phrase “Project
43. Gutenberg” appears, or with which the phrase “Project
Gutenberg” is associated) is accessed, displayed, performed,
viewed, copied or distributed:
This eBook is for the use of anyone anywhere in the United
States and most other parts of the world at no cost and
with almost no restrictions whatsoever. You may copy it,
give it away or re-use it under the terms of the Project
Gutenberg License included with this eBook or online at
www.gutenberg.org. If you are not located in the United
States, you will have to check the laws of the country
where you are located before using this eBook.
1.E.2. If an individual Project Gutenberg™ electronic work is
derived from texts not protected by U.S. copyright law (does not
contain a notice indicating that it is posted with permission of
the copyright holder), the work can be copied and distributed to
anyone in the United States without paying any fees or charges.
If you are redistributing or providing access to a work with the
phrase “Project Gutenberg” associated with or appearing on the
work, you must comply either with the requirements of
paragraphs 1.E.1 through 1.E.7 or obtain permission for the use
of the work and the Project Gutenberg™ trademark as set forth
in paragraphs 1.E.8 or 1.E.9.
1.E.3. If an individual Project Gutenberg™ electronic work is
posted with the permission of the copyright holder, your use and
distribution must comply with both paragraphs 1.E.1 through
1.E.7 and any additional terms imposed by the copyright holder.
Additional terms will be linked to the Project Gutenberg™
License for all works posted with the permission of the copyright
holder found at the beginning of this work.
1.E.4. Do not unlink or detach or remove the full Project
Gutenberg™ License terms from this work, or any files
44. containing a part of this work or any other work associated with
Project Gutenberg™.
1.E.5. Do not copy, display, perform, distribute or redistribute
this electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1
with active links or immediate access to the full terms of the
Project Gutenberg™ License.
1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if
you provide access to or distribute copies of a Project
Gutenberg™ work in a format other than “Plain Vanilla ASCII” or
other format used in the official version posted on the official
Project Gutenberg™ website (www.gutenberg.org), you must,
at no additional cost, fee or expense to the user, provide a copy,
a means of exporting a copy, or a means of obtaining a copy
upon request, of the work in its original “Plain Vanilla ASCII” or
other form. Any alternate format must include the full Project
Gutenberg™ License as specified in paragraph 1.E.1.
1.E.7. Do not charge a fee for access to, viewing, displaying,
performing, copying or distributing any Project Gutenberg™
works unless you comply with paragraph 1.E.8 or 1.E.9.
1.E.8. You may charge a reasonable fee for copies of or
providing access to or distributing Project Gutenberg™
electronic works provided that:
• You pay a royalty fee of 20% of the gross profits you derive
from the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
45. payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”
• You provide a full refund of any money paid by a user who
notifies you in writing (or by e-mail) within 30 days of receipt
that s/he does not agree to the terms of the full Project
Gutenberg™ License. You must require such a user to return or
destroy all copies of the works possessed in a physical medium
and discontinue all use of and all access to other copies of
Project Gutenberg™ works.
• You provide, in accordance with paragraph 1.F.3, a full refund of
any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.
• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.
1.E.9. If you wish to charge a fee or distribute a Project
Gutenberg™ electronic work or group of works on different
terms than are set forth in this agreement, you must obtain
permission in writing from the Project Gutenberg Literary
Archive Foundation, the manager of the Project Gutenberg™
trademark. Contact the Foundation as set forth in Section 3
below.
1.F.
1.F.1. Project Gutenberg volunteers and employees expend
considerable effort to identify, do copyright research on,
transcribe and proofread works not protected by U.S. copyright
46. law in creating the Project Gutenberg™ collection. Despite these
efforts, Project Gutenberg™ electronic works, and the medium
on which they may be stored, may contain “Defects,” such as,
but not limited to, incomplete, inaccurate or corrupt data,
transcription errors, a copyright or other intellectual property
infringement, a defective or damaged disk or other medium, a
computer virus, or computer codes that damage or cannot be
read by your equipment.
1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except
for the “Right of Replacement or Refund” described in
paragraph 1.F.3, the Project Gutenberg Literary Archive
Foundation, the owner of the Project Gutenberg™ trademark,
and any other party distributing a Project Gutenberg™ electronic
work under this agreement, disclaim all liability to you for
damages, costs and expenses, including legal fees. YOU AGREE
THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE, STRICT
LIABILITY, BREACH OF WARRANTY OR BREACH OF CONTRACT
EXCEPT THOSE PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE
THAT THE FOUNDATION, THE TRADEMARK OWNER, AND ANY
DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE
TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL,
PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE
NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.
1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you
discover a defect in this electronic work within 90 days of
receiving it, you can receive a refund of the money (if any) you
paid for it by sending a written explanation to the person you
received the work from. If you received the work on a physical
medium, you must return the medium with your written
explanation. The person or entity that provided you with the
defective work may elect to provide a replacement copy in lieu
of a refund. If you received the work electronically, the person
or entity providing it to you may choose to give you a second
opportunity to receive the work electronically in lieu of a refund.
47. If the second copy is also defective, you may demand a refund
in writing without further opportunities to fix the problem.
1.F.4. Except for the limited right of replacement or refund set
forth in paragraph 1.F.3, this work is provided to you ‘AS-IS’,
WITH NO OTHER WARRANTIES OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.
1.F.5. Some states do not allow disclaimers of certain implied
warranties or the exclusion or limitation of certain types of
damages. If any disclaimer or limitation set forth in this
agreement violates the law of the state applicable to this
agreement, the agreement shall be interpreted to make the
maximum disclaimer or limitation permitted by the applicable
state law. The invalidity or unenforceability of any provision of
this agreement shall not void the remaining provisions.
1.F.6. INDEMNITY - You agree to indemnify and hold the
Foundation, the trademark owner, any agent or employee of the
Foundation, anyone providing copies of Project Gutenberg™
electronic works in accordance with this agreement, and any
volunteers associated with the production, promotion and
distribution of Project Gutenberg™ electronic works, harmless
from all liability, costs and expenses, including legal fees, that
arise directly or indirectly from any of the following which you
do or cause to occur: (a) distribution of this or any Project
Gutenberg™ work, (b) alteration, modification, or additions or
deletions to any Project Gutenberg™ work, and (c) any Defect
you cause.
Section 2. Information about the Mission
of Project Gutenberg™
48. Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new
computers. It exists because of the efforts of hundreds of
volunteers and donations from people in all walks of life.
Volunteers and financial support to provide volunteers with the
assistance they need are critical to reaching Project
Gutenberg™’s goals and ensuring that the Project Gutenberg™
collection will remain freely available for generations to come. In
2001, the Project Gutenberg Literary Archive Foundation was
created to provide a secure and permanent future for Project
Gutenberg™ and future generations. To learn more about the
Project Gutenberg Literary Archive Foundation and how your
efforts and donations can help, see Sections 3 and 4 and the
Foundation information page at www.gutenberg.org.
Section 3. Information about the Project
Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-
profit 501(c)(3) educational corporation organized under the
laws of the state of Mississippi and granted tax exempt status
by the Internal Revenue Service. The Foundation’s EIN or
federal tax identification number is 64-6221541. Contributions
to the Project Gutenberg Literary Archive Foundation are tax
deductible to the full extent permitted by U.S. federal laws and
your state’s laws.
The Foundation’s business office is located at 809 North 1500
West, Salt Lake City, UT 84116, (801) 596-1887. Email contact
links and up to date contact information can be found at the
Foundation’s website and official page at
www.gutenberg.org/contact
49. Section 4. Information about Donations to
the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission
of increasing the number of public domain and licensed works
that can be freely distributed in machine-readable form
accessible by the widest array of equipment including outdated
equipment. Many small donations ($1 to $5,000) are particularly
important to maintaining tax exempt status with the IRS.
The Foundation is committed to complying with the laws
regulating charities and charitable donations in all 50 states of
the United States. Compliance requirements are not uniform
and it takes a considerable effort, much paperwork and many
fees to meet and keep up with these requirements. We do not
solicit donations in locations where we have not received written
confirmation of compliance. To SEND DONATIONS or determine
the status of compliance for any particular state visit
www.gutenberg.org/donate.
While we cannot and do not solicit contributions from states
where we have not met the solicitation requirements, we know
of no prohibition against accepting unsolicited donations from
donors in such states who approach us with offers to donate.
International donations are gratefully accepted, but we cannot
make any statements concerning tax treatment of donations
received from outside the United States. U.S. laws alone swamp
our small staff.
Please check the Project Gutenberg web pages for current
donation methods and addresses. Donations are accepted in a
number of other ways including checks, online payments and
50. credit card donations. To donate, please visit:
www.gutenberg.org/donate.
Section 5. General Information About
Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could
be freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose
network of volunteer support.
Project Gutenberg™ eBooks are often created from several
printed editions, all of which are confirmed as not protected by
copyright in the U.S. unless a copyright notice is included. Thus,
we do not necessarily keep eBooks in compliance with any
particular paper edition.
Most people start at our website which has the main PG search
facility: www.gutenberg.org.
This website includes information about Project Gutenberg™,
including how to make donations to the Project Gutenberg
Literary Archive Foundation, how to help produce our new
eBooks, and how to subscribe to our email newsletter to hear
about new eBooks.
53. Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade
Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.
Let us accompany you on the journey of exploring knowledge and
personal growth!
ebookultra.com