We hold these truths to be self-evident, that all men are created equal, that they are endowed by their Creator with certain unalienable Rights, that among these are Life, Liberty and the pursuit of Happiness.--That to secure these rights, Governments are instituted among Men, deriving their just powers from the consent of the governed, --That whenever any Form of Government becomes destructive of these ends, it is the Right of the People to alter or to abolish it, and to institute new Government, laying its foundation on such principles and organizing its powers in such form, as to them shall seem most likely to effect their Safety and Happiness. Prudence, indeed, will dictate that Governments long established should not be changed for light and transient causes; and accordingly all experience hath shewn, that mankind are more disposed to suffer, while evils are sufferable, than to right themselves by abolishing the forms to which they are accustomed. But when a long train of abuses and usurpations, pursuing invariably the same Object evinces a design to reduce them under absolute Despotism, it is their right, it is their duty, to throw off such Government, and to provide new Guards for their future security.--Such has been the patient sufferance of these Colonies; and such is now the necessity which constrains them to alter their former Systems of Government. The history of the present King of Great Britain is a history of repeated injuries and usurpations, all having in direct object the establishment of an absolute Tyranny over these States. To prove this, let Facts be submitted to a candid world.
Below are key documents highlighting how the Department of Homeland Security (DHS) was created through the combination of all or part of 22 different federal departments and agencies into a unified, a more effective, integrated Department, creating a strengthened homeland security enterprise and a more secure America that is better prepared to confront the range of threats we face.
The HTTP 201 Created success status response code indicates that the request has succeeded and has led to the creation of a resource. The new resource, or a description and link to the new resource, is effectively created before the response is sent back and the newly created items are returned in the body of the message, located at either the URL of the request, or at the URL in the value of the Location header.
\n The HTTP 201 Created success status response code indicates that the request has\n succeeded and has led to the creation of a resource. The new resource, or a description\n and link to the new resource, is effectively created before the response is sent back\n and the newly created items are returned in the body of the message, located at either\n the URL of the request, or at the URL in the value of the Location header.\n
The conservation legacy of Theodore Roosevelt is found in the 230 million acres of public lands he helped establish during his presidency. Much of that land - 150 millions acres - was set aside as national forests. Roosevelt created the present-day USFS in 1905, an organization within the Department of Agriculture. The idea was to conserve forests for continued use. An adamant proponent of utilizing the country's resources, Roosevelt wanted to insure the sustainability of those resources.
During Roosevelt's administration, the National Park System grew substantially. When the National Park Service was created in 1916 - seven years after Roosevelt left office - there were 35 sites to be managed by the new organization. Roosevelt helped created 23 of those. See below for a list of the sites created during his administration which are connected with the National Park Service.
In 1789, Congress created three Executive Departments: Foreign Affairs (later in the same year renamed State), Treasury, and War. It also provided for an Attorney General and a Postmaster General. Domestic matters were apportioned by Congress among these departments.
The Social Security number (SSN) was created in 1936 for the sole purpose of tracking the earnings histories of U.S. workers, for use in determining Social Security benefit entitlement and computing benefit levels. Since then, use of the SSN has expanded substantially. Today the SSN may be the most commonly used numbering system in the United States. As of December 2008, the Social Security Administration (SSA) had issued over 450 million original SSNs, and nearly every legal resident of the United States had one. The SSN's very universality has led to its adoption throughout government and the private sector as a chief means of identifying and gathering information about an individual.
In 1972, SSA created an electronic file, the Numerical Index File or Numident, to house the numerically-ordered master file of all assigned SSNs. In 1973, SSA began converting its legacy SS-5 records to the Numident electronic database, completing the conversion in 1979. There is one Numident record for each SSN ever assigned.
Also, in 1979 SSA created an electronic file called MULTX from a set of punch cards identifying multiple SSNs that was maintained by SSA's Office of Earnings Operations. As of December 2007, SSA had identified and cross-referenced in the MULTX file over 4.7 million individuals with multiple SSNs, about 93 percent of whom have only two SSNs. Generally, those with multiple SSNs are the "very old" on the Numident; a study conducted in 2002 showed a weighted average age of 82.9 (SSA 2002). The requirement for proof of age and identity for SSN applicants beginning in 1974 combined with the implementation of an automated SSN screening system in 1984 have significantly reduced the multiple-SSN problems.
In August 1987, SSA began a three-state pilot of the "Enumeration at Birth" (EAB) process in which the parent of a newborn can request an SSN as part of the state's birth registration process. Additional states began to participate in EAB in July 1988. By the end of 1991, 45 states, the District of Columbia, Puerto Rico, and New York City had signed agreements (Long 1993, 83). Today, over 90 percent of parents use the EAB process offered in all 50 states plus Puerto Rico and the District of Columbia. SSA receives nearly three-quarters of original SSN applications through the EAB process and issues over 4 million SSNs via EAB each year (SSA 2006). No microfilm SS-5 exists for a record created through the EAB process.
On November 18, 2008, President George W. Bush issued EO 13478 rescinding the 1943 EO requiring all federal agencies to use the SSN as an identifier. Then in December, the FTC (2008) issued a plea to companies, schools, and other private entities to find better ways to authenticate identities than using the SSN. State and local entities have begun to delete SSNs on electronic versions of public records. Congress has also considered legislation that would require the Centers for Medicare and Medicaid Services to use an alternative to the SSN as the Medicare claim number. Even SSA, which created the SSN for its program use, has ceased to print the full SSN on some of its correspondence with beneficiaries (Lockhart 2002). The agency now advises individuals to keep their Social Security card in a safe place and not to carry it with them (SSA 2007a).
The vacancies in the white projects were created primarily by the Federal Housing Administration program to suburbanize America, and the Federal Housing Administration subsidized mass production builders to create subdivisions that were "white-only" and they subsidized the families who were living in the white housing projects as well as whites who were living elsewhere in the central city to move out of the central cities and into these white-only suburbs. So it was the Federal Housing Administration that depopulated public housing of white families, while the public housing authorities were charged with the responsibility of housing African-Americans who were increasingly too poor to pay the full cost of their rent.
Runs your workflow when check suite activity occurs. A check suite is a collection of the check runs created for a specific commit. Check suites summarize the status and conclusion of the check runs that are in the suite. For information, see "Getting started with the Checks API." For information about the check suite APIs, see "CheckSuite" in the GraphQL API documentation or "Checks" in the REST API documentation.
Runs your workflow when someone creates a deployment in the workflow's repository. Deployments created with a commit SHA may not have a Git ref. For information about the APIs to create a deployment, see "createDeployment" in the GraphQL API documentation or "Deployments" in the REST API documentation.
Runs your workflow when a third party provides a deployment status. Deployments created with a commit SHA may not have a Git ref. For information about the APIs to create a deployment status, see "createDeploymentStatus" in the GraphQL API documentation or "Create a deployment status" in the REST API documentation.
Runs your workflow when a discussion in the workflow's repository is created or modified. For activity related to comments on a discussion, use the discussion_comment event. For more information about discussions, see "About discussions." For information about the GraphQL API, see "Discussion."
Runs your workflow when a comment on a discussion in the workflow's repository is created or modified. For activity related to a discussion as opposed to comments on the discussion, use the discussion event. For more information about discussions, see "About discussions." For information about the GraphQL API, see "Discussion."
Runs your workflow when an issue or pull request comment is created, edited, or deleted. For information about the issue comment APIs, see "IssueComment" in the GraphQL API documentation or "Issue comments" in the REST API documentation.
Runs your workflow when an issue in the workflow's repository is created or modified. For activity related to comments in an issue, use the issue_comment event. For more information about issues, see "About issues." For information about the issue APIs, see "Issue" in the GraphQL API documentation or "Issues" in the REST API documentation.