text:
Shooting Rubberbands at the Stars

Shooting Rubberbands at the Stars is the debut studio album by American alternative rock band Edie Brickell & New Bohemians, released on August 9, 1988, by Geffen Records. The album went 2× platinum in the United States.

"What I Am" was the lead single and big hit from the album, reaching #7 on the Billboard Hot 100. The follow-up single, "Circle", was about strained relationships. Although described by author Brent Mann as "the perfect follow up single to 'What I Am'" and which "had 'smash' written all over it", it stalled at #48 on the Billboard Hot 100 and fared slightly better on the Billboard Mainstream Rock chart, reaching #32. Cash Box said of "Circle" that "The key to this gentle song is Brickell’s breathy intensity. Supported by an acoustic-slanted track, she manages to sell the unusually dark lyric shadings." Another song from the album, "Little Miss S." was inspired by Edie Sedgwick and reached #38 on the Mainstream Rock chart and #14 on the Modern Rock Tracks chart.

Reception
"Shooting Rubberbands at the Stars is almost impossible to be cynical about (I tried)," remarked Time Out, "and the band are so likeable it's almost unreal."

Personnel
The New Bohemians
 * Edie Brickell – vocals
 * Kenny Withrow – guitars
 * Brad Houser – bass
 * Brandon Aly – drums
 * John Bush – percussion

 * with:
 * Paul "Wix" Wickens – keyboards
 * Robbie Blunt – guitars
 * Chris Whitten – drums
 * John Henry – backing vocals

Both Chris Whitten and Paul "Wix" Wickens were/are members of Paul McCartney's band; Whitten from 1989 to 1990 and Wickens from 1989–present.

Production

 * Pat Moran – producer, engineer
 * George Marino – mastering at Sterling Sound (New York City, New York)
 * Barry Diament – CD mastering at Barry Diament Mastering (New York City, New York)
 * Gabrielle Raumberger – art coordinator
 * Terry Robertson – CD design
 * Edie Brickell – cover illustration
 * Mark Abrahams – solo photography
 * Bob Cook – band photography
 * Tracks 6 & 8 published by Geffen Music-Withrow Publishing-Edie Brickell Songs.
 * Tracks 11 & 12 published by Geffen Music-Edie Brickell Songs.
 * All other tracks published by Geffen Music-Strangemind Productions-Enlightened Kitty-Withrow Publishing-Edie Brickell Songs.

title: Shooting Rubberbands at the Stars


text:
Talk:Janwillem van de Wetering

Untitled
This is a near-complete bibliography, in any case not partial anymore. gidonb 14:30, 12 Dec 2004 (UTC)

Still partial
There is no treatment whatsoever of Wetering's status as one of the most influential figures in Western Zen. His seminal, groundbreaking work, "The Empty Mirror", is listed, but not discussed. This is a partial biography. Laodah 17:31, 19 April 2016 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Talk:Janwillem van de Wetering


text:
Talk:Brute-force attack/to do

 * Discussion of TWINKLE and TWIRL
 * Add an overview of suggested hardware designs for key search.
 * Discuss hash collision search; MD5CRK
 * Discuss Time-memory tradeoffs
 * Briefly survey the cracking challenges (RC5, DES etc)
 * Types of attacks
 * Attacks on wireless networks
 * Tools used for brute force attacks

title: Talk:Brute-force attack/to do


text:
Dresden Funicular Railway

The Dresden Funicular Railway (Standseilbahn Dresden) is a funicular in Dresden, Germany, connecting the districts of Loschwitz, near the "Blue Wonder" bridge, and Weisser Hirsch.

The railway is one of two funicular railways in Dresden, the other being the unusual Schwebebahn Dresden, a suspended monorail. Both lines are operated by the Dresdner Verkehrsbetriebe AG, who also operate the city's tram, bus and ferry networks.

History
Although the construction of the line had been discussed and planned since 1873, the permit to build the railway was not issued until 1893. The railway was opened on October 26, 1895, and was originally run by a steam engine.

In 1910 the line was converted to run on electricity, and in 1912 its operation was transferred to the Dresden municipal tramways, whose successors still operate it. During the bombing of Dresden on the 13 February 1945, the lower station of the funicular was destroyed. However the line's cars had been moved for safety into the line's tunnels and survived.

Major renewals took place in 1978 and 1993. On January 6, 2014, the line was again closed for a major refurbishment of both the cars and the line. The refurbishment is expected to be completed by April, 2014 and to cost €350,000.

Operation
The funicular operates between 06:30 and 21:00 on weekdays, and between 09:00 and 21:00 at weekends and public holidays. During operating hours there are between four and six journeys per hour in each direction.

The line has the following technical parameters:

title: Dresden Funicular Railway


text: Category:Rise Against albums

title: Category:Rise Against albums


text:
Category:Etymology

Etymology is the study of the history of words, their origins, and how their form and meaning have changed over time.

title: Category:Etymology


text:
Talk:Coregonus

Old discussions
This is one of those names for which WP's "common name" rule completely breaks down. As FishBase shows, it's simply not the case that "whitefish" and Coregonus are synonymous, despite what the ITIS guy says. Better for us to be careful and use the genus name for precise taxonomy, and common name to route people to possible taxa (if they even have one in mind, "whitefish" often meaning no more than "not a pink fish" :-) ). Stan 14:42, 12 Dec 2004 (UTC)

 * Hmm. That may be.  Wikipedia distinguishes Whitefish from white fish, the fisheries term, which is roughly "not a pink fish"—basically whatever you put in fish sticks or fry to go with chips. (See the "see also" in this page.) I've gotten heat for not being anglocentric enough here, so I try to err on the side of common names—even though I would really prefer all taxa to be under their systematic names with redirects from common names (something I'll never get). Let me get some of these species sorted out a bit more and let's revisit the issue of moving back to Coregonus in a bit. (Coregonus has a history, so it's not a simple move...) —Tkinias 23:00, 12 Dec 2004 (UTC)

 * It occurred to me to consult my big OED, and for "whitefish"/"white-fish"/"white fish" it has the vague not-pink-fish concept as the first definition, #2 is a synonym for beluga, and #3 is Coregonus specifically. Dunno what to make of that... I've come to take a pretty hard line on common names, generally only use them when the consensus is crystal-clear. Interesting contrast between plants and fish - in plants, genera often have agreed-upon common names, and families don't, while in fish most families have common names, while the genera usually don't. Stan 03:40, 13 Dec 2004 (UTC)

 * Interesting. Recall that OED lists definitions purely chronologically, without regard to their commonality in present usage.  Cf. Merriam-Webster, which has:
 * a : any of various freshwater salmonid food fishes (especially of genera Coregonus and Prosopium) b : any of various fishes resembling the true whitefishes c British : any of various market fishes with white flesh that is not oily
 * the flesh of a whitefish especially as an article of food
 * I suspect the meaning of "beluga" is obsolete.

 * Given all this—and that neither OED nor M-W supports the whitefish–white fish distinction, I think a disambig page is in order. I'll make one up and sort it all out when I get a chance.  Thanks for bringing it to my attention. —Tkinias 21:37, 13 Dec 2004 (UTC)

Disambig
I've made Whitefish a disambig page. I hope this is all clearer now. —Tkinias 23:43, 27 Dec 2004 (UTC)

Coregonus ambiguities/corrections
Copied from Talk:WikiProject Fishes

Coregonus There is an odd reference to a submarine at the end of the coregonus article that probably doesn't belong there. I've left it there, but someone might want to have a look.

The reference to blackfin cisco being extinct is incorrect, and is in fact contradicted by the blackfin cisco page. I'll make the correction. The status of this group is problematic. The proliferation of cisco species in the Laurentian great lakes is based on the work of a single researcher and the subject of debate. Some note might be made of that, but since it's all pretty up in the air, maybe not. I'm new to this encyclopedia business.

I will also clean up the capitalized species names in the section.--Peter3 18:28, 3 August 2006 (UTC)

OK. I've just started looking at some other coregonus entries and discovered that the submarine business crops up in other species. Doesn't seem to fit. The lake herring/cisco entry is a bit jumbled, with a bunch of stuff that has nothing to do with the species C. artedi but relates to ciscos generally. The general bits probably belong in the general Coregonus article.--Peter3 18:47, 3 August 2006 (UTC)

I've written entries for kiyi, northern cisco and shortjaw cisco. I also generalized the cisco (fish) entry to the ciscoes and cleaned up some entries that had duplicate or outdated information.Peter3 15:32, 1 November 2006 (UTC)

Inconnu
Hello. I'm new here, but noticed that the FishBase listing is missing Inconnu (Stenodus leucihthys), but there is a Wikipedia entry for Inconnu. I'm basing this upon Lake, River & Sea-Run Fishes of Canada by Frederick H. Wooding.

I thought about editing the page, but got a bit confused about the markup. Then I noticed that the list is according to FishBase, so if it isn't contained there, it shouldn't just be added to that list. However, it would be nice to link in the Wikipedia page for Inconnu to the Coregonus page for completeness.

Derek 15:14, 11 February 2007 (UTC)

Old page history
Some old page history that used to be at the title "Coregonus" can now be found at Talk:Coregonus/Old history. Graham 87 02:17, 24 June 2011 (UTC)

title: Talk:Coregonus


text:
Talk:Business continuity planning

Withdrawn standard referenced
BSI standard 25777:2008 is replaced by ISO 27031:2011 so should reference to that withdrawn standard be removed from the list? I think it causes unnecessary checking for information seekers. Sohannin (talk) 20:43, 6 March 2012 (UTC)

Most recent FAC
I raised the following article once before and I believe the current article has addressed all the objection points raised during the first round:

 * 1) No references - References Added.
 * 2) BCP is not "a methodology to create a manual" - Wording corrected.
 * 3) BCP has a lot of overlaps with the risk management process, but this article doesn't even consider that link. - Referenced in the first paragraph, since this is not an article about Risk Management, risk management doesn't need to be explained.

 * 1) no examples of BCP in real life. - Added
 * 2) No examples of failure of organisations which did not do it and had problems because of it. - Added
 * 3) No examples of failures of organisations which did do it. - Added
 * 4) no comments on risk acceptance and the impossibility of completely protecting against all disasters.
 * 5) extremely focused on small business / office scenario, what about BCP for large factories? Does the BCP methodology not cover that area? - Disagree with this point.  The BCP process is applicable to any type of activity, as long as the organization classifies a non-office function like distribution as "critical".  I think this is clear.
 * 6) what about other ways of doing it? - Sorry, there is not other ways of going through a BCP process.  If you bypass the process (or a phase in the process), your plan will stink....
 * 7) please add copyright notice to your diagram. - Done
 * 8) please add comparison to methodologies used in Japan and Taiwan where a disaster like 9/11 is considered relatively small and massive earthquakes are expected to be handled effectively. - BCP process is the same regardless of the location or the threat!
 * 9) please consider linking citations - Added.

Let’s see what the second round turns up. Please review for featured article status Revmachine21 12:42, 30 Apr 2005 (UTC)

First FAC
It looks like a nice article so far (I'm no expert in the field, so I can't judge any content). As a laypeson, however, I'm missing context. Where does BCP come from? You must establish that it's not original research rightaway by mentioning who originated this methodology, or in what field it started. Any books to add to the references? JRM 14:43, 2004 Dec 12 (UTC)

 * Thanks again JRM, good input. My professional background is in BCP (i.e. BCP Manager) and this content originated from my head; I was trained on the job in the finance industry.  I will need to research the historical precedents to the 'science'.  BCP methodology is advocated by governments for organizations of all sizes so it is not proprietary.  This can be a highly complex field and I am struggling to keep the context general enough for small industry, non-profit, educational organizations etc.  As way of reference, my last firm's BCP manual was 400+ pages long.  From your comments sounds like I've made it too generic and need to add color. Revmachine21 15:18, 12 Dec 2004 (UTC)

 * Genericity is not bad; Wikipedia is a secondary source. However, anything we say should also be verifiable—i.e, we must mention what we're generalizing over. ("Cat flinging is a hobby practiced by sadists. It was first mentioned in a 1974 article by Isaac Isaacson published in "Unethical Biology" [...] According to Fred Foobar of the Ministry of Excellence, one should always keep the cat to be flung by the tail, but multiple sources, including the Association of Feline Deviants, claim any body part will do.") Etcetera, etcetera, followed by references to the article, Foobar's statement, and multiple references including one for the AFD.

 * Paraphrasing and summarizing is allowed (necessary, even), but we should always strive to check our facts and cite our sources. An article that's "made up" by someone from working knowledge is better than none at all (in fact, the vast majority of articles in Wikipedia starts like that and many never get any further), but an article that can mention where it came from is even better. However, that's not of immediate importance. You can focus on getting everything of importance in before trying to tie it all to sources. See also How to write a great article, which goes in great detail on how to best approach this sometimes daunting task. JRM 18:57, 2004 Dec 12 (UTC)

Comments
I have comments on this topic. The overall concept of Business Continuity and Disaster Recovery Planning are under review and development by the ISO to create a family of standards similar to the ISO 9000 family for Quality Management. This new family will be covered in the ISO 27000 family and several of the existing standards as mentioned below will fold into this new family of standards including ISO 17799, ISO 24762, ISO 27001, BS 25999-1. These are discussed in ISO/TC 223 (IWA 5:2006).

The overall principle here is that Disaster Recovery is primarily designed for technology and as such is designated as specific to technology only within the proposed standards. Business Continuity Management is the holistic view for managing risk to continued operation of business. Business Continuity Planning (Plans) are the governing documentation that will include all the aspects of risk mitigation; including security, technology, preparation and recovery for the various scenarios up to and including a pandemic.

Therefore the information consolidation should take place under the heading of “Business Continuity Management” not Business Continuity Plan. This will enhance the value of information offered. 19:54, 30 May 2007 (UTC)19:54, 30 May 2007 (UTC)WoodstockDan 19:54, 30 May 2007 (UTC)

I have some comments on the article. However, overall it is a good article, and my comments should be read in that context. Indeed, I hope the fact that they will be obscure points, to most 'lay persons', underlines that.

(1) I feel that your article is too focussed on the IT aspects of business continuity. The methodology you described comes from the IT business continuity standards. BS7799 is still valid as an IT standard, but the British Standards Institute is developing a new standard based on PAS56, which is what most UK business continuity practitioners work to (see www.thebci.org). The London bombings of 7/7 exposed that too many organisations’ BCPs did not give enough thought to the human aspects of emergencies.

 * Two ideas here, (1) add what you think is appropriate about PAS56, and/or (2) add a section to describe the such local standards to de-Westernize the article as you see fit. If I don't like it, I will edit. Revmachine21 13:48, 16 August 2005 (UTC)

 * BS7799, or ISO17799 as it's known internationally, is indeed chiefly an IT standard, with some more general disaster management procedure standards. It's also official, and recognised by British Standards (not called the BSI any more) and the International Organization for Standardization.  Whereas PAS56 is a "standard" created by a for-profit organisation calling themselves the Business Continuity Institute (£60 / $111 to see a standard?  Real standards are available for free), with under 2000 members worldwide.  Any mention of this 'PAS56' will be veering close to advertising.  (Try and find anything on PAS01 - PAS55!). Proto t c 14:16, 16 August 2005 (UTC)

 * As I stated, PAS56 is the basis for a new business continuity standard, that will shortly be published by British Standards. The Publically Available Specification Publically Available Specification IS published by British Standards, and they hold the copyright.  You may not be able to find 1 to 55 - they have probably been developed to full standards!  It is also referred to and recommended by the UK government's statutory guidance to public sector organisations: see Emergency Preparedness (warning! large pdf file) section 6.43 Sneakysnaga t c 20:57, 16 August 2005

I would like to comment on your comments, if I may. The new British Standard for Business Continuity, which is to be BS 25999, will replace PAS 56, but I don't belive it is based on PAS 56. I understand that the expert committee involved with its development are building it from the "ground up". BS 7799, as it was called, was in two parts. A Specification and A Guidance. The Guidance part (part 1) was adopted by ISO and called ISO/IEC 17799. Part 2 of the standard is the specification, which means companies can be audit to the standard, or if the wish, to certify to the standard. It is a management system for Information Security and not just IT Security. Yes, it was developed by the IT ISO technical committee, but it is an organization wide standard. In October 2005 this part of the standard was adopted by ISO and is now ISO/IEC 27001:2005. ISO/IEC 17799:2005 will become ISO/IEC 27002 in 2007, but this is expected to be a name change only. BSI Still exists as a company, but has four divisions, one of which is Britsh Standards (I have BSI on my business card). Can I propose that Business Continuity really is about the planning (BCP) of how an organization cn return to normal business operation in the event of a disaster, Service Continuity is about recovering the IT service delivery and Disaster Recovery is about recovering the organizations information in the event of a disaster? The circumstances of when information is lost may be different to the circumstances of when there is an organization wide disaster. Business Continuity is led by the business. Disaster Recovery and Service Continuity are a subset of Business Continuity. --Rob 12:36, 5 April 2006 (UTC)

(2) Business Continuity Management emerged from Disaster Recovery, as organisations realised that a focus on IT recovery from disruption might be irrelevant if the wider business could not operate. Business Continuity today focuses as much on business processes, as the IT underpinnings of those processes. It is also tightly coupled with Crisis Management, which aims to ensure the reputation of the organisation survives an incident intact. This topic should be mentioned and linked to.

 * Please do so. Revmachine21 13:48, 16 August 2005 (UTC)
 * P.S. Went back and checked the article, Crisis Management is already referenced.  Revmachine21

(3) There is much debate about DR and BCM as labels for activities, which is in part because of the historical roots of the discipline. This reflects that there is a continuum of related activities that may take place under this heading, with a variety of methods. Accordingly, setting out a single method as correct is probably not appropriate for this article.

 * Don't understand what you mean here. Personally would avoid an archane treatise about terminology.  This is supposed to be an encyclopedia article for the general public, not a PhD dissertation going into the quantative differences between word X and Y. Revmachine21 13:48, 16 August 2005 (UTC)

 * Correct, there is no single 'correct' method of business continuity planning. They all share the same underlying principles, however. Proto t c 14:16, 16 August 2005 (UTC)

(4) You state that “This lack of interest unequivocally ended September 11th 2001, when simultaneous terrorist attacks devastated downtown New York City and changed the 'worst case scenario' paradigm for business continuity planning.” Your citation is to an opinion piece, which itself has no evidence that this paradigm shift has taken place, and is in fact a call for it to take place. By contrast there is much evidence to suggest that many organisations still do not have business continuity plans at all.

 * Sorry, totally disagree. Regulators, particularly financial regulators, have raised the mark dramatically, added miles/kilometers to minimum safe distances.  Companies raised their budgets.  Drills became more serious.  This is personal experience earned by force marching staff down 37 flights of stairs to make sure they knew how to get out of my high-rise building and being subjected to much more audit scrutinity of my BCP plans.   Oh, BTW, when we got to the bottom floor we found the emergency exits were locked from the outside.  If that had been for real, we woulda been spam in a can. Revmachine21 13:48, 16 August 2005 (UTC)

 * Please include a reference to the National Institute for Occupational Safety and Health (NIOSH)for chemical and radiological events. — Preceding unsigned comment added by LeavingEden2018 (talk • contribs) 02:04, 18 February 2018 (UTC)

 * Indeed. ISO 17799 didn't exist in its current form until after September 11.  A far greater emphasis on disaster planning, business contoinuity, crisis management, whatever you want to call it has definitely been visible since 2001. Proto t c 14:16, 16 August 2005 (UTC)

(5) My comments are based on the UK experience, and my reading of your article is that it is mostly relevant to the ‘West’. I would suggest that for a global resource such as the Wikipedia, a context statement is relevant. I personally have no idea about the global spread of business continuity but imagine it is less well advanced in the other parts of the world.

 * I would argue that the BCP discipline is driven by heavily regulated industries such as finance, pharmaceutical, energy, health, etc. In all those fields, the 'West' unfortunately leads the rest of the world, other countries tend to follow, all-be-it with their own adaptions.  If you can come up with some relevant information to add a non-Western spin, please do so. Revmachine21 13:48, 16 August 2005 (UTC)

 * Excellent comments it seems. You clearly have a detailed knowledge of the subject and it is exactly someone like you that needs to fix the things you see. No one, even a very knowledgeable person, such as Revmachine21 who I believe wrote nearly the entire article can write without any bias, and you may have uncovered it, or you may be off base on some of your comments--I don't know enough about the subject to decide. But you and Rev can discuss it and fix the issues. Please find the relevant sources and cite them so that the article can be as verifiably correct as possible. Consider signing up for a username and helping to improve the article. Thanks - Taxman Talk 12:22, August 16, 2005 (UTC)

 * Thank you Taxman. I have now signed up for a username.  I will endeavour to help out as much as possible.  Time permitting! Sneakysnaga t c 20:57, 16 August 2005

(6) Regarding the suggestion to merge this article with Disaster Recovery
 * The concept of Disaster Recovery only embraces one aspect of Business Continuity and the planning that an organization must undertake to ensure reliable service delivery. Perhaps "Disaster Recovery" and "Business Impact Analysis" would more appropriately exist separately from, but still contain links to, "Business Continuity Planning." Networktester t c 12:09, 25 February 2006
 * Disaster recovery is already in existence, click link. Also agree that it should remain separate.  The Business Impact Analysis would have to be a new article, probably a nice addition too.  Have at it & have fun! Revmachine21 00:24, 26 February 2006 (UTC)

There is over reliance on BS7799. We will have to appreciate that BS7799 is a information security standard and it does not clearly spell out BCP practices. BCP is not about IT only! what happened in Kathrina storm/9-11/Mumbai floods is not about IT alone. It's time we cleaned up this article. Let's do justice to field of BCP and put content accordinly.

 * Fabulous idea darling. Please proceed.  Revmachine21 08:46, 13 October 2006 (UTC)

Article Introduction
Can I make a few comments on the article introduction?

This article is redirected from Business Continuity Management and the terms are largely interchangeable. I actually think management is a better reflection of what actually happens, the word planning assumes never actually doing. Would it be appropriate to mention the fact that the two terms are commonly interchanged.

It is not necessarily a peer mentored process, why is this one in

It does not produce a plan but a capability. This seems to reflect that the whole point of BCP is to create a plan

The aim should be to recover some or all of an organisations processes but critically, and this is not mentioned, to a pre agreed level. It is not about business as usual but getting to an agreed level within a target time

It does seem to be UK centric with no mention in the introduction of other standards such as the North American NFPA 1600, Australian HB292/3 and ISO/PAS 22399. Also not sure what the Civil Contingencies Act in the UK has much to do with the subject.

Prior to the introduction of BS25999 BCM professionals did not have to rely on BS7799 as stated in the article. BS7799 and its subsequent revisions is an Information Security Management standard that includes a section on business continuity. One of the three pillars of information security management is availability. This is obviously relevant but there were other documents that BCM professionals could use including PAS56 (a fore runner of BS25999), earlier versions of NFPA1600, earlier versions of HB292/3 and the various generally accepted practice documents produced by the BCI and DRI

Would it be appropriate and accepted to make some changes based on these observations? —Preceding unsigned comment added by Samsungjohnny (talk • contribs) 15:13, 13 January 2008 (UTC)

 * The topic of the page is Business Continuity Planning. It is thus preferable not to over-develop tangental aspects. Equally, not use additional material to place links to your own site.  —Preceding unsigned comment added by 66.84.37.52 (talk) 15:52, 13 January 2008 (UTC)

I am suggesting changing the content, not to develop tangential topics or link to my own content. Please read my suggestions rather than jumping to conclusions. Samsungjohnny (talk) 16:08, 13 January 2008 (UTC)

 * Change of content for an established page like this should be evolutionary and built upon long term consensus. Radical change, is not required. Previous edits illustrate my concern. 66.84.37.52 (talk) 19:57, 13 January 2008 (UTC)

OK, whatever. I will present my suggestions in another way then if a wholesale change is not the correct way of moving forward. The introduction to the article suffers from a UK focussed perspective and is a little misleading in some respects not accurately reflectng the current best practice in BCP, so here goes, my tuppence worth for user review

FIRST PARA Remove peer mentoring. BC Planning is not necessarily a peer mentored process

Change logistitical plan to capability. Capability is a mcuh more relevant subject because the plan is made up from a variety of processes, systems etc

Add after predetermined time, and to a pre defined level. A recovery does not necessarily have to be to a full level but will probably be at a reduced level

Remove extended disruption and replace with disruptive event. This leads the reader into thinking that the only things that cause business continuity to be used is a disaster or extended disruption but BCP seeks to mitigate a broad range of disruptions

Remove the logistical plan is called a business continuity plan. Business continuity planning produces a wide range of documented systems only one of which is the business continuity plan

SECOND PARA Change mission to activity and change longterm health to longterm viability

Broaden out the range of incidents described to include, IT problems, information security breaches and others

THIRD PARA Change the word lax to poor. Lax indicates a lack of activity but it is not just the lack of activity but also the wrong activity

FOURTH AND FIFTH PARA These seem to be very UK focussed and I am not sure what the UK Civil Contingencies Act has to do with the subject. Can I suggest replacing these two paragraphs entirely to refelect the fact that a number of professional institutes and standards bodies have standards and guidance documents, maybe listing some examples. The previous edit that has been stricken did include a suggestion to this but I wont be so prescriptive here.

Over to editors for view Samsungjohnny (talk) 21:16, 13 January 2008 (UTC)

Moving "How-To" Guidelines into Wikibooks
See peer review article updates before mass reversion of Master Business Continuity Planner (MBCP) work-in-process
 * -- 66.45.145.191 14:17, 26 October 2006 (UTC)
 * Note: This migation process required purging all external URLS
 * -- 66.45.145.191 14:31, 26 October 2006 (UTC)
 * Replaced non-"How To" sections with corrected peer review version.
 * geoWIZard-Passports 10:30, 10 December 2006 (UTC)

Introduction
BCP methodology is scalable for an organization of any size and complexity. Even though the methodology has roots in regulated industries, any type of organization may create a BCP manual, and arguably every organization should have one in order to ensure the organization's longevity. Evidence that firms do not invest enough time and resources into BCP preparations are evident in disaster survival statistics. Fires permanently close 44% of the business affected. In the 1993 World Trade Center bombing, 150 businesses out of 350 affected failed to survive the event. Conversely, the firms affected by the Sept 11 attacks with well-developed and tested BCP manuals were back in business within days.

A BCP manual for a small organization may be simply a printed manual stored safely away from the primary work location, containing the names, addresses, and phone numbers for crisis management staff, general staff members, clients, and vendors along with the location of the offsite data backup storage media, copies of insurance contracts, and other critical materials necessary for organizational survival. At its most complex, a BCP manual may outline a secondary work site, technical requirements and readiness, regulatory reporting requirements, work recovery measures, the means to reestablish physical records, the means to establish a new supply chain, or the means to establish new production centers. Firms should ensure that their BCP manual is realistic and easy to use during a crisis. As such, BCP sits along side crisis management and disaster recovery planning and is a part of an organization's overall risk management.

The development of a BCP manual has five main phases: analysis, solution design, implementation, testing and organization acceptance, and maintenance.

Much of the BCP material on the internet is sponsored by consultancies who offer fee-based services for BCP solution development, however basic tutorials are freely available on the internet for properly motivated organizations.

From reading this it seems that the whole point of BCP is to produce a manual. This is not the case at all. It is to produce an ongoing capability and changes with the organisation and its goals and resources.

It also defines the BIA process in rather prescriptive terms. A BIA can and should be suitable for the organisation not following the defined zones as described here

The description about BCP post Y2K and post the 9/11 attacks are extremely US focussed. The UK, which has experienced 30 odd years of Northern Irish terrorism has developed arguably the most mature BCP capabilities precisely because of it.

The various standards and accepted best practice guidelines from various public and private sector organisations seek to promote BCP so that organisations are not compelled to seek third party consultants

The main area of concern I have for this section though is the concentration on producing a BC Manual

Samsungjohnny (talk) 21:32, 13 January 2008 (UTC)

Analysis
The analysis phase in the development of a BCP manual consists of an impact analysis, threat analysis, and impact scenarios with the resulting BCP plan requirement documentation.

Impact analysis
An impact analysis results in the differentiation between critical and non-critical organization functions. A function may be considered critical if the implications for stakeholders of damage to the organization resulting are regarded as unacceptable. Perceptions of the acceptability of disruption may be modified by the cost of establishing and maintaining appropriate business or technical recovery solutions. A function may also be considered critical if dictated by law. Next, the impact analysis results in the recovery requirements for each critical function. Recovery requirements consist of the following information:
 * The time frame in which the critical function must be resumed after the disaster
 * The business requirements for recovery of the critical function, and/or
 * The technical requirements for recovery of the critical function

Threat analysis

After defining recovery requirements, documenting potential threats is recommended to detail a specific disaster’s unique recovery steps. Some common threats include the following:

 * Disease
 * Earthquake
 * Fire
 * Flood
 * Cyber attack
 * Hurricane
 * Utility outage
 * Terrorism

All threats in the examples above share a common impact - the potential of damage to organizational infrastructure - except one (disease). The impact of diseases is initially purely human, and may be alleviated with technical and business solutions. During the 2002-2003 SARS outbreak, some organizations grouped staff into separate teams, and rotated the teams between the primary and secondary work sites, with a rotation frequency equal to the incubation period of the disease. The organizations also banned face-to-face contact between opposing team members during business and non-business hours. With such a split, organizations increased their resiliency against the threat of government-ordered quarantine measures if one person in a team contracted or was exposed to the disease. Damage from flooding also has a unique characteristic. If an office environment is flooded with non-salinated and contamination-free water (e.g.m, in the event of a pipe burst), equipment can be thoroughly dried and may still be functional.

 * I added some more to the article (such as random failure of mission critical systems), but I also think "Terrorism" should be removed.  Loss of Confidentiality (or theft), Availability, or Integrity of critical information or material, or loss of mission critical functionality is the goal of any attacker - terrorist, hacker, or Other.   I see no difference between a Terrorist and and Insider intend to do the same damage (sabotoge or other forms).   I suggest simply the introduction of an internal or external threat entity.--74.107.74.39 (talk) 23:50, 26 March 2011 (UTC)

Definition of impact scenarios
After defining potential threats, documenting the impact scenarios that form the basis of the business recovery plan is recommended. In general, planning for the most wide-reaching disaster or disturbance is preferable to planning for a smaller scale problem, as almost all smaller scale problems are partial elements of larger disasters. A typical impact scenario like 'Building Loss' will most likely encompass all critical business functions, and the worst potential outcome from any potential threat. A business continuity plan may also document additional impact scenarios if an organization has more than one building. Other more specific impact scenarios - for example a scenario for the temporary or permanent loss of a specific floor in a building - may also be documented.

Recovery requirement documentation
After the completion of the analysis phase, the business and technical plan requirements are documented in order to commence the implementation phase. For an office-based, IT intensive business, the plan requirements may cover the following elements which may be classed as ICE (In Case of Emergency) Data: Other business environments, such as production, distribution, warehousing etc will need to cover these elements, but are likely to have additional issues to manage following a disruptive event.
 * The numbers and types of desks, whether dedicated or shared, required outside of the primary business location in the secondary location
 * The individuals involved in the recovery effort along with their contact and technical details
 * The applications and application data required from the secondary location desks for critical business functions
 * The manual workaround solutions
 * The maximum outage allowed for the applications
 * The peripheral requirements like printers, copier, fax machine, calculators, paper, pens etc.

Solution design
The goal of the solution design phase is to identify the most cost effective disaster recovery solution that meets two main requirements from the impact analysis stage. For IT applications, this is commonly expressed as: Disaster recovery plans may also be required outside the IT applications domain, for example in preservation of information in hard copy format, or restoration of embedded technology in process plant. This BCP phase overlaps with Disaster recovery planning methodology. The solution phase determines:
 * 1) The minimum application and application data requirements
 * 2) The time frame in which the minimum application and application data must be available
 * the crisis management command structure
 * the location of a secondary work site (where necessary)
 * telecommunication architecture between primary and secondary work sites
 * data replication methodology between primary and secondary work sites
 * the application and software required at the secondary work site, and
 * the type of physical data requirements at the secondary work site.

Implementation
The implementation phase, quite simply, is the execution of the design elements identified in the solution design phase. Work package testing may take place during the implementation of the solution, however; work package testing does not take the place of organizational testing.

Testing and organizational acceptance
The purpose of testing is to achieve organizational acceptance that the business continuity solution satisfies the organization's recovery requirements. Plans may fail to meet expectations due to insufficient or inaccurate recovery requirements, solution design flaws, or solution implementation errors. Testing may include:
 * Crisis command team call-out testing
 * Technical swing test from primary to secondary work locations
 * Technical swing test from secondary to primary work locations
 * Application test
 * Business process test

At minimum, testing is generally conducted on a biannual or annual schedule. Problems identified in the initial testing phase may be rolled up into the maintenance phase and retested during the next test cycle.

Maintenance
Maintenance of a BCP manual is broken down into three periodic activities. The first activity is the confirmation of information in the manual. The second activity is the testing and verification of technical solutions established for recovery operations. The third activity is the testing and verification of documented organization recovery procedures. A biannual or annual maintenance cycle is typical.

Information update and testing
All organizations change over time, therefore a BCP manual must change to stay relevant to the organization. Once data accuracy is verified, normally a call tree test is conducted to evaluate the notification plan's efficiency as well as the accuracy of the contact data. Some types of changes that should be identified and updated in the manual include:
 * Staffing changes
 * Staffing persona
 * Changes to important clients and their contact details
 * Changes to important vendors/suppliers and their contact details
 * Departmental changes like new, closed or fundamentally changed departments.

Testing and verification of technical solutions
As a part of ongoing maintenance, any specialized technical deployments must be checked for functionality. Some checks include:

 * Virus definition distribution
 * Application security and service patch distribution
 * Hardware operability check
 * Application operability check
 * Data verification

Testing and verification of organization recovery procedures
As work processes change over time, the previously documented organizational recovery procedures may no longer be suitable. Some checks include:

 * Are all work processes for critical functions documented?
 * Have the systems used in the execution of critical functions changed?
 * Are the documented work checklists meaningful and accurate for staff?
 * Do the documented work process recovery tasks and supporting disaster recovery infrastructure allow staff to recover within the predetermined recovery time objective?

Treatment of test failures
As suggested by the diagram included in this article, there is a direct relationship between the test and maintenance phases and the impact phase. When establishing a BCP manual and recovery infrastructure from scratch, issues found during the testing phase often must be reintroduced to the analysis phase.
 * -- 66.45.145.191 13:22, 26 October 2006 (UTC)

Managing collaborative groups
Please explain the addition of this descriptor to the introductory image? I certainly did not have 'managing collaborative groups' in mind when I created the image. When looking at the wikilink to the MCG outine, nothing particularly jumped out at me to indicate why MCG had any relevance to BCP or the planning process. Please explain your reasoning. Thanks in advance. P.S. Some of the recent changes are quite nice additions. Revmachine21 10:48, 10 December 2006 (UTC)

 * Repeat request for clarification... otherwise I'm deleting the text. Revmachine21 02:15, 24 March 2007 (UTC)

Merge Bs 25999
An article about the standard for BCP would seem to have a huge overlap with this article. Is there really sufficient distinguishable material for a separate article? -- Whpq 02:41, 19 January 2007 (UTC)

 * I don't agree. BS 25999 is a significant new development and will evolve into a large topic itself especially when it becomes and ISO standard. It should not be merged into this topic.Binarygal

 * I don't agree with the merger proposal. BCP stands independent of BS25999 and was in existence before the standard.  Seems to me that the BS25999 article needs a rework and expansion in line with the other BSI standards.  Revmachine21 02:14, 24 March 2007 (UTC)

 * I wikified the Bs 25999 page today, but do not have enough experience with the subject to expand the article. As said above, it needs a rework as well.  I originally supported a merge based upon the shape of the Bs 25999 article, but I'm deferring to others on this one - they know more than I do about the appropriateness of the merge.  *Vendetta* (whois talk edits) 23:13, 1 April 2007 (UTC)

Exercising care developing the first paragraph & first section
The Intro paragraph grew (in a good way from an information standpoint) and got clunky. Let's be more careful from a style perspective when editing! The Introduction section has been expanded with materials moved out of first paragraph. IMO, the Intro section needs more work. I will do what I can but request collaboration from those other Wikipedian's monitoring this page. Revmachine21 01:40, 24 March 2007 (UTC)

Slightly expanded view of BCP
BCP is more than recovery from disasters: fire, flood, earthquake and/or pandemics. BCP is a plan to handle all of the bumps thrown at a business: competitive price drops, worker strikes, increased minimum wage etc.... The data on this page is good, but it seems to be excessively focused on the DRP side of BCP (and the DRP page is lacking much of this material). Maybe this could be refocused in the future? Iam.the.Unkn0wn1 4:28, 18 July 2007 (UTC)

Comment on section regarding BCP Standards
I would suggest that the author of this fine article consider adding comments regarding NFPA 1600 to the standards discussion. As it stands now, readers will assume that the only BCP standard that exists is BS25999, which is used primarily in the UK. In the U.S., the predominant standard is NFPA 1600, and I believe it deserves equal attention.

--MJKuras 18:38, 13 December 2007 (UTC)MJKuras

StandardsDirect.org
I removed the link to a standards purchase site, standardsdirect.org. See Wikipedia talk:WikiProject Spam for more about this site. As I see it, Wikipedia is not a directory and we're not here to help people sell things. Most of these standardsdirect.org links have been added by single purpose accounts who likely have a conflict of interest. See:
 * Conflict of Interest Guideline
 * What Wikipedia is Not Policy
 * External Links Guideline
 * Spam Guideline

If an established, high-volume editor wants to add it back to the article, by all means go ahead. Otherwise, it stays out pending resolution at the spam discussion link above. -- A. B. (talk • contribs) 00:43, 23 October 2008 (UTC)

Maximize what?
The standard provides a best practice framework to minimize disruption and maximize recovery time Excuse me, could somebody explain me in a sentence, why a long recovery time is better than a short one? If I were a company, I would maximize recovery speed or minimize recovery time.--Kifo (talk) 10:24, 12 July 2013 (UTC)
 * I agree. Seems the entire phrase doesn't belong there. Removing it........ My name is Mercy11 (talk) 02:25, 13 July 2013 (UTC), and I approve this message.

Title and content as a whole
This article does not really discuss business continuity planning, but almost exclusively the subset of it that is disaster recovery, and indeed primarily only with reference to natural disasters, rather than collapsing and needing to be recovered.

The fundamental goal of business continuity planning is assurance of resilience so that business continues to operate in the face of incidents. This point is so fundamental I'm amazed it has been omitted by the authors of this article. 212.159.59.5 (talk) 10:51, 27 August 2014 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 one external links on Business continuity planning. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20060810074640/http://www.fema.gov:80/business/bc.shtm to http://www.fema.gov/business/bc.shtm
 * Added archive https://web.archive.org/web/20130513081920/http://www.nfpa.org/assets/files//PDF/Research/RFLithiumIonBatteriesHazard.pdf to http://www.nfpa.org/assets/files/

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.— InternetArchiveBot  (Report bug) 07:39, 11 November 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on Business continuity planning. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20160303224604/http://www.virtualdcs.co.uk/blog/business-continuity-planning-rpo-and-rto.html to http://www.virtualdcs.co.uk/blog/business-continuity-planning-rpo-and-rto.html
 * Corrected formatting/usage for http://www.fema.gov/business/bc.shtm

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 08:44, 27 July 2017 (UTC)

X
X Xkxjxjx02 (talk) 12:15, 23 March 2019 (UTC)

Relationships and Entities
Others have noted there's an overemphasis on IT in the article.

What specifically about the continuity of relationships - for example, if the company should go out of business, there may need to be a plan for customers to be serviced (or records retained) by a designated alternate entity. I think this type of continuity setup is common in the Accounting world for instance.

DouglasHeld (talk) 10:00, 10 August 2022 (UTC)

title: Talk:Business continuity planning


text:
Category:Eponyms

An eponym is a person, place, or thing after whom or after which something is named, or believed to be named. Since many medical conditions, sports moves, bridge and chess techniques, buildings, prizes, and other things have been named after people, these are not included in this category, as categorization on the basis of having been named for a person is considered to be overcategorization based on trivial aspects of the article. This category is for the process or phenomenon of naming things after people. Feel free to add other items to the appropriate lists under the category Category:Lists of eponyms.

title: Category:Eponyms


text:
Northwest University (China)

Northwest University is a public university located in Xi'an, Shaanxi, China. It is affiliated with the Province of Shaanxi, and co-funded by the Shaanxi Provincial People's Government and the Ministry of Education. The university is part of Project 211 and the Double First-Class Construction.

History
The earliest predecessor of the school was the Shaanxi University Hall and the Capital University Hall Accelerated Science and Technology School in 1902. The school was first called Northwest University in 1912 and changed its name to National Northwest University in 1923. In 1937, the school formed the National Xi'an Temporary University with the National Peking University, Peking Normal University, Peiyang University College of Engineering, and Peking Research Institute, which moved west to Shaanxi. In 1938, National Xi'an Temporary University was changed to National Northwest Associated University. In 1939, it was renamed National Northwest University. After the war, the universities that had moved to the west moved back. In 1950, the school was renamed Northwest University. In 1988, Chinese University Ranking(CUAA), placed this university as NO.7 in the Science at that time. Today, Northwest University still keeps a leading position on the Chinese language, economic and so on fields.

title: Northwest University (China)


text:
Stanisław Jan Jabłonowski

Prince Stanisław Jan Jabłonowski (1634–1702) was a Polish nobleman, magnate, Grand Guardian of the Crown since 1660, the Grand Camp Leader of the Crown since 1661, voivode of the Ruthenian Voivodship since 1664, Field Crown Hetman since 1676, Great Crown Hetman since 1683 and castellan of Kraków since 1692. Jabłonowski was a candidate for the Polish Throne following the death of King John III Sobieski.

A talented and skillful political and military leader, Jabłonowski participated in the War with Sweden during The Deluge, then with the Cossacks and Muscovy. He took part in the Chocim campaign of 1673 and participated in the Vienna expedition of 1683. He led the right wing of Polish cavalry forces at the Battle of Vienna. He also stopped the Tatars at Lwów in 1695. In 1692 Jabłonowski built the stronghold and the neighbouring town of Okopy Świętej Trójcy. During the Royal election of 1697, he supported Augustus II, later in opposition to the King. In 1698, Emperor Leopold I granted him and his family the hereditary title of Prince.

His daughter, Princess Anna Jabłonowska, who married Rafał Leszczyński, was the mother of King Stanisław I.

Biography
Stanisław was son of the Lord Sword-Bearer Jan Jabłonowski (1600–1647) and Anna Ostroróg, the daughter of author and scholar Jan Ostroróg. After the abdication of King John II Casimir in 1668, Jabłonowski supported the French prince Louis, Grand Condé as a candidate for the Polish crown. He died on 3 April 1702.

title: Stanisław Jan Jabłonowski


text:
Carpet Museum of Iran

Located beside Laleh Park in Tehran the Carpet Museum of Iran was established by the order of Shahbanu Farah Pahlavi in 1976 to exhibit a variety of Persian carpets from all over Iran.

The museum's exhibition hall occupies 3,400 sqm and its library contains approximately 7,000 books. The museum was designed by architect Abdol-Aziz Mirza Farmanfarmaian.

title: Carpet Museum of Iran


text:
Henry Youle Hind

Henry Youle Hind (1 June 1823 – 8 August 1908) was a Canadian geologist and explorer. He was born in Nottingham, England, and immigrated to Canada, settling in Toronto, Ontario, in 1846. Hind led expeditions to explore the Canadian prairies in 1857 and 1858. In 1857, he explored the Red and Assiniboine River valleys, and in 1858, the Assiniboine, Souris, Qu'Appelle, and South Saskatchewan River valleys. The expeditions are described in his reports Narrative of the Canadian Red River Exploring Expedition of 1857 and Reports of Progress on the Assiniboine and Saskatchewan Exploring Expedition. Hind's activities changed perceptions of the North West and helped open up the Canadian Prairies for agriculture settlement.

Early life
Henry Youle Hind was born in Nottingham, England. He was the third son of Thomas Hind and Sarah Youle Hind. His older brothers were Thomas and James Fisher, the younger William. He also had a younger sister Sarah. On 7 February he married Katherine Cameron at York Mills. She was the second daughter of Lieutenant-Colonel Duncan Cameron. Their first child Thomas Francis Neil Hind was born in 1851. They settled in Toronto where they had four more sons and two daughters by 1863.

Hind was responsible for much of his own education growing up, but did receive some formal schooling. He was taught the classics, mathematics, and penmanship at Nottingham Grammar School. In 1837 he went to study in Leipzig. In 1839 he returned to England and continued his studies in Nottingham for another four years. On 26 May 1843 Hind was accepted into Cambridge University but only stayed for one year.

In 1846, he immigrated to Canada where he settled in Toronto. In March 1847 he began his scientific career writing on a meteorological 'halo'. In October of that year he was employed by Egerton Ryerson. He was given a position at the Provincial Normal School in Toronto as a second master of science and mathematics. In 1850 he published Lectures on Agricultural Chemistry and the following year A Comparative View of the Climate of Western Canada. In December 1851 he became an early member of the Canadian Institute. From 1852 until 1855 he was the editor of the Institute's periodical the Canadian Journal. He was also employed as a professor of chemistry at the University of Toronto Trinity College, a position he held until 1864. Between 1856 and 1858 he published articles in the Canadian Almanac. These included The Future of Western Canada, Our Railway Policy, and The Great North-West.

1857 Red River Expedition
By the 1850s British North America had reached a critical stage in its development. Since the 1837 Rebellions in Upper Canada and Lower Canada there had been an increase in immigration and construction of canals and rail lines. In the Canadas agricultural land was becoming scarcer and higher in price. In the North-West, fur trade networks were becoming unstable with the future of the west remaining in the control of the Hudson's Bay Company unlikely. New agricultural land was needed by people in Upper Canada and Lower Canada. Out of this need for land a movement of expansionism was created in Upper Canada.

In Toronto and the Ottawa Valley prominent members of society including George Brown and Alexander Mcdonnell sought to annex the North-West. To prove that the land in the North-West as suitable, the British and Canadian governments funded expeditions west in 1857. The British expedition was formed by the Royal Geographical Society and was led by John Palliser. The Canadian expedition was led officially by George Gladman. Hind was recommended by the head of the Canadian Geological Survey, William Logan, to lead the scientific portion of the expedition. Throughout the expedition Hind was to collect information on topography, vegetation, soil and meteorological observations.

The Canadian expedition departed on 23 July 1857 from Toronto on the Northern Railway. The group included George Gladman, his son Henry, Simon Dawson, W. H. E. Napier, S. L. Russell, G. F. Gaudet, A. M. Wells, J. A. Dickenson and Robert Wynne. The expedition included a dozen Iroquois, representatives of the fur trade, a dozen Ojibwa, several French Canadians, a Scottish man and a Métis man. The group arrived at Fort William by the end of the month.

The Palliser and Hind expeditions sought to prove that the previously uninhabitable fur trade lands of the North-West would be useful for agricultural development and immigrants from Upper and Lower Canada. These scientific expeditions were the most immediate consequences of the expansionist campaign. Ultimately the work of Palliser and Hind redefined public opinion and the perceived geography of the North-West. They created the idea of two vast sub-districts. Palliser's Triangle consisted of poor soil and was arid and uninhabitable. Hind's discovery, called the Fertile Belt, stretched from the Red River Settlement to the Saskatchewan River Valley and the Rocky Mountains. They reinforced the myth of good land in the north of Saskatchewan and the myth of bad land in the interior.

The Fertile Belt supported expansionist claims of an agricultural oasis. Hind was aware of this and noted it in his work on the expedition, Narrative of the Canadian Red River Exploring Expedition of 1857 and of the Assiniboine and Saskatchewan Exploring Expedition of 1858 stating that "it is a physical reality of the highest importance to the interests of British North America that this continuous belt can be settled and cultivated from a few miles west of the Lake of Woods to the Passes of the Rocky Mountains, and any line of communication, whether by waggon road or railroad, passing through it, will eventually enjoy the great advantage of being fed by an agricultural population from one extremity to another." The route that the Canadian expedition used was well known by fur traders and was also used by the Palliser Expedition. They reached Fort Frances by 19 August 1857. From there Hind and Simon Dawson split from George Gladman. They met six men and two canoes to cross the southern portion of the Lake of the Woods to portage the western shore of the Roseau River. Using the Roseau River, Hind and Dawson were to reach the Red River. This was not a usual route for fur traders.

On 22 August 1857 they reached Garden Island. This was a traditional Ojibwa settlement where they grew corn, potatoes, pumpkin and squash. On the Island Hind collected samples of corn which caused the group to be questioned by an Ojibwa raiding party. An unnamed Ojibwa man was quoted in Hind's Narrative as saying "to deny your request; but we see how the Indians are treated far away. The white man comes, looks at their flowers, their trees, and their rivers; others soon follow; the lands of the Indians pass from their hands, and they have nowhere a home. You must go by the way white man had hitherto gone. I have told you all." Following this encounter, Hind and Dawson were forced to take the traditional fur trade route down the Winnipeg River to the Red River.

Through the government commission of the 1857 expedition Hind was to complete three tasks. The first was to explore the Red River Settlement, the second to examine the Assiniboine River westward as far as Portage la Prairie and make inquiries in the Souris Valley about lignite coal. Third, Hind had to explore the Red River Valley southward to the Roseau River and examine the river well enough to understand the route from the Lake of the Woods. He only had one month from 9 September until 8 October to complete these tasks.

The expedition ended quickly; Hind was back in Toronto by 4 November 1857. Although he had left the North-West, the work of the expedition was not over. Hind printed a report on the expedition in 1858 that ran over four hundred pages in total length. His report was received well especially by the Globe, a newspaper run by expansionist George Brown. The reception of the Canadian expedition ensured another for the following year although this time it would be led by Hind and Simon Dawson.

1858 Assiniboine and Saskatchewan Expedition
The success of the 1857 expedition led to the creation of two Canadian expeditions led by Simon Dawson and Hind in 1858. Dawson was to evaluate the country from the Red River to Fort William for an immigration route. Hind's expedition was to look westward from the Red River to the south branch of the Saskatchewan River to examine territory for the possibility of settlement, coal mining in the Souris Valley and the salt springs of Lake Winnipegosis. The members of Hind's expedition included photographer and surveyor Humphrey Lloyd Hime, J.A. Dickenson, John Fleming, thirteen Iroquois, an Ojibwa man, and two French Canadians.

The group arrived at Grand Portage on 5 May 1858 and had arrived at the mouth of the Winnipeg River by the 29 May. It took some time to prepare the supplies and men for the expedition but they were in the field by 19 June. In addition to scientific information, Hind also collected information on the lifestyle of the Plains Cree. In 1857 the Plains Cree in council had decided that no white man should be allowed to hunt in or travel through their country due to multiple broken promises and the destruction of the buffalo. Hind was witness to the collapse of the hunting economy of the old North-West. By 18 September 1858 Hind's expedition was beginning its last phase. By 28 December he was back in Toronto.

Later career
Following Hind's return to Toronto he resumed his teaching position at University of Toronto, Trinity College and membership to the Royal Canadian Institute. He prepared a report on the 1858 expedition and attempted to organize a third expedition to the Bow River and the Rocky Mountains. An economic depression in 1857 left the Canadian government wary of further expenditures on scientific expeditions so Hind's proposal was declined. In 1859 he published Of Some of the Superstitions and Customs Common Among the Indians in the Valley of the Assiniboine and Saskatchewan in the Canadian Journal. After 1859, Hind attempted to resume exploring and publishing. During the winter of 1859-1860 Hind returned to England to see his Narrative published. In 1861 he planned an expedition to the North-East. He sought to survey the land around the Labrador Peninsula. This was not a government funded expedition. In 1863 he published a report on this expedition entitled Explorations in the Interior of the Labrador Peninsula in two volumes. In 1864 Hind left his job at Trinity College after being invited to speak at the Royal Geographical Society. Once back in Toronto he was invited by Peter Mitchell of New Brunswick to have their geological resources surveyed. Hind left Toronto in May for New Brunswick. At the same time as Hind's geological survey, another was being led by L. W. Bailey and G. F. Matthew. Only one of these surveys was to be paid a sum of five hundred dollars by the Canadian government. While the government was deciding which report would be used, an anonymous editorial was published in The Headquarters, a local daily in Fredericton which scrutinized the work of Bailey and Matthew. It was believed that Hind was the author of the editorial and it had serious consequences for him. He lost his reputation among workers in the same field and was not employed as the provincial geologist of New Brunswick.

In September 1864 Hind settled his family in Fredericton. In July 1865 his eldest son drowned while bathing in the Saint John River. The family remained in Fredericton until the following year. In the fall of 1866 the Hind family moved to Windsor, Nova Scotia where the boys attended King's College and the girls Edgehill. Two of Hind's other sons died; James Archibald of unknown causes after the move to Windsor and John Youle of typhoid in 1880. In Windsor Hind was employed by the Mineral Exploration and Mining Association of Nova Scotia. In 1876 he was invited by Francis von Ellerhausen to make a geological survey of Labrador. Two years later he displayed a map of the oceanic currents in the region. From 1884 until his death in 1908 Hind wrote no more on any scientific or public subject. He became focused on the local history of Windsor. In 1889 he published a history of the Old Burying Ground and in 1890 the Centennial History of King's College. In February 1906 he became ill and died on 8 August 1908. He was buried in Maplewood, Nova Scotia.

Hind was named a National Historic Person in 2018.

Works
Source:
 * The Canoe Route Between Fort William...Fort Garry...1857, (1858)
 * Lake Superior And The Red River Settlement, (1859)
 * North-West Territory..., (1859)
 * Reports Of...Assiniboine & Saskatchewan Exploring Expedition, (1859)
 * Narrative Of The Red River Exploring Expedition Of 1857, (1860)
 * A Sketch Of An Overland Route To British Columbia, (1862)
 * Explorations In The Interior Of The Labrador Peninsula, (1863)
 * Eighty Years' Progress Of British North America, (1863)
 * The Dominion Of Canada, (1869)

title: Henry Youle Hind


text:
Kent Downs

The Kent Downs is an Area of Outstanding Natural Beauty (AONB) in Kent, England. They are the eastern half of the North Downs and stretch from the London/Surrey borders to the White Cliffs of Dover, including a small section of the London Borough of Bromley. The AONB also includes the Greensand Ridge, a prominent sandstone escarpment which lies south of the chalk escarpment of the North Downs.

It was first designated as an AONB in July 1968 and covers 878 square km (326 square miles). The AONB's highest point is Toy's Hill, at 250m above sea level, and its boundaries include three main rivers: the Darent, Medway and Stour.

To the west, Surrey Hills AONB adjoins the Kent Downs AONB, and includes a continuation of the North Downs chalk ridge which runs through the Kent Downs, stretching from Farnham to the English Channel and reappearing within the Parc Naturel Régional des Caps et Marais d’Opale in France. High Weald AONB lies to the south east, separated by a distance of just over 2km at Bough Beech Reservoir.

As part of the management of the AONB, Village Design Statements have been adopted by 14 per cent of villages within its boundaries, going on to form part of Supplementary Planning Guidance, recognising the character of the historic landscape and distinctiveness of settlements.

Areas
Among the named parts of the Downs are:
 * Alkham Valley –  a dry valley north-west of Dover;
 * Betsom's Hill –  highest point in Kent at 251 m; near Westerham
 * Blue Bell Hill
 * Burham Down
 * Castle Hill
 * Chartham Downs
 * Denge Wood
 * Detling Hill
 * Elham Valley
 * Hollingbourne Downs
 * Knole Park
 * Lullingstone Country Park
 * Ranscombe Farm
 * Samphire Hoe
 * Summerhouse Hill
 * Tolsford Hill
 * Torry Hill
 * Wye Downs

Walking
The North Downs Way runs through the full length of the AONB, the Stour Valley Walk passes through the east of the AONB, and the Greensand Way to the south of Sevenoaks.

title: Kent Downs


text:
Carl Clauberg

Carl Clauberg (28 September 1898 – 9 August 1957) was a German gynecologist who conducted medical experiments on (mostly Jewish) human subjects at Auschwitz concentration camp. He worked with Horst Schumann in X-ray sterilization experiments at Auschwitz concentration camp.

In 1945, near the close of WWII, he was captured by the Red Army and sentenced to 25 years in prison. He was released in 1955 under a prisoner exchange agreement, and he returned to Germany and continued to practice medicine. Due to public outcry from Holocaust survivors, Clauberg was arrested in 1955, but died before he could be tried.

Early life
Carl Clauberg was born in 1898 in Wupperhof (now part of Leichlingen), Rhine Province, into a family of craftsmen.

Medical career
During the First World War he served as an infantryman. After the war, he studied medicine and eventually reached the rank of chief doctor in the University gynaecological clinic. He joined the Nazi party in 1933 and later was appointed associate professor of gynaecology at the University of Königsberg. He carried out research on female fertility hormones (particularly progesterone) and their application as infertility treatments, obtaining a habilitation for this work in 1937. He received the rank of SS-Gruppenführer of the Reserve.

Human experiments at Auschwitz
In 1942 he approached Heinrich Himmler, who knew of him through treatment of a senior SS officer's wife and asked him for an opportunity to perform mass sterilizations on women for his experiments. Himmler agreed, and in December 1942 Clauberg moved to Auschwitz concentration camp. His laboratory was in a part of the Block 10 in the main camp. Clauberg's goal was to find an easy and cheap method to sterilize women. He injected caustic substances into their uteruses without anesthetics. His test subjects were Jewish and Romani women, who either directly died or suffered permanent injuries and infections. About 700 women were also successfully sterilized.

Himmler wanted to know how much time it would take to sterilize 1000 Jewish women in that way. Clauberg's answer was satisfactory: One doctor with 10 assistants should be able to conduct sterilization of a few hundred, or even a few thousand, Jews in one day.

POW, 1945–1955
When the Red Army approached the camp, Clauberg moved to Ravensbrück concentration camp to continue his experiments on Romani women. Soviet troops captured him there in 1945.

After the war in 1948, Clauberg was put on trial in the Soviet Union and was sentenced to 25 years in prison. In 1955, he was released (but not pardoned) by the Soviet Union under the Adenauer-Bulganin prisoner exchange agreement, with the final group of about 10,000 POWs and civilian internees.

Medical career, arrest and death, 1955–1957
He returned to West Germany, where he was reinstated at his former clinic based on his prewar scientific output. Bizarre behavior, including openly boasting of his "achievements" in "developing a new sterilization technique at the Auschwitz concentration camp", destroyed any chance he might have had of staying unnoticed. In 1955, after public outcry from groups of survivors, Clauberg was arrested. He died before trial on 9 August 1957 in Kiel, Germany.

Clauberg test
The Clauberg test is an obsolete bioassay to assess progestational activity based on the conversion of proliferative endometrium to secretory endometrium in immature rabbits.

title: Carl Clauberg


text:
1993–94 FA Premier League

The 1993–94 FA Premier League (known as the FA Carling Premiership for sponsorship reasons) was the second season of the FA Premier League, the top division of professional football in England. Manchester United won the league by eight points over nearest challengers Blackburn Rovers, their second consecutive league title. Swindon Town finished bottom of the league in their first season of top-flight football and were relegated along with Sheffield United and Oldham Athletic. Manchester United also broke their own record of the most points in a season, set by themselves the previous season. This would be surpassed by Chelsea in the 2004–05 season.

New league sponsors
From the start of the 1993–94 season, the FA Premier League was sponsored by Carling Breweries.

Transfers
Just before the start of the season, Roy Keane became the most expensive footballer signed by an English football team. The 22-year-old Irish midfielder left relegated Nottingham Forest for Manchester United for a fee of £3.75 million.

During the 1993–94 season, many players were transferred between Premier League clubs for fees exceeding £1 million. They included David White (Manchester City to Leeds United), David Rocastle (Leeds United to Manchester City), Roy Wegerle (Blackburn Rovers to Coventry City) and Tim Flowers (Southampton to Blackburn Rovers). At £2.5 million, Flowers became the most expensive goalkeeper in English football.

Summary
Manchester United led the 1993–94 Premier League for almost all of the season, eventually finishing as champions eight points ahead of runners-up Blackburn Rovers. They also won the FA Cup after beating Chelsea 4–0 in the final, thereby becoming only the fourth team to achieve this feat in the 20th century (after Tottenham in 1961, Arsenal in 1971 and Liverpool in 1986). Their lead of the Premier League stood at 11 points by the end of October and peaked at 16 points at one stage, but a run of bad results in March was followed by defeat at Blackburn at the beginning of April, which meant that they now led the league merely on goal difference. A return to form towards the end of April then saw United seal the league title with two games still to play.

Norwich City, Leeds United, Newcastle United, Everton and Aston Villa were among the sides who showed promise early in the season before Manchester United established a runaway lead. Norwich reached the third round of the UEFA Cup after famously beating Bayern Munich in the second round, but their league form slumped after manager Mike Walker departed to Everton in January, and the Norfolk side finished 12th. Everton's brief lead of the league in the opening stages of the season was followed by a slump in form, and manager Howard Kendall stepped down at the beginning of December with the Toffees now in the bottom half of the table. They only narrowly avoided relegation on the final day of the season. Aston Villa finished a disappointing 10th in the league, but won the Football League Cup for the fourth time.

Finishing runners-up in the Premier League were Blackburn Rovers, whose top scorer Alan Shearer found the net 31 times in the league. In third place came Newcastle United, whose 22-year-old striker Andy Cole was the Premier League's leading scorer with 34 goals in 40 games, with a total of 41 goals in all competitions. In fourth place came Arsenal, who achieved success in European competition with a 1–0 win over Parma in the Cup Winners' Cup final.

Swindon Town managed just five league wins all season and were relegated in bottom place having conceded 100 league goals in 42 games; their record for the most goals conceded in a Premier League season would last for three decades before it was surpassed by Sheffield United in 2024. Oldham Athletic, who had avoided relegation on goal difference the previous season, were relegated on the final day of the season after failing to win at Norwich City. The final relegation place went to Sheffield United, who were relegated from the top flight after a 3–2 defeat at Chelsea, with the winning goal coming in injury time (a draw would have been enough to survive, and a loss would have still been enough had Everton not won their final match, 3–2 at home to Wimbledon after coming from 0–2 down). Ipswich Town, who failed to win any of their final 11 games, avoided relegation by holding Blackburn to a goalless draw at Ewood Park, and were less than a minute from being relegated, only to be saved by Chelsea’s late win over Sheffield United.

Teams
Twenty-two teams competed in the league – the top nineteen teams from the previous season and the three teams promoted from the First Division. The promoted teams were Newcastle United, West Ham United and Swindon Town. Newcastle United and West Ham United returned to the top flight after absences of four and one year respectively, while Swindon Town played in the top flight for the first and only time. They replaced Crystal Palace, Middlesbrough and Nottingham Forest, who were relegated to the First Division after their top flight spells of four, one and sixteen years respectively.

Personnel and kits
(as of 8 May 1994)

Hat-tricks

 * Note: 4 – player scored 4 goals; (H) – Home; (A) – Away

Player

 * Most yellow cards: 10
 * 🏴 Dane Whitehouse (Sheffield United)

 * Most red cards: 2
 * 🇫🇷 Eric Cantona (Manchester United)
 * 🏴 Chris Makin (Oldham Athletic)

Club

 * Most yellow cards: 44
 * Sheffield United

 * Fewest yellow cards: 12
 * Coventry City

 * Most red cards: 4
 * Oldham Athletic
 * Sheffield United

 * Fewest red cards: 0
 * Blackburn Rovers
 * Coventry City
 * Everton
 * Ipswich Town
 * Leeds United
 * Manchester City
 * Wimbledon

title: 1993–94 FA Premier League


text:
Eduard Schönfeld

Eduard Schönfeld (22 December 1828 – 1 May 1891) was a German astronomer.

Education
Schönfeld was born at Hildburghausen, in the Duchy of Saxe-Meiningen, where he had a distinguished career at the gymnasium. On leaving the gymnasium, he desired to devote himself to astronomy, but abandoned the idea in deference to his father's wishes. He went first to Hanover, and afterwards to Kassel to study architecture, for which he seems to have had little inclination. 1849 found him studying chemistry under Bunsen at Marburg, where his love for astronomy was revived by Gerling's lectures.

In 1851 he visited the Bonn Observatory and studied astronomy under Friedrich Wilhelm Argelander. In 1853 he was appointed assistant, and in the following year won a doctor's degree with his treatise Nova elementa Thetidis. At Bonn he took an important part in preparing the Durchmusterung of the northern heavens. He took up the investigation of the light-changes in variable stars, devoting to this work nights which, on account of moonlight, were unsuitable for zone observations. The results of these researches were published in the ''Sitz. Berich. Wien. Akad.'' vol. xlii.

Mannheim Observatory
For a short time he was a Privatdozent at Bonn, but in 1859 he was appointed director of the Mannheim Observatory. The instrumental equipment of that observatory was somewhat antiquated, his largest telescope being a small refractor of 73 lines aperture, but he selected a line of work to suit the instruments at his disposal, observing nebulae and variable stars and keeping a watch on comets and new planets. The results of his observations of nebulae are contained in two catalogues published in the Astronomische Beobachtungen der Grossherzoglichen Sternwarte zu Mannheim, 1st and 2nd parts (1862 and 1875), and those of his variable star observations appeared in the Jahresberichte des Mannheimer Vereins für Naturkunde, Nos. 32 and 39 (1866 and 1875).

Bonn Observatory
On the death of Argelander, which occurred on 17 February 1875, Schönfeld was appointed to succeed him as director of the Bonn Observatory, and soon after his appointment he began his last and greatest piece of work, the extension, on Argelander's plan, of the survey of the heavens down to 23 degrees of south declination. The experience gained on the northern survey under Argelander's direction enabled Schönfeld to introduce some improvements in the methods employed, which increased the accuracy of this work, which was practically accomplished in March 1881, some revision only remaining to be done. These zone observations afforded 363,932 separate places of stars, and form the groundwork of the catalogue of 133,659 stars between 2 and 23 degrees south declination, which was published in 1886 as the eighth volume of the Bonn observations.

Affiliations
Schönfeld was a member of the Astronomische Gesellschaft from its foundation in 1863, being a member of council up to 1869, and in 1875 becoming editor of its publications and secretary in conjunction with Winnecke. In 1878 he was elected a Foreign Associate of the Royal Astronomical Society.

Legacy
Minor planet 5926 Schönfeld is named in his honor.

title: Eduard Schönfeld


text:
Heteromyidae

Heteromyidae is a family of rodents consisting of kangaroo rats, kangaroo mice, pocket mice and spiny pocket mice. Most heteromyids live in complex burrows within the deserts and grasslands of western North America, though species within the genus Heteromys are also found in forests and their range extends as far south as northern South America. They feed mostly on seeds and other plant parts, which they carry in their fur-lined cheek pouches to their burrows.

Although they are very different in physical appearance, the closest relatives of the heteromyids are pocket gophers in the family Geomyidae.

Description
There are about fifty-nine members of the family Heteromyidae divided among six genera. They are all small rodents, the largest being the giant kangaroo rat (Dipodomys ingens) with a body length of 15 cm and a tail a little longer than this. In many species the tail is tufted and is mainly used for balance. Other adaptations include partially fused vertebrae in the neck, short fore limbs and much enlarged bullae (bubble-shaped bones in the skull). The skulls vary widely across the group but they are all thin and papery and do not have the robust cranial crests and ridges found on the skulls of members of the family Geomyidae. The skull has other peculiarities. There is an extra hole that penetrates the rostrum, distinctive occluded teeth and the masseter muscle, which moves the lower jaw, is set far forward on the snout, an arrangement found in squirrels, beavers, pocket gophers, heteromyids and a few other groups. The dental formula is teeth in total. In the kangaroo rats, the teeth continue to grow all the time, being worn away as the animal chews. The molars have two-lobed cusps. The upper incisors are grooved and the enamel on the molars is quickly worn away by chewing leaving the dentine exposed. In the kangaroo rats they are unrooted but in the pocket mice they have roots.

Fur-lined cheek pouches are a feature across the family Heteromyidae. They have openings near the mouth and extend backwards along the sides of the neck. The fur on the animal's body is in general short and fine and often matches in colour the soil of the region in which the animal lives, being some shade of buff, pale brown, reddish-brown or grey. The spiny pocket mice have coarser fur and spiky bristles on the back near the tail.

Distribution
Heteromyids are endemic to the western United States, Mexico, Central America and northwestern South America. They are creatures of open country, mostly specialising in prairies, arid lands and desert fringes, but the spiny pocket mice are found in both wet and dry tropical forests in Central and northwestern South America. During the Oligocene, the extent of arid lands across the United States was greater than it is today and these animals occurred more widely. Fossils of kangaroo rats are known from the Pliocene.

Behaviour
The kangaroo rats, kangaroo mice and pocket mice are adapted for life in deserts and other arid environments where they largely feed on dry seeds. Kangaroo rats have no need to drink because they are able to extract sufficient water from metabolising their food, obtaining half a gram of water from each gram of seeds eaten. They carry most of the seeds they find back to their burrows in exterior cheek folds lined with fur rather than in cheek pouches inside the mouth as do hamsters. This is because carrying the food in the mouth would involve wetting it and moisture needs to be conserved as much as possible in dry environments. Most species store the seeds they gather in special chambers in the burrow where they absorb moisture from the humid air. Others, such as Merriam's kangaroo rat, bury them in shallow caches in the open air.

It has been found that there is little hoarding done in the winter but that food is most commonly stored in the autumn and spring. Heteromyids use sight and olfactory clues to locate possible food and then use their fore-feet to manipulate objects. Kangaroo mice make greater use of clumped food where wind or water has concentrated seeds in shallow depressions or around rocks while pocket mice hunt around under vegetation or debris for individual food items. It has been found that pocket mice forage more efficiently than kangaroo rats and this is thought to be due to the fact that they handle their finds more and are better able to distinguish between food and non-food items.

These animals excavate long burrow systems with passages, chambers and multiple entrances. They are largely nocturnal, feeding and moving about at night and resting deep in their burrows during the day. Here it is cooler and more humid which conserves moisture and the animals may temporarily block the entrances to augment this. They are able to concentrate their urine to a viscous consistency which further reduces water loss. Under extreme conditions, some are able to aestivate in chambers under ground.

Kangaroo rats have large hind feet with long metatarsals and no first digits. With these they bound around not using their fore feet at all for locomotion. Pocket mice are smaller and can also move with leaps but they normally run around on four limbs. Members of the genus Heteromys, the spiny pocket mice, move around on all fours and do not leap at all.

Ecology
Kangaroo rats and pocket mice form a part of the diet of many predatory creatures. They are eaten by foxes, coyotes, snakes and birds. They have acute hearing and can detect the approaching swoop of an owl or the movements of a snake. Many can leap to avoid the predators as they seek the safety of their burrows. The largest kangaroo rats can leap 2.75 m in a single bound.

In the Sonoran Desert there are many closely related species of heteromyid mice and rats. Each has its own niche in the environment which means that they do not unnecessarily compete with each other for the limited available resources. Bailey's pocket mouse climbs into plants and bushes in order to find seeds and berries still attached to the plant. It is the only species able to eat the wax found inside the seeds of the jojoba plant. Merriam's kangaroo rat primarily moves rapidly from one bush to another gathering seed but overlooking anything lying on the desert floor. The desert pocket mouse forages across the open desert floor and gathers seeds that have fallen to the ground.

Taxonomy

 * Family Heteromyidae
 * Subfamily Heteromyinae — spiny pocket mice
 * Genus Heteromys
 * Panamanian spiny pocket mouse, Heteromys adspersus
 * Trinidad spiny pocket mouse, Heteromys anomalus
 * Southern spiny pocket mouse, Heteromys australis
 * Overlook spiny pocket mouse, Heteromys catopterius
 * Desmarest's spiny pocket mouse, Heteromys desmarestianus
 * Gaumer's spiny pocket mouse, Heteromys gaumeri
 * Goldman's spiny pocket mouse, Heteromys goldmani
 * Mexican spiny pocket mouse, Heteromys irroratus
 * Nelson's spiny pocket mouse, Heteromys nelsoni
 * Cloud-dwelling spiny pocket mouse, Heteromys nubicolens
 * Paraguaná spiny pocket mouse, Heteromys oasicus
 * Mountain spiny pocket mouse, Heteromys oresterus
 * Painted spiny pocket mouse, Heteromys pictus
 * Salvin's spiny pocket mouse, Heteromys salvini
 * Jaliscan spiny pocket mouse, Heteromys spectabilis
 * Ecuadoran spiny pocket mouse, Heteromys teleus
 * Subfamily Dipodomyinae — kangaroo rats and mice
 * Genus Dipodomys — kangaroo rats
 * Agile kangaroo rat, Dipodomys agilis
 * California kangaroo rat, Dipodomys californicus
 * Gulf Coast kangaroo rat, Dipodomys compactus
 * Desert kangaroo rat, Dipodomys deserti
 * Texas kangaroo rat, Dipodomys elator
 * San Quintin kangaroo rat, Dipodomys gravipes
 * Heermann's kangaroo rat, Dipodomys heermanni
 * Giant kangaroo rat, Dipodomys ingens
 * Merriam's kangaroo rat, Dipodomys merriami
 * Chisel-toothed kangaroo rat, Dipodomys microps
 * Nelson's kangaroo rat, Dipodomys nelsoni
 * Fresno kangaroo rat, Dipodomys nitratoides
 * Ord's kangaroo rat, Dipodomys ordii
 * Panamint kangaroo rat, Dipodomys panamintinus
 * Phillips's kangaroo rat, Dipodomys phillipsii
 * Dulzura kangaroo rat, Dipodomys simulans
 * Banner-tailed kangaroo rat, Dipodomys spectabilis
 * Stephens's kangaroo rat, Dipodomys stephensi
 * Narrow-faced kangaroo rat, Dipodomys venustus
 * Genus Microdipodops — kangaroo mice
 * Pale kangaroo mouse, Microdipodops pallidus
 * Dark kangaroo mouse, Microdipodops megacephalus
 * Subfamily Perognathinae — pocket mice
 * Genus Perognathus
 * White-eared pocket mouse, Perognathus alticola
 * Arizona pocket mouse, Perognathus amplus
 * Olive-backed pocket mouse, Perognathus fasciatus
 * Plains pocket mouse, Perognathus flavescens
 * Silky pocket mouse, Perognathus flavus
 * San Joaquin pocket mouse, Perognathus inornatus
 * Little pocket mouse, Perognathus longimembris
 * Merriam's pocket mouse, Perognathus merriami
 * Great Basin pocket mouse, Perognathus parvus
 * Genus Chaetodipus
 * Little desert pocket mouse, Chaetodipus arenarius
 * Narrow-skulled pocket mouse, Chaetodipus artus
 * Bailey's pocket mouse, Chaetodipus baileyi
 * California pocket mouse, Chaetodipus californicus
 * Dalquest's pocket mouse, Chaetodipus dalquesti
 * Chihuahuan pocket mouse, Chaetodipus eremicus
 * San Diego pocket mouse, Chaetodipus fallax
 * Long-tailed pocket mouse, Chaetodipus formosus
 * Goldman's pocket mouse, Chaetodipus goldmani
 * Hispid pocket mouse, Chaetodipus hispidus
 * Rock pocket mouse, Chaetodipus intermedius
 * Lined pocket mouse, Chaetodipus lineatus
 * Nelson's pocket mouse, Chaetodipus nelsoni
 * Desert pocket mouse, Chaetodipus penicillatus
 * Sinaloan pocket mouse, Chaetodipus pernix
 * Baja pocket mouse, Chaetodipus rudinoris
 * Spiny pocket mouse, Chaetodipus spinatus

Hafner et al. (2007) summarized the molecular and morphological data to date and proposed the following taxonomy:

Finding that the formerly recognized genus Liomys is paraphyletic, they subsumed it into Heteromys. Most authorities prior to this (Alexander and Riddle, 2005; Patton, 2005) treated Liomys as a separate genus.

title: Heteromyidae


text:
Aurélien Scholl

Aurélien Scholl (July 13, 1833 in Bordeaux – April 16, 1902), was a French author and journalist.

He was successively editor of Le Voltaire and of L'Écho de Paris. He wrote largely for the theatre, as well as a number of novels dealing with Parisian life. He was included in the painting Music in the Tuileries, by Manet, as one of the flâneurs of the day.

Works

 * Lettres à Mon Domestique (1854)
 * L'Outrage (1867)
 * Fleurs d'Adultère (1880)
 * L'Orgie Parisienne (1883)
 * La Farce Politique (1887)
 * Les Ingénues de Paris (1893)
 * Denise (1894)
 * Tableaux Vivants (1896)
 * Les petits papiers. Comédie en un acte (1897)
 * L'esprit d'Aurelien Scholl (1925) edited by Léon Treich

title: Aurélien Scholl


text:
Brocken Transmitter

The Brocken Transmitter (Sender Brocken) is a facility for FM- and TV-transmitters on the Brocken, the highest mountain in Northern Germany.

The facility includes two transmission towers. The old tower was built between 1936 and 1937. It is 53 metres high (including its antenna mast, which no longer exists, it had a height of 95 metres) and has an observation deck, which can be reached by elevator. This tower was intended to be used after 1939 for TV transmissions to central Germany, but due to the beginning of World War II, it was transformed into a radar facility. Unlike most modern TV towers, the old tower looks like a block of flats with a square cross section. The arrangement of the windows in the observation deck is similar to those in the restaurant in the Radio tower Berlin.

In 1973 a new TV tower was built on Brocken. This 123-metre, freestanding steel-tube tower stands on three legs, which hold shafts for cable and stairways for personnel access. Above the legs are three decks for directional radio transmission aerials. The new TV tower is not accessible to the public.

While Germany was divided into East and West, the Brocken transmitter was used for TV and FM-transmissions, even though it lay in the restricted area of the east-west frontier (on the Eastern Side). Its location so close to the border enabled it to be received in parts of the West.

In the first half of the 1990s the transmitting aerial of the old tower was removed and replaced by a radome holding air traffic control radar equipment.

The Brocken Transmitter is property of Deutsche Telekom.

Digital television

 * ARD-MDR1 HD (DVB-T2), UHF channel 45 (vertical) 50 kW
 * ARD-MDR2 HD (DVB-T2), UHF channel 34 (vertical) 50 kW
 * ZDF HD (DVB-T2), UHF channel 37 (vertical) 50 kW

Analogue television (formerly)

 * Das Erste (originally DFF1), VHF channel E6 (Horizontal) 100 kW
 * ZDF, UHF channel 49 500 kW
 * MDR Fernsehen (originally DFF2), UHF channel 34 (Horizontal) 1000 kW

FM radio

 * MDR Sachsen-Anhalt, 94.6 MHz (60 kW)
 * MDR Jump, 91.5 MHz (100 kW)
 * MDR Kultur, 107.8 MHz (10 kW)
 * Deutschlandfunk Kultur, 97.4 MHz (100 kW)
 * 89.0 RTL, 89.0 MHz (60 kW)
 * Radio SAW, 101.4 MHz (100 kW)

title: Brocken Transmitter


text:
Talk:Scrying

Improvement of article
I have tried to improve this article by adding reliable sources. I removed some original research. HealthyGirl (talk) 01:44, 26 April 2016 (UTC)

the majority of this article seems to be intent on debunking rather than providing knowledge or history of the practice at its basest levels. articles of this nature typically do not have anywhere near as much emphasis on disproving or disavowing their subjects, as this is typically not overly required or wanted when someone is looking for information. there's also a sort of unpleasant tone that goes along with a few of the "points of contention" herein - indeed, i'm not entirely sure this is the proper place to debate anything. Passename666 (talk) 03:12, 22 December 2017 (UTC)

Tense
This edit, changed the entire article to past tense. Is this appropriate? I suspect that in is inappropriate for the section on "Modern-day traditions and fictions". Other views welcome. Martinevans123 (talk) 18:19, 4 November 2018 (UTC)
 * Feel free to undo the tense change. There seems no reason! RobP (talk) 21:59, 4 November 2018 (UTC)
 * Ok. Have restored long-standing version until we see any argument justifying. Martinevans123 (talk) 22:03, 4 November 2018 (UTC)

 * User:Martinevans123 The ip editor who changed the tense is a subtle disruptive vandal. Whilst changing tense in certain articles could be an innocent misunderstanding, other edits show this not to be the case. For instance this edit to Franz Kafka shows tense changed to past for certain elements, but conversely changed to present tense for elements that certainly require past, ie "Few of Kafka's works were are published during his lifetime"; " Kafka's unfinished works… were are ordered by Kafka to be destroyed…"

 * Then there's the ridiculous change to past in this edit to article Apitoxin: "Apitoxin or honey bee venom is was a bitter colorless liquid…"; "The main component is was melittin, amounting to 52%…"

 * The editor also enjoys incorrect capitalisation and inserting an apostrophe into possessive "its" (it's). These, and tense changes, and undoing reverts constitute the entirety of their output, there is nothing of use at all. I have spent a few hours undoing the damage and posted a warning on their talk page, I'd be glad if an admin could keep an eye on it. Thanks, Captainllama (talk) 22:07, 10 November 2018 (UTC)

 * Thanks for the update. I'll try to keep an eye on them with my updated scrying mirror. Martinevans123 (talk) 22:13, 10 November 2018 (UTC)

Scrying ...
William S. Burroughs spent hours just staring at his reflection in a small pool of water. He said that 'scrying' was the only way to see things as they really are. Attila911 (talk) 15:29, 7 June 2020 (UTC)

I reached this article from the article about Jakob Bohme who had a Divine vision when he "focused his attention" on a beam of light. I've never heard the term "scrying" before but it seems to me that Scrying is simply meditation on an external object rather than an internal point or chakra. So I think the article on Scrying should have some kind of reference to the articles on Meditation and on Attention.LFlagg (talk) 01:27, 24 January 2021 (UTC)

title: Talk:Scrying