Başlığın diğer anlamları için Uzay Yolu (anlam ayrımı) sayfasına bakınız.

Uzay Yolu (özgün adı: Star Trek), Gene Roddenberry tarafından oluşturulan bilimkurgu televizyon dizisi, film ve roman serisi. 11 kez dizi, 13 kez sinema filmi, yüzlerce kez roman, video oyunu ve hikâye olarak yayımlandı. 8 Eylül 2021 Çarşamba günü Uzay Yolu'nun ilk televizyon yayının 55. yılı kutlandı.

İnsanların galakside diğer bilinçli canlılarla birleşerek Birleşik Gezegenler Federasyonu'nu kurdukları, kurgusal bir 3. Dünya Savaşı sonrası bir geleceği tasvir eder.

Kahramanlar genelde fedakârdır ama zaman zaman sonuç almak için başka yollara baş vurabilirler. 1960'larda Orijinal Seri'de ve diğer serilerde olduğu gibi hikâyelerdeki çatışmalar ve politik boyutlar günümüz olaylarını yansıtır. Dizilerdeki emperyalizm, sınıf kavgası, ırkçılık, insan hakları ve teknolojinin etkileri gibi konular ilk yayınladıkları zaman olduğu gibi bugün de yankılanmaktadır.

Televizyon dizileri
Uzay Yolu 1966'da bir televizyon dizisi olarak hayata başladığında yaklaşık 6 senedir planlama aşamasındaydı. Orijinal Seri 3 sezon sonunda düşük reytingler yüzünden yayından kaldırılmasına rağmen kendisinden sonra 5 serinin daha yayınlanmasına sebep oldu. Bu 6 seri toplamda 726 bölüm veya 30 televizyon sezonuna denk gelmektedir. Bu da 570,75 saatlik program süresine denk gelir. Orijinal Seri Türkiye'de 17 Ekim 1972'de yayımlanmaya başladı.

Uzay Yolu: Orijinal Seri

(Star Trek: The Original Series)
Uzay Yolu ilk kez ABD'de 8 Eylül 1966 Perşembe günü NBC televizyonunda yayınlandı. Dizi William Shatner tarafından oynanan Kaptan Kirk'ün kumandasındaki Atılgan Yıldız Gemisi'nin mürettebatını ve onların "daha önce hiç kimsenin gitmediği yerlere cesurca gitmek" olan 5 yıllık görevinin hikâyelerini anlatmaktadır. Sadece 3 sezon sonunda dizi yayından kaldırıldı ve son bölüm 3 Haziran 1969'da gösterildi. Tekrarların gösterimini takriben bir kültürel fenomen haline geldi. İlk başta sadece Uzay Yolu olarak bilinmesine rağmen daha sonraki yıllarda Uzay Yolu: Orijinal Seri (Star Trek: Original Series) ya da Klasik Trek (Classic Trek) olarak anıldı. Şu anda başta Amerika olmak üzere birçok ülke televizyonunda hâlâ yayınlanmaktadır. Serinin 2006 Eylül'ünde dijital olarak yenilenmiş ve yüksek çözünürlükte tekrar dağıtılacağı açıklandı.

Uzay Yolu: Animasyon Seri

(Star Trek: The Animated Series)
Uzay Yolu: Animasyon Serisi Filmation adlı firma tarafından yapıldı ve iki sezon boyunca gösterimde kaldı. Orijinal seriden Walter Koenig haricinde diğer bütün başrol oyuncuları sesleri ile diziye katıldılar. Koenig bütçe sıkıntıları yüzünden yapımcılar tarafından çağrılmamıştı. Animasyon tekniği egzotik ve geniş uzaylı dünyaları ve manzaralarına izin verse de, bütçe sıkıntıları yüzünden animasyonlar vasat olarak kaldı. İlk başta Paramount tarafından onaylanmış olmasına rağmen tam olarak resmî Uzay Yolu sayılmadı. Buna rağmen bu serideki birçok eleman daha sonra dizilerde ve/veya filmlerde resmileştirildi. Örneğin Kirk'ün orta adı Tiberuis ilk olarak Animasyon seride ortaya atıldı, daha sonra Uzay Yolu VI: Keşfedilmemiş Ülke ile resmiyete kavuştu.

Uzay Yolu: Safha II

(Star Trek: Phase II)
Uzay Yolu: Safha II Paramount Televizyon tarafından 1978'de bayrak gemisi tv dizi olarak önerilmişti. Yapım başlamadan  12 bölümün senaryoları yazılmıştı. Dizi Orijinal serideki mürettabatın büyük bir bölümünü (Spock olarak geri dönmeyi reddeden Leonard Nimoy hariç) ikinci bir beş yıllık görev için bir araya getirecekti. Nimoy'un yerine Xon adında daha genç safkan bir Volkanlı düşünülmüştü, buna rağmen Nimoy'un misafir oyuncu olarak arada görüneceği umut ediliyordu. Setler yapılmış hatta ciddi rakamda test çekimleri yapılmıştı. Buna rağmen dördüncü bir televizyon ağının riski ve "o zamanlar yakın tarihte" yayınlanan Yıldız Savaşları filminin popülaritesi yüzünden Paramount haftalık bir dizi yerine bir sinema filmi yapmaya karar verdi. Bu serinin ilk bölümünün senaryosu Uzay Yolu: Sinema Filmi adlı ilk filmin senaryosu için temel oluşturdu. Diğer üç tanesi ise Uzay Yolu: Yeni Nesil için uyarlandı.

Uzay Yolu: Yeni Nesil

(Star Trek: The Next Generation)
Uzay Yolu: Yeni Nesil yaklaşık olarak Orijinal Seriden bir yüzyıl sonra geçmekte, gene Atılgan adında fakat daha yeni ve gelişmiş (Atılgan-D) yeni bir yıldız gemisi içermekte ve Kaptan Jean Luc Picard'ın (Patrick Stewart) emri altındaki yeni bir mürettebatın maceralarını anlatmaktadır. Dizi ilk olarak 28 Eylül 1987'de yayınlandı ve 23 Mayıs 1994'te son buldu. Yeni Nesil Uzay Yolu dizileri arasından en yüksek reytinglere sahipti ve yayınlandığı ilk birkaç yıl boyunca hep 1 numaralı dizi olarak kaldı. En iyi drama dalında bir Emmy için aday olan (1994 yılında) tek Uzay Yolu dizisi idi. Ayrıca en iyi televizyon programı olarak Peabody Ödülü'de kazandı.

 Uzay Yolu: Derin Uzay Dokuz

(Star Trek: Deep Space Nine)Uzay Yolu: Derin Uzay Dokuz Yeni Nesil ile aynı zamanda geçmektedir ve 1993'ten başlayarak yedi yıl boyunca yayınlandı. Bir yıldız gemisi yerine bir uzay istasyonunda geçen tek Uzay Yolu dizisidir. Dizi Kumandan (daha sonra Kaptan) Benjamin L. Sisko (Avery Brooks) tarafından yönetilen ve Bajoran sisteminde yeni keşfedilmiş ve sabit yegane Solucan deliği'nin (:en:wormhole) yanında bulunan uzay istasyonundaki mürettebatın ve istasyon sakinlerinin maceralarını izler. Hikâye hemen yakındaki Bajor gezegenin Cardassia'lılar tarafından işgali, Sisko benzersiz ruhsal rolü ve Dominion ile olan savaş gibi konuları da içerir. Derin Uzay Dokuz Gene Roddenberry'nin daha önceki serilerde yasakladığı uzun seri hikâye anlatımı, mürettebat içinde çatışma gibi konularla diğer Uzay Yolu serilerinden ayrılır..

 Uzay Yolu: Voyager

(Star Trek: Voyager)Uzay Yolu: Voyager yedi yıl boyunca yayınlandı. Kaptan Kathryn Janeway (Kate Mulgrew) adında bir kadın kaptan içeren tek Uzay Yolu dizisidir. Dizi USS Voyager'ın 70.000 ışık yılı uzaklıktaki Delta çeyreğinde(Delta Quadrant) kayboluşunu gösterir. 70 yıllık bir eve dönüş yolculuğu ile karşı karşıya olan mürettebat zorlukların üstesinden gelmek ve kendi aralarından çatışmaları yenmek zorundadır. Voyager orijinalde Uzay Yolu'nun birçok tanıdıklarından uzaktı, fakat daha sonraki sezonlarda Borg ve Q gibi tanıdık simalar görünmeye başladılar.STARTREK.COM : Episode (Q2)  En son erişim  24 Ağustos, 2006

 Uzay Yolu: Atılgan Uzay Yolu: Atılgan (Star Trek: Enterprise)(ilk olarak sadece  "Atılgan" olarak yayınlandı) diğer Uzay Yolu serilerinin başlangıcı niteliğindedir. Pilot bölüm Federasyon'un kurulmasından on yıl önce geçer. Uzay Yolu: İlk Temas filmindeki olaylar ve orijinal Uzay Yolu arasındaki bir zamanda geçer. Dizi Kaptan Jonathan Archer (Scott Bakula) yönetimi altındaki Dünya Yıldız Gemisi Atılgan uzayı keşfini konu alır. Atılgan kendisinden önceki bütün insan yapımı taşıtlardan daha hızlıdır ve daha uzağa gidebilmektedir. Atılgan'ın başlangıçtaki reytingleri oldukça güçlü olmasına rağmen hızla düşmeye başladı. Orijinal seride olduğu gibi fanlar sayesinde 2. ve 3. sezonda da yayında kalması sağlandı. Seri dördüncü yılında da reyting kaybetmeye devam etti ve Paramount 2005 başında seriyi iptal etti.

 Star Trek: Discovery Star Trek: Discovery, internette yayınlanan ilk Star Trek serisidir. İlk iki sezonu kabaca Orijinal Seri'den on yıl önce geçmektedir.  24 Eylül 2017'de Amerika Birleşik Devletleri ve Kanada'da CBS'de gösterime girdi. Dizi şu anda Amerika Birleşik Devletleri'nde Paramount+'ta devam etmektedir. Netflix, diziyi -Kanada dışında- dünya çapında dağıtmaktadır.

Discovery, her sezonda tek bir uzun hikâyenin takip ettiği bir seridir. Önceki Star Trek serilerinden ayrı olarak, ana kahraman Michael Burnham (Martin-Green tarafından canlandırılmıştır), serinin büyük bir kısmında geminin kaptanı bile değildir. İlk sezon Birleşik Gezegenler Federasyonu ve Klingon İmparatorluğu arasındaki bir savaşı izler. Discovery 'nin ilk 2 sezonu 23.yüzyılın ortalarında (2256-2259 yıllarında) geçerken, 3. ve 4. sezonları 32.yüzyıl sonlarında (2188-3190 yıllarında) geçer.

 Star Trek: Picard Star Trek: Picard, Discovery gibi CBS All Access için oluşturulmuş bir seridir. 23 Ocak 2020'de gösterime girmiştir. Yeni Nesil'den yaklaşık 30 yıl sonrasında geçen dizide Patrick Stewart, Jean-Luc Picard rolünü yeniden canlandırıyor.  İlk sezon Picard'ın emekliliğini, geçmişteki başarısızlıkları olarak gördüğü şeylerin kefaretini aramasını ve bir maceraya atılmasını konu alıyor. Dizinin 10 bölümlük 2. sezonunun "The Star Gazer" adlı ilk bölümü 3 Mart 2022'de Amazon Prime üzerinde yayına girmiştir.

 Star Trek: Lower Decks Star Trek: Lower Decks, Rick and Morty yazarı Mike McMahan tarafından yaratılan bir animasyon yetişkin komedi dizisidir. Dizi, "Yıldız Filosu'nun en az önemli gemilerinden birinin" destek ekibini takip ediyor.  Dizinin prömiyeri 6 Ağustos 2020'de CBS All Access'te yapıldı.

 Star Trek: Prodigy Star Trek: Prodigy, Kevin ve Dan Hageman tarafından Paramount+ ve kablolu kanal Nickelodeon için oluşturulan bir animasyon dizisidir.  Dizi, macera aramak için terk edilmiş bir yıldız gemisini kullanan bir grup genci takip ediyor. Dizinin prömiyeri 28 Ekim 2021'de yapıldı.

 Star Trek: Strange New Worlds

 Sinema filmleri

Paramount Pictures bugüne kadar on adet Uzay Yolu filmi yayınladı. Bunlardan ilk altısı Orijinal Seri'nin kahramanlarını, geri kalan dördü ise Yeni Nesil'in kahramanlarını içermektedir. Kuzey Amerika ve Birleşik Krallık'ta altıncı filmden sonra numara verilmek adetinden vazgeçilmesine rağmen Avrupa'da hala numaralama sistemi devam etmektedir. Uzay Yolu hayranları arasında çift rakam ile başlayan filmlerin tek ile başlayanlara oranla daha başarılı olduğu gibi bir batıl inanç vardır. Hayranlara göre 2, 4, 6 ve 8 numaralı filmler tepede Uzay Yolu I, V ve IX ise dipte yer almaktadır. 2009 yılında J.J. Abrams'ın orijinal diziye yeni bir yorum getirmesiyle seri yeniden başlatılmış oldu.

 Diğer hikâye kurguları ve resmiyet

Uzay Yolu markası resmî olarak yayınlanmış 8 televizyon dizisinden ve bugüne kadar çevrilmiş 13 filmden oluşur. Bunun haricinde 3 animasyon dizi, romanlar, video oyunları, çizgi romanlar ve Uzay Yolu evreni ile ilgili diğer malzemeler Paramount Pictures tarafından lisanslanmış olmalarına rağmen resmî sayılmazlar.

Romanlar genellikle televizyon dizileri sırasında tam açıklanmamış olayları konu alarak Uzay Yolu evrenindeki boşlukları tamamlarlar. Uzay Yolu'nun sahibi Paramount Pictures kabul etmese de, hayranlar romanları da resmî Uzay Yolu malzemesi olarak saymaktadırlar. Birçok yazar kendi romanları için de kendi serilerini de yaratmışlardır.

Televizyon dizileri ve Paramount tarafından çekilen sinema filmleri dışında, Uzay Yolu markası bir sürü yazar ve sanatçı tarafından Genişletilmiş Uzay Yolu Evreni adıyla genişlemiştir. Genelde bu yazar ve sanatçılar genelde var olan devamlığı sürdürmek ya da kendi hikâyelerini yazmakta özgürdürler. Benzer biçimde dizi ve sinema yapımcıları da resmî sayılmayan bu eserlere bağlı kalmak zorunda değillerdir.

Bunun dışında Uzay Yolu evreninde geçen birçok hayran yapımı film de bulunmaktadır. Hatta bu filmlerden bazıları (Ör: Of Gods and Men) Uzay Yolu'nda oynamış ve/veya yönetmenlik yapmış sanatçıları içerebilir.

 "Uzay Yolu" ismi Star Trek kelimesi Türkçeye Uzay Yolu olarak çevrilmesine rağmen tam çeviri Yıldız Yolculuğu terimine daha yakındır. Star Trek ismi bugüne kadar yayınlanan tüm dizi ve filmler içinde sadece Uzay Yolu: İlk Temas'ta warp sürücüsünün kaşifi Zefram Cochrane tarafından dile getirildi. Bunun dışında Yeni Nesil'in son bölümünde "...trek through the stars..." terimini kullanmıştır. Uzay Yolu'nun orijinal film müziği "Star Trek" kelimesini içeren şarkı sözlerine sahipti fakat daha sonra sadece enstrümantal olarak kullanıldı.

 Kültürel etki

Uzay Yolu bugün Paramount'un sahip olduğu milyar dolarlık bir endüstridir. Gene Roddenberry Orijinal Seri'yi klasik bir macera draması olarak NBC'ye sattı. İlk olarak diziyi (Wagon Train to the Stars) olarak adlandırmıştı. Bir yıldız gemisinde geçmesine ve gelecekte yaşanmasında rağmen Roddenberry bu analojiyi kullanarak ve onları umut, hümanizm ile harmanlayarak güncel dünya problemlerini ekrana taşımak istemişti. Açılış cümlesinde "Daha önce hiçbir insanın gitmediği yerlere cesurca gitmek..." sözü neredeyse birebir olarak Beyaz Saray'ın 1957'deki Sputnik uçuşundan sonra yayınlanan bir kitapçığından alınmıştır. Kirk, Spock ve Doktor McCoy'dan oluşan merkezi üçlü klasik mitolojiden örneklenmiştir. Güncel olaylar ve insanlar arasındaki farklar üzerinde durmak amacı ile mürettebat etnik olarak farklı bireylerden oluşturulmuştur.

"Uzay Yolu" ismi, Kaptan Kirk, Mr. Spock vs. bugün dünyada en çok bilinen isimler arasındadırlar. Uzay Yolu'nun kültürel etkisi uzun yaşamını ve popülerliğini geride bırakmıştır. Günümüzde Uzay Yolu ve türevleri birçok ülkenin televizyonlarında yayınlanmaktadırlar. Hayranlar kendilerine Trekkie adını takmışlardır ve şovun etrafında bir alt-kültür oluşmuştur.

Uzay Yolu otomatik kapılar, tablet PC'ler, PDA'lar cep telefonları gibi bir sürü günümüz teknolojisi için esin kaynağı olmuştur. Işınlanma olarak tasvir edilen madde-enerji dönüşümünü popüler hale getirmiştir. Kaptan Kirk'in "Işınla, Scotty" (:en:Beam me up, Scotty) ve doktorun "Ölmüş, Jim" sözleri halk diline girmiştir. 1976'da gelen mektuplar ve kampanyalar sonunda NASA ilk uzay mekiğini kurgusal yıldız gemisi Atılgan'a atıfla Enterprise (Atılgan) olarak isimlendirmiştir.

 Şu anki durum ve gelecek

2005 yılında son seri Atılganın iptal edilmesinden sonra Uzay Yolu yirmi beş seneden beri ilk defa yapımda ve/veya planlama aşamasında bir seri ya da filmsiz buldu. Uzay Yolu: Derin Uzay Dokuz selefinin yüksek reytinglerine ulaşamadı. Daha sonra Uzay Yolu: Voyager'ın iptal edilme dedikoduları, Atılgan'ın iptal edilmesi ve son film Uzay Yolu: Nemesis'in gişede beklenen başarıyı gösterememesi markanın öldüğü şeklinde yorumlandı. Tüm bunlara rağmen Nisan 2006'da yeni bir sinema filminin resmî olarak ilan edilmesi markanın henüz ölmediğinin göstergesi.

Uzay Yolu serileri bugün birçok ülkenin birçok kanalında tekrar tekrar yayınlanmaktadırlar.

Notlar
Adını seride, 2063 yılının Nisan ayında Vulcanlarla insanlar arasında gerçekleşen ilk temastan alan "İlk Temas Günü" her yıl Nisan ayında Uzay Yolu hayranları tarafından çeşitli etkinliklerle kutlanıyor.

Dizinin her bölümü istisnalar dışında, farklı ellerden çıkan senaryolarla ve farklı yönetmenler tarafından çekilmiştir. Bu tekdüzeliği önlemiş ve her bölüme ayrı bir bakış katmıştır.

17 Ekim 1972'de de Türkiye'de siyah beyaz tek kanallı TRT televizyonunda Uzay Yolu adıyla gösterilmeye başlandı. Aynı yıl Günaydın gazetesi Uzay Yolu'nu çizgi roman formatında yayınladı.

TRT tarafından duyarlı bir şekilde yapılan çeviri ve seslendirmeler, o dönemlerde pek az kişinin kullandığı tarayıcı, alıngaç, bilgisayar gibi kelimelerin halk tarafından benimsenerek dilimize kazandırılmasını sağlamıştır. O yıllarda çok fazla bilinmeyen Lazer, ışınlama, ışık hızı gibi birçok bilimsel kavram ile de bu dizi sayesinde tanışılmıştı. Türkiye 'de 1984'ten 1998'e kadar 6 kanal dolaşmıştır: TRT 1, Star TV, Show TV, Cine 5, Kanal 6 ve TGRT.

Kaptan Kirk'in iradesi, Spock'ın mantığı, işlenen bilimsel temalar, o zamanlarda birçok kişiye ilham kaynağı olmuştur.

Uzay Yolu Turist Ömer Uzay Yolunda (1973) filmine de ilham kaynağı olmuştur. Hulki Saner'in yönettiği filmde başrollerde Sadri Alışık ve o yıllarda TRT de yayınlanan dizideki seslendirmeyi yapan tiyatro sanatçıları oynamışlardı. Bilal Tahir Sümer seslendirme ekibinin başlıcalarındandır. Hulki Saner'in  filmi, dünya sinemasında ilk Uzay Yolu uyarlaması olarak bilinir.

Kaynakça
Bu makaledeki bilgilerin büyük çoğunluğu İngilizce Wikipedia'daki :en:star trek'ten çevrilmiştir.
Aynı zamanda Uzay Yolu resmî sitesinden de bilgiler bulunmaktadır.

Kaynak notları

Dış bağlantılar

 Memory Alpha - Star Trek Wiki Encyclopedia.
 TrekCore.com  - Largest Star Trek Multimedia Outlet
 StartrekMovie.com - Official Movie Site 2009

Amerika Birleşik Devletleri Çıkışlı Diziler
1966'da başlayan Amerika Birleşik Devletleri televizyon dizileri

Uzay Yolu


Kurudere, Zonguldak ilinin Devrek ilçesine bağlı bir köydür.

Tarihçe
Köy, Eveyikli köyüne bağlı beş mahallenin birleştirilmesiyle kuruldu.

Coğrafya
Köy, Zonguldak il merkezine 82 km, Devrek ilçe merkezine 27 km uzaklıktadır.

Nüfus

Kaynakça

Dış bağlantılar

Devrek belde ve köyleri

Kurudere, Devrek


Le projet de centrale nucléaire de Kharkiv (en ukrainien : Харківська АТЕЦ) est un projet de centrale nucléaire abandonné, située près du village de Birky, dans l'oblast de Kharkiv, en Ukraine. Deux réacteurs nucléaires VVER-1000 étaient censées produire de l'électricité, ainsi que fournir de la chaleur à Kharkiv, ce qui était prévu par le plan directeur de développement de Kharkiv de 1986.

Le projet nucléaire de Kharkiv, d'une capacité de , a été développé sur la base d'une décision du Conseil des ministres de l'URSS en date du . La période de construction de l'APEC était programmée de 1985 à 1996. Il était prévue que la première unité soit mise en service en 1993 et la seconde en 1995.

La construction des bâtiments principaux n'a jamais été entamée, seuls la construction des infrastructures et les préparatifs des gros travaux ont été réalisés. À la suite de la catastrophe de Tchernobyl suivi de l'effondrement de l'Union soviétique, le projet fut abandonné.

La construction d'un village résidentiel était prévue pour la réinstallation du personnel d'exploitation, de construction et de montage. Des immeubles de grande hauteur inachevés sont présents et  de terres ont été alloués à ces constructions, dont  de terres arables et  de pâturages.

Kharkiv
Kharkiv
Économie à Kharkiv

Centrale nucléaire de Kharkiv


is a district located in Kumamoto Prefecture, Japan.

Following the Tamana merger (but with 2003 population estimates), the district has an estimated population of 47,029 and the density of 222 persons per square kilometer. The total area is 211.54 km2.

Towns and villages
Gyokutō
Nagasu
Nagomi
Nankan

Mergers
See Merger and dissolution of municipalities of Japan.
On October 3, 2005 the towns of Taimei, Tensui and Yokoshima merged into the expanded city of Tamana.
On March 1, 2006 the towns of Kikusui and Mikawa merged to form the new town of Nagomi.

Districts in Kumamoto Prefecture

Tamana District, Kumamoto


was a district located in Nishimikawa Region in central Aichi Prefecture, Japan.

The entire district is now part of the city of Toyota.

As of 2004 (the last data available), the district had an estimated population of 16,703 with a density of 43.84 persons per km2. Its total area was 381.06 km2.

Municipalities
Prior to its dissolution, the district consisted of three towns and one village:

 Asuke
 Asahi
 Inabu
 Shimoyama

Notes

History

Kamo District (加茂郡) was one of the ancient districts of Shinano Province, but was transferred to Mikawa Province during the Sengoku period. In the cadastral reforms of the early Meiji period, on July 22, 1878, Kamo District was divided into Higashikamo District and Nishikamo District within Aichi Prefecture. With the organization of municipalities on October 1, 1889, Higashikamo District was divided into 18 villages.

District Timeline

 The village of Asuke was elevated to town status on December 17, 1890, and two new villages were created in 1889 and 1890. In a round of consolidation, the remaining number of villages was reduced from 19 to six in 1906.
 On April 1, 1955, three of the remaining villages (Morioka, Kamo, and Aro) were annexed by the town of Asuke; however, a new village (Asahi) was created through a border adjustment with parts of the village of Sanno (formerly from Ena District, Gifu Prefecture).
 On November 1, 1961, the village of Matsudaira gained town status, followed by the village of Asahi.
 On April 1, 1967, the town of Matsudaira was annexed by the city of Koromo.

Recent mergers
 On October 1, 2003 - The town of Inabu was transferred from Kitashitara District to Higashikamo District, leaving the district with two towns and one village.
 On April 1, 2005 - The towns of Asuke, Asahi and Inabu, and the village of Shimoyama, along with the town of Fujioka, and the village of Obara (both from Nishikamo District), were all merged into the expanded city of Toyota. Therefore, Higashikamo District was dissolved as a result of this merger.

See also
 List of dissolved districts of Japan
 Nishikamo District, Aichi
 Kamo District, Gifu
 Kamo District, Hiroshima
 Kamo District, Shizuoka

External links
 Counties of Japan

Former districts of Aichi Prefecture

Higashikamo District


En théorie des graphes, la matrice de Tutte d'un graphe  est une matrice utilisée pour déterminer l'existence d'un couplage parfait, soit d'un ensemble d'arêtes incidentes à chaque sommet exactement une fois.

Si l'ensemble des sommets est , alors la matrice de Tutte de  est une matrice de taille  ayant pour coefficients :

où  sont les indéterminées. Le déterminant de cette matrice antisymétrique est un polynôme (en les variables ) : il coïncide avec le déterminant pfaffien de  et est non-identiquement nul si et seulement si un couplage parfait existe. (Ce polynôme ne doit pas être confondu avec le polynôme de Tutte de ).

La nom matrice de Tutte provient du mathématicien W. T. Tutte, et est la généralisation de la matrice d'Edmonds pour les graphes bipartis équilibrés.

Théorie des graphes

Matrice de Tutte


Steven Krueger (né le ) est un acteur américain. Il est connu pour ses rôles de l'entraîneur Ben Scott dans la série à succès Yellowjackets et de Josh Rosza dans la série The Originals

Vie et carrière
Krueger est né à Appleton, Wisconsin et a grandi à Sarasota, Floride. Il a fait ses débuts d'acteur peu de temps après avoir déménagé à Los Angeles fin 2009 dans un épisode de la série 90210 . Au cours des années suivantes, il a fait un certain nombre d'apparitions récurrentes dans des séries notables comme Pretty Little Liars, Workaholics, Parenthood et Two And a Half Men.

En 2013, Krueger joue un rôle récurrent dans The Originals, le spin-off de la série à succès The Vampire Diaries . Son personnage, Josh, fut le premier personnage gay introduit dans la série  et devait initialement apparaître dans trois épisodes . Cependant, très apprécié des fans et à la fin de 2013, son rôle dans la série fut plus régulier. il est devenu une partie intégrante de la série tout au long de sa dernière saison en 2018.

Depuis la fin de The Originals, il a continué à travailler sur un certain nombre de série. En novembre 2019, il a été annoncé qu'il rejoignait le casting du pilote de Yellowjackets, réalisé par Karyn Kusama. Krueger joue Ben Scott, l'entraîneur adjoint de l'équipe de football des filles du lycée qui est bloqué dans les montagnes après avoir survécu à un accident d'avion il y a 25 ans. Yellowjackets a fait ses débuts en novembre 2021. Toujours en 2021, Krueger a joué un rôle récurrent en tant que Heath dans la troisième saison de  Roswell, Nouveau-Mexique.

Filmographie

Cinéma
 2015 : Chair de poule, le film : Davidson
 2016 : Satanic : David

Télévision
 2009 : 90210 Beverly Hills : Nouvelle Génération : Vince (saison 2, épisode 6)
 2009 : Cold Case : Affaires classées : Étudiant (saison 7, épisode 9)
 2010 : Parenthood : Brody (saison 1, épisode 7)
 2010 : Les Experts : Manhattan : Greg (saison 6, épisode 22)
 2010 : Super Hero Family : Reynolds (épisode 4)
 2010 : The Middle : Esteban (saison 2, épisode 5)
 2010-2013 : Pretty Little Liars : Ben Coogan (3 épisodes)
 2011 :  : Acteur
 2011 : Workaholics : Quaid Franklin (saison 2, épisode 1)
 2012 : Madison High (téléfilm) : Pete
 2012 : Zeke et Luther : Vin Jackman (saison 3, 2 épisodes)
 2012-2013 : Mon oncle Charlie : Sean (saison 10, 2 épisodes)
 2013 : Anger Management : Ryan Hoggett (saison 2, épisode 22)
 2013-2018 : The Originals : Josh Rosza (46 épisodes)
 2014 : Mes parents terribles (téléfilm) : Brady
 2015 : Hawaii 5-0 : Eran Dobrian (saison 5, épisode 19)
 2017 : Un terrible secret (téléfilm) : David
 2017 :  : Orson (saison 1, épisode 3)
 2019 : Good Trouble : Eli (saison 1, épisode 7)
 2019 : NCIS : Enquêtes spéciales : Andrew Townsley (saison 16, épisode 15)
 2021 : Roswell, New Mexico : Heath Tuchman (saison 3, 9 épisodes)
 2021-2022 : Yellowjackets : Ben Scott (10 épisodes)

Références

Liens externes

Naissance en mai 1989
Personnalité américaine née d'un parent allemand
Personnalité américaine née d'un parent anglais
Acteur américain de télévision
Acteur américain de cinéma
Étudiant de l'université de Virginie
Naissance au Wisconsin

Steven Krueger


احتياطي النفط  هو كمية النفط التي يمكن استخراجها تقنيًا بتكلفة مجدية من الناحية المالية بناءً على سعر النفط الحالي. بناءً على ذلك ستتغير الاحتياطيات بتغير السعر، على عكس مصادر النفط التي تتضمن كل النفط الذي يمكن استخراجه تقنيًا بأي سعر. ربما تتعلق الاحتياطيات ببئر، أو خزان (مكمن)، أو حقل، أو دولة، أو العالم. ترتبط التصنيفات المختلفة للاحتياطات بدرجة يقينها.

يشير حجم النفط الموجود في خزان (نفط المكمن) (بالإنجليزية: oil in place) إلى إجمالي الكمية المقدرة من النفط في خزان معين، وتشمل كميتي النفط القابلة وغير القابلة للإنتاج. لا يمكن استخراج سوى نسبة ضئيلة من هذا النفط وإحضارها إلى السطح، ويعود السبب في ذلك إلى خصائص الخزانات (المكامن) والتحديدات على التكنولوجيات المستخدمة في استخراج النفط، وتعتبر النسبة القابلة للإنتاج فقط احتياطيًا. يطلق على النسبة ما بين الاحتياطيات وكمية النفط الإجمالية في خزان معين «عامل الاستخلاص» (عامل الاسترداد). يعتمد تحديد عامل الاستخلاص لحقل معين على عدة سمات للعملية، بما في ذلك الطريقة المستخدمة في استخراج النفط والتطورات التكنولوجية.

استنادًا إلى بيانات منظمة أوبك في بداية عام 2013، توجد أكبر احتياطيات النفط المثبتة والتي تضم احتياطيات النفط غير التقليدية أيضًا، في فنزويلا (بنسبة 20% من الاحتياطيات العالمية)، والسعودية (بنسبة 18% من الاحتياطيات العالمية)، وكندا (بنسبة 13% من الاحتياطيات العالمية)، وإيران (بنسبة 9%).

نظرًا لعدم إمكانية فحص جيولوجيا السطح السفلي للأرض بشكل مباشر، يجب استخدام تقنيات غير مباشرة (مثل الجيوفيزياء الاستكشافية) لتقدير حجم الموارد وإمكانية استخراجها. رغم زيادة التكنولوجيات الحديثة (مثل المسح السيزمي) من دقة التقنيات المستخدمة، ما زالت توجد شكوك كبيرة. بشكل عام، تعد معظم التقديرات المبكرة لاحتياطي حقل النفط، تقديرات متحفظة وتميل إلى النمو بمرور الوقت. تسمى هذه الظاهرة بنمو الاحتياطيات.

لا تكشف معظم الدول المنتجة للنفط عن البيانات الخاصة بهندسة مكامن حقولها، وتقدم بدلًا من ذلك مزاعم غير مراجعة لاحتياطياتها من النفط. يشتبه أن الأرقام التي كشفت عنها بعض الحكومات الوطنية جرى التلاعب بها لأسباب سياسية.

تصنيفات
تبنى جميع تقديرات الاحتياطيات على اليقين، تبعًا للكمية المتاحة من البيانات الجيولوجية والهندسية الموثوقة وتفسيرها. يمكن التعبير عن الدرجة النسبية لعدم اليقين بتقسيم الاحتياطيات إلى صنفين رئيسيين، وهي: «مثبتة» أو «غير مثبتة». يمكن أيضًا تقسيم الاحتياطيات غير المثبتة إلى صنفين فرعيين: «محتملة» و«ممكنة» للإشارة إلى الدرجة النسبية لعدم اليقين بشأن وجودها. تستند التعاريف الأكثر قبولًا إلى التعاريف التي اعتمدتها جمعية مهندسي البترول والمجلس العالمي للبترول في عام 1997.

احتياطات مثبتة (مؤكدة)
الاحتياطيات المثبتة هي الاحتياطيات التي يزعم تمتعها بقدر معقول من اليقين (لا تقل عادةً عن 90% من الثقة) ويمكن استخراجها في ظل الظروف الاقتصادية والسياسية القائمة، بالاستعانة بالتكنولوجيا المتاحة. يرمز المتخصصون في الصناعة إليها بـ«بّي90» (أي يوجد يقين بنسبة 90% من الإنتاج). تعرف الاحتياطيات المثبتة في مجال الصناعة بـ«1بّي».

تقسم الاحتياطيات المثبتة إلى «مثبتة نامية» و«مثبتة غير نامية». الاحتياطيات المثبتة النامية هي الاحتياطات التي يمكن إنتاجها من الآبار والثقوب الموجودة، أو من خزانات إضافية تتطلب الحد الأدنى من الاستثمارات (نسبة نفقات التشغيل). تتطلب الاحتياطيات المثبتة غير النامية استثمارات رأسمالية إضافية (مثل حفر آبار جديدة) لإحضار النفط إلى السطح.

حتى ديسمبر عام 2009، كانت الاحتياطيات المثبتة «1بّي» النوع الوحيد الذي سمحت هيئة الأوراق المالية والبورصات الأمريكية لشركات النفط بإبلاغ المستثمرين عنه. يجب على الشركات المدرجة في البورصات الأمريكية إثبات مزاعمها، لكن الكثير من الحكومات وشركات النفط الوطنية لا تكشف عن البيانات المدققة لتدعم مزاعمها. منذ يناير عام 2010 وإلى الآن، تسمح هيئة الأوراق المالية والبورصات الأمريكية للشركات بتقديم معلومات اختيارية إضافية تعلن فيها عن وجود 2بّي (الاحتياطيات المثبتة والمحتملة) و3بّي (الاحتياطيات المثبتة والمحتملة والممكنة) لكن بشرط أن يتحقق استشاريون مؤهلون من طرف ثالث من التقييم، تختار الكثير من الشركات استخدام تقديرات 2بّي و3بّي من أجل الأغراض الداخلية فقط.

احتياطيات غير مثبتة (غير مؤكدة)
تعتمد الاحتياطيات غير المثبتة على البيانات الجيولوجية أو الهندسية أو كلتيهما معًا، وتشبه في ذلك البيانات المستخدمة في تقديرات الاحتياطيات المثبتة، لكن يَحول عدم اليقين التقني أو التعاقدي أو التنظيمي (التقريري) دون تصنيف هذه الاحتياطيات على أنها مثبتة. ربما تستخدم شركات النفط والوكالات الحكومية الاحتياطيات غير المثبتة داخليًا لأغراض التخطيط المستقبلية، لكنها لا تجمعها بانتظام. تصنف الاحتياطيات غير المثبتة إلى محتملة وممكنة.

تُنسب الاحتياطيات المحتملة إلى التراكمات المعروفة ويزعم حصولها على 50% من مستوى الثقة في استخراجها. يرمز المتخصصون في مجال الصناعة إليها بـ«بّي50» (أي يوجد يقين بنسبة 50% من الإنتاج). يُرمز إلى مجموع الاحتياطيات المثبتة والمحتملة في الصناعة بـ«2بّي» (مثبتة ومحتملة).

تُنسب الاحتياطيات الممكنة إلى التراكمات المعروفة التي تملك فرصة أقل لاستخراجها مقارنة بالاحتياطيات المحتملة. يُرمز إلى هذا الصنف من الاحتياطيات بـ«بّي10» أي أنها تملك نسبة 10% من اليقين في إنتاجها.

يجب أن تشمل أسباب تصنيف الاحتياطيات قدر الإمكان على تفسيرات جيولوجية متباينة، واحتياطيات لا يمكن إنتاجها بمعدلات تجارية، وعلى عدم اليقين بسبب ملء الاحتياطيات (نتيجة التسرب من المناطق المجاورة)، والاحتياطيات المتوقعة بالاعتماد على طرق الاستخراج المستقبلية. يُرمز لمجموع احتياطيات الموارد المثبتة والمحتملة والممكنة في الصناعة بـ«3بّي» (مثبتة ومحتملة وممكنة).

تصنيفات الاحتياطي الروسي
تقابل التصنيفات «إيه» و«بي» و«سي1» في روسيا، الاحتياطيات القابلة للإنتاج المثبتة النامية، والاحتياطيات غير المنتجة المثبتة النامية، والاحتياطيات المثبتة غير النامية على التوالي. يُرمز إلى الاحتياطيات المثبتة بـ«إيه.بي.سي1». يتضمن التصنيف الروسي «سي2» الاحتياطيات المحتملة والممكنة.

احتياطي النفط الاستراتيجي
تحتفظ العديد من الدول باحتياطيات النفط التي تسيطر عليها الحكومة للأسباب اقتصادية وأمنية. وفقًا لإدارة معلومات الطاقة الأمريكية، تودع نحو 4.1 مليار برميل (650 مليون متر مكعب) من النفط في الاحتياطيات الاستراتيجية، وتسيطر الحكومة على 1.4 مليار برميل منها. لا تحسب هذه الاحتياطيات عادة ضمن احتياطيات النفط الوطنية.

{| class="wikitable" border="1"
|-
! colspan=4 style="background: #6688AA; color: white;" |الترتيب على حسب احتياطي النفط المؤكد (2007)  (مليار برميل)
|-
! الدولة
! الاحتياطي
|-
|
|297.7
|-
|
|268.4
|-
|
|173.2
|-
|
|157.3
|-
|
|140.3
|-
|
|140
|-
|
|97.8
|-
|
|80
|-
|
|48.47
|-
|
|37.14
|-
|
|30
|-
|
|21
|-
|
|16
|-
|
|15.2
|-
|
|12.4
|-
|
| 12.3
|-
|
| 11.8
|}

 إحصائيات الطاقة من الحكومة الأمريكية
 تشكل احتياطيات النفط للدول التابعة لأوبك 78٪ (939 مليار برميل) من احتياطي النفط العالمي

انظر أيضا
 قائمة الدول حسب استهلاك النفط

المراجع

احتياطيات النفط
ذروة النفط
نفط

احتياطي النفط


Die P.C. Hooftstraat im Stadtteil Oud-Zuid in Amsterdam ist eine der teuersten Einkaufsstraßen der niederländischen Metropole. Ihren Namen hat sie von Pieter Corneliszoon Hooft, einem niederländischen Dichter.

Sie beherbergt mehr elegante Ladengeschäfte mit luxuriöser Designer-Ware, Parfüm, Schmuck, Kunst und Antiquitäten als irgendeine andere Straße der niederländischen Hauptstadt. Internationale Modemarken wie Burberry, Gucci, Prada, Giorgio Armani, Ralph Lauren, Louis Vuitton, Yves Saint Laurent, Hermès, Chanel und viele mehr haben auf dieser Straße ihre  Filialen angesiedelt.
Sie beginnt westlich am Vondelpark und führt dann etwa 700 Meter in Richtung Osten bis zur Straße "Stadhouderskade".

Die nächsten Straßenbahnhaltestellen befinden sich im Osten am Rijksmuseum und im Westen an der Van Baerlestraat.

Amsterdam-Zuid
Straße in Amsterdam

P.C. Hooftstraat


WinFS (short for Windows Future Storage) was the code name for a canceled data storage and management system project based on relational databases, developed by Microsoft and first demonstrated in 2003 as an advanced storage subsystem for the Microsoft Windows operating system, designed for persistence and management of structured, semi-structured and unstructured data.

WinFS includes a relational database for storage of information, and allows any type of information to be stored in it, provided there is a well defined schema for the type. Individual data items could then be related together by relationships, which are either inferred by the system based on certain attributes or explicitly stated by the user. As the data has a well defined schema, any application can reuse the data; and using the relationships, related data can be effectively organized as well as retrieved. Because the system knows the structure and intent of the information, it can be used to make complex queries that enable advanced searching through the data and aggregating various data items by exploiting the relationships between them.

While WinFS and its shared type schema make it possible for an application to recognize the different data types, the application still has to be coded to render the different data types. Consequently, it would not allow development of a single application that can view or edit all data types; rather, what WinFS enables applications to do is understand the structure of all data and extract the information that they can use further. When WinFS was introduced at the 2003 Professional Developers Conference, Microsoft also released a video presentation, named IWish, showing mockup interfaces that showed how applications would expose interfaces that take advantage of a unified type system. The concepts shown in the video ranged from applications using the relationships of items to dynamically offer filtering options to applications grouping multiple related data types and rendering them in a unified presentation.

WinFS was billed as one of the pillars of the "Longhorn" wave of technologies, and would ship as part of the next version of Windows.  It was subsequently decided that WinFS would ship after the release of Windows Vista, but those plans were shelved in June 2006, with some of its component technologies being integrated into ADO.NET and Microsoft SQL Server.

Motivation
Many filesystems found on common operating systems, including the NTFS filesystem which is used in modern versions of Microsoft Windows, store files and other objects only as a stream of bytes, and have little or no information about the data stored in the files.  Such file systems also provide only a single way of organizing the files, namely via directories and file names.

Because a file system has no knowledge about the data it stores, applications tend to use their own, often proprietary, file formats. This hampers sharing of data between multiple applications. It becomes difficult to create an application which processes information from multiple file types, because the programmers have to understand the structure and semantics of all the files. Using common file formats is a workaround to this problem but not a universal solution; there is no guarantee that all applications will use the format. Data with standardized schema, such as XML documents and relational data fare better, as they have a standardized structure and run-time requirements.

Also, a traditional file system can retrieve and search data based only on the filename, because the only knowledge it has about the data is the name of the files that store the data.  A better solution is to tag files with attributes that describe them.  Attributes are metadata about the files such as the type of file (such as document, picture, music, creator, etc.). This allows files to be searched for by their attributes, in ways not possible using a folder hierarchy, such as finding "pictures which have person X". The attributes can be recognizable by either the file system natively, or via some extension. Desktop search applications take this concept a step further. They extract data, including attributes, from files and index it. To extract the data, they use a filter for each file format. This allows for searching based on both the file's attributes and the data in it.

However, this still does not help in managing related data, as disparate items do not have any relationships defined. For example, it is impossible to search for "the phone numbers of all persons who live in Acapulco and each have more than 100 appearances in my photo collection and from whom I have had e-mail within the last month". Such a search could not be done unless it is based on a data model which has both the semantics as well as relationships of data defined.  WinFS aims to provide such a data model and the runtime infrastructure that can be used to store the data, as well as the relationships between data items according to the data model, doing so at a satisfactory level of performance.

Overview
WinFS natively recognizes different types of data, such as  picture, e-mail, document, audio, video, calendar, contact, rather than just leaving them as raw unanalyzed bytestreams (as most file systems do). Data stored and managed by the system are instances of the data type recognized by the WinFS runtime. The data are structured by means of properties. For example, an instance of a résumé type will surface the data by exposing properties, such as Name, Educational Qualification, Experience. Each property may be a simple type (strings, integers, dates) or complex types (contacts). Different data types expose different properties. Besides that, WinFS also allows different data instances to be related together; such as a document and a contact can be related by an Authored By relationship. Relationships are also exposed as properties; for example if a document is related to a contact by a Created By relationship, then the document will have a Created By property. When it is accessed, the relationship is traversed and the related data returned. By following the relations, all related data can be reached. WinFS promotes sharing of data between applications by making the data types accessible to all applications, along with their schemas. When an application wants to use a WinFS type, it can use the schema to find the data structure and can use the information. So, an application has access to all data on the system even though the developer did not have to write parsers to recognize the different data formats. It can also use relationships and related data to create dynamic filters to present the information the application deals with. The WinFS API further abstracts the task of accessing data. All WinFS types are exposed as .NET objects with the properties of the object directly mapping to the properties of the data type. Also, by letting different applications that deal with the same data share the same WinFS data instance rather than storing the same data in different files, the hassles of synchronizing the different stores when the data change are removed. Thus WinFS can reduce redundancies.

Access to all the data in the system allows complex searches for data across all the data items managed by WinFS. In the example used above ("the phone numbers of all persons who live in Acapulco and each have more than 100 appearances in my photo collection and with whom I have had e-mail within last month"), WinFS can traverse the subject relationship of all the photos to find the contact items. Similarly, it can filter all emails in last month and access the communicated with relation to reach the contacts. The common contacts can then be figured out from the two sets of results and their phone number retrieved by accessing the suitable property of the contact items.

In addition to fully schematized data (like XML and relational data), WinFS supports semi-structured data (such as images, which have an unstructured bitstream plus structured metadata) as well as unstructured data (such as files) as well. It stores the unstructured components as files while storing the structured metadata in the structured store. Internally, WinFS uses a relational database to manage data. It does not limit the data to belonging to any particular data model. The WinFS runtime maps the schema to a relational modality, by defining the tables it will store the types in and the primary keys and foreign keys that would be required to represent the relationships. WinFS includes mappings for object and XML schemas by default. Mappings for other schemas must be specified. Object schemas are specified in XML; WinFS generates code to surface the schemas as .NET classes. ADO.NET can be used to directly specify the relational schema, though a mapping to the object schema must be provided to surface it as classes. Relationship traversals are performed as joins on these tables. WinFS also automatically creates indexes on these tables, to enable fast access to the information. Indexing speeds up joins significantly, and traversing relationships to retrieve related data is performed very fast. Indexes are also used during information search; searching and querying use the indexes to quickly complete the operations, much like desktop search systems.

Development

The development of WinFS is an extension to a feature that was initially planned in the early 1990s. Dubbed Object File System, it was supposed to be included as part of Cairo. OFS was supposed to have powerful data aggregation features, but the Cairo project was shelved, and with it OFS. However, later during the development of COM, a storage system, called Storage+, based on then-upcoming SQL Server 8.0, was planned, which was slated to offer similar aggregation features. This, too, never materialized, and a similar technology, Relational File System (RFS), was conceived to be launched with SQL Server 2000. However, SQL Server 2000 ended up being a minor upgrade to SQL Server 7.0 and RFS was not implemented.

The concept was not scrapped, and served as the base for WinFS. WinFS was initially planned for inclusion in Windows Vista, and build 4051 of Windows Vista, then called by its codename "Longhorn", given to developers at the Microsoft Professional Developers Conference in 2003, included WinFS, but it suffered from significant performance issues. In August 2004, Microsoft announced that WinFS would not ship with Windows Vista; it would instead be available as a downloadable update after Vista's release.

On August 29, 2005, Microsoft quietly made Beta 1 of WinFS available to MSDN subscribers. It worked on Windows XP, and required the .NET Framework to run. The WinFS API was included in the System.Storage namespace. The beta was refreshed on December 1, 2005 to be compatible with version 2.0 of the .NET Framework. WinFS Beta 2 was planned for some time later in 2006, and was supposed to include integration with Windows Desktop Search, so that search results include results from both regular files and WinFS stores, as well as allow access of WinFS data using ADO.NET.

On June 23, 2006, the WinFS team at Microsoft announced that WinFS would no longer be delivered as a separate product, and some components would be brought under the umbrella of other technologies. Many of the principle features Microsoft intended to provide with WinFS included a pane for metadata property editing, breadcrumb-based property navigation, filtering or stacking items over properties, incremental search, and saved searches; these features were incorporated in Windows Vista. Query composition, a feature of WinFS that allowed users to perform additional searches that reuse the results of a previous query, was later incorporated in Windows Vista.

Examples of uses of the technology are the object-relational mapping components into ADO.NET Entity Framework; support for unstructured data, adminless mode of operation, support for file system objects via the FILESTREAM data type, and hierarchical data  in SQL Server 2008, then codenamed Katmai, as well as integration with Win32 APIs and Windows Shell and support for traversal of hierarchies by traversing relationships into later releases of Microsoft SQL Server; and the synchronization components into Microsoft Sync Framework.

In 2013 Bill Gates cited WinFS as his greatest disappointment at Microsoft and that the idea of WinFS was ahead of its time, which will re-emerge.

Data storage

Architecture

WinFS uses a relational engine, which derives from SQL Server 2005, to provide the data-relations mechanism. WinFS stores are simply SQL Server database (.MDF) files with the FILESTREAM attribute set. These files are stored in the access-restricted folder named "System Volume Information" (placed in the volume root), in folders under the folder "WinFS" with names of GUIDs of these stores.

At the bottom of the WinFS stack lies WinFS Core, which interacts with the filesystem and provides file-access and -addressing capabilities. The relational engine leverages the WinFS core services to present a structured store and other services such as locking, which the WinFS runtime uses to implement the functionality. The WinFS runtime exposes services such as Synchronization and Rules that can be used to synchronize WinFS stores or perform certain actions on the occurrence of certain events.

WinFS runs as a service that runs three processes:

 WinFS.exe, which hosts relational datastore
 WinFSSearch.exe, which hosts the indexing and querying engine
 WinFPM.exe (WinFS File Promotion Manager), which interfaces with the underlying file-system

It allows programmatic access to its features via a set of .NET Framework APIs. These enable applications to define custom-made data types, define relationships among data, store and retrieve information, and allow advanced searches. The applications can then aggregate the data and present the aggregated data to the user.

Data store
WinFS stores data in relational stores, which are exposed as virtual locations called stores. A WinFS store is a common repository where any application can store data along with its metadata, relationships and schema. WinFS runtime can apply certain relationships itself; for example, if the values of the subject property of a picture and the name property of a contact are same, then WinFS can relate the contact with the picture. Relations can also be specified by other applications or the user.

WinFS provides unified storage, but stops short of defining the format that is to be stored in the data stores. Instead it supports writing data in application-specific formats. But applications must provide a schema that defines how the file format should be interpreted. For example, a schema could be added to allow WinFS to understand how to read and thus be able to search and analyze, (say) a PDF file. By using the schema, any application can read data from any other application, and this also allows different applications to write in each other's format by sharing the schema.

Multiple WinFS stores can be created on a single machine. This allows different classes of data to be kept segregated; for example, official documents and personal documents can be kept in different stores. WinFS, by default, provides only one store, named "DefaultStore". WinFS stores are exposed as shell objects, akin to Virtual folders, which dynamically generate a list of all items present in the store and present them in a folder view. The shell object also allows searching information in the datastore.

A data unit that has to be stored in a WinFS store is called a WinFS Item. A WinFS item, along with the core data item, also contains information on how the data item is related to other data. This Relationship is stored in terms of logical links. Links specify which other data items the current item is related with. Put in other words, links specify the relationship of the data with other data items. Links are physically stored using a link identifier, which specifies the name and intent of the relationship, such as type of or consists of. The link identifier is stored as an attribute of the data item. All the objects that have the same link ID are considered to be related. An XML schema, defining the structure of the data items that will be stored in WinFS, must be supplied to the WinFS runtime beforehand. In Beta 1 of WinFS, the schema assembly had to be added to the GAC before it could be used.

Data model
WinFS models data using the data items, along with their relationships, extensions and rules governing its usage. WinFS needs to understand the type and structure of the data items, so that the information stored in the data item can be made available to any application that requests it. This is done by the use of schemas. For every type of data item that is to be stored in WinFS, a corresponding schema needs to be provided to define the type, structure and associations of the data. These schemas are defined using XML.

Predefined WinFS schemas include schemas for documents, e-mail, appointments, tasks, media, audio, video, and also includes system schemas that include configuration, programs, and other system-related data. Custom schemas can be defined on a per-application basis, in situations where an application wants to store its data in WinFS, but not share the structure of that data with other applications, or they can be made available across the system.

Type system

The most important difference between a file system and WinFS is that WinFS knows the type of each data item that it stores. And the type specifies the properties of the data item. The WinFS type system is closely associated with the .NET framework's concept of classes and inheritance. A new type can be created by extending and nesting any predefined types.

WinFS provides four predefined base types – Items, Relationships, ScalarTypes and NestedTypes. An Item is the fundamental data object which can be stored, and a Relationship is the relation or link between two data items. Since all WinFS items must have a type, the type of item stored defines its properties. The properties of an Item may be a ScalarType, which defines the smallest unit of information a property can have, or a NestedType, which is a collection of more than one ScalarTypes and/or NestedTypes. All WinFS types are made available as .NET CLR classes.

Any object represented as a data unit, such as contact, image, video, document etc., can be stored in a WinFS store as a specialization of the Item type. By default, WinFS provides Item types for Files, Contact, Documents, Pictures, Audio, Video, Calendar, and Messages. The File Item can store any generic data, which is stored in file systems as files. But unless an advanced schema is provided for the file, by defining it to be a specialized Item, WinFS will not be able to access its data. Such a file Item can only support being related to other Items.

A developer can extend any of these types, or the base type Item, to provide a type for their custom data. The data contained in an Item is defined in terms of properties, or fields that hold the actual data. For example, an Item Contact may have a field Name that is a ScalarType, and one field Address, a NestedType, which is further composed of two ScalarTypes. To define this type, the base class Item is extended and the necessary fields are added to the class. A NestedType field can be defined as another class that contains the two ScalarType fields. Once the type is defined, a schema has to be defined, which denotes the primitive type of each field, for example, the Name field is a String, the Address field is a custom defined Address class, both the fields of which are Strings. Other primitive types that WinFS supports are Integer, Byte, Decimal, Float, Double, Boolean and DateTime, among others. The schema will also define which fields are mandatory and which are optional. The Contact Item defined in this way will be used to store information regarding the Contact, by populating the properties field and storing it. Only those fields marked as mandatory needs to be filled up during initial save. Other fields may be populated later by the user, or not populated at all. If more properties fields, such as last conversed date, need to be added, this type can be extended to accommodate them. Item types for other data can be defined similarly.

WinFS creates tables for all defined Items. All the fields defined for the Item form the columns of the table and all instances of the Item are stored as rows in the table for the respective Items. Whenever some field in the table refers to data in some other table, it is considered a relationship. The schema of the relationship specifies which tables are involved and what the kind and name of the relationship is. The WinFS runtime manages the relationship schemas. All Items are exposed as .NET CLR objects, with a uniform interface providing access to the data stored in the fields. Thus any application can retrieve object of any Item type and can use the data in the object, without being aware of the physical structure the data was stored in.

WinFS types are exposed as .NET classes, which can be instantiated as .NET objects. Data are stored in these type instances by setting their properties. Once done, they are persisted into the WinFS store. A WinFS store is accessed using an ItemContext class (see Data retrieval section for details). ItemContext allows transactional access to the WinFS store; i.e. all the operations since binding an ItemContext object to a store till it is closed either all succeed or are all rolled back. As changes are made to the data, they are not written to the disc; rather they are written to an in-memory log. Only when the connection is closed are the changes written to the disc in a batch. This helps to optimize disc I/O. The following code snippet, written in C#, creates a contact and stores it in a WinFS store.

 //Connect to the default WinFS store
 using(ItemContext ic = ItemContext.Open())
 {
     //Create the contact and set the data in appropriate properties
     ContactEAddress contact = new ContactEAddress() {
         Name = new PersonName() {                      // Name is a ComplexType
             Displayname = "Doe, John",
             FirstName = "John",
             LastName = "Doe"
         },
         TelephoneNumber = new TelephoneNumber() {     // Telephone number is a ComplexType
             Country = CountryCode.Antarctica,
             Areacode = 4567,
             Number = 9876543210
         },
         Age = 111                                     // Age is a SimpleType
    };

    //Add the object to the user's personal folder.
    //This relates the item with the Folder pseudo-type, for backward
    //compatibility, as this lets the item to be accessed in a folder
    //hierarchy for apps which are not WinFS native.
    Folder containingFolder = UserDataFolder.FindMyPersonalFolder();
    containingFolder.OutFolderMemberRelationship.AddItem(ic, contact);

    //Find a document and relate with the document. Searching begins by creating an
    //ItemSearcher object. Each WinFS type object contains a GetSearcher() method
    //that generates an ItemSearcher object which searches documents of that type.
    using (ItemSearcher searcher = Document.GetSearcher(ic))
    {
         Document d = searcher.Find(@"Title = 'Some Particular Document'");
         d.OutAuthoringRelationship.AddItem(ic, contact);
    }
    //Since only one document is to be found, the ItemContext.FindOne() method
    //could be used as well.

    //Find a picture and relate with it
    using (ItemSearcher searcher = Picture.GetSearcher(ic))
    {
         Picture p = searcher.Find(@"Occasion = 'Graduation' and Sequence = '3'");
         p.OutSubjectRelationship.AddItem(ic, contact);
    }

    //Persist to the store and close the reference to the store
    ic.Update();
 }

Relationships
A datum can be related to one more item, giving rise to a one-to-one relationship, or with more than one items, resulting in a one-to-many relationship. The related items, in turn, may be related to other data items as well, resulting in a network of relationships, which is called a many-to-many relationship. Creating a relationship between two Items creates another field in the data of the Items concerned which refer the row in the other Item's table where the related object is stored.

In WinFS, a Relationship is an instance of the base type Relationship, which is extended to signify a specialization of a relation. A Relationship is a mapping between two items, a Source and a Target. The source has an Outgoing Relationship, whereas the target gets an Incoming Relationship. WinFS provides three types of primitive relationships – Holding Relationship, Reference Relationship and Embedding Relationship. Any custom relationship between two data types are instances of these relationship types.

 Holding Relationships specify ownership and lifetime (which defines how long the relationship is valid) of the Target Item. For example, the Relationship between a folder and a file, and between an Employee and his Salary record, is a Holding Relationship – the latter is to be removed when the former is removed. A Target Item can be a part of more than one Holding Relationships. In such a case, it is to be removed when all the Source Items are removed.
 Reference Relationships provide linkage between two Items, but do not have any lifetime associated, i.e., each Item will continue to be stored even without the other.
 Embedding Relationships give order to the two Items that are linked by the Relationship, such as the Relationship between a Parent Item and a Child Item.

Relationships between two Items can either be set programmatically by the application creating the data, or the user can use the WinFS Item Browser to manually relate the Items. A WinFS item browser can also graphically display the items and how they are related, to enable the user to know how their data are organized.

Rules
WinFS includes Rules, which are executed when a certain condition is met. WinFS rules work on data and data relationships. For example, a rule can be created that states that whenever an Item is created which contains field "Name" and if the value of that field is some particular name, a relationship should be created that relates the Item with some other Item. WinFS rules can also access any external application. For example, a rule can be built which launches a Notify application whenever a mail is received from a particular contact. WinFS rules can also be used to add new properties fields to existing data Items.

WinFS rules are also exposed as .NET CLR objects. As such any rule can be used for any purpose. A rule can even be extended by inheriting from it to form a new rule that consists of the condition and action of the parent rule plus something more.

RAV
WinFS supports creating Rich Application Views (RAV) by aggregating different data in a virtual table format. Unlike database view, where each individual element can only be a scalar value, RAVs can have complex Items or even collections of Items. The actual data can be across multiple data types or instances and can even be retrieved by traversing relationships. RAVs are intrinsically paged (dividing the entire set of data into smaller pages containing disconnected subsets of the data) by the WinFS runtime. The page size is defined during creation of the view and the WinFS API exposes methods to iterate over the pages. RAVs also supports modification of the view according to different grouping parameters. Views can also be queried against.

Access control
Even though all data are shared, everything is not equally accessible. WinFS uses the Windows authentication system to provide two data protection mechanisms. First, there is share-level security that controls access to your WinFS share. Second, there is item level security that supports NT compatible security descriptors. The process accessing the item must have enough privileges to access it. Also in Vista there is the concept of "integrity level" for an application. Higher integrity data cannot be accessed by a lower integrity process.

Data retrieval

The primary mode of data retrieval from a WinFS store is querying the WinFS store according to some criteria, which returns an enumerable set of items matching the criteria. The criteria for the query is specified using the OPath query language. The returned data are made available as instances of the type schemas, conforming to the .NET object model. The data in them can be accessed by accessing the properties of individual objects.

Relations are also exposed as properties. Each WinFS Item has two properties, named IncomingRelationships and OutgoingRelationships, which provide access to the set of relationship instances the item participates in. The other item which participates in one relationship instance can be reached through the proper relationship instance.

The fact that the data can be accessed using its description, rather than location, can be used to provide end-user organizational capabilities without limiting to the hierarchical organization as used in file-systems. In a file system, each file or folder is contained in only one folder. But WinFS Items can participate in any number of holding relationships, that too with any other items. As such, end users are not limited to only file/folder organization. Rather, a contact can become a container for documents; a picture a container for contacts and so on. For legacy compatibility, WinFS includes a pseudo-type called Folder, which is present only to participate in holding relationships and emulate file/folder organization. Since any WinFS Item can be related with more than one Folder item, from an end user perspective, an item can reside in multiple folders without duplicating the actual data. Applications can also analyze the relationship graphs to present various filters. For example, an email application can analyze the related contacts and the relationships of the contacts with restaurant bills and dynamically generate filters like "Emails sent to people I had lunch with".

Searches
The WinFS API provides a class called the ItemContext class, which is bound to a WinFS store. The ItemContext object can be used to scope the search to the entire store or a subset of it. It also provides transactional access to the store. An object of this class can then spawn an ItemSearcher object which then takes the type (an object representing the type) of the item to be retrieved or the relationship and the OPath query string representing the criteria for the search. A set of all matches is returned, which can then be bound to a UI widget for displaying en masse or enumerating individually. The properties items can also be modified and then stored back to the data store to update the data. The ItemContext object is closed (which marks the end of association of the object with the store) when the queries are made or changes merged into the store.

Related items can also be accessed through the items. The IncomingRelationships and OutgoingRelationships properties give access to all the set of relationship instances, typed to the name of the relationship. These relationship objects expose the other item via a property. So, for example, if a picture is related to a picture, it can be accessed by traversing the relationship as:

ContactsCollection contacts = picture.OutgoingRelationships.Cast(typeof(Contact)).Value;
// This retrieves the collection of all outgoing relationships from a picture object
// and filters down the contacts reachable from them and retrieves its value.

// Or the relationship can be statically specified as
ContactsCollection contacts = picture.OutgoingRelationships.OutContactRelationship.Contact;

An OPath query string allows to express the parameters that will be queried for to be specified using Item properties, embedded Items as well as Relationships. It can specify a single search condition, such as "title = Something'", or a compound condition such as "title = 'Title 1' || title = 'Title 2' && author = 'Someone'". These boolean and relational operations can be specified using C# like &&, ||, =, != operators as well as their English-like equivalent like EQUAL, NOT EQUAL. SQL like operators such as LIKE, GROUP BY and ORDER BY are also supported, as are wildcard conditions. So, "title LIKE 'any*'" is a valid query string. These operators can be used to execute complex searches such as
using (ItemContext ic = ItemContext.Open())
{
    // Searching begins by creating a ItemSearcher object. The searcher is created from a
    // relationship instance because the contacts being searched for are in relation. The
    // first parameter defines the scope of the search. An ItemContext as the scope means
    // the entire store is to be searched. Scope can be limited to a set of Items which may
    // be in a holding relationship with the contacts. In that case, the set is passed as
    // the scope of the search.
    ItemSearcher searcher = OutContactRelationship.GetTargetSearcher(ic, typeof(Contact));
    ContactCollection contacts = searcher.FindAll("OutContactRelationship.Contact.Name LIKE 'A*'");
}
The above code snippet creates an ItemSearcher object that searches on the OutContactRelationship instance that relates pictures and contacts, in effect searching all pictures related with a contact. It then runs the query Name LIKE 'A*'" on all contacts reachable through OutContactRelationship, returning the list of "contacts whose names start with A and whose pictures I have". Similarly, more relationships could be taken into account to further narrow down the results. Further, a natural language query processor, which parses query in natural language and creates a well-formed OPath query string to search via proper relationships, can allow users to make searches such as "find the name of the wine I had with person X last month", provided financial management applications are using WinFS to store bills.

Different relations specify a different set of data. So when a search is made that encompasses multiple relations, the different sets of data are retrieved individually and a union of the different sets is computed. The resulting set contains only those data items that correspond to all the relations.

Notifications
WinFS includes better support for handling data that changes frequently. Using WinFS Notifications, applications choose to be notified of changes to selected data Items. WinFS will raise an ItemChangedEvent, using the .NET Event model, when a subscribed-to Item changes, and the event will be published to the applications.

Information Agent
WinFS includes an Information Agent feature for the management, retrieval, and storage of end-user notification rules and preferences for changes to items in the data store. Using Information Agent, it is possible to automatically define relations to new items based on events such as appointments, with an example being that appointments can be related to photos based on the dates the photos were taken, enabling queries for birthdays or holidays without needing to know the actual dates of such events ("find all photos taken on this birthday"). Other examples include automatically moving new items to specific folders based on a rule as determined by appointment times and dates the photos were taken ("when I import a photo taken during a business event, move it to the Business Events folder") or more complex possibilities. Information Agent can also forward notifications to other devices ("if I receive a high priority email from my boss, send a notification to my phone") and is similar to Rules and Alerts functionality of Microsoft Outlook.

Data sharing
WinFS allows easy sharing of data between applications, and among multiple WinFS stores, which may reside on different computers, by copying to and from them. A WinFS item can also be copied to a non-WinFS file system, but unless that data item is put back into the WinFS store, it will not support the advanced services provided by WinFS.

The WinFS API also provides some support for sharing with non-WinFS applications. WinFS exposes a shell object to access WinFS stores. This object maps WinFS items to a virtual folder hierarchy, and can be accessed by any application. Virtual folders can automatically share new content referenced by the query with users (a virtual folder for "all vacation photos" can automatically share new items returned by this query with users). WinFS data can also be manually shared using network shares, by sharing the legacy shell object. Non-WinFS file formats can be stored in WinFS stores, using the File Item, provided by WinFS. Importers can be written, to convert specific file formats to WinFS Item types.

In addition, WinFS provides services to automatically synchronize items in two or more WinFS stores, subject to some predefined condition, such as "share only photos" or "share photos that have an associated contact X". The stores may be on different computers. Synchronization is done in a peer-to-peer fashion; there is no central authority. A synchronization can be either manual or automatic or scheduled. During synchronization, WinFS finds the new and modified Items, and updates accordingly. If two or more changes conflict, WinFS can either resort to automatic resolution based on predefined rules, or defer the synchronization for manual resolution. WinFS also updates the schemas, if required.

Application support

Shell namespace
WinFS Beta 1 includes a shell namespace extension, which surfaces WinFS stores as top level objects in My Computer view. Files can be copied into and out of the stores, as well as applications can be directly used to save there. Even folders such as My Documents can be redirected to the stores. WinFS uses Importer plug-ins to analyze the files as they were being imported to the store and create proper WinFS schemas and objects, and when taking the objects out, re-pack them into files. If importers for certain files are not installed, they are stored as generic File types.

Microsoft Rave
Microsoft Rave is an application that shipped with WinFS Beta 1. It allows synchronization of two or more WinFS stores, and supports synchronization in full mesh mode as well as the central hub topology. While synchronizing, Microsoft Rave will determine the changes made to each store since the last sync, and update accordingly. When applying the changes, it also detects if there is any conflict, i.e., the same data has been changed on both stores since the last synchronization. It will either log the conflicting data for later resolution or have it resolved immediately.  Microsoft Rave uses peer-to-peer technology to communicate and transfer data.

StoreSpy

With WinFS Beta 1, Microsoft included an unsupported application called StoreSpy, which allowed one to browse WinFS stores by presenting a hierarchical view of WinFS Items. It automatically generated virtual folders based on access permissions, date and other metadata, and presented them in a hierarchical tree view, akin to what traditional folders are presented in. The application generated tabs for different Item types. StoreSpy allowed viewing Items, Relationships, MultiSet, Nested Elements, Extensions and other types in the store along with its full metadata. It also presented a search interface to perform manual searches, and save them as virtual folders. The application also presented a graphical view of WinFS Rules. However, it did not allow editing of Items or their properties, though it was slated for inclusion in a future release. But the WinFS project was cut back before it could materialize.

Type Browser
WinFS also includes another application, named WinFS Type Browser, which can be used to browse the WinFS types, as well as visualize the hierarchical relationship between WinFS types. A WinFS type, both built-in types as well as custom schemas, can be visualized along with all the properties and methods that it supports. It also shows the types that it derives from as well as other types that extend the type schema. However, while it was included with WinFS, it was released as an unsupported tool.

OPather
WinFS Beta 1 also includes an unsupported application, named OPather. It presents a graphical interface for writing Opath queries. It can be used by selecting target object type and specifying the parameters of the query. It also includes Intellisense-like parameter completion feature. It can then be used to perform visualization tasks like binding results of a query to a DataGrid control, create views of the data in WinFS itself, or just extract the query string.

Project "Orange"
Microsoft launched a project to build a data visualization application for WinFS. It was codenamed "Project Orange" and was supposedly built using Windows Presentation Foundation. It was supposed to provide exploration of Items stored in WinFS stores, and data relationships were supposed to be a prominent part of the navigation model. It was supposed to let people allow organization of the WinFS stores graphically as well – productizing many of the concepts shown in the IWish Concept Video WMV File. However, since the WinFS project went dark, the status of this project is unknown.

See also
 Desktop organizer
 GNOME Storage – a storage management system for the GNOME desktop
 NEPOMUK
 ReFS
 Relational database management system (RDBMS)

References

External links
 WinFS Blog
 WinFS at the Microsoft Developer Network (Internet Archive cache)
 Channel 9 Videos
 WinFS Newsgroup
 WinFS Beta 1 Preview
 WinFS area on NetFXGuide.com (Internet Archive cache)

Microsoft application programming interfaces
Windows disk file systems
Windows administration
Semantic file systems
Articles with example C Sharp code

WinFS


Miguel Rodríguez Fandeo (Caracas, Venezuela, 4 de abril de 1953) es un político y economista venezolano. En la administración pública venezolana, ocupó los cargos de Ministro de Estado, Jefe de CORDIPLAN (Oficina de Coordinación y Planificación, antecesora del Ministerio de Planificación) y presidente del Banco Central de Venezuela durante el segundo gobierno de Carlos Andrés Pérez.

Biografía
En 1977, se gradúa de Economía e Ingeniería, estudió las dos carreras a la vez, de la Universidad Central de Venezuela. Beneficiado por el programa de becas Fundayacucho, creado bajo el primer gobierno de Carlos Andrés Pérez, viaja a Boston a aprender inglés. Posteriormente realiza un doctorado en la Universidad de Harvard, y luego elige realizar una maestría en la Universidad Yale, al haber sido aceptado también en las universidades de Columbia, Berkeley y Harvard. Durante su estadía en Yale, trabaja como asistente de James Tobin, Premio en Ciencias Económicas en memoria de Alfred Nobel 1981; su cercanía a esta figura lo convierten en ese entonces en un partidario del keynesianismo.

En 1985 regresa a Venezuela a trabajar en el IESA; ese año publica en El Diario de Caracas un artículo titulado "Mitos y realidades del endeudamiento externo de Venezuela", que llama la atención del expresidente Carlos Andrés Pérez, quien lo contacta, siendo la primera vez que se reúnen.

En 1987, regresa a Washington al ser seleccionado por el Instituto Peterson dentro de un grupo de trescientos economistas, y pasa un año y medio en dicha institución. Durante su estadía en Estados Unidos, se reúne con frecuencia con Pérez, quien le ofrece el cargo de Ministro de Planificación (Cordiplan) luego de llegar por segunda vez a la presidencia al triunfar en las elecciones de 1988.

Rodríguez, junto con Pedro Tinoco, en febrero de 1989 fueron identificados como los responsables de El Gran Viraje, un programa de ajustes económicos propuestos y emprendidos por Carlos Andrés para acabar con la corrupción, que también buscaba refinanciar la deuda externa y prevenir que el país entrara en quiebra que recibió con un déficit fiscal de 6.500 millones de dólares de deuda vencida en cartas de crédito, por importaciones subsidiadas a un cambio de 4.30 luego de eliminar el programa de control de cambio RECADI establecido desde 1983 durante el gobierno de Luis Herrera Campíns. Se estableció una renegociación de la Deuda externa con los bancos que Venezuela venía pagando 4,500 millones de dólares anuales. Estos ajustes no fueron bien recibidos por la sociedad venezolana en general y han sido considerados por la opinión pública como uno de los detonantes de El Caracazo, una revuelta popular ocurrida a finales de febrero de 1989. Este programa de ajustes tuvo gran éxito en el plano económico, al lograr bajar la inflación y promover el crecimiento que llegó al 9% interanual del PIB en apenas tres años. En febrero de 1990 logran reestructurar la deuda a 15 años con 7 años de gracia, reducen el pago anual de 4,500 a unos 1,200 millones de dólares y logra un préstamo de 1,200 millones para el proyecto de Macagua II.

Luego del primer intento de golpe de Estado de Venezuela de 1992 liderado por Hugo Chávez, Pérez es presionado por su propio partido y por el partido opositor Copei para que cambie su gabinete, al que responsabilizan de la crisis política e institucional existente, como condición para formar un gobierno de coalición. Rodríguez es entonces desplazado de Cordiplan por Ricardo Hausmann, y es enviado a la presidencia del Banco Central de Venezuela, donde desplaza a su vez a Pedro Tinoco. Con estos cambios, Pérez espera estabilizar su gobierno pero a la vez seguir promoviendo el programa de ajustes económicos, ya que Hausmann y Rodríguez poseen ideas similares. No obstante, estos cambios no son considerados suficientes por los partidos citados y Rodríguez es removido del BCV menos de un mes después de haber sido designado su presidente.

Rodríguez se postuló como candidato en las elecciones presidenciales de 1998, apoyado por el Movimiento Apertura, luego de que Claudio Fermín se distanciara de Pérez y fuera entonces descartado; no obstante, Rodríguez solamente obtuvo el 0.30% de los votos. Desde entonces, Miguel Rodríguez ha seguido una carrera académica en el IESA y en la Universidad Santa María, llegando a ser decano del departamento de Ciencias Económicas de esta última entre 2002 y 2004.

Véase también

 Ministerio del Poder Popular de Planificación

Referencias

Bibliografía

Enlaces externos
 Video año 2021: MIGUEL RODRÍGUEZ: POLÍTICOS CORRUPTOS IMPIDIERON LOS AJUSTES DE CAP | TESTIMONIOS
 Video año 2021: MIGUEL RODRÍGUEZ: EMPRESARIOS PARÁSITOS FUERON ENEMIGOS DE LA REFORMA | TESTIMONIOS | SEGUNDA PARTE
  Video año 2021: MIGUEL RODRÍGUEZ:VENEZUELA PUDO SER LA ECONOMÍA MÁS SÓLIDA DEL MUNDO | TESTIMONIOS | TERCERA PARTE
Caraqueños
Ministros de Planificación de Venezuela
Economistas de Venezuela
Ingenieros de Venezuela
Políticos de la Venezuela contemporánea
Alumnado de la Universidad Central de Venezuela
Alumnado de la Universidad Yale
Alumnado de la Universidad de Harvard
Ministros durante la presidencia de Carlos Andrés Pérez
Presidentes del Banco Central de Venezuela
Candidatos presidenciales de Venezuela

Miguel Rodríguez Fandeo


Grifo Alto es un distrito del cantón de Puriscal, en la provincia de San José, de Costa Rica.

Historia
Grifo Alto ha existido desde la creación de los distritos originales de Puriscal en la década de 1910. En el pasado poseía un área de 23,85 km² más tras un ordenamiento territorial en la década de 1990 su superficie aumentó a la cifra actual.

Geografía

Demografía

Localidades
 Poblados: Cacao, Cuesta Mora, Grifo Bajo, Poró, Pueblo Nuevo, Salitrillo.

Cultura
En el poblado de Salitrillos se realiza una romería el día 2 de agosto, donde proviene gente de diferentes distritos, en conmemoración a la Virgen de los Ángeles.

Transporte

Carreteras
Al distrito lo atraviesan las siguientes rutas nacionales de carretera:
 Ruta nacional 137

Referencias

Distritos del cantón de Puriscal

Grifo Alto (Costa Rica)


Juniperus procera er tegund barrtrés af einisætt. Upprunninn frá fjöllum Afríku og Arabíuskaga.

Tilvísanir

Einisætt

Juniperus procera


An Bothriochloa wrightii in uska species han Liliopsida nga syahan ginhulagway ni Eduard Hackel, ngan ginhatag han pagkayana nga asya nga ngaran ni Johannes Jan Theodoor Henrard. An Bothriochloa wrightii in nahilalakip ha genus nga Bothriochloa, ngan familia nga Poaceae. Waray hini subspecies nga nakalista.

Mga kasarigan

Mga sumpay ha gawas

Bothriochloa

Bothriochloa wrightii


La fontaine ballainvilliers est une fontaine située dans le centre-ville de Riom en Auvergne, place de la Fédération, devant la basilique Saint-Amable.

Historique
La fontaine a été construite en 1764 à l'initiative de l'intendant de la généralité de Riom, Bernard de Ballainvilliers.

L'inscription côté sud, en haut, de la fontaine permet de savoir qu'elle a été construite par Philibert Chaper, fontainier à Clermont-Ferrand, sous la direction de l'architecte Claude-François Legay (1728-1803) et sous le contrôle du consul Vissac :
Chaper aquilex struxit
Legay architecto direxit
Vissac ædilis inspexit
3,000 libris constitit.

Le père mariste Jean Bonnet a dénombré 62 fontaines en 1796 dans une étude sur les Fontaines riomoises.

Protection
La fontaine Ballainvilliers a été inscrite au titre des monuments historiques en 1927.

Présentation

Notes et références

Annexes

Bibliographie

Articles connexes
 Liste des monuments historiques de Riom
 Fontaines protégées aux monuments historiques en Auvergne-Rhône-Alpes

Liens externes

 Art et histoire en Auvergne-Rhône-Alpes : Les fontaines, Riom
 Petit patrimoine : Fontaine Ballainvilliers à Riom (63)

Ballainvilliers
Monument historique inscrit en 1927

Fontaine Ballainvilliers


Chinolonele reprezintă un grup de medicamente chimioterapice sintetice cu spectru larg și cu efect bactericid. Cele mai importante chinolone utilizate în terapie sunt fluorochinolonele, care prezintă un atom de fluor în poziția 6 a nucleului chinolonic. Sunt antibiotice foarte eficiente și prezintă unele avantaje farmacocinetice (precum biodisponibilitatea orală mare și volumul de distribuție larg) și o activitate antimicrobiană caracterizată printr-un spectru larg de activitate. Totuși, prezintă un mare risc în ceea ce privește reacțiile adverse (tendinite, rupturi de tendoane, neuropatii) și a dezvoltării bacteriilor de rezistență la fluorochinolone.

Fluorochinolonele sunt active atât pe bacteriile Gram-pozitive, cât și pe cele Gram-negative. Exemple de astfel de medicamente sunt: ciprofloxacina, levofloxacina și moxifloxacina.

Începând cu anul 2019, autorizația de punere pe piață pentru cele din generația 1 a fost retrasă din Uniunea Europeană, iar pentru celelalte antibiotice chinolonice rămase în uz s-au introdus restricții stricte de utilizare.

Istoric
Deși nu este un derivat adevărat de chinolonă, ci un analog cu atom de azot (naftiridină), acidul nalidixic este considerat ca fiind prima chinolonă sinsteizată. Aceasta a fost introdusă încă din anul 1962 pentru tratamentul infecțiilor de tract urinar. Acidul nalidixic a fost descoperit de către George Lesher și colegii săi în timpul încercării de a sintetiza derivați de clorochină. Se consideră astfel că acidul nalidixic este predecesorul tuturor chinolonelor, inclusiv al fluorochinolonelor. De atunci, mai mult de 10.000 de analogi structurali au fost sintetizați, dar doar câțiva se află în terapie.

În anii 1970 au fost introduși în terapie alți compuși din prima generație, precum: acidul pipemidic și acidul oxolinic, ca forme îmbunătățite ale acidului nalidixic.  Acești agenți au fost utilizați în tratamentul multor infecții bacteriene, chiar și comune și necomplicate. Ulterior, au fost dezvoltate încă trei generații de fluorochinolone.

În iulie 2008, FDA a emis o atenționare black-box pentru utilizarea fluorochinolonelor, datorită reacțiilor adverse de afectare a tendoanelor. În 2016, FDA a atenționat cu privire la alte efecte adverse periculoase asociate uzului oral sau injectabil, precum: neuropatia periferică și afectarea sistemului nervos central, cu recomandarea de restrângere a domeniului terapeutic. Ulterior, și Agenția Europeană a Medicamentului a propus retragerea autorizațiilor de punere pe piață compușii din generația 1 și restricții stricte de utilizare pentru ceilalți reprezentanți.

Utilizări medicale
Fluorochinolonele sunt utilizate pentru infecții localizate la nivelul aparatului genito-urinar, fiind utilizate adesea în tratamentul infecțiilor nosocomiale localizate în cateterele urinare. În alte cazuri, sunt prescrise doar în cazuri de multi-rezistență a agenților patogeni sau când terapia cu alte antibiotice nu a avut efect. Totuși, sunt și utilizate ca tratament de primă linie în cazul unor infecții acute de pielonefrită sau prostatită bacteriană.

Efecte adverse
Efectele adverse produse de chinolone variază de la ușoare la severe. Sunt bine tolerate, totuși reacțiile adverse produce, chiar dacă sunt rare, pot fi foarte severe. Tratamentul cu chinolone și fluorochinolone este asociat cu un risc (de aproximativ 0,08 - 0,20%) de afectare a tendoanelor, cu aparția tendinitelor și a rupturilor de tendoane. Afectarea la nivelul sistemului nervos central este caracterizată de insomnie, agitație și rar convulsii și psihoză. Alte efecte adverse posibile sunt: rupturi ale aortei, dezvoltarea unei infecții cu Clostridium difficile (colită pseudomembranoasă), specifică tuturor antibioticelor cu spectru larg, și exacerbarea simptomelor din miastenia gravis.

Interacțiuni
Chinolonele și fluorochinolonele nu trebuie să fie asociate cu alte produse ce conțin cationi multivalenți, precum sunt antiacidele care conțin ioni de aluminiu sau magneziu, și de asemenea nici cu produse ce conțin calciu, fier sau zinc, întrucât acestea reduc invariabil absorbția orală de chimioterapic. Alte medicamente care prezintă interacțiuni cu fluorochinolonele sunt: sucralfatul, probenecidul, cimetidina, teofilina, warfarina, antiviralele, fenitoina, ciclosporina, rifampina, pirazinamida și cicloserina.

Mecanism de acțiune

Chinolonele își manifestă activitatea antibacteriană prin inhibarea despiralizării și duplicării ADN-ului bacterian. Mai exact, acestea inhibă enzimele denumite girază, topoizomerază I și IV, care sunt implicate în replicarea ADN-ului, ceea ce duce la moartea celulei bacteriene.

Celulele eucariote nu conțin ADN-girază și topoizomerază IV, totuși există dezbateri în ceea ce privește acțiunea fluorochinolonelor asupra ADN-ului sănătos al celulelor umane. S-a demonstrat că unii compuși din această clasă inhibă sinteza de ADN mitocondrial.

Farmacologie
Farmacoforul sau unitatea structurală chimică ce conferă activitatea chinolonelor este nucleul chinolinic-carboxilic. Introducerea diferiților substituenți pe acest nucleu a dus la obținerea unei varietății mari de compuși chinolonici, inclusiv cei care prezintă un atom de fluor în poziția 6. Totuși, acesta nu este necesar pentru activitatea antibacteriană, ci conferă lipofilie.

Din punct de vedere farmacocinetic, prezintă o biodisponibilitate orală bună și un volum de distribuție larg. Astfel, compușii mai noi se pretează uzului oral în favoarea administrării intravenoase, minimizând necesitatea spitalizării, și prezintă un timp de înjumătățire mai prelungit, ceea ce permite administrarea unei doze unice zilnice.

Generații

Generația 1
Sunt derivați de chinolonă:
 Acid oxolinic
 Rosoxacină
 Flumechină
Sunt analogi, dar nu chinolone:
 Acid nalidixic, este o naftiridină
 Acid pipemidic, este o pirido-pirimidină
 Cinoxacină, este o cinolină

Generația a 2-a
 Ciprofloxacină
 Fleroxacină
 Lomefloxacină
 Nadifloxacină
 Norfloxacină
 Ofloxacină
 Pefloxacină
 Rufloxacină
 Analogi structurali: enoxacină

Generația a 3-a
 Balofloxacină
 Grepafloxacină
 Levofloxacină
 Pazufloxacină
 Sparfloxacină
 Temafloxacină
Analogi structurali: tosufloxacină

Generația a 4-a
 Clinafloxacină
 Gatifloxacină
 Moxifloxacină
 Sitafloxacină
 Prulifloxacină
 Besifloxacină
 Delafloxacină
 Analogi structurali: gemifloxacină; trovafloxacină și alatrofloxacină (promedicament)

Note

Chinolonă


Cansu Dere (d. 14 Ekim 1980, Ankara), Türk oyuncu, sunucu ve eski mankendir.

Hayatı
14 Ekim 1980 tarihinde Ankara'da doğdu. Anne tarafından İzmir, İstanbul ve Selanik kökenli, baba tarafından ise Bulgaristan kökenlidir. İlk ve orta öğrenimini İzmir'de tamamladı. 2000 yılında Kanal D'nin düzenlediği Miss Turkey yarışmasının 3. güzeli oldu ve profesyonel mankenlik yapmaya başladı. İstanbul Üniversitesi Edebiyat Fakültesi Arkeoloji Bölümünü yarıda bırakarak mankenlik mesleğine ağırlık vermiştir. Hakan Yıldırım, Cengiz Abazoğlu, Ümit Ünal, Evrim Timur, Arzu Kaprol, Bahar Korçan ve Dilek Hanif gibi moda tasarımcılarının defilelerinde yer almıştır. İTKİB'in tüm yurt dışı organizasyonlarında Türkiye'yi temsil eden Cansu Dere, 2002 ve 2003 yılları arasında Paris'te çeşitli defilelere katılmış ve birçok önemli fotoğrafçıyla çalışmalar gerçekleştirmiştir.

Kariyeri
1998 yılında Arçelik reklamında yer alan Dere, 2000 yılında televizyon dünyasına girmiştir. İlk sunuculuk deneyimini Kanal D'deki Çocuk ve Müzik programıyla yaşamıştır. Ardından 2004 yılında Show TV'de yayımlanan Türkiye'nin Yıldızları adlı yarışmayı sunmuştur. NTV'de yayımlanan Life Style Moda programında sunuculuğun yanı sıra editörlük de yapmıştır. 2005 yılında yine NTV'de N Moda programının sunuculuğunu üstlenmiştir.

2004 yılında Hilal Saral'ın yönettiği ve Amerikan sitcom'u Sex and the City dizisinden uyarlanan Metro Palas adlı diziyle oyunculuğa adım atmıştır. Daha sonra Türkan Derya'nın yönettiği Alacakaranlık adlı dizide "Irmak Bozoğlu" karakterini canlandırmıştır. 2005 yılında Zeynep Günay Tan'ın yönettiği Güz Yangını dizisindeki "Ceylan" rolüyle dikkatleri çeken Dere, bu dönemde Çağan Irmak'ın TV filmi formatında çektiği Kabuslar Evi filminde köylü "Esma" karakterini oynamıştır. 2006 yılında Cem Yılmaz ve Zafer Önen ile beraber Opet reklamında yer almıştır. 2006-2008 yılları arasında yayımlanan Sıla isimli dizide Mehmet Akif Alakurt ile birlikte başrol oynayarak popülerliğini arttırmıştır. "Sıla" karakteri ile yer aldığı dizi ile hayran kazanmaya başlamıştır. 2007 yılında Kenan İmirzalıoğlu ile birlikte rol aldığı Son Osmanlı Yandım Ali adlı, "Defne" karakterini oynadığı dönem filmi 1 milyonun üstünde seyirci tarafından izlenmiştir. 2009 yılında, senaryosunu Onur Ünlü'nün yazdığı ve Taner Elhan'ın yönettiği Acı Aşk adlı filmde rol almıştır. Halit Ergenç, Songül Öden ve Ezgi Asaroğlu ile başrolleri paylaştığı filmde "Oya" adlı bir fotoğrafçıyı oynamıştır.

2009 yılında döneme damgasını vuran Ezel dizisindeki "Eyşan" rolü ile daha da ünlenmiştir. Yine 2009 yılında Totally Spies:Casus Kızlar Her Şey Nasıl Başladı? filminde Alex ve Mandy karakterlerini seslendirmiştir. 2010 yılında Yahşi Batı filminde "Mary Lou" karakterini oynamıştır.

2011 yılında Serdar Akar'ın yönettiği, 3. sinema filmi Behzat Ç. Seni Kalbime Gömdüm'''ü çekmiştir. Filmde "Songül" isimli bir polisi canlandırmıştır. 2012 yılında El Yazısı filminde yine başrolü üstlenmiştir. Dere bu kez küçük bir kasabada eczacılık yapan "Zeynep" rolünü üstlenmiştir.Muhteşem Yüzyıl dizisinde İranlı "Firuze" karakteri ile yer almıştır. 2016 yılının Ekim ayında Star TV'de yayımlanmaya başlayan Anne dizisinde "Zeynep" karakterini canlandırmıştır. Daha sonra 2018 yılında yayımlanan ve Haluk Bilginer ile başrolü paylaştığı, internet platformu puhutv'de yayımlanan Şahsiyet dizisinde "Nevra Elmas" karakterini canlandırmıştır. 2019 yılında ise Tolga Sarıtaş ile başrolünü paylaştığı, FOX'ta yayımlanan Ferhat ile Şirin'' dizisinde "Banu Karalı" karakterini canlandırmıştır fakat proje fazla uzun sürmeyip 6. bölümünde final yapmıştır. 2020 yılında ise Caner Cindoruk ve Melis Sezen ile başrolü paylaştığı, Kanal D'de yayımlanan İngiliz yapımı Doctor Foster dizisinin Türkiye uyarlaması olan Sadakatsiz adlı dizide "Asya Yılmaz" karakterine hayat verdi. Dizi, 25 Mayıs 2022 tarihinde 60. bölümü ile final yaparak sona erdi.

Filmografisi

Ödülleri ve adaylıkları

Kaynakça

Dış bağlantılar

 IMDb sayfası
 SinemaTürk sayfası

1980 doğumlular
Ankara doğumlu kadın oyuncular
21. yüzyılda Türk kadın oyuncular
Türk kadın sinema oyuncuları
Türk kadın dizi oyuncuları
Türk kadın modeller
Türk televizyon sunucuları
İstanbul Üniversitesi Edebiyat Fakültesinde öğrenim görenler
Yaşayan insanlar
Bulgaristan Türkleri

Cansu Dere


Die Bathygadidae sind eine Fischfamilie aus der Ordnung der Dorschartigen (Gadiformes). Die Fische leben weltweit in Tiefen von 200 bis 2700 Metern, meist zwischen 400 und 1500 Metern, in tropischen und subtropischen Meeren, nicht aber in Regionen über dem Kontinentalsockel im östlichen Pazifik.

Merkmale
Bathygadidae werden 25 bis 63,5 cm lang. Sie besitzen zwei Rückenflossen, von denen die erste kurz und die zweite lang ist. Die zweite Rückenflosse beginnt kurz hinter der ersten. Ihre Flossenstrahlen sind länger als die der Afterflosse. Die erste Rückenflosse hat einen schlanken, stachligen zweiten Flossenstrahl. Das Maul ist breit, endständig und leicht protraktil (vorstülpbar). Die Schnauze ist abgerundet. Beide Kiefer sind mit kleinen bis winzigen Zähnen besetzt. Die Kinnbartel ist lang, kurz oder kann fehlen. Die Anzahl der Branchiostegalstrahlen liegt bei sieben. Die Kiemenreusenstrahlen des ersten Kiemenbogens sind schlank, lang und zahlreich. Der Darm ist einfach N- oder S-förmig gefaltet.

Der Mageninhalt der Bathygadidae besteht meist aus Ruderfußkrebsen, Krill und Garnelen, so dass angenommen wird, dass sie sich, im Unterschied zu den Grenadierfischen, vor allem von pelagischer Beute ernähren.

Systematik
Die Bathygadidae wurden lange Zeit als Unterfamilie den Grenadierfischen (Macrouridae) zugeordnet. 2009 wurden sie von Adela Roa-Varón und Guillermo Ortí in den Familienrang erhoben. Die Bathygadidae sind die Schwestergruppe der Macruronidae.

Gattungen und Arten

Es gibt zwei Gattungen mit insgesamt 26 Arten:

 Bathygadus
 Bathygadus antrodes (Jordan & Starks, 1904)
 Bathygadus bowersi (Gilbert, 1905)
 Bathygadus cottoides Günther, 1878
 Bathygadus dubiosus Weber, 1913
 Bathygadus entomelas Gilbert & Hubbs, 1920
 Bathygadus favosus  Goode & Bean, 1886
 Bathygadus furvescens Alcock, 1894
 Bathygadus garretti Gilbert & Hubbs, 1916
 Bathygadus macrops Goode & Bean, 1885
 Bathygadus melanobranchus Vaillant, 1888
 Bathygadus nipponicus (Jordan & Gilbert, 1904)
 Bathygadus spongiceps Gilbert & Hubbs, 1920
 Bathygadus sulcatus (Smith & Radcliffe, 1912)
 Gadomus
 Gadomus aoteanus McCann & McKnight, 1980
 Gadomus arcuatus (Goode & Bean, 1886)
 Gadomus capensis (Gilchrist & von Bonde, 1924)
 Gadomus colletti Jordan & Gilbert, 1904
 Gadomus denticulatus Gilbert & Hubbs, 1920
 Gadomus dispar (Vaillant, 1888)
 Gadomus filamentosus (Smith & Radcliffe, 1912)
 Gadomus introniger Gilbert & Hubbs, 1920
 Gadomus longifilis (Goode & Bean, 1885)
 Gadomus magnifilis Gilbert & Hubbs, 1920
 Gadomus melanopterus Gilbert, 1905
 Gadomus multifilis (Günther, 1887)
 Gadomus pepperi Iwamoto & Williams, 1999

Nutzung
Von den Bathygadidae kommt nur die nordatlantische Art Bathygadus macrops in so großer Anzahl vor, dass sie von wirtschaftlichem Interesse ist und befischt wird. Daneben wird auch der in derselben Region, aber tiefer lebende B. melanobranchus in geringem Maße gefangen.

Literatur
 Joseph S. Nelson, Terry C. Grande, Mark V. H. Wilson: Fishes of the World. Wiley, Hoboken, New Jersey, 2016, ISBN 978-1118342336
 Cohen, D.M.; Inada.T.; Iwamoto, T.; Scialabba, N. FAO species catalogue. Vol. 10: Gadiform fishes of the world (Order Gadiformes). An annotated and illustrated catalogue of cods, hakes, grenadiers and other gadiform fishes known to date. FAO Fisheries Synopsis. No. 125, Vol. 10. Rome, FAO. 1990. 442 p. online

Einzelnachweise

Weblinks

Dorschartige
Gadiformes
Tiefseefisch

Bathygadidae


Clotilde es una ópera en dos actos con música de Carlo Coccia y libreto en italiano de Gaetano Rossi. Se estrenó el 8 de junio de 1815 en el Teatro San Benedetto de Venecia, Italia.

Referencias

Enlaces externos

Óperas de Carlo Coccia
Óperas en italiano
Óperas de 1815
Óperas estrenadas en Venecia

Clotilde (ópera)


هدوء نسبي مسلسل عربي ضخم الإنتاج عرض على قناة روتانا خليجية وقناة نسمة خلال رمضان 1430 هـ - 2009 بطولة عابد فهد ونادين سلامة ونيللي كريم ونخبة من نجوم الفن العربي.إنتاج روتانا خليجية وإيبلا الدولية للإنتاج السينمائي والتلفزيوني وهو من إخراج شوقي الماجري.

مراجع

أعمال عن الغزو الأمريكي للعراق
مسلسلات تلفزيونية سورية
مسلسلات تلفزيونية مصرية بدأ عرضها في 2009

هدوء نسبي (مسلسل)


An Cyrtococcum humbertianum in uska species han Liliopsida nga ginhulagway ni Aimée Antoinette Camus. An Cyrtococcum humbertianum in nahilalakip ha genus nga Cyrtococcum, ngan familia nga Poaceae.

Mabibilngan ini ha Madagascar. Waray hini subspecies nga nakalista.

Mga kasarigan

Cyrtococcum

Cyrtococcum humbertianum


Ruj (rujevina, lat. Rhus), rod listopadnih penjačica, grmova i drveća iz porodice Anacardiaceae. Latinsko ime roda dolazi iz grčke riječi rhodo (crven), zbog boje plodova, a koristio ga je još Teofrast.

Listovi mirisavog ruja, Rhus coriaria, koriste se za aromatiziranje duhana,a neke zemlje ovu biljku uzgajaju zbog proizvodnje tanina.

Rodu pripada 54 priznate vrste, a u Hrvatskoj su poznate vrste Mirisavi ruj i runjavi ili kiseli ruj.

Biljka otrovni ruj pripada rodu toxicodendron (Toxicodendron vernix), otrovna je na dodir, nekada je bila klasificirana ovom rodu, pa joj je ostalo ime ruj.

 Rhus allophyloides Standl.
 Rhus amherstensis W.W.Sm.
 Rhus andrieuxii Engl.
 Rhus aromatica Aiton
 Rhus arsenei F.A.Barkley
 Rhus × ashei (Small) Greene
 Rhus bahamensis G.Don
 Rhus barclayi (Hemsl.) Standl.
 Rhus caudata Lauterb.
 Rhus chinensis Mill.
 Rhus chondroloma Standl.
 Rhus choriophylla Wooton & Standl.
 Rhus ciliolata Turcz.
 Rhus copallinum L.
 Rhus coriaria L.
 Rhus dhuna Buch.-Ham. ex Hook.f.
 Rhus duckerae F.A.Barkley
 Rhus galeottii Standl.
 Rhus glabra L.
 Rhus hartmanii F.A.Barkley
 Rhus hypoleuca Champ. ex Benth.
 Rhus integrifolia (Nutt.) Benth. & Hook.f. ex W.H.Brewer & S.Watson
 Rhus jaliscana Standl.
 Rhus kearneyi F.A.Barkley
 Rhus lamprocarpa Merr. & L.M.Perry
 Rhus lanceolata (A.Gray) Britton
 Rhus lenticellosa Lauterb.
 Rhus lentii Kellogg
 Rhus linguata Slis
 Rhus michauxii Sarg.
 Rhus microphylla Engelm.
 Rhus muelleri Standl. & F.A.Barkley
 Rhus nelsonii F.A.Barkley
 Rhus oaxacana Loes.
 Rhus ovata S.Watson
 Rhus pachyrrhachis Hemsl.
 Rhus palmeri Rose
 Rhus potaninii Maxim.
 Rhus × pulvinata Greene
 Rhus punjabensis J.L.Stewart ex Brandis
 Rhus rubifolia Turcz.
 Rhus sandwicensis A.Gray
 Rhus schiedeana Schltdl.
 Rhus schmidelioides Schltdl.
 Rhus standleyi F.A.Barkley
 Rhus taishanensis S.B.Liang
 Rhus taitensis Guill.
 Rhus tamaulipana B.L.Turner
 Rhus teniana Hand.-Mazz.
 Rhus tepetate Standl. & F.A.Barkley
 Rhus terebinthifolia Schltdl. & Cham.
 Rhus trilobata Nutt.
 Rhus typhina L.
 Rhus vestita Loes.
 Rhus virens Lindh. ex A.Gray
 Rhus wilsonii Hemsl.

Vanjske poveznice

Izvori

Rujevke

Ruj


Die Western Australia International 1999 im Badminton fanden Ende September 1999 statt.

Sieger und Platzierte

Weblinks
 http://tournamentsoftware.com/sport/tournament.aspx?id=3CF05511-89DB-450B-A838-B9AE61B92DC2

1999
Badminton 1999

Western Australia International 1999