951 resultados para Sotavangit ja internoidut : Prisoners of war and internees
Resumo:
The organic matter contained within a series of Albian to Cenomanian, dark gray to black marls was characterized using pyrolysis techniques and analysis (elemental and carbon isotopes) of isolated kerogens. It was concluded that this material had a marine affinity. Variations in geochemical characteristics reflect differences in the extent of preservation, rather than changes in organic provenance. These changes appear to reflect differences in water depth and the position of the depositional site relative to the oxygen-minimum zone. Sediments displaying the most elevated levels of organiccarbon and hydrogen enrichment probably reflect sedimentation within the oxygen-minimum zone. Waters within the oxygen-minimum zone were probably dysaerobic, rather than anoxic. The presence of at least trace quantities of oxygen at the depositional site explains the poor degree of organic preservation and the material's largely gas-prone characteristics.
Resumo:
Holes drilled into the volcanic and ultrabasic basement of the Izu-Ogasawara and Mariana forearc terranes during Leg 125 provide data on some of the earliest lithosphere created after the start of Eocene subduction in the Western Pacific. The volcanic basement contains three boninite series and one tholeiite series. (1) Eocene low-Ca boninite and low-Ca bronzite andesite pillow lavas and dikes dominate the lowermost part of the deep crustal section through the outer-arc high at Site 786. (2) Eocene intermediate-Ca boninite and its fractionation products (bronzite andesite, andesite, dacite, and rhyolite) make up the main part of the boninitic edifice at Site 786. (3) Early Oligocene intermediate-Ca to high-Ca boninite sills or dikes intrude the edifice and perhaps feed an uppermost breccia unit at Site 786. (4) Eocene or Early Oligocene tholeiitic andesite, dacite, and rhyolite form the uppermost part of the outer-arc high at Site 782. All four groups can be explained by remelting above a subduction zone of oceanic mantle lithosphere that has been depleted by its previous episode of partial melting at an ocean ridge. We estimate that the average boninite source had lost 10-15 wt% of melt at the ridge before undergoing further melting (5-10%) shortly after subduction started. The composition of the harzburgite (<2% clinopyroxene, Fo content of about 92%) indicates that it underwent a total of about 25% melting with respect to a fertile MORB mantle. The low concentration of Nb in the boninite indicates that the oceanic lithosphere prior to subduction was not enriched by any asthenospheric (OIB) component. The subduction component is characterized by (1) high Zr and Hf contents relative to Sm, Ti, Y, and middle-heavy REE, (2) light REE-enrichment, (3) low contents of Nb and Ta relative to Th, Rb, or La, (4) high contents of Na and Al, and (5) Pb isotopes on the Northern Hemisphere Reference Line. This component is unlike any subduction component from active arc volcanoes in the Izu-Mariana region or elsewhere. Modeling suggests that these characteristics fit a trondhjemitic melt from slab fusion in amphibolite facies. The resulting metasomatized mantle may have contained about 0.15 wt% water. The overall melting regime is constrained by experimental data to shallow depths and high temperatures (1250? C and 1.5 kb for an average boninite) of boninite segregation. We thus envisage that boninites were generated by decompression melting of a diapir of metasomatized residual MORB mantle leaving the harzburgites as the uppermost, most depleted residue from this second stage of melting. Thermal constraints require that both subducted lithosphere and overlying oceanic lithosphere of the mantle wedge be very young at the time of boninite genesis. This conclusion is consistent with models in which an active transform fault offsetting two ridge axes is placed under compression or transpression following the Eocene plate reorganization in the Pacific. Comparison between Leg 125 boninites and boninites and related rocks elsewhere in the Western Pacific highlights large regional differences in petrogenesis in terms of mantle mineralogy, degree of partial melting, composition of subduction components, and the nature of pre-subduction lithosphere. It is likely that, on a regional scale, the initiation of subduction involved subducted crust and lithospheric mantle wedge of a range of ages and compositions, as might be expected in this type of tectonic setting.
Resumo:
Twenty-six samples representing the wide range of lithologies (low- and intermediate-Ca boninites and bronzite andesites, high-Ca boninites, basaltic andesites-rhyolites) drilled during Leg 125 at Sites 782 and 786 on the Izu-Bonin outer-arc high have been analyzed for Sr, Nd, and Pb isotopes. Nd-Sr isotope covariations show that most samples follow a trend parallel to a line from Pacific MORB mantle (PMM) to Pacific Volcanogenic sediment (PVS) but displaced slightly toward more radiogenic Sr. Pb isotope covariations show that all the Eocene-Oligocene samples plot along the Northern Hemisphere Reference Line, indicating little or no Pb derived from subducted pelagic sediment in their source. Two young basaltic andesite clasts within sediment do have a pelagic sediment signature but this may have been gained by alteration rather than subduction. In all isotopic projections, the samples form consistent groupings: the tholeiites from Site 782 and Hole 786A plot closest to PMM, the boninites and related rocks from Sites 786B plot closest to PVS, and the boninite lavas from Hole 786A and late boninitic dikes from Hole 786B occupy an intermediate position. Isotope-trace element covariations indicate that these isotopic variations can be explained by a three-component mixing model. One component (A) has the isotopic signature of PMM but is depleted in the more incompatible elements. It is interpreted as representing suboceanic mantle lithosphere. A second component (B) is relatively radiogenic (epsilon-Nd = ca 4-6; 206Pb/204Pb = ca 19.0-19.3; epsilon-Sr = ca -10 to -6)). Its trace element pattern has, among other characteristics, a high Zr/Sm ratio, which distinguishes it from the ìnormalî fluid components associated with subduction and hotspot activity. There are insufficient data at present to tie down its origin: probably it was either derived from subducted lithosphere or volcanogenic sediment fused in amphibolite facies; or it represents an asthenospheric melt component that has been fractionated by interaction with amphibole-bearing mantle. The third component (C) is characterized by high contents of Sr and high epsilon-Sr values and is interpreted as a subducted fluid component. The mixing line on a diagram of Zr/Sr against epsilon-Sr suggests that component C may have enriched the lithosphere (component A) before component B. These components may also be present on a regional basis but, if so, may not have had uniform compositions. Only the boninitic series from nearby Chichijima would require an additional, pelagic sediment component. In general, these results are consistent with models of subduction of ridges and young lithosphere during the change from a ridge-transform to subduction geometry at the initiation of subduction in the Western Pacific.
Resumo:
This document is the result of a process of web development to create a tool that will allow to Cracow University of Technology consult, create and manage timetables. The technologies chosen for this purpose are Apache Tomcat Server, My SQL Community Server, JDBC driver, Java Servlets and JSPs for the server side. The client part counts on Javascript, jQuery, AJAX and CSS technologies to perform the dynamism. The document will justify the choice of these technologies and will explain some development tools that help in the integration and development of all this elements: specifically, NetBeans IDE and MySQL workbench have been used as helpful tools. After explaining all the elements involved in the development of the web application, the architecture and the code developed are explained through UML diagrams. Some implementation details related to security are also deeper explained through sequence diagrams. As the source code of the application is provided, an installation manual has been developed to run the project. In addition, as the platform is intended to be a beta that will be grown, some unimplemented ideas for future development are also exposed. Finally, some annexes with important files and scripts related to the initiation of the platform are attached. This project started through an existing tool that needed to be expanded. The main purpose of the project along its development has focused on setting the roots for a whole new platform that will replace the existing one. For this goal, it has been needed to make a deep inspection on the existing web technologies: a web server and a SQL database had to be chosen. Although the alternatives were a lot, Java technology for the server was finally selected because of the big community backwards, the easiness of modelling the language through UML diagrams and the fact of being free license software. Apache Tomcat is the open source server that can use Java Servlet and JSP technology. Related to the SQL database, MySQL Community Server is the most popular open-source SQL Server, with a big community after and quite a lot of tools to manage the server. JDBC is the driver needed to put in contact Java and MySQL. Once we chose the technologies that would be part of the platform, the development process started. After a detailed explanation of the development environment installation, we used UML use case diagrams to set the main tasks of the platform; UML class diagrams served to establish the existing relations between the classes generated; the architecture of the platform was represented through UML deployment diagrams; and Enhanced entity–relationship (EER) model were used to define the tables of the database and their relationships. Apart from the previous diagrams, some implementation issues were explained to make a better understanding of the developed code - UML sequence diagrams helped to explain this. Once the whole platform was properly defined and developed, the performance of the application has been shown: it has been proved that with the current state of the code, the platform covers the use cases that were set as the main target. Nevertheless, some requisites needed for the proper working of the platform have been specified. As the project is aimed to be grown, some ideas that could not be added to this beta have been explained in order not to be missed for future development. Finally, some annexes containing important configuration issues for the platform have been added after proper explanation, as well as an installation guide that will let a new developer get the project ready. In addition to this document some other files related to the project are provided: - Javadoc. The Javadoc containing the information of every Java class created is necessary for a better understanding of the source code. - database_model.mwb. This file contains the model of the database for MySQL Workbench. This model allows, among other things, generate the MySQL script for the creation of the tables. - ScheduleManager.war. The WAR file that will allow loading the developed application into Tomcat Server without using NetBeans. - ScheduleManager.zip. The source code exported from NetBeans project containing all Java packages, JSPs, Javascript files and CSS files that are part of the platform. - config.properties. The configuration file to properly get the names and credentials to use the database, also explained in Annex II. Example of config.properties file. - db_init_script.sql. The SQL query to initiate the database explained in Annex III. SQL statements for MySQL initialization. RESUMEN. Este proyecto tiene como punto de partida la necesidad de evolución de una herramienta web existente. El propósito principal del proyecto durante su desarrollo se ha centrado en establecer las bases de una completamente nueva plataforma que reemplazará a la existente. Para lograr esto, ha sido necesario realizar una profunda inspección en las tecnologías web existentes: un servidor web y una base de datos SQL debían ser elegidos. Aunque existen muchas alternativas, la tecnología Java ha resultado ser elegida debido a la gran comunidad de desarrolladores que tiene detrás, además de la facilidad que proporciona este lenguaje a la hora de modelarlo usando diagramas UML. Tampoco hay que olvidar que es una tecnología de uso libre de licencia. Apache Tomcat es el servidor de código libre que permite emplear Java Servlets y JSPs para hacer uso de la tecnología de Java. Respecto a la base de datos SQL, el servidor más popular de código libre es MySQL, y cuenta también con una gran comunidad detrás y buenas herramientas de modelado, creación y gestión de la bases de datos. JDBC es el driver que va a permitir comunicar las aplicaciones Java con MySQL. Tras elegir las tecnologías que formarían parte de esta nueva plataforma, el proceso de desarrollo tiene comienzo. Tras una extensa explicación de la instalación del entorno de desarrollo, se han usado diagramas de caso de UML para establecer cuáles son los objetivos principales de la plataforma; los diagramas de clases nos permiten realizar una organización del código java desarrollado de modo que sean fácilmente entendibles las relaciones entre las diferentes clases. La arquitectura de la plataforma queda definida a través de diagramas de despliegue. Por último, diagramas EER van a definir las relaciones entre las tablas creadas en la base de datos. Aparte de estos diagramas, algunos detalles de implementación se van a justificar para tener una mejor comprensión del código desarrollado. Diagramas de secuencia ayudarán en estas explicaciones. Una vez que toda la plataforma haya quedad debidamente definida y desarrollada, se va a realizar una demostración de la misma: se demostrará cómo los objetivos generales han sido alcanzados con el desarrollo actual del proyecto. No obstante, algunos requisitos han sido aclarados para que la plataforma trabaje adecuadamente. Como la intención del proyecto es crecer (no es una versión final), algunas ideas que se han podido llevar acabo han quedado descritas de manera que no se pierdan. Por último, algunos anexos que contienen información importante acerca de la plataforma se han añadido tras la correspondiente explicación de su utilidad, así como una guía de instalación que va a permitir a un nuevo desarrollador tener el proyecto preparado. Junto a este documento, ficheros conteniendo el proyecto desarrollado quedan adjuntos. Estos ficheros son: - Documentación Javadoc. Contiene la información de las clases Java que han sido creadas. - database_model.mwb. Este fichero contiene el modelo de la base de datos para MySQL Workbench. Esto permite, entre otras cosas, generar el script de iniciación de la base de datos para la creación de las tablas. - ScheduleManager.war. El fichero WAR que permite desplegar la plataforma en un servidor Apache Tomcat. - ScheduleManager.zip. El código fuente exportado directamente del proyecto de Netbeans. Contiene todos los paquetes de Java generados, ficheros JSPs, Javascript y CSS que forman parte de la plataforma. - config.properties. Ejemplo del fichero de configuración que permite obtener los nombres de la base de datos - db_init_script.sql. Las consultas SQL necesarias para la creación de la base de datos.
Resumo:
The plant-signaling molecules salicylic acid (SA) and jasmonic acid (JA) play an important role in induced disease resistance pathways. Cross-talk between SA- and JA-dependent pathways can result in inhibition of JA-mediated defense responses. We investigated possible antagonistic interactions between the SA-dependent systemic acquired resistance (SAR) pathway, which is induced upon pathogen infection, and the JA-dependent induced systemic resistance (ISR) pathway, which is triggered by nonpathogenic Pseudomonas rhizobacteria. In Arabidopsis thaliana, SAR and ISR are effective against a broad spectrum of pathogens, including the foliar pathogen Pseudomonas syringae pv. tomato (Pst). Simultaneous activation of SAR and ISR resulted in an additive effect on the level of induced protection against Pst. In Arabidopsis genotypes that are blocked in either SAR or ISR, this additive effect was not evident. Moreover, induction of ISR did not affect the expression of the SAR marker gene PR-1 in plants expressing SAR. Together, these observations demonstrate that the SAR and the ISR pathway are compatible and that there is no significant cross-talk between these pathways. SAR and ISR both require the key regulatory protein NPR1. Plants expressing both types of induced resistance did not show elevated Npr1 transcript levels, indicating that the constitutive level of NPR1 is sufficient to facilitate simultaneous expression of SAR and ISR. These results suggest that the enhanced level of protection is established through parallel activation of complementary, NPR1-dependent defense responses that are both active against Pst. Therefore, combining SAR and ISR provides an attractive tool for the improvement of disease control.
Resumo:
Since 2008, international speculation about the viability of Kim Jong-Il's leadership in North Korea has been at the forefront of diplomatic discussions. North Korea is known to be a secretive state where human rights violations abound. This paper discusses the history of leadership and government in North Korea since World War II, the current human rights situation in the country, the role of China, and potential successors to Kim Jong-Il. The ramifications of impending regime change are discussed in terms of North Korea's human rights issues and economic problems. While current efforts at diplomacy have proved ineffective, the need for concerned nations, intergovernmental organizations, and non-governmental organizations to be prepared to engage North Korea after Kim Jong-Il is imperative.