Thank you for contacting me regarding the fiscal year 2012 National Defense Authorization Act, passed by the Senate on December 1, 2011, that included several provisions relating to the authority of the United States to detain certain individuals associated with al Qaeda, the Taliban and 9/11 conspirators.
It is well-founded in our history that the United States has the authority to hold enemy combatants until the end of hostilities in order to prevent their return to the battlefield. The detainee provisions in the National Defense Authorization Act codify this long-recognized authority, and make clear that any al Qaeda terrorist, whether foreign or American, who takes up arms against the United States, can be held under the laws of war. Because we are at war, detention within a military framework is often the most fitting solution for handling certain terrorist detainees. At the same time, the provisions ensure that the rights of United States citizens continue to be protected by the Constitution. Thus, any American detained under this authority would still be able to challenge his detention in a federal habeas proceeding.
During the vigorous debate of the National Defense Authorization Act, several Senators offered amendments intended to address perceived problems with the provisions. Rather than improve the legislation, however, these amendments would have severely undermined our intelligence collection efforts from suspected terrorists. As we continue to fight al Qaeda and other terrorists, our primary concern must be to ensure that our military and intelligence professionals have the authority and flexibility they need to collect valuable intelligence. Because of the negative impact these amendments would likely have had on such critical collection efforts, I am thankful the amendments were defeated. Following vigorous debate and an agreement to re-emphasize current law concerning the detention of persons captured inside the United States, the Senate passed the National Defense Authorization bill with overwhelming bipartisan support. Following a conference with the House of Representatives, the final version of the National Defense Authorization Act was passed on December 15th.
If you would like to receive timely email alerts regarding the latest congressional actions and my weekly e-newsletter, please sign up via my web site at: www.chambliss.senate.gov. Please let me know how I may be of assistance to you.
Dear Mr. Chambliss:
I appreciate your thoughtful, reasoned response. As I still disagree with your position on this legislation, I present the following counter-arguments for your consideration as time permits.
Article I, section 8 of the Constitution grants Congress authority to declare war. No such declaration has been issued since June of 1942. We are not, therefore, at war.
While several extended military engagements have been authorized by Congress since cessation of the Second World War, including our operations in Iraq and Afghanistan, the War Powers Resolution of 1973 was passed specifically to limit the authority of the President to engage our military forces indefinitely. This legislation has been controversial ever since, but has not yet been declared unconstitutional by the Supreme Court. As recently as March of this year, President Obama was rebuked by Congress for involving our military in the Libyan conflict without adhering to the provisions outlined in the aforementioned resolution.
Because organizations such as al Qaeda operate independently of a specific state government against whom we might declare war, there is little hope for ever establishing a peace treaty to which all of their members will adhere, irrespective of the outcome of any actions by our military. While our military may be effective in reducing - or even eliminating entirely - the strength and influence of any one specific terrorist organization, there will always be terrorists who wish us harm. There will always be a need for us to protect ourselves from these individuals and organizations. To consider this situation, therefore, an official state of war - at least, in the constitutional sense - is to accept a permanent condition under which the rights of citizens are reduced in order to facilitate such protection.
Article III, section 3 of the Constitution provides a definition for treason, including an "aid and comfort" clause. As such, no additional authorization is required to allow our government to punish citizens who either participated in the attacks on 9/11 or supported those who did. Such punishment, however, would be pursuant to a conviction of treason, and the Sixth Amendment guarantees the right to a speedy and public trial. To detain any citizen on suspicion of acts that would constitute treason without a timely opportunity to confront their accuser and argue their innocence, with aid of legal counsel, is a clear violation of that citizen's constitutional rights.
In closing, I would argue that one of the most well-founded principles in our history is the notion of "innocent until proven guilty". If the intention of indefinitely detaining enemy combatants is to "prevent their return to the battlefield", that implies that the battlefield is precisely where we originally found them, directly engaging our forces, weapon in hand. Anything falling outside of that scenario is a question of evidence. Any argument that we must detain an individual without trial because we "know" they are an enemy combatant is logically fallacious: while we may have evidence that a given individual has committed treasonous acts, until a conviction has been established, we do not have, in the judicial sense, proof. We cannot know for certain without a trial, so we cannot deny one category of suspect a trial without severely undermining the notion that a suspect's guilt must be judicially proven in order to justify their continued detention. To do so threatens the very fabric of our society; it may, from time to time, provide physical protection for a few Americans… but it makes us all less American.
locating XPage components with XspQuery
Sun, Apr 14th 2013 12:00a Tim Tripcony Several years ago, I wrote a utility Java class designed to make it easy to search for components within the current XPage instance based on various criteria. I've found it enormously useful, and, apparently, so has Keith Strickland, because he added it to org.openntf.xsp.extlib, complete with a few refinements. As an example of how you might use this, examine the following line of code:
List requiredFields = new XspQuery()
.addInstanceOf(UIInput.class)
.addEquals("required", true)
.loc [read] Keywords: ldd
lotus
dojo
java
javascript
openntf
oracle
server
388
your how is not your what
Wed, Apr 3rd 2013 11:36a Tim Tripcony I've noticed a pattern emerging when I'm asked for help with XPages. Here's a representative conversation:
"I'm trying to do [X] and it's not working. How can I do that?"
"What are you trying to accomplish?"
"I already told you. I'm trying to do [X]."
"No, that's how you're trying to do it. What are you trying to do?"
For example, replace "[X]" with "reach into a repeat control from outside it" (since this has become the most frequent topic I'm asked about [read] Keywords: xpages application
my new favorite quote
Sat, Mar 23rd 2013 5:20p Tim Tripcony "We go about our daily lives understanding almost nothing of the world. We give little thought to the machinery that generates the sunlight that makes life possible, to the gravity that glues us to an earth that would otherwise send us spinning off into space, or the atoms of which we are made and on whose stability we fundamentally depend. Except for children (who don’t know enough not to ask the important questions), few of us spend much time wondering why nature is the way it is; where the [read] Keywords: wiki
Taking the scary out of Java in XPages: Prologue
Tue, Feb 26th 2013 9:50p Tim Tripcony The discussion following my last post made stark the need for greater availability of information that makes the nature of Java more accessible to Domino developers. Credit for the title of this post goes to Declan, who is considering writing a series of blog posts on this topic. I will be doing the same; hopefully there will be a fair amount of duplication. As David Leedy is fond of stating, it's a good thing when several people share the same information, because that makes it easier for the [read] Keywords: domino
xpages application
java
152
SSJS is a crutch
Fri, Feb 22nd 2013 10:50p Tim Tripcony I've been debating for quite a while whether I should write this post. It obviously makes a potentially controversial statement. A fellow developer who knew I was drafting it put my hesitance into perspective: "you really want to be that guy?" This was my response:
I want to be the guy who saves people pain. But sometimes to do that, you have to tell your friend if she wants to stop being punched in the face, she needs to leave the guy who keeps punching her in the face.
This post is ju [read] Keywords: agent
domino
formula language
ibm
lotus
lotusscript
notes
xpages applications
development
java
javascript
openntf
wiki
123
Passthru vs. component - my perspective
Sat, Feb 16th 2013 9:40p Tim Tripcony Paul Withers posted a thorough article explaining the differences between namespaced XPage components (e.g. ) and their corresponding passthru elements (e.g. ), providing numerous examples of what actually happens when these objects are constructed. I've always heard (and often repeated) that passthru elements are more efficiently processed than their namespaced equivalents, so Paul's post inspired me to offer my own perspective.
Simply put, there's practically no difference... but there a [read] Keywords: acl
domino
xpages application
development
properties
security
135
org.openntf.xsp.extlib
Mon, Jan 21st 2013 5:20a Tim Tripcony About 18 months ago, I created an OpenNTF project called Community Control Library. The fundamental reason for creating the project was my belief that the single factor keeping the Domino community from realizing the true potential of the platform is the assumption that the XPages Extension Library is the extension library, not an extension library. Let's briefly revisit its history:
IBM starts an internal project, code named "Porus" (in reference to the Greek / Roman god of plenty), inte [read] Keywords: domino
ibm
notes
policies
xpages application
applications
best practice
community
development
openntf
wiki
