text:
Date: March 1998. Last edited: $Date: 1999/04/14 21:45:49 $
Status: . Editing status: incomplete first draft. This explains the rationale for XML namespaces and RDF schemas, and derives requirement on them from a discussion of the process by which we arrive at standards.
(These ideas were mentioned in a keynote on "Evolvability" at WWW7 and this text follows closely enough for you to give yourself the talk below using those slides. More or less. If and when we get a video from WWW7 of the talk, maybe we'll be able to serve that up in parallel.)
The World Wide Web Consortium was founded in 1994 on the mandate to lead the Evolution of the Web while maintaining its Interoperability as a universal space. "Interoperability" and "Evolvability" were two goals for all W3C technology, and whilst there was a good understanding of what the first meant, it was difficult to define the second in terms of technology.
Since then W3C has had first hand experience of the tension beween these two goals, and has seen the process by which specifications have been advanced, fragmented and later reconverged. This has led to a desire for a technological solution which will allow specifications to evolve with the speed and freedom of many parallel deevlopments, but also such that any message, whether "standard" or not, at least has a well defined meaning.
There have been technologies dubbed "futureproof" for years and years, whether they are languages or backplane busses. I expect you the reader to share my cynicism when encountering any such claim. We must work though exactly what we mean: what we expect to be able to do which we could not do before, and how that will make evolution more possible and less painfull.
A rule explicit or implcit in all the email-like Internet protocols has always been that if you found a mail header (or something) which you did not understand, you should ignore it. This obviously allows people to add all sorts of records to things in a very free way, and so we can call it the rul of free extension. It has its advatage of rapid prototyping and incremental deployment, and the disadvantage of ambiguity, confusion, and an inability to add a mandatory feature to an existing protocol. I adopeted the rule for HTML when initially designing it - and used it myself all the time, adding elements one by one. This is one way in which HTML was unlike a conventional SGML application, but it allowed the dramatic development of HTML.
The development of HTML between 1994 and 1998 took place in a cycle, fuelled by the tension between the competitive urge of companies to outdo each other and the common need for standards for moving forward. The cycle starts simply simply bcause the HTML standard is open and usable by anyone: this means that any engineer, in any company or waiting for a bus can think of new ways to extend HTML, and try them out.
The next phase is that some of these many ideas are tried out in prototypes or products, using the fact free extension rule that any unrecongined extensiosn will be ignored by everything which does not understand them. The result is a drmatic growth in features. Some of these become product differentiators, during which time their originators are loth to discuss the technology with the competition. Some features die in the market and diappear from the products. Those successful features have a fairly short lifetime as product differetiators, as they are soon emulated in some equivalent (though different) feature in competeing products.
After this phase of the cycle, there are three or four ways of doing the same thing, and engineers in each company are forced to spend their time writing three of four different versions of the same thing, and coping with the software architectural problems which arise from the mix of different models. This wastes program size, and confuses users. In the case for example, of the TABLE tag, a browser meeting one in a document had no idea which table extension it was, so the situation could become ambiguous. If the interpretation of the table was important for the safe interpretation ofthe document, the server would never know whether it had been done, as an unaware client would blithely ignore it in any case. This internal software mess resulting from having to implement multiple models also threatens future deevlopment. It turns the stable consistent base for future development into something fragmented and inconsistent: it is difficult to design new features in such an environment.
Now the marketting pressure is off which prevented discussions, and there is a strong call for the engineers to get around the W3C table, and iron out a common way of doing things. As this happens, a system is designed which puts together the best aspects of each other system, plus a few weeks experience, so everyone is in the end happier with the result. The companies all go away making public promises to implement it, even though the engineering staff will be under pressure to add the next feature and startthe next cycle. The result is published as a common specification opene to anyone to implement. And so the cycle starts again.
This is not the way all W3C activities have worked, but it was the particular case with HTML, and it illustrates some of the advantages and disadvantages with the free extenstion rule.
The HTML cycle as a method of arriving at consensus on a document has its drawbacks. By 1998, there were reasons to change the cycle.The work in the W3C, which had started off in 1994 with several years backlog of work, had more or less caught up, and was begining to lead, rather than trail, developments. The work was seen less as fire fighting and more as consolitation. By this time the spec was growing to a size where the principle of modularity was seriously flaunted. Any new developments clearly had to be seperate modules. Already style information had been moved out into the Cascading Style Sheets language, the programming interface work was a seperate Document Object Model activity, and guidelines for accessibility were tackled by a seperate group.
Inthe future it was clear that we needed somehow to set up a modular system which would allow one to add to HTML new standard modules. At the same time, it was clear that with XML available as a manageble version of SGML as a base for anyone to define their own tag sets, there was likely to be a deluge of application-specific and industry-specific XML based languages. The idea of all this happening underthefree extension rule was frightening. Most applications would simply add new tags to HTML. If we continued the process of retrospectively roping into a new bigger standard, the document would grow without limit and become totally unmanageble. The rule of free extesnion was no longer appropriate.
Now let us compare this situation with the way development occus in the world of distributed computing, specifically remote rpocedure call (RPC) and distributed object oriented systems. In these systems, the distributed system (equivalent to the server plus the client for the web) is viewed as a single software system which happens to be spread over several physical machines. [nelson - courier, etc]
The network protocols are defined automatically as a function of the software interfaces which happen to end up being between modules on different machines. Each interface, local or remote, has a well documented structure, and the list of functions (procedures, methods or whatever) and parameters are defined in machine-processable form. As the system is built, the compiler checks that the interfaces required by one module is exactly provided by another module. The interface, in each version of its development, typically has an identifying (typically very long) unique number.
The interface defines the parameters of a remote call, and therefore defines exactly what can occur in a message from one module to another. There is no free extension. If the interface is changed, and a new module made, any module on the other side of the interface will have to be changed too, or you can't build the system.
The great advantage of this is that when the system has been built, you expect it to work. There is no wondering wether a table is being displayed - if you have called the table module, you know exactly what the module is supposed to do, and there is no way the system could be without that module. Given the chaos of the HTML devleopment world, you can imagine that many people were hankering after the well defined interfaces of the distributed computing technology.
With well-defined interfaces, either everything works, or nothing. This was in fact at least formally the case with SGML documents. Each had a document type definition (DTD) refered to at the the top, which defiend in principle exactly what could and could not be in the document. PICS labels were similar in that thet are self-describing: they actually have a URI atthe top which points to a machine-readable description of what can and can't be in athat PICS label. When you see one of these documents, as when you get an RPC mesaage with an interface number on it, you can check whether you understand the interface or not. Another intersting thing you can do, if you don't have a way of processing it, is to look it up in some index and dynamically download the code to process it.
The existence of the Web makes all this much smoother: instead of inventing arbitrary names for inetrfaces, tyou can use a real URI which can be dereferenecd and return the master definition of the interface in real time. The Web can become a decentralised registray of interfaces (languages) and code modules.
The need was clearly for the best of both worlds. One must be able to freely extend a language, but do so with an extension language which is itself well defined. If for example, documents which were HTML 2.0 plus Netscape's version of tables version 2.01 were identified as such, mcuh o the problem of ambiguity would have been resolved, but the rest ofthe world left free to make their own table extensions. This was the goal of the namespaces work in XML.
To be able to use the namespaces work in the extension of HTML, HTML has to transition from being an SGML application (with certain constraints) to being an XML based langauge. This will not only give it a certain ease of parsing, but allow it to build on the modularity introduced by namespaces.
In fact, already in April of 1998 there was a W3C Recommendation for "MathML", defined as as XML langauge and obviously aimed at being usable in the context of an HTML document, but for which there was no defined way to write a combined HTML+MathML document. MathML was already waiting for XML namespaces.
XML namespaces will allow an author (or authoring tool, hopefully) to declare exactly waht set of tags he orshe is using in a document. Later, schemas should allow a browser to decide what to do as a fall back when finding vocabulary which it does not understand.
It is expected that new extensions to HTML be introduced as namespaces, possibly languages in their own right. The intent is that the new languages, where appropriate, will be able to use the existing work on style sheets, such as CSS, and the existing DOM work which defines a programming interface.
Language mixing is an important facility, for HTML, for the evolution of all other Web and application technology. It must allow, in a mixed labguage document, for both langauges to be well defined. A mixed langage document is quiote analogous to a program which makes calls to two runtime libraries, so it is not rocket science. It is not like an RPC message, which in most systems is very strongly ytped froma single rigid definition. (An RPC message can be represented as a structured document but not, in general, vice-versa)
Language mixing is a realtity. Real HTML pages are often HTML with Javascript, or HTML plus CSS, or both. They just aren't declared as such. In real life, many documents are made from multiple vocabularies, only some of which one understands. I don't understand half the information in the tax form - but I know enough to know what applies to me. The invoice is a good example. Many differet coloured copies of the same document used to serve as a packing list, restocking sheet, invoice, and delivery note. Different parts of a company would understand different bits: the financial dividion woul dcheck amounts and signatures, the store would understand the part numbers, and the sales and marketting would define dthe relationship betwene the part numbers and prices.
No longer can the Web tolerate the laxness which HTML and HTTP have been extended. However, it cannot constrain itself to a system as rigid as a classical disributed object oriented system.
The note on namespaces defines some requirements of a language framework which allows new schmata to be developed quite independently, and mixed within one document. This note elaborates on the sorts of things which have to be possible when the evolution occurs.
You may notice than nowhere in the architecture do XML or RDF specify what language the schema should be written in. This is because much of the future power of the system will lie in the power of the schema and related documents, so it isimportant to leave that open as a path for the future. In the short term, yo can think of a schema being written in HTML and english. Indeed, this is enough to tie the significance of documents written in the schema to the law of the land and mkae the document an effective part of serious commercial or other social interaction. You can imagine a schema being in a sort of SGML DTD language which tells a computer program what constraints there are on the structure of documents, but nothing about their meaning. This allows a certain crude validity check to be made on a document but little else.
Now let us imagine further power which we could put into a schema language.
A crucial first milestone for the system is partial understanding. Let's use the scenario of an invoice, like the scenario in the "Extensible languages" note. An invoice refers to two schemata: one is a well-known invoice schema and the other a proprietory part number schema. The requirement is that an invoice processing program can process the invoice without needing to understand the part description.
Somehow the program must find out that the invoice is from its point of view just as valid as an invoice with the details fo the part description stripped out.
One possibility is to mark the part description as "optional" on the text. We could imagine a well-known way of doing this. It could be done in the document itself [as usual, using an arbitrary syntax:]
<item> <partnumber>8137498237</> <optional> <xml:using href="http://aeroco.com/1998/03/sy4" as="A">
<a:partdesc> ... <a:partdesc> </xml:using>
</opional> </item>
There are problems with this. One is that we are relying on the invoice schema to define what in invoice is and isn't and what it means. It would be nice if the designer of the invoice could say whether the item should contain a part description of not, or whether it is possible to add things into the item description or not. But in general if there is something to be said we like to allow it to be said anywhere (like metadata). But for the optionalness to be expressed elsewhere would save the writer of every invoice the bother of having to explicitly.
The other more fundamental problem is that the notion of "optional" is subjective. We can be more precise about "partial understanding" by saying that the invoice processing system needs to convert the document which contains things it doesn't understand into a document which it does completely understand: a valid invoice. However, another agent may which to convert the same detailed invoice into, say, a delivery note: in this case, quite different information would be "optional".
To be more specific, then, we need to be able to describe a transformation from one document to another which preserves "valididy" in some sense. A simple form of transformation is the removal of sections, but obviously there can be all kinds of level of transformation language ranging from the cudest to theturing complete. Whatever the language, statement that given a document x, that some f(x) can be deduced.
In practice, this suggest that one should leave the actual choice of the transformation language as a flexibility point. However, as with most choices of computer language, the general "principle least power" applies:
When expressing something, use the least powerful language you can. |
(@@justify in greater depth in footnote)
While being able to express a very complex function may feel good, the result will in general be less useful. As Lao-Tse puts it, "Usefulness from what is not there". From the point of view of translation algorithms, one usefulness is for them to be reversible. In the case in which you are trying to prove something (such as access to a web site or financial credibility) you need to be able to derive a document of a given form. The rules you use are the pieces of the web of trust and you are looking for a path through the web of trust. Clearly, one approach is to enumerate all the things which can be deduced from a given document, but it is faster to have an idea of which algorithms to apply. Simple ones have input and output patterns. A deletion rule is a very simple case
This is stream editor languge for "Remove "foo" from any string leaving what was on either side". If this rule is allowed, it means that "foo"is optional. @@@ to be continued
Optional features and Partial Understanding
The test of independent invention is a thought experiment which tests one aspect of the quality of a design. When you design something, you make a number of important architectural decisions, such as how many wheels a car has, and that an arch will be used between the pillas of the vault. You make other arbitrary decisions such as the color of the car, the side of the road everyone will drive, whether to open the egg at the big end or the little end.
Suppose it just happens that another group is designing the same sort of thing, tackling the same problem, somewhere else. They are quite unknown to you and you to them, but just suppose that being just as smart as you, they make all the same important archietctural decisions. This you can expect if you believe hat these decisions make logical sense. Imagine that they have the same philosophy: it is largely the philosophy which we are testing. However, imagine that they make all the arbitrary decisions differently. They complement bit 7. They drive on the other other side of the road. They use red buoys on the starbord side, and use 575 lines per screen on their televisions.
Now imagine that the two systems both work (locally), and being usccessful, grow and grow. After a while, they meet. Suddenly you discover each other. Suddenly, people want to work across both systems. They want to connect two road systems, two telephone systems, two networks, two webs. What happens?
I tried originally to make WWW pass the test. Suppose someone had (and it was quite likely) invented a World Wide Web system somewhere else with the same principles. Suppose they called it the Multi Media Mesh (tm) and based it on Media Resource Identifiers(tm), the MultiMedia Transport Protocol(tm), and a Multi Media Markup Language(tm). After a few years, the Web and the Mesh meet. What is the damage?
(see also WWW and Unitarian Universalism)
Obviously we are looking for the latter option. Fortunately, we could immediately extend URIs to include "mmtp://" and extend MRIs to include "http:\\". We could make gateways, and on the better browsers immediately configure them to go through a gateway when finding a URI of the new type. The URI space is universal: it covers all addresses of all accessible objects. But it does not have to be the only universal space. Universal, but not unique. We could add MMML as a MIME type. And so on. However, if we required all Web servers to synchronise though one and only one master lock server in Waltdorf, we would have found the Mesh required synchronisation though a master server in Melbourne. It would have failed.
No system completely passes the ToII - it is always some trouble to convert.
As the Web becomes the basis for many many applications to be build on top of it, the phenomenon of independent invention will recur again and again. We have to build technology so as to make it easy for systems to pass the test, and so survive real life in an evolving world.
If systems cannot pass the TOII, then we can only achieve worldwide interoperability when one original design has originally beaten the others. This can happen if we all sit down together as a worldwide committee and do a "top down"design of the whole thing before we start. This works for a new idea but not for the automation of something which, like pharmacy or trade, has been going on for centuries and is just being represented in the Semantic Web. For example, the library community has had endless trouble trying to agree on a single library card format (MARC record) worldwide.
Another way it can happen is if one system is dropped completely, leading to a complete loss of the effport put into it. When in the late 1980s Europe eventually abandoned its suite of ISO protocols for networking because they just could not interwork with the Internet, a huge amount of work was lost. Many problems, solved in Europe but not in the US (including network addresses of more than 32 bits) had to be solved again on the Internet at great cost. Sweden actually changed from driving on the left to driving on the right. All over the world, people have changed word processor formats again and again but only at the cost of losing access to huge amounts of legacy information. The test of independent invention is not just a thought experiment, it is happening all the time.
So now let us get more specific about what we really need in the underlying technology of the Semantic Web to allow systems in the future to pass the test of independent invention.
Our first assumption is that we will be smarter in the future. This means that we will produce better systems. We will want to move on from version 1 to version 2, from version n to version n+1.
What happens now? A group of people use version 4 of a word process and share some documents. One touches a document using a new version 5 of the same program. Oen of the other people tries to load it using version 4 of the software. The version 4 program reads the file, and find it is a version5 file. It declares that there is no way it can read the file,as it was produced in the future, and there is no way it can predict the future to know how to read a version 5 file. A flag day occurs: everyone in the group has to upgrade immediately - and often they never even planned to.
So the first requirement is for a version 4 program to be able to read a version 5 file. Of course there will be some features in version 5 that the version 4 program will not be able to understand. But most of the time, we actually find that what we want to achieve can be done by partial understanding - understanding those parts of the document which correspond to functions which exist in version 4. But even though we know partial understanding would be acceptable, with most systems we don't know how to do even that.
The philosophical assumption that we may not be smarter than everyone else (a huge step for some!) leads us to realise that others will have gret ideas too, and will independently invent the same things. It forces us to consider the test of independent invention.
The requirement for the system to pass the ToII is for one program which we write to be able to read somehow (partially if not totally) data written by the program written by the other folks. This simple operation is the key to decentralised evolution of our technology, and to the whole future of the Web.
So we have deduced two requirements for the system from our simple philosophical assumptions:
We are we with the requirements for evolvability so far? We are looking for a tecnology which has free but well defined extension. We want to do it by allowing documents to use mixed vocabularies. We have already found out (from PICS work for example) that we need to be abl eto know whether extension vocabulary is mandatory or can be ignored. We want to use the Web for any registry, rather than any central point. The technology has to be allow an application to be able to convert the output of a future version of itself, or the output of an equivalent program written indpendently, into something it can process, just by looking up schema information.
Now let us look at the world of data on the Web, the Semantic Web, which I expect we expect to become a new force in the next few years. By "data" as opposed to "documents", I am talking about information on the Web in a form specifically to aid automated processing rather than human browsing. "Data" is characterised by infomation with a well defined strcuture, where the atomic parts have wel ldefined types, such as numbers and choices from finite sets. "Data", as in a relational database, normally has well defined meaning which has rarely been written down. When someone creates a new databse, they have to give the data type of each column, but don't have to explain what the field name actually means in any way. So there is a well defined semantics but not one which can be accessed. In fact, the only time you tells the machine anything about the semantics is when you define which two columns of different tables are equivalent in some way, so that they can be used for example as the basis for joining the two databases. (That the meaning of data is only defined relative to the meaning of other data is of course quite normal - we don't expect machines to have any built in understanding of what "zip code" might mean apart from where you can read it and write it and what you can compare it with). Notice that what happens with real databases is that they are defined by users one day, and they evolve. They are rarely the result of a committee sitting down and deciding on a set of concepts to use across a company or an industry, and then designing the data schema. The schema is craeted on the fly by the user.
We can distinguish two ways in which tha word "schema" has been used:
Syntactic Schema: A document, real or imagined, which constrains the structure and/or type of data. (pl.: Schemata). |
Semantic schema: A document, real or imagined, which defines the infereneces from one schema to another, thus defining the semantics of one syntactic schema in terms of another. |
I will use it for the first only. In fact, a syntactic schema dedfines a class of document, and often is accompanied by human documentation which provides some rough semantics.
There is a huge amount ("legacy" would unfairly suggest obsolescence) of data in relational databases. A certain amount of it is being exported onto the web as virtual hypertext. There are many applications which allow one to make hypertext views of difeferent aspects of a database, so that each server request is met by performing adatabse query, and then formatting the result as a report in HTML, with appropriate style and decoration.
Information about information is interesting in two ways. Firstly, it is interesting because the Web society desperately needs it to be able to manage social aspects of information such as endorsement (PICS labels, etc), ownership and access rights to information, privacy policies (P3P, etc), structuring and cataloguing information and a hundred otehr uses which I will not try to ennumerate. This first aspect is discussed elsewhere. (See Metadata architecture about general treatment of metadata and labels, and the Technology and Society domain for overveiw of many of the social drivers and related projects and technology)
The second interest in metadata is that it is data. If we are looking for a language for putting data onto the Web, in a machine understandable way, then metadata happens to be a first application area. Also, because metadat ais fundamental to most data on eth web, it is the focus of W3C effort, while many other forms of data are regarded as applications rather than core Web archietcure, and so are not.
Suppose for example that you run a server which provides online stock prices. Your application which today provides fancy web pages with a company's data in text and graphs (as GIFs) could tomorrow produce the same page as XML data, in tabular form, for machine access. The same page could even be produced at the same URL in two formats using content negotiation, or you could have a typed link between the machine-understandable and person-understandable versions.
The XML version contains at the top (or soemewhere) a pointer to a schema document. This poiner makes the document "self-describing". It is this pointer which is the key to any machine "understanding" of the page. By making the schema a first class object, in other words by giving its URL and nothing else, we are leaving the dooropen to many possibilities. Now it is time to look at the various sorts of schema document which it could point to.
Computer languags can be classified into various types, with various capabilities, and the sort we chose for the schema document, and information we allow the schema fundamentally affects not just what the semantic web can be but, more importantly, how it can grow.
The schema document can, broadly, be one of the following:
We'll go over the pros and cons of each, because none of these should be overlooked, but some are often way better than others.
This may sound like a silly trivial example, but like many trival examples, it is not silly. If you just name your schema somewhere in URI space, then you have identified it. This deosn't offer a lot of help to anyone to find any documentation online, but one fundamental function is possible. Anyone can check compatability: They can compare the schema against a list of schemata they do understand, and return yes or no.
In fact, they can also se an idnex to look up information about the schema, including ifnromation about suitable software to download to add understanding of the document. In fact this level is the level which many RPC systems use: the interface is given a unique but otherwise random number which cannot be dereferenced directly.
So this is the level of machine-understanding typical of distributed ocmputing systems and should not be underestimated. There are lot sof parts of URI space you can use for this: yo might own some http: space (but never actually serve the document at that point) , but if you don't, you can always generate a URI in a mid: ro cid: space or if desperate in one of the hash spaces.
The next step up from just using the Schema identifier as a document tyope identifier is to make that URI one which will dereference to a human-readable document. If you're a computer, big deal. But as well as allowing a strict compatiability test (test for equality of the schema URI), this also allows human beings to get involed if ther is any argument as to what a document means. This can be signifiant! For example, the schema could point to a complete technical spec which is crammed with legalese about what the document does and does not imply and commit to. At the end of the day, all machine-understandable descriptions of documents are all very well, but until the day that they bootstrap themselves into legality, they must all in the end be defined in terms of human-readable legalese to have social effect. Human legalese is the schema language of our society. This is level 2.
Now we move into the meat of the schema system when we start to discuss schema documents which are machine readable. Now we are starting to enable some machine understanding and automatic processing of document types which have not been pre-programmed by people. Ça commence.
The next level we consider is that when your brower (agent, whatever) dereferences the namespace URI, it finds a schema which defines the structure of the document. (This is a bit like an SGML Doctument type Definition, DTD). It allows you to do everything which the levels 1 and 2 allowed, if it has sufficient comments in it to allow human arguments to be settled.
In addition, a system which has a way of defining structure allows everyone to have one and only one parser to handle all manner of documents. Any document coming across the threshold can be parsed into a tree.
More than that, it allows a document o be validated against allowed strctures. If a memeo contains two subject fields, it is not valid. This is one fo the principal uses of DTDs in SGML.
In some cases, there maybe another spin-off. You can imagine that if the schema document lists the allowed structrue of the document, and the types (and maybe names) of each element, then this would allow an agent to construct, on the fly, a graphic user interface for editing such a document. This was the intent with PICS rating systems: at least, a parent coming across a new rating system would be be given a a human-readable description of the various parameters and would be able to select personal preferences
The next step in the power of schema languages it so be able to distinguish optional extensions from mandatory extensions. This is the simplest thing one can do to allow the crudest form of partial understanding. It breaks out of the rule that any extension can be ignored. There has been a long series of attempts to add this distinction to HTTP, without a lot of success, as it is nota very exciting feature by itself. However, for many extensions it is essential. There will always be somethings which you really want to be ignorable - little comments which most software can happily throw away, such as assing birthday greetings to a check. There will always be some extensions which are obsolutely not optional - such as extending a check to work in a currency otehr than US dollars.
With this small addition, we now reach a major goal for evolvability: the ability for a version 1 program to read a version 2 file. This can be done by making the version 2 language a superset of the version 1 language, but labelling the new vocabulary as optional or not in the schema (or in schema information in the document). The version 1 program can throw away all optional version 2 features, and only give up if the version 2 document really does use a feture which must be understood but isn't understood by version 1 programs.
Sometimes software engineers will solve a problem with the most powerful tool available. The top of the list is the large set of all Turing complete langages (basically, programming languages). The great thing about a real prgramming language is that there is nothing you can in theory do with any computer which you can't write a program to do. It is powerful.
For example, using a complete programming language allows you to write a complex program to convert from one manufacturer's dtaa format to another - for exaple from "Word" to "Wordperfect" or between two standards such as GIF to PNG.
You an imagine that on the web, linked from the schemas of various formats were programs, written in commonly understodd languages such as Java, to do such conversions. This provides another great goal of evolvabilty: to convert data between specs designed quite independently.
However, there is a cost in using this level. The conversion program becomes a black box. because a powerful possibly complex language is used, in general the actual operation of the program becomes impossible to trace: the program is regarded as a "black box" with an input and an output. Ideed, software engineering encourages program modules being regarded as black boxes which perform to a specification, but which one does not open up.
This means the program has to be run once on the whole document or not at all. There is a huge difference between this and a set of schema information which defines the mapping betwen elements of two languages which are both written in the same framework, and can in fact be converte


text:
Impress.ly offers efficient yet in-depth control of the design of your site. The design features that can be changed are detailed here:
- Skins: A skin is a complete design package for your site. Select a different skin to activate a completely different set of design changes in your site.
- Navigation: Navigation refers to the icon layout of your Home page and the behaviour of these icons.
- Background: Change the background (color/image) of the homescreen. The colors will be automagically adjusted according to the colors of the new background.
- Header: Change the way the top part of the homescreen looks. Use the site name, logo or none of these to create the best looking site.
- Colors: Select a color palette for your site that matches your background.
- Font: The Header font is used for your site title on the homescreen, the Menu font is used for the items on the homescreen and the Body font is used for the rest of the texts.
- Shape: Change the shape of design flourishes used in your site.
- Animation: Change the way animations will be used in your site and what kind of animations you prefer.
To make design changes to your site, follow these instructions.
- Run through the first steps of creating your site. Add extra content before making design changes to make sure any changes to design are final.
- Once you've created the site and added content, find the Style tab in the left vertical menu.
- Decide which aspects of your design you'd like to change. (Refer to the list above to see which aspects you might like to change.)
- Making design changes is easy. Play around with the different options in each category to create your ideal site.

subset: commoncrawl


text:
5.19. Client: Scripting
Use the vpnd script. Only you may need to modify it a little. Make the following changes:
Change the variables at the top to match your setup. Most should be just fine as they are, but you can change them should you need to.
Line 27: add the local and remote IP addresses before $PPP_OPTIONS
Line 31: Change this line, and the two after it to set routes for your internal nets.
5.19.1. Keeping it running
While bash scripts are generally stable, they have been known to fail. In order to make sure that the vpnd script keeps running, add an entry to the client's crontab that runs the check-vpnd script. I run mine every 5 minutes or so. If vpnd is indeed running, check-vpnd doesn't use much CPU.


text:
JERUSALEM – A House Republican report released this week on the Obama administration's response to the Sept. 11, 2012, Benghazi terror attack is missing one essential piece that could help to answer many of the questions raised in the report.
That piece is the alleged illicit activities transpiring inside the U.S. facilities that were attacked.
The 46-page report by five committees of the Republican-led House says the White House scrubbed terrorism and al-Qaida from talking points and misled the American public by blaming the attack on an obscure YouTube film.
The report further questions why the White House falsely claimed the U.S. facilities were targeted in unplanned, popular street protests while it was known to the government almost immediately that the Benghazi mission and nearby CIA annex were attacked by militants in a premeditated fashion.
One key question of the congressional probe centers on why the State Department chose to reduce security at the U.S. Benghazi mission and to deny multiple requests for more security assistance.
TRENDING: Hunter Biden rips Republicans probing family's alleged corruption
The report rejects State Department claims that funding was the reason for the security reductions.
States the report: "It is clear that funding – or a lack thereof – is not the reason for the reductions in security, as Deputy Assistant Secretary for Diplomatic Security Lamb testified and as emails reviewed by the Committees attest.
"Moreover, a lack of funding would not have been at issue with respect to the rejection of the request to extend the deployment of the [U.S. Military Security Support Team], as that team was provided via the Defense Department at no expense to the State Department."
A key accusation in the report alleges the White House generated talking points for the public that "excluded details about the wide availability of weapons and experienced fighters in Libya, an exacerbating factor that contributed to the lethality of the attacks."
The report does not mention that the weapons and fighters may actually be the reason for the coordinated assaults on the U.S. facilities. According to Middle Eastern security officials, the U.S. mission was allegedly used to help coordinate arms and other aid to the jihadist-led rebel; insurgencies in Libya and in Syria.
The U.S. mission's alleged role in arming the rebels, as first exposed by WND, may help to answer many of the questions in the probe, including why the White House did not want to draw attention to al-Qaida's role in the attacks.
It also could explain why security was reduced as the compound. An increased security presence at the U.S. mission would have drawn attention to the shabby, nondescript building that was allegedly being used for such sensitive purposes.
WND has filed numerous reports quoting Middle East security officials who described the mission in Benghazi as a meeting place to coordinate aid for the rebel-led insurgencies in the Middle East, including the transfer of weapons to rebels.
Two weeks after the Benghazi attack, WND also broke the story that murdered U.S. Ambassador Christopher Stevens himself played a central role in recruiting jihadists to fight Bashar al-Assad's regime in Syria, according to Egyptian security officials.
In November 2012, Middle Eastern security sources further described both the U.S. mission and nearby CIA annex in Benghazi as the main intelligence and planning center for U.S. aid to the rebels that was being coordinated with Turkey, Saudi Arabia and Qatar.
Many rebel fighters are openly members of terrorist organizations, including al-Qaida.
Among the tasks performed inside the Benghazi facility was collaborating with countries, most notably Turkey, on the recruitment of fighters – including jihadists – to target Assad's regime, the security officials said.
Stevens served as a key contact with the Saudis to coordinate the recruitment by Saudi Arabia of Islamic fighters from North Africa and Libya, Egyptian security officials told WND. The jihadists were sent to Syria via Turkey to attack Assad's forces, said the security officials.
The officials said Stevens also worked with the Saudis to send names of potential jihadi recruits to U.S. security organizations for review. Names found to be directly involved in previous attacks against the U.S., including in Iraq and Afghanistan, were ultimately not recruited by the Saudis to fight in Syria, said the officials.
White House officials previously denied aiding arms shipments to the rebels.
However, confirming WND's exclusive reporting for over a year, the New York Times last month reported that since early 2012, the CIA has been aiding the Arab governments and Turkey in shopping for and transporting weapons to the Syrian rebels.
Previously, multiple establishment news media reports described the U.S. role in helping to arm the Libyan rebels attacking the regime of Moammar Ghadaffi. At the same time it was widely reported that al-Qaida groups were among the Libyan rebels.


text: 179A.1 ROOKHOPE stands in a pleasant place, If the false thieves wad let it be; But away they steal our goods apace, And ever an ill death may they die! 179A.2 And so is the men of Thirlwa nd Williehaver, And all their companies thereabout, That is minded to do mischief, And at their stealing stands not out. 179A.3 But yet we will not slander them all, For there is of them good enough; It is a sore consumed tree That on it bears not one fresh bough. 179A.4 Lord God! is not this a pitiful case, That men dare not drive their goods to t fell, But limmer thieves drives them away, That fears neither heaven nor hell? 179A.5 Lord, send us peace into the realm, That every man may live on his own! I trust to God, if it be his will, That Weardale men may never be overthrown. 179A.6 For great troubles theyve had in hand, With borderers pricking hither and thither, But the greatest fray that eer they had Was with the Men of Thirlwa nd Williehaver. 179A.7 They gatherd together so royally, The stoutest men and the best in gear, And he that rade not on a horse, I wat he rade on a weil-fed mear. 179A.8 So in the morning, before they came out, So well, I wot, they broke their fast; In the [forenoon they came] unto a bye fell, Where some of them did eat their last. 179A.9 When they had eaten aye and done, They sayd some captains here needs must be: Then they choosed forth Harry Corbyl, And Symon Fell, and Martin Ridley. 179A.10 Then oer the moss, where as they came, With many a brank and whew, One of them could to another say, I think this day we are men enew. 179A.11 For Weardale men is a journey taen; They are so far out-oer yon fell That some of thems with the two earls, And others fast in Barnard castell. 179A.12 There we shal get gear enough, For there is nane but women at hame; The sorrowful fend that they can make Is loudly cries as they were slain. 179A.13 Then in at Rookhope-head they came, And there they thought tul a had their prey, But they were spyd coming over the Dry Rig, Soon upon Saint Nicholas day. 179A.14 Then in at Rookhope-head they came, They ran the forest but a mile; They gatherd together in four hours Six hundred sheep within a while. 179A.15 And horses I trow they gat But either ane or twa, And they gat them all but ane That belanged to great Rowley. 179A.16 That Rowley was the first man that did them spy; With that he raised a mighty cry; The cry it came down Rookhope burn, And spread through Weardale hasteyly. 179A.17 Then word came to the bailifs house, At the East Gate, where he did dwell; He was walkd out to the Smale Burns, Which stands above the Hanging Well. 179A.18 His wife was wae when she heard tell, So well she wist her husband wanted gear; She gard saddle him his horse in haste, And neither forgot sword, jack, nor spear. 179A.19 The bailif got wit before his gear came That such news was in the land; He was sore troubled in his heart, That on no earth that he could stand. 179A.20 His brother was hurt three days before, With limmer thieves that did him prick; Nineteen bloody wounds lay him upon; What ferly wast that he lay sick? 179A.21 But yet the bailif shrinked nought, But fast after them he did hye, And so did all his neighbours near, That went to bear him company. 179A.22 But when the bailiff was gathered, And all his company, They were numberd to never a man But forty [or] under fifty. 179A.23 The thieves was numberd a hundred men, I wat they were not of the worst That could be choosed out of Thirlwa nd Williehaver, . . . . 179A.24 But all that was in Rookhope-head, And all that was i Nuketon Cleugh, Where weardale men oertook the thieves, And there they gave them fighting eneugh. 179A.25 So sore they made them fain to flee, As many was a out of hand, And, for tul have been at home again, They would have been in iron bands; 179A.26 And for the space of long seven years, As sore they mighten a had their lives; But there was never one of them That ever thought to have seen their wives. 179A.27 About the time the fray began, I trow it lasted but an hour, Till many a man lay weaponless, And was sore wounded in that stour. 179A.28 Also before that hour was done, Four of the thieves were slain, Besides all those that wounded were, And eleven prisoners there was taen. 179A.29 George Carrick and his brother Edie, Them two, I wot, they were both slain; Harry Corbyl and Lennie Carrick Bore them company in their pain. 179A.30 One of our Weardale men was slain, Rowland Emerson his name hight; I trust to God his soul is well, Because he Fought unto the right. 179A.31 But thus they sayd: Well not depart While we have one; speed back again! And when they came amongst the dead men, There they found George Carrick slain. 179A.32 And when they found George Carrick slain, I wot it went well near their Heart; Lord, let them never make a better end That comes to play them sicken a part! 179A.33 I trust to God, no more they shal, Except it be one for a great chance; For God wil punish all those With a great heavy pestilence. 179A.34 Thir limmer thieves, they have good hearts, They nevir think to be oerthrown; Three banners against Weardale men they bare, As if the world had been all their own. 179A.35 Thir Weardale men, they have good hearts, They are as stif as any tree; For, if theyd every one been slain, Never a foot back man would flee. 179A.36 And such a storm amongst them fell As I think you never heard the like, For he that bears his head so high, He oft-times falls into the dyke. 179A.37 And now I do entreat you all, As many as are persent here, To pray for [the] singer of this song, For he sings to make blithe your cheer.


text:
Dr. Conrad Murray Found Guilty of Involuntary Manslaughter of Michael Jackson
A jury found Michael Jackson's doctor guilty of involuntary manslaughter in the 2009 death of the King of Pop.
Dr. Conrad Murray appeared stone-faced as the verdict was read Monday in a Los Angeles courtroom. The 58-year-old doctor, who is to be sentenced November 29, is facing up to four years in prison. He could also lose his medical license.
Jackson's sister LaToya screamed out upon hearing the verdict, while his crying mother, Katherine, was consoled by her son, Jermaine Jackson.
Murray's supporters looked somber over the news, with one shaking her head back and forth, mouthing the word "no."
Jackson fans who had gathered outside the courtroom burst into applause and cheered as the verdict, "Guilty!," was announced.
The decision was reached after less than nine hours of deliberation. The prosecution asked for Murray to be remanded into custody immediately. "He is now a convicted felon," prosecutor David Walgren said.
Defense lawyer Ed Chernoff argued that he is not danger to the community before Murray was escorted out of the courtroom by the Sheriff.
Jackson died on June 25, 2009. The complete story of his death finally emerged during the six-week trial. It was the tale of a tormented genius on the brink of what might have been his greatest triumph with one impediment standing in his way -- extreme insomnia.
Testimony came from medical experts, household employees and Murray's former girlfriends, among others.
The most shocking moments, however, came when prosecutors displayed a large picture of Jackson's gaunt, lifeless body on a hospital gurney and played the sound of his drugged, slurred voice, as recorded by Murray just weeks before the singer's death.
Jackson talked about plans for a fantastic children's hospital and his hope of cementing a legacy larger than that of Elvis Presley or The Beatles.
"We have to be phenomenal," he said about his "This Is It" concerts in London. "When people leave this show, when people leave my show, I want them to say, `I've never seen nothing like this in my life. Go. Go. I've never seen nothing like this. Go. It's amazing. He's the greatest entertainer in the world."'
Throughout the trial, Jackson family members watched from the spectator gallery, fans gathered outside with signs and T-shirts demanding, "Justice for Michael," and an international press corps broadcast reports around the world. The trial was televised and streamed on the Internet.
Prosecutors portrayed Murray as an incompetent doctor who used the anesthetic propofol without adequate safeguards and whose neglect left Jackson abandoned as he lay dying.
Murray's lawyers sought to show the doctor was a medical angel of mercy with former patients vouching for his skills. Murray told police from the outset that he gave Jackson propofol and other sedatives as the star struggled for sleep to prepare for his shows. But the doctor said he administered only a small dose on the day Jackson died.
Lawyers for Murray and a defense expert blamed Jackson for his own death, saying the singer gave himself the fatal dose of propofol while Murray wasn't watching. A prosecution expert said that theory was crazy.
Murray said he had formed a close friendship with Jackson, never meant to harm him and couldn't explain why he died.
The circumstances of Jackson's death at the age of 50 were as bizarre as any chapter in the superstar's sensational life story.
Jackson was found not breathing in his own bed in his rented mansion after being dosed intravenously with propofol, a drug normally administered in hospitals during surgery.
The coroner ruled the case a homicide and the blame would fall to the last person who had seen Jackson alive -- Murray, who had been hired to care for the singer as the comeback concerts neared.
Craving sleep, Jackson had searched for a doctor who would give him the intravenous anesthetic that Jackson called his "milk" and believed to be his salvation. Other medical professionals turned him down, according to trial testimony.
Murray gave up his practices in Houston and Las Vegas and agreed to travel with Jackson and work as his personal physician indefinitely.
For six weeks, as Jackson undertook strenuous rehearsals, Murray infused him with propofol every night, the doctor told police. He later tried to wean Jackson from the drug because he feared he was becoming addicted.
Jackson planned to pay Murray $150,000 a month for an extended tour in Europe. In the end, the doctor was never paid a penny because Jackson died before signing the contract.
During the last 24 hours of his life, Jackson sang and danced at a spirited rehearsal, reveling in the adulation of fans who greeted him outside. Then came a night of horror, chasing sleep -- the most elusive treasure the millionaire entertainer could not buy.
Testimony showed Murray gave Jackson intravenous doses that night of the sedatives lorazepam and midazolam. Jackson also took a Valium pill. But nothing seemed to bring sleep.
Finally, Murray told police, he gave the singer a small dose of propofol -- 25 milligrams -- that seemed to put him to sleep. The doctor said he felt it was safe to leave his patient's bedside for a few minutes, but Jackson was not breathing when he returned.
Witnesses said he was most likely dead at that point.
What happened next was a matter of dispute during the trial. Security and household staff described Murray as panicked, never calling emergency services but trying to give Jackson CPR on his bed instead of the firm floor.
A guard said Murray was concerned with packing up and hiding medicine bottles and IV equipment before telling him to call emergency services. Prosecutors said Murray was distracted while Jackson was sedated, citing Murray's cell phone records to show he made numerous calls.
Authorities never accused Murray of intending to kill the star, and it took eight months for them to file the involuntary manslaughter charge against him. It was the lowest possible felony charge involving a homicide.
There was no law against administering propofol or the other sedatives. But prosecution expert witnesses said Murray was acting well below the standard of care required of a physician.
They said using propofol in a home setting without lifesaving equipment on hand was an egregious deviation from that standard. They called it gross negligence, the legal basis for an involuntary manslaughter charge.
The defense team countered with its own expert who presented calculations suggesting that Jackson gave himself the fatal dose.
In closing arguments, the prosecutor said the mystery of what happened behind the closed doors of Jackson's bedroom on the fatal day probably would never be solved.
Fox News' Lee Ross and the Associated Press contributed to this report.
Read more: http://www.foxnews.com/entertainment...#ixzz1d7tlVP3i


text:
In the spirit of creativity and experimention, I've come up with this idea for a simple, but I hope, delicious rice salad. It would be briliant for a summer buffet, or served as a side dish. I know it's not exactly summer yet- or even really spring: as I write I'm looking out on to a cold, wet and miserable London Saturday morning.
I was playing around with flavour combinations the other day, and discovered that prawn and leeks make an excellent match when combined with the aniseedy tastes of fennel. Here's how to make it:
Chop up some leeks (giviing them a rinse and removing the tougher outer skin bits first) and sweat them gently in a saucepan with some butter. It's probably going to work best if the leeks are chopped up into small pieces. I also find that leeks go brown very quickly, so you need to watch these like a hawk. Try and keep that lovely, fresh verdant green colour. You could of course parboil the leeks first (plunging them very quickly into boiling water and rinsing off under a freezing cold tap) which should help to set the colour.
Into the hot pan goes some fennel seeds and then some good quality prawns. I used smallish frozen prawns, which, of course, are pre-cooked, so just need heating through after they have been defrosted. Check the seasoning and add sea salt and black pepper. Set to one side.
Boil rice in the usual way. I used Uncle Ben's Long Grain rice, which has had the starch removed, and won't go mushy. This is a good thing. Combine the rinsed rice with the leeks, prawn and fennel seeds. Mix in a simple vinagrette (a third olive oil, groundnut oil, a splash of wine or cider vinegar or lemon juice could be just the ticket) and serve cold. A garnish ('orrible word!) of chopped dill would work well with the fish and fennel.


text:
Search through more than 50,000 user-created Webmixes to add to your account. You can get all updates from the original creator or you can claim the Webmix as your own!
Number of followers
"I know that I received this gift for a higher purpose and to seek the truth. It is simply my role to bring this energy to the world--Mahendra Kumar Trivedi
Mahendra Trivedi amassed a collection of over 4,000 scientific studies in many life sciences and material sciences and also has several dozens of publications in leading international peer-reviewed sc
Mr. Trivedi have an inherent intelligence that treats each recipient and specimen uniquely. In one particular study at the California Pacific Medical Center Research Institute,
Hi!!! I am John, did Ph. D. from GCU, USA and researching on Biofield Treatments.
Research and studies on Biofield effect and Alternative energy healing.
Follow Mahendra Trivedi and study his disciplinary works in chemistry , molecular biophysics and biochemistry , materials science , agriculture , medicine .
Mahendra Trivedi having a collection of over 4,000 scientific studies in agriculture, livestock, biotechnology, microbiology, materials science, genetics, cancer and human health.
Mahendra Trivedi has the unique ability to harness the energy from the universe and transmit it to anywhere on earth, infusing it into living organisms and nonliving materials to optimize their potent
No description
Mahendra Trivedi is recognized throughout the world for his ability to transmit a powerful form of energy known as the Trivedi Effect®. The experiences of over 200,000 individuals throughout the world
Master of energy transformation, Mr. Mahendra Trivedi is one of the most famous spiritual healers/leaders. He has the higher level of consciousness. Commonly known as the Trivedi Effect.
Characterisation of Physical, Spectral and Thermal Properties of Biofield treated Resorcinol by Mr. Mahendra Kumar Trivedi


text:
Art has exceeded our expectations in every important area. Specifically, he is professional, knowledgeable, and has integrity. His professionalism has shown from day 1. He arrives early, always communicates well, and knows the greater San Diego markets well. He is incredibly knowledgeable about home sales and purchases. My wife and I both have long standing careers in finance so real estate isn't terribly far from our field of knowledge. However, Art consistently demonstrates he can provide with a better solution to every issue or goal we have had. He knows the financing components. He understands the proper value of a home. He communicates well with the other parties. Art has steered us clear of much more than what he's encouraged us to consider. For such a large financial decision that is refreshing for us. Art has had plenty of opportunities to close a deal with us, earlier than has actually happened. We have noticed a drastically different pressure from previous agents we had met with in years past. Art's integrity is easy to notice when working with him. This, above everything else, is why we have worked with Art to buy two homes and sell one. And we will work with him as long as he's in the business because it has been that important of an influence for us.
west2water http://www.zillow.com/profile/Gregg-Neuman/Reviews/?review=4707394 December 28, 2018


text:
Staying Competitive in the Extraordinary New Orleans Music Scene
What's Working with Cam Marston
Release Date: 11/26/2018
What's Working with Cam Marston
The NFL attracts elite athletes. and think they have what it takes. Timaje is preparing for NFL Day where scouts will look him over. Chancellor is preparing to join a college football team where he expects his skills to shine. They both have lots of support in their corner, they're doing the work to ready themselves for the tests they'll soon get, and their attitudes point to success. And, for what it's worth, they can now count on me being in their corner, too. But...it's a long, narrow road ahead. Show Sponsors: Find Cam Marston's book - What Works: The Ten Best Ideas from...
info_outline Nick Bloom is the THE Guy Across the World When it Comes to Work from Home Trends and Its Impact on the WorkplaceWhat's Working with Cam Marston
is an economist at Stanford. He began long before they became a thing with Covid. Nick gives me the final word on whether work from home is profitable for companies, how it impacts creativity, and what most organizations are doing now that employees are insisting on a work from home environment. He also shares that NOT commuting to work saves a ton of time for all workers and an addiitonal 18 minutes for women. Why? Gotta listen... . Show Sponsors: Find Cam Marston's book - What Works: The Ten Best Ideas from the First Two-Hundred Episodes on . To get the Top 3 Tips of...
info_outline Applying a Resilience Mentality to Our Business. Author Amy Morin tells us how.What's Working with Cam Marston
Amy Morin made a name for herself with a blog that caught fire followed by a Ted Talk that caught fire. In both instances she wrote and spoke about what mentally strong people DON'T do. Avoid these pitfalls, she says, and you'll deal with life's inevitable adversity much better. In today's show I ask her to apply this mental framework to work, business, customers, and employees and she offers fantasitc advice. Show Sponsors: Find Cam Marston's book - What Works: The Ten Best Ideas from the First Two-Hundred Episodes on .
info_outline Hazardous Waste Disposal - Ted Reese of Cadence Environmental Energy Explains How It's DoneWhat's Working with Cam Marston
When huge chemical containers are cleaned at chemical plants, what happens to the left over hazardous sludge? What's done with the excess from some cosmetic overruns? What about those piles of tires we used to see stacked up behind old tire shops? is president and CEO of . His company destroys wastes that contain energy value by feeding it into long rotary kilns at cement plants that operate at above 2600 degrees Fahrenheit. It's all high in carbon which reduces fossil fuels needed to generate the heat. The resulting product, now harmless, becomes part of the ready made cement we use to...
info_outline Myth v Reality in the EV Car Battery World. A Chat with the Leadership of E-Mobility and TERREPOWERWhat's Working with Cam Marston
Are electric car batteries an environmental disaster like some would have you think? Or are they God's gift to planet earth as others would have you think? I speak with Maria Caballero, President of E-Mobility, a division of TERREPOWER and , President of TERREPOWER, a division of BBB Industries. TERREPOWER takes used EV batteries and remanufacture them for resale. The execs say that, yes, there is an environmental cost to creating them, like there is for all things, but the benefit of running a car with no emissions outweights their cost. They also do electric storage tied to solar panels....
info_outline Aaron Beam Was Head of Accounting at Healthsouth When He Decided the Fudge the Numbers. It Was the Beginning of His and Healthsouth's Downfall.What's Working with Cam Marston
says it was his boss' drive for weath that put pressure on him to fudge the numbers. Aaron admits he liked the wealth that Healthsouth had generated for him, too. But that moment in his boss' office when things got heated about missing the quarterly numbers, Aaron says he should have said No. His inaction in that moment has shaped his life since. Show Sponsors: Find Cam Marston's book - What Works: The Ten Best Ideas from the First Two-Hundred Episodes on .
info_outline The New Research on Tactics for Leading The Millennial Generation. Dr Kevin McGarry explains.What's Working with Cam Marston
Dr. is the CEO of . His research has put him at the forefront of understanding, managing, and guiding the Millennial generation. The focus of much debate over the years, the Millennials remain the most vexxing generation in the workplace today. With a background in leadership in financial services, McGarry's research has led him to developing for management and leadership that have proven helpful in the US and abroad. Hint: If they know WHY they're doing something, they're much more likely to buy in. Plus so much more. Discount Code: leadingwithcam . Ebook Link: Show Sponsors: ...
info_outline Creative, Collaborative, and Team Supportive Workspaces. Rebecca Swanner is Workplace Sector Leader of Architectural and Engineering Design Firm HED.What's Working with Cam Marston
The workplace is permanently changed by Covid. Getting team members to return to the office during the work week will require new tactics including mandatory days in the office and a new office design upon arrival. should know. She designed her company's new Los Angeles workspace with the new hybrid work arrangements in mind. She runs Workplace Sector and spends time with her clients learning their challenges, their needs, and their workplace hopes then turns it into reality for her client's workforce. She and I talk about workplace design that fosters collaboration, creativity, the...
info_outline Workforce Challenges Often Triggered by Childcare Issues. Autumn Zellner, CEO of STARS Early Learning Academy, Explains.What's Working with Cam Marston
Childcare was in a crisis before the pandemic. Too many kids. Too few spots. Many people who wanted to work were forced to stay home and care for young children and this burden impacted females much more so than males. Not much has changed since. In fact, it may have gotten worse. Many of the grants and subsidies offered during the pandemic are no longer available. Autumn Zellner runs . She gets multiple calls each day from parents desperate to work and desperate to find a safe place to leave their children during the day. Autumn turns them all away. She wants to grow but the costs of...
info_outline From Less than 100 Kernels in a Freezer to Needing More Land - The Remarkable Story of Bayou Cora Farms.What's Working with Cam Marston
Josh and Jared Higginbotham found just shy of 100 kernals of heirloom corn in a freezer in a barn. They were the last of their grandfather's stash and these brothers decided to plant it and see what happened. Today their non-GMO corn products are purchased across the country from their farm in south Alabama and they're looking for more acreage to try to meet the rising demand. Show Sponsors: Find Cam Marston's book - What Works: The Ten Best Ideas from the First Two-Hundred Episodes on .
info_outlineStaying busy and relevant in the New Orleans music scene isn't easy. It requires talent and commitment because there is always someone in the wings waiting to replace you, especially in New Orleans - one the the nation's busiest and most competitive music scenes. How John "Papa" Gros stays sharp is a lesson for all of us, and how he feeds energy to his bandmates and how he receives their inspiration in the moment is a message we can all benefit from. John knows What's Working because he's doing it every day.
Besides all of this, he may just be the coolest guy I've ever talked to.


text:
Translated by Dr. Hannah Berliner Fischthal
The town of Dąbrowa Górnicza can thank, in part, a very old
community for its name. Old-Dąbrowa was founded hundreds of
years ago, among desolate forests and swamps, on a hill that slopes down to the
valley, Czarna Przemsza. This old Dąbrowa was the
beginning of the contemporary town, which developed in quick tempo, thanks to
the black diamonds underground. It is difficult to determine when the
neighborhood was created since there was no aristocratic manor around which the
community could tie its history. (The name probably derives from the
Dąbrowa forests, where the community was found. By the way, another
neighborhood in the town carries the name of dąbniki ). [Both
names derive from oak in Polish HBF].
The coalmines from the 18th century in Czarna Przemsza did not
develop they way they should have. In the years 1795-1806 the Prussians
exploited the coalmines. Later, in the time of Warsaw's leadership, the
managers, obedient to Napoleon's war, allowed the mines to become disorganized
and neglected. After the Congress of Vienna in 1815, people once again became
interested in the soil, when the Kingdom of Poland was created. Czarist Russia
ruled the Czarna Przemsza. Afterwards, when Stanisław Staszic
of the Kingdom of Poland took over office as Director General of the Division
of Industry, Trade, and Culture, the Polish coalmines were revived. Thanks to
Staszic's work and efforts, a coalmining community was established in
Dąbrowa, and he laid the foundation for the future development of the
entire community, Przemsza. In the second half of the 19th century,
on Staszic's initiative, two coalmines were built (and later fell down):
(a) Reden in Dąbrowa Górnicza, and
(b) Hain in Strzemieszyce.
After 1985 [1895? translator's note], under Staszice's management, new layers of coal were discovered in Dąbrowa. The coalmine Kasaweri and others were established; also in Sielce, Pogoń, Strzemieszyce. In the years 1834/39 the foundry Bankowa was established with funds from the Polish Bank, which in 1831 had taken over the management of textiles in the Kingdom of Poland[1]. Dąbrowa first received town rights in 1916 for industrial development . (Connected to the growth of the population in 1880, the number of residents approximated 6,000; in 1897 14,870, and in 1921 30,871.) The proletarian groups helped to fulfill Dąbrowa Górnicza as a center of revolutionary movement (it participated in the revolution of 1905-06)[2].
In 1889 a school for colliers was opened, which operated until 1905. During the
revolution the courses stopped, but they later resumed and continued until WWI
broke out. In 1919 the school was changed to a trade school for colliers and
foundry workers[3], bearing
Staszic's name.
The Jewish population
In 1931 there were 5,150 Jews in Dąbrowa Górnicza; in 1940 the
number grew to 5,663. Most of them were businessmen, artisans and owners of
small stores and workshops. The first deportation of the Jews to Auschwitz took
place May 1942; the second in June.
[Page 75]
The mass-deportation to Auschwitz occurred in August of the same year. From the
first to the seventh of August 1943, the Hitlerists deported about 3,000 Jews
from Sosnowiec, Będzin, and Dąbrowa Górnicza to Auschwitz.
Approximately 400 Jews were shot while attempting to escape or
(from the Silesian Library in Katowice, translated from Polish).
by Cwi Simchoni
Translated by Dr. Hannah Berliner Fischthal
I first came to Dabrowa as a youth in 1900 when I paid to be a journeyman to
Josel Wilkes. He lived then in Reden in the home of Lejbl Frochtcwajg. He had a
nickname Tsigush [pipe] because of the long one which he always
kept in his mouth, never taking it out, whether he smoked or not. He was an
angry Jew with a bass voice, and strict. In the corridors of the courtyard
stood large crates with papers which his son-in-law Jekele Rozen, who lived
with him, had from his business they were full of tobacco and
cigarettes. No child outside of the family was permitted in these corridors to
play with the little papers, which used to flutter around.
Out of protest, children would take revenge against Tsigush for not allowing them into the courtyard. They used to enter it fearfully, grab a few papers, and run away. Nobody envied the child he would catch committing this sin.
In general, the colony of Reden did not make a homey impression. The main street, from the so-called barracks until Reden, had deep ditches on both sides. When it rained, the water reached to the barracks, where it disappeared. Small, wooden bridges were scattered every few meters so we could go from one sidewalk to another.
In the small streets there were no bridges, and the mud was terrible. In the lower places the mud was a half-meter high. When a wagon with goods got its wheels stuck in the deep mud, several people had to go and help pull it out. On the sides the mud was thin. We had to maneuver and search well where to step. A person could put his foot in the mud and pull it out, minus his boot. That's how it was in the low places where there was no drain for the water. The water remained in the same place, until it dried out.
You could find a prayer minyan at old Rechnic's home on Chochlewka-Zagórcze (street). Whoever wanted to pray in Reden, cut through the coalmine Reden, and pushed his way through to Chochlewka-Zagórcze.
The elderly Rechnic, slightly hunchbacked, was a rich Jew; he kept horses in the colliery Mortimer in Zagórcze. He sat like an innkeeper in his courtyard with his whole family, and all were employed on his ranch.
The large factories with the tall chimneys, the Huta Bankowa, the zinc works Huta Cynkowa, and the coalmine Reden, were not encompassed by walls in those days. From the large ovens, tongues of fire of all colors issued forth. In the dark nights you could see a beautiful photographic mirage.
The entire administration of Dabrowa consisted, in those days, of a village
ruler and a scribe. They were in Reden, located a story above the
pharmacist. On the ground floor of the community building was the prison
(Koze, as it was called). During the time of the Russian
occupation, the koze consisted of two rooms, one for the arrestees
and another for the guard.
[Page 77]
The ruler of the village, Lis that was his name a short man with
a hunchback, a big anti-Semite, endorsed all the anti-Jewish legislation of the
Tsarist government, and looked to catch anybody breaking a rule. If a young man
from another town had no passport, nobody would envy him. Lis quickly denounced
him, and the stranger was imprisoned until he was sent away in a procession of
(from the history of the Jewish community in Dąbrowa-Górnicza)
by Cwi Simchoni
Translated by Dr. Hannah Berliner Fischthal
Our town Dąbrowa is one of the youngest towns in Poland. It grew out of
the hidden, thick forest areas, where thieves loitered on the paths, waiting to
rob their victims.
It was not built in the characteristically antiquated style of other old towns and villages in Poland; it did not have a market area around it, no old castles, no remains of the old Polish battles (which had invited Jews to come to develop trade), no old cemetery, and so on. This is why the town lore is woven with legends of great humanitarian personalities, of large deeds and accomplishments in all areas of society.
Sometime in the 17th and 18th centuries, when the first sprouts of industry became visible, engineers came from Germany and France (engaged through the big capitalistic concerns at the time). They met in the western corner of Poland, in the large forests surrounding the town of Będzin. The goal was to extract, from rich layers of earth of outstanding quality, great treasures of coal and iron. Intensive work was begun to dig out of the depths the precious material used to heat and to drive the machinery of industry.
The classless farmers of the surrounding villages began to stream to various points where new possibilities for work were forming. A new place to live began to be established. The neighboring Jews of Będzin were the first to step over the threshold. They actually named the new place with the name from the brama [gate] of the wall that used to surround Będzin, the remains of which were still visible as of late.
People did not know the names of the Jews who came to Dąbrowa. They were known by the city from which they came. For example: Proszowicer, Jędrzejówer, Szydłowiecer, etc.
The town of Dąbrowa was divided into various neighborhoods which were called colonies. Workers concentrated around every coalmine or factory. They built houses and, with time, constructed larger and smaller streets. In addition, social networks built apartments for their workers and employees, who received apartments in which to live at no cost. In every colony, two or three Jews, artisans or a small businessmen searching for a place to live and to earn a living, would push themselves in.
The largest concentration of Jews lived in the part of town called the Huta Bankowa. Esteemed artisans and employers, Chasidim and progressives, workers and toilers, lived there.
When Hitler, may his name be blotted out, and his hooligans befell Poland
our town suffered the same fate as all the other towns in Poland
it was ruined and everything was eradicated down to the foundation.
[Page 78]
Translated by Lance Ackerfeld
The Dąbrowa city council decided that it is prohibited for any Jew to settle in
this city, except if he had received a license for this beforehand from the
city (Glos Radomski).
In Dąbrowa, like in many other cities in Poland, anti-Jewish riots took place. In Dąbrowa the soldiers carried out beatings and looting, the same soldiers fired at a procession of strikers and after they dispersed them, they looted Jewish shops, and with that they finished their handiwork. In Dąbrowa and the rest of the places an unseen hand was felt, that organized and supervised the riots. In Dąbrowa and Kielce there were threats of riots and the Jews were warned about them before they occurred. The rumors of riots in Dąbrowa made an impression on the Jewish laborers and they did not take any part in procession.
The Jewish weekly Hatzfira dedicated in its 12th
edition (18th of Adar II, 5679) an article about the forecast
of riots against the Jews in the city of Dąbrowa as well, that according to the
indications, these were riots that had been organized ahead of time, that they had
a political intention, and the intention was apparent and clear: to put down the laborers'
strike and the uprising that was seen beforehand, not only by forceful and
violent means, not only by shooting, but also by assisting the riots against
the Jews. The laborer's strike, which was meant to be a strong protest against
the political agenda prevailing in Poland, had been talked about for a long
time. However, the authorities made preparations in order to put down the
insurgence and especially in the Dąbrowa region, in which communist ideology
had been spread amongst the laborers, and it seemed that the owners of the
unseen hand had succeeded, and riots against Jews took place before, during and
after the strike.
The Zionist Histadrut
In spite of the difficult conditions that the Zionist Histradrut had
to work under in our city, the Zionist labor [party] had developed well over the
last period of time. The number of organized members has grown and up to 200
shekalim [Zionist membership fees] have been sold. 4,397
crowns have been collected for the national fund and its institutions, from
which 698 crowns are for the Jews living in the land of Israel. Likewise, the
Zionists in our city endeavor to distribute Jewish newspapers, not only in our
city, but also in nearby cities.
Awremele Lejb Sztorchajn
one of the Mizrachi founders in Dąbrowa |
The Zionist movement is very strong and significant amongst the 500 Jewish families settled here. On the 20th of Tamuz a meeting was held and 2,300 crowns were raised for the Jewish National fund.
On Thursday, the 24th of Tamuz, a wonderful Herzl dinner was held in the Odeon theatre. The hall was appropriately decorated. M. J. Fried from Warsaw appeared as speaker, and enlightened on the spiritual profile of our leader. On the screen there were slides shown from the congress and the settlements in the Land of Israel. The orchestra played some Mendelssohn Bartholdy pieces. The dinner ended with the singing of the Hatikva [Israeli national anthem] amongst an incredible spiritual uplifting. As a token of recognition, the Bet Ha'am [organization] decided to plant five trees in the Herzl forest in the name of the speaker, Mr. Fried. The Tzofim [scouts] planted another three trees in the name of the speaker.
Rabbi Jechiel Rapaport from Andrzejów and Mr. Juda Szczeranski from Warsaw visited our town for a month. This rabbi founded the Mizrachi organization, and many prominent people of the city were members of it. Mr. Szczeranski ran an extensive campaign for the Mizrachi fund and he managed, despite the small number of members, to collect a respectable sum.
On Wednesday, the 1st of Tevet, there was a founding meeting for the Tzirei Mizrachi [Young Mizrachi]. Mr. Chaim Lustiger spoke about the Mizrachi concept and also explained to the assembled gathering about the function of the Tzirei Mizrachi. After the lecture, a committee was elected in which the following people participated: Szlomo Brandys, Szlomo Nusbaum, Chaim Lustiger, Chaim Grajcer and Natan Nusbaum. At the same event a sum of five hundred crowns were collected for the erection of a building in the land of Israel, and the planting of trees in the Herzl forest in the name of our founding member Mr. Chaim Lustiger. Likewise, classes were begun in the themes of bible, Talmud, the Hebrew language and the history of the Jewish people.
The Tzirei Mizrachi in our city held a dinner on the 15th of Shevat. Member, Chaim Lustiger, opened the dinner and members, Chaim Welner (Bedzin), Wajner (Sosnowiec) and Wajnszel lectured in eloquent Hebrew. At the same event a respectable sum of money was collected for the Herzl forest.
It is worth noting, that we thought about holding the dinner in the synagogue, however, the Shlomi Emunei Israel organization [The welfare of Jewish beliefs] influenced the community authorities and didn't allow us to carry out what we'd planned.
On the 1st of Iyar a Mizrachi type cheder [Jewish school] was opened with two departments. There were about 50 pupils. The curriculum was: Torah, the prophets, Mishnah, the Hebrew language, explanation of prayers and secular studies. There was a supervisory committee in charge of the cheder in which the following participated: S. Rabinowicz, J. Frydman, S. Finkelsztajn, J. Welner, A. Waltfrynt and L. Kuchen.
By request of the regional committee in Sosnowiec, on Tuesday we had a general meeting of our organization members on the 16th of Av, in which participated the Rabbi Gaon Menachem-Mendel Landau, may he live long and merry, from Zabrze, and members of the central committee, Mr. Levi Icchak Jungster and Mr. Icchaak Cwi Wajner from Sosnowiec. The hall was completely filled. Mr. Chanoch Gerszon Szpilberg proposed electing the Rabbi Gaon as the chairman, and members of the presidency, Messrs Levi Icchak Jungster, Icchak Cwi Wajner, Jakob Szalom Fiszel, Jakob Frydman, and secretaries J. J. Bach and S. Nusbaum. His proposition was accepted with a prolonged applause. The honorable visiting rabbi opened the meeting with a short speech which had a deep and impression on the gathering. Mr. Levi Ichhak Jungster presented a report on the central committee's activities and encouraged the audience to help the organization in any way they could. His speech was halted several times because of enthusiastic applause. Mr. J. Wajner spoke about the Rabbi Akiva fund. His speech made a great impression on the audience. The chairman suggested a 15 minute break and during this time, another 25 members enrolled. In addition, a respectable sum of money was collected for the Histadrut taxes. Mr. Szpilberg presented a report on the activities of the civic committee. J. Jungster closed the meeting with a short speech and approached the members with a vigorous request that they work with all their power for the Hamizrachi. The meeting ended with the singing of Hatikva. It was decided to plant a garden in the Herzl forest in the name of the Rabbi Gaon from Zabrize, may he live long and merry.
After a lengthy break in the activities of the KKL [Jewish National Fund] in our city, we returned to work. A five member combined committee was elected, in which two of our members participated. The new committee began working with enthusiasm. The rest of the members also devoted themselves to collecting money during Purim. A total of ten thousand marks were collected for the KKL this was the sum of money defined by the central committee of the KKL, and it was four times larger than the sum collected in previous years.
After a short break we went back to work. We called a general members meeting, and member, S. Wajnrajch spoke about the function of Tzirei Mizrachi during the present period. After this, a permanent new committee presented themselves for elections, and they were organized thus: S. Wajnrajch chairman, Ch. Grajcer deputy chairman, Z. Liberman secretary, C. Nusbaum treasurer, J. Sywek the cultural and KKL representative, Naftali Bitner Keren Hechalutz representative and members of the committee: A. C. Wolhendler, S. Brandys, N. Frajman. The new committee immediately began actual work. We are certain, that its function will be satisfactory.
JewishGen, Inc. makes no representations regarding the accuracy of
the translation. The reader may wish to refer to the original material
for verification.
JewishGen is not responsible for inaccuracies or omissions in the original work and cannot rewrite or edit the text to correct inaccuracies and/or omissions.
Our mission is to produce a translation of the original work and we cannot verify the accuracy of statements or alter facts cited.
Dabrowa Górnicza, Poland Yizkor Book Project JewishGen Home Page
Copyright © 1999-2024 by JewishGen, Inc.
Updated 15 Apr 2020 by LA


text:
- Also Known As
- Hot Shots Golf: Out of Bounds
- Number of Players
- 8
- Genre
- Release Date
PlayStation 3
- 18th Mar 2008
- 26th Mar 2008
- 26th Jul 2007
PlayStation Plus Premium (Subscription)
- 13th Jun 2022
- Series
Sorry, no Everybody's Golf: World Tour review yet.
Screenshots 10
Everybody's Golf: World Tour News
News Tee Off with the European PlayStation Store's Golf Sale
Those of you keeping an attentive eye on the PlayStation Store may have noticed that Sony's launched a stealth golf-themed sale on its digital storefront. The scale of the sale might not be the greatest, but there are still some pleasing deals within. Perhaps the biggest steal is Everybody's Golf for Vita, which can be yours for a tempting...
News Hot Shots Golf Finally Gets Move and 3D Support
Out now
After months of waiting, the western versions of Hot Shots Golf: Out of Bounds — also known as Everybody's Golf: World Tour — finally have PlayStation Move and 3DTV support. Our friends iWaggle3D grabbed the patch and have already posted up some first impressions of its motion controls. A word of warning: you have to perform a full...
Feature Must-Have PlayStation 3 Games - James's Picks
Prepare to be surprised
To introduce you to the team we've put together here at Push Square, we asked each team member for two PS3 games they considered absolutely essential. Here, editor James Newton heads to the opposite ends of the PS3 spectrum. Everybody's Golf: World Tour: Also known as Hot Shots Golf: Out of Bounds, this first HD...
About The Game
Developed by Clap Hanz, in conjunction with Sony Computer Entertainment America's Santa Monica Studios, Everybody's Golf: World Tour brings a brand new chapter of the beloved franchise onto PLAYSTATION3 for the first time.
Showcasing high definition graphics along with new, more accurate golf physics, Everybody's Golf: World Tour offers up a new level of immersion to the franchise's signature over-the-top visuals and pick up and play action. Everybody's Golf: World Tour brings an entirely new element of gameplay control by introducing a shot system that focuses on the player's swing instead of a power meter.
Featuring more than 15 zany golfers and caddies, Everybody's Golf: World Tour adds six new courses to the overall challenge, ranging from pitch-and-putt par three layouts to challenging 18-hole configurations. In addition, players will have unprecedented online access with the ability to create tournaments of up to 50 participants, and even access unique downloadable content. With vibrantly detailed courses, wacky new characters, and a wealth of online features, Everybody's Golf: World Tour promises to enter the next generation strokes ahead of the competition.
Crazy Characters and Caddies - Choose from 15 different playable characters and six different caddies, each with their own distinct look and characteristics that embody the fun and spirit of the franchise. Customise characters in a variety of clothing options, and monitor character attributes including power, control, and accuracy.
Downloadable Content - In between rounds, head to the PlayStation Store to download exciting content including playable characters, new courses, clubs, and clothing.
A Variety of Golf Outings - Multiple single-player and multi-player modes of play including VS Mode, Training Mode, Tournament Mode, Stroke Mode, Match Play Mode, and other challenging modes offer a diverse golfing experience for everyone.
Extensive Stat Tracking - Everybody's Golf: World Tour offers a wide range of statistical information that allows players to measure themselves versus the competition. Track game data through each round to compare skills in categories like best average score, driving distance, driving accuracy (fairways hit), greens in regulations, par pace percentage, putting accuracy, average putt length, holes-in-one, and many other stat options.
New Shot System - Focus on the swing and not a power meter. Players will closely monitor takeaway and impact zone, taking into account distance, club selection, and weather. Of course, players may still opt for the traditional shot meter if desired.
Online Action - Customise a tournament and square off with up to 50 others, or create a match with up to eight players and follow the action of each player. Enter the online lobby and customise your character with more than 300 options including hair, masks, clothing, and numerous other entertaining options while sending messages and setting up matches.
Larger Courses and Environments - Strategically play your next shot while taking into account the entire course. Larger playable environments let you play your errant tee shot from a neighboring hole, or take aim at a different fairway and use it as a shortcut to better align the next shot.
Six Immaculate New Courses - Adding to the wide variety of existing courses, Everybody's Golf: World Tour introduces a set of new courses that bring players to unique and dramatic locations including links along the coast, in the desert, among the mountains, and in the woods.
Refined Putting Stroke - A new putting stroke is in place to take player emphasis off the power meter and focus on the beautiful environments that Everybody's Golf: World Tour and the PS3 deliver. The traditional putting stroke is still a selectable option.