text:
//---------------------------------------------------------------------------
//
// <copyright file="PropertyChangedEventManager.cs" company="Microsoft">
//    Copyright (C) Microsoft Corporation.  All rights reserved.
// </copyright>
//
// Description: Manager for the PropertyChanged event in the "weak event listener"
//              pattern.  See WeakEventTable.cs for an overview.
//
//---------------------------------------------------------------------------

using System;
using System.Collections;       // ICollection
using System.Collections.Specialized;   // HybridDictionary
using System.ComponentModel;    // INotifyPropertyChanged
using System.Diagnostics;       // Debug
using System.Reflection;        // MethodInfo
using System.Windows;           // WeakEventManager
using MS.Internal.WindowsBase;  // SR

namespace System.ComponentModel
{
    /// <summary>
    /// Manager for the INotifyPropertyChanged.PropertyChanged event.
    /// </summary>
    public class PropertyChangedEventManager : WeakEventManager
    {
        #region Constructors

        //
        //  Constructors
        //

        private PropertyChangedEventManager()
        {
        }

        #endregion Constructors

        #region Public Methods

        //
        //  Public Methods
        //

        /// <summary>
        /// Add a listener to the given source's event.
        /// </summary>
        public static void AddListener(INotifyPropertyChanged source, IWeakEventListener listener, string propertyName)
        {
            if (source == null)
                throw new ArgumentNullException("source");
            if (listener == null)
                throw new ArgumentNullException("listener");

            CurrentManager.PrivateAddListener(source, listener, propertyName);
        }

        /// <summary>
        /// Remove a listener to the given source's event.
        /// </summary>
        public static void RemoveListener(INotifyPropertyChanged source, IWeakEventListener listener, string propertyName)
        {
            /* for app-compat, allow RemoveListener(null, x) - it's a no-op (see Dev10 796788)
            if (source == null)
                throw new ArgumentNullException("source");
            */
            if (listener == null)
                throw new ArgumentNullException("listener");

            CurrentManager.PrivateRemoveListener(source, listener, propertyName);
        }

        /// <summary>
        /// Add a handler for the given source's event.
        /// </summary>
        public static void AddHandler(INotifyPropertyChanged source, EventHandler<PropertyChangedEventArgs> handler, string propertyName)
        {
            if (handler == null)
                throw new ArgumentNullException("handler");

            CurrentManager.PrivateAddHandler(source, handler, propertyName);
        }

        /// <summary>
        /// Remove a handler for the given source's event.
        /// </summary>
        public static void RemoveHandler(INotifyPropertyChanged source, EventHandler<PropertyChangedEventArgs> handler, string propertyName)
        {
            if (handler == null)
                throw new ArgumentNullException("handler");

            CurrentManager.PrivateRemoveHandler(source, handler, propertyName);
        }

        #endregion Public Methods

        #region Protected Methods

        //
        //  Protected Methods
        //

        /// <summary>
        /// Return a new list to hold listeners to the event.
        /// </summary>
        protected override ListenerList NewListenerList()
        {
            return new ListenerList<PropertyChangedEventArgs>();
        }

        /// <summary>
        /// Listen to the given source for the event.
        /// </summary>
        protected override void StartListening(object source)
        {
            INotifyPropertyChanged typedSource = (INotifyPropertyChanged)source;
            typedSource.PropertyChanged += new PropertyChangedEventHandler(OnPropertyChanged);
        }

        /// <summary>
        /// Stop listening to the given source for the event.
        /// </summary>
        protected override void StopListening(object source)
        {
            INotifyPropertyChanged typedSource = (INotifyPropertyChanged)source;
            typedSource.PropertyChanged -= new PropertyChangedEventHandler(OnPropertyChanged);
        }

        /// <summary>
        /// Remove dead entries from the data for the given source.   Returns true if
        /// some entries were actually removed.
        /// </summary>
        protected override bool Purge(object source, object data, bool purgeAll)
        {
            bool foundDirt = false;

            if (!purgeAll)
            {
                HybridDictionary dict = (HybridDictionary)data;

                // copy the keys into a separate array, so that later on
                // we can change the dictionary while iterating over the keys
                ICollection ic = dict.Keys;
                String[] keys = new String[ic.Count];
                ic.CopyTo(keys, 0);

                for (int i=keys.Length-1; i>=0; --i)
                {
                    if (keys[i] == AllListenersKey)
                        continue;       // ignore the special entry for now

                    // for each key, remove dead entries in its list
                    bool removeList = purgeAll || source == null;

                    if (!removeList)
                    {
                        ListenerList list = (ListenerList)dict[keys[i]];

                        if (ListenerList.PrepareForWriting(ref list))
                            dict[keys[i]] = list;

                        if (list.Purge())
                            foundDirt = true;

                        removeList = (list.IsEmpty);
                    }

                    // if there are no more entries, remove the key
                    if (removeList)
                    {
                        dict.Remove(keys[i]);
                    }
                }

                if (dict.Count == 0)
                {
                    // if there are no more listeners at all, remove the entry from
                    // the main table, and prepare to stop listening
                    purgeAll = true;
                    if (source != null)     // source may have been GC'd
                    {
                        this.Remove(source);
                    }
                }
                else if (foundDirt)
                {
                    // if any entries were purged, invalidate the special entry
                    dict.Remove(AllListenersKey);
                    _proposedAllListenersList = null;
                }
            }

            if (purgeAll)
            {
                // stop listening.  List cleanup is handled by Purge()
                if (source != null) // source may have been GC'd
                {
                    StopListening(source);
                }
                foundDirt = true;
            }

            return foundDirt;
        }

        #endregion Protected Methods

        #region Private Properties

        //
        //  Private Properties
        //

        // get the event manager for the current thread
        private static PropertyChangedEventManager CurrentManager
        {
            get
            {
                Type managerType = typeof(PropertyChangedEventManager);
                PropertyChangedEventManager manager = (PropertyChangedEventManager)GetCurrentManager(managerType);

                // at first use, create and register a new manager
                if (manager == null)
                {
                    manager = new PropertyChangedEventManager();
                    SetCurrentManager(managerType, manager);
                }

                return manager;
            }
        }

        #endregion Private Properties

        #region Private Methods

        //
        //  Private Methods
        //

        // PropertyChanged is a special case - we superimpose per-property granularity
        // on top of this event, by keeping separate lists of listeners for
        // each property.

        // Add a listener to the named property (empty means "any property")
        private void PrivateAddListener(INotifyPropertyChanged source, IWeakEventListener listener, string propertyName)
        {
            Debug.Assert(listener != null && source != null && propertyName != null,
                "Listener, source, and propertyName of event cannot be null");

            AddListener(source, propertyName, listener, null);
        }

        // Remove a listener to the named property (empty means "any property")
        private void PrivateRemoveListener(INotifyPropertyChanged source, IWeakEventListener listener, string propertyName)
        {
            Debug.Assert(listener != null && source != null && propertyName != null,
                "Listener, source, and propertyName of event cannot be null");

            RemoveListener(source, propertyName, listener, null);
        }

        // Add a handler for the named property (empty means "any property")
        private void PrivateAddHandler(INotifyPropertyChanged source, EventHandler<PropertyChangedEventArgs> handler, string propertyName)
        {
            AddListener(source, propertyName, null, handler);
        }

        // Remove a handler for the named property (empty means "any property")
        private void PrivateRemoveHandler(INotifyPropertyChanged source, EventHandler<PropertyChangedEventArgs> handler, string propertyName)
        {
            RemoveListener(source, propertyName, null, handler);
        }

        private void AddListener(INotifyPropertyChanged source, string propertyName, IWeakEventListener listener, EventHandler<PropertyChangedEventArgs> handler)
        {
            using (WriteLock)
            {
                HybridDictionary dict = (HybridDictionary)this[source];

                if (dict == null)
                {
                    // no entry in the hashtable - add a new one
                    dict = new HybridDictionary(true /* case insensitive */);

                    this[source] = dict;

                    // listen for the desired events
                    StartListening(source);
                }

                ListenerList list = (ListenerList)dict[propertyName];

                if (list == null)
                {
                    // no entry in the dictionary - add a new one
                    list = new ListenerList<PropertyChangedEventArgs>();

                    dict[propertyName] = list;
                }

                // make sure list is ready for writing
                if (ListenerList.PrepareForWriting(ref list))
                {
                    dict[propertyName] = list;
                }

                // add a listener to the list
                if (handler != null)
                {
                    ListenerList<PropertyChangedEventArgs> hlist = (ListenerList<PropertyChangedEventArgs>)list;
                    hlist.AddHandler(handler);
                }
                else
                {
                    list.Add(listener);
                }

                dict.Remove(AllListenersKey);   // invalidate list of all listeners
                _proposedAllListenersList = null;

                // schedule a cleanup pass
                ScheduleCleanup();
            }
        }

        private void RemoveListener(INotifyPropertyChanged source, string propertyName, IWeakEventListener listener, EventHandler<PropertyChangedEventArgs> handler)
        {
            using (WriteLock)
            {
                HybridDictionary dict = (HybridDictionary)this[source];

                if (dict != null)
                {
                    ListenerList list = (ListenerList)dict[propertyName];

                    if (list != null)
                    {
                        // make sure list is ready for writing
                        if (ListenerList.PrepareForWriting(ref list))
                        {
                            dict[propertyName] = list;
                        }

                        // remove a listener from the list
                        if (handler != null)
                        {
                            ListenerList<PropertyChangedEventArgs> hlist = (ListenerList<PropertyChangedEventArgs>)list;
                            hlist.RemoveHandler(handler);
                        }
                        else
                        {
                            list.Remove(listener);
                        }

                        // when the last listener goes away, remove the list
                        if (list.IsEmpty)
                        {
                            dict.Remove(propertyName);
                        }
                    }

                    if (dict.Count == 0)
                    {
                        StopListening(source);

                        Remove(source);
                    }

                    dict.Remove(AllListenersKey);   // invalidate list of all listeners
                    _proposedAllListenersList = null;
                }
            }
        }

        // event handler for PropertyChanged event
        private void OnPropertyChanged(object sender, PropertyChangedEventArgs args)
        {
            ListenerList list;
            string propertyName = args.PropertyName;

            // get the list of listeners
            using (ReadLock)
            {
                // look up the list of listeners
                HybridDictionary dict = (HybridDictionary)this[sender];

                if (dict == null)
                {
                    // this can happen when the last listener stops listening, but the
                    // source raises the event on another thread after the dictionary
                    // has been removed (bug 1235351)
                    list = ListenerList.Empty;
                }
                else if (!String.IsNullOrEmpty(propertyName))
                {
                    // source has changed a particular property.  Notify targets
                    // who are listening either for this property or for all properties.
                    ListenerList<PropertyChangedEventArgs> listeners = (ListenerList<PropertyChangedEventArgs>)dict[propertyName];
                    ListenerList<PropertyChangedEventArgs> genericListeners = (ListenerList<PropertyChangedEventArgs>)dict[String.Empty];

                    if (genericListeners == null)
                    {
                        if (listeners != null)
                        {
                            list = listeners;           // only specific listeners
                        }
                        else
                        {
                            list = ListenerList.Empty;  // no listeners at all
                        }
                    }
                    else
                    {
                        if (listeners != null)
                        {
                            // there are both specific and generic listeners -
                            // combine the two lists.
                            list = new ListenerList<PropertyChangedEventArgs>(listeners.Count + genericListeners.Count);
                            for (int i=0, n=listeners.Count; i<n; ++i)
                                list.Add(listeners.GetListener(i));
                            for (int i=0, n=genericListeners.Count; i<n; ++i)
                                list.Add(genericListeners.GetListener(i));
                        }
                        else
                        {
                            list = genericListeners;    // only generic listeners
                        }
                    }
                }
                else
                {
                    // source has changed all properties.  Notify all targets.
                    // Use previously calculated combined list, if available.
                    list = (ListenerList)dict[AllListenersKey];

                    if (list == null)
                    {
                        // make one pass to compute the size of the combined list.
                        // This avoids expensive reallocations.
                        int size = 0;
                        foreach (DictionaryEntry de in dict)
                        {
                            Debug.Assert((String)de.Key != AllListenersKey, "special key should not appear");
                            size += ((ListenerList)de.Value).Count;
                        }

                        // create the combined list
                        list = new ListenerList<PropertyChangedEventArgs>(size);

                        // fill in the combined list
                        foreach (DictionaryEntry de in dict)
                        {
                            ListenerList listeners = ((ListenerList)de.Value);
                            for (int i=0, n=listeners.Count;  i<n;  ++i)
                            {
                                list.Add(listeners.GetListener(i));
                            }
                        }

                        // save the result for future use (see below)
                        _proposedAllListenersList = list;
                    }
                }

                // mark the list "in use", even outside the read lock,
                // so that any writers will know not to modify it (they'll
                // modify a clone intead).
                list.BeginUse();
            }

            // deliver the event, being sure to undo the effect of BeginUse().
            try
            {
                DeliverEventToList(sender, args, list);
            }
            finally
            {
                list.EndUse();
            }

            // if we calculated an AllListeners list, we should now try to store
            // it in the dictionary so it can be used in the future.  This must be
            // done under a WriteLock - which is why we didn't do it immediately.
            if (_proposedAllListenersList == list)
            {
                using (WriteLock)
                {
                    // test again, in case another thread changed _proposedAllListersList.
                    if (_proposedAllListenersList == list)
                    {
                        HybridDictionary dict = (HybridDictionary)this[sender];
                        if (dict != null)
                        {
                            dict[AllListenersKey] = list;
                        }

                        _proposedAllListenersList = null;
                    }

                    // Another thread could have changed _proposedAllListersList
                    // since we set it (earlier in this method), either
                    // because it calculated a new one while handling a PropertyChanged(""),
                    // or because it added/removed/purged a listener.
                    // In that case, we will simply abandon our proposed list and we'll
                    // have to compute it again the next time.  But that only happens
                    // if there's thread contention.  It's not worth doing something
                    // more complicated just for that case.
                }
            }
        }

        #endregion Private Methods

        ListenerList _proposedAllListenersList;
        static readonly string AllListenersKey = "<All Listeners>"; // not a legal property name
    }
}

redpajama_set_name: RedPajamaGithub


Episode 83 - The brothers learn of the massacre of their sons & allies, and summon Draupadi to break the news. As usual, all she wants is revenge. Thus the Pandavas go off on one final mission to avenge the death of their sons. They track down Ashwatthaman and find him hanging out with Vyasa and Narada. As soon as they set eyes on each other, the boy Brahmin sets off his Brahmashira weapon, which is 100s of times more powerful than the Brahmastra, and sounds a lot like a hydrogen bomb-- "All living things are destroyed and no rains fall for 12 years."
The Rishis step in and order Arjun to put his guns away, but Ashwatthaman cannot retract this weapon once it is unleashed, so instead, he turns it loose on the wombs of the Pandava women, making them sterile and killing their one remaining heir-- Uttara's unborn son Parikshit.
Fortunately, Krishna revives the kid, but there shall be no more Pandava offspring after this.
To help explain how Ashwatthaman was able to pull off this massacre single-handedly, Krishna tells a few stories about Shiva, and just how temperamental and dangerous he can be. In fact, Shiva really comes off as more of a force of nature than a Saddhu living in the hills.
My guess is, that if we understood the physics of Time, we might realize that Shiva stands in for one of the main functions of time, which is change. The other aspects of time are novelty (Brahma), and the moment of Now, which I believe is represented by Vishnu.
I was just rewatching Sita Sings the Blues, it occurred to me that Ravana didn't do anything wrong according to the Dharma of a kshatriya or at least not much. He had great spiritual power and he kidnapped a woman of his caste to marry her. He didn't force himself on her. It's true that he should have fought rama for her, but he must surely have felt justified if the kind of reasoning used for justification in the Mahabharata is applied to his case. He wants her and can't think of a way to get her without trickery. It makes me wonder about the moral message of the Ramayana even more than the Mahabharata. Any thoughts?
I'm so deep in the rules of morality in the Mahabharata that I can tell you what makes Ravana a bad guy-- on two counts. The first is not that he stole Rama's wife, but that he failed to first vanquish Rama. We saw that in the abduction of Draudpadi-- Jayadratha was criticized only for failing to first kill the Pandavas. Apparently it was otherwise OK to steal her.
But we know that sometimes the rules are meant to be broken, and that for a good cause, one may break the rules and still be considered righteous. The distinction is very subtle-- it's OK to break the rules if you are good, but not OK if you are bad. And Ravana is bad. That's just a fact. Therefore he has no excuse for breaking the rules.
Thanks for staying with me so long!


Contrary to the public perception that all childless women are generally unhappy with their condition, the study shows that assumptions of older, childless women being dissatisfied with their status do not apply to the largest group of childless older women.
"Our research leads to the notion that for some women, childbearing might not have even been part of an equation," says Joyce Abma, Ph.D., lead author of the study. "Public impressions that all older childless women are eager to start a family and 'beat the odds' of increasing infertility stand to be refined." Public health campaigns to encourage women to begin childbearing before age-related issues begin are, perhaps, not relevant for a larger subgroup of women than previously realized.
It seems like every statistical study released these days somehow vindicates the childfree - but this one has particularly notable dimensions. Perhaps the only problem is making sure people find out about this. I'm afraid the Hewlett-type assumption that every woman must want a baby sill continue to prevail.


Software is composed of modules, perhaps developed by the same person or team or (more probably) developed by several teams who may or may not coordinate their work. Each module's users know its interface but not its implementation. The modules are connected (through their interfaces) to each other in a specific configuration, the software's architecture. All of these can be changing: a module's implementation, a module's interface, and how it is connected to other modules. How does software evolve?
Figure 1. Evolution, represented by red arrows.
A module's implementation can change or be replaced.
A module's interface can change or be replaced.
The module's connections to other modules can change.
Two or more of the above can happen at once.
A module's interface and implementation may evolve together or independently.
The implementation may be refactored or otherwise changed to meet developmental quality goals, without changing the module interface.
The interface may evolve in a way that the module implementer foresaw and prepared for, or that fortuitously is met by the existing implementation, so that the implementation does not change.
Both the interface and the implementation may evolve.
A system or subsystem's interface, module configuration, and its component modules may evolve together or independently.
The (sub)system's interface may evolve in a way that doesn't require the implementation to change.
The configuration in which its modules are connected together may evolve in a way that doesn't affect the subsystem interface.
A module may be replaced by another with the same interface.
A module may be replaced by another with a different interface.
A module's interface and/or implementation may evolve as descxribed above.
Some combination of these, or all of them, may occur together.
Changes to a module's implementation that do not affect its interface have no effect on the modules connected to it or the subsystem in which it forms a part. Changes that affect a module's interface propagate outwards, affecting other modules and/or the configuration in which they are connected.
The typical case involves a change to the module's interface and the evolution of its implementation to match; or a change to the (sub)system's interface and some combination of module replacement, rearrangement of modules in a new configuration, and changes to a module's interface and implementation.
Figure 2. An increment in the evolution of a (sub)system.
only without Rearrangement of components .
Figure 2 illustrates the possible paths from one development state of a system, subsystem, or module, to the next increment in its evolution.


The authors of the guidebook know their subject. Mark Andrew Calderwood is a second generation pegmatite geologist-mineralogist, who started exploring and mining Western Australian pegmatites with his father in the 1970s. He has personally mined more than a few of the described localities and currently manages a tantalite deposit in Africa. Benjamin Alexander Grguric is a professional mineralogist and a life-long fossicker. Mark Ivan Jacobson is also a geologist-mineralogist with a specialty in pegmatites since the 1970s. These three have combined their experiences, providing the reader with the results of their searching and finding pegmatites in Western Australia.


text:
Дятлево () — деревня в Алнашском районе Удмуртии, входит в Ромашкинское сельское поселение. Находится в 3 км к северо-востоку от села Алнаши и в 84 км к юго-западу от Ижевска.

Население на 1 января 2008 года — 184 человека.

История
По итогам десятой ревизии 1859 года в 52 дворах казённой деревни Дятлево (Ключ Омча) Елабужского уезда Вятской губернии проживало 143 жителя мужского пола и 163 женского, работали мельница и почтовая станция. К 1897 году в деревне проживало 502 человека. На 1914 год жители деревни Дятлева (Сизьгурт, Ключ-Омча) числились прихожанами Свято-Троицкой церкви села Алнаши.

В 1921 году, в связи с образование Вотской автономной области, деревня передана в состав Можгинского уезда. В 1924 году при укрупнении сельсоветов она вошла в состав Алнашского сельсовета Алнашской волости. В 1929 году упраздняется уездно-волостное административное деление и деревня причислена к Алнашскому району.

В феврале 1930 года в деревне организована сельскохозяйственная артель (колхоз) «Выль Удмурт» (Новый Удмурт). Согласно уставу: «…В члены артели могли вступить все трудящиеся, достигшие 16-летнего возраста (за исключением кулаков и граждан, лишенных избирательных прав)…». В 1932 году в колхозе состояло 39 хозяйств с общим количеством населения 107 человек, в том числе трудоспособных 88 человека, имелись птицеводческая товарная ферма, ветряная мельница и крупорушка. В 1935 году в колхозе имелись 3 фермы: овцеводческая товарная ферма, птицеводческая товарная ферма и кролиководческая товарная ферма.

В ноябре 1950 года решением общего собрания колхозников деревня вошла в состав объединенного колхоза «имени Пушкина», с центральной усадьбой в деревне Старая Шудья. В 1958 году колхозы «имени Пушкина» и «имени Крупской», объединены в колхоз «Россия», который в 1963 году был переименован в колхоз «Правда», центральная усадьба колхоза по прежнему размещалась в деревне Старая Шудья.

В 1991 году Алнашский сельсовет разделён на Алнашский и Ромашкинский сельсоветы, деревня передана в состав нового сельсовета. 16 ноября 2004 года Ромашкинский сельсовет был преобразован в муниципальное образование «Ромашкинское» и наделён статусом сельского поселения.

Социальная инфраструктура
 Дятлевская начальная школа — 11 учеников в 2008 году
 Дятлевский детский сад

Примечания

Населённые пункты Алнашского района

redpajama_set_name: RedPajamaWikipedia


text:
Q: Story identification - Desert planet with "Makers" I recall reading a sci-fi novel that was set on a desert planet where the main character was part of the technologically backwards inhabitants of the planet, however there were some (at least two, but possibly more) technologically advanced people that also lived on the planet as well, and were rulers who were treated by the people as gods or wizards or something like that.
The main character is a male non-tech-savvy inhabitant of the planet who starts living under the jurisdiction of one of these rulers, but during the story travels to the domain of a different one. He might have been a refugee, but I am not 100% sure on that part. He did travel with a group of other people, and he was the leader of the group as I recall. He also had a female love interest in the group with him.
When they arrived at the place where the other ruler lived, he saw that the landscaping included water features, and was impressed by that. He met with the other ruler, who told him about something called "Makers", which the ruler had created and which would inhabit his body and help it to fight sicknesses, and to repair itself. The word "Makers" seems to have been the rulers way of dumbing down the concept so that it was able to be understood by the main character.
I am not sure if the "Makers" were genetically engineered biological creatures, or if they were nanobots of some sort, but whatever they were, they did infect him, and after a slight initial sickness he then felt their effects positively because he healed quicker from injuries.
Other than that, I can remember that there was a sandstorm at one point in the story during which they all had to hide in tents and wait it out. The book must have been published at least 20 years ago, since as I recall I read it after finding it in a library discard sale some time around 2010.

A: The book is Hammerfall by C. J. Cherryh. The book was published in 2002 so it does match your time frame.

I recall very little of the book, but luckily as straycat points out in a comment there is a description of it on Wikipedia. The "Makers" are nanobots called nanoceles. The protagonist is Marak and his wife/love interest is Norit. The "other ruler" is called Luz and she does infect Marak's party with the nanoceles. After Marak has recovered from a fever Norit tells him:

"We are mad," Norit said, having captured half a breath, "we are mad because we have these creatures in our blood. And they have them inside, too. Luz has them, very, very tiny, so tiny no eye can see; but they move through our blood and through our ears and our eyes and they make us have the visions. They make the fever. They heal us.

I don't recall water features in Luz's palace, but as I recall there is a large ornamental pool at the edge of the city.
The story is set on a desert planet and there are sandstorms a plenty so there are scenes where Marak is pinned down by a sandstorm. I have the book (though I have no memory of when I read it) so I can check other plot points if you want me to.

redpajama_set_name: RedPajamaStackExchange


text:
Poster Print of Portrait of the Grand Duchess Maria Pavlovna, c1822(?). Artist: George Dawe
> Daughter
> Dawe
> George Dawe
> Grand Duchess
> Grand Duchess Maria Pavlovna Of Russia
> Imperial
> Maria Pavlovna Of Russia
> The Art Collector
Portrait of the Grand Duchess Maria Pavlovna, c1822(?). Artist: George Dawe
Portrait of the Grand Duchess Maria Pavlovna, c1822(?). Grand Duchess Maria Pavlovna of Russia (1786-1859) was the third daughter of Tsar Paul I of Russia and Maria Feodorovna. In 1804 she married Charles Frederick, Hereditary Grand Duke of Saxe-Weimar-Eisenach. Their second daughter, Augusta, was the first Empress of Germany, as the consort of Kaiser Wilhelm I. Detail. Found in the collection of The Hermitage, St Petersburg.
Portrait of the Grand Duchess Maria Pavlovna, c1822(?). Grand Duchess Maria Pavlovna of Russia (1786-1859) was the third daughter of Tsar Paul I of Russia and Maria Feodorovna. In 1804 she married Charles Frederick, Hereditary Grand Duke of Saxe-Weimar-Eisenach. Their second daughter, Augusta, was the first Empress of Germany, as the consort of Kaiser Wilhelm I. Detail. Found in the collection of The Hermitage, St Petersburg
© The Art Collector
Daughter , Dawe , George Dawe , Grand Duchess , Grand Duchess Maria Pavlovna Of Russia , Imperial , Maria Pavlovna Of Russia , The Art Collector
© Copyright Heritage Images - All Rights Reserved 2021
Orders made through www.heritage-print.com are fulfilled by Media Storehouse®

redpajama_set_name: RedPajamaCommonCrawl


text:
EntertainmentTelevision
In Eerie, self-fulfilling prophecy, The Ultimate Warrior gave his own eulogy hours before his death
I'll be honest. I'm sad. I was a kindergartner, but I remember Wrestlemania VI. It's the favorite of my brother and me. We'd rent the VHS in the years that followed and re-enact every move of The Rockers, Earthquake, Rick Martel, and especially The Ultimate Warrior and Hulk Hogan.
Warrior, aka Jim Hellwig, died late Tuesday night in Arizona at age 54. Less than 24 hours before he suddenly collapsed, he appeared on WWE Monday Night Raw to celebrate his induction into the WWE Hall of Fame the previous day.
Nobody knew that this would be the last time we saw The Ultimate Warrior. I was so excited that he was "back" in the business after so many years of anger and bitter separation from the company. I never thought the WWE was fair to him. They tried to erase his legacy — more so they tried to discredit it with an at-best inaccurate, at-worst horribly libelous DVD in 2005.
This was it, though! He's back. He has years to reconnect with the WWE Universe. We'd see him every few months and be reminded of the old glory. He'd put over young stars. He'd shake the ropes. It was an enormously positive feeling.
Then it was gone.
Instead of giving a preview of things to come, Warrior was giving his own eulogy. And it was a hell of a eulogy:
Speak to me, Warriors! As I thought about what I was going to say this evening, it's been hard for me to find the words. [Puts on mask.] Well then, you shut up Warrior, and let me do the talking.
No WWE talent becomes a legend on their own. Every man's heart one day beats its final beat. His lungs breathe a final breath. And if what that man did in his life makes the blood pulse through the body of others, and makes them bleed deeper, and something larger than life, then his essence, his spirit, will be immortalized. By the storytellers, by the loyalty, by the memory of those who honor him and make the running the man did live forever.
You, you, you, you, you, you are the legend-makers of Ultimate Warrior. In the back, I see many potential legends, some of them with warrior spirits. And you will do the same for them. You will decide if they lived with the passion and intensity. So much so that you will tell your stories and you will make them legends, as well. I am Ultimate Warrior. You are the Ultimate Warrior fans. And the spirit of Ultimate Warrior will run forever!
Rest in peace, Warrior.
deathThe Ultimate Warriorwarriorwwe
John Guilfoil is the editor-in-chief of Blast: Boston's Online Magazine and the Blast Magazine Network. He can be reached at [email protected]. Tweet @johnguilfoil.
johnguilfoil April 9, 2014
I call on @WWE to make a new #UltimateWarrior DVD — an accurate one this time, please. RIP. http://t.co/wTvJ8G3IM2
Eric Bowden April 9, 2014
Eric Bowden liked this on Facebook.
Colin Sheehan April 9, 2014
Colin Sheehan liked this on Facebook.
Al Pacelli April 9, 2014
Al Pacelli liked this on Facebook.
Dulce April 21, 2014
Truly a legend. He will b sourly missed. Rest in Peace Ultimate Warrior.


Join us for our first of three Women's Nights this semester! Tuesday, October 4th meet at the Newman Center at 7:45pm to walk over to the FOCUS Missionaries' house.
The topic for this session is Identity and the Feminine Geninus. This is a great opportunity to talk about the things we don't normally discuss on a college campus. We hope you can join us!


Maltego comes in two flavors, a community edition and a commercial version. The community edition is great if you don't want to cough up the money, but it does limit your effectiveness. Having been on both sides I can whole heartedly say the commercial edition is well worth the price you pay!
Being free, the Community Edition is the version of choice for this tutorial. So be sure to grab a copy and install before continuing. Installation is straight forward, so we won't waste time going over the process.
Let's start out by learning our away around the interface that is clearly based on the Office Ribbon design. Please note we won't be going over every feature but just enough to familiarize users with the application.
Across the top we have the Main Navigation Bar. We are currently under the Investigate Tab, which is where most of our work will be done. Here you have the ability to edit and manipulate items on your clipboard, set the level of results per transform and set zoom levels.
Under the Manage Tab we can manage and import transforms as well as entities. You can also create and manage your very own transforms in this area.
We can start out by selecting the New Graph symbol at the top left hand corner of the page to begin a graph or use the keyboard shortcut CTRL + T.
On the left side you will now see a new Menu. This is the Palette Toolbar. The Palette Toolbar is where you will select an entity to move to the main clipboard. In order to select an entity, simply highlight the item of your choice and drag it to an open area in the New Graph in the main window. You have a choice to select anything from a domain name or IP block to a person, place or phrase.
In this example our target will be the Cyber Security Czar of the United States, Howard Schmidt. So click and drag the Person entity from the Personal Section of the Palette and place it in your New Graph. In order to input new information or edit existing information for any entity on the graph, simply double-click on the icon and start typing.
Once you have input the entity properties select OK. At this point you have the ability to run a transform on your entity. But what is a transform? Simply put, a transform is a way of querying information on a particular entity (more on this later).
By right-clicking on the entity you have the ability to select a transform to discover existing information or possible links to your entity. Maltego will use API's search engines and various websites to attain information regarding your target. As you can see, you have the ability to search for your target's email address, phone number as well as any links that the target has on different websites using various methods and resources.
In this example we will select Run Transform> Email addresses from Person> and then use the 'All in this set' option to search for email addresses via Public PGP server, Search engines and common free email providers such as Hotmail and Gmail. Also notice the icons that are just to the right of our search options. The blue spheres that you see, if clicked, will take you to a brief descriptions page describing the selected transform and what it does. The hazy square to the left of the blue sphere is a handy shortcut to the transform manager.
Results will start to appear immediately, but a listing of all email addresses may take a couple minutes depending on the speed of your system and the network connection. In the meantime, let's point out another important difference between the Community and Commercial Editions of Maltego.
As you can see here the Maltego Client requests are sent out via the client over HTTP for the CE edition and HTTPS for the commercial edition.
We have now gone from just a name to a list of possible email addresses. But how do we know these email addresses are valid or even connected to the individual in question? Maltego figures this out by taking the responses from the search engine and assigns it a weight based on relevance. For example, when matching an individual to an email address, the weight would correspond to how closely the found email address matches the initial name. Another way to quickly identify which results have the most weight is to simply highlight them and check their weight under the Properties Window (more on this later). You will also notice that since you have run the initial search, your other Property Windows have been filled with useful information.
The Overview Window gives you a quick glance at your transform results via color coded circles. Here we only have one brown circle for the originating entity for the name that we typed and several green circles for the child entities which are email addresses in this case. If you zoom out on the overview you will find a legend in the lower right-hand corner of the Overview Window that will allow you to see which color maps to which circle.
The Transform Output Windows display the number of results per search. As you can see here we just ran 3 transforms, all of which were searching for email addresses, but the process used 3 different search methods.
The Detail View and the Properties View presents a more specific approach and understanding to the information that is currently on your main graph window. By highlighting an entity on the main graph like we have done here, you can now see the outgoing links from that entity in the Detail View. This really helps when you need a compressed view instead of having to scroll all around on the main diagram to look at information. The Property View allows you to check the weight and as well as the number of links coming into and out of an entity.
Now that you have your results let's examine them further by weight. As you can see the email address 'howard at schmidt dot org' has a corresponding weight of 100 points. I'm sure there is more than one 'Howard Schmidt' in the world, so even though we got a perfect score, we're still not sure this is the object of our investigation. Let's examine this a bit further and drill down on this email address. We can do this by copying this email entity to a new graph. In Maltego it definitely helps to create a new graph to keep your information straight, since the more results you get in a graph the more cluttered the graph will become.
Most high-end targets have a picture and full bio posted somewhere on the net including company websites, magazines for which they've written or even conferences where they have spoken. But why not let Maltego do the legwork for you by utilizing an easy trick to take advantage of the ever expanding amount of data published by the target themself. So let's run a nifty little transform on our entity via the Rapleaf API to check the target's membership in social networks. This is a great way to combine technology and the unique abilities of humans to verify data.
Maltego comes preloaded with over 100 transforms, but, in order to get the most out of your transforms (in particular the Rapleaf API), you will have to register for an API key. Until you register and input the API key, the Rapleaf transform will be useless to you. In order to get an API key browse out to https://www.rapleaf.com/developer/api_access and fill out the accompanying form. You will then receive an API key from Rapleaf. Once you receive your key open up your transform manager and then select the Rapleaf transform. Input your API key and accept the disclaimer and you will be on your way.
This transform will now go out and cross check the email address you entered with known social networks to see if any links can be determined between the address you entered and numerous social networking sites.
As you can see here it's returned with several results linking the email address in question with accounts on LinkedIn, Twitter and Facebook. We can now examine the links by going to our Property View Window and opening the URL.
Looking at the LinkedIn account of our target, it now becomes possible to associate a face with a name thus becoming quite easy to confirm that this is in fact our target. By examining the page further, you also notice that the Twitter location tracking feature is on. This is good, because it now will allow us to see the tweeting location of our individual.
With the latitude and longitude information we can now bring up various online earth viewing sites and examine the location. We can even bring up a map of the location in question and extrapolate the address and phone number. All of this information gathered with just a simple name and a great tool.
As you have just seen Maltego is a quick and effective information gathering tool that will allow you to pull information from multiple resources all into one place for analysis. We only managed to go over a fraction of Maltego's functionality, but it's easy to see how, in a matter of minutes, you can paint an accurate picture of a person, place or organization. It's definitely a tool that you should not only add to your toolkit but dive in with vigor. So whether you are a seasoned IT security pro or a newbie ready to cut his teeth on a tool, Maltego 3 will give the user a place to stand among the sheer torrent of information likely to be encountered while profiling an organization or individual.
Stay tuned to further tutorials on Maltego including how to create your own custom transform.


text:
Home » Law and Ethics » Eve teasing is very common social problem and every day women come across some form of eve teasing. In this case, do you think that women should be empowered to fight back due to end this evil act.
Eve teasing is very common social problem and every day women come across some form of eve teasing. In this case, do you think that women should be empowered to fight back due to end this evil act.
Sexual harassment, often known as "eve teasing", is a regular occurrence for the women and girls of Bangladesh. A recent study by the Bangladesh National Women Lawyers' Association (BNWLA) showed that almost 90 percent of girls aged 10-18 have undergone the experience. The harassment can take a variety of forms and the perpetrators come from multiple walks of life; they are rich and poor, educated and uneducated; according to the BNWLA study, teenage boys, rickshaw pullers, bus drivers, street vendors, traffic police and often supervisors or colleagues of the working women had all been cited as "eve teasers".
For the girls and women who are subject to sexual harassment, the experiences are traumatic and can leave deep psychological scars. The BNWLA study also noted that in the past two years, at least 12 girls have committed suicide in circumstances stemming from "eve teasing". And the innocuousness of the label belies further violent implications. It is often associated with rape and
murder.
Rape is the most common form of violence against women in Bangladesh. Between 2002 and 2006, there were over five thousand reported incidents. Almost two thousand of those rapes were of girl children. 625 of the victims were killed after they were raped and 69 killed themselves. One has to wonder how many of these crimes could have been prevented if society took sexual harassment more seriously and did not wait until girls were raped and murdered to take action. No one should have to suffer the experience of sexual harassment or the physical and sexual assaults that often come with it. As vicious and tormenting as sexual harassment is for the girls and women who endure it, however, the implications extend to the entire nation.
Curtailed Education
Sexual harassment increases girls' drop-out rate from school.5 Parents concerned about their daughter's honor or safety sometimes keep their daughters home and/or marry them off at an early age.
Education is an inalienable right guaranteed under the Convention on the Rights of the Child to which Bangladesh is a signatory. But more than that, education for girls is key to improving the standard of living in a society. Anything that results in girls not being educated is a disaster for us all.
Study after study shows that educating girls yields a multiplicity of benefits, including later marriages; reduced fertility rates; decreased infant and maternal mortality; improved health and nutritional status; and greater participation of women in political and economic decisions.
According to the UN Population Fund study, educated women farmers perform exceptionally well compared to men. A study found that crop yields could rise up to 22 percent if women farmers had the same education and inputs (such as fertilizer, credit, investment) as men farmers. Kumud Sharma of the Centre for Women's Development Studies in New Delhi has noted that even a basic education raises awareness on once-taboo issues, such as domestic violence. With education comes the confidence and the courage to ask questions and raise a voice against injustice. Educated women take active roles in economic and political decision making and are more likely to resist physical abuse at home.
Education helps women make calculated decisions about their futures. If a woman goes to school, she becomes an educated mother who has basic health care knowledge. An educated woman is less likely to die in pregnancy or childbirth, she provides better nutrition for her children, and she has fewer of them.10 UNICEF reported in 2007 that when mothers are educated through primary school, the mortality rate for their children is halved. Access to education passes through generations; an educated mother is two times more likely to send her child to school than an uneducated mother.
Through the same process in which eve teasing pushes girls out of education, girls who are harassed are also pushed into marriage, before they are physically or mentally prepared. Half of Bangladeshi girls are married before they reach 15 years old, and they usually bear their first child while they are still teenagers. Adolescent girls face the risks of childbirth often without medical care and have a high incidence of maternal mortality. Mothers in aged 15 to 19 face a 20 to 200 percent greater chance of dying in pregnancy than women aged 20 to 24. There are further implications of child marriages. Bangladesh has the highest rates of malnutrition in the world. The vicious cycle of malnutrition is perpetuated by the status of women and particularly young mothers within the family hierarchy. As the young wife, she usually eats last and least, taking whatever is left over after feeding the husband and sons. Hence, she gives birth to underweight, malnourished, unhealthy babies and this cycle continues with no respite in sight.
Hindered Development
Sexual harassment is a manifestation of the patriarchal cultural norms of Bangladesh. It also reinforces those norms; it is both a symptom and a cause. Inasmuch as the harassment contributes to maintaining the low status of women, it also interferes with ending hunger. A 2003 study by the International Food Policy Research Institute (IFPRI), which utilizes data from over one hundred thousand children in 36 developing countries, demonstrates that when women's status gets better, their nutrition improves and their children's nutrition improves. In South Asia, where the status of women is the lowest, improvements in women's status would have the strongest affect. The study concluded that if there were an equalization of men's and women's decision-making power in South Asia, the incidence of underweight children under three years old would fall by up to 13 percentage points, resulting in 13.4 million fewer undernourished children in the region.16 This study shows that elevating women's overall status seems to be a crucial precondition to ending hunger.
Bangladesh is not a country that can afford to dally or placate traditional attitudes when it comes to ending hunger. It has one of the highest rates of child mortality in the world and the majority of those deaths are from causes related to hunger.17 Sexual harassment is implicated in those deaths. The phenomenon must be dealt with seriously and immediately. It affects not only the girls and women who are subject to the acts but also leads to social violence, stops girls from being educated, promotes maternal and child mortality, keeps women from being empowered, and ultimately prevents the end of hunger.
The Response
Article 76 of the Dhaka Metropolitan Police Ordinance and Article 509 of the Penal Code of 1860 affirm that any acts, conducts, or verbal abuses that are used to disgrace women are punishable by law.18 In other words, sexual harassment is illegal. However, state interventions have been inadequate in stopping it to date. The law enforcing authorities have failed to protect women and girls.
We must take sexual harassment seriously and bring it to a halt. We can do this through the legal system, by enforcing the laws, arresting the perpetrators, and bringing them to trial. Alongside a legal response, we must also work to alter the underlying conditions that give rise to the offenses. By raising the status of women and girls, and endeavoring to achieve gender equality, we can end the practice of sexual harassment, end hunger and uplift the quality of life for all.
The Hunger Project and National Girl Child Day
The Hunger Project (THP), a global, strategic organization committed to the sustainable end of world hunger, recognizes that the future of Bangladesh resides in the future of its girls. As long as girls are treated as inferior and less valuable than boys, the general well-being of society cannot advance. Former Secretary General of the United Nations, Kofi Annan, has said: "There is no tool for development more effective than the education of girls. No other policy is as likely to raise economic productivity, lower infant and maternal mortality, improve nutrition and promote health."
In accordance with these facts, The Hunger Project designed a strategy to cause a breakthrough in elevating status of girls in Bangladesh. In 2000, we organized the first National Girl Child Day on September 30th. Working with government ministries, women's organizations, schools, the media, and more than 300 NGOs we seek to awaken Bangladeshi citizens to the critical importance of providing better health, education and nutrition to girls as the highest leverage investment for the future of the country.
National Girl Child Day is now celebrated in festivities across the entirety of the country. Hunger Project volunteers take a leadership role to ensure that the National Girl Child Day celebrations reach out to villagers in every district. Essay contests are held in schools throughout the nation. Both boys and girls win prizes for writing about the importance of better health and education for girls in Bangladeshi society. In festivities in Dhaka, as well as in remote rural areas, organizations rally their constituency to hold teach-ins and marches in support of National Girl Child Day.
National Girl Child day generates powerful media coverage in newspaper, television and radio – educating the public on the critical importance of this issue. The girl child is celebrated for who she is and what she means for the future of Bangladesh.
Violence against women is a common occurrence in most societies whether the violence is physical or mental. In South Asia it is a daily and often deadly fact of life for millions of women and girls. Women and girls are generally looked down upon, trapped within cultural framework, molded by rigid perceptions of patriarchy. As a result violence against women is viewed as a .normal. Phenomenon even from the women's perspective. South Asian women suffer multiple forms of violence including domestic violence, rape, dowry deaths, sexual harassment, suicide, forced marriage, trafficking and other psychological and financial oppression. Violence against women has become one of the most visible social issues in this region.
Violence Against Women in Bangladesh
As a South Asian country, Bangladesh is no different from its neighbors. Violence against women is amongst the most serious threats to overall development and progress in Bangladesh. Widespread violence and repression in numerous forms puts women.s lives at risk in almost all parts of the country. This is further compounded by the gender bias against women in the society. Before discussing the nature and extent of violence against women it is important to focus on the general socio-economic and legal rights of women in Bangladesh.
Socio-economic status of women
Women in Bangladesh are not a homogenous group; they belong to the rich, middle and poor classes and are from different cultural and ethnic minority groups. They are also differentiated by rural and urban settings. Although women constitute half of the population, various indicators reveal that the status of women is much lower than that of men. Their literacy rate is only 43.2 percent, much lower than that of men 61.0. Excessive mortality among women due to discrimination has resulted in a sex ratio in the population of 105 men to every 100 women.1 Despite constitutional guarantees of gender equality and legislative and other affirmative interventions, the status of Bangladeshi women is on the whole dismal. Women are subjected to discrimination and violence within the household, at the workplace and in the society. Their inferior status can be traced to the patriarchal values entrenched in the society which keep women subjugated, assigns them a subordinate and dependent role, and, prevents them from accessing power and resources. Men hold the power and resource within families and control any property and family income. Women are considered as men.s property, their sexual activity, income and labor being systemically controlled by the men in their family. Social expectations still pivot around child rearing and household management. The practice of Purda (seclusion), although changing, is still socially valued. Social norms, education, employment and legal rights and gender inequality in Bangladesh are all perpetuated by patriarchy. From their childhood, women are forced to live in a culture, which tolerates and even permits inhuman treatment to them. As more women are entering the workforce, conflict is growing between the patriarchal social norms and women.s urge for economic independence. In recent years there has been a significant change in the attitude towards women taking up outside employment. With the breakup of the extended family, greater numbers of women are seeking employment. At home, however, workingwomen do not have control over their own income, rather her husband dictates how to spend the money. The influx of women into the employment market has result in further potential forms of violence. Working women face the threat of violence from the public because they are outside the home and from their employer, who are usually male, who are skeptical about women holding positions of responsibility. Furthermore, it is difficult for a woman to get paid employment and when they do there is a lack of parity between her wages and her male counterpart who undertakes similar work.
Women.s Legal Status
A reflection of the low status accorded to women is the discrimination against them in the law. Although the Constitution of Bangladesh states that women have equal footing with men in all spheres of public life2, it also recognizes religious personal laws3, which are unequal to women. According to the Constitution, the State takes responsibility to ensure non-discrimination among its citizens and maintain gender equality. However, in the personal sphere, the state does not specify its responsibility to ensure non-discrimination. Similarly in spite of the declaration of equality in the Constitution, women are deprived of their guaranteed rights by some of the discriminatory civil and religious laws. For example, according to the Citizenship Act, 1951 the right of citizenship can be transferred from the father, neither a woman.s husband nor her children have entitlement of citizen through her. Apart from this, the four most important events in the life of a woman: marriage; divorce; custody of children; and, inheritance rights are governed by personal laws. Since personal laws are based on religious and social value systems, and male dominance is entrenched in the culture, personal laws have reinforced age-old patriarchy and hindered women.s enjoyment of equal rights under the law. In Bangladesh, the majority of the population is Muslim, although several other minority groups exist. Both Muslim and non-Muslim women face gender discrimination under their personal laws. For example, under the Muslim law of inheritance a son receives double what a daughter receives. Similarly a Muslim mother.s custodial right is severely restricted; a mother looses her custodial right the moment she marries a man unrelated to her child. This reinforces the patriarchal notion that children belong to their father.s family. Polygamy of up to four wives is permitted for a Muslim man if he has legally take written permission from his current wife. In practice, however, the wife.s permission is obtained through coercion, threat and violence. Similarly, a Hindu woman receives only a limited share of the paternal property. Under no circumstances does she have recourse to bring a suit of divorce. The situation is awful when a Hindu widow is incapable of contracting a second valid marriage.
It is clear therefore that inequalities in the personal laws act as a considerable obstacle to achieving women.s right. It must be remembered that the enactment of legislation alone does not result in immediate change in women.s actual situation. The government of Bangladesh has from time to time enacted or amended several Acts to safeguard women.s legal right or to improve their status. These laws however are often hardly enforced or are misused. Since women form the most vulnerable group in the society, they repeatedly suffer from the existing discriminative legal system also. In Bangladesh, a victimized woman usually tries to avoid the legal process as she becomes more stigmatized by the society. She dares not file complaints; fearing negligence and harassment in police station, courts and society. The members of the police in most of the cases look down upon the oppressed women and will not take their complaints, unless they are compelled to do so by pressure from a higher authority. In cases of sexual violence the police often advise the victim to submit a medical document. However, the offender may .manage. the police, the medical officer or witness to say that the offence did not happen and the case is not pursed further. The existing legal process is elaborate, time consuming, expensive and often discourages women from taking legal action and enforcing their rights in the court. As a result of the harassment and complexities of the court procedure, survivors are often compelled to accept out of court settlements. The expenses involved in seeking legal redress; lawyer.s fees, court fees, and other incidental expenses, make it very hard for poor, illiterate, and disadvantaged rural women to even consider legal action. Moreover, whilst government legal aid is available, the aid procedure is complicated and the majority of women are unaware of this provision. As a result Non- Governmental Organizations (NGOs) and private volunteer organizations, rather than the State, become the main actors in undertaking legal awareness campaign.
Violence against Women: An Overview
Violence against women remains a prevailing social problem in contemporary Bangladesh. Brutal attacks on women have become commonplace and widespread across the country. Daily news reports are filled with atrocities including physical and psychological torture, sexual harassment, sexual assault, rape, dowry related violence, trafficking, forced prostitution, coerced suicide and murder. The rate of reported violent acts against women has risen consistently and at an alarming rate, especially since the early 1990.s4. The following data has been taken from 22 police stations in the capital city over the last three years.
Reported incidents of violence against women in police stations
Considering that violence against women remains one of the most under reported crimes in Bangladeshi it is implicit that the reported figures are a gross underestimate. Therefore, whilst statistical data is incomplete there is a consensus that the general trend overwhelmingly suggests that women in Bangladesh are at increasing risk of being victimized. Several factors have contributed to this situation. First, as has been mentioned earlier, patriarchal attitudes are deeply entrenched in society. Traditionally men have been in a dominant position and women in a submissive one. This is perceived not only traditional but also natural. Furthermore, there is a tendency, particularly in village areas, to legitimize the patriarchal attitudes on the basis of tradition and orthodox religion. Secondly, various community leaders actively oppose women.s rights in order to maintain their own power positions within the community. Local leaders try to enforce age-old patriarchal traditions and discourage women's empowerment. Furthermore, they often remain silent and fail to protest against violent acts against women, sometimes blaming the victims for the crimes. In this way, they legitimize violation of women who assert rights outside their traditional roles. Thirdly, although many laws are in place to protect women, enforcement of these laws is lax and ineffective. Without proper law enforcement and court procedures, laws are virtually useless. The general public is well aware that law enforcement agencies often accepts bribes, ignores serious complaints, destroys or loses evidence, and frees criminals. In addition, the judicial system has several structural and procedural barriers. Political affiliations and motivations often affect court decisions. The lack of separation of the judiciary has resulted in a compromise of impartial justice in Bangladesh. As a result of the lax law enforcement, the general public has diminished trust and confidence in the system. On the other hand, criminals recognize that there are loopholes in the system, and they might easily avoid punishment. Finally, the community has become desensitized to the sufferings of others. Community members, having a host of problems themselves, fearing retaliation by gangsters and hoodlums, and perhaps aware of the lax law enforcement; they fail to take a proactive role to end violence against women Many other factors have also contributed to the current situation of women in Bangladesh and the alarming increase in the rate of violent acts against women. The factors are interrelated and the problem is very complicated. Unfortunately, there is no quick fix to the current problem of violence against women. It has become increasingly evident that laws and policies alone will be ineffective, rather collaborative multifaceted efforts are required to address this serious social problem.
UN Definition on violence against Women
In 1993, the United Nations General Assembly adopted the Declaration on the Elimination of Violence against Women, the first collaborative international human rights declaration exclusively addressing the issue. The UN declaration emphasizes that the global problem of violence against women crosses national boundaries into the realm of basic human rights. As such, the declaration states that violence against women violates a woman's fundamental human rights and freedoms and that the international community has an obligation to protect and promote those rights. Article 2 of the declaration takes on the difficult task of defining violence against women. The definition of violence against women in the declaration is the internationally accepted definition and states violence against women shall be understood to encompass, but not limited to, physical, sexual, and psychological violence perpetrated by family members, the community, or the state. The forms of violence specifically mentioned in the document include battery, dowry related violence, sexual abuse of children, marital rape, rape, female genital mutilation, sexual harassment, trafficking, forced prostitution, and others. This definition does not claim to be all-inclusive and recognizes that various other forms of violence exist around the globe. The declaration is, therefore, somewhat arbitrary in that it does not provide sufficient guidance regarding controversial issues such as, for example, whether control over a woman's reproductive rights constitutes violence against women. Nevertheless, despite its lacking, the declaration offers the first internationally accepted definition of violence against women and a strong basis for the struggle to eliminate gender violence around the world.
Major trends in violence
In light of the above discussion the most common manifestations of violence in Bangladesh are detailed below. Available data from the Police Department give some indication of the extent of these types of violence. This data indicates that in 2004 there were 3081 crimes for dowry, 3083 women were raped, and 198 women were injured from acid attack. The most significant part of this data is only one seventh (5584) of the total (34061) number of accused were arrested.
Outbreak of violence against women January ~ December 2010
Domestic violence, or violence perpetuated in the home or family environment, is a major social problem in Bangladesh. Domestic violence incidences are fairly common and widespread across the country. Women of all economic strata are vulnerable to maltreatment and abuse by husbands, in-laws, and other family members. Available data suggests that the number of cases of domestic violence is increasingly being reported in the newspaper.
Reports of Domestic Violence in 9 Daily Newspapers 2001-2004
Despite the severe consequences to women's physical and emotional health, domestic violence is not recognized as a serious social problem and society does not perceive domestic violence to be a serious crime. Rather, it is viewed as a personal matter that should be resolved privately within the family. As a result, law enforcement agencies are reluctant to get involved in cases of domestic violence and women are often victimized with no recourse.The implicit indifference of society in matters of domestic violence perpetuates the notion that domestic violence is legitimate and male domination in the family is acceptable. While men take advantage of this right to exert authority, women's tolerance of domestic violence further entrenches domestic violence into the fabric of daily life in Bangladesh. Naturally, questions arise as to why women are silent and do not speak out against domestic violence? Why do so many victims continue to stay with abusive spouses? First, one has to bear in mind the social context in which women are raised. Bangladeshi women, as part of a patriarchal society, are from an early age, taught to be submissive, tolerant, and self-sacrificing. Furthermore, the social belief that a woman's place is in her husband's home is also deeply rooted in women's self-view and self-worth.These social values make it extremely difficult for women to assert themselves and speak out against domestic violence. In cases of marital and family conflict, society generally places the blame on the wife and holds her exclusively responsible for failing to build a strong foundation in the family. Consequently, women are reluctant to complain of domestic violence or file cases against their husbands out of fear of unrelenting social stigmatization. A second major reason that women rarely assert themselves in these matters is that women have few alternatives to staying with their husbands. In some cases a woman might return to her paternal home and find shelter with her parents or siblings, but in most cases, women lack family or community support. With no alternative, women realize that they have no choice but to tolerate domestic violence and make the best of their tragic situation.
Torture by Husband/Wife Beating
Wife beating is the most commonly occurring act of domestic violence in Bangladesh. An international report published by the United Nations in September of 2000 ranked the country first in wife beating and found that nearly half of the adult female population surveyed reported physical abuse by their husbands. This fact may be startling to the international community, however, in Bangladesh it is common knowledge that husbands exert their authority and physically assault wives for even minor mistakes, such as an unsatisfactory meal, an untidy room, a conversation with another man, or any act of disagreement or disobedience. Men have been socially conditioned to genuinely believe in their own superiority. From childhood they are treated differently from their sisters. They grow to believe that they are more valuable and more deserving than women, and that there opinions and views should have more weight than any woman's. Furthermore, predominant religious misinterpretations have further legitimized these feelings. These religious interpretations have also provided men with the justification to chastise wives for disobedience and bring them back to the so-called correct path. In this way, men are able to delude themselves into believing that abuse of their wives amounts to a religious duty and they are completely justified in their actions.
Dowry-Related Violence
The practice of dowry demand (Joutuk) is not deeply rooted in Bengali Muslim tradition, but has emerged as a major social evil in recent years. Generally dowry means the property that the bride.s family gives to the groom or his family upon marriage. However, in Bangladeshi law, dowry has been given an extended meaning .whatever is presented whether before or after marriage under demand, compulsion or pressure as consideration for the marriage can be said to be dowry. The emergence of dowry is more due to greed and commercialization of marriage than the impact of traditional culture. Rising unemployment has contributed to the phenomenon; as more and more young men are unable to find employment, their families use marriage and
dowry demand as a source of income8. Prospective grooms and their families demand large sums of money or property from the would-be bride's family as a precondition to the marriage agreement. Although dowry demand is illegal the practice persists in the rural communities. In fact, few marriages in the rural areas are performed without a dowry condition. In most cases the complete dowry is not paid at the time of marriage. Rather the bride's family pays part of the dowry before the marriage and promises to pay the remainder soon after the marriage. When the bride's family fails to meet the deadline, her husband and in-laws verbally and physically abuse her to compel her family to pay. In many cases the abuse becomes severe in nature, for example, the woman has acid throw on her face, is burnt, severely beaten, and in some cases even murdered.
For the most part, married women in Bangladesh are not aware of their own sexual and reproductive rights, and have only limited control over their own bodies. A woman's freedom of choice regarding sexual intercourse, birth control, pregnancy, pre-natal care, and abortion is restricted by the collaborative decision-making of her husband and his family. A man has complete autonomy to determine when he will have intercourse with his wife. In this situation, the husband is the aggressor and the wife merely a passive participant. Similarly, a wife's personal convictions on birth control and family planning are irrelevant in decision-making; once again she plays a passive role to her husband's wishes. If the husband dislikes birth control, for whatever reason, then the wife has no way of protecting herself from unwanted pregnancies.
Often there is a pressure from the husband's family for the wife to produce offspring, particularly male offspring. The family is mainly concerned with the birth of heirs, not the good health of the mother. As a result, a young woman might begin conceiving at a very early age and endure several consecutive pregnancies in the hope of a male offspring. The in-law family pressures the woman to give birth to sons, as if she has control over biology, and if she fails to meet their expectations, they inflict various forms of physical and psychological abuse on her. Although everyone is involved in the decision for the couple to have a child, nobody is involved in providing adequate pre-natal care to the expectant mother. Only 5% of the reproductive aged women access existing health care facilities. Many women remain neglected and abused in the in-law.s home; they often endure low calorie intake, insufficient nutrition and insufficient medical attention through the course of their pregnancy and as a result are at serious risk of birth complications and maternal mortality. In fact, 37% of all deaths of reproductive aged women are due to maternity related issues. In Bangladesh three women die every hour because of maternal related complexities and nine million women whose lives have been saved following maternity related complications continue to suffer from other long-term diseases.
Rape is one of the most brutal forms of violence against women in Bangladesh. In a culture that holds a woman's chastity sacred, rape crimes are particularly injurious to a woman's self-identity and social future as well as her physical and psychological wellbeing. The ever-increasing rate of rape crimes is an alarming phenomenon and depicts the diminishing value of women in society.
Reported Cases of Rape in 9 Daily Newspapers 2000-2004
It appears that increasing numbers of men perceive women to be nothing more than an object used to satisfy one's sexual urges. Furthermore there is evidence that men not only rape women, but also physically torture and murder the victims as well. In the last few years, gang rape has become the prevalent form of rape in Bangladesh. Several men kidnap a woman, take her to an isolated place, and take turns raping her. This new trend is particularly alarming; first because the attack is much more brutal and damaging to a woman, and second because it shows that rape is an accepted activity in many men's peer groups. Men are discussing and planning gang rapes with their friends, no longer ashamed of their disgusting intentions. As such, rape is being normalized in the male community.
Acid Violence
Acid violence is a crime that has been popularized in Bangladesh. The flinging of acid on the bodies and faces of women became a common means of taking revenge by rejected suitors in the 1980s but has reached the highest peak in recent years. Bangladesh has the highest worldwide incidence of acid violence and, acid burns constitute 9% of the total burn injuries in Bangladesh11. Acid violence involves throwing acid at a person's body to disfigure and scar the person for life. A recent study reveals that land disputes account for 27% of acid attacks, followed by 18% for family disputes, 10% for refusal of sex, 8% for refusal of romantic relationship, 5% for dowry conflicts, 4% for marital disputes, 3% for refusal of marriage proposal, 2% for political enmity, and the remaining 23% for unknown reasons. Despite new harsh laws, acid violence has bas been increasing over the last few years.
Numbers of Cases of Acid Violence Reported….. 2000 ~ 2004
1 Bangladesh National Women's Lawyers Association (BNWLA). "81% Girls Fall Victim to Eve Teasing: Study." BNWLA, July 2008.
http://www.bnwla.org.bd/content/view/186/lang,en/. (accessed September 23rd, 2008).
3 Bangladesh National Women's Lawyers Association (BNLWA). "Eve Teasing." BNWLA. http://www.bnwla.org.bd/content/view/165/133/lang,en/. (accessed September 23rd,
4 Fahmina, Taskin. "Violence Against Women: Statistics of the Last Five Years." Law and Our Rights 10. (2008). http://www.thedailystar.net/law/2007/03/02/investigation.htm.
5 Rashid, Mamunur. "Letting Eve-Teasing Go Unpunished." The Daily Star. September 9, 2007.
7 Statement by H.E. Barrister Ziaur Rahman Khan, MP Hon'ble Chairman Parliamentary Standing Committee on Foreign Affairs Government of the People's Republic of
Bangladesh at the Third Committee of the 60th Session of the UN General Assembly on Agenda item 67: Promotion and Protection of the Rights of Children. New
York, 18 October 2005.
8 United Nations Population Fund (UNFPA). State of World Population 2005: The Promise of Equality. UNFPA: New York, 2005, p. 47.
9 Quoted in "In India, Domestic Violence Rises with Education". Majumdar, Swapna. November, 6th 2003. http://www.womensenews.org/article.cfm/dyn/aid/1591. (accessed
September 22nd, 2008).
10 UNICEF. The State of the World's Children 2007. New York: UNICEF, 2007.
13 UNICEF, "Info by Country." UNICEF. http://www.unicef.org/infobycountry/bangladesh_35505.html. (accesssed September 21, 2008).
14 UNICEF. "Early Marriage: Child Spouses." Innocenti Report. No. 7. UNICEF, March 2001.
15 Centre for Social Research (CSR). "CSR Story." CSR. http://www.csrindia.org/story.html. (accessed September 20th, 2008).
16 Quisumbin, Agnes R. "Reducing Poverty and Hunger in Asia: Women's Status and the Changing Nature of Rural Livelihoods in Asia." 2020 Vision for Food, Agriculture and
the Environment.15. Washington D.C.: IFPRI, March, 2008.
17 UNICEF. The State of the World's Children 2007. New York: 2007.
18 Rashid, Mamunur. "Letting Eve-Teasing Go Unpunished." The Daily Star. September 9, 2007.
Harassment: the effects of "eve teasing" on development in Bangladesh Emma Weisfeld-Adams


text:
Este anexo é composto por uma lista de Promontórios de São Tomé e Príncipe.

Ilha de São Tomé

Ponta Barro Bóbó
Ponta Cruzeiro
Ponta Burnay
Ponta Azeitona
Ponta Basson Gai
Ponta do Homem da Capa
Ponta Lama Porco
Ponta Cavingui
Ponta Baleia
Ponta Barro Preto
Ponta Ío Macaco
Ponta Mussandá
Ponta dos Morcegos
Ponta Lebre
Ponta Diogo Vaz
Ponta Alemã
Ponta Furada
Ponta Juliana
Ponta Griobo
Ponta Planier
Ponta Guebu
Ponta Madioca
Ponta Bote
Ponta da Garça
Ponta Juntabudo
Ponta do Ocá
Ponta dos Bica
Ponta André
Ponta Simão Fidi
Ponta da Agulha
Ponta Praião
Ponta Canido
Ponta de São Marçal
Ponta de São Jerónimo
Ponta Fernão Dias

Ilha do Príncipe

Ponta da Furna
Ponta Marmita
Ponta Manjona
Ponta Pedra Furada
Ponta do Pico Negro
Ponta Café
Ponta Telha
Ponta Cana
Ponta Atalaia
Ponta da Graça
Ponta Viro Viro
Ponta da Mina
Ponta Capitão
Ponta dos Mosteiros

Ilhéu das Rolas

Ponta Joana
Ponta da Garça
Ponta de Santo António

Ver também
Geografia de São Tomé e Príncipe

Referências
Grande Atlas Mundial, Selecções do Reader´s Digest, 1ª Edc. setembro, 2006, Pág. 223. ISBN 972-609-471-2
Grande Dicionário Enciclopédico Ediclube Vol. XVI, Pág. 5574 e 5575. 1996. ISBN 972-719-056-1

Ligações externas
Mapa do Arquipélago de São Tomé e Príncipe.
São Tomé e Príncipe.
worldatlas São Tomé e Príncipe.
Página do Governo da República Democrática de São Tomé e Príncipe.
Convite ao Paraíso Africano - São Tomé e Príncipe.

Promontorios


text:
Summary: Briefs on al-Qahtani's Motion to Compel
By Harry Larson
Thursday, April 19, 2018, 6:00 AM
A U.S. Navy bus passes Camp Delta, a prison at Guantanamo Bay. (Photo: Wikimedia/U.S. Air Force)
Thursday morning, Judge Rosemary Collyer of the D.C. federal district court will hear argument on whether the government may be compelled to examine Guantanamo Bay detainee and alleged 9/11 conspirator Mohammed al-Qahtani to determine whether he is "eligible for direct repatriation." Al-Qahtani, whom U.S. officials have acknowledged was tortured and who, according to his medical expert, suffers various psychological and physical ailments that cannot be treated while still held in custody in Guantanamo, requested in April that the government either repatriate him to Saudi Arabia to receive treatment or else set up a "Mixed Medical Commission" pursuant to the procedures outlined in Section 3-12 of the Army detention regulation. This regulation provides for medical examinations by three-person medical panels consisting of two members from a "neutral country" and one U.S. army medical officer, and implements various provisions of the Third Geneva Convention dealing with "enemy prisoner[s] of war."
The government declined al-Qahtani's request for either repatriation or examination by a medical commission in June, pointing to findings that continued detention was necessary to national security, disagreeing that al-Qahtani "cannot receive effective treatment for his current mental health conditions while he remains in [U.S.] custody," and arguing, in any event, that al-Qahtani does not qualify as an "enemy prisoner of war" under the army regulation or the provisions of the Third Geneva Convention that it implements.
Al-Qahtani subsequently filed a motion to compel a medical commission examination. The case raises complicated issues regarding the scope of courts' habeas jurisdiction and the rights of so-called "enemy combatants" who are not affiliated with a traditional state entity. The major points in both sides' briefs are explained below.
Because 28 U.S.C. § 2241(e)(2) denies any court "jurisdiction to hear or consider any [non-habeas] action against the United States … relating to any aspect of the detention, transfer, treatment, trial, or conditions of confinement of an alien" held as an enemy combatant, the court may only exercise jurisdiction over al-Qahtani's claim to the extent it sounds in habeas. (While Congress purported to also strip habeas jurisdiction through 28 U.S.C. § 2241(e)(1), the Supreme Court held that provision to be an unconstitutional violation of the suspension clause in Boumediene v. Bush).
Though medical examinations are not themselves traditional habeas relief, al-Qahtani argues that the power to compel them must come part-and-parcel with the court's habeas jurisdiction. Because the legality of al-Qahtani's detention and availability of habeas relief might turn on the results of a medical commission's determination, the court must, al-Qahtani argues, have power to order such a determination in order to give meaning to its habeas jurisdiction. In support, al-Qahtani cites the All Writs Act , which empowers courts to "issue all writs necessary or appropriate in aid of their respective jurisdictions and agreeable to the usages and principles of law." Al-Qahtani also argues that the court should issue a preliminary injunction compelling access to a medical commission pursuant to Federal Rule of Civil Procedure 65(a), claiming that the following equities weigh in its favor:—his high risk of irreparable harm, high likelihood of success on the merits, the slight injury the government would face as a result of forming the medical commission, and the "the public interest in justice and the rule of law."
By contrast, the government argues that the court should deny al-Qahtani's request for "extraordinary relief too far removed from habeas' traditional remedy of release." Al-Qahtani, according to the government, does not "seek an order of release or challenge his conditions of confinement"; rather, he "seeks an order compelling the United States to take a series of actions that only, in the end, may possibly result in his release." Further, "such an order would also require the United States to, among other things, develop standards for determining the disabilities and sicknesses that would warrant repatriation in this noninternational armed conflict against al-Qaida, Taliban, and associated forces, which stretches habeas far beyond its traditional remedy of release." Because the All Writs Act "does not enlarge the Court's habeas jurisdiction or provide it with an independent basis for jurisdiction in the first instance," it could not, according to the government, serve as the basis for sweeping such extraordinary remedies under habeas' umbrella.
To support its narrower conception of habeas jurisdiction, the government cites language in the Supreme Court's decision in Skinner v. United States suggesting that "when a prisoner's claim would not 'necessarily spell speedier release,' that claim does not lie at 'the core of habeas corpus,'" as well as the D.C. Circuit's interpretation of Skinner in Davis v. United States Sentencing Commission as "suggest[ing] that habeas might not even be available for 'probabilistic' claims." The government further cites Nettles v. Grounds, a recent en banc Ninth Circuit decision, which held that "[b]ecause success on [the plaintiff's] claims would not necessarily lead to his immediate or earlier release from confinement, [his] claim does not fall within 'the core of habeas corpus.'"
Finally, the government argues that even if al-Qahtani's claim does sound in habeas, the court should still "refrain from exercising its habeas jurisdiction" because, as the Supreme Court noted in Munaf v. Geren, "habeas corpus is governed by equitable principles" and "prudential concerns." Those concerns weigh against exercising jurisdiction because
an order requiring the Executive to take certain actions in conformance with asserted treaty obligations, as implemented through military regulation, and contrary to the Executive's interpretation of how those obligations apply to Petitioner … would be inconsistent with the Executive's interpretation of the relevant treaty and regulation provisions, and would place an extraordinary burden on the Executive.
The government also claims that because the relief al-Qahtani seeks would change the status quo by creating a new medical body, it "would go well beyond the scope of a preliminary injunction," requiring the court to evaluate the request as one for a permanent injunction. And it argues that al-Qahtani cannot make the required showing of an irreparable injury, the inadequacy of other remedies, a favorable balance of hardships, and a lack of harm to the public interest.
Al-Qahtani criticized the government's logic in his reply brief as leading to "an inelegant Catch-22," that would, by analogy, "prevent this Court from ruling on a motion to compel access to a prisoner at Guantánamo filed by his lawyers" because a counsel's access to his client, though "a predicate to seeking release in habeas," does "not directly implicate release from custody or a change in conditions of confinement." Al-Qahtani further urges that the government placed too much weight on one-off lines from Skinner and related cases, while not putting enough emphasis on more recent decisions from within the D.C. Circuit.
Specifically, al-Qahtani pointed to the D.C. Circuit's decisions in Al Warafi v. Obama, where the court's decision on habeas relief turned on an arguably similar question, namely whether the detainee qualified "as 'medical personnel' within the meaning of Article 24 of the First Geneva Convention and Section 3-15(b)(1)-(2) of the Army detention regulation." He also cited the D.C. District Court's decision in Aamer v. Obama, where the court denied a detainee's request for repatriation. There the detainee had raised a similar medical claim under Section 3-12 of the Army regulation, and the court claimed that there was "no dispute that [it had] subject matter jurisdiction over" the action. However, Aamer had "not established his explicit entitlement to release under the Regulation," because he had "neither [applied] for repatriation… nor requested an examination by a Mixed Medical Commission." By contrast, al-Qahtani had.
Merits: Scope of the Conflict and Enemy Combatants vs. "Other Detainees"
If the court does exercise jurisdiction over al-Qahtani's claim, it must then determine whether Section 3-12 actually entitles him to a medical commission examination. Tracking the petitioner's earlier argument in Aamer, al-Qahtani argues that the regulation requires such commissions for enemy prisoners of war and, because he does not fall into any of the regulation's explicit categories of prisoners, he should, according to a provision in the regulation's glossary, be considered as an "other detainee" and "be treated as an enemy prisoner of war until a legal status is ascertained by a competent authority." The fact that a 2004 Combatant Status Review Tribunal had designated al-Qahtani as an "enemy combatant," like recent decisions of the Periodic Review Board, simply have "no relevance under AR 190-8."
The government responds that the Army regulation cannot be interpreted in a vacuum but must rather be understood with respect to the provisions of the Third Geneva Convention it aims to implement. Indeed, the regulation embraces that principle in Section 1-1 where it stipulates that "the provisions of the Geneva Conventions take precedence" over any contrary regulations. The convention, in turn, offers "prisoner of war" protections to soldiers in a state army or certain other uniformed combatants. Al-Qahtani, by contrast, can only claim the lesser protections under Common Article 3 of the Geneva Conventions that, in "armed conflicts not of an international character," detained persons "shall in all circumstances be treated humanely."
Here, the government argues, the court should defer to President Bush's 2002 determination that al-Qaeda fighters "do not qualify for prisoner of war status." Al-Qahtani is therefore not entitled to the protections of many Geneva Convention provisions—or the army regulations implementing them. And because the Army regulation's specifications regarding "other detainees" are made "[i]n accordance with Article 5 [of the Third Geneva Convention]" they should not apply to al-Qahtani. The D.C. Circuit's arguably contrary approach in Al Warafi, where it applied certain provisions in the Army detention regulation dealing with medical personnel, should not govern this case as the "provisions at issue [there] concerned a fundamentally distinct category of persons" for whom release may have been a matter of entitlement, rather than a class of individuals whom the regulationmerely makes "eligible" for repatriation.
Further, the complexities of "establish[ing] procedures governing the operation of" any commissions established pursuant not just to the Army regulation but also the Geneva Convention's requirements would raise "novel, complex, and difficult issues … likely to be the subject of additional litigation that [would] further entangle[] the Court." Such entanglement might affect the "United States' interests with regard to the Geneva Conventions and related laws and customs of armed conflict."
Al-Qahtani argues, by contrast, that the Army regulation is binding domestic law that the court must apply independent of the Geneva Conventions. Section 1-1's provision for the conventions' primacy over contrary regulations should be understood to "enshrine[] a baseline" which the "United States remains at liberty to expand." This principle is reflected in various provisions of the Defense Department's "Law of War Manual" and in the Army regulation's application to "persons held during military operations other than war."
Al-Qahtani further argues that, even if certain of the regulation's protections are limited to "international" conflicts, "there is no controlling authority finding that the conflict [in Afghanistan] was noninternational in nature." Indeed, the D.C. Circuit's willingness to apply the regulation in Al Warafi might suggest protections attaching to international conflicts applied.
Further, al-Qahtani argues, whatever the conflict in Afghanistan became over time, al-Qahtani "was allegedly taken into U.S. custody in December of 2001" when "the United States still characterized the conflict … as an international armed conflict." Moreover, "irrespective of whether or how the conflict out of which Mr. al-Qahtani's imprisonment arose is characterized," at least Common Article 3 should apply—and that alone might "encompass[] the obligation to repatriate ill prisoners like Mr. al-Qahtani."
Finally, al-Qahtani argues that, notwithstanding President Bush's determination that al-Qaeda fighters should not receive prisoner-of-war protections, "it is not the
Executive's province to say what the law is here." Citing the Supreme Court's independent determination of what the laws of war require in Hamdan v. Rumsfeld, as well as the court's reservation regarding Hamdan's "potential status as a prisoner of war" and Justice David Souter's reference to the Army regulation's requirements in his concurrence in Hamdi v. Rumfeld, al-Qahtani urges the court to make an independent determination of his status.
Al-Qahtani's motion to compel implicates a complex set of issues regarding the scope of federal courts' habeas jurisdiction and the application and incorporation of various international law protections to so-called enemy combatants. Judge Collyer has her work cut out for her.
Detention & Guantanamo,
Guantanamo Litigation: District Court
Harry is a second year student at Harvard Law School, where he is an editor of the Harvard Law Review. He has interned with Akin Gump and with the Mexican American Legal Defense and Educational Fund and previously worked on expert economic testimony at the litigation consulting firm Cornerstone Research. He graduated from Yale College in 2014 with a BA in English and Economics.
Guantanamo Detainee Files Suit for Release Following Completion of 10-Year Sentence
Tia Sewell Mon, Jul 11, 2022, 1:30 PM
Al-Qahtani Repatriated to Saudi Arabia Following Judge's Grant of His Motion for a Mixed Medical Commission
Anastasia Bradatan Thu, May 12, 2022, 10:40 AM
Ketanji Brown Jackson, Guantanamo and the Role of Defense Attorneys
Benjamin Wittes Sun, Mar 20, 2022, 4:42 PM
Guantanamo Bay: Twenty Years Later
John Bellinger Mon, Jan 24, 2022, 8:01 AM
It's Time to Close Guantanamo
Dianne Feinstein Tue, Jan 11, 2022, 8:01 AM