text:
Musō Shinden-ryū

Musō Shinden-ryū (夢想神伝流) is a style of sword-drawing art (iaido) founded by Nakayama Hakudō (中山博道) in 1932. Nakayama Hakudō studied under Hosokawa Yoshimasa, a master of the Shimomura branch (下村派) of Hasegawa Eishin-ryū, and Morimoto Tokumi, a fellow student of Ōe Masaji of the Tanimura branch (谷村派). The name Musō Shinden-ryū most likely comes from the name given to the Shimomura branch by Hosokawa, Musō Shinden Eishin-ryū (無雙神傳英信流).

Particularities
The kata from Musō Shinden-ryū have a number of differences from the kata of its sister art, Musō Jikiden Eishin-ryū. Among the most visible are the manner in which the furikaburi (raising the sword overhead, sometimes called furikamuri) and the nōtō (sheathing) are done. Both arts also differ from many other iaijutsu schools in that the kiai is performed silently, without hassei (shouting).

Furikaburi
After striking with one hand, primarily on nukitsuke (cutting as one draws the sword out), the sword is brought to a position about ten centimeters above the left shoulder, blade edge up, and with the point facing backwards. The movement resembles a thrust to the rear. Unlike in Musō Jikiden Eishin-ryū, the sword does not fall off behind the back but always stays over shoulder height. The right hand then raises the sword overhead while the left hand takes its place on the hilt, thus entering in the jōdan stance or kamae. The sword should now be right in the middle line of the body, with the tip raised forty-five degrees upward (Chuden) or level with the ground (Shoden) and your left hand hovering just above your forehead.

Nōtō
In Musō Shinden-ryū, the sheathing is performed horizontally with the blade outwards. Only when the sword is about two-thirds of the way in the saya is the edge turned to face upwards. The blade and saya should cross your center line at a 45-degree angle while sheathing.

Shoden (初伝)
The word "Shoden", which can be translated as the "first transmission", consists of the kata of Ōmori-ryū iaijutsu plus one kata variation exclusive to Musō Shinden-ryū. The kata start from the seiza sitting posture. This series of kata became the first to be learned when the 17th headmaster of the Tanimura branch, Ōe Masamichi, reorganized and rationalized the curriculum of Hasegawa Eishin-ryū at the start of the 20th century. The kata Ryūtō, which involves the Ukenagashi technique, is often considered as the most difficult kata of the Omori set. The seventh kata, Juntō was created neither for dueling nor for self-defense, but to serve as kaishakunin.

According to his own memoirs, Nakayama Hakudō invented the twelfth kata, In'yō Shintai Kaewaza, as a variation on the fifth kata In'yō Shintai.

The following is the order given by Yamatsuta. In some schools, the order of the last two kata are reversed.

 * 01. Shohattō (初発刀)
 * 02. Satō (左刀)
 * 03. Utō (右刀)
 * 04. Ataritō (当刀)
 * 05. In'yō Shintai (陰陽進退)
 * 06. Ryūtō (流刀)
 * 07. Juntō (順刀)
 * 08. Gyakutō (逆刀)
 * 09. Seichūtō (勢中刀)
 * 10. Korantō (虎乱刀)
 * 11. In'yō Shintai Kaewaza (陰陽進退替業)
 * 12. Battō (抜刀)

Chūden (中伝)
The word "Chūden" can be translated as the "middle-transmission" and consists of ten techniques from Hasegawa Eishin-ryū. This series of kata is executed from the tachihiza (more commonly called tatehiza) sitting position. In contrast to the first series of kata, the enemy is considered to be sitting very close and thus the primary goal of the chūden techniques is to create proper cutting distance (kirima) by stepping back instead of forward.

Ōe Masamichi is credited with developing the hayanuki (quick draw) exercise. In this style of training, the practitioner executes all ten techniques in a row. Two versions of hayanuki exist. In one version, both the left and right hands are used to execute the movements, just as in the normal practice. The second version involves drawing the sword with only the right hand, as if you were on a horse. This kind of practice is not done in formal presentations.

 * 01. Yokogumo (横雲)
 * 02. Toraissoku (虎一足)
 * 03. Inazuma (稲妻)
 * 04. Ukigumo (浮雲)
 * 05. Yamaoroshi (山颪)
 * 06. Iwanami (岩浪)
 * 07. Urokogaeshi (鱗返)
 * 08. Namigaeshi (浪返)
 * 09. Takiotoshi (滝落)
 * 10. Nukiuchi (抜打)

Okuden (奥伝)
The word "Okuden" can be translated as the "inner transmission". Oku-iai, as it is also called, is divided into two groups: suwari-waza (sitting techniques) and tachi-waza (standing techniques). As in Chūden, the sitting techniques are performed from tatehiza.

Suwari-waza (座業) * Despite the fact to be a sitting-form, in an Enbu the Itomagoi form is usually performed after the execution of all standing forms so the kenshi is ready to begin the finishing reiho, like Battô in Omori-ryu and Nukiuchi in Hasegawa Eishin Ryu.
 * 01. Kasumi (霞) – Mist
 * 02. Sunegakoi (脛囲) – Covering the shin
 * 03. Shihogiri (四方切) – Cutting four corners
 * 04. Tozume (戸詰) – Across the screen doors
 * 05. Towaki (戸脇) – Along the screen doors
 * 06. Tanashita (棚下) – Under the shelf
 * 07. Ryozume (両詰) – Obstacles on both sides
 * 08. Torabashiiri (虎走) – Running Tiger
 * 09. *Itomagoi (暇乞) – Request Leave of Absence [Three forms]

Tachi-waza (立業) * This is believed to be a kata that Oe Masamichi Sensei discarded when he re-organized the old tradition. It is generally not performed.
 * 01. Yukitsure (行連) – Escort
 * 02. Rentatsu (連達) – Escort
 * 03. Somakuri (惣捲) – Cutting the multiple opponents
 * 04. Sodome (総留) – One-handed cuts
 * 05. Shinobu (信夫) – Stealth
 * 06. Yukichigai (行違) – Passing by
 * 07. Sodesurigaeshi (袖摺返) – Flipping the sleeves
 * 08. Moniri (門入) – Entering the gate
 * 09. Kabezoi (壁添) – Along the walls
 * 10. Ukenagashi (受流) – Block and deflect
 * 11. *Oikakegiri (追掛斬) – Pursue & Cut Down
 * 12. Ryoushihikitsure (両士引連) – Accompanied Journey

Kumitachi
The paired Kumitachi techniques (the kenjutsu part of the curriculum) are rarely taught today. Tachi Uchi-no-Kurai and Tsumeiai-no-Kurai are the series most often taught.

Tachi Uchi-no-Kurai (太刀打之位)
 * 1. Deai (出合)
 * 2. Tsukekomi (附込)
 * 3. Ukenagashi (請流)
 * 4. Ukeire (請入)
 * 5. Tsukikage (月影)
 * 6. Suigetsutō (水月刀)
 * 7. Dokumyōken (独妙剣)
 * 8. Zetsumyōken (絶妙剣)
 * 9. Shinmyōken (心明剣)
 * 10. Uchikomi (打込)

Tsume Iai-no-Kurai (詰居合之位)
 * 1. Hassō (発早・發早・八相)
 * 2. Kobushidori (拳取)
 * 3. Iwanami (岩浪)
 * 4. Yaegaki (八重垣)
 * 5. Urokogaeshi (鱗返)
 * 6. Kuraiyurumi (位弛)
 * 7. Tsubamegaeshi (燕返)
 * 8. Gansekiotoshi (眼関落)
 * 9. Suigetsutō (水月刀)
 * 10. Kasumiken (霞剣)

title: Musō Shinden-ryū


text:
Talk:Dachshund

Doxon and doxie as nicknames for a dachshund
Are "doxon" or "doxie" valid nicknames for a "dachshund" ?

"Doxie" has been used for ever. It's a easier to read version of "dachsie" which is pronounced fairly similarly and is short for "dachshund."

"Doxon," "daschund," "dotson," "doxen," and "dash hound" are all misspellings/mispronunciations, with "dash hound" being probably the most common one. Just because it is common does not mean it is "equally correct." It is not a regionalism like, say, "aluminium" is, or a dialect difference such as speakers of AAVE using "axe" instead of "ask." An earlier comment suggested it was valid because "I've seen it used on Etsy." Etsy does not spell check its users' posts before they go live. Either the seller on Etsy cannot spell "dachshund," or they are banking on their buyers not being able to spell it and want to optimize their hits in the search.

Jjjjjjjjjj (talk) 02:23, 23 April 2018 (UTC)
 * Unfortunately all that is Original research. ... Thanks,   CJ [a Kiwi] in    Oz   02:58, 23 April 2018 (UTC)
 * Are Etsy and eBay staff using the terms, or are users using the terms? If it's the latter, then it's not a reliable source (although it could be indicative of how the terms are being used). Let's find a better source before including. —C.Fred (talk) 15:08, 23 April 2018 (UTC)

Okay, I just started working on "doxie" first of all.

Already one sees that currently on Wikipedia for "doxie" there is a hatnote back to dachshund.

So I did a search for: doxie dachshund on HighBeam Research (I wasn't aware of HighBeam's partnership with Wikipedia).

There were 54 results listed, and so I'll just include here a few of the most recent.

Being sufficiently recent for all these they showed up without needing to sign up for the partnership with HighBeam.

1. This one is from The Gazette (Colorado Springs) a Pulitzer Prize winning newspaper based in Colorado Springs, Colorado:

Hot dog is top dog when these Colorado Springs dachshund owners get together, (September 10, 2017)

2. This one is from a paper called the Northwest Herald:

Dachshund dogs to race in Sunset Doxie Derby in Lake in the Hills (August 25, 2017)

3. This one is from the Los Angeles Daily News:

Buck the Dachshund puppy is ready to play (August 18, 2017)

4. So this one is from The Spokesman-Review

Breast cancer survivors find support at 10th Komen Race for the Cure (April 27, 2015)

Please feel free to post any thoughts on that.

Jjjjjjjjjj (talk) 01:33, 30 April 2018 (UTC)

 * For a similar search of: doxon dachshund on HighBeam there's 0 results. So that's evidence that doxie has gotten to be more prevalent than doxon. Jjjjjjjjjj (talk) 01:40, 30 April 2018 (UTC)

 * And a search for just doxon on HighBeam is giving 26 results, but it doesn't seem that any of them are references to the dachshund dog breed. Jjjjjjjjjj (talk) 01:45, 30 April 2018 (UTC)

Name capitalization question
Is there a reason why dachshund in the text (as well as on at least one other page is lowercase? It looks like other dog names, even those not including a modifier that usually takes a capital (French, English, etc.), are capitalized: I didn't want to make a change in case this was a particular element of how the breed is discussed. I really don't have a dog in this fight, to use a related expression; I just noticed the inconsistency and was wondering why it existed. nwatra (talk) 14:34, 15 September 2018 (UTC)
 * Bulldog
 * Border Collie
 * Pug
 * etc.
 * Per MOS:COMMONNAMES, common names ... except there they contain proper names or when such name starts in a sentence use lower case initial letters. I am assuming this applies to dogs. Here's a link that discusses caps in dog names: http://www.onlinegrammar.com.au/dog-breeds-and-capital-letters/. Seems to be "a trend towards more minimal capitalization" in the dog world, however, the names of animal breeds are often capitalized in publications produced by official breeders. As far as WP is concerned, I think we have to adhere to the "rules" set out in MOS:COMMONNAMES. So, dog names should not be capitalized unless they include a proper name or at the beginning of a sentence.-- BC talk to me 22:16, 15 September 2018 (UTC)
 * Thanks. So it looks like a fair number of the other dog pages (and some cats and horses, based on some quick searching) are out of sync with MOS:COMMONNAMES. (Looks like this has been an question for a while; I feel like bringing them into alignment will be a big task. nwatra (talk) 20:33, 17 September 2018 (UTC)
 * WP should include something clear about caps and dog/cat/horse breeds. Consensus should be reached, and such consensus should relate to proper grammar (e.g. see above link) and the fact that there is supposedly a trend towards more minimal capitalization. IMO, WP should not adopt a capitalization policy based on the fact that official breeders' publications most often capitalize their breeds.-- BC talk to me 21:21, 17 September 2018 (UTC)

External links part modified
Just added a link to educational article with a video about Dachshund. I think it will be very interesting for kids (video) and adultsMark.barkan (talk) 11:09, 2 December 2020 (UTC)

Capitalization (or not) of military ranks
Re: German field marshal Erwin Rommel

A military rank or job title is capitalized when followed by a person's name to form a title, but not when modified. MOS:MILTERMS says "Military ranks follow the same capitalization guidelines as given under § Titles of people", and that section says "For fuller details, see Wikipedia:Manual of Style/Biographies § Titles of people." The example there (in MOS:JOBTITLES) shows that a modified title is not capitalized: "Mao met with US president Richard Nixon in 1972." Of course, if not modified by the nationality, it would be changed to "Mao met with President Richard Nixon in 1972.", with "President" capitalized. So MOS:JOBTITLES takes precedence over the other two abridged sections of the MoS. Chris the speller  yack  00:43, 27 October 2022 (UTC)

German breeding ban contreversy
Hi

I wondered if it might be appropriate to add a bit on the controversy this year about a German bill on dog breeding which was misinterpreted as a potential ban on the Dachshund. It could go under 'Symbol of Germany', as the German Kennels Association made a big deal about it and launched a petition.

Source: https://www.bbc.co.uk/news/world-europe-68689823

Thanks, TheDelix (talk) 19:28, 12 April 2024 (UTC)

 * Doesn't seem too relevant to dachshunds given the bill isn't going to target them (despite the description applying exactly to them), if the bill did target them it could be relevant.
 * Unrelated but that BBC article is a great example of how normally reliable sources are absolutely terrible when it comes to coverage of animal breeds and animal health. Traumnovelle (talk) 20:47, 12 April 2024 (UTC)
 * That is a good point @Traumnovelle - thank you.
 * The truth might be that the bill has little to do with the Dachshund, but it may be useful to talk about the controversy as in media etc. it was definitely seen as specifically about the Dachshund.
 * Perhaps it would be a good way of correcting this particular misinformation?
 * Thanks, TheDelix (talk) 21:14, 12 April 2024 (UTC)
 * I doubt this will be an event that lasts in people's mind, it was a short lived outrage shortly quelled with a statement. If the bill does ultimately result in a ban on dachshund breeding it'd be worth including but unless there's some sort of change to German breed standards like in the aftermath of Pedigree Dogs Exposed then this event will likely be nothing more than just a temporary outrage swiftly forgotten. Traumnovelle (talk) 21:18, 12 April 2024 (UTC)
 * Ok agreed
 * Thanks, TheDelix (talk) 21:24, 12 April 2024 (UTC)

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

title: Talk:Dachshund


text:
Louis Alterie

Louis "Two Gun" Alterie (August 2, 1886 – July 18, 1935), born Leland A. Varain, and aka "Diamond Jack Alterie", was a Californian who became a notorious hitman for the Chicago North Side Gang during the early years of Prohibition.

Early years
Alterie was born Leland A. Varain in Northern California on August 2, 1886. He moved to Chicago as a young man, and eventually joined the predominantly Irish North Side Gang, which was headed by Dean O'Banion. Befitting his California background, Alterie was a Western enthusiast who wore a ten-gallon hat and two holstered Colt .45 revolvers and owned a ranch near Sedalia, Colorado. As well as being a top gunman for the North Side Gang, he also formed the Theatrical Janitors' Union and used his position as union president to extort money from theater owners.

Gang war with Chicago Outfit
In the early 1920s, the North Side Gang's greatest rival was the Chicago Outfit, run first by John "The Fox" Torrio and then Al Capone. During this period a series of disputes over bootlegging territories and other matters led the North Siders into conflict with the Outfit and its allies, the Genna brothers of Little Italy. Alterie by some reports killed more than 20 Outfit and Genna gang members during this conflict which had erupted into a full-scale gang war in 1924 when O'Banion was murdered by Outfit gunmen in his floral shop on State Street in Chicago.

Exile to Colorado
Alterie was considered the "flake" of the O'Banion gang. He once feigned insanity prior to a murder trial to give his criminal associates time to kill or intimidate witnesses. His act was so convincing that many considered him actually insane.

Incensed by O'Banion's murder, Alterie publicly challenged his killers to a shootout on State Street. However, cooler heads within the North Side Gang were upset by Alterie's bravado; they worried that this would result in unwanted attention from both rival gangs and Chicago officials. Moran convinced Alterie to leave Chicago until it was safe to return.

Alterie chose to go to his Moonridge ranch in Colorado. However, he soon attracted unwanted attention from the Colorado authorities. In November 1932, Alterie was involved in a gangland shooting in Glenwood Springs, Colorado. In February 1933, as part of a sentencing agreement, Alterie agreed to leave Colorado and not come back for a period of five years. At this point, Alterie returned to Chicago. Over the next few years, he briefly returned to Colorado several times, but kept his residence in Chicago.

Return to Chicago and death
During Alterie's absence from Chicago, the gang war between the North Side Gang and the Chicago Outfit continued. In 1929, the Outfit had killed seven North Side gang members in the infamous St. Valentine's Day Massacre. The Chicago Outfit was now in charge.

Other than a vagrancy arrest in Chicago in 1933, Alterie kept a low profile. However, that changed in June 1935 when he was forced to testify against Ralph "Bottles" Capone, Al Capone's brother, on a tax evasion charge. Louis Alterie was killed on July 18, 1935, while leaving his North Side Chicago apartment. Ironically, Alterie was shot by snipers lying in wait for him across from his apartment, using a technique Alterie had pioneered during Prohibition.

The lead story in that afternoon's Chicago Daily News, written by Robert J. Casey, began: "'Two-Gun Louie'" Alterie came out of the shadows of the alky racket long enough to die. He was shot down—in the technique he himself had done so much to perfect." A sidebar by Clem Lane, a legendary city editor, began: "This is the story of 'Two-Gun Louie' Alterie, one-time pugilist, one-time policeman, one-time robber, one-time lieutenant of Johnny Torrio and Dion O'Banion, erstwhile rancher and union business agent, and today the subject of a coroner's inquest as to who shot him and why not sooner."

He was buried in an unmarked grave in Forest Lawn Memorial Park Cemetery in Glendale, California.

title: Louis Alterie


text:
Royal University of Bhutan

The Royal University of Bhutan (Dzongkha: འབྲུག་རྒྱལ་འཛིན་གཙུག་ལག་སློབ་སྡེ་; Wylie: 'brug rgyal-'dzin gtsug-lag-slob-sde), founded on June 2, 2003, by a royal decree, is the national university of Bhutan. It is the first and the oldest university in Bhutan.

Colleges
The university was established to consolidate the management of tertiary education in Bhutan. It is a decentralized university with nine constituent colleges and two affiliated college spread across the kingdom. The principle which influenced the development of a university system was the government's priority for equitable development. The colleges of the university are:
 * College of Natural Resources (CNR) in Lobesa, Punakha
 * College of Science and Technology (CST) in Rinchhending, Phuntsholing
 * Gaeddu College of Business Studies (GCBS) in Gedu, Chukha
 * College of Language and Culture Studies (CLCS) in Taktse, Trongsa.
 * Jigme Namgyel Engineering College (JNEC) in Dewathang, Samdrup Jongkhar
 * Paro College of Education (PCE) in Paro
 * Royal Thimphu College (RTC) in Ngabiphu, Thimphu (affiliated college)
 * Norbuling Righter College, paro (affiliated college)
 * Samtse College of Education (SCE) in Samtse
 * Sherubtse College in Kanglung, Trashigang
 * Gyalpozhing College of Information Technology in Gyalpozhing, Mongar

The university maintains a connection with other universities which include the University of New Brunswick in Canada, Naropa University and the School for International Training in the United States, the University of Salzburg in Austria, and the University of Delhi in India, in the areas of research, student exchange and internship programs for students and faculty.

Jigme Khesar Namgyel Wangchuck, the fifth king of Bhutan, is the chancellor. Nedip Dorji, an Oxford graduate, is the current vice chancellor and handles the day-to-day administration of the university system.

The Centre for Bhutan Studies (CBS) in Thimphu, originally slated to become a member institution of the university, has retained its autonomous status.

Administration
Based on the distributed model with campuses of the colleges forming the core element of the university, the office of the vice-cancellor at the center is responsible for central coordination while the constituent member colleges look after academic functions of teaching and research within their respective colleges. Located at Mothithang, Thimphu, the office of the vice-chancellor consists of the departments of registry, academic affairs, planning and resources, and research and external relations.

The twofold objective of the university as stated in the royal charter (RUB 2003, p. 3) is to develop and provide programmes of study at tertiary education level, of relevance and good quality which will fulfill the needs of the country for an educated and skilled population; and to promote and conduct research, to contribute to the creation of knowledge in an international context and to promote the transfer of knowledge of relevance to Bhutan.

Programmes
The Royal University of Bhutan offers programmes across its campuses in eight broad curriculum areas. These include:
 * teacher education
 * business and management
 * engineering and physical sciences
 * computing and information science
 * biological sciences and agriculture
 * health sciences
 * humanities and social sciences
 * Dzongkha language and literature

There are plans to include programmes in arts and design, media and mass communication, Bhutanese history and culture, gross national happiness, counseling and Buddhist studies in the colleges.

Most programmes are full-time, although the two colleges of education, Sherubtse College, and the Institute of Language and Culture Studies, offer part-time and distance education programmes. Some programmes offered at Sherubtse College provide their students with freedom to cross departmental boundaries with double degree programmes.

The university offers diploma, degree, and honours degree courses of study.

Diploma
The diploma programme consists of 240 credits out of which at least 100 credits are at second year degree level. The programme usually takes over two years of full-time study, or more, if it consists of more than 120 credits.

The diploma may be an interim award in a degree programme, in which case the programme aims to prepare diploma graduates for employment as well as to prepare them to progress to the award of a degree. The diploma may also be an award for an entirely free standing programme unrelated to a degree programme, in which case the programme aims at every specific employment or skills-based target.

Degree
The degree programme consists of 360 credits, out of which at least 90 shall be at third year level. The degree programme usually takes over three years of full-time study, or more, if it consists of more than 360 credits.

Honours degree
The honours degree supplements and develops the subject matter learned from the degree to a higher level. It includes a project, emphasizes students' self study and prepares them for postgraduate study. The honours degree consists of 480 credits, out of which at least 90 credits are at fourth year level. The honours degree usually takes over four years of full-time study, with the inclusion of the degree programme of 360 credits included.

Students across the colleges have opportunities to partake in activities from study of their programmes and community service to a range of extracurricular activities.

title: Royal University of Bhutan


text:
User talk:Aperculum

=Please people, say something.=

Useful talk

 * Hello and welcome. I removed your name from December 14 because that list is just for people and events in the encyclopedia; there's a list of Wikipedian birthdays at Wikipedians by birthday if you want to add yourself there. Cheers, —No-One Jones (m) 00:26, 22 Oct 2004 (UTC)

Useless mumbling

 * Like this, this is useless talk.

Happy Birthday!
Happy birthday, Lauri! Best wishes. --[[User:Whosyourjudas|Whosyourjudas\talk]] 03:08, 14 Dec 2004 (UTC)

Notification: changes to "Mark my edits as minor by default" preference
Hello there. This is an automated message to tell you about the gradual phasing out of the preference entitled "Mark all edits minor by default", which you currently have enabled.

On 13 March 2011, this preference was hidden from the user preferences screen as part of efforts to prevent its accidental misuse (consensus discussion). This had the effect of locking users in to their existing preference, which, in your case, was. To complete the process, your preference will automatically be changed to  in the next few days. This does not require any intervention on your part and you will still be able to manually mark your edits as being 'minor'. The only thing that's changed is that you will no longer be able to have them marked as minor by default. For more information on what a minor edit is, see WP:MINOR or feel to get in touch.

Thank you for your understanding and happy editing :) Editing on behalf of User:Jarry1250, LivingBot (talk) 21:05, 13 March 2011 (UTC)

title: User talk:Aperculum


text:
User talk:66.214.177.86

Thanks for your suggestions to improve Thomas Jefferson. However, such suggestions belong on the article's talk page - Talk:Thomas Jefferson - and not in the article itself. Feel free, of course, to improve the article yourself. Thank you. Rdsmith4— Dan | Talk 00:22, 22 Oct 2004 (UTC)

title: User talk:66.214.177.86


text:
Jan Klemens Branicki

Count Jan Klemens Branicki (also known as Jan Kazimierz Branicki; 21 September 1689 – 9 October 1771) was a Polish nobleman, magnate and Hetman, Field Crown Hetman of the Polish–Lithuanian Commonwealth between 1735 and 1752, and Great Crown Hetman between 1752 and 1771. One of the wealthiest Polish magnates in the 18th century, owner of 12 towns, 257 villages and 17 palaces. He was the last male representative of the Branicki family.

He was a recipient of the Spanish Order of the Golden Fleece.

Biography
He was the son of the Palatine of Podlaskie Voivodeship Stefan Mikołaj Branicki and Katarzyna Scholastyka Sapieha, the daughter of Hetman Kazimierz Jan Sapieha. Jan had three wives:

The first wife was Princess Katarzyna Barbara Radziwiłł, the daughter of Count and Grand Marshal Karol Stanisław Radziwiłł, whom he married on 1 October 1720 in Biała Podlaska. His second wife was Barbara Szembek in 1732; this marriage ended in a divorce.

His third and last wife was Izabella Poniatowska, the daughter of the magnate Stanisław Poniatowski, whom he married in 1748.

He was Podczaszy of Lithuania (podczaszy litewski) in 1723, Grand Standard-Bearer of the Crown (chorąży wielki koronny) in 1724, commander of an infantry regiment (szef regimentu pieszego) in 1726, Artillery General of the Crown (generał artylerii koronnej) in 1728, hetman polny koronny in 1735, Palatine of Kraków Voivodship (wojewoda krakowski) in 1746, hetman wielki koronny in 1752 and Castellan of Kraków (kasztelan krakowski) in 1762. He was the Starost of Brańsk, Bielsk Podlaski, Mościsk, Janów Lubelski, Bohusław, Złotoryja, Krośno and Jezierzysk (starosta brański, bielski, mościcki, janowski, bohuslawski, złotoryjski, krośnienski, jezierzyski).

Branicki was one of the most powerful and influential magnates in Poland of the 18th century. He was the leader of the magnates party. Connected with the Radziwiłł and Potocki families and an opponent of the "Familia".

He sympathized with confederates of the Radom Confederation and the Confederation of Bar. Branicki was the owner of Białystok. At that time Białystok began to develop. In 1745 he established a military and engineer school and a theatre.

In 1763–1764 he ran in the election for the King of Poland, but was beaten by his brother-in-law Stanisław Poniatowski.

Marriage and issue
He married three times:
 * 1) Princess Katarzyna Barbara Maria Radziwillówna (Biała Podlaska, 6 December 1693 - Białystok, 16 October 1730) in Biała Podlaska, on 1 October 1720
 * 2) Barbara Szembekówna in 1732 and divorced
 * 3) Izabella Poniatowska on 19 November 1748 with no issue.

Awards

 * Knight of the Order of the White Eagle, since 1726.
 * Order of the Golden Fleece (Spanish Order)

title: Jan Klemens Branicki


text:
User talk:Stevenkrivit

Hello and welcome to Wikipedia! Hope you like it here, and stick around.

Here are some tips to help you get started:

 * Try the Tutorial, and feel free to experiment in the test area.
 * If you need help, post a question at the Help Desk
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Remember Neutral point of view
 * Explore, be bold in editing pages, and, most importantly, have fun!

Good luck!

[[User:Meelar|Meelar (talk)]]

P.S. One last helpful hint. To sign your posts like I did above (on talk pages, for example) use the '~' symbol. To insert just your name, type ~~~ (3 tildes), or, to insert your name and timestamp, use ~~~~ (4 tildes).

title: User talk:Stevenkrivit


text: User talk:80.128.38.125

title: User talk:80.128.38.125


text:
User:Ua747sp

Howdy.

title: User:Ua747sp


text:
Ancud

Ancud is a city in southern Chile located in the northernmost part of the island and province of Chiloé, in Los Lagos Region. It is the second largest city of Chiloé Archipelago after Castro. The city was established in 1768 to function as the capital of the archipelago and held that position until 1982. Founded as bulwark against foreign powers in colonial times, the city played an important role in the Chilean colonization of Patagonia in the 19th century.

Geography
Numerous glaciations have dredged the Chacao Channel to the north, separating Chiloé Island from mainland Chile to the north, marking the border between two natural regions of Chile, Zona Sur to the north and Zona Austral to the south. The Pacific Ocean lies on the west as the Chilean Coastal Range continues as a chain of islands. To the southeast of the commune is Quemchi and Dalcahue to the south. The commune has a surface area of 1752.4 sqkm. To the west are the coastal villages of Pumillahue and Quetalmahue, among others. 25 kilometers west of Ancud lies Islotes de Puñihuil Natural Monument, a group of preserved islands that provide habitat to various penguin species.

History
Prior to its establishment as a Spanish settlement the site of Ancud was known as Puerto Inglés (lit. English port). It was on here that Hendrik Brouwer, the leader of the Dutch expedition to Valdivia died on August 7, 1643, before reaching Valdivia.

As consequence of the Seven Years' War the Spanish authorities had the coastal fortification system of Chile updated and expanded. Inspired in the recommendations of former governor Antonio Narciso de Santa María, the Spanish founded the "city-fort" of Ancud in 1767–1768 and separated Chiloé from the Captaincy General of Chile into a direct dependency of the Viceroyalty of Peru. As with other 18th-century forts in Chile, the establishment of Ancud led through the new Ancud-Castro road to an expansion on local trade and agriculture.

Between 1839 and 1864 the Chilean Navy ran the Ancud Nautic School (Escuela Náutica de Ancud) in the town. Among its alumni was Francisco Hudson.

Climate
Ancud has an oceanic climate (Köppen climate classification Cfb) with significant precipitation in each month. Winters are cool and wet with a July average of 7.5 C. Precipitation during this time of the year is very high, averaging around 350 mm and humidity is high, averaging around 87-88%. Summers are mild with a January average of 15.0 C and during this time, precipitation is lower though still significant, averaging 125 mm in January. Temperatures rarely exceed 30 C. The average annual precipitation is 2540 mm and there are 200 days with measureable precipitation. However, precipitation is highly variable from year to year with 1993 being the driest, recording only 759 mm and 1977 being the wettest at 3712 mm. The record high was 32.7 C on January 27, 1975, and the record low was -3.0 C on June 30, 1970.

Demographics
According to the 2002 census of the National Statistics Institute, Ancud spans an area of 1252.4 sqkm and has 39,946 inhabitants (19,793 men and 20,153 women). Of these, 27,292 (68.3%) lived in urban areas and 12,654 (31.7%) in rural areas. The population grew by 6.5% (2,430 persons) between the 1992 and 2002 censuses. The demonym of a person from Ancud is Ancuditano for a man and Ancuditana for a woman.

Administration
As a commune, Ancud is a third-level administrative division of Chile administered by a municipal council, headed by an alcalde who is directly elected every four years. The 2008-2012 alcalde is Federico Krüger Finterbüch.

Within the electoral divisions of Chile, Ancud is represented in the Chamber of Deputies by Mr. Gabriel Ascencio (PDC) and Mr. Alejandro Santana (RN) as part of the 58th electoral district, together with Castro, Quemchi, Dalcahue, Curaco de Vélez, Quinchao, Puqueldón, Chonchi, Queilén, Quellón, Chaitén, Hualaihué, Futaleufú and Palena. The commune is represented in the Senate by Camilo Escalona Medina (PS) and Carlos Kuschel Silva (RN) as part of the 17th senatorial constituency (Los Lagos Region).

Education
Previously the area had a German school, Deutsche Schule Ancud-Chiloe.

Cathedral
The Cathedral of Ancud is the main religious temple of the city, and it is a building built after the 1960 earthquake, in the same place as the temple destroyed during that event.

Colonial fort system

The fort system of Ancud together with nearby the forts of Agüi one of the four fort systems that existed in colonial Chiloé. The fort system of Ancud is made up of two forts and four batteries. Fuerte Real de San Carlos was built as late as 1824 by orders of Antonio de Quintanilla, the last Spanish governor of Chiloé. The arsenal (polvorín) of this can still be seen at the centre of a small plaza. The battery of San Antonio is the best preserved part of the fort system.

title: Ancud


text:
User talk:Dr Zen

Poll: Micronation Infobox
An info box template has recently been created by myself and O^O for use in Wikipedia articles about micronations and other unrecognised entities, to address longstanding concerns and edit wars that have resulted from the inappropriate use of the standard country infobox in these types of articles.

This new info box has so far been successfully incorporated into the following articles: Sealand, Republic of Rose Island, Independent State of Aramoana, Empire of Atlantium, Avram and Province of Bumbunga, and it is intended to incorporate it into most of the other articles in the [|micronation category] in due course.

However, one editor, Samboy has suggested that the micronation infobox should be excluded from Empire of Atlantium on the grounds that the article is "not notable" and because only 22% of micronation articles in Wikipedia currently have the info box (ie because the info box project is not yet complete).

As someone who has contributed to similar discussions in the past, I thought this might interest you. I have instituted a poll on this subject here, and invite you to review it if you are so inclined.

Thanks. --Gene_poole 06:14, 7 November 2005 (UTC)

 * My personal issue with Gene Poole's action is that there is a conflict of interest here. One of the first micronations he added this infobox to is, conveniently enough, his own micronation.  And, while he sets up a poll about whether we should add the template to the article, he did not mention the poll in WP:RFC, which is the best way to make the poll visible to people who have never been involved in the issue.  Instead, he posts the existence of the poll on the user pages of a number of users who he feels are symphathetic to his micronation.  User:Tony Sidaway has felt that this kind of campaigning is dishonest. Samboy 07:22, 7 November 2005 (UTC)

ArbCom elections are now open!
MediaWiki message delivery (talk) 12:52, 23 November 2015 (UTC)

Splitting discussion for Clitoris
An article that you have edited or that may interest you, (Clitoris), has content that I have proposed to be removed and moved to another article, (Human clitoris). If you are interested, please visit the discussion. Thank you. Peaceray (talk) 05:40, 21 March 2023 (UTC)

title: User talk:Dr Zen


text:
User talk:Pptudela

Taxicabs in Mexico City
Many thanks for your contributions. I have added a couple of sentences that, I hope, conveys what is happening without saying outright that the police are corrupt :-). I have also added the three references you gave me so folks can read for themselves the situation. Please feel free to amend things if I have got them wrong and thank you again for your interest. BTW, if you look at the talk page I might need your help to defend the restructuring I have carried out :-(. TerriersFan 23:53, 10 September 2006 (UTC)

Smile!

has smiled at you! Smiles promote WikiLove and hopefully this one has made your day better. Spread the WikiLove by smiling to someone else, whether it be someone you have had disagreements with in the past or a good friend. Happy editing! Smile at others by adding {{subst:Smile}} to their talk page with a friendly message. Saber girl08 04:57, 19 March 2007 (UTC)

Arcos Bosques
Another editor has added the "prod" template to the article Arcos Bosques, suggesting that it be deleted according to the proposed deletion process. All contributions are appreciated, but the editor doesn't believe it satisfies Wikipedia's criteria for inclusion, and has explained why in the article (see also What Wikipedia is not and Notability). Please either work to improve the article if the topic is worthy of inclusion in Wikipedia or discuss the relevant issues at its talk page. If you remove the prod template, the article will not be deleted, but note that it may still be sent to Articles for deletion, where it may be deleted if consensus to delete is reached. Oo7565 16:50, 10 May 2007 (UTC)

Fair use rationale for Image:Giazotto_and_Albinoni_-_Adagio_in_G_minor.ogg
Thanks for uploading Image:Giazotto_and_Albinoni_-_Adagio_in_G_minor.ogg. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in Wikipedia articles constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale.

If you have uploaded other fair use media, consider checking that you have specified the fair use rationale on those pages too. You can find a list of 'image' pages you have edited by clicking on the "my contributions" link (it is located at the very top of any Wikipedia page when you are logged in), and then selecting "Image" from the dropdown box. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you. ShakespeareFan00 13:54, 12 May 2007 (UTC)

Image:Keith_Jarrett_-_Sun_Bear_Concerts_-_Tokyo_Encore.ogg
I have tagged Image:Keith_Jarrett_-_Sun_Bear_Concerts_-_Tokyo_Encore.ogg as no rationale, because it does not provide a fair use rationale. If you believe the image to be acceptable for fair use according to Wikipedia policy, please provide a rationale explaining as much, in accordance with the fair use rationale guideline, on the image description page. Please also consider using or one of the other tags listed at Image copyright tags. Thank you. ShakespeareFan00 10:30, 13 May 2007 (UTC)

Image:Miguel_Bernal_Jimenez_-_Retablo_Medieval_Concertino_para_Organo_y_Orquesta_-_Mester_de_Juglares.ogg
I have tagged Image:Miguel_Bernal_Jimenez_-_Retablo_Medieval_Concertino_para_Organo_y_Orquesta_-_Mester_de_Juglares.ogg as no rationale, because it does not provide a fair use rationale. If you believe the image to be acceptable for fair use according to Wikipedia policy, please provide a rationale explaining as much, in accordance with the fair use rationale guideline, on the image description page. Please also consider using or one of the other tags listed at Image copyright tags. Thank you. ShakespeareFan00 17:37, 13 May 2007 (UTC)

Image:Silvestre_Revueltas_-_Sensemayá.ogg
I have tagged Image:Silvestre_Revueltas_-_Sensemayá.ogg as no rationale, because it does not provide a fair use rationale. If you believe the image to be acceptable for fair use according to Wikipedia policy, please provide a rationale explaining as much, in accordance with the fair use rationale guideline, on the image description page. Please also consider using or one of the other tags listed at Image copyright tags. Thank you. ShakespeareFan00 14:47, 14 May 2007 (UTC)

Donating time consuming
Yes, donating to WP might be time consuming. I've thought of it myself but my online banking interface seems so complex that it would take lots of time to learn how it is done. I also once donated, but I never learnt if they reached their target (money sent). Gnetter (talk) 14:17, 7 April 2008 (UTC)

Notification of automated file description generation
Your upload of File:Arcos building mexico-city.JPG or contribution to its description is noted, and thanks (even if belatedly) for your contribution. In order to help make better use of the media, an attempt has been made by an automated process to identify and add certain information to the media's description page.

This notification is placed on your talk page because a bot has identified you either as the uploader of the file, or as a contributor to its metadata. It would be appreciated if you could carefully review the information the bot added. To opt out of these notifications, please follow the instructions here. Thanks! Message delivered by Theo's Little Bot (opt-out) 12:12, 3 January 2014 (UTC)

 * Another one of your uploads, File:Base station mexico-city.JPG, has also had some information automatically added. If you get a moment, please review the bot's contributions there as well. Thanks! Message delivered by Theo's Little Bot (opt-out) 12:52, 22 January 2014 (UTC)

title: User talk:Pptudela


text:
Talk:Ilex verticillata

Self-pollinating or not?
Question was re holly article saying hollies are dioecious (period), while this article said some hollies are self pollinating. Most are dioecious. Some are self-pollinating, which is quite a sales advantage, when trying to convince a customer, who just wants to plunk a pretty plant into his garden, to buy a breeding pair of hollies, one of which will never have any berries, particularly when there is no good way to identify a male except for examining the flowers, at which point you don't want to transplant them, so the chances of getting two females which won't produce any berries is a bit too high. So there was a real motivation to find self-pollinating varities, such as Ilex aquifolium Pyramidalis, Foster holly, Burford holly, dwarf Burford holly or Nellie R. Stevens holly, list the authorities. I see one every day, a single holly bush, evergreen, usually covered in berries, but don't know the variety. Gzuckier 16:12, 22 Oct 2004 (UTC)

winter holly
will the dwarf male winter holly "sprite" pollinate the standard size female winter holly? Can a male pollinate a female if 2 miles apart? thanks for your reply!!
 * Males should be within 10 yards of females. David notMD (talk) 11:14, 13 January 2021 (UTC)

As food
is it edible? is it poisonous?MY♥IN chile 20:26, 17 July 2008 (UTC)
 * Not edible. David notMD (talk) 11:14, 13 January 2021 (UTC)

YRC Worldwide official color
YRC (which stands for yellow roadway corporation) says that the color of its trucks (which are orange) is based on the "swamp holly" berry which can be seen a great distance. All the other hollies that have the same name have red berries. I'm guessing YRC's holly is this one but I don't have a citation. Americasroof (talk) 16:09, 29 January 2010 (UTC)

title: Talk:Ilex verticillata


text:
German modal particles

German modal particles (Modalpartikeln or Abtönungspartikeln) are uninflected words that are used mainly in the spontaneous spoken language in colloquial registers in German. Their dual function is to reflect the mood or the attitude of the speaker or the narrator and to highlight the sentence's focus.

Often, a modal particle has an effect that is vague and depends on the overall context. Speakers sometimes combine several particles, as in doch mal, ja nun or ja doch nun mal. It is a feature typical of the spoken language.

Most German words can be translated into English without any problems but modal particles are a challenge to translate because English has no real equivalent to them.

List of modal particles
Halt, eben and einmal (in this context always in full) and nun einmal (shortened: nun mal) imply that the often-unpleasant fact expressed in a sentence cannot be changed and must be accepted. Halt and nun mal are more colloquial than eben. In English, they could be rendered by "as a matter of fact" or "happen to":

 * Gute Kleider sind eben teuer. ("Good clothes are expensive, and it can't be helped." / "Good clothes happen to be expensive.")
 * Er hat mich provoziert, da habe ich ihn halt geschlagen. ("He provoked me so I hit him – what did you expect?")
 * Es ist nun einmal so. ("That's just how it is.")

Einmal, shortened to  mal (literally "once", roughly "for once") primarily indicates that the speaker dispenses with temporal precision, it can indicate a certain immediacy to the action or even imply a command. On the other hand, it can give a kind of casualness to a sentence and so makes it sound less blunt:

 * Hör mal zu! (Listen!" or "Listen to me"!)
 * Beeile dich mal! ("Do hurry up!")
 * Sing mal etwas Schönes! ("Why don't you sing something pretty?")
 * Schauen wir mal. (lit.: "Let's take one look." meaning: "Let's just relax and then we'll see what we'll be doing.")

Ja ("you know"/"everyone knows"/"I already told you") indicates that the speaker thinks that the fact should already be known to the listener and intends the statement to be more of a reminder or conclusion:

 * Ich habe ihm ein Buch geschenkt, er liest ja sehr gerne. ("I gave him a book as, you know, he likes to read.")
 * Heidi ist ja ein Kind. ("Heidi is a child as you can see.")

Doch can have several meanings. (See also .) It can be used affirmatively or to convey emphasis, urgency or impatience. It can also be a reply to a real, imagined, or pre-emptively-answered disagreement, hesitation, or wrong assumption on the part of the listener or other people. In other situations, it can have different effects.

Conversely, doch can also express doubt and in writing, the affirmative and the doubtful meanings may be ambiguous and depend on context. In speech, the different meanings of doch can be told apart by different types of emphasis:

 * Gehst Du nicht nach Hause? Doch, ich gehe gleich. ("Are you not going home?" "Oh, yes, I am going in a moment".) (Affirmation of a negative question; obligatory.)
 * Komm doch her! ("Do come here!") (Emphatically)
 * Komm doch endlich her! ("Do come on! Get a move on!") (More emphatically and impatiently)
 * Ich habe dir doch gesagt, dass es nicht so ist. ("I did tell you that it isn't like that." or "I told you it isn't like that, didn't I?")
 * Ich kenne mich in Berlin aus. Ich war doch letztes Jahr dort. ("I know my way around Berlin. I was there last year, after all/as a matter of fact.")

In that way, doch can be similar to stressed schon ("indeed"), but stressed schon implies an actual qualification of the statement, which is often made explicit by a phrase with aber ("but"):

 * Ich war schon auf der Party, aber Spaß hatte ich nicht. ("I was indeed at the party, but I did not enjoy myself.")

That should not be confused with the adverbial meaning of the unstressed schon, "already". However, at least in writing, schon "already" must be either made unmistakable by the context, such as by additional adverbs, or replaced by its equivalent, bereits:

 * Ich war schon (/bereits) auf der Party, aber Spaß hatte ich (noch) nicht. ("I was already at the party, but I had not (yet) been enjoying myself.")

In other contexts, doch indicates that the action described in the sentence is unlikely to occur:

 * Du bist also doch gekommen! ("You came after all.")
 * Ich sehe nicht viel fern, aber wenn etwas Gutes kommt, schalte ich doch ein. ("I don't watch much TV, but I do tune in if something good comes on.")

Gar is used to intensify a statement, the completeness or a total lack of something:

 * Ich besitze gar kein Auto. ("I'm afraid I have no car [at all].")

At the beginning of a sentence, especially in literary contexts, gar sometimes has a different meaning and is often interchangeable with sogar or ganz:

 * Gar die Lehrerin hat über dich gelacht! = Sogar die Lehrerin hat über dich gelacht! ("Even the teacher laughed at you!") Here, gar does not act as a modal particle.
 * Gar 20 Jahre lebe ich jetzt schon hier. = Ganze 20 Jahre lebe ich jetzt schon hier. ("I have already been living here for two entire decades.")

Rein often precedes gar to point out the total lack of something:

 * Ich habe rein gar nichts gemacht! ("I did absolutely nothing!")

Total, besides its use as an adjective and adverb, can also act as a modal particle indicating irony. It is best translated as "well", "really" or "let me think...":

 * A: Hast du Lust meinen Geschirrspüler auszuräumen? B: Total... ("A: Do you want to empty my dishwasher? B: Let me think... no!")
 * Ich musste heute drei Stunden beim Arzt warten... hat total Spaß gemacht... ("Today I had to wait for three hours at the doctor's office... it really was a lot of fun!")

Aber, when not as a conjunction, is very similar to doch and conveys a meaning of disagreement to a previously stated or implied assertion. Alternatively aber can be used to show surprise:

 * Du sprichst aber schon gut Deutsch! ("But you do already speak good German!")
 * Du sprichst aber gut Deutsch! ("Wow, do you speak good German!")

Sowieso, ohnehin or eh, meaning "anyway(s)", implies an emphasized assertion. Especially in Southern German, eh is colloquially most common. All these can be enforced by a preceding doch:

 * Ich hab ihm eh gesagt, dass er sich wärmer anziehen soll. ("I told him to put on warmer clothes in the first place.")
 * Das ist eh nicht wahr. ("That's not true anyway.")

Vielleicht, as a modal particle, is used for emphasis and should not be confused with the adverb vielleicht, meaning "perhaps":

 * Das ist vielleicht ein großer Hund! (with an emphasis on "Das", "That's quite a large dog!")

But:
 * Vielleicht ist das ein großer Hund. Es ist schwer zu erkennen. ("Maybe that's a large dog. It's difficult to tell.")

Fei, which is no longer recognised as the adverb fein "finely", is a particle peculiar to Upper German dialects. It denotes that the speaker states that something important might be a surprise for the listener. Giving an adequate translation even into Standard German is difficult, and the best substitute would probably be to use an understatement with strong affirmative meaning. In English, translations to "I should think" or "just to mention" seem possible depending on context:

 * Des kôsch fei net macha! (Swabian) = Das kannst du (eigentlich wirklich) nicht machen. (You can't do that! / If you do look at it, you really can't do that. / You can't, I should think, do that.)
 * I bin fei ned aus Preissen! (Bavarian) = Ich bin, das wollte ich nur einmal anmerken, nicht aus Preußen. / Ich bin wohlgemerkt (gar) nicht aus Preußen. (Just to mention, I'm not from Prussia.)

Wohl is often used instead of epistemic adverbs, such as vermutlich or wahrscheinlich or to emphasise a strong disagreement. A literal translation with "probably" or at least with "seemingly" is possible:
 * Es wird wohl Regen geben. ("It looks like rain. / It's probably going to rain.")
 * Du bist wohl verrückt!. ("You must be out of your mind.")

Note on mal: The colloquial shortening of einmal to mal is not considered standard, unlike for modal particles.

title: German modal particles


text:
Software prototyping

Software prototyping is the activity of creating prototypes of software applications, i.e., incomplete versions of the software program being developed. It is an activity that can occur in software development and is comparable to prototyping as known from other fields, such as mechanical engineering or manufacturing.

A prototype typically simulates only a few aspects of, and may be completely different from, the final product.

Prototyping has several benefits: the software designer and implementer can get valuable feedback from the users early in the project. The client and the contractor can compare if the software made matches the software specification, according to which the software program is built. It also allows the software engineer some insight into the accuracy of initial project estimates and whether the deadlines and milestones proposed can be successfully met. The degree of completeness and the techniques used in prototyping have been in development and debate since its proposal in the early 1970s.

Overview
The purpose of a prototype is to allow users of the software to evaluate developers' proposals for the design of the eventual product by actually trying them out, rather than having to interpret and evaluate the design based on descriptions. Software prototyping provides an understanding of the software's functions and potential threats or issues. Prototyping can also be used by end users to describe and prove requirements that have not been considered, and that can be a key factor in the commercial relationship between developers and their clients. Interaction design in particular makes heavy use of prototyping with that goal.

This process is in contrast with the 1960s and 1970s monolithic development cycle of building the entire program first and then working out any inconsistencies between design and implementation, which led to higher software costs and poor estimates of time and cost. The monolithic approach has been dubbed the "Slaying the (software) Dragon" technique, since it assumes that the software designer and developer is a single hero who has to slay the entire dragon alone. Prototyping can also avoid the great expense and difficulty of having to change a finished software product.

The practice of prototyping is one of the points Frederick P. Brooks makes in his 1975 book The Mythical Man-Month and his 10-year anniversary article "No Silver Bullet".

An early example of large-scale software prototyping was the implementation of NYU's Ada/ED translator for the Ada programming language. It was implemented in SETL with the intent of producing an executable semantic model for the Ada language, emphasizing clarity of design and user interface over speed and efficiency. The NYU Ada/ED system was the first validated Ada implementation, certified on April 11, 1983.

Outline
The process of prototyping involves the following steps:

 * 1) Identify basic requirements
 * Determine basic requirements including the input and output information desired. Details, such as security, can typically be ignored.
 * 1) Develop initial prototype
 * The initial prototype is developed that includes only user interfaces. (See Horizontal Prototype, below)
 * 1) Review
 * The customers, including end-users, examine the prototype and provide feedback on potential additions or changes.
 * 1) Revise and enhance the prototype
 * Using the feedback both the specifications and the prototype can be improved. Negotiation about what is within the scope of the contract/product may be necessary.  If changes are introduced then a repeat of steps #3 and #4 may be needed.

Dimensions
Nielsen summarizes the various dimensions of prototypes in his book Usability Engineering:

Horizontal prototype
A common term for a user interface prototype is the horizontal prototype. It provides a broad view of an entire system or subsystem, focusing on user interaction more than low-level system functionality, such as database access. Horizontal prototypes are useful for:
 * Confirmation of user interface requirements and system scope,
 * Demonstration version of the system to obtain buy-in from the business,
 * Develop preliminary estimates of development time, cost and effort.

Vertical prototype
A vertical prototype is an enhanced complete elaboration of a single subsystem or function. It is useful for obtaining detailed requirements for a given function, with the following benefits:
 * Refinement database design,
 * Obtain information on data volumes and system interface needs, for network sizing and performance engineering,
 * Clarify complex requirements by drilling down to actual system functionality.

Types
Software prototyping has many variants. However, all of the methods are in some way based on two major forms of prototyping: throwaway prototyping and evolutionary prototyping.

Throwaway prototyping
Also called close-ended prototyping. Throwaway or rapid prototyping refers to the creation of a model that will eventually be discarded rather than becoming part of the final delivered software. After preliminary requirements gathering is accomplished, a simple working model of the system is constructed to visually show the users what their requirements may look like when they are implemented into a finished system. It is also a form of rapid prototyping.
 * Rapid prototyping involves creating a working model of various parts of the system at a very early stage, after a relatively short investigation. The method used in building it is usually quite informal, the most important factor being the speed with which the model is provided. The model then becomes the starting point from which users can re-examine their expectations and clarify their requirements. When this goal has been achieved, the prototype model is 'thrown away', and the system is formally developed based on the identified requirements.

The most obvious reason for using throwaway prototyping is that it can be done quickly. If the users can get quick feedback on their requirements, they may be able to refine them early in the development of the software. Making changes early in the development lifecycle is extremely cost effective since there is nothing at that point to redo. If a project is changed after a considerable amount of work has been done then small changes could require large efforts to implement since software systems have many dependencies. Speed is crucial in implementing a throwaway prototype, since with a limited budget of time and money little can be expended on a prototype that will be discarded.

Another strength of throwaway prototyping is its ability to construct interfaces that the users can test. The user interface is what the user sees as the system, and by seeing it in front of them, it is much easier to grasp how the system will function.

 * …it is asserted that revolutionary rapid prototyping is a more effective manner in which to deal with user requirements-related issues, and therefore a greater enhancement to software productivity overall. Requirements can be identified, simulated, and tested far more quickly and cheaply when issues of evolvability, maintainability, and software structure are ignored. This, in turn, leads to the accurate specification of requirements, and the subsequent construction of a valid and usable system from the user's perspective, via conventional software development models.

Prototypes can be classified according to the fidelity with which they resemble the actual product in terms of appearance, interaction and timing. One method of creating a low fidelity throwaway prototype is paper prototyping. The prototype is implemented using paper and pencil, and thus mimics the function of the actual product, but does not look at all like it. Another method to easily build high fidelity throwaway prototypes is to use a GUI Builder and create a click dummy, a prototype that looks like the goal system, but does not provide any functionality.

The usage of storyboards, animatics or drawings is not exactly the same as throwaway prototyping, but certainly falls within the same family. These are non-functional implementations but show how the system will look.

Summary: In this approach the prototype is constructed with the idea that it will be discarded and the final system will be built from scratch. The steps in this approach are:
 * 1) Write preliminary requirements
 * 2) Design the prototype
 * 3) User experiences/uses the prototype, specifies new requirements
 * 4) Repeat if necessary
 * 5) Write the final requirements

Evolutionary prototyping
Evolutionary prototyping (also known as breadboard prototyping) is quite different from throwaway prototyping. The main goal when using evolutionary prototyping is to build a very robust prototype in a structured manner and constantly refine it. The reason for this approach is that the evolutionary prototype, when built, forms the heart of the new system, and the improvements and further requirements will then be built.

When developing a system using evolutionary prototyping, the system is continually refined and rebuilt.
 * "…evolutionary prototyping acknowledges that we do not understand all the requirements and builds only those that are well understood."

This technique allows the development team to add features, or make changes that couldn't be conceived during the requirements and design phase.

 * For a system to be useful, it must evolve through use in its intended operational environment. A product is never "done;" it is always maturing as the usage environment changes…we often try to define a system using our most familiar frame of reference—where we are now. We make assumptions about the way business will be conducted and the technology base on which the business will be implemented. A plan is enacted to develop the capability, and, sooner or later, something resembling the envisioned system is delivered.

Evolutionary prototypes have an advantage over throwaway prototypes in that they are functional systems. Although they may not have all the features the users have planned, they may be used on an interim basis until the final system is delivered.

 * "It is not unusual within a prototyping environment for the user to put an initial prototype to practical use while waiting for a more developed version…The user may decide that a 'flawed' system is better than no system at all."

In evolutionary prototyping, developers can focus themselves to develop parts of the system that they understand instead of working on developing a whole system.

 * To minimize risk, the developer does not implement poorly understood features. The partial system is sent to customer sites. As users work with the system, they detect opportunities for new features and give requests for these features to developers. Developers then take these enhancement requests along with their own and use sound configuration-management practices to change the software-requirements specification, update the design, recode and retest.

Incremental prototyping
The final product is built as separate prototypes. At the end, the separate prototypes are merged in an overall design. By the help of incremental prototyping the time gap between user and software developer is reduced.

Extreme prototyping
Extreme prototyping as a development process is used especially for developing web applications. Basically, it breaks down web development into three phases, each one based on the preceding one. The first phase is a static prototype that consists mainly of HTML pages. In the second phase, the screens are programmed and fully functional using a simulated services layer. In the third phase, the services are implemented.
 * "The process is called Extreme Prototyping to draw attention to the second phase of the process, where a fully functional UI is developed with very little regard to the services other than their contract."

Advantages
There are many advantages to using prototyping in software development – some tangible, some abstract.

Reduced time and costs: Prototyping can improve the quality of requirements and specifications provided to developers. Because changes cost exponentially more to implement as they are detected later in development, the early determination of what the user really wants can result in faster and less expensive software.

Improved and increased user involvement: Prototyping requires user involvement and allows them to see and interact with a prototype allowing them to provide better and more complete feedback and specifications. The presence of the prototype being examined by the user prevents many misunderstandings and miscommunications that occur when each side believe the other understands what they said. Since users know the problem domain better than anyone on the development team does, increased interaction can result in a final product that has greater tangible and intangible quality. The final product is more likely to satisfy the user's desire for look, feel and performance.

Disadvantages
Using, or perhaps misusing, prototyping can also have disadvantages.

Insufficient analysis: The focus on a limited prototype can distract developers from properly analyzing the complete project. This can lead to overlooking better solutions, preparation of incomplete specifications or the conversion of limited prototypes into poorly engineered final projects that are hard to maintain. Further, since a prototype is limited in functionality it may not scale well if the prototype is used as the basis of a final deliverable, which may not be noticed if developers are too focused on building a prototype as a model.

User confusion of prototype and finished system: Users can begin to think that a prototype, intended to be thrown away, is actually a final system that merely needs to be finished or polished. (They are, for example, often unaware of the effort needed to add error-checking and security features which a prototype may not have.) This can lead them to expect the prototype to accurately model the performance of the final system when this is not the intent of the developers. Users can also become attached to features that were included in a prototype for consideration and then removed from the specification for a final system. If users are able to require all proposed features be included in the final system this can lead to conflict.

Developer misunderstanding of user objectives: Developers may assume that users share their objectives (e.g. to deliver core functionality on time and within budget), without understanding wider commercial issues. For example, user representatives attending Enterprise software (e.g. PeopleSoft) events may have seen demonstrations of "transaction auditing" (where changes are logged and displayed in a difference grid view) without being told that this feature demands additional coding and often requires more hardware to handle extra database accesses. Users might believe they can demand auditing on every field, whereas developers might think this is feature creep because they have made assumptions about the extent of user requirements. If the developer has committed delivery before the user requirements were reviewed, developers are between a rock and a hard place, particularly if user management derives some advantage from their failure to implement requirements.

Developer attachment to prototype: Developers can also become attached to prototypes they have spent a great deal of effort producing; this can lead to problems, such as attempting to convert a limited prototype into a final system when it does not have an appropriate underlying architecture. (This may suggest that throwaway prototyping, rather than evolutionary prototyping, should be used.)

Excessive development time of the prototype: A key property to prototyping is the fact that it is supposed to be done quickly. If the developers lose sight of this fact, they very well may try to develop a prototype that is too complex. When the prototype is thrown away the precisely developed requirements that it provides may not yield a sufficient increase in productivity to make up for the time spent developing the prototype. Users can become stuck in debates over details of the prototype, holding up the development team and delaying the final product.

Expense of implementing prototyping: the start up costs for building a development team focused on prototyping may be high. Many companies have development methodologies in place, and changing them can mean retraining, retooling, or both. Many companies tend to just begin prototyping without bothering to retrain their workers as much as they should.

 * A common problem with adopting prototyping technology is high expectations for productivity with insufficient effort behind the learning curve. In addition to training for the use of a prototyping technique, there is an often overlooked need for developing corporate and project specific underlying structure to support the technology. When this underlying structure is omitted, lower productivity can often result.

Applicability
It has been argued that prototyping, in some form or another, should be used all the time. However, prototyping is most beneficial in systems that will have many interactions with the users.

 * It has been found that prototyping is very effective in the analysis and design of on-line systems, especially for transaction processing, where the use of screen dialogs is much more in evidence. The greater the interaction between the computer and the user, the greater the benefit is that can be obtained from building a quick system and letting the user play with it.

Systems with little user interaction, such as batch processing or systems that mostly do calculations, benefit little from prototyping. Sometimes, the coding needed to perform the system functions may be too intensive and the potential gains that prototyping could provide are too small.

Prototyping is especially good for designing good human–computer interfaces. "One of the most productive uses of rapid prototyping to date has been as a tool for iterative user requirements engineering and human–computer interface design."

Dynamic systems development method
Dynamic Systems Development Method (DSDM) is a framework for delivering business solutions that relies heavily upon prototyping as a core technique, and is itself ISO 9001 approved. It expands upon most understood definitions of a prototype. According to DSDM the prototype may be a diagram, a business process, or even a system placed into production. DSDM prototypes are intended to be incremental, evolving from simple forms into more comprehensive ones.

DSDM prototypes can sometimes be throwaway or evolutionary. Evolutionary prototypes may be evolved horizontally (breadth then depth) or vertically (each section is built in detail with additional iterations detailing subsequent sections). Evolutionary prototypes can eventually evolve into final systems.

The four categories of prototypes as recommended by DSDM are:
 * Business prototypes – used to design and demonstrates the business processes being automated.
 * Usability prototypes – used to define, refine, and demonstrate user interface design usability, accessibility, look and feel.
 * Performance and capacity prototypes – used to define, demonstrate, and predict how systems will perform under peak loads as well as to demonstrate and evaluate other non-functional aspects of  the system (transaction rates, data storage volume, response time, etc.)
 * Capability/technique prototypes – used to develop, demonstrate, and evaluate a design approach or concept.

The DSDM lifecycle of a prototype is to:
 * 1) Identify prototype
 * 2) Agree to a plan
 * 3) Create the prototype
 * 4) Review the prototype

Operational prototyping
Operational prototyping was proposed by Alan Davis as a way to integrate throwaway and evolutionary prototyping with conventional system development. "It offers the best of both the quick-and-dirty and conventional-development worlds in a sensible manner. Designers develop only well-understood features in building the evolutionary baseline, while using throwaway prototyping to experiment with the poorly understood features."

Davis' belief is that to try to "retrofit quality onto a rapid prototype" is not the correct method when trying to combine the two approaches. His idea is to engage in an evolutionary prototyping methodology and rapidly prototype the features of the system after each evolution.

The specific methodology follows these steps:

 * An evolutionary prototype is constructed and made into a baseline using conventional development strategies, specifying and implementing only the requirements that are well understood.
 * Copies of the baseline are sent to multiple customer sites along with a trained prototyper.
 * At each site, the prototyper watches the user at the system.
 * Whenever the user encounters a problem or thinks of a new feature or requirement, the prototyper logs it. This frees the user from having to record the problem, and allows him to continue working.
 * After the user session is over, the prototyper constructs a throwaway prototype on top of the baseline system.
 * The user now uses the new system and evaluates. If the new changes aren't effective, the prototyper removes them.
 * If the user likes the changes, the prototyper writes feature-enhancement requests and forwards them to the development team.
 * The development team, with the change requests in hand from all the sites, then produce a new evolutionary prototype using conventional methods.

Obviously, a key to this method is to have well trained prototypers available to go to the user sites. The operational prototyping methodology has many benefits in systems that are complex and have few known requirements in advance.

Evolutionary systems development
Evolutionary Systems Development is a class of methodologies that attempt to formally implement evolutionary prototyping. One particular type, called Systemscraft is described by John Crinnion in his book Evolutionary Systems Development.

Systemscraft was designed as a 'prototype' methodology that should be modified and adapted to fit the specific environment in which it was implemented.

 * Systemscraft was not designed as a rigid 'cookbook' approach to the development process. It is now generally recognised[sic] that a good methodology should be flexible enough to be adjustable to suit all kinds of environment and situation...

The basis of Systemscraft, not unlike evolutionary prototyping, is to create a working system from the initial requirements and build upon it in a series of revisions. Systemscraft places heavy emphasis on traditional analysis being used throughout the development of the system.

Evolutionary rapid development
Evolutionary Rapid Development (ERD) was developed by the Software Productivity Consortium, a technology development and integration agent for the Information Technology Office of the Defense Advanced Research Projects Agency (DARPA).

 * Fundamental to ERD is the concept of composing software systems based on the reuse of components, the use of software templates and on an architectural template. Continuous evolution of system capabilities in rapid response to changing user needs and technology is highlighted by the evolvable architecture, representing a class of solutions. The process focuses on the use of small artisan-based teams integrating software and systems engineering disciplines working multiple, often parallel short-duration timeboxes with frequent customer interaction.

 * Key to the success of the ERD-based projects is parallel exploratory analysis and development of features, infrastructures, and components with and adoption of leading edge technologies enabling the quick reaction to changes in technologies, the marketplace, or customer requirements.

To elicit customer/user input, frequent scheduled and ad hoc/impromptu meetings with the stakeholders are held. Demonstrations of system capabilities are held to solicit feedback before design/implementation decisions are solidified. Frequent releases (e.g., betas) are made available for use to provide insight into how the system could better support user and customer needs. This assures that the system evolves to satisfy existing user needs.

The design framework for the system is based on using existing published or de facto standards. The system is organized to allow for evolving a set of capabilities that includes considerations for performance, capacities, and functionality. The architecture is defined in terms of abstract interfaces that encapsulate the services and their implementation (e.g., COTS applications). The architecture serves as a template to be used for guiding development of more than a single instance of the system. It allows for multiple application components to be used to implement the services. A core set of functionality not likely to change is also identified and established.

The ERD process is structured to use demonstrated functionality rather than paper products as a way for stakeholders to communicate their needs and expectations. Central to this goal of rapid delivery is the use of the "timebox" method. Timeboxes are fixed periods of time in which specific tasks (e.g., developing a set of functionality) must be performed. Rather than allowing time to expand to satisfy some vague set of goals, the time is fixed (both in terms of calendar weeks and person-hours) and a set of goals is defined that realistically can be achieved within these constraints. To keep development from degenerating into a "random walk," long-range plans are defined to guide the iterations. These plans provide a vision for the overall system and set boundaries (e.g., constraints) for the project. Each iteration within the process is conducted in the context of these long-range plans.

Once an architecture is established, software is integrated and tested on a daily basis. This allows the team to assess progress objectively and identify potential problems quickly. Since small amounts of the system are integrated at one time, diagnosing and removing the defect is rapid. User demonstrations can be held at short notice since the system is generally ready to exercise at all times.

Tools
Efficiently using prototyping requires that an organization have the proper tools and a staff trained to use those tools. Tools used in prototyping can vary from individual tools, such as 4th generation programming languages used for rapid prototyping to complex integrated CASE tools. 4th generation visual programming languages like Visual Basic and ColdFusion are frequently used since they are cheap, well known and relatively easy and fast to use. CASE tools, supporting requirements analysis, like the Requirements Engineering Environment (see below) are often developed or selected by the military or large organizations. Object oriented tools are also being developed like LYMB from the GE Research and Development Center. Users may prototype elements of an application themselves in a spreadsheet.

As web-based applications continue to grow in popularity, so too, have the tools for prototyping such applications. Frameworks such as Bootstrap, Foundation, and AngularJS provide the tools necessary to quickly structure a proof of concept. These frameworks typically consist of a set of controls, interactions, and design guidelines that enable developers to quickly prototype web applications.

Screen generators, design tools, and software factories
Screen generating programs are also commonly used and they enable prototypers to show user's systems that do not function, but show what the screens may look like. Developing Human Computer Interfaces can sometimes be the critical part of the development effort, since to the users the interface essentially is the system.

Software factories can generate code by combining ready-to-use modular components. This makes them ideal for prototyping applications, since this approach can quickly deliver programs with the desired behaviour, with a minimal amount of manual coding.

Application definition or simulation software
A new class of software called Application definition or simulation software  enables users to rapidly build lightweight, animated simulations of another computer program, without writing code. Application simulation software allows both technical and non-technical users to experience, test, collaborate and validate the simulated program, and provides reports such as annotations, screenshot and schematics. As a solution specification technique, Application Simulation falls between low-risk, but limited, text or drawing-based mock-ups (or wireframes) sometimes called paper-based prototyping, and time-consuming, high-risk code-based prototypes, allowing software professionals to validate requirements and design choices early on, before development begins. In doing so, the risks and costs associated with software implementations can be dramatically reduced.

To simulate applications one can also use software that simulates real-world software programs for computer-based training, demonstration, and customer support, such as screencasting software as those areas are closely related.

Requirements Engineering Environment
"The Requirements Engineering Environment (REE), under development at Rome Laboratory since 1985, provides an integrated toolset for rapidly representing, building, and executing models of critical aspects of complex systems."

Requirements Engineering Environment is currently used by the United States Air Force to develop systems. It is:

 * an integrated set of tools that allows systems analysts to rapidly build functional, user interface, and performance prototype models of system components. These modeling activities are performed to gain a greater understanding of complex systems and lessen the impact that inaccurate requirement specifications have on cost and scheduling during the system development process. Models can be constructed easily, and at varying levels of abstraction or granularity, depending on the specific behavioral aspects of the model being exercised.

REE is composed of three parts. The first, called proto is a CASE tool specifically designed to support rapid prototyping. The second part is called the Rapid Interface Prototyping System or RIP, which is a collection of tools that facilitate the creation of user interfaces. The third part of REE is a user interface to RIP and proto that is graphical and intended to be easy to use.

Rome Laboratory, the developer of REE, intended that to support their internal requirements gathering methodology. Their method has three main parts:
 * Elicitation from various sources (users, interfaces to other systems), specification, and consistency checking
 * Analysis that the needs of diverse users taken together do not conflict and are technically and economically feasible
 * Validation that requirements so derived are an accurate reflection of user needs.

In 1996, Rome Labs contracted Software Productivity Solutions (SPS) to further enhance REE to create "a commercial quality REE that supports requirements specification, simulation, user interface prototyping, mapping of requirements to hardware architectures, and code generation..." This system is named the Advanced Requirements Engineering Workstation or AREW.

Non-relational environments
Non-relational definition of data (e.g. using Caché or associative models) can help make end-user prototyping more productive by delaying or avoiding the need to normalize data at every iteration of a simulation. This may yield earlier/greater clarity of business requirements, though it does not specifically confirm that requirements are technically and economically feasible in the target production system.

PSDL
PSDL is a prototype description language to describe real-time software. The associated tool set is CAPS (Computer Aided Prototyping System). Prototyping software systems with hard real-time requirements is challenging because timing constraints introduce implementation and hardware dependencies. PSDL addresses these issues by introducing control abstractions that include declarative timing constraints. CAPS uses this information to automatically generate code and associated real-time schedules, monitor timing constraints during prototype execution, and simulate execution in proportional real time relative to a set of parameterized hardware models. It also provides default assumptions that enable execution of incomplete prototype descriptions, integrates prototype construction with a software reuse repository for rapidly realizing efficient implementations, and provides support for rapid evolution of requirements and designs.

title: Software prototyping


text:
Talk:Electoral district

Untitled
Question: Should this redirect to Electorate, rather than to Constituency ? --Nickj 00:37, 22 Oct 2004 (UTC)

'Electoral seat' rather than 'electoral district'?
The article looks like an attempt to use electoral district as a generic. It seems to me however that electoral seat is more generic, not least because electoral district had specific statutory meaning in Scotland, until 1996, under the Local Government (Scotland) Act 1973, and was definitely not a parliamentary or national assembly seat. The Scottish electoral district was regional a council seat and might have been called a ward but that legislators seemed to want a term such that the regional council seat could not be confused with the contemporaneous district council ward. What the article says at present about the United Kingdom is misleading. Anyone who knows the UK would not use electoral district to refer to a parliamentary or national assembly electoral seat (constituency), but might use it to refer to a local government electoral seat. Laurel Bush (talk) 18:38, 28 November 2008 (UTC).
 * There's no good solution to this problem (varieties of English), but in general Wikipedia prefers to use the unambiguous phrase. Unfortunately I'm afraid "electoral seat" might be even more ambiguous - I've never actually seen the term before, so I had to guess at its meaning after reading your headline.  Until seeing your explanation, I thought it just meant a position that can be won (and not a physical area), analogous to the term seat.  I suspect many others would encounter this confusion - a Google search shows the term "electoral district" to be over 100 times more common than "electoral seat"; "electoral district" is also the term used generically in Political Science journals.  "Electoral district" can also be easily shortened to the generic district as well in the article text; it would be a bit weird to use "electoral seat" for the title and then refer to it as a "district" in the main text.  Scott Ritchie (talk) 20:38, 28 November 2008 (UTC)

UK parliamentary constituencies are often called seats. Something needs to be done about the article's misleading reference to the UK. Laurel Bush (talk) 12:22, 1 December 2008 (UTC).

 * The expression "seat" refers literally to the sucessful politician's chair in the legislative chamber. It has very little meaning to a description of the boundaries of the region within which the voters who elect that politician reside.  Of course,  it is the voters of that area who send the candidate to his seat.  The formal and informal terminology for the districting arrangements vary widely between the English-speaking countries.  Even in a single country,  multiple names are used.  For example, in Australia,  the districts are legally called "divisions",  but almost nobody calls them that.  They are also called "electorates"  and they are also called "seats".   One would refer to politician Mr XYZ's "seat",  but an ordinary voter would not normally say that they reside a particular "electorate".
 * Anyway the point is that "electoral district" is about the most generic, non-country-specific descriptor that can be indentified for a general discussion of the topic.Eregli bob (talk) 18:42, 23 May 2010 (UTC)
 * , as the say. "Electoral district" doesn't look like a generic term to me, but rather a term used for a specific thing in a couple of countries. It also sounds similar to district, a term used for administrative areas in various countries. Personally speaking, I think the title 'Electoral area' would make the scope of the article clearer.

 * For what it's worth, 'electoral seat' sounds awkward to me. Aoeuidhtns (talk) 12:46, 11 October 2011 (UTC)

Constituency
I've merged Constituency here. Three years after it was created it's part dictdef, part disambiguation, with one line about franking privilege which I copied. I also merged constituent (politics) which was a similar mess, though it had more substance, which I included in Electoral district. I don't see what current benefit there is for having separate articles; it's not as though there is currently a huge mass of information. There is scope for an article about "Constituency" in the sense of "group of voters with some commonality", but for now I've just listed interest group at constituency (disambiguation) as the closest match currently available.

Also added a Electoral district section, which suggests the overall article might be better moved to "Constituency" (!), or "Electorate". jnestorius(talk) 22:03, 29 April 2011 (UTC)

 * Thank you for giving the article some love. Really, what it needs is just more good content.  When we have enough we can worry about whether it's more about (people) constituencies or districts. Scott Ritchie (talk) 07:44, 6 May 2011 (UTC)

 * Well, the merging of constituency (more of a territory one represents) and an electoral district (district used in an election), makes it pretty hard to describe the situation in the Netherlands, where there are 20 electoral districts, in which the voters may not be offered the same lists of candidates and parties, but the votes are all counted as if those electoral districts form one multi-member constituency...ThW5 (talk) 18:44, 9 August 2012 (UTC)

Maori Electorates
It's incorrect to say that Maori electorates in New Zealand aren't geographical - they are geographical. They cover the country geographically as the General electoral seats do - the only difference is that only people on the Maori electoral roll can vote for them, just as only people on the General roll can vote in the General electorates. 60.234.139.97 (talk) 05:41, 5 May 2011 (UTC)

Technical terms
There are 24 redirects to this page, many of which refer to official terms used in various countries. I've just added a redirect for a second of these (electoral division, a term used in England and Wales), but I wonder if there's enough material to make a dab page for this subject. This page could then start with a line which reads something along the lines of "This article is about electoral districts in general. For specific terms see Electoral district (disambiguation)." Or should I just edit the Electoral division page? Aoeuidhtns (talk) 11:58, 11 October 2011 (UTC)

 * If there is substantial material to add about the meaning, history and implications of this subject in a particular country, by all means create a separate article. You might want to create it in user space first e.g. at User:Aoeuidhtns/Electoral division and ask here for opinions once we can see what you have come up with.
 * However, creating country-specific articles which have substantial overlap in content/meaning would go against the policy WP:Content forking.
 * You could consider creating List of national terms for electoral districts, if it would be interesting or useful; but I suspect that it might not be either!
 * Probably the best option is to consider expanding the section here titled "Terminology". – Fayenatic (talk) 17:47, 17 October 2011 (UTC)

Government
Types of electoral constituency 2C0F:F5C0:506:170E:60C5:FB97:CDD8:9656 (talk) 07:03, 6 January 2023 (UTC)

title: Talk:Electoral district


text:
Mitchell River (Queensland)

The Mitchell River is a river in Far North Queensland, Australia. The river rises on the Atherton Tableland about 50 km northwest of Cairns and flows about 750 km northwest across Cape York Peninsula from Mareeba to the Gulf of Carpentaria.

The river's watershed covers an area of 71757 km2. The Mitchell has the state's largest discharge, at 11.3 e6ML annually, but is intermittent and may be dry for part of the year. Lake Mitchell is the main water storage facility on the river.

It was named by Ludwig Leichhardt on 16 June 1845 after Sir Thomas Mitchell while he was on his overland expedition from Moreton Bay to Port Essington. It may have been previously named the Vereenighde River in 1623 by Dutch merchant and navigator Jan Carstensz.

Biophysical aspects
The Mitchell River and its tributaries have for a long time carved their way westwards through the rugged, weathered highlands of the Great Dividing Range, carrying away sediments to be deposited in the broad floodplains and wetlands of the Gulf Savannah country.

The rivers' waters "pulse" annually with monsoonal rains, seasonally collecting water from across the local tropical rainforests in the highlands to the east; the wet sclerophyll forests in the central uplands; a variety of woodlands plus savannah in the western plains; annually flooding with freshwater, the tidal plains, wetlands, estuaries, and mangroves of the lower Mitchell and coastal plains.

From source to mouth, the Mitchell River is joined by 34 tributaries including the McLeod River, Hodgkinson River, St George River, Dry River, Little Mitchell River, Walsh River, Lynd River, Palmer River and Alice River.

Protected areas within the Mitchell River catchment include the Hann Tableland, Mitchell-Alice Rivers, Chillagoe-Mungana Caves, part of Bulleringa to the south, and most of the Forty Mile Scrub national parks.

Fauna and flora
Being a large river system, the Mitchell River may contain within its catchment one of Australia's most ecologically diverse aquatic systems consisting of a rich variety of both wet and dry tropical monsoonal habitats.

The catchment ecology as a whole has been generally described as follows:

The vegetation in the Mitchell River Catchment area ranges from the World Heritage Wet Tropic rainforest on the eastern highlands to the open savannah on the western and lower Mitchell plains. The extensive mangroves and lagoon systems at the delta of the Mitchell River are recognised worldwide. The permanent waters in the upper catchment are associated with springs and water holes...

More specifically, while this ecologically diverse river system is relatively poorly studied, it is known to contain at least 18 rare, endangered or vulnerable animal species including the golden-shouldered parrot, the Gouldian finch and the northern bettong. The mouth of the river lies in the Gulf Plains Important Bird Area.

Towns
The major towns in the river's catchment are Kowanyama, Chillagoe, Dimbulah, Mount Carbine and Mount Molloy. Other smaller towns in the Mitchell River catchment include Mutchilba and Almaden.

History
Kunjen (also known as Koko Wanggara, Ngundjan and Olkola) is a language of Western Cape York. The Kunjen language region includes the landscape within the local government boundaries of Kowanyama Community Council and Cook Shire Council.

Yir Yiront (also known as Yiront, Jirjoront, Yir-yiront, and Kokomindjan) is an Australian Aboriginal language. Its traditional language region is in Western Cape York within the local government areas of Aboriginal Shire of Kowanyama and Shire of Cook, in the catchments of the Coleman River and Mitchell River. Following the removal of Aboriginal people from their traditional lands, it is also spoken in Pormpuraaw and Kowanyama.

Maps

 * Mitchell River Watershed Management Group's Map of the Mitchell River's catchment area
 * Mitchell River Watershed Management Group's Map of Towns, Communities, Stations and Riverways in the Catchment
 * Mitchell River Watershed Management Group's Map of the Biophysical Regions through which the Mitchell River passes
 * Queensland Department of Natural Resources and Water Map of Mitchell River Catchment waterways (including Water Resource Plan boundaries)

Organisations

 * Official homepage of Mitchell River Watershed Management Group Inc

Videos

 * Our World 2 Video & Brief on local Aboriginal Knowledge of SeaLevel Rise in Mitchell River catchment, including footage and the telling of some traditional knowledge for Mitchell River Accessed 28 January 2009

title: Mitchell River (Queensland)