ࡱ> ` Dbjbjss By<|,8888pt4 ,PN$(9A RDgiiiiii$h CyCyCyNۚۚۚCylg˚CygۚۚD ͟Q(8&+<;`P   L hMZ el$rhMZMZMZaXMZMZMZPCyCyCyCy,Dppq$n,pp,,, World Meteorological Organization Intergovernmental Oceanographic Commission    Joint WMO-IOC Technical Commission for Oceanography and Marine Meteorology Sixth Session of the JCOMM Management Committee (MAN) Paris, 3-6 December 2007 DATA MANAGEMENT PA issues, plan of action and deliverables (Agenda Item 3.1 (3))) Submitted by DMPA Coordinator, Bob Keeley Summary: This report presents summary information on major JCOMM DMPA activities since MAN-V Action: The Management Committee is invited to note the information and comment as appropriate Appendices: A JCOMM Data Management Plan B Implementation Plan for the JCOMM Data Management Plan JCOMM Data Management Programme Area Issues, Plan of Action and Deliverables 1. Meetings The following JCOMM DMPA related meetings were held since MAN-V: Second Session of the Data Management Coordination Group, Geneva, Switzerland, 10-12 October 2006 (DMCG-II) Second meeting of the Expert Team on Marine Climatology, Geneva, Switzerland, 26-27 March 2007 (ETMC-II) Also the 19th session of the IOC Committee on the International Oceanographic Data and Information Exchange, was held in Trieste, Italy, 12-16 March 2007 (IODE-XIX). 2. DMCG Activities A meeting of DMCG is planned for March, 2008 to review progress, emphasize those activities to be completed by JCOMM-III and to plan for activities to be recommended to JCOMM-III. A Data Management Plan was drafted, taking into account the IOC Strategic Plan for Oceanographic Data and Information Management. It was circulated for comments and revisions made such that it is ready for broad distribution. The document is found in annex 1. A preliminary implementation plan based on the DM Plan has been drafted. This plan encompasses all of the work currently undertaken by DMPA as well as projections of future work. A draft version is attached in annex 2. It is expected that the strategy and the implementation plan will be recommended to JCOMM-III. Interaction between ETMC and ETDMP is still limited largely because of the differences in focus. Some crossovers have been achieved with the inclusion of some trial data sets (MCSS) under the purview of ETMC being included in the development of the end-to-end data system (E2E) development of ETDMP. In addition, there have been some ETMC activities to include more direct connections to oceanographic programs (sea ice, I-COADS, extreme waves). Furthering this interaction needs continuing work. DMPA has been slow to develop a web presence. This is partly due to waiting for resolution of differences in JCOMM main sites (at WMO and IOC), but predominantly because of work load. In spite of this, the work of DMPA has been represented at a number of meetings through member's attendance. DMPA continues its connections to ICG through participation of Mr. Thomas (Australia). Members have attended meetings on WIS, and various WMO groups (WIS, ETDRC), European meetings of SeaDataNet, IOOS activities in the U.S. (though this has been quiet of late), and in national fora in which members of DMPA contribute in the data collection and management activities. In addition, to improve links between other PAs and DMPA, the chair has attended both OPCG and SPCG meetings. This latter activity has spawned discussions and some work on the development of an extreme wave database. We are expecting to make progress on this site for JCOMM-III, but work will continue after as well. Cooperation with IODE continues to develop. The chair of DMCG is now formally an IODE Officer (a member of the executive) and the chair of IODE is a formal member of the DMCG. Collaboration is also developing through JCOMM contributions to the drafting of the IOC Data Strategy and through joint training activities at the IODE Project Office (DBCP and E2E training sessions). IODE and DMCG are collaborating on the development of an ISO metadata profile for ocean data and cooperating with similar developments of the IPET-MI group in WMO. This close cooperation will continue on and through JCOMM-III. The development of standards for QC and other matters was being taken up through the hosting of a joint IODE/JCOMM Standards Forum. This is scheduled for the last week of January 2008 to be held in the IODE Project Office with funding provided by the United States. On the agenda are discussions towards agreeing on standards for QC of a number of ocean variables, on standardized code lists (variable names, ships, instruments, etc.) and ontologies. Also included is the discussion of the Marine Community Profile and the profile for atmospheric data, both based on ISO 19115. Of crucial importance will be a decision on how the wider community will be informed of, and contribute to broader discussions of the agreement reached at this meeting and a means to continue the development of these and other standards. Discussions will be held on how best to take advantage of joint ISO-WMO Standards developments. Standards development is an ongoing activity and we will want a member of DMPA to be targeted to lead this. The Meta-T Pilot Project is progressing, though slowly (workload of the chair became an issue so another individual has agreed to co-chair). This group has had active discussions on what information is required to travel with the data, and what is relatively static and so can be housed and referenced separately. Their work crosses over into the ODAS developments (a database of instrument characteristics) being hosted in China and BUFR templates, since it is through these templates that the information will be transmitted with the data. The ODAS database will take over the information maintenance formerly managed in the On-line Information Service Bulletin on non-drifting ODAS operated by ISDM (Canada). There are active email discussions between members of OPA and DMPA, the WMO secretariat and input from the ET Data Representation and Codes (a WMO committee). More information is provided below. DMCG has undertaken a number of related activities to modernize the transmission of data from platforms at sea to use table driven code forms. First, it was necessary to have representation on the WMO ET-DRC since they are responsible for recommending changes to table driven code forms. Hester Viola of the JCOMMOPS accepted to be the DMCG representative and attended the last meeting of this group on our behalf. Next, BUFR templates from the JCOMM groups managing VOS, surface drifters, moored platforms, Argo floats, and other ocean profilers have been received by an established task team of DMCG. Work has begun to identify the common components and an initial proposal was drafted to standardize content. This is progressing in combination with the Meta-T and ODAS discussions. Work is planned, though not yet done, to use a second BUFR Master Table developed some years ago as a way to easily include not only the biological and chemical measurements important to groups such as coastal GOOS, but also the vital information on measurement techniques that must be used to correctly interpret these kind of measurements. We hope to have stable and approved templates for most or all of the above kinds of data by JCOMM-III, but maintenance of codes is an ongoing task. There have been limited activities of DMPA with the IODE Project Office with regards to training materials. The primary focus is on preparing the appropriate material. In this respect certain IODE manuals and JCOMM (formerly IGOSS) material is being updated jointly and will serve as reference material in OceanTeacher. This is undertaken as well in conjunction with a WMO lead review of the list of quality related JCOMM publications and proposed addition of information. Results from the planned Standards Forum will be provided. In addition, an activity to develop documentation (a cookbook with recipes) of how researchers at the national level can contribute to JCOMM data collection activities is underway. This exists as an outline and sample text that discusses in very practical terms what is involved and who to contact. Authors from IODE and JCOMM PAs for the various sections are being solicited to complete this text. An initial version of this particular document is expected to be available for JCOMM-III. DMCG-II established an ad hoc working group on Capacity Building tasked to prepare guidance on a JCOMM CB Implementation plan and to prepare a JCOMM Strategic Plan, taking into consideration, inter alia (i) the JCOMM CB structure, as adopted by JCOMM-II; (ii) the interaction of the cross-cutting team on CB with the Pas, as described in the ToRs of the JCOMM CB Rapporteurs, adopted by JCOMM-II; (iii) the need for interaction between the JCOMM, WMO and IOC CB activities; (iv) the need for a mechanism and guidelines to receive, review and adopt CB proposals; and (v) the need for a mechanism and guidelines to review and evaluate JCOMM CB activities. The report was to be completed within three months for MAN review, and to finalize within six months). This target was not met, but the draft has been completed now and is available for discussion at the MAN-VI meeting. DMCG noted that the ETDMP had a membership that was working exclusively on E2E/WIS technical issues. The DMCG would like to see a broader scope for this ET, particularly to assist in helping to converge the diverse data systems in place in JCOMM. The chairs of the DMCG and ETDMP intend to develop a workplan for JCOMM-III that will reflect broader interests. 3. META-T Activities The development of the Water Temperature Metadata Pilot Project (META-T PP,  HYPERLINK "http://marinemetadata.org/meta-t" http://marinemetadata.org/meta-t) is progressing slowly. The Pilot Project has proposed three categories for the instrumental metadata from concerned types of platforms 1) real-time with observations (push); 2) real-time via metadata servers (pull), and 3) delayed mode, as well as the mechanisms to make the SST and/or temperature profile metadata available in real time. NOAA/NDBC, USA, and NMDIS, China, have offered to develop and run mirrored metadata servers for category 2 metadata. Specific data streams have been considered (e.g. drifting buoys, ships, floats, etc.) and the categorization of related metadata types initiated. Good progress was made regarding the VOS data stream and the list of category 1 metadata for the VOS template is nearly completed. META-T is now in a position to make recommendations to the SOT Task Team on codes. The META-T work plan is now as follows: Obtaining agreement regarding the list of metadata required for the VOS BUFR template Submitting the list to the SOT Task Team on Codes Selecting another project to develop another list of metadata regarding another type of platform (i.e. another data stream, e.g. buoys, floats, OceanSITES, tide gauges, ODAS) Set up the META-T servers at both the NMDIS and NOAA/NDBC 3.3 Specific data streams have been considered (e.g. drifting buoys, ships, floats, etc.) and META-T in order to take the META-T requirements for category 1 metadata into account when defining requirements for the BUFR templates for buoy data. 3.4 NDBC, USA and NMDIS, China are working to agree on the communication between the two centres for mirroring the metadata servers (category 1 and 2 metadata). 3.5 A second META-T workshop is being proposed to be held in conjunction with CLIMAR-III. We intend to present results and recommendations based on this work to JCOMM-III. ETMC Activities ETMC agreed to pursue the development of an Extreme Wave Database with recommendations made at ETWS-II. The ETMC invited its Members to seek National contributions to the database for both in situ and satellite data once established, and asked the Secretariat to draft a recommendation for JCOMM-III in this regard. In the meantime, some preliminary activities are being undertaken by members to estimate the volume of data, the sources that could contribute, and to identify the characteristics of the data to be included. ETMC followed the proposal from the DMCG to restructure the MCSS, endorsed the proposed TT-DMVOS (later also endorsed by SOT-IV), and proposed a new Task Team on Marine Meteorological and Oceanographic Climatological Summaries (TT-MOCS). ETMC established an ad hoc TT to define the TOR of the TT-MOCS (TOR to be finalized soon). It was agreed that in addition to the Minimum Quality Control Standards (MQCS) the marine meteorological community should work toward an internationally agreed Higher-level of Quality Control (HQC). It tasked the TT-MOCS to look into this. Work is progressing on a formal proposal to JCOMM-III for a version IV of IMMT format, and a version VI of MQCS. ETMC agreed that a proposal by the TT-DMVOS for utilization and further development of IMMA should be finalized by CLIMAR-III and then circulated through the ETMC for formal agreement. The format will then be either proposed to JCOMM-III for adoption and inclusion in the Manual on and the Guide to Marine Meteorological Services or published as a JCOMM Technical Report. ETMC proposed that the SOT conduct an intercomparison survey of e-logbooks. The proposal was later endorsed by the SOT-IV who asked its Task Team on Instrument Standards to proceed with the intercomparison. There is concern about the plan for ships call sign masking of VOS delayed mode data and ETMC recommended to SOT that such data should not be masked. The ETMC stressed that access to ODAS metadata was essential for marine climatology. It is encouraging the implementation panels under JCOMM or its associated programmes as well as WMO and IOC Members/Member States to augment their contributions to ensure the required metadata, both historical and operational, be submitted through the existing systems, or should assist in the development of new systems. The Team agreed to propose a recommendation for adoption by JCOMM-III in this regard. ETMC has now established links with the CCl and with other JCOMM groups (e.g. ETWS, ETSI, SOT, DBCP). It was agreed to continue to investigate the development of marine indices in cooperation with the JCOMM Services Programme Area and its Expert Teams, initially through the proposed TT-MOCS, with the aim of promoting some of the indices (e.g. wind waves, sea-ice) at the forthcoming CLIMAR-III meeting. ETMC noted that changes were required to the Manual on Marine Meteorological Services (WMO-No. 558) and the Guide to Marine Meteorological Services (WMO-No. 471). It is expected that additional changes would be proposed by the TT-DMVOS and the future TT-MOCS by the time of CLIMAR-III, and that all required changes should eventually be compiled in a consolidated proposal to be endorsed by the ETMC, and eventually submitted to JCOMM-III for approval. Revisions to the ETMC ToR should be proposed to JCOMM-III, in light of the new TT-DMVOS and TT-MOCS Task Teams and the restructuring of the MCSS. ETMC members were invited to provide comments about the ToR to its Chairperson, who was tasked, in liaison with the Secretariat and the TT Chairpersons to draft revised ToR for the ETMC. The Third JCOMM Workshop on Advances in Marine Climatology (CLIMAR-III) is planned in Gdynia, Poland, 6-9 May 2008. Major goals of the workshop are (i) to review ongoing developments in the flow and standardization of marine (meteorological and oceanographic) data and metadata under JCOMM, (ii) to foster and coordinate the development of marine (meteorological and oceanographic) climate data and products, including ICOADS, and (iii) to seek and compile appropriate contributions for a second revision of the JCOMM TR No. 13. Announcement has been issued and a web site established ( HYPERLINK "http://icoads.noaa.gov/climar3/" http://icoads.noaa.gov/climar3/). The deadline for submitting abstracts and registering have been extended to 7 December 2007. Six Sessions are being planned: Session I: Characteristics of Observational Data. Characteristics of the data available from marine observing platforms (VOS, Research Vessels, buoys, ODAS, satellites). Session II: Data Management (data flow, best practices, historical and contemporary data and metadata rescue, and the status of and plans for ICOADS). Session III: Product Development Methodologies (climate products, quality control and data quality assessments, parameterizations). Session IV: New Climate Products. New marine and oceanographic climate products. Session V: Observation-based Analyses of Climate Variability and Change (applications of data for climate research, including indices, variability, and global change). Session VI: Initialization and Assessment of Climate Models (applications of data for climate models, including reanalyses, how data are used to assess and improve models, and vice versa, and aspects of climate prediction). 5. ETDMP Activities The ET-DMP has focused on the development and testing of end-to-end data management technology (E2E Technology). The goals of this technology are (i) to integrate the non-homogenous real-time and delayed-mode local data systems into a unified distributed marine data system that will provide transparent exchange between the local data systems, and (ii) to provide end-user access to any data or information generated by the systems. The E2E Technology is now a WMO Information System (WIS) prototype component, constituting a WIS Data Collection and Production Centre (DCPC), and is currently based at the IOC Project Office for IODE in Oostende. To expand the reach of the prototype, a presentation demonstrating the technology was made at the recent IODE meeting. In addition, documents were prepared and distributed that described a checklist of what activities were necessary to participate. Other documentation of the project is under review to increase the level of understanding of the project. Further to this goal, a training session was held at the IODE Project Office in Oct 2007 to encourage greater participation. The E2E technology has also been accepted by IODE as the basis for their Ocean Data Portal development. By linking these developments (JCOMM, WIS, IODE) we are encouraging a single window into the marine meteorology and oceanography domain that also serves to contribute to GEOSS. We will recommend this collaboration with WIS continue through JCOMM-III. ANNEX I JCOMM Data Management Plan Prepared by the members of the Data Management Coordination Group August, 2007 Table of Contents  TOC \o "1-3" \h \z \u  HYPERLINK \l "_Toc175549315" JCOMM Data Management Plan  PAGEREF _Toc175549315 \h 3  HYPERLINK \l "_Toc175549316" 1. The Vision and Objectives of JCOMM  PAGEREF _Toc175549316 \h 3  HYPERLINK \l "_Toc175549317" 2. Purpose and Scope of this Plan  PAGEREF _Toc175549317 \h 3  HYPERLINK \l "_Toc175549318" 3. Organization of the Plan  PAGEREF _Toc175549318 \h 3  HYPERLINK \l "_Toc175549319" 4. Data and Information Exchange  PAGEREF _Toc175549319 \h 3  HYPERLINK \l "_Toc175549320" 4.1 From Collectors to the Shore  PAGEREF _Toc175549320 \h 3  HYPERLINK \l "_Toc175549321" 4.2 Using the GTS  PAGEREF _Toc175549321 \h 3  HYPERLINK \l "_Toc175549322" 4.3 Using the Internet  PAGEREF _Toc175549322 \h 3  HYPERLINK \l "_Toc175549323" 4.3.1 netCDF  PAGEREF _Toc175549323 \h 3  HYPERLINK \l "_Toc175549324" 4.3.2 xml  PAGEREF _Toc175549324 \h 3  HYPERLINK \l "_Toc175549325" 4.3.3 Other Formats and Data Structures  PAGEREF _Toc175549325 \h 3  HYPERLINK \l "_Toc175549326" 5. Data Processing  PAGEREF _Toc175549326 \h 3  HYPERLINK \l "_Toc175549327" 5.1 Data Versions  PAGEREF _Toc175549327 \h 3  HYPERLINK \l "_Toc175549328" 5.2 Data Quality  PAGEREF _Toc175549328 \h 3  HYPERLINK \l "_Toc175549329" 5.3 Duplicates  PAGEREF _Toc175549329 \h 3  HYPERLINK \l "_Toc175549330" 5.4 Contents  PAGEREF _Toc175549330 \h 3  HYPERLINK \l "_Toc175549331" 5.5 Processing history  PAGEREF _Toc175549331 \h 3  HYPERLINK \l "_Toc175549332" 5.6 Metadata  PAGEREF _Toc175549332 \h 3  HYPERLINK \l "_Toc175549333" 5.7 Model Data  PAGEREF _Toc175549333 \h 3  HYPERLINK \l "_Toc175549334" 5.8 SOCs and RNODCs  PAGEREF _Toc175549334 \h 3  HYPERLINK \l "_Toc175549335" 6. Access  PAGEREF _Toc175549335 \h 3  HYPERLINK \l "_Toc175549336" 6.1 Discovery  PAGEREF _Toc175549336 \h 3  HYPERLINK \l "_Toc175549337" 6.2 Browse  PAGEREF _Toc175549337 \h 3  HYPERLINK \l "_Toc175549338" 6.3 Data Delivery  PAGEREF _Toc175549338 \h 3  HYPERLINK \l "_Toc175549339" 6.4 Data Access Policies and Security  PAGEREF _Toc175549339 \h 3  HYPERLINK \l "_Toc175549340" 7. Coordination and Linkages  PAGEREF _Toc175549340 \h 3  HYPERLINK \l "_Toc175549341" 7.1 Within JCOMM Activities  PAGEREF _Toc175549341 \h 3  HYPERLINK \l "_Toc175549342" 7.2 With IODE Activities  PAGEREF _Toc175549342 \h 3  HYPERLINK \l "_Toc175549343" 7.3 With Other IOC Programmes  PAGEREF _Toc175549343 \h 3  HYPERLINK \l "_Toc175549344" 7.4 With WMO  PAGEREF _Toc175549344 \h 3  HYPERLINK \l "_Toc175549345" 7.5 With ICSU WDCs  PAGEREF _Toc175549345 \h 3  HYPERLINK \l "_Toc175549346" 7.6 With Other Programmes  PAGEREF _Toc175549346 \h 3  HYPERLINK \l "_Toc175549347" 8. Communications  PAGEREF _Toc175549347 \h 3  HYPERLINK \l "_Toc175549348" 9. Conclusion  PAGEREF _Toc175549348 \h 3  JCOMM Data Management Plan 1. The Vision and Objectives of JCOMM The stated vision of the Joint WMO-IOC Technical Commission for Oceanography and Marine Meteorology (JCOMM) is to coordinate, regulate and facilitate, at the global level, a fully integrated marine observing, data management and services system that uses state-of-the-art technologies and capabilities; is responsive to the evolving needs of all users of marine data and products; and includes an outreach programme to enhance the national capacity of all maritime countries. JCOMM aims to maximize the benefits for its Members/Member States in the projects, programmes and activities that it undertakes in their interest and that of the global community in general. For information about JCOMM see  HYPERLINK "http://www.jcomm.info" http://www.jcomm.info. As found in the JCOMM Strategy document,  HYPERLINK "http://www.wmo.ch/pages/prog/amp/mmop/documents/JCOMM-Strategy-v1.pdf" http://www.wmo.ch/pages/prog/amp/mmop/documents/JCOMM-Strategy-v1.pdf, the long-term objectives of JCOMM are: To enhance the provision of marine meteorological and oceanographic services in support of the safety of navigation and safe operations at sea; contribute to risk management for ocean-based economic, commercial and industrial activities; contribute to the prevention and control of marine pollution, sustainable development of the marine environment, coastal area management and recreational activities, and in support of the safety of coastal habitation and activities; and to coordinate and enhance the provision of the data, information, products and services required to support climate research and the detection and prediction of climate variability; To coordinate the enhancement and long-term maintenance of an integrated global marine meteorological and oceanographic observing and data management system, containing both in situ and remote sensing components and including data communication facilities, as part of the Global Ocean Observing System (GOOS) and the World Weather Watch (WWW), and in support of the World Climate Programme (WCP), the World Climate Research Programme (WCRP), the Global Climate Observing System (GCOS), and other major WMO and IOC programmes; To coordinate and regulate the maintenance and expansion of a comprehensive database of marine meteorological, oceanographic and sea ice data, in support of marine services, operational meteorology and oceanography and the WCP; To manage the evolution of an effective and efficient programme through the selective incorporation of advances in meteorological and oceanographic science and technology; and to work to ensure that all countries have the capacity to benefit from and contribute to these advances, and to the work of JCOMM in general. 2. Purpose and Scope of this Plan JCOMM was established by the World Meteorological Organization (WMO) and UNESCOs Intergovernmental Oceanographic Commission (IOC) in 1999 to be their major advisory body on all technical aspects of operational marine meteorology and oceanography. Prior to this, marine meteorological and oceanographic observations, data management and service provision programmes were internationally coordinated by two separate bodies: IOC working jointly with WMO through the Committee for the Integrated Global Ocean Services System (IGOSS), and WMO through its Commission for Marine Meteorology (CMM). IGOSS dealt with real-time oceanographic data (defined as data collected within the last 30 days) and managed physical oceanographic variables only hence the perception on the oceanographic side that JCOMM deals in real-time data only. On the meteorological side, CMMs work covered the complete time frame from real-time to delayed mode (data not distributed in real-time and usually of higher resolution and quality) and built and maintained archives of marine data. This current JCOMM Data Management Plan (DMPlan) must address issues relevant to both real-time data handling as well as managing delayed mode data in archives. The present structure of JCOMM (in 2007) has three Programme Areas (PAs), one for Operations (OPA), one for Services (SPA) and one for Data Management (DMPA). The groups in the OPA and SPA are focused on activities supporting a type of data (or sometimes an observing technique), or on a service such as safety or emergency support. Each of these has its own history of managing data and information prior to its incorporation into JCOMM. When JCOMM was formed a decision had to be made about how to organize the cross cutting activity of data management. The choice was made to place data management in a separate PA to recognize that managing the data and information of JCOMM is an important activity equal to acquiring and delivering data and services. The potential weakness is that the activities of the DMPA may not be strongly linked to the day-to-day data management activities in the various groups of the other PAs. The challenge to the DMPA is to work within the requirements of the activities within the OPA and SPA and still achieve the broad goals of JCOMM. This plan will adopt an approach that looks for commonalities across all of these systems and exploits these to improve interoperability. A main goal of this DMPlan, therefore, must be to explain how data management can be conducted under the present structure to promote the long-term objectives of JCOMM. JCOMM deals in a variety of data within the broad domains of oceanography and marine meteorology. Both meteorology and physical oceanography have a strong history of data exchange and it is these types of data that are normally considered part of JCOMM activities. Biological or chemical variables have a history of data exchange within oceanography but only in delayed mode and only for a limited number of variables. Only recently have these kinds of data been exchanged in real-time, such as in the International Ocean Carbon Coordination Project. The coastal module of GOOS has defined common variables to be exchanged and more than half of these are outside of the physical oceanographic domain. JCOMM must position itself to handle this broader range of variables. New observing technologies are being developed at a fast pace. In addition to improvements in measuring traditional physical oceanographic variables, such as temperature and salinity, there are sensors being built that can provide immediate and reliable measurements of chemical and biological components in the ocean. These data can be transmitted instantly through satellite systems. New offshore cabled networks allow for the streaming of data of all kinds from television images, acoustics or more conventional oceanographic and meteorological observations with 2-way communication to the sensors. Open ocean moorings with both meteorological and oceanographic measurements available immediately are being deployed. All of these data will be challenging for JCOMM to both coordinate and manage. Computer modeling of the atmosphere has been an important activity for many years. In the last few years, modeling of the ocean has increased substantially. Now, ocean and atmospheric models are starting to be fully coupled. Ice modeling is being injected into these coupled models and there are some developments to include biological and chemical components in the ocean as well. Model results are valuable for forecasting and in hindcast studies as well. They permit us to fill in data gaps and to predict conditions where data are sparse. When these results are reformulated as products they can become particularly useful in decision making, disaster mitigation and a host of other uses. Models can be operated in research, operational or reanalysis mode. Models run for research purposes are constantly being checked, results verified against observations, model characteristics altered and so on until such time as the newer version is determined to be an improvement on an existing operational model. Results from research model runs are of use to the research community primarily. In contrast, the characteristics of operational, and to an even larger extent reanalysis, models are held stable. Results from these models are the basis for many products because they use the physics in the models to fill in information in oceanic and atmospheric areas where observations are not available. These results are valuable to save and can be used in a similar way as are historical observations. Satellite observations are also of interest to JCOMM. Satellites provide the synoptic and broad scale views that are unattainable from in-situ observing systems. They are a complement to the in-situ systems in that they provide surface conditions on broad spatial scales at an instant of time. There is already a well developed international system for managing satellite data (see  HYPERLINK "http://www.ceos.org/" http://www.ceos.org/ , the home page of the Committee on Earth Observation Satellites, CEOS). The DMPlan needs to take into consideration the level of interoperability that is required with CEOS and how this can be attained. Metadata must also be considered as an important component of JCOMM. Metadata is a term used to cover a wide range of information. It may be information that describes the contents of archives (such as what data they contain, over what time and space scales) down to detailed information about characteristics of the instrumentation, placement of sensors, or characteristics of the models. No common terminology has developed to talk about these different kinds of metadata, so this document will provide examples of the kind of information considered whenever the term is used. Metadata are important for a number of uses. Just as the scope of metadata is wide, so its uses are broad. For example, information about the contents of archives is used in cataloguing systems so that potential users can locate data of interest. Information about instrument characteristics or sampling schemes is important in comparing measurements from different instruments to ensure that systematic differences are taken into consideration. The DMPA is not alone in addressing issues of managing oceanographic and meteorological data in the international arena. On the oceanographic side, the Intergovernmental Data and Information Exchange (IODE,  HYPERLINK "http://www.iode.org/" http://www.iode.org/ ) committee of IOC has operated for many years managing many different kinds of data including types common with JCOMM. The difference has been that IODE has mostly concentrated on data that arrive in the data system with significant time delays, some that may be up to years while the management of the real-time data was left to IGOSS. IODE is a close partner in managing the oceanographic data and is a co-sponsor of many of the data management activities of relevance to JCOMM. A more recent initiative of WMO, thus far advanced largely through its Commission for Basic Systems (CBS), is its WMO Information System, WIS (see  HYPERLINK "http://www.wmo.ch/pages/prog/www/WIS-Web/home.html" http://www.wmo.ch/pages/prog/www/WIS-Web/home.html).This is an overarching approach and a single coordinated global infrastructure for the collection, distribution, retrieval of, and access to data and informationof all WMO and related programmes. JCOMM, as a technical commission being co-sponsored by WMO, is a contributor to WIS. Both oceanographic and meteorological data contribute to the holdings within the World Data Center (WDC) system (see  HYPERLINK "http://www.ngdc.noaa.gov/wdc/wdcmain.html" http://www.ngdc.noaa.gov/wdc/wdcmain.html ). It is expected that the WDC system will ultimately archive all of the data collected and managed by JCOMM. The JCOMM data management activities, therefore, need to provide data and information to the WDCs and work with them to build a complete, global data system. The creation of the Global Climate Observing System (GCOS) and all of its components views JCOMM as an important contributor. The GCOS Implementation Plan (GCOS-92) (see  HYPERLINK "http://www.wmo.int/pages/prog/gcos/Publications/gcos-92_GIP.pdf" http://www.wmo.int/pages/prog/gcos/Publications/gcos-92_GIP.pdf ) cites 21 specific actions requiring the support of JCOMM as an Agent for Implementation. Of these, some relate directly to the data systems. The DMPlan must provide the direction that will ensure these expectations are met. Details of how JCOMM should link into these various programmes are provided later in this document. The initial sections of this plan discuss what activities JCOMM should undertake to ensure that the data collected under its Programme Areas are well coordinated and managed. Finally, it is obvious that the data management component of JCOMM is broad and has to make many connections both within and outside of the two parent organizations of WMO and IOC. This DMPlan provides the broad outlines and recommendations by which the DMPA will help attain the vision of JCOMM. This plan will not provide the details of how the recommendations will be met; rather, this is the subject of an implementation plan that must be built from the agreed plan. As technology advances, and as the implementation develops, there will be changes in emphasis or new capabilities not anticipated by this DMPlan. 3. Organization of the Plan An examination of the long-term objectives of JCOMM and expectations for action by JCOMM, such as from the GCOS-IP, require that there exists a functioning system of reliable and regular observations at sea. the data and information come to processing centres in a timely way. notifications of hazardous conditions are issued to mariners or nations in time to take action to avoid potential harm. data collected by JCOMM activities be maintained over many years such that climate variability, trends, and prediction can be studied and advanced. information be maintained about the observing practices so that older data may be compared to more recent data. there be standardization in such areas as data formats, content, naming conventions, processing procedures, etc. to ensure interoperability. data version control be addressed. data management activities and experiences are made available equally to all WMO-IOC Member-Member States. To organize the discussion, this document will divide the tasks into main areas and make recommendations in each. The major data management themes that are used are: Data and Information Exchange includes issues of transporting data to and between archives or processing centres. Data Processing includes issues of data quality assessment, version control, content, etc. Access includes issues of finding, browsing, and moving data and information to users. Coordination and Linkages includes issues of how activities in the different PAs need to link together as well as the links between JCOMM and other organizations. Communications including the dissemination of information about JCOMM data management, training materials, performance measures, reports, etc. Interoperability is a central issue for JCOMM because of the many contributors to data collection, processing and distribution. This is an issue that cuts across all of the sections of the DMPlan. A heavy emphasis is evident here on the adoption of standardized procedures in all areas of data management. It is only through the adoption of standard practices that the required level of interoperability will be attained. 4. Data and Information Exchange This section deals with the various aspects of moving the observational data collected at sea to the appropriate archive or data distribution centres. Most of the data coming ashore from instruments do so in data structures driven either by the instrument manufacturers or by telecommunications demands. Once ashore, the data are converted to formats used for data exchange in real-time (up to 30 days old for oceanographic data, a few hours old for meteorological data) or a less timely exchange referred to as delayed mode. Real-time data exchange normally uses the GTS (Global Telecommunications System) with relatively few and well controlled formats. In delayed mode, there are many formats and the communications channel is increasingly the Internet. 4.1 From Collectors to the Shore Operations at sea are strongly challenged by the size of the worlds oceans, by harsh conditions, by scarce power for instrumentation and by constrained communications capabilities. Because of these, measurements at sea are difficult to obtain and often are limited in geographic extent and to short periods of time. In moving data ashore (often via satellites), a premium is placed on compact data formats that squeeze the most information into the smallest message length. Consequently, the data streams that come ashore are strongly linked to the types of instruments used and so manifest a wide variety of data formats. Individual processing systems have been developed to manage these data streams. While there is some hope that limitations on communications bandwidth will ease in the near future, the trend is to make even more varied observations at sea. So, although bandwidth will increase, the quantity of measurements will also. Without the adoption of some standard for reporting from platforms at sea, there will continue to be a variety of data formats. Both WMO and IOC have sought for decades to standardize communications of data, largely in the context of reporting data over the GTS. An avenue that has not been widely explored is to use these same standards, or others, for reporting directly from the instruments at sea. Recommendation 4.1: JCOMM should encourage instrument manufacturers to standardize the formats of the data and information coming from instruments used at sea. 4.2 Using the GTS The GTS (see  HYPERLINK "http://www.wmo.ch/web/www/TEM/gts.html" http://www.wmo.ch/web/www/TEM/gts.html ), is one of the means of data exchange used by oceanographers and meteorologists. For WMO it is the transmission mechanism of choice for operational, time critical data exchange. This is still true in the development of the WMO Information System, WIS. Being co-sponsored by WMO, JCOMM will need to adopt this same view. On the GTS, the Traditional Alphanumeric Code forms (TACs) have strongly regulated formats and contents (e.g. FM-13 SHIP). This has been of advantage in that there is a commonly understood protocol for naming variables, for units of reporting and additional information to be sent with the observations. The capabilities and variety of the TACs are more developed for meteorological than for oceanographic data. However, it is increasingly the case that either new variables or new information about how existing variables are observed needs to be exchanged. The TACs are an older technology, with roots extending back to the International Synoptic Land Code agreed to in Rome in 1913. It is a technology that WIS is phasing out. Replacing the TACs are Table-Driven Codes (TDCs) such as the Binary Universal Form for the Representation of meteorological data, BUFR (see  HYPERLINK "http://www.wmo.ch/web/www/WMOCodes.html" http://www.wmo.ch/web/www/WMOCodes.html ). TDCs offer a flexible form that allows data to be structured within the exchange format in ways that are linked to the kind of data observed. As an example, a BUFR message is built using a set of carefully defined tables of variables and attributes, generally using only SI (International System of Units see  HYPERLINK "http://physics.nist.gov/cuu/Units/index.html" http://physics.nist.gov/cuu/Units/index.html ) units, with rules about how the information is structured into a well formed message. The BUFR tables show their heritage in that they are much more capable of describing meteorological variables than oceanographic ones. One of the complications of oceanographic data, which does not appear in meteorological data, is that oceanography spans a variety of disciplines. Whereas it is possible to draw the analogy between physical oceanographic variables and meteorological ones, oceanography also includes chemistry, geophysics and biology. The present structure of BUFR tables is not particularly well suited to handling data from other disciplines, nor the metadata that are crucial for correct interpretation of the observed values. There is also a character form of TDCs, in this case closely linked to BUFR, called CREX (Character form for the Representation and EXchange of data see the same link as for BUFR). The chief difference between CREX and BUFR is that a CREX message is in ASCII characters and so is directly readable by people and hence removes the software dependency of BUFR. WMO has expressed the requirement to move all of its GTS, and possibly other observational data exchanges to use TDCs. JCOMM must be a partner in this process. In the simplest case, JCOMM must actively work to build capability for exchanging data in TDCs, including BUFR. The work will entail such tasks as devising and validating appropriate BUFR templates that include and extend the information now sent in TACs. encouraging ocean and meteorological centres to develop capacity to both read and write TDCs. consideration of how TDCs may be used to acquire data from instruments and platforms at sea. Recommendation 4.2a: DMPA lead the development of the detailed plan to change GTS data reporting from TACs toTDCs. A number of years before JCOMM was formed, there was some activity to build another set of BUFR tables whose structure is better tuned to the requirements for all kinds of ocean (and some atmospheric) data. BUFR was designed with the capacity to handle a number of different tables, so this was simply exploiting an existing capability. This new set of tables was designated Master Table 10 (MT10) and met the requirements at the time for an alternate set of tables that BUFR could support. No ocean centres were capable of encoding or decoding BUFR data and so the use of these tables was not implemented. However, with encouragement from JCOMM to get both ocean and meteorological data reported in BUFR, MT10 should be revisited and evaluated against current needs. Recommendation 4.2b: The DMPA in association with the appropriate WMO committee should evaluate MT10 for its relevance to present needs. The advantage of BUFR, and other TDCs, is the set of tables (termed classes in BUFR) that designate variables and attributes, in a machine-readable form. These tables constitute the vocabulary of BUFR. While it is certainly advantageous in that the meanings are well defined, the construction of BUFR causes some unpleasant side effects. One such is that a BUFR variable is characterized by the number of bits used to express the value. The same variable, such as sea temperature, may have more than one BUFR variable assigned, since sea temperature can be recorded to 1, 2 or 3 decimal places. Each needs a different number of bits to express the value and so each gets a different BUFR designator. A second issue is that because the data are in binary, and different computer operating systems have different ways of handling binary data, different software routines are needed for the different operating systems. So, there are a number of versions of BUFR encoding and decoding software and this challenges them all to produce identical results. These shortcomings, along with the strengths of BUFR need to be considered in discussions of metadata and vocabularies described later. Recommendation 4.2c: Enhanced interaction between JCOMM and CBS or other appropriate WMO committees is needed to expand the scope of TDCs to more fully incorporate JCOMM considerations, including software reliability, human readability, and the archival and exchange of historical and delayed-mode data in its originally reported form. 4.3 Using the Internet Data are also exchanged using other telecommunication systems, notably the Internet. For these exchanges there is no standard for naming variables and attributes, no universally agreed structures or formats, no real order at all, beyond the broad constraints of standards such as the Hypertext Transfer Protocol (HTTP) and the File Transfer Protocol (FTP). Use of the Internet is very widespread and this lack of order makes the exchange of data a complicated process because every data provider must give detailed information on their formats, contents, processing steps, etc., and receivers need to build software capability to handle the wide variety from different data providers. 4.3.1 netCDF There are preferred practices that are starting to emerge for data exchange using the Internet. The use of netCDF ( see  HYPERLINK "http://www.unidata.ucar.edu/software/netcdf/" http://www.unidata.ucar.edu/software/netcdf/ ) for the exchange of in-situ ocean data is increasingly prevalent. Its use started in earnest during the World Ocean Circulation Experiment, WOCE, in the 1990s and is now a part of the Argo (see  HYPERLINK "http://wo.jcommops.org/cgi-bin/WebObjects/Argo" http://wo.jcommops.org/cgi-bin/WebObjects/Argo ), OceanSITES (see  HYPERLINK "http://www.oceansites.org/" http://www.oceansites.org/ ) and GOSUD (see  HYPERLINK "http://www.ifremer.fr/gosud/" http://www.ifremer.fr/gosud/ ) programs. Todays version of netCDF is most suitable for data that has some regularity in one or more of the horizontal, vertical or time coordinates, but it can be used when even this is lacking (Note that this limitation is being addressed in a new version to be issued soon). The weakness of netCDF is that there is no single standard for naming variables or attributes. There are common practices including the Climate and Forecast (CF - see  HYPERLINK "http://www.cgd.ucar.edu/cms/eaton/cf-metadata/" http://www.cgd.ucar.edu/cms/eaton/cf-metadata/ ) conventions, but the use of netCDF for data exchange would be greatly enhanced with the adoption of a standard vocabulary. Never-the-less, netCDF is in wide enough use that provision of data in this format should be considered by JCOMM. Recommendation 4.3.1a: JCOMM to support the widespread use of netCDF as a data exchange format. Recommendation 4.3.1b: JCOMM to encourage usage of the CF convention for variable naming in netCDF and stay informed of CF updates to meet JCOMM contributors' needs. Working with the groups that maintain and extend netCDF would be a useful activity for JCOMM. Another development that should be noted in this context is the planned convergence of netCDF with the Hierarchical Data Format (HDF see  HYPERLINK "http://www.hdfgroup.org/" http://www.hdfgroup.org/ ). Considering long-term archive requirements, it should be noted that formats such as netCDF and HDF, like BUFR, are extremely complex, and highly dependent on software. Recommendation 4.31c: JCOMM stay informed on netCDF maintenance and developments. 4.3.2 xml Xml is yet another way to structure data and information for exchange. To date its main use has been in exchanging low volume data, though perhaps at high frequency. It is a very popular structure because of its flexibility, its readability and the wide availability of software to parse messages and extract content. With the development of Service Oriented Architecture models, xml will only gain popularity. The flexibility of xml is also one of its weaknesses. The meaning of the xml tags must be understood by both the sender and receiver of the message. This means that each tag must be defined; in effect the vocabulary must be established between sender and receiver, before the messages are exchanged. Until this vocabulary is defined, this is no better a solution than using any other format with arbitrary names for variables. Still, the commercial acceptance of using xml and hence the broad availability of software makes this an attractive option to consider for both data and metadata. Recommendation 4.3.2a: DMPA monitor the development of xml and encourage appropriate use for the exchange of data and metadata. Recommendation 4.3.2b: DMPA encourage the development of vocabularies used in xml that are as close as possible to those used in other formats. 4.3.3 Other Formats and Data Structures Of course, netCDF is not the only format used for exchanging data on the Internet. Other data structures are in use, but there is no coordination between these formats and so no standards have developed. Still, JCOMM must recognize that netCDF is not the sole way that users will wish to exchange data and therefore must continue to keep abreast of formats used and developed that offer broad scale appeal. It will be necessary as well to create mappings from one set of naming and format conventions to another, but at least with fewer formats, the mapping process will be easier. This should include, for example, mapping of BUFR names to netCDF CF conventions. Recommendation 4.3.3a: JCOMM must recognize that other formats and data structures besides netCDF will have appeal and encourage activities that broaden their use and standardize their content. There is at present a distinction made between data that are exchanged in real-time and those exchanged in delayed mode. Typically the GTS and its suite of data formats are used for real-time, and a host of formats, netCDF being one, for exchange in delayed mode. This distinction is artificial in that it is only because of limiting bandwidth of communications channels that the full resolution data cannot be sent as soon as the observations are taken. Artificial or not, there are a wide variety of exchange formats for delayed mode data using whatever communications channels are available. For example, standardized alphanumeric International Maritime Meteorological (IMM) formats were introduced by WMO around 1951 for the exchange of delayed-mode (e.g., keyed logbook data) from Voluntary Observing Ships (VOS). These were upgraded in 1982 and continue to be upgraded and used in the Marine Climatological Summaries Scheme (MCSS) today. The most recent development in this area is the IMM Archive (IMMA) format, which is widely used by the research community to access VOS and many other marine data stored in the International Comprehensive Ocean-Atmosphere Data Set (ICOADS). Like the earlier IMM formats, IMMA is a relatively simple alphanumeric format, but with a more flexible and extensible design including a critical archive feature that permits attachment of the original (raw input) data. The delayed mode formats have operated outside of the more formalized system governing evolution of the TDCs and freezing the form of the TACs. While that system helps assure the rigid levels of standardization required for mature operational applications, even small format changes in the TDCs therefore can take some time to be implemented. In contrast, IMM (and some other delayed mode formats) can be modified relatively easily (e.g., by JCOMM without required cross-Commission agreement), and this flexibility can have important advantages, at least in the research arena, in that the formats can be more immediately responsive to new developments in technology, and in data and metadata management. Recommendation 4.3.3b: JCOMM work with partners to encourage the continuing evolution of exchange formats to more robust and stable forms, while at the same time assuring that sufficient flexibility and agility can be preserved for the archival of JCOMMs delayed mode data and metadata. 5. Data Processing Members of JCOMM maintain and support their own national archives. The strategies and resources (people, hardware, software) needed are driven by national requirements and funding. It is not worthwhile for JCOMM to try to dictate the details of how this archiving takes place. However, JCOMM can provide valuable coordination in recommending data management practices that standardize how data are handled and thereby improve the preservation of the data and its usability. This section discusses the processing functions that impact the fidelity of archived data. 5.1 Data Versions The raw observations coming from an instrument may be considered to be the first version of the data, and the highly processed data that are exchanged to be another version. There may be many versions representing the processing steps between these two and there may be other versions after data are available for exchange. Versions are generated by the calibrations applied to the data collected, by value adding processes such as quality control, by smoothing and filtering, etc. It is important to be able to distinguish between these versions especially after the versions have reached archives or are exchanged. In dealing with data versions, the satellite community speaks of levels of data. The levels are indicative of the amount of processing that the data have undergone. So, level 0 is assigned to the data as delivered directly from the instrument sensor, while level 3 are gridded data processed from a single type of sensor (one satellite sensor or one in-situ network). The conventions used in The Global Ocean Observing System (GOOS) Prospectus 1998 (see annex 4 of  HYPERLINK "http://ioc.unesco.org/oceanteacher/OceanTeacher2/01_GlobOcToday/06_OpOc/04_GOOS/Prospectus/contents.htm" http://ioc.unesco.org/oceanteacher/OceanTeacher2/01_GlobOcToday/06_OpOc/04_GOOS/Prospectus/contents.htm ) are based on the definitions used by the atmospheric research community since the Global Atmospheric Research Programme, GARP. These are very similar to those of the satellite community with level 3 being gridded products and level 4 being model results. There is no history of the use of such schemes in oceanography although this is likely to change very quickly with the development of operational oceanography and global modeling. But there are subtleties that are not expressed in these simple schemes that can have a strong impact on usage of the data. For example, for bandwidth or other reasons, the full resolution data coming from oceanographic sensors at sea are not immediately returned to shore and distributed, such as on the GTS. Instead the TACs provide a way to distribute a degraded copy (in both vertical resolution and in precision of measurement). These low resolution forms enter and reside in archives until the higher resolution forms arrive in delayed mode thus leading to the potential archiving of both resolutions. And though it should be relatively simple to recognize that these derive from the same observation, this is not always straightforward. The delayed mode data may have corrections to positions or times, or calibrations carried out on the original measurements. All of these change the content and make the matching of the quickly arriving, low resolution data to the more slowly arriving, corrected, high resolution form a difficult process. In recognition of this issue, a pilot project was initiated within the Ship Observation Team (SOT) in the OPA that uses a unique identifier attached to both the real-time and delayed mode versions of the same original data. The matching is then done through examining these identifiers, not through looking at any of the data or information about the data. The scheme has shown value in this use and should be considered as a candidate technology in addressing the versioning issue. Another subtlety is associated with the archiving of the data. It is common in both oceanography and marine meteorology archive centres to see the same data arrive more than once. The first time the data might arrive in real-time and in a lower resolution form as already described. The next time, the higher resolution or more complete delayed mode form arrives (e.g., VOS reports containing data and metadata fields in IMM format that cannot be represented in FM-13). After some work by scientists, errors in the data may be fixed, calibrations carried out and so on and the data are again sent to the archive centre. It may be that some years later, the same data are submitted yet again because whoever was responsible was not sure they submitted the data so they send it again to be sure, or some data that were formerly missing have been recovered and the data are resent. This can happen for complete collections or sometimes just for selected components. These all represent versions of the data. Recommendation 5.1: DMPA needs to consult JCOMM PAs to get a full description of the versioning issue, to develop a strategy to manage versions, and to implement the strategy. 5.2 Data Quality Assessing the quality of data is a complicated process that uses knowledge of oceanography and meteorology, and knowledge of the area and time in which the data are collected. The degree of scrutiny is dependent on the use of the data. Data collected and distributed in real-time, such as in model assimilation, must be handled rapidly and usually this means being checked by automated procedures. It is accepted that such procedures cannot bring to bear all of the knowledge that an experienced person would, but as long as the number and type of errors that pass through the procedures do not adversely affect the results, this is acceptable. Assessing the quality of delayed mode data often falls into the domain of scientists who have their own experience and tools they use. Because of the accepted constraints of moving data in real-time, it is easier to get agreement on standardized procedures for carrying out quality control for this exchange. Users accept that not all errors will be caught. Getting the same acceptance for standardized delayed mode procedures is more difficult. Often the problems are more difficult to detect and require a broader set of corroborating evidence. It is becoming increasingly common for ocean data to be reported or distributed with quality indicators attached. Processing centres add value to the original data by passing the data through test procedures and then using flags to indicate the quality of the data. These typically are placed on each observation. There are a number of places where standardization of practices would benefit users. Presently a large impediment to a user wishing to take advantage of the flags is that the test procedures are not well documented nor are the descriptions readily available. Moreover, there are so many different procedures applied in different ways, even if a user accepted the tests as valid, combining data from many sources would mean determining that all groups used functionally similar tests. A standard set of tests to be applied as a minimum set would greatly improve the process of exploiting flags set by different groups. This standard set would need to respect the differences between real-time and delayed mode data. Recommendation 5.2a: DMPA should encourage the development and wide spread implementation of a standard suite of data quality testing procedures. In the process of carrying out tests on observations, a decision must be made about how to report the results of the tests. There is wide agreement that flags will be used, but there is no agreement on what they will report. In one scheme, flags are used to indicate if an observation (or perhaps group of observations) passes or fails a test. The result is that a single observed value may have a collection of flags attached to it, one for each test performed. The advantage of this scheme is that there is no interpretation of the goodness of the data, simply a statement of success or failure of a test on an observation. Users are therefore able to decide for themselves which tests they consider appropriate and so take into consideration the test results when viewing the data. The disadvantage of the pass/fail flagging is that it does not help a user who does not have enough knowledge to decide the importance of this or that test failure. Another scheme for indicating data quality has been developed for them. In this scheme, the same suite of tests may be run as for the first, but depending on the results, a value judgment is made about whether the data are acceptable. So, each observation receives a single flag that indicates if the measured value is considered good or not (or some degree of uncertainty). The advantage of this strategy is that, at least in oceanography, there is still much energy devoted to visual inspection of data and it is the technician operating the quality control process who makes the final decision. The disadvantage is that the results are not strictly reproducible since it relies on operator judgment. There are arguments to support both schemes. In situations where there is an abundance of data, algorithms can be used to decide on the inclusion or exclusion of data to be used. Where data are scarce, each observation is precious and work is undertaken to use everything that can be used. It is time to reconcile these different approaches to ensure that users are best served. Recommendation 5.2b: DMPA should resolve the differences in how the quality of data is indicated to best serve user needs. Many programmes currently use a data quality flagging scheme that provides an assessment of the quality of observations. However, there is no universal way that quality is indicated. Within the ocean community, there has been a tendency to standardize on the flagging scheme inherited from IGOSS. This scheme has some differences with the scheme used in the meteorological community as embodied in the BUFR tables. Finally, another group working in the U.S. (the QARTOD initiative) is currently devising another interpretation. The problem is that although single digits are used by all, a particular digit value has different meanings for each scheme. Although a user can sort this out with appropriate documentation from each data provider, it is an inconsistency that should be removed. A related question that also needs consideration is how to manage the quality flags that come with data. One solution is for the receiver to keep these flags and add their own. After data change hands a few times, the resulting series of quality flags may well be confusing to a user. The other solution is for the receiver to use the attached flags as guidance, but if additional QC is done, to overwrite the incoming flags with the results of this action. The user sees only the one set of flags, but there may be some valuable information lost. Recommendation 5.2c: JCOMM to work with all appropriate bodies to converge toward more uniform schemes (and ultimately a single scheme) to indicate data quality. These recommendations are important. There are substantial resources expended in assessing the quality of data, and these are consumed over and over again by each group receiving data. Until there is consistency in what procedures are applied, acceptance on a broad scale of the correctness of the procedures, and a standardization of how results are reported, there will be no resource savings. 5.3 Duplicates Data versions are created in the processing of data from original forms to forms in an archive and made available to users. Duplicates, and near duplicates, may also created as well. This can happen as the data are transferred to various archive centres and exchanged in projects around the world. Because of processing that takes place at each of these centres, the data and information that is archived may not be identical to the original. This can be the result of format conversions, trimming away of some of the information when data are sent from one place to another, errors in transcription, etc. Similar problems can occur in an individual archive where the same data arrive from two different sources. If these arrive at separate times, or have different content, or are processed by different people, the fact that they are duplicates may escape notice. If someone wants to assemble all of the available data, they may contact different archives asking for their holdings. In return they will receive these multiple copies, some of which will be obvious as exact duplicates and some which will be inexact duplicates that are not so obviously derived from the same original. These duplications may have significant impacts on analyses and so are undesirable and need to be eliminated. The detection of exact duplicates is relatively straightforward and can be taken care of by algorithmic means. But finding inexact duplicates is not so simple. Inexact duplicates can arise, for example, if position precision is degraded, or if a value derived by extrapolation is inserted at the surface. The longer that data have existed, the more likely it is that that they have been through more transformations and exchanges and so the more likely that inexact copies exist in a number of places. Though there are examples of software operating today that are reasonably good at detecting such duplications, none of the schemes are fool proof. A possible solution would be to employ unique identifiers as briefly described under versioning as a way to help find duplicates. The idea would be to attach a unique identifier to the original data as collected. As the data went through processing, were delivered to and passed among archives, the unique identifier would always accompany the data; that is it would never be removed by any process along the way and would never be altered. Then, as newly arrived data came to an archive or user, they need only check for a duplication of the identifier, and not have to devise elaborate rules to decide if the new data are exact or inexact copies of something already present. Another solution would have national archives maintain data collected by their own nationals, but would provide these data to all others. That is, the original or reference copy would be maintained at a single location. All other copies would be recognized as copies and if there were any differences, the original version would be considered the true version. Weaknesses of this are that not all nations have the same infrastructure to fully support this model, and there would need to be some resolution of where data would go when the collection activity is multi-national. Recommendation 5.3a: DMPA develop a methodology to address how to identify exact and inexact duplicates in contemporary JCOMM data. The unique identifier approach can be effective both within a single archive and across archives that exchange data. It could be implemented in an incremental way such that as an archive adopted the practice of employing unique identifiers, it would accrue benefits by simplifying its duplicates detection process. In order for this to propagate into all of the archive systems in the world, there would need to be close cooperation of JCOMM with existing archives of IODE, WMO and ICSU. Recommendation 5.3b: JCOMM consider developing a comprehensive system to uniquely tag data from all of its programmes and employ this to detect data duplications. 5.4 Contents Each data system, whether dealing in real-time or delayed mode data has its own scheme for storing the data and the information about the data. The methods that are used are strongly influenced by the available computer infrastructure. The result of these varying approaches is that it is difficult to compare data and information from different sources. For example, it may be that one source provides a lot of detailed information about the instrumentation employed whereas another source provides no such information. The differences are not usually as extreme as this example, but these are differences that can be remedied to provide a more consistent and therefore, interoperable collection of data when assembling them from different sources. There are some examples in operation now that have gone part way to standardization. There are, for example, two vocabularies, represented by BUFR tables and the CF conventions. As noted earlier, a mapping between these vocabularies would ease the inter-comparison of data reported in each. But this is really only a first step. As an example, it is common practice for an archive centre to keep information about the origins of the data they receive. It should be possible to develop a set of standard attributes to be recorded when known about these origins. Then, when data are requested, this information can be reported in a standard way. A few years ago, this idea was presented in the context of a discussion of Marine XML. The idea was that information could be assembled into packages of standard content that were called bricks (see  HYPERLINK "http://www.iode.org/marinexml/files.php?action=viewfile&fid=4&fcat_id=3" http://www.iode.org/marinexml/files.php?action=viewfile&fid=4&fcat_id=3 ). For example, standard content for the origin of data would be information about who sent the data, their address, the name of the project under which the data were collected, the name of the platform and so on. The essential idea was that each brick dealt with discrete and separable information. It is possible to use a collection of bricks to build a structure for observations and in this, for example, could be found data quality flags. A suite of bricks were envisioned that contained the varied information content of both measurements and information that make up a collection of data. By assembling the bricks in different ways, a variety of data types could be built into a collection. The most powerful aspect of this, though, is that adopting such a strategy would standardize the content and thereby remove the ambiguities that are present in many data exchanges. The metadata standards developed as part of ISO (International Standards Organization) or the U.S. FGDC (Federal Government Data Committee) have at their heart similar ideas. However, they do not yet go as far into the detail and content of observations, nor do they yet provide the necessary flexibility. Still, because there are similarities, it would be worthwhile to take this work into consideration when deciding what information to include and how the information should be structured. Recommendation 5.4: JCOMM explore the ideas embedded in xml "bricks" as a standard way to organize and preserve information and data. 5.5 Processing history It is almost always true that when data arrive at any data centre they are transformed into some other internal data structure. But an important consideration in the archive and data preservation process is the accurate preservation of all of the originally reported data. Errors can frequently occur in translations of data between different formats. Keeping a copy of the data as originally received is a safe way to guard against transcription errors. The transformation process can include actions such as converting data from one format or units to another (e.g. to SI units in BUFR, from originally reported units), applying quality test procedures, ingesting data into archives or models, corrections when possible, and so on. The processing stages can become very complicated with many decision points that cause changes in processing depending on the kind of data involved and its origins. Each of these steps that transforms the data or adds to it (as a quality assessment procedure adds quality flags) could be recorded as a processing history. This strategy can be very useful in finding and fixing problems generated in the course of routine processing. It can also be very useful in explaining anomalies detected in data. There are a few programmes within JCOMM now where retaining a processing history has become standard practice (e.g. the Global Temperature and Salinity Profile Project). These programmes should be examined to determine the value of creating and preserving a processing history. JCOMM can then use this advice as a basis for recommending appropriate usage on a broad scale. Recommendation 5.5: DMPA explore the value of preserving a processing history and recommend broad adoption if appropriate. 5.6 Metadata There are a number of initiatives related to metadata that are currently underway. One that has a substantial international subscription is the Marine Metadata Interoperability Project being run from the Monterey Bay Aquarium Research Institute (see  HYPERLINK "http://marinemetadata.org/" http://marinemetadata.org/ ). Their work is mostly focused on ontologies (the science of describing the kinds of entities in the world and how they are related) and vocabularies. There is also a project within JCOMM to define the kinds of metadata that should accompany measurements that are distributed in real-time or in delayed mode. Generally, these deal with characteristics of instruments, data quality, etc. This has been pursued by the Expert Team on Data Management Practices and is strongly linked to both the WMO Information System developments and those of SeaDataNet (see http://www.seadatanet.org/ ). There is the Dublin Core Metadata Initiative (see  HYPERLINK "http://dublincore.org/" http://dublincore.org/ ). At the risk of over-simplifying this, the metadata considered here grew from the domain of library science and is strongly related to describing document origins and contents. There is the well known ISO organization which develops a broad collection of standards including for metadata. (see  HYPERLINK "http://www.iso.org/iso/en/ISOOnline.frontpage" http://www.iso.org/iso/en/ISOOnline.frontpage ). Each of the above tackles the issue of defining standards for recording metadata. Most have a particular purpose in mind, and this drives the content to be described. But it is evident that metadata comprises a wide range of information. One attempt to address and categorize this range has been made by the U.S. Data Management and Communications Expert Team on Metadata (see  HYPERLINK "http://dmac.ocean.us/index.jsp" http://dmac.ocean.us/index.jsp ). They divide the categories of metadata into consumer use, data management, discovery, access, transport, and archive. Specific metadata items exist in more than one of these groups. At present, the term metadata is used in many ways, with the interpretation being provided by the context of the use. But this is confusing and it would be far better to take the approach of developing categories of metadata, and to define the content to suit the purpose. We would then speak of discovery metadata, or transport metadata and both the purpose and content would be clear. Recommendation 5.6a: DMPA examine existing metadata initiatives to develop a categorization that aligns with the purpose of the metadata. Recommendation 5.6b: DMPA use the metadata categorization to develop a plan in which metadata initiatives align with its work and become engaged in these activities. While the above activity is going on, there is a fairly well described class of metadata that is used for discovery. The information in this class is sufficient for a potential user of data to identify the data collections that exist in their area of interest, in a time frame of interest, in a scientific domain of interest, and perhaps even with variables of interest. This class of information appears in the FGDC (U.S. Federal Government Data Committee, see  HYPERLINK "http://www.fgdc.gov/" http://www.fgdc.gov/ ) standard used within the U.S., in the ISO19115 standard (see  HYPERLINK "http://www.isotc211.org/" http://www.isotc211.org/) and in the GCMD (Global Change Master Directory, see  HYPERLINK "http://gcmd.nasa.gov/" http://gcmd.nasa.gov/ ) and there are others. The objectives of these are to build standard records that can be stored in an electronic catalogue and that can be searched to find data of interest. This work is far enough advanced that JCOMM can usefully participate and in so doing will fulfill one of the recommendations covered in the section on Access that follows. Recommendation 5.6c: JCOMM define its requirements for discovery metadata and embody these in a formal metadata structure. There exist a number of sources of information about the characteristics of platforms and instruments which are used to acquire oceanographic and meteorological data. For marine meteorology, there is WMO Publication 47: International List of Selected, Supplementary and Auxiliary Ships (see  HYPERLINK "http://www.wmo.ch/pages/prog/www/ois/pub47/pub47-home.htm" http://www.wmo.ch/pages/prog/www/ois/pub47/pub47-home.htm ). More recently, the Chinese Oceanographic Data Centre has established an electronic, on-line data base of instrumentation information about ocean data buoys, platforms, and other automated Ocean Data Acquisition Systems (ODAS - see  HYPERLINK "http://www.odas.org.cn/" http://www.odas.org.cn/ for information about this system). Both of these sources reflect the need to have information about the ways that observations at sea are collected. Such information is crucial in helping to explain such things as systematic changes in observations from one platform to another or in compensating for changes in observation methods when looking at long time series. These sources are but two examples of the kind of additional information that is needed to interpret observations. Gathering information of this kind and keeping the information up to date is not simple. It must rely on the individuals in countries whose job it is to service the platforms or instruments to ensure that changes are recorded quickly. However, there is also the role of an international body to be sure that the information is readily available, preserves past information as well as reflecting the most recent information. Recommendation 5.6d: JCOMM to encourage all agencies keeping information about instruments, platforms, etc., to place this information on-line and keep it up-to-date. Recommendation 5.6e: JCOMM to develop a strategy for managing the international suite of these metadata sources so that they are easily found and used. 5.7 Model Data Computer modeling is an activity carried out in many Member and Member States actively involved in JCOMM activities, with uses ranging from research to product development. The results are closely linked to how the observational data are assimilated into the model and how the computations are carried out by the software. Numerical models can produce large volumes of data since they can provide a continuous, quantitative representation of atmosphere or ocean variability in the four dimensions of space and time. The results of models are valuable to others because they take limited observational data and perform a kind of interpolation/extrapolation to provide results where observations are poorly sampled in space and/or time. Models can be used to hindcast or reconstruct past variability; nowcast or provide the state of the system by combining observations, dynamics and other empirical information; and forecast conditions in the future. The resulting value-added fields and products are used by others directly or as inputs to other kinds of models. Research models are run to explore scientific issues, are constantly being improved or changed, and have results that are generally of immediate use to only a small audience. Operational models are run on a routine schedule, have characteristics that are fixed for considerable periods of time and hence can be readily documented, have undergone some degree of observational validation, and provide products that are of wider use and distributed to clients on a routine basis. Reanalyses fall into a third model category, in which tightly constrained versions of operational models are run over long retrospective periods to produce the most homogeneous results for climate research. The shared characteristics of operational and reanalysis models define the key attributes that determine if model results have value to archive. JCOMM should consider the results of such models as data assets and consequently they should be managed appropriately. Recommendation 5.7a: JCOMM to work with the modeling community to define the characteristics that determine which outputs should be archived. The volume of data produced by a model may be an issue. In addition, it will be important to devise an appropriate indexing scheme so that subsets of the outputs can be quickly identified and accessed. Recommendation 5.7b: JCOMM to work with relevant modeling groups to develop cost-effective strategies for the storage and archival of operational model outputs and products. The model characteristics are of great importance as they impact what data and information to archive, and for how long they should be archived. In addition to this, the data assimilation schemes, observational inputs, computational algorithms and generally the important internal operations of the model need to be documented so that comparisons may be made between models and observations, and reliability can be assessed. Recommendation 5.7c: Appropriate model characteristics will be archived with model results. Models change and improve so that older versions of models are retired and newer versions come into operation. Each time there is a change to an operational model, the value of retaining output from the earlier version should be assessed. Recommendation 5.7d: JCOMM will collaborate with model developers to decide the long-term value of preserving outputs of retired versions of models. 5.8 SOCs and RNODCs SOCs (Specialized Oceanographic Centres) are a legacy from IGOSS. They were formed by member agencies volunteering to carry out an activity to meet a particular need within IGOSS. SOCs were of different kinds with different foci, such as managing data or on capacity building activities. The list of SOCs included SOCs for real-time ocean profile data, for sea level, and surface drifters. RNODCs (Responsible National Oceanographic Data Centres) were a creation of IODE. These included RNODCs for the Southern Ocean, for surface drifters, for MARPOLMON (Marine Polution Monitoring Programme), for IGOSS, for the western Pacific (WESTPAC), for the JASIN Project (Joint Air-Sea Interaction Experiment), for ADCP (Acoustic Doppler Current Profilers) and for the Indian Ocean (INDO). In the last review of IODE, it was determined that the RNODC system was working only in a few cases. Consequently, they were abolished with IODE intending to find another mechanism to support the functions. In fact, there is still a strong reason for the activities performed by some of the former RNODCs. This issue is not resolved at this point in time. Where it is of interest to JCOMM, the activities of former SOCs and RNODCs should be formally recognized either as a component of the appropriate PAs, or adopted as an extension of other activities of interest. Where there are overlaps of activities, actions should be taken to decrease the level of overlap and to enhance the cooperation. Recommendation 5.8: JCOMM and IODE seek efficiencies in the operations of former SOCs and RNODCs. 6. Access Finding data of interest in the world of distributed archives and data sources is not easy and it can be very difficult for the occasional user. However, the ability to make observations in the marine environment is changing rapidly, and it is becoming much easier for new data sources to appear that are outside of the traditional data collection communities. It is therefore important to have some way to find all of these data sources. Once data are found, they must be available to users. If there are products generated from the data, these products must also be available. This section discusses how to provide access to the data and information held in JCOMM. 6.1 Discovery Currently, there is a high level of importance assigned in the international data management community to the construction of catalogues that describe the data held in the large archive centres. This development is advancing through the acceptance of standards for describing data holdings as embodied in such catalogues as the GCMD, through the use of the FGDC metadata standard and the ISO model. There is much work going on now to develop domain specific "profiles", such as ones for meteorological or for oceanographic data, within ISO standards. Constructing catalogues with the same (or fields that have a 1-1 mapping) contents and linking catalogues by using standards such as ISO-23950 allows queries to cross from one catalogue to another. This achieves interoperability, without the requirement of centralizing the catalogue. These help to address the "data discovery" problem. Another strategy is to exploit existing commercial search engines, such as Google, as the way to locate data. To do this requires placing appropriate information in the parts of static web pages that describe the data so that the search engine web crawlers can locate the information and index it. To be effective, there needs to be an agreed standard for how data will be described, perhaps similar to what appears in ISO profiles. Both of these strategies have merit and perhaps cater to different user communities. These ideas need to be explored and tested. Recommendation 6.1a: JCOMM pursue the creation of standards for data discovery metadata and encourage these to be used to support interoperable catalogue services and registries. Recommendation 6.1b: JCOMM explore how commercial search engines can be used as another way to search catalogues so that users can use Internet tools to locate data. 6.2 Browse After potentially useful data collections have been identified, some further exploration usually is required to determine if the archive has the specific data of interest. This is often necessary since the data discovery information may not be detailed enough to answer all questions that a user might have. Generally, the tools needed to support this browse capability are closely tied to the archive in which the data reside. This can be remedied to a degree by adopting certain technologies. For example, OPeNDAP (Open-source Project for a Network Data Access Protocol see  HYPERLINK "http://www.opendap.org/" http://www.opendap.org/ ) also provides browse capabilities for data collections available in netCDF or a few other formats and using certain standard structures. This technology provides a looser connection to archive formats. Web service technology, as embodied in the standards promoted by the Open Geospatial Consortium (OGC see http://www.opengeospatial.org/ ) such as for web map services, may be of use. This strategy would identify a set of data browse services that every archive centre should comply with and which would deliver a standardized response. This provides a very loose connection to archive structures since each archive would write the connection software needed to provide the standardized service. There are other technologies being explored including those embodied in the WMO Information System, WIS, described later. Recommendation 6.2: JCOMM explore the implementation issues of existing or proposed methods for supporting browse functions. 6.3 Data Delivery Delivering data to users is a fundamental objective. Therefore, once the source of data has been identified and the data of interest have been verified to be in the archives, the next step is to provide access to the data. Ideally, this would take place through an interactive query that selects only the data of interest and passes the results directly to the person making the query. But it is unrealistic to expect that this can be done in every case. The reality is that some data providers do not have the computer capabilities to support this service. In other cases, the volume of data requested may be so large that a server trying to provide the data would fail. A further consideration is the national policies on providing basic data and higher-level products to users. Both the WMO and IOC have policies regarding access to data. It is important that each member follow these policies to provide as free and open access to the data as they can. Each member needs to analyze their capabilities and national policies and determine for themselves what can be supported. Recommendation 6.3a: Each member state of JCOMM needs to examine its ability and willingness to provide all of its data holdings on-line. Each will determine what level of support it can bring to bear. The WMO Information System (WIS) has a role to play in providing access to data. The role of JCOMM in WIS is discussed later. Not all data users will be satisfied by the functionality provided by WIS. This means that JCOMM will also need to participate in other distribution schemes for providing data and information to clients. In general terms, it is important to be sure that what is built is part of a larger project and where possible, exploits standards such as those promoted by OGC or ISO bodies. There must be agreements on a small but common set of data exchange formats that all sites will offer. Recommendation 6.3b: DMPA must keep aware of other and continuing projects to improve the access to data and where possible both participate in the projects and adopt procedures that improve access to JCOMM data. Because much of the real-time data are collected through JCOMM programs, and because JCOMM through cooperation with IODE and WMO has access to the historical record, an argument can be made for developing at least two sorts of products from the archives. The first is to build climatologies that can be used by all members. Such climatologies are very valuable in testing whether newly arrived data appear to have unusual values and so may, in fact, be in error. They are also valuable in assessing if present conditions are warmer or cooler than average. At the moment, there are a number of climatologies in existence and depending on which is used, results of comparisons and conclusions about differences can vary. Climatologies should be built with the active collaboration of appropriate members of the scientific community. Such collaboration ensures that there are sound principles behind the choices made in consolidating and averaging data and hence increase the acceptance of the results. A second product is to construct specialized archives. A good example would be to build an archive of all of the instrumented wave elevation and wind data where the waves are extreme. Such an archive would be invaluable to wave modelers since there are few such data to be had, and it is in the extreme events that the differences of the models show most clearly. There are other examples of where such extreme event data would be useful as well including episodic events such as El Nino, harmful algal blooms (HABS), sudden deepening of storms, etc. Just as for climatologies, the building of such archives needs to be done in close cooperation with the appropriate scientific group. In the case of extreme waves, the group exists in the SPA. In some cases, it may be sufficient to build appropriate data mining tools that can find and extract the data required from global archives. In other cases, it may be necessary to search out such data from the various agencies around the world that hold them and do all of the consolidation and standardization to bring the data into a single archive. Recommendation 6.3c: DMPA encourage the compilation and adoption of a standard climatology, of the creation of specialized archives, and other products that have wide spread applicability to Members and Member States. Not to be forgotten is the importance of the information that describes the instruments used to make the observations, the ways the observations were collected, whatever processing they may have passed through and so on. These metadata are extremely valuable in helping to interpret the observations and are especially important when looking at long time series where instrumentation may have changed. These metadata should accompany the data so that the user has the full information required to make maximum use of the data. Recommendation 6.3d: JCOMM needs to ensure that all information required for the correct interpretation of data be included when data are delivered to clients. 6.4 Data Access Policies and Security The first issue has to do with the data and information access policies of member states of JCOMM. Both WMO (see  HYPERLINK "http://ftp.wmo.int/pages/about/Resolution40.html" http://ftp.wmo.int/pages/about/Resolution40.html ) and IOC (see  HYPERLINK "http://www.iode.org/index.php?option=com_content&task=view&id=51&Itemid=95" http://www.iode.org/index.php?option=com_content&task=view&id=51&Itemid=95 ) have data policies that have been constructed with careful consideration of the views of member states. Different countries will have more explicit policies that will apply to exchanging data, or delivering data to clients as envisaged in this DMPlan. Clearly JCOMM data management activities need to operate within these intergovernmental and national policies. The second issue concerns guarding the integrity of data holdings from malicious individuals who break into computer systems and do harm. This is a serious issue even when the data are freely available. Each country providing access to its data or information holdings needs to protect these assets in conformance with national practices. 7. Coordination and Linkages As an international organization co-sponsored by WMO and IOC, JCOMM has many connections among its internal programmes as well as to organizations and groups outside. A JCOMM DMPlan must recognize these partners and the distributed nature of the international data system. Data collection is carried out as a national activity, whether or not it is part of an international programme. There is a diversity of observational, processing, and distribution capacity among nations. This DMPlan needs to function within this context and encourage and support increasing these capacities for members of JCOMM. To meet JCOMM objectives will take an increased level of cooperation and coordination by all members of JCOMM and other international organizations. Strong partnerships need to be forged with these other programmes. This section explores the implications of these connections and discusses some of the needs to support or enhance the cooperation. 7.1 Within JCOMM Activities The OPA encompasses many of the observation programs at sea. It includes programs using surface drifters (Data Buoy Cooperation Panel, DBCP), Volunteer Observing Ships (VOS), Ships Of Opportunity (SOOP), the international tide gauge network (GLOSS), and others. Many of these systems have been in place for a number of years and have built procedures for managing their own data and information streams. Some, such as VOS, are heavily reliant on facilities at WMO for managing information about the fleet. Others, such as DBCP, recognizing the limitations of their initial systems, are now helping to build new ones to hold information about their platforms, (e.g. ODAS metadata). The SPA also has observing programs incorporated into their work. For examples, the ET (expert team) concerned with waves and the ET on sea ice both deal in observations made by others. Their focus has been on coordinating activities so that data collected by one organization are easily available to another. The SPA also includes groups with a strong focus on products to support such activities as safe operations at sea or responding to accidents. The DMPA has activities that connect directly to some of the observation programs within the other PAs. But this is not true for all OPA and SPA activities. The interaction between the data managers of the different groups has been through informal discussions only with the result that there is only a small degree of commonality. Recommendation 7.1a: JCOMM develop a formal mechanism to ensure regular exchanges of information and ideas on how data are managed between the groups in OPA, SPA, and DMPA. It was recognized that in creating JCOMM there needed to be links to the satellite community and the data that are so acquired. JCOMM has satellite rapporteurs in each of the programme areas. Their responsibilities are to understand the activities in the PA, to understand activities taking place in the satellite community, to help make linkages where appropriate and to bring to the attention of one or the other community actual and proposed activities that impact operations. Data management in the DMPA is focused on in-situ observations. There is no intention to duplicate the data management activities that are employed in the satellite community. However, it is important to build bridges to that community so that data handled by JCOMM and data acquired by satellite operators can easily be combined and compared. Recommendation 7.1b: JCOMM must consider interoperability issues with satellite data providers so that satellite and in-situ data are easily compared. Data management activities across JCOMM PAs will be furthered by the introduction of standard practices in many facets of their work. This ranges from simple things such as the adoption of common naming conventions for variables, consistent units of measurement, selection of common formats for delivery of data to clients, and mandatory metadata content to describe data holdings throughout JCOMM PAs. There is much work to be done in the domain of standards. However, there have already been significant activities by other groups so that all of what is needed may not have to be developed by JCOMM. Indeed, JCOMM should take the approach of adopting an existing practice as the standard as the first choice when this is available. If no existing practice meets the minimum needs for JCOMM, the second consideration should be given to make appropriate adaptations to an existing practice. Finally, and as a last choice, JCOMM may need to devise its own standards, though this should not be done without careful consideration. Recommendation 7.1c: JCOMM should first adopt an existing standard or best practice, as a second option adapt an existing one, or failing that create its own. JCOMM will need a process to adopt, adapt or create its standard practices including the certification or appropriate re-evaluation of longstanding standards already in use within JCOMM (e.g., delayed mode VOS formats). There is no such process at the moment, though there are examples of similar activities such as within the WMO domain in such committees as the ET-DRC (Expert Team on Data Representation and Codes) and elsewhere. Because JCOMM should only, as a last resort, create its own standards, it does not require the same process as in ISO or OGC. Instead, JCOMM requires a process that can recognize where standards are required, identify candidates to be considered, evaluate candidate practices and then recommend their use across JCOMM. The accreditation process for standards will require both a group to coordinate this activity and assistance by JCOMM members to take part in the evaluation process. Recommendation 7.1d: JCOMM develop a process to accredit standards to be recommended for use across all activities. Recommendation 7.1e: DMPA develop a plan for coordination of the accreditation process and carrying out of evaluations. As a standard is adopted, this information must get out to JCOMM members and they will need to take steps to implement it. There will, therefore, be a role for communications and a repository for the documentation of the standards used by JCOMM. This could well be served by JCOMMOPS, or some other suitable and widely visible agency. Recommendation 7.1f: JCOMM establish a highly visible and accessible repository where information about JCOMM standards can be found. Members will have varying abilities to respond to adopting recommended standards. It is unlikely that a standard will be implemented across all JCOMM members simultaneously. Indeed, if this is a requirement for a standard to be effective, JCOMM will need to ensure an appropriate implementation procedure is in place. The speed of implementation of standards may be enhanced by an appropriate use of capacity building activities. Recommendation 7.1g: As part of the accreditation process, consideration must be given to how to implement the standard across JCOMM members as rapidly as possible. Due consideration should be given to how capacity building resources may be used. Coordination must also take place with the other programmes in IOC, WMO, regional and national activities. Some of this will be ensured by members of the DMPA and other PAs being participants of the various activities. A challenge to the DMPA will be to keep abreast of these activities, and to select those in which to participate actively and those that bear watching only. Because of the wide variety of programmes, DMPA needs to adopt a reporting process whereby members hearing of significant activities to JCOMM can report these. Equally, DMPA needs to look ahead to select priority activities and use this as a basis for gauging where member resources are to be invested. Recommendation 7.1h DMPA establish a reporting process that has members informing the group of significant activities in other programmes. Recommendation 7.1i: DMPA set priority activities each intersessional period and use this as the guidance to selecting activities for its members. Within the OPA there has developed a simple quarterly reporting system (see  HYPERLINK "http://www.oco.noaa.gov/index.jsp?show_page=page_status_reports.jsp&nav=observing" http://www.oco.noaa.gov/index.jsp?show_page=page_status_reports.jsp&nav=observing ) whose goal is to provide a concise view of where the observing system stands in meeting GOOS objectives. The target audience for this report is senior members of governments who have the ability to influence budgets. The results shown in these quarterly reports are still limited to only 5 variables whereas there are a number of other variables that should also be represented. These reports represent one measure of how well the data systems are functioning. DMPA needs to provide the necessary support to fill out the missing portions of this reporting system. Recommendation 7.1j: DMPA in collaboration with OPA, and SPA encourage the completion of quarterly reporting of other important variables following the model used by OPA. The data systems in PAs have more detailed measures of how they are meeting their requirements. Some of these are formalized in an annual reporting mechanism, while others are less formal. There are a number of measures that can be thought of as possible candidates to be used by all data systems. This could include measures such as: the percentage of data reporting in real-time with detected problems. the percentage of total data received that report in real-time. the time delays between receiving real-time and delayed mode versions of the same measurements. the mean time to report a real-time observation (report time observation time) Other measures can be imagined. The objective of defining such a list would be to find elements across all data systems that gauge the success of the programmes to meet the overall objectives of JCOMM. It would provide a means for data managers of the various systems to see how they compare to others, to identify weaknesses and to show quantitative improvements as corrective actions are taken. Developing this list is an activity that could be coordinated by DMPA but requires the support of data systems operated by OPA and SPA. Recommendation 7.1k: DMPA collaborate with appropriate members of OPA and SPA to develop a set of data system performance metrics and implement a standard reporting of these results. 7.2 With IODE Activities IODE began many years before real-time transmission of oceanographic data was practical. Its focus, therefore, is on acquiring the data collected after the cruise or data collection activity takes place, carrying out some degree of quality assessment and building national archives to ensure the data are preserved. Data managed within the IODE system generally are of scientific quality and therefore suitable for investigations into climate studies. Many of the data come from scientific researchers who contribute the data to their national data centres. These national centres, of which there are about 60, come together under IODE to exchange information and to build the current data exchange system. IODE centres handle a variety of data including a wide range of physical, geological, chemical, biological, and even some meteorological observations. In scope, the types of data managed by IODE are broader than currently managed by JCOMM. However, there is overlap in both the kinds of data managed by JCOMM and IODE and the time scales on which those data are handled. Depending on national organization, there can be a high degree of cooperation between IODE and JCOMM. This cooperation is vital. The full suite of oceanographic and meteorological measurements is large and diverse, and the work needed to manage the data is substantial. Recommendation 7.2a: IODE and JCOMM formalize the relationship between the organizations. It is suggested that the chair of IODE be named a member of the DMPA-CG and the chair of the DMPA be named an Officer of IODE. Where there is a high degree of overlap of interests in types of data, it is important to consider streamlined operations. In this spirit, IODE and JCOMM share the ETDMP (Expert Team on Data Management Practices) and coordinate its activities. Likewise certain data management programmes of IODE, such as the Global Temperature and Salinity Profile Project (GTSPP), are jointly supported by JCOMM and IODE. There are other examples and it is important to identify and recognize these joint programmes. Recommendation 7.2b: Data management programmes of joint interest to both JCOMM and IODE be formally recognized and supported by both organizations. IODE members maintain a number of archives that are of direct interest to JCOMM and the opposite is also true. It is important for JCOMM to gain easy access to data maintained by IODE (of course, the reverse is also true for IODE having access to JCOMM archives). The comments made earlier about processing and access all apply here and should be taken into consideration. For example, confusion may arise where real-time data are handled by one organization, but the delayed mode by another. In such a case, there may be differences in labeling the origins of the data, in the resolution, in processing, etc. This means a high degree of cooperation will be needed to ensure data can cross organizational boundaries without confusion of content. There is little doubt that this will mean the adoption of interoperability standards (a ready mapping of one standard to another) or the adoption of the same standards. Recommendation 7.2c: IODE and JCOMM cooperate to ensure easy access and clearly described content of respective data streams and archives. 7.3 With Other IOC Programmes There are a number of other programs and projects within IOC including GOOS (the ocean component in GCOS), GODAE, OOPC, GHRSST, Argo, etc. JCOMM is involved in many of these. JCOMM figures prominently in the GCOS Plan, being mentioned in 21 actions. These span the range of JCOMM activities in all Program Areas. Those with direct mention of data management functions include: O6: Improve meta-data acquisition and management for a selected, expanding subset of VOS (VOSClim) together with improved measurement systems. O11: Ensure real-time exchange and archiving of data. Ensure historical sea level records are recovered and exchanged. O24: Promote development of integrated analysis products and reanalysis using historical data. O33: Develop and implement comprehensive data management procedures. O34: Undertake a project to develop an international standard for ocean meta-data. O35: Undertake a project to apply the innovations emerging from the Future WMO Information System initiative, and innovations such as OPeNDAP to develop an ocean data transport system for data exchange between centres and for open use by the ocean community generally. O36: Plan and implement a system of regional, specialized and global data and analysis centres. O39: Develop plans for and coordinate work on data assembly and analyses. This DMPlan addresses meeting the first part of O33. Implementation of the recommendations of this plan will meet the second part of O33 and will address all of the other actions. Recommendation 7.3a: JCOMM and DMPA move quickly to adopt a data management plan and to further develop an implementation plan based on the DMPlan as rapidly as possible. The GODAE project (see  HYPERLINK "http://www.godae.org/" http://www.godae.org/ ) is nearing its end. It has developed a number of products, intercomparisons, common output strategies and so on. The work that has been done is important and directly relevant to implementing recommendations that are part of this strategy. Similarly, the GHRSST (see  HYPERLINK "http://www.ghrsst-pp.org/" http://www.ghrsst-pp.org/ ) project has much to offer in demonstrating, among other products, how in-situ and satellite observations can be used together. Argo (see  HYPERLINK "http://wo.jcommops.org/cgi-bin/WebObjects/Argo" http://wo.jcommops.org/cgi-bin/WebObjects/Argo ) shows how an international system can collect, manage and distribute data to support operational oceanography requirements. All of this experience is important and needs to be captured to build an effective data management system for JCOMM activities. Recommendation 7.3b: JCOMM must work closely with the many other IOC programs in developing its implementation plans. Capacity building is an important activity. Within data management activities, it needs to cover all aspects from assembly of collected data, to processing and quality control, to archiving and providing access to the data. Information about the data collection, processing, etc., as referred to in other parts of this document is equally important. Suitable activities to increase the capabilities of JCOMM members to fully participate in data management and to use the managed data must be supported. But JCOMM is not alone in wanting to address these issues. Both of the co-sponsors of JCOMM, the WMO and IOC, have capacity building programs. Rather than construct something new, it makes more sense for JCOMM to collaborate with these efforts. This can be, for example, by ensuring suitable training materials on marine operations are present and by contributing instructors as appropriate. Joint activities between Member and Member States are another way to increase members capabilities. Recommendation 7.3c: JCOMM should collaborate with existing IOC (and WMO) capacity building activities to ensure that the marine component is included. 7.4 With WMO The WMO Information System (WIS) has an important role to play in providing data. The linkages of the meteorological side of JCOMM are closer to the developments of WIS than the oceanographic side. However, at the invitation of WIS, the DMPA chair and a member of the Data Management Coordination Group were invited to a meeting to discuss the development of WIS. The terminology used to describe the components of WIS is different than what is used by oceanographers, but the functions described are readily understood. In fact, DMPA had already taken some steps that compliment the work of WIS through its support of the E2EDM (End to End Data Management see  HYPERLINK "http://e2edm.meteo.ru/e2edm/index.php?section=1" http://e2edm.meteo.ru/e2edm/index.php?section=1 ) pilot project. At the meeting, connections were made between the work of E2EDM and WIS and this work continues. Recommendation 7.4a: DMPA and WIS should cooperate to ensure that all components of JCOMM data systems are available to WIS. There are a number of other programs within WMO for which there are strong impacts on data management activities of JCOMM. These include the various committees, such ET-DRC, who regulate how data are presented on the GTS, to the secretariat who maintains publications such as Pub 47. JCOMM must be engaged in these groups to represent its activities and to influence, as appropriate, activities in WMO. Recommendation 7.4b: DMPA ensure appropriate experts are fully engaged in appropriate WMO activities. 7.5 With ICSU WDCs There is a hierarchy of archives that exist in the world and into which JCOMM data management activities fit. On the broadest international level there are the World Data Centers. These were set up a number of years ago by ICSU (International Council for Science, see  HYPERLINK "http://www.icsu.org/index.php" http://www.icsu.org/index.php ) for various disciplines, including meteorology and oceanography, and they continue to operate. Their mandate has been to act as the global archive for data of one kind or another such that a client anywhere in the world could come to a WDC and find any data that might have been collected. WDCs rely on data exchange agreements with national data centres. Just as JCOMM must have close ties to IODE for oceanographic data, it must also have similar ties to the various WDCs managing data of interest. Indeed, the issues of standards, archives, and access all apply to consideration of interactions with WDCs as well. JCOMM should take the opportunity to build stronger ties. Recommendation 7.5a: DMPA initiate a discussion with WDCs to build stronger links between the observing and archive systems and how WDCs operate. This should be done with other appropriate partners. The WDCs in the international data system are the focal point for all of the data. Besides ensuring the safe keeping and dissemination of the data, they are also in a position to create or collaborate on the production of climatologies. These products, as mentioned earlier, can be an important output from JCOMM. Members can both contribute by timely provision of data to WDCs and benefit from recent and appropriate and timely updates to the global data set and climatologies. Recommendation 7.5b: JCOMM members support the timely assembly of data in WDCs and encourage timely updates and distribution of the global data sets and climatologies. 7.6 With Other Programmes There are a host of other programmes and projects carried out in national and international fora that lie outside of the organizations discussed already. Many of the data management problems they address are the same ones experienced by JCOMM. Data collected under the JCOMM umbrella contribute to these programmes and JCOMM members also are members of these programmes. There is a great deal of inter-programme communication through the individuals that contribute to JCOMM and these other programmes. Data management plans and implementation cannot and should not ignore these activities. The experience is valuable and the solutions are worthy of note. Recommendation 7.6: JCOMM must develop a level of interoperability in data management with other major international and significant national programmes. 8. Communications Implementation of all of the recommendations posed will enhance greatly the capabilities of JCOMM to meet its objectives. However, it is clear that JCOMM is not an organization operating in isolation from other activities and programmes. Implementing the recommendations is only completing part of the work. It is important that after collaboration with our partners on many of their issues, JCOMM communicate these results to the wider world. It is important to tell others what is being done and why, and to show results. It is through this process that others will understand what JCOMM is doing and express interest in joining or pointing out similar endeavours. One way to provide information is to use the Internet and WWW technology. JCOMM already has a web site. There are also sites (e.g.  HYPERLINK "http://wo.jcommops.org/cgi-bin/WebObjects/JCOMMOPS" http://wo.jcommops.org/cgi-bin/WebObjects/JCOMMOPS and  HYPERLINK "http://icoads.noaa.gov/etmc" http://icoads.noaa.gov/etmc ) associated with specific programs or Expert Teams. Within these sites, it will be necessary to have additional pages that provide information about standards adopted by JCOMM, about how to connect to data and information and the work program and results from the DMPA. None of this is currently available (or written) but it is important and must be undertaken. Recommendation 8a: DMPA undertake to design and populate web pages that explain its activities. It is important for representatives of JCOMM to attend meetings of other organizations where interests intersect. At these meetings, JCOMM must make the case for what they are doing and why and encourage even greater cooperation. Recommendation 8b: DMPA will provide its representatives (and encourage the necessary national and international support) to attend meetings of other organizations and committees whose interests intersect. 9. Conclusion This plan presents a review of the various components of data management that must be considered as part of JCOMM. It makes a number of recommendations. Some of these are, in fact, underway either as formal projects in JCOMM, as an activity undertaken by one or more members, or as activities undertaken by other organizations with which JCOMM is linked. Most of the work requires coordination of activities across JCOMM Member / Member States. Developing this degree of cooperation will be a challenge. The national organizations of each member have national priorities and objectives that must be met. Progress will be made by aligning these national requirements with activities at an international scale. Of course, this is merely a plan and does not lay out the implementation steps. That is something that needs more work since this is where analyses of existing activities, forming working groups, pilot projects and experimenting with ideas will be explored. As a follow on, once this DMPlan is accepted, an implementation plan should be drawn up that takes the accepted recommendations and lays out a work schedule and target timelines to realize the objectives of the recommendations. ANNEX II Implementation Plan for the JCOMM Data Management Plan Prepared by Bob Keeley, Chair DMPA Last update: 7 Sep, 2007 Introduction This document is a follow on to the JCOMM Data Management Plan (DMPlan). Its purpose is to link the many recommendations of the DMPlan and to elaborate them as concrete tasks and actions that will realize the objectives of the plan. To this end, the recommendation numbering present in the DMPlan is preserved in the elaboration of this implementation plan. This is done using the prefix DMP and the numbering in the DMPlan for the various sections and recommendations. The plan presented here will be more volatile than the recommendations of the DMPlan. As work is identified and completed, this Implementation Plan will need to record progress. Undoubtedly, ideas will change and the evolution of this plan must move with new ideas and technology. It should be expected that it will need to be revisited each year to determine where progress has been made, where work is not progressing fast enough and where new work is required. It is important, therefore, to develop this plan in a way that allows for easy updating. This Implementation Plan links every recommendation in the DMPlan to one or more tasks and each task may be linked to one or more actions. Sometimes a single task meets the objective of the recommendation and no subdivision into actions is needed. While the bulk of the document is composed of the very detailed content of the implementation plan, it is much more detailed than most readers may be interested in. For this reason, the details are presented in annexes with a summary of the actions and some of the results to date provided in the body of the document itself. The information in both the body and annexes is presented with the same overall themes of the DMPlan (i.e. Data and Information Exchange, Data Processing, Access, Coordination and Linkages, and Communications). Of note is that the detailed plan has a specific indicator of when the task or project is completed so that a definite end point is always present. For ongoing tasks, such as communications, the end point is transferred down to the action level where individual developments can be actioned and noted when complete. The actions linked to the tasks are the activities that have taken place or should take place under the Data Management Programme Area, or in other PAs where data management activities take place. Actions may accomplish only portions of the stated task. Each of these has deliverables and the results should be updated each year. DMP 4.0: Data and Information Exchange This section treats issues that deal with moving the data from where they are collected to the appropriate shore facilities and archives in time frames that are required to meet operational or other needs. It encompasses all of the data management issues that arise from collection activities through to user-ready data sitting in well managed archives. The discussion is divided into a number of subsections and each contains a number of recommendations and actions. The sections below provide a brief summary of the implementation sequence to realize the recommendations. Greater detail is provided in Annex DMP-4. DMP 4.1: From Collectors to the Shore Recommendation 4.1: JCOMM should encourage instrument manufacturers to standardize the formats of the data and information coming from instruments used at sea. Short term actions: There have been some developments by manufacturers experimenting with what is called sensorML. While this is not a standardization of formats, it is a standardization of a data structure. This can be encouraged. Chair DMCG has raised the issue with OCG, and tabled it with scientific programmes through representation at OOPC. Follow on actions: This will be an ongoing activity to encourage manufacturers through interactions with the people who buy and use oceanographic and meteorological instruments. Members of OPA and SPA can be helpful in communicating the desirability of standards to instrument manufacturers. DMP 4.2: Using the GTS Recommendation 4.2a: DMPA lead the development of the detailed plan to change GTS data reporting from TACs to TDCs. Short term actions: DMPA has set up a group to work with other PAs to develop BUFR templates for data of interest. Some of these are well along, such as DBCP and Argo, others are progressing, such as SOT. So far first versions of templates are built. : A second activity (Meta-T) is the standardization of metadata that started under SOT but has been picked up by DMPA. This has made some progress in identifying the relevant metadata and deciding what needs to travel with the data, what can be held independently for reference and what needs to be archived with the data. : A third activity is to assist in the development of a CREX version for sea level in support of multi-hazard warning systems. This work has been completed. Follow on actions: Current BUFR templates have the same or similar information organized in different ways because they were developed independently. We want to unify the way the same information appears in templates to simplify the construction and maintenance of software. : The work of the Meta-T group will need to be extended to more variables than it currently considers and linked to the Chinese efforts for ODAS. : BUFR tables will need to be examined to ensure the presence of non-physical variables as required for reporting in coastal regions. Recommendation 4.2b: The DMPA in association with the appropriate WMO committee should evaluate MT10 for its relevance to present needs. Short term actions: A number of years ago a second BUFR Master Table, called MT10, for oceanographic variables was developed experimentally. This version allows for a different organization of BUFR descriptors and has descriptors for a wide variety of non-physical data. It has been adopted by the GHRSST Project and is being tested. Some changes are required to bring MT10 into conformance with present TDC practices. Follow on actions: Assuming MT10 proves out, there will need to be appropriate changes to MT10 and the formal submission to WMO for acceptance. Recommendation 4.2c: Enhanced interaction between JCOMM and CBS or other appropriate WMO committees is needed to expand the scope of TDCs to more fully incorporate JCOMM considerations, including software reliability, human readability, and the archival and exchange of historical and delayed-mode data in its originally reported form. Short term actions: A first requirement is to be sure JCOMM has representation on ET/DRC and this was done with the nomination and acceptance of the JCOMMOPS TC. Follow on actions: There is the need to continue to work closely with CBS to ensure JCOMM interests are considered. As more ocean data centres become involved in operational ocean modeling and prediction systems, there will be greater collaboration between IODE and NMHCs. This is to be encouraged. DMP 4.3: Using the Internet Recommendation 4.3.1a: JCOMM to support the widespread use of netCDF as a data exchange format. Short term actions: Argo, GOSUD, OceanSITES and GTSPP all are using netCDF at present. WMO has established a working group on formats and Gilbert Maudire (France) has been nominated to represent JCOMM. Follow on actions: JCOMM and IODE are developing a manual on the establishment of an NODC. Inclusion of discussions of formats and data structures should be part of this. Recommendation 4.3.1b: JCOMM to encourage usage of CF convention for variable naming in netCDF and stay informed of CF updates to meet JCOMM contributors' needs. Short term actions: The CF convention has become the recommended standard for Argo. This will be encouraged in other projects currently using or starting to use netCDF. Follow on actions: Greater awareness of CF and other standards is required within JCOMM data management activities. Increasing broad awareness will need a number of approaches including prominence on web sites, active encouragement by JCOMM and training materials. Recommendation 4.3.1c: JCOMM stay informed on netCDF maintenance and developments. Short term actions: Members of DMCG will be asked to review the use of netCDF in their domains of expertise and to provide information on developments. Follow on actions: netCDF is known to be weak in supporting the characteristics of point data, a type that is very prevalent in JCOMM. While some steps have been taken by netCDF developers, more is required. DMCG or JCOMM members actively involved in managing point data (in particular) need to work with netCDF developers. Recommendation 4.3.2a: DMPA monitor the development of xml and encourage appropriate use for the exchange of data and metadata. Short term actions: In the context of WIS, there are collaborations between the JCOMM E2E project to define and use xml tags for information about data holdings. Follow on actions: Continue to develop the use of xml in WIS and E2E projects. : A MarineXML project was operating with support from IODE a few years ago. Some JCOMM members were also involved. The results, while interesting, have not been implemented. Recommendation 4.3.2b: DMPA encourage the development of vocabularies used in xml that are as close as possible to those used in other formats. Short term actions: The collaboration of the JCOMM E2E project with WIS is contributing to this objective. : Other work related to standards is also taking place. Follow on actions: JCOMM members are working closely with the Marine Metadata Initiative lead by the Monterey Bay Aquarium. This initiative is focusing on bringing together vocabularies (among other things) and building a way to mapping terms from one to another. This is an important endeavour that will impact JCOMM and so JCOMM must continue to be involved. Recommendation 4.3.3a: JCOMM must recognize that other formats and data structures besides netCDF will have appeal and encourage activities that broaden their use and standardize their content. Short term actions: Some progress has started in the context of BUFR templates and in conjunction with the Meta-T project. Follow on actions: New technology will continue to provide both new kinds of data and increasing information. New data structures will be needed that are robust to allow for the inclusion of this new information. These data structures should develop in the context of standards for content. Recommendation 4.3.3b: JCOMM work with partners to encourage the evolution of exchange formats to more robust and stable forms, while at the same time assuring that sufficient flexibility and agility can be preserved for the archival of JCOMMs delayed mode data and metadata. Short term actions: Activity has taken place in past years in the context of the IMM format that supports I-COADS. The work on standardizing content in BUFR templates is related to this objective. Follow on actions: This will be a continuing activity to respond to new kinds of instruments, new data and new requirements for preserving information. DMP 5.0: Data Processing This section treats issues that deal with processing the data. It encompasses all of the data management issues that arise from accepting and processing data into archives. The discussion is divided into subsections and each contains a number of recommendations and actions. The sections below provide a brief summary of the implementation sequence to realize the recommendations. Greater detail is provided in Annex DMP-5. DMP 5.1: Data Versions Recommendation 5.1: DMPA needs to consult JCOMM PAs to get a full description of the versioning issue, to develop a strategy to manage versions, and to implement the strategy. Short term actions: A standards forum is in planning for early 2008. The intention is to formalize a process for accepting standards in JCOMM and IODE, and to arrive at an initial list of adopted standards. : Some work has been done to test a unique data identifier in SOT. A report with recommendations will be written. Follow on actions: An ongoing process for setting standards that encompasses more than just data quality is needed. A proposal is to be discussed at the standards forum. : Work on data version control is needed and a practical implementation scheme devised. DMP 5.2: Data Quality Recommendation 5.2a: DMPA should encourage the development and wide spread implementation of a standard suite of data quality testing procedures. Short term actions: The standards forum referenced in 5.1 is the first step and will deal with some data quality testing procedures. : The Marine Climatological Summaries Scheme has made particular progress in establishing common data quality testing procedures. There will be a report from ETMC on their implementation success. Follow on actions: As test procedures are required and developed, a standards process will need to bring forward the existence of the procedures to the community, and then advocate for acceptance and implementation of the agreed standard. Recommendation 5.2b: DMPA should resolve the differences in how the quality of data is indicated to best serve user needs. Short term actions: This topic will be discussed at the planned standards forum. Follow on actions: Once agreement is reached, a viable implementation plan is needed to ensure all JCOMM data are flagged in the same way. Recommendation 5.2c: JCOMM to work with all appropriate bodies to converge toward more uniform schemes (and ultimately a single scheme) to indicate data quality. Short term actions: Work on the process to facilitate cooperation and converge will begin at the standards forum (see 5.1) Follow on actions: All appropriate groups need to be part of the process and accept the results. DMP 5.3: Duplicates Recommendation 5.3a: DMPA develop a methodology to address how to identify exact and inexact duplicates in contemporary JCOMM data. Short term actions: This was expected to be covered by the standards forum, but has been postponed from the agenda of the first meeting. There is some experience in duplicates management in some of the JCOMM and IODE programmes and this experience and suggestions need to be drawn out in a document. Follow on actions: From the summary of experience a plan of action that covers both a better way to find duplicates in existing data collections and a way to lessen the incidence of duplicates in the assembly of data collections is required. Recommendation 5.3b: JCOMM consider developing a comprehensive system to uniquely tag data from all of its programmes and employ this to detect data duplications. Short term actions: There is some experience within the SOT and this needs to be documented and examined for broad application. Follow on actions: Depending on the effectiveness of existing schemes, improvements may need to be sought and then a careful implementation strategy that allows, if possible, a staged implementation. DMP 5.4: Contents Recommendation 5.4: JCOMM explore the ideas embedded in xml "bricks" as a standard way to organize and preserve information and data. Short term actions: Some of these ideas are coming into play in analyzing BUFR templates. This is closely tied to standardizing information content in archives. Follow on actions: Because of the close ties to standardizing content, both of these subjects must be treated together. It will be important to see how well a re-organizing of information in BUFR improves managing the data and how well it is accepted. DMP 5.5: Processing history Recommendation 5.5: DMPA explore the value of preserving a processing history and recommend broad adoption if appropriate. Short term actions: There is some experience in preserving such information in SOT. In the short term, documentation of the practice is needed with particular emphasis on the problems that are solved or alleviated by such a practice. Follow on actions: Once the advantages of preserving such information become known, there will be wider acceptance and a greater likelihood of gaining international recognition as a best practice. DMP 5.6: Metadata Recommendation 5.6a: DMPA examine existing metadata initiatives to develop a categorization that aligns with the purpose of the metadata. Short term actions: Some work on this has been done in the JCOMM E2E project and within some of the DMAC discussions. Follow on actions: As WIS develops with E2E, a first version of how to organize some of the information will be in operation. This will allow an evaluation of strengths and weaknesses of this scheme, plus the ability to assess the extension to other kinds of metadata. Recommendation 5.6b: DMPA use the metadata categorization to develop a plan in which metadata initiatives align with its work and become engaged in these activities. Short term actions: The Meta-T project has addressed this issue from the point of view of information required to accompany data in real-time or in delayed mode. This is a different aspect than used in E2E and so broadens the scope. Follow on actions: As Meta-T develops and experience is gained, refinements will be needed and extensions to other variables. Recommendation 5.6c: JCOMM define its requirements for discovery metadata and embody these in a formal metadata structure. Short term actions: Work on meteorological and oceanographic ISO profiles has proceeded independently. There are many similarities to the solutions, but some differences as well. In the short term, it is expedient to get the discovery metadata defined and operating within the ISO profiles. : Greg Reed, author of the oceanographic ISO profile, has agreed to represent JCOMM on the WMO committee responsible for the meteorological profile. Follow on actions: In the longer term, it seems advantageous to try to unite the ISO profiles in a single form. This will help clients seeking to find data of interest and encourage interoperability. Recommendation 5.6d: JCOMM to encourage all agencies keeping information about instruments, platforms, etc., to place this information on-line and keep it up-to-date. Short term actions: In the short term, the Meta-T project is working with the ODAS project in China to get the metadata relevant to SST on-line and easily searched. It is hoped that this will form the basis for an international system for other variables. Follow on actions: The ODAS project will need to broaden its scope and increase its search capability. Of greatest importance will be to develop the facility to keep their information from providers up-to-date. Recommendation 5.6e: JCOMM to develop a strategy for managing the international suite of these metadata sources so that they are easily found and used. Short term actions: The ODAS development in China represents the initial work in this domain. This site is limited in the kind of metadata managed. : Work of the E2E project in WIS will address both discovery metadata and data transport metadata. Follow on actions: The ODAS development in China represents the initial work in this domain. It seems clear that there will never be a single point of contact for all metadata so some mechanism for finding the many sources will be necessary. DMP 5.7: Model Data Recommendation 5.7a: JCOMM to work with the modeling community to define the characteristics that determine which outputs should be archived. Short term actions: A document will be prepared for circulation to set out the issues and suggest possible solutions. Follow on actions: Responses to the initial document will be used to reformulate a plan that is supportable by both the modeling community and managers of the data. Recommendation 5.7b: JCOMM to work with relevant modeling groups to develop cost-effective strategies for the storage and archival of operational model outputs and products. Short term actions: As part of the initial document for archiving model data, there will be a discussion of possible ways to standardize outputs for greater usability. Follow on actions: Opinions and support from the modeling community will be crucial for any plans to standardize results. The reformulated plan must gain this support. Recommendation 5.7c: Appropriate model characteristics will be archived with model results. Short term actions: It is expected that model results will need to be qualified by sufficient descriptive information about the characteristics of the model so that users can know how to interpret the results. The initial document on archiving model results (see 5.7a) will discuss this and propose something. Follow on actions: Opinions and support from the modeling community will be crucial for defining the information needed to describe model results. The reformulated plan must gain this support DMP 5.8: SOCs and RNODCs Recommendation 5.8: JCOMM and IODE seek efficiencies in the operations of former SOCs and RNODCs. Short term actions: Any plan will need to first identify the operating SOCs and RNODCs after the re-organizations to form JCOMM and at IODE. Then, a comparison of procedures and outputs weighed against what is needed by JCOMM and IODE will need to be made. An initial plan will need to be produced. Follow on actions: Once agreement has been reached on where streamlining can occur in the operations of SOCs and RNODCs, appropriate steps to re-align operations by the national agencies operating these facilities will be sought. DMP 6.0: Access This section treats issues that deal with accessing data. Access includes being able to find data or information needed, to look through the data to decide that what specifically is wanted is present and, finally, being able to acquire the data and information. The discussion is divided into subsections and each contains a number of recommendations and actions. The sections below provide a brief summary of the implementation sequence to realize the recommendations. Greater detail is provided in Annex DMP-6. DMP 6.1: Discovery Recommendation 6.1a: JCOMM pursue the creation of standards for data discovery metadata and encourage these to be used to support interoperable catalogue services and registries. Short term actions: Both WMO and IOC have developed ISO profiles for their respective organizations. Since JCOMM crosses both domains, we wish to ensure as much commonality between the two as possible. Greg Reed, author of the oceanographic ISO profile, has agreed to represent JCOMM on the WMO committee responsible for the meteorological profile. : We need to start building the infrastructure to support management of the metadata that will use the ISO profiles. Follow on actions: Agreed metadata content and an established infrastructure are only the support tools. It will be important to develop the habit in all of the organizations contributing information to JCOMM to create and maintain the metadata records. Recommendation 6.1b: JCOMM explore how commercial search engines can be used as another way to search catalogues so that users can use Internet tools to locate data. Short term actions: Commercial search engines are powerful toosl that require no support by JCOMM and yet can significantly increase the exposure of JCOMM information. A study is required to determine how the metadata records that are required by JCOMM for its own purposes can be made accessible to commercial search engines. Follow on actions: If it is determined that with an appropriate level of effort the metadata records of JCOMM can be made accessible to commercial search engines, implementation plans will need to be formulated and carried out. DMP 6.2: Browse Recommendation 6.2: JCOMM explore the implementation issues of existing or proposed methods for supporting browse functions. Short term actions: There are many tools existing and in preparation that permit browsing of data. Some of these are currently under development by JCOMM in the context of WIS. A review document that discusses what is presently available and what is on the horizon is needed. Follow on actions: JCOMM centres will need to support WIS capabilities, and this will be a focus for implementation. DMP 6.3: Data Delivery Recommendation 6.3a: Each member state of JCOMM needs to examine its ability and willingness to provide all of its data holdings on-line. Each will determine what level of support it can bring to bear. Short term actions: JCOMM centres holding data and information have large differences in the ability to place data on-line. At the same time, there are also sensitivities to allowing access certain data. A poll of JCOMM Member / Member States capabilities and intentions to place data on-line will help clarify what can be done. Some of this information is presently available in national reports from IODE. Follow on actions: Mutual cooperation and capacity building will be an important aspect to helping Member / Member States place data on-line. A plan for improving what is available on-line is needed. Recommendation 6.3b: DMPA must keep aware of other and continuing projects to improve the access to data and where possible both participate in the projects and adopt procedures that improve access to JCOMM data. Short term actions: Chair ETMC informed of RECLAIM project to recover information from ship logbooks. : IODE-19 national reports provide links to data sets. : 2007 WCRP Data Management task group has a list of project web sites. Follow on actions: Keeping abreast of these data rescue and access plans in countries will be helpful in promoting cooperation and capacity building. Recommendation 6.3c: DMPA encourage the compilation and adoption of a standard climatology, of the creation of specialized archives, and other products that have wide spread applicability to members. Short term actions: The climatology developed and circulated through the WDC-A is an example of what JCOMM needs to continue to support. Likewise, specialized archives, such as started for extreme waves, will be very useful to the wave community and should not take too much effort to produce. These and others are to be encouraged. Follow on actions: All JCOMM Member / Member States can provide information on what they are doing with respect to climatologies and specialized data sets. This will help to promote international cooperation and encourage convergence to standardized forms. Recommendation 6.3d: JCOMM needs to ensure that all information required for the correct interpretation of data be included when data are delivered to clients. Short term actions: There is a huge variety of information that is held to describe data collections in JCOMM. A document was prepared and presented at IODE-19 that describes the technical information needed to link to data. : There are some data type specific documents like this created for IODE a number of years ago. Follow on actions: The specification of required information should be stored in the metadata profiles discussed earlier. DMP 7.0: Co-ordination and Linkages JCOMM operates within a world of many national and international programmes. Because of this, the JCOMM DMPlan treats issues that deal with co-ordination and links with other programmes to improve the overall handling of data and information. The discussion is divided into subsections and each contains recommendations and actions. The sections below provide a brief summary of the implementation sequence to realize the recommendations. Greater detail is provided in Annex DMP-7. DMP 7.1: Within JCOMM Activities Recommendation 7.1a: JCOMM develop a formal mechanism to ensure regular exchanges of information and ideas on how data are managed between the groups in OPA, SPA, and DMPA. Short term actions: Chair DMCG attended OPA and SPA meetings : Encourage joint projects such as GTSPP, GOSUD : Encourage linking of existing data systems of PAs to systems such as WIS in WMO and Ocean Data Portal in IODE. Follow on actions: DMPA activities must be closely linked to solutions being worked on in the other PAs. : DMPA needs to continually reinforce its role of promoting common solutions to common problems, encouraging activities in other PAs to adopt solutions as often as possible and to encourage standardization. Recommendation 7.1b: JCOMM must consider interoperability issues with satellite data providers so that satellite and in-situ data are easily compared. Short term actions: The E2E project within JCOMM will involve a satellite data centre in its development activities. : DMCG satellite rapporteur is examining possible extensions of the GHRSST solution to other variables. Follow on actions: The experience of the GHRSST Project has some valuable solutions to combining satellite and in-situ data. These need to be explored further. Recommendation 7.1c: JCOMM should first adopt an existing standard or best practice, as a second option adapt an existing one, or failing that create its own. Short term actions: A joint IODE, JCOMM meeting to discuss standards is planned for early 2008. The objective is to adopt an initial set of standards, Follow on actions: There are other common practices developed in other international groups and JCOMM needs to be aware of these as well. A compilation of the more common practices will be an important adjunct to the compilation of practices used in JCOMM. This can be accomplished if a standards process is agreed to at the meeting in 2008. Recommendation 7.1d: JCOMM develop a process to accredit standards to be recommended for use across all activities. Short term actions: The Standards Forum in early 2008 will discuss and hopefully agree on a process and a way to implement the standards widely. Follow on actions: Follow on meetings will be needed to continue the adoption of standards throughout JCOMM. Recommendation 7.1e: DMPA develop a plan for coordination of the accreditation process and carrying out of evaluations. Short term actions: The meeting referenced in 7.1d will need to produce such a plan. Follow on actions: Mechanisms for proposing standards and evaluation of proposals will be needed. The ongoing accreditation process will need to produce such a plan. Recommendation 7.1f: JCOMM establish a highly visible and accessible repository where information about JCOMM standards can be found. Short term actions: Web sites are being created for the different PAs in JCOMM. However, it will be necessary to provide cross links especially when other PAs refer to standards or best practices they employ. : The Standards Forum will also address this issue of communicating results. Follow on actions: A process for posting documents that explain agreements reached, and the details of the agreements must be established. Recommendation 7.1g: As part of the accreditation process, consideration must be given to how to implement the standard across JCOMM members as rapidly as possible. Due consideration should be given to how capacity building resources may be used. Short term actions: In discussing implementation in the standards setting process, we will need to discuss whether a standard must be implemented on a community wide basis or can be done at separate times by organizations. Follow on actions: Capacity building can be a very useful mechanism to encourage a more rapid adoption of standards. Recommendation 7.1h: DMPA establish a reporting process that has members informing the group of significant activities in other programmes. Short term actions: Communicating what are the various activities in the PAs is an important activity. A number of mechanisms need to be used, including providing information in national reports, polls of Member / Member States, joint projects and personal contacts. Follow on actions: Reporting of these activities can take the form of activities listed on web pages. Recommendation 7.1i: DMPA set priority activities each intersessional period and use this as the guidance to selecting activities for its members. Short term actions: Complete the initial version of the implementation plan and vet it. Follow on actions: Each year, DMCG should update the plan with activities accomplished, and changes to reflect new or altered circumstances. Recommendation 7.1j: DMPA in collaboration with OPA, and SPA encourage the completion of quarterly reporting of other important variables following the model used by OPA. Short term actions: There can be no effective reporting until there is an organized collection of the data for the variables in question. OPA and SPA need to examine their activities to see what can and needs to be done. Follow on actions: Once the problems to be overcome are identified, activities need to take place to enable reporting of other variables. Recommendation 7.1k: DMPA collaborate with appropriate members of OPA, SPA to develop a set of data system performance metrics and implement a standard reporting of these results. Short term actions: Data systems within the PAs are different because of different origins and requirements. A study in conjunction with OPA, SPA chairs will be required to look for the common elements that can be used across all or most systems. Follow on actions: The data system managers in the PAs will need to implement regular reporting of performance. DMP 7.2: With IODE Activities Recommendation 7.2a: IODE and JCOMM formalize the relationship between the organizations. It is suggested that the chair of IODE be named a member of the DMPA-CG and the chair of the DMPA be named an Officer of IODE. Short term actions: IODE accepted the DMPA chair as an Officer in IODE and IODE Chair is a member of DMCG Follow on actions: JCOMM should be represented at IODE activities and vice versa. Recommendation 7.2b: Data management programmes of joint interest to both JCOMM and IODE be formally recognized and supported by both organizations. Short term actions: Develop a list of programmes of mutual interest and have them recognized as joint activities. Follow on actions: Develop ways that mutual support of these programmes can be accomplished. Recommendation 7.2c: IODE and JCOMM cooperate to ensure easy access and clearly described content of respective data streams and archives. Short term actions: Develop a joint list of candidate data centres that can contribute to WIS. Develop the checklist of requirements to take part in WIS. : Standards Forum in early 2008 will assist. Follow on actions: Encouraging cooperation between NMHs and IODE centres in managing data is an important step to build closer cooperation. This will occur through participation in programmes of mutual interest, such as WIS. DMP 7.3: With Other IOC Programmes Recommendation 7.3a: JCOMM and DMPA move quickly to adopt a data management strategy and to further develop an implementation plan based on the strategy as rapidly as possible. Short term actions: Complete the first version of the data management strategy and circulate it widely. Follow on actions: Use the agreed strategy to create an implementation plan. Recommendation 7.3b: JCOMM must work closely with the many other IOC programs in developing its implementation plans. Short term actions: Collaborate with IOC in the generation of their data strategy. Follow on actions: Ensure that IOC and others are aware of and contribute ideas towards changes in the strategy and updates to the implementation plan as appropriate. Recommendation 7.3c: JCOMM should collaborate with existing IOC (and WMO) capacity building activities to ensure that the marine component is included. Short term actions: Determine how JCOMM can cooperate with IOC and WMO in capacity building activities and initiate actions. Follow on actions: Provide training materials and experts as possible to support training activities. DMP 7.4: With WMO Recommendation 7.4a: DMPA and WIS should cooperate to ensure that all components of JCOMM data systems are available to WIS. Short term actions: ETDMP has a strong focus on WIS. Follow on actions: Encourage IODE centres to contribute to WIS by providing information about what they need to do and what benefits they will gain from the activity. Recommendation 7.4b: DMPA ensure appropriate experts are fully engaged in appropriate WMO activities. Short term actions: Work with WMO on the Quality Management Framework to include information of relevance to JCOMM. Appoint a member to the WMO FOrmtas group to represent JCOMM interests. : Collaborate on data exchange formats. Follow on actions: As appropriate, combine IODE and JCOMM documentation and materials. Provide experts as needed to WMO meetings and activities. DMP 7.5: With ICSU WDCs Recommendation 7.5a: DMPA initiate a discussion with WDCs to build stronger links between the observing and archive systems and how WDCs operate. This should be done with appropriate other partners. Short term actions: Start the discussion with WDC management to explain what is wanted and explore how to better align activities. Follow on actions: Continue the discussion with WDCs to ensure good coordination of activities. Recommendation 7.5b: JCOMM members support the timely assembly of data in WDCs and encourage timely updates and distribution of the global data sets and climatologies. Short term actions: Identify the target climatologies and encourage all JCOMM programmes to contribute data in a timely way. This was done at IODE-19.. Follow on actions: Ensure that timely delivery is maintained and that there is consistency in the data. DMP 7.6: With Other Programmes Recommendation 7.6: JCOMM must develop a level of interoperability in data management with other major international and significant national programmes. Short term actions: It is not possible for a coordinated JCOMM response to all initiatives. Focus energies on cooperation with WIS. Follow on actions: Select activities that provide the greatest impact. DMP 8.0: Communications Communicating activities undertaken and accomplished by JCOMM is important. It informs our partners about what we are doing and improves opportunities for cooperation. The text below provides a brief summary of the implementation sequence to realize the recommendations. Greater detail is provided in Annex DMP-8. Recommendation 8a: DMPA undertake to design and populate web pages that explain its activities. Short term actions: Develop the location and design for a DMPA web site. Follow on actions: Solicit input from DMPA members to populate web pages. As appropriate collaborate with groups (such as IODE) who have similar requirements. Recommendation 8b: DMPA will provide its representatives (and encourage the necessary national and international support) to attend meetings of other organizations and committees whose interests intersect. Short term actions: Support the organization of CLIMAR-III Follow on actions: Carry out the CLIMAR-III and assist or attend other meetings as appropriate. Annex DMP-4: Details of implementation Actions for Data and Information Exchange RecommendationTaskAction DescriptionWhoTargetStatus4.1: JCOMM should encourage instrument manufacturers to standardize the formats of the data and information coming from instruments used at sea1: Developments of standards1. Discuss what can be done to encourage standards with OPA, othersChair DMCGSep-09Informed OCG-2 and OOPC-12 of standards forum plans. Discussed opportunities of sensorML. See also 5.2a task 1 action 32. Use all opportunities to encourage manufacturers to utilize common formatsChair DMCGSep-09Not started4.2a: DMPA lead the development of the detailed plan to change GTS data reporting from TACs toTDCs1: Developments of table driven code forms1. Establish JCOMM Task Team on Table Driven CodesR. Keeley - lead + Dengwen Xia (*), E. Charpentier, H. Viola, D. Thomas (*), L. Rickards (*), S. Woodruff, N. Mikhailov (*), (*)= contact point. Will identify suitable expertOct-06Members are as stated. So far, contact points have not provided another name. Keeley provided comments to Charpentier on what was missing in current templates.2. JCOMM-II: Paragraph 7.1.8 - Intensify collaboration of the IODE NODC`s with WMO NMHS`s at the national level on JCOMM data management activitiesChair DMCG, chair IODE, Secretariats IOC, WMOSep-09See 7.3b task 1 action 13. JCOMM-II: Paragraph 7.5.3: Initiate actions for the BUFR encoding for the GTS exchange of oceanographic data, as appropriate, including in particular profiling float dataChair DMCGSep-09This action will follow on the development of BUFR templates as established by the TT in 4.2a task 1 action 1. BUFR template already developed for Argo, by Argo DMT.4. JCOMM-II: Paragraph 11.5.17 and Recommendation 11/1 (JCOMM-II): Develop an action plan for JCOMM contributions to multi-hazard warning systemsChair DMCGSep-09See 5.2a task 2 action 25. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex. Prepare a comprehensive review of existing activities and work on the required standardized data and metadata formatsChair DMCGSep-09See 6.1a task 2 action 26. MAN-V: 3.3.13 The Committee decided to proceed with the preparation of BUFR tables for non-physical parameters (action: DMPA).Chair DMCGSep-09This is an additional action for the TT of 4.2a task 1 action 1. It likely will be by establishing MT107. Provide assistance as possible to oceanographic and meteorological centres to handle data in TDCsMembers DMPA and JCOMMSep-09Argo has developed software for encoding and decoding BUFR. Software is shared8. Promote the use of TDCs in moving data from instruments at sea to shore data systemsChair DMCGSep-09Not started2: Develop the Meta-T project1. Recommend for Meta-T to prepare report for SOT-IV (April 2007) for category 1Chair Meta-TApr-07Document prepared for SOT-IV2. META-T to make recommendations to TT on table driven codes as far as BUFR requirements are concernedChair Meta-TJul-07Document prepared for SOT-IV3. MAN 4.1.4 Efforts remain to be made in order to collect all required data sets, including delayed mode data and metadata, from the fleet (recommendation: DMPA and OPA).Chair DMPASep-09Inquire from chair OPA. What do we report?4. MAN 4.1.5 Some specific activities were suggested to the Management Committee by the OOPC chair: Continue and improve collaboration with tsunami programmes (action: all PAs and DMP rapporteur)Chair DMPASep-09See 7.6 task 2 action 35. Use the lessons learned from the Meta-T project to extend the principles to other variablesChair Meta-T, chair DMCGSep-09Not started3: Developments for sea level reporting1. Review and comment to WMO/CBS ETDRC team on current CREX code formChair DMCGOct-06Chair DMCG passed comments in May 20062. MAN-V: Through the DMPA together with CBS, to develop, agree on standards including QC, and implement the CREX code format for sea level data monitoring in support of tsunami EWS (action for DMPA);Chair DMCGSep-09See 5.2a task 2 action 33. MAN 4.6.1 The Committee reviewed the status of implementation of the action plan for multi-hazard warning systems and urged the JCOMM PAs to continue to implement these actions (action for PAs).Chair DMCGSep-09See 7.3c task 2 action 24.2b: The DMPA in association with the appropriate WMO committee should evaluate MT10 for its relevance to present needs.3: Developments of table driven code forms1. Bring MT10 into conformance with ETDRC BUFR rules of todayChair DMCGMay-08This is the second task for the TT on TDC2. Extend as needed MT10 to handle GRA requirements for common variablesChair DMCGMay-08Not started3. Evaluate the utility of MT10 for transmission of ocean measurements and metadataChair DMCGSep-09Not started4.2c: Enhanced interaction between JCOMM and CBS or other appropriate WMO committees is needed to expand the scope of TDCs to more fully incorporate JCOMM considerations, including software reliability, human readability, and the archival and exchange of historical and delayed-mode data in its originally reported form.1: Developments of table driven code forms1. Propose JCOMM representative to CBS to attend CBS ET/DRC meetingsChair DMCGMay-07Hester Viola nominated and accepted by ETDRC2. JCOMM-II; Paragraph 7.1.4 Maintain a permanent list of oceanography and marine meteorology data management initiatives to promote complementarity and synergyChair ETDMPSep-09See 7.6 task 2 action 13. JCOMM-II: Paragraph 7.1.8 - Intensify collaboration of the IODE NODC`s with WMO NMHS`s at the national level on JCOMM data management activitiesChair DMCG, chair IODE, Secretariats IOC, WMOSep-09See 7.3b task 1 action 14. Encourage WMO to develop test data that can be used to determine if TDC software is operating properlyChair DMCGSep-09Not started4.3.1a: JCOMM to support the widespread use of netCDF as a data exchange format.1: Development of formats1. Promote use of netCDF in existing and new data management projects of JCOMM, IODE and other places.Chair DMCGSep-09Argo, GOSUD, OceanSITES use netCDF. WMO has established a WG on data formats. Gilbert Maudire nominated to represent JCOMM DMPA.4.3.1b: JCOMM to encourage usage of the CF convention for variable naming in netCDF and stay informed of CF updates to meet JCOMM contributors' needs.1: Development of formats1. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex. Prepare a comprehensive review of existing activities and work on the required standardized data and metadata formatsChair DMCGSep-09See 6.1a task 2 action 22. Provide links to netCDF and CF on DMPA web siteChair DMCGSep-09Not started. Web site not yet established4.3.1c: JCOMM stay informed on netCDF maintenance and developments.1: Development of formats1. Ask DMPA formats member to provide an update on netCDF developments at the next meetingChair DMCGJan-08Not started2. Work to extend the capabilities of netCDF to better support point dataChair DMCGSep-09A new version of netCDF is being issued that allows for more than one unlimited dimension3. Extend the capability of netCDF to handle other types of measurementsChair DMCGSep-09Not started4.3.2a: DMPA monitor the development of xml and encourage appropriate use for the exchange of data and metadata.1: Collaboration with WIS1. Assist WIS ET in establishing XML profile for data exchangeDavid Thomas (lead) + chairs ETDMP, IODE, DMCGMar-07Inquire of David2: Development of standard xml content1. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex. Prepare a comprehensive review of existing activities and work on the required standardized data and metadata formatsChair DMCGSep-09See 6.1a task 2 action 22. Evaluate the utility of the work on CDI by SeaDataNetChair DMCGJan-08Not started3. Get report on xml components of E2EChair DMCGJan-08Inquire of chair ETDMP4.3.2b: DMPA encourage the development of vocabularies used in xml that are as close as possible to those used in other formats.1: Collaboration with WIS1. Propose how marine XML can be used in WISDavid Thomas (lead) + chairs IODE, DMCG, ETDMPMar-07Inquire of David2. Evaluate the utility of the work on vocabularies done by SeaDataNet, MMI, and othersChair DMCGJan-08Not started3. Identify and work with oceanographic and meteorological groups experimenting with xml to standardize tags and contentsChair DMCG to leadSep-09Not started4.3.3a: JCOMM must recognize that other formats and data structures besides netCDF will have appeal and encourage activities that broaden their use and standardize their content.1: Development of standard content1. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex. Prepare a comprehensive review of existing activities and work on the required standardized data and metadata formatsChair DMCGSep-09See 6.1a task 2 action 22. Look at standardized content for BUFR and extrapolate to other formatsChair DMCGJan-08Not started. This is the 3rd job of the TT on TDC of 4.2a3. Continue to review formats that are used and encourage convergence to fewer formsMembers DMPASep-09Not started4.3.3b: JCOMM work with partners to encourage the evolution of exchange formats to more robust and stable forms, while at the same time assuring that sufficient flexibility and agility can be preserved for the archival of JCOMMs delayed mode data and metadata.1: Development of standard content1. Identify more robust exchange formats and promote use at meetings and other venueChair DMCG, members DMPAJan-08Not started Annex DMP-5: Details of implementation Actions for Data Processing RecommendationTaskAction DescriptionWhoTargetStatus5.1: DMPA needs to consult JCOMM PAs to get a full description of the versioning issue, to develop a strategy to manage versions, and to implement the strategy.1: Standardize data content1. JCOMM-II: Paragraph 7.6.2: Convene a joint JCOMM/IODE/GODAE Workshop on quality control and data assembly in conjunction with GODAR workshop in 2007. Comment: Chair DMCG to discuss with Chair SPA, Chair IODEChair ETMC, chair SPA, chair IODESep-09See 5.2a task 3 action 12. Report on results of the use of a unique data identifier in SOT and develop a proposal of extending its use for versions as appropriateChair GTSPPSep-09Not started3. Identify other schemes for dealing with data versions and evaluate their usefulness in real situations in meteorology and oceanographyChair DMCGSep-09Not started4. Develop a strategy to identify data versions, and where possible implement thisDMPA leadSep-09Not started5.2a: DMPA should encourage the development and wide spread implementation of a standard suite of data quality testing procedures.1: Work plan of ETMC1. Prepare document on common issues of quality control of surface marine variablesChair ETMC, chair DMCG, chairs GOSUD, SAMOSMay-07Discussion was initiated among the Chairs (Jan. 2007), and was continued briefly at SOT-IV between the ETMC and SAMOS Chairs2. Issue Circular Letter if deadline to meet minimum QC standards has been met (MQCS and IMMT) variablesWMO secretariatJan-07Inquire of Charpentier3. Convene a joint JCOMM/IODE/GODAE Workshop on quality control and data assembly in conjunction with GODAR workshop in 2007.Chair DMCGOct-07Levitus contacted and no such workshop is planned. Exploring links to QARTOD and SeaDataNet. Standards forum is in planning for Jan 2008 in Oostende2: Developments for sea level reporting1. Propose ESEAS QC procedures to GLOSS chair and others as best practicesChair DMCG, chair IODEJun-07ESEAS QC provided to Kevin Wong in BOM by chair DMCG. Present as part of GLOSS in Jun 2007. Believe that GLOSS is considering recommending this as a standard - inquire of Rickards2. JCOMM-II: Paragraph 11.5.17 and Recommendation 11/1 (JCOMM-II): Develop an action plan for JCOMM contributions to multi-hazard warning systemsChair DMCGSep-09Inquire3. MAN-V: Through the DMPA together with CBS, to develop, agree on standards including QC, and implement the CREX code format for sea level data monitoring in support of tsunami EWS (action for DMPA);Chair DMCGSep-09CREX format has been proposed. QC standards will be proposed to GLOSS. This is linked to 5.2a task 2 action 14. MAN 4.1.5 Some specific activities were suggested to the Management Committee by the OOPC chair: Continue and improve collaboration with tsunami programmes (action: all PAs and DMP rapporteur)Chair DMCGSep-09See 7.6 task 2 action 35. MAN 4.6.1 The Committee reviewed the status of implementation of the action plan for multi-hazard warning systems and urged the JCOMM PAs to continue to implement these actions (action for PAs).Chair DMCGSep-09See 7.3c task 2 action 26. MAN 4.6.8 To refine, publish and implement QC standards for real-time GTS transmission of SL data (action for DMPA);Chair DMCGSep-09Look at ESEAS software and get endorsement from GLOSS. This is linked to 5.2a task 2 action 13: Standardize data content1. JCOMM-II: Paragraph 7.6.2: Convene a joint JCOMM/IODE/GODAE Workshop on quality control and data assembly in conjunction with GODAR workshop in 2007. Comment: Chair DMCG to discuss with Chair SPA, Chair IODEChair ETMC, chair SPA, chair IODESep-09See 5.2a task 1 action 34: Work plan of ETMC1. JCOMM-II: Recommendation 9 (JCOMM-II): Implement the new version of the Minimum Quality Control Standards for all data collected from 1 January 2007Chair ETMCSep-09Inquire of chair ETMC2. JCOMM-II: Recommendation 9 (JCOMM-II): Review the implementation and value of the revised format and quality control standardsChair ETMCSep-09Inquire of chair ETMC5.2b: DMPA should resolve the differences in how the quality of data is indicated to best serve user needs.1: Standardize data content1. JCOMM-II: Paragraph 7.6.2: Convene a joint JCOMM/IODE/GODAE Workshop on quality control and data assembly in conjunction with GODAR workshop in 2007. Comment: Chair DMCG to discuss with Chair SPA, Chair IODEChair ETMC, chair SPA, chair IODESep-09See 5.2a task 1 action 35.2c: JCOMM to work with all appropriate bodies to converge toward more uniform schemes (and ultimately a single scheme) to indicate data quality.1: Standardize data content1. JCOMM-II: Paragraph 7.6.2: Convene a joint JCOMM/IODE/GODAE Workshop on quality control and data assembly in conjunction with GODAR workshop in 2007. Comment: Chair DMCG to discuss with Chair SPA, Chair IODEChair ETMC, chair SPA, chair IODESep-09See 5.2a task 1 action 32: Standardize quality control procedures1. JCOMM-II: Paragraph 7.6.3: Prepare a revised Expert Team Data Management Practices work plan for Implementation of OIT projectChair ETDMPSep-09See 7.6 task 2 action 22. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex. Prepare a comprehensive review of existing activities and work on the required standardized data and metadata formatsChair DMCGSep-09See 6.1a task 2 action 25.3a: DMPA develop a methodology to address how to identify exact and inexact duplicates in contemporary JCOMM data.1: Standardize data content1. JCOMM-II: Paragraph 7.6.2: Convene a joint JCOMM/IODE/GODAE Workshop on quality control and data assembly in conjunction with GODAR workshop in 2007. Comment: Chair DMCG to discuss with Chair SPA, Chair IODEChair ETMC, chair SPA, chair IODESep-09See 5.2a task 1 action 32. Report on results of the use of a unique data identifier in SOT and develop a proposal of extending its use for duplicates identification as appropriateChair DMCGSep-09See 5.1 task 1 action 2, also 5.3b task 1 action 13. Prepare an analysis of how the global data system could reorient so that all members retained their own data and provided these freely for data exchange on demandChair DMCGSep-09Not started5.3b: JCOMM consider developing a comprehensive system to uniquely tag data from all of its programmes and employ this to detect data duplications.1: Standardize data content1. Investigate broader use of CRC or identify another alternative such as CDIChair ETDMPSep-09Not started. This may come up at Standards Forum - see 5.2a task 1 action 35.4: JCOMM explore the ideas embedded in xml "bricks" as a standard way to organize and preserve information and data.1: Standardize xml content1. JCOMM-II: Paragraph 7.6.3: Prepare a revised Expert Team Data Management Practices work plan for Implementation of OIT projectChair ETDMPSep-09See 7.6 task 2 action 22. Work with oceanographic and meteorologuical groups experimenting with xml to standardize tags and contentsChair DMCG leadSep-09See 4.3.2b task 1 action 35.5: DMPA explore the value of preserving a processing history and recommend broad adoption if appropriate.1: Standardize data content1. Propose content and method for preserving processing historyChair DMCGSep-09Not started. This may come up at Standards Forum - see 5.2a task 1 action 32. Propose implementation plan for preserving processing historyChair DMCGSep-09Not started5.6a: DMPA examine existing metadata initiatives to develop a categorization that aligns with the purpose of the metadata.1: Standardize data content1. Enumerate the use categories of metadata (discovery, browse, access, etc.) to ensure they are distinguishable in purpose with as few overlaps as possibleChair DMCGSep-09Not started2. Enumerate the functional categories of metadata (vocabularies, qc standards, services, registries, etc.) to ensure they are distinguishable in purpose with as few overlaps as possibleChair DMCGSep-09Not started5.6b: DMPA use the metadata categorization to develop a plan on which metadata initiatives align with its work and become engaged in these activities.1: Develop the Meta-T project1. Meta-T to define timetable for its work planChair Meta-TNov-06Inquire2. Extend the principles learned in the Meta-T project to other variablesChair Meta-T, chair DMCGSep-09Not started5.6c: JCOMM define its requirements for discovery metadata and embody these in a formal metadata structure.1: Standardize metadata content1. JCOMM-II: Paragraph 7.6.3: Prepare a revised Expert Team Data Management Practices work plan for Implementation of OIT projectChair ETDMPSep-09See 7.6 task 2 action 22. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex. Prepare a comprehensive review of existing activities and work on the required standardized data and metadata formatsChair DMCGSep-09See 6.1a task 2 action 23. Work with appropriate partners (IODE, GEOSS, WIS) to define and implement a globally searchable discovery catalogueDMPASep-09Not started5.6d: JCOMM to encourage all agencies keeping information about instruments, platforms, etc., to place this information on-line and keep it up-to-date.1: Build the ODAS, China1. Continue to request updates on instruments employed on non-drifting ODAS platformsSecretariats IOC, WMOMar-07CL to be issued and results passed to chair DMCG and ODAS China2. Prepare a document that describes the existing xml format for ODAS metadata and recommend a standardODAS China (Chen Jixiang to consult chair ETMC)Mar-07Draft has been prepared and is under discussion with chair ETMC.2: Develop the Meta-T project1. Ensure linkage between ODAS and Meta-TChair DMCGOct-06Dengwen Xia (ODAS) member of Meta-T2. MAN-V: 3.3.7 Further consolidation is required of metadata management (e.g. ODAS, Meta-T) and IODE (SG-MEDI) and adoption of the developed standards by the relevant communities is highly needed (recommendation: DMPA).Chair DMCGSep-09See 6.1a task 1 action 43: Standardize metadata content1. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex. Prepare a comprehensive review of existing activities and work on the required standardized data and metadata formatsChair DMCGSep-09See 6.1a task 2 action 25.6e: JCOMM to develop a strategy for managing the international suite of these metadata sources so that they are easily found and used.1: Build the ODAS, China1. ODAS to contact programmes/projects (not only member states and consult with OPA)Secretariats IOC, WMOMar-07CL to be issued and results passed to chair DMCG and ODAS China2. Create links from ODAS back to instrument operator sitesODAS China (Chen Jixiang, Dengwen Xia)Jan-07Reported complete in May 2007 report2: Standardize metadata content1. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex: Establishment (under DMCG and IODE) of an ad hoc Task Team, comprising representatives of JCOMM DM, IODE and GODAE (metadata, data formats)Chair DMCG, chair IODESep-09See 7.2c task 3 action 32. MAN-V: 3.3.6 The location of the data discovery metadata records and the way those records relevant to JCOMM and/or IODE are built will have to be clarified by the DMCG and included in the JCOMM Data Management Strategy (recommendation: DMPA).Chair DMCG, chair IODESep-09See 5.6c task 1 action 33. MAN-V: 3.3.7 Further consolidation is required of metadata management (e.g. ODAS, Meta-T) and IODE (SG-MEDI) and adoption of the developed standards by the relevant communities is highly needed (recommendation: DMPA).Chair DMCGSep-09See 6.1a task 1 action 45.7a: JCOMM to work with the modeling community to define the characteristics that determine which outputs should be archived.1: Determining what model outputs should be archived1. Prepare a document that discusses model characteristics, proposes when model outputs be archived, when model outputs are disposed of and circulate to community for commentChair DMCGJan-08Not started5.7b: JCOMM to work with relevant modeling groups to develop cost-effective strategies for the storage and archival of operational model outputs and products.1: Determining what model outputs should be archived1. Survey modeling community and look for opportunities to standardize archiving of model results and productsChair DMCGJan-08Not started5.7c: Appropriate model characteristics will be archived with model results.1: Determining how to archive results1. Collaborate with modeling community to define what metadata needs to be archived with model resultsChair DMCGJan-08Not started5.7d: JCOMM will collaborate with model developers to decide the long-term value of preserving outputs of retired versions of models.1: Determining when to dispose of results fro older models1. Collaborate with modeling community to define criteria for disposing of model resultsChair DMCGJan-08Not started5.8: JCOMM and IODE seek efficiencies in the operations of former SOCs and RNODCs.1: Reconcile activities of SOCs and RNODCs1. Compare procedures of operating SOCs and RNODCs with overlapping responsibilities and propose changesChair DMCGJan-08Not started2. Implement changes in SOC operations in conjunction with appropriate changes in RNODCsDirectors of SOCs and RNODCsSep-09Not started Annex DMP-6: Details of implementation Actions for Access RecommendationTaskAction DescriptionWhoTargetStatus6.1a: JCOMM pursue the creation of standards for data discovery metadata and encourage these to be used to support interoperable catalogue services and registries.1: Develop standard discovery metadata to support MEDI1. Recommend for SG-MEDI Chair to participate in IPET-MIChair DMCGOct-06Greg Reed accepted2. Comment on SG-MEDI ISO ocean profile and IPET-MI ISO atmospheric profileChair ETDMPDec-06Inquire3. MAN-V: 3.3.6 The location of the data discovery metadata records and the way those records relevant to JCOMM and/or IODE are built will have to be clarified by the DMCG and included in the JCOMM Data Management Strategy (recommendation: DMPA).Chair DMCG, chair IODESep-09See 5.6e task 2 action 24. MAN-V: 3.3.7 Further consolidation is required of metadata management (e.g. ODAS, Meta-T) and IODE (SG-MEDI) and adoption of the developed standards by the relevant communities is highly needed (recommendation: DMPA).Chair DMCGSep-09Dengwen Xia (ODAS) member of Meta-T5. MAN-V: 3.3.7 The Committee noted that SG-MEDI and DMPA had common interests and should work together more (recommendation: DMPA).Chair DMCGSep-09Greg Reed accepted to work on our behalf2: Standardize xml content1. JCOMM-II: Paragraph 7.6.3: Prepare a revised Expert Team Data Management Practices work plan for Implementation of OIT projectChair ETDMPSep-09See 7.6 task 2 action 22. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex. Prepare a comprehensive review of existing activities and work on the required standardized data and metadata formats (as depicted in xml)Chair DMCGSep-09Define how to respond to this recommendation then ask Greg Reed for help3: Build an interoperable catalogue service1. Work with appropriate partners (IODE, GEOSS, WIS) to define and implement a globaly searchable discovery catalogueDMPASep-09See 5.6c task 1 action 36.1b: JCOMM explore how commercial search engines can be used as another way to search catalogues so that users can use Internet tools to locate data.1: Alternative searching to discover data1. Identify someone to prepare a document about how commercial search engines can be used to search catalogues and what is required to achieve this.Chair DMCGJan-08Not started2. Implement the alternative searching solution as appropriateDMPASep-09Not started6.2: JCOMM explore the implementation issues of existing or proposed methods for supporting browse functions.1: Alternative searching to discover data1. Prepare document that describes present or proposed methods for supporting browse functions.Chair DMCGJan-08Not started2. Implement the browsing solutions as appropriate.DMPASep-09Not started6.3a: Each member state of JCOMM needs to examine its ability and willingness to provide all of its data holdings on-line. Each will determine what level of support it can bring to bear.1: On-line data delivery1. Document prepared by DMPA to question member states about their ability to provide all data holdings on-line.Chair DMCGJan-08Not started. Use national reports to IODE-19 as a starting point. Use web links from WCRP Data Management Task Group for project data sets.6.3b: DMPA must keep aware of other and continuing projects to improve the access to data and where possible both participate in the projects and adopt procedures that improve access to JCOMM data.1: Work plan of ETMC1. Determine interest of GODAR in Historical Ship Data Rescue activityChair ETMCJan-07Syd Levitus was informed (via 12 Dec. 2006 e-mail) about the Recovery of Logbooks And International Marine data (RECLAIM) project. Also, a link was established to GODAR from the RECLAIM website2: On-line data delivery1. Keep abreast of developments in other international or national projectsDMPASep-09Argo provides on-line access through web interface, through OPeNDAP and ftp6.3c: DMPA encourage the compilation and adoption of a standard climatology, of the creation of specialized archives, and other products that have wide spread applicability to members.1: Work plan of ETMC1. Develop proposal for an extreme wave event archiveChair DMCG, chair ETMC, chair ETWSMar-07The basic proposal was agreed to both by ETWS-II and ETMC-II, with some suggestions for fine-tuning and next steps.2. Implement the extreme wave event archive as possibleChair DMCG, chair ETMC, chair ETWSSep-09Not started6.3d: JCOMM needs to ensure that all information required for the correct interpretation of data be included when data are delivered to clients.1: On-line data delivery1. Prepare document to provide guidelines on what information is required for correct interpretation of delivered dataChair DMCG, chair ETDMPMar-07A document prepared for IODE-19 (IOC/IODE-XIX/22 add.) describes technical details to allow connection to on-line sources. Annex DMP-7: Details of implementation Actions for Co-ordination and Linkages RecommendationTaskAction DescriptionWhoTargetStatus7.1a: JCOMM develop a formal mechanism to ensure regular exchanges of information and ideas on how data are managed between the groups in OPA, SPA, and DMPA.1: Build the ODAS, China1. Alert OPA to the importance of metadata for historical dataChair DMCGMar-07Verbal presentation made at OCG-22: Inform groups within JCOMM1. JCOMM-II; Paragraph 7.1.4 Maintain a permanent list of oceanography and marine meteorology data management initiatives to promote complementarity and synergyChair DMCG, chair ETDMP, chair ETMCSep-09See 7.6 task 2 action 12. JCOMM-II: Paragraph 7.1.6 Encourage synergies between ETMC and ETDMPChair DMCG, chair ETDMP, chair ETMCSep-09Not evident where commonalities are3. JCOMM-II Paragraphs 7.6.7 and 7.6.10 : Ensure wider participation of GTSPP and GOSUD in Expert Team Data Management Practices pilot projects, carrying out the functions of GTSPP and GOSUD data sources under the E2EDM system prototypeChair DMCG, chair ETDMPSep-09See 7.4a task 2 action 54. JCOMM-II: Paragraph 8.1.15 Establish and ensure coordination of capacity building with Programme Areas Observations, Data Management, and ServicesDMPA CB RapporteurSep-09Inquire5. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex: Establishment (under DMCG and IODE) of an ad hoc Task Team, comprising representatives of JCOMM DM, IODE and GODAE (metadata, data formats)Chair DMCG, chair IODESep-09See 7.2c task 3 action 36. MAN-V: 3.3.9 The Committee also encouraged DMPA and other Programme Areas to engage in more unified data management operations (recommendation: DMPA and other PAs).Chair DMCGSep-09Chair DMCG attended SPA-3 and OCG-27. MAN-V: 3.4.5 The Committee recognized that there is a need to better define cross-PA issues and urged the PAs to define a strategic and implementation plan for PA cross-cutting activities and interactions (recommendation: PAs).Chair DMCGSep-09Strategy document was circulated to other PAs. Implementation plan will identify initial areas for work8. JCOMM-II : Paragraph 7.1.17 : Organize a Third JCOMM Workshop on Advances in Marine Climatology to be held in 2007Chair ETMCMay-08ETWS-II, ETMC-II, and SOT-IV (Mar.-Apr. 2007) were briefed on workshop plans. As of Sep 2007 local arrangements, workshop goals and structure are completed.7.1b: JCOMM must consider interoperability issues with satellite data providers so that satellite and in-situ data are easily compared.1: Interactions with satellite community1. Involve a satellite data centre as E2E prototype data providerTT E2EDM, DMCG satellite rapporteurMay-07Inquire2. Propose possible GHRSST-like continuous intercomparison/validation for other variablesDMCG satellite rapporteurJul-07Inquire2: Interoperability of in-situ with satellite data1. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex: Establishment (under DMCG and IODE) of an ad hoc Task Team, comprising representatives of JCOMM DM, IODE and GODAE (metadata, data formats)Chair DMCG, chair IODESep-09See 7.2c task 3 action 37.1c: JCOMM should first adopt an existing standard or best practice, as a second option adapt an existing one, or failing that create its own.1: Adoption of standards1. Promote the examination and adoption of existing standardsChair DMCGOct-07Planning underway for a standards forum See 5.2a task 1 action 37.1d: JCOMM develop a process to accredit standards to be recommended for use across all activities.1: Adoption of standards1. Prepare a document on a process to accredit standards and vet this with JCOMMChair DMCGJan-08Use standards forum as first instance of process. Document it. See 5.2a task 1 action 37.1e: DMPA develop a plan for coordination of the accreditation process and carrying out of evaluations.1: Adoption of standards1. Prepare a plan to coordinate the accreditation process and vet this with JCOMMChair DMCGJan-08Use standards forum as first instance of process. Document it. See 5.2a task 1 action 37.1f: JCOMM establish a highly visible and accessible repository where information about JCOMM standards can be found.1: Adoption of standards1. Work with IODE Project Office to build repositoryChair DMCGJan-08See 8a task 17.1g: As part of the accreditation process, consideration must be given to how to implement the standard across JCOMM members as rapidly as possible. Due consideration should be given to how capacity building resources may be used.1: Adoption of standards1. Prepare implementation plans for adopting standards that assess adverse impacts of standards and suggest how this can be minimizedChair DMCGJan-08Not started. See 5.2a task 1 action 37.1h: DMPA establish a reporting process that has members informing the group of significant activities in other programmes.1: Inform groups within JCOMM1. JCOMM-II; Paragraph 7.1.4 Maintain a permanent list of oceanography and marine meteorology data management initiatives to promote complementarity and synergyChair DMCG, chair ETDMP, chair ETMCSep-09See 7.6 task 2 action 17.1i: DMPA set priority activities each intersessional period and use this as the guidance to selecting activities for its members.1: Review of activities1. Update the implementation plan prior to each DMCG and use plan to guide activitiesChair DMCGJan-08First version of implementation plan in preparation7.1j: DMPA in collaboration with OPA, and SPA encourage the completion of quarterly reporting of other important variables following the model used by OPA.1: Review of activities1. Review what variables are not now in OPA quarterly report and suggest actions to improve thisChair DMCGJan-08Raised at OCG-2. No further actions7.1k: DMPA collaborate with appropriate members of OPA, SPA to develop a set of data system performance metrics and implement a standard reporting of these results.1: Review of activities1. Propose a set of performance metrics for data systems for commentChair DMCGJan-08Raised at OCG-2. No further actions7.2a: IODE and JCOMM formalize the relationship between the organizations. It is suggested that the chair of IODE be named a member of the DMPA-CG and the chair of the DMPA be named an Officer of IODE.1: Encourage closer collaboration with IODE1. JCOMM-II: Paragraph 7.1.8 - Intensify collaboration of the IODE NODC`s with WMO NMHS`s at the national level on JCOMM data management activitiesChair DMCG, chair IODE, Secretariats IOC, WMOSep-09See 7.3b task 1 action 12. JCOMM-II : Paragraph 7.7.1 and Recommendation 7/2 (JCOMM-II): Develop a JCOMM data management strategy to be closely coordinated with those of IODE and WMO Information systemChair DMCG, chair IODE, WISSep-09See 7.3b task 2 action 13. Establish formal relationship with IODEChair DMCG, chair IODESep-09Chair IODE installed as member of DMCG at DMCG-2. Chair DMCG installed as IODE Officer following IODE-197.2b: Data management programmes of joint interest to both JCOMM and IODE be formally recognized and supported by both organizations.1: Encourage closer collaboration with IODE1. Develop list of programmes of mutual interest to IODE and JCOMM and suggested ways to support theseChair DMCG, chair IODESep-09Not started7.2c: IODE and JCOMM cooperate to ensure easy access and clearly described content of respective data streams and archives.1: Work plan of ETDMP1. Propose possible participation of ODIN networks as E2E data providers, possibly through EB projectsDMCG CB rapporteurMay-07Inquire2: Collaboration with WIS1. Provide checklist of requirements to be a DCPC of WISDavid ThomasMar-07Inquire3: Encourage cooperation with IODE1. JCOMM-II; Paragraph 7.1.4 Maintain a permanent list of oceanography and marine meteorology data management initiatives to promote complementarity and synergyChair DMCG, chair ETDMP, chair ETMCSep-09See 7.6 task 2 action 12. JCOMM-II: Paragraph 7.1.8 - Intensify collaboration of the IODE NODC`s with WMO NMHS`s at the national level on JCOMM data management activitiesChair DMCG, chair IODE, Secretariats IOC, WMOSep-09See 7.3b task 1 action 13. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex: Establishment (under DMCG and IODE) of an ad hoc Task Team, comprising representatives of JCOMM DM, IODE and GODAE (for standard metadata, data formats)Chair DMCG, chair IODESep-09DMCG-2 adopted IODE metadata representative (Greg Reed) to represent DMPA as well. Data formats are being tackled by a WMO WG. See 4.3.1a task 1 action 17.3a: JCOMM and DMPA move quickly to adopt a data management strategy and to further develop an implementation plan based on the strategy as rapidly as possible.1: Work plan of ETDMP1. Develop membership list of ETDMPChair ETDMPOct-06Inquire2. Invite nominations for ETDMP renewalSecretariats IOC, WMODec-06Inquire3. Prepare work plan and proposals to improve connections between E2E prototype, WIS and othersChair ETDMPJan-07Inquire4. Present checklist document to IODE-19 (12-16 March 2007)Chair ETDMP, chair DMCGMar-07Document was presented. Some improvements in document are needed. Keeley and Mikhailov to undertake5. Identify additional data providers from existing data portal providers (projects)Chair DMCGMay-07Invited IODE members to respond. None yet6. Continue technical development of E2E prototypeTT E2EDMMay-09Inquire2: Work plan of ETMC1. Establish new JCOMM Task Team on MCSS including IMMT and MQCSChair ETMCAug-07Terms of Reference and membership agreed to at ETMC-II (Mar. 2007) with minor changes, and by the VOS Panel during SOT-IV. SOT suggested addition of 3 members and of VOSClim issues to the ToR. A 3-year project plan is to be produced by the TT-DMVOS co-Chairs by Aug. 2007.2. Explore connection between ETSI and ETMC (GDSIDB)Chair ETMCAug-07ETMC-II proposed a new Task Team on Marine and Ocean. Climatological Summaries. ETSI Chair agreed to help develop the ToR for TT-MOCS (by Aug. 2007). Also, the ETMC Chair briefed ETSI-III/GDSIDB-XI (Mar. 2007) on relevant ETMC-II discussions.3: Development of a data management strategy1. Prepare revised draft Strategy and circulate to JCOMM, IODE, ... for commentsChair DMCGDec-06Document revised by chair DMCG and distributed by C. Clark on 22 Dec 20062. Revise draft Strategy based on received comments and distribute final version to JCOMM co-PresidentsChair DMCGFeb-07Comments received. Consolidate them into new version and issue. Waiting for remarks from Clark.3. Prepare draft implementation planChair DMCG and membersApr-07Initial plan as xml is under construction4. JCOMM-II : Paragraph 7.7.1 and Recommendation 7/2 (JCOMM-II): Develop a JCOMM data management strategy to be closely coordinated with those of IODE and WMO Information systemChair DMCG, chair IODE, WISSep-09See 7.3b task 2 action 15. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex: Develop a rolling implementation plan, with the wider community, for the integration of new technological developments in data and product managementChair DMCG, chair IODE, WISSep-09See 7.3b task 2 action 36. JCOMM-II: Recommendation 9 (JCOMM-II): Implement the new version of the International Maritime Meteorological Tape format for all data collected as from 1 January 2007Chair ETMCSep-09See 5.2a task 4 action 17. MAN-V: 3.3.10 The Committee noted the IOC Strategic Plan for Oceanographic Data and Information Management should be made as far as possible consistent with the JCOMM Data Management strategy (recommendation: DMPA).Chair DMPASep-09See 7.3b task 1 action 37.3b: JCOMM must work closely with the many other IOC programs in developing its implementation plans.1: Develop JCOMM data management strategy1. JCOMM-II: Paragraph 7.1.8 - Intensify collaboration of the IODE NODC`s with WMO NMHS`s at the national level on JCOMM data management activitiesDMCGSep-09Encouraged this at IODE-192. JCOMM-II: Paragraph 7.2.2: Work with IODE and IOC to develop a data management strategy document as a guide for complementary progress between relevant WMO and IOC programmesDMCGSep-09Data Management strategy for IOC presented at IOC in Jun 20073. MAN-V: 3.3.10 The Committee noted the IOC Strategic Plan for Oceanographic Data and Information Management should be made as far as possible consistent with the JCOMM Data Management strategy (recommendation: DMPA).Chair DMPASep-09Assisted in review of draft IOC data management strategy2: Develop JCOMM data management implementation plan1. JCOMM-II : Paragraph 7.7.1 and Recommendation 7/2 (JCOMM-II): Develop a JCOMM data management strategy to be closely coordinated with those of IODE and WMO Information systemChair DMCG, chair IODE, WISSep-09First version is in preparation2. JCOMM-II: Paragraph 11.1.5: Incorporate the appropriate actions within the Plans prepared by GCOS and by the GEO into the activities of the relevant JCOMM coordination groupsChair DMCGSep-09This is being done by chair DMCG3. JCOMM-II: Recommendation 2 (JCOMM-II) and Annex: Develop a rolling implementation plan, with the wider community, for the integration of new technological developments in data and product managementChair DMCG, chair IODE, WISSep-09This is underway7.3c: JCOMM should collaborate with existing IOC (and WMO) capacity building activities to ensure that the marine component is included.1: DMCG Capacity Building1. Organize training course for E2E prototype data providers (Ostend, Belgium)Chair ETDMP (lead) + chair DMCGOct-07Tentative schedule of training. Waiting for suitable times and numbers of participants2. Identify missing digital library material and course material for OT related to JCOMM subject areasMurray Brown, chair DMCG, DMPA CG RapporteurMar-07Inquire3. Investigate possible collaboration with COMET and MetEd programme (related to meteorology training)OceanTeacher DM Editor (Murray Brown) - lead + DMPA CB Rapporteur + Dave ThomasMar-07Inquire4. JCOMM-II: Paragraphs 7.2.3 and 7.2.5, and Recommendation 7/1 (JCOMM-II): Organize training workshops through the IOC Project Office for IODEDMPA CB RapporteurSep-09Inquire5. JCOMM-II: Paragraph 8.1.7: Evaluate all specific JCOMM training events, based on the of questionnaires developed, and involving the donors, the recipients and the executing agenciesDMPA CB RapporteurSep-09Inquire6. JCOMM-II: Paragraph 8.1.2 : Continue, expand and formalize regional requirements surveysDMPA CB RapporteurSep-09Inquire7. JCOMM-II: Paragraph 8.1.3: Continue regional development projects within the broader context of the global programme for natural disaster mitigationDMPA CB RapporteurSep-09Inquire8. JCOMM-II: Paragraph 8.1.15 Establish and ensure coordination of capacity building with Programme Areas Observations, Data Management, and ServicesDMPA CB RapporteurSep-09See 7.1a task 2 action 49. JCOMM-II: Paragraph 8.3.1: Develop a project on early warning system to mitigate flooding and earthquake effects on the African coastDMPA CB RapporteurSep-09Inquire10. MAN-V: 3.3.3 The Committee agreed to task the DMCG with the coordination of the submission of materials to OceanTeacher (action: DMPA).DMPA CB RapporteurSep-09Inquire2: Developments for sea level reporting1. Identify material on multi hazard warning and mitigation for OceanTeacher (see also 2.4)Chair ETWSMar-07Inquire2. MAN 4.6.1 The Committee reviewed the status of implementation of the action plan for multi-hazard warning systems and urged the JCOMM PAs to continue to implement these actions (action for PAs).Chair DMCGSep-09Work was done on CREX7.4a: DMPA and WIS should cooperate to ensure that all components of JCOMM data systems are available to WIS.1: Work plan of ETDMP1. Submit draft checklist of technical requirements to be met by E2E prototype data providers, discuss with DMCG Chair and finalizeChair ETDMP, chair DMCGMar-07Prepared for IODE-192. Submit document to IODE and invite IODE data centres to participate in E2E prototypeChair DMCG, chair ETDMPMar-07See 7.3a task 1 action 42: Collaboration with WIS1. Submit list of candidate DCPCs (see 2.2.i) to WMOChair DMCG (lead) + chair ETDMPMay-07Inquire of chair ETDMP2. Agree on accreditation process for DCPCs suggested by JCOMM (and IODE)Chair DMCG (lead) + Dave Thomas + Chair ET-WISC (H. Knottenberg, Germany)Jun-07Inquire3. Discuss linkages of DMCG, WIS and other major programmesChair DMCG (lead) + S. PouliquenJun-07Inquire4. JCOMM-II: Paragraph 7.5.16 : Provide an appropriate JCOMM participation in the CBS activities related to data exchangeChair DMCGSep-09See 7.4b task 2 action 25. JCOMM-II Paragraphs 7.6.7 and 7.6.10 : Ensure wider participation of GTSPP and GOSUD in Expert Team Data Management Practices pilot projects, carrying out the functions of GTSPP and GOSUD data sources under the E2EDM system prototypeChair DMCG, chair ETDMPSep-09GTSPP and GOSUD data at GDAC in IFREMER are available in E2E prototype system6. JCOMM-II : Paragraph 7.7.1 and Recommendation 7/2 (JCOMM-II): Develop a JCOMM data management strategy to be closely coordinated with those of IODE and WMO Information systemChair DMCG, chair IODE, WISSep-09See 7.3b task 2 action 17. JCOMM-II: Paragraph 11.1.5: Incorporate the appropriate actions within the Plans prepared by GCOS and by the GEO into the activities of the relevant JCOMM coordination groupsChair DMCGSep-09See 7.3b Task 2 Action 28. MAN-V: 3.3.8 WMO Secretariat to prepare a questionnaire to Member States represented on JCOMM asking for information on potential JCOMM DCPCs for marine meteorological and oceanographic variables (action: Secretariats and DMPA).Chair DMCGSep-09Inquire of secretariat7.4b: DMPA ensure appropriate experts are fully engaged in appropriate WMO activities.1: Take part in WMO QMF work1. Prepare assessment table of WMO and IOC documentsSecretariat WMO, DMCG membersJan-07Table sent by secretariat. Reviewed by DMCG chair2. Identify first contact points for IOC and WMO documentsDMCG membersFeb-07Done by DMCG3. Co-ordinate assessment processSecretariats, contactsMar-07Awaiting action by DMCG. There are a number of manuals that are joint with IODE. IODE is starting a process to review these as well2: Collaboration with WIS1. Investigate participation of ETDMP expert(s) in ET-WISC, ET-CTSChair ETDMP (lead), + chair DMCG + Dave ThomasDec-06Inquire of chair ETDMP2. JCOMM-II: Paragraph 7.5.16 : Provide an appropriate JCOMM participation in the CBS activities related to data exchangeChair DMCGSep-09ETDMP is leading this3: Collaboration with WMO1. JCOMM-II: Paragraph 7.2.6: Arrange for ongoing JCOMM representation on ICG/WISChair DMCGSep-09Check with secretariat if chair ETDMPs work meets this2. Collaborate on WMO exchange formats working groupGilbert MaudireSep-09See 4.3.1a task 1 action 17.5a: DMPA initiate a discussion with WDCs to build stronger links between the observing and archive systems and how WDCs operate. This should be done with appropriate other partners.1: Define roles with respect to WDC1. Propose relationship to WDCschair DMCGSep-09Proposed this to IODE-19. Need to make contact with ICSU. A meeting of WDCs is being planned. I proposed to Peter P that IODE, JCOMM also attend.7.5b: JCOMM members support the timely assembly of data in WDCs and encourage timely updates and distribution of the global data sets and climatologies.1: Define roles with respect to WDC1. Encourage timely delivery of data to IODE centres exchanging with WDCsChair DMCGSep-09Presented to OCG-2. Presented to IODE-197.6: JCOMM must develop a level of interoperability in data management with other major international and significant national programmes.1: Contribute to GEOSS development1. Participate in GEOSS teleconferences as per invitation received from Secretariats (and based upon their availability and expertise)DMCG membersDec-07Thomas participated in Oct. Very sporadic participation. Need another plan2: Inform other groups1. JCOMM-II; Paragraph 7.1.4 Maintain a permanent list of oceanography and marine meteorology data management initiatives to promote complementarity and synergyChair DMCG, chair ETDMP, chair ETMCSep-09Not started2. JCOMM-II: Paragraph 7.6.3: Prepare a revised Expert Team Data Management Practices work plan for Implementation of OIT projectChair ETDMPSep-092006-07 work plan prepared at OCG-23. MAN 4.1.5 Some specific activities were suggested to the Management Committee by the OOPC chair: Continue and improve collaboration with tsunami programmes (action: all PAs and DMP rapporteur)Chair DMPASep-09Not started Annex DMP-8: Details of implementation Actions for Communications RecommendationTaskAction DescriptionWhoTargetStatus8a: DMPA undertake to design and populate web pages that explain its activities.1: Develop communications tools1. Establish Task Team for the DMPA web presence to discuss building DMPA web site and sub-sites for ETsSecretariats (lead) + chairs DMCG, ETDMP, ETMCOct-06TT is populated2. Prepare document describing web site layout, structure and content guidelines and distribute to DMCG membersTask Team for the DMPA web presence + SecretariatsOct-06IOC secretariat started3. Create DMPA web presence templatesSecretariats (lead) + chairs DMCG, ETDMP, ETMCNov-06Inquire4. Start to populate DMPA web sitesSecretariats + members DMCGDec-06Waiting web site development5. MAN-V: 3.5.6 The Committee agreed that the division of information and avoidance of duplication between the main JCOMM web site and more specific sub-web sites would need to be reviewed and revised on a continuing basis (recommendation: Secretariats and PAs).Secretariats and chair DMCGSep-09Waiting web site development6. MAN-V: 3.5.8 The Committee recommended the preparation and publishing of a Communication strategy document (recommendation: Secretariats, JCOMM co-presidents and PAs coordinators).Co-presidents and chair DMCGSep-09Nothing seen yet8b: DMPA will provide its representatives (and encourage the necessary national and international support) to attend meetings of other organizations and committees whose interests intersect.1: Work plan of ETMC1. CLIMAR-3 organizationChair ETMCMay-08Site, date settled2: Work plan of ETMC1. JCOMM-II : Paragraph 7.1.17 : Organize a Third JCOMM Workshop on Advances in Marine Climatology to be held in 2007Chair ETMCSep-09To be held in Poland, May 2008. As of Sep 2007, Poland has local arrangements completed and scientific programme organized     JCOMM/MAN-VI/Doc 3.1 (3) page  PAGE 2 JCOMM/MAN-VI/Doc 2(2) page  PAGE 3 JCOMM/MAN-VI/Doc 3.1 (3) ef{|   ) C D J K W ] ` İĠܕppbTbC5h9CJOJQJ^JaJ h:5h9CJOJQJ^JaJh9CJOJQJ^JaJh]CJOJQJ^JaJ&h:5h95CJOJQJ\^JaJ h]5CJOJQJ\^JaJh9h9mH sH h9CJOJQJaJmH sH 'jDh9CJOJQJUaJmH sH h9CJaJmH sH jL2h9CJUaJh9mH sH jh9U%h95CJOJQJ^JaJmH sH e  ] ^ _ ` ? @ gdh/$a$gd9gd9  7 gd9$ 7 a$gd9yDD`   * ͼyoeyWI7#hRrhRr5CJOJQJ^JaJhh/CJOJQJ^JaJh$lCJOJQJ^JaJh9OJQJ^Jh$lOJQJ^Jhh9OJQJ^Jh9CJOJQJ^JaJ&h:5h96CJOJQJ]^JaJ&hh96CJOJQJ]^JaJ hM6CJOJQJ]^JaJ hh9CJOJQJ^JaJ hK#h9CJOJQJ^JaJ h$l5CJOJQJ\^JaJ R S ` a  x y  4 5 *+Nh^hgdh/ & Fgdh/ & Fgdh/ hgdh/gdh/* Q S ` 4  &$(?,------. . . ...>.?.@.`.a.1噑yjy`yhh/0JOJQJjhh/OJQJUjhh/OJQJUhh/OJQJnHtHhh/OJQJhh/5OJQJhh/B*CJOJQJphhh/CJOJPJQJhRrCJOJQJh@UCJOJQJh$lCJOJQJhh/5CJOJQJhh/CJOJQJhRrhh/5CJOJQJaJ%NOKL$$((@,A,-----+0,01 1$^gdh/ & F 1$gdh/ n1$^gdh/ h1$^gdh/ & Fgdh/gdh/112E22.3/3#4$444s5t5557799 ^`gdh/ & Fgdh/ & F h^`gdh/gdh/ nh1$^h`gdh/h1$^h`gdh/ & F1$gdh/1$gdh/1$4s55588M;V;_;;;<=?EE*F+F,FKFLFFmJnJJJ5L7LL MMNNRPSPTP[Pݻݮr`#h@Uh@U5CJOJQJ^JaJh9CJOJQJ^JaJhRrCJOJPJQJhh/B*CJOJQJphhh/CJOJPJQJhh/0JCJj}hh/CJUjhh/CJUhh/CJPJhh/CJPJh hh/6CJ hh/CJhh/5CJOJQJhh/OJQJhh/CJOJQJ%9;;<<==??@@cBdBCCFFyGHHHImJnJgdh/ & Fgdh/ ^gdh/ ^`gdh/ & Fgdh/nJJJ6L7LMMNNSP\P]P^PyPzP{PPPPPPPVQ ! gd@U$a$gd@Ugd@U$a$gd@UH$gdh/ & FH$gdh/gdh/ hgdh/[P^PtPxPyPPPPPPPPPPPQQQQ4Q̾l\N\2l\6jrh+Ch@U>*B*CJUmHnHphuh+Ch@UCJmHnHuh+Ch@U0JCJmHnHu(jh+Ch@U0JCJUmHnHuh+Ch@UCJ^Jjh+Ch@UCJU^Jh@U5CJ^J#hRrh@U5CJOJQJ^JaJh@UCJ^Jh+Ch@U5CJ ^JaJ h@U5CJ ^JaJ h@U5CJ,^JaJ,h+Ch@U5CJ,^JaJ,h@U5CJOJQJ^JaJ4Q5Q6QPQQQRQSQTQUQVQWQXQtQuQvQwQQQQQQQQQܹܤ|n|R|<ܹ*jh+Ch@UCJUmHnHu6jlh+Ch@U>*B*CJUmHnHphuh+Ch@UCJmHnHuh+Ch@U0JCJmHnHu/h+Ch@UCJOJPJQJmHnHsH tH u(jh+Ch@U0JCJUmHnHuh@UCJmHnHu*jh+Ch@UCJUmHnHu'jh+Ch@UCJUmHnHuh+Ch@UCJmHnHuQQQQQQQQQRRRRRRR R!R"R#R$R@RARõÙÉu_uRuõh@UCJmHnHu*jh+Ch@UCJUmHnHu'jh+Ch@UCJUmHnHuh+Ch@UCJmHnHu6jfh+Ch@U>*B*CJUmHnHphuh+Ch@UCJmHnHuh+Ch@U0JCJmHnHu/h+Ch@UCJOJPJQJmHnHsH tH u(jh+Ch@U0JCJUmHnHuVQQ"RRRFSSSBTTTMUUUEVVV*B*CJUmHnHphuh+Ch@UCJmHnHu/h+Ch@UCJOJPJQJmHnHsH tH uh@UCJmHnHu*jh+Ch@UCJUmHnHu'jh+Ch@UCJUmHnHuh+Ch@UCJmHnHuh+Ch@U0JCJmHnHu(jh+Ch@U0JCJUmHnHu6j`h+Ch@U>*B*CJUmHnHphuRRRRRRRRRRRSSSS$S%S&S@SASBS룋~unuZ~uRER7Ejh+Ch@UUjh+Ch@UUh+Ch@U'jTh+Ch@U>*B*Uph h+Ch@Uh+Ch@U0Jjh+Ch@U0JU/h+Ch@UCJOJPJQJmHnHsH tH u(jh+Ch@U0JCJUmHnHuh@UCJmHnHu*jh+Ch@UCJUmHnHuh+Ch@UCJmHnHu'jh+Ch@UCJUmHnHuBSCSDSESFSGSHSdSeSfSgSxSySzSSSSSSSSSSSSSSSSSSSSSSSSSSTT»§Ÿퟑ»}Ÿo»jh+Ch@UU'jHh+Ch@U>*B*Uphjh+Ch@UUh+Ch@U'jNh+Ch@U>*B*Uph h+Ch@Uh+Ch@U0J(h+Ch@UOJPJQJmHnHsH tH jh+Ch@U0JUjh+Ch@UU h@U(TTT T!T"TT?T@TATBTCTDT`TaTbTcTlTmTnTTTTTTTTTTTTTTTͲޘՑ}oޘՑ['j6h+Ch@U>*B*Uphjh+Ch@UU'j<h+Ch@U>*B*Uph h+Ch@U(h+Ch@UOJPJQJmHnHsH tH  h@Ujh+Ch@UUjh+Ch@UUh+Ch@Uh+Ch@U0Jjh+Ch@U0JU'jBh+Ch@U>*B*Uph#TTTTTTTTTTTTUUUU+U,U-UGUʵfVBV'jh+Ch@UCJUmHnHuh+Ch@UCJmHnHu6j0h+Ch@U>*B*CJUmHnHphuh+Ch@UCJmHnHuh+Ch@U0JCJmHnHu(jh+Ch@U0JCJUmHnHu(h+Ch@UOJPJQJmHnHsH tH jh+Ch@U0JU h@Ujh+Ch@UUjh+Ch@UUh+Ch@UGUHUIUJUKULUMUNUOUkUlUmUnUUUUUUUUUUִkcVcHVCV h@Ujh+Ch@UUjh+Ch@UUh+Ch@U'j*h+Ch@U>*B*Uph h+Ch@Uh+Ch@U0Jjh+Ch@U0JU/h+Ch@UCJOJPJQJmHnHsH tH u(jh+Ch@U0JCJUmHnHuh@UCJmHnHu'jh+Ch@UCJUmHnHu*jh+Ch@UCJUmHnHuUUUUUUUUUUUUUUUUUUUUVVVV#V$V%V?V@VAVBVCVDVEVFVGVcVdVպղ~ղpjh+Ch@UU'jh+Ch@U>*B*Uph h@Ujh+Ch@UUjh+Ch@UUh+Ch@U'j$h+Ch@U>*B*Uph h+Ch@Uh+Ch@U0Jjh+Ch@U0JU(h+Ch@UOJPJQJmHnHsH tH %dVeVfVrVsVtVVVVVVVVVVVVVVVVVVVVVVVVVV W W WWWͲޘՑ}oޘՑ['j h+Ch@U>*B*Uphjh+Ch@UU'jh+Ch@U>*B*Uph h+Ch@U(h+Ch@UOJPJQJmHnHsH tH  h@Ujh+Ch@UUjh+Ch@UUh+Ch@Uh+Ch@U0Jjh+Ch@U0JU'jh+Ch@U>*B*Uph#WWW6W7W8W9W:W;WWZW[W\W]WkWlWmWWWWWWWWWWWWWWWWWWWWWʵʬʬʵʬoʬaj}h+Ch@UU'jh+Ch@U>*B*Uphjh+Ch@UU'jh+Ch@U>*B*Uph h+Ch@Uh+Ch@U0J(h+Ch@UOJPJQJmHnHsH tH jh+Ch@U0JU h@Ujh+Ch@UUjh+Ch@UUh+Ch@U&WWWWWWXXXX XXX)X*X+X,X-X.XѼr^rH^;^h@UCJmHnHu*jwh+Ch@UCJUmHnHu'jh+Ch@UCJUmHnHuh+Ch@UCJmHnHu6jh+Ch@U>*B*CJUmHnHphuh+Ch@UCJmHnHuh+Ch@U0JCJmHnHu(jh+Ch@U0JCJUmHnHu(h+Ch@UOJPJQJmHnHsH tH jh+Ch@U0JUjh+Ch@UU.X/X0X1XMXNXOXPX]X^X_XyXzX{X|X}X~XXXXXXXXXXXXXXXXXXXѶѮyeѮWyjkh+Ch@UU'jh+Ch@U>*B*Uph(h+Ch@UOJPJQJmHnHsH tH  h@Ujqh+Ch@UUjh+Ch@UUh+Ch@U'jh+Ch@U>*B*Uph h+Ch@Uh+Ch@U0Jjh+Ch@U0JU/h+Ch@UCJOJPJQJmHnHsH tH u"XXXXXXXXYYYYYYY Y!Y"Y>Y?Y@YAYfYgYhYYYYYYYYYǺǬϒ~Ǻpϒ[(jh+Ch@U0JCJUmHnHuj_h+Ch@UU'jh+Ch@U>*B*Uph(h+Ch@UOJPJQJmHnHsH tH  h@Ujeh+Ch@UUjh+Ch@UUh+Ch@Ujh+Ch@U0JU'jh+Ch@U>*B*Uph h+Ch@Uh+Ch@U0J YYYYYYYYYYYYYYYYYYZZŰviQD;4; h+Ch@Uh+Ch@U0Jjh+Ch@U0JU/h+Ch@UCJOJPJQJmHnHsH tH uh@UCJmHnHu*jYh+Ch@UCJUmHnHu'jh+Ch@UCJUmHnHuh+Ch@UCJmHnHu(jh+Ch@U0JCJUmHnHu6jh+Ch@U>*B*CJUmHnHphuh+Ch@UCJmHnHuh+Ch@U0JCJmHnHuZZZ#Z$Z%Z?Z@ZAZBZCZDZEZFZGZcZdZeZfZ~ZZZZZZZZZZZZZZZZZͲޘՑ}oޘՑ['jh+Ch@U>*B*UphjMh+Ch@UU'jh+Ch@U>*B*Uph h+Ch@U(h+Ch@UOJPJQJmHnHsH tH  h@UjSh+Ch@UUjh+Ch@UUh+Ch@Uh+Ch@U0Jjh+Ch@U0JU'jh+Ch@U>*B*Uph#ZZZZZZZZZ[[[[[ [![-[.[/[I[J[K[L[M[N[O[P[Q[m[n[o[p[[[[[[[[ʵʬʬʵʬoʬaj;h+Ch@UU'jh+Ch@U>*B*UphjAh+Ch@UU'jh+Ch@U>*B*Uph h+Ch@Uh+Ch@U0J(h+Ch@UOJPJQJmHnHsH tH jh+Ch@U0JU h@UjGh+Ch@UUjh+Ch@UUh+Ch@U&[O[[\T\\\\\\__``ccdcQ & F 8EƀPӨ()^gd@Ugd@Ugd@Ugd@Ugd@U ! gd@Ugd@U[[[[[[[[[[[[[[[[[[[\\\\\ \!\2\ȭȥ}m_mC}m6jh+Ch@U>*B*CJUmHnHphuh+Ch@UCJmHnHuh+Ch@U0JCJmHnHu(jh+Ch@U0JCJUmHnHu h@Uj5h+Ch@UUh+Ch@U'jh+Ch@U>*B*Uph h+Ch@Uh+Ch@U0J(h+Ch@UOJPJQJmHnHsH tH jh+Ch@U0JUjh+Ch@UU2\3\4\N\O\P\Q\R\S\T\U\V\r\s\t\u\\\\\\\\\ܹܤ|n|R|<ܹ*j)h+Ch@UCJUmHnHu6jh+Ch@U>*B*CJUmHnHphuh+Ch@UCJmHnHuh+Ch@U0JCJmHnHu/h+Ch@UCJOJPJQJmHnHsH tH u(jh+Ch@U0JCJUmHnHuh@UCJmHnHu*j/h+Ch@UCJUmHnHu'jh+Ch@UCJUmHnHuh+Ch@UCJmHnHu\\\\\\\\_________ ` ```ļmZH#h@Uh@U5CJOJQJ^JaJ$h@Uh@U0JCJOJQJ^JaJ/jh@Uh@UCJOJQJU^JaJ)jh@Uh@UCJOJQJU^JaJ h@Uh@UCJOJQJ^JaJh@U6CJaJh@UCJaJh@UCJ^Jjh+Ch@UCJU^J/h+Ch@UCJOJPJQJmHnHsH tH u(jh+Ch@U0JCJUmHnHu``a`b```ggmnGHjkl9:;mn9ҿҮҮҿҮҮrҿҮҮZҿҮҮ/jh@Uh@UCJOJQJU^JaJ/jh@Uh@UCJOJQJU^JaJ/jh@Uh@UCJOJQJU^JaJh@Uh@U6CJaJ h@Uh@UCJOJQJ^JaJ$h@Uh@U0JCJOJQJ^JaJ)jh@Uh@UCJOJQJU^JaJ/juh@Uh@UCJOJQJU^JaJdcreseWfXfXQ & F 8EƀPӨ()^gd@Ugd@UQ & F 8EƀPӨ()^gd@UXfggggllqqtt xxyyzzT|U|}gd@Ugd@UQ & F 8EƀPӨ()^gd@U}}tuwxders,-gd@Ugd@Ugd@U9:;deklm,ƢǢҿҮҮҿҁuujXjҮ#h@Uh@U>*CJOJQJ^JaJh@Uh@UCJaJh@Uh@U6CJaJ(h@Uh@UCJOJQJ^JaJmH sH /jh@Uh@UCJOJQJU^JaJ h@Uh@UCJOJQJ^JaJ$h@Uh@U0JCJOJQJ^JaJ)jh@Uh@UCJOJQJU^JaJ/jh@Uh@UCJOJQJU^JaJCk!I & F Eƀñfgd@UI & F Eƀñfgd@UI & F Eƀñfgd@UOLk!I & F EƀPӨgd@UI & F EƀPӨgd@UI & F EƀPӨgd@ULoڔ۔kffgd@UI & F EƀPӨgd@UI & F EƀPӨgd@URk!I & F EƀPӨgd@UI & F EƀPӨgd@UI & F Eƀñfgd@UOœkfffaff\fgd@Ugd@Ugd@UI & F EƀPӨgd@UI & F EƀPӨgd@U œghBCGC$EƀpӨgd@Ugd@Ugd@U#$ϧЧ./jkөԩ|"6s9FҿҮҮҿҮҮ~ҿҮlllaaҮh@Uh@UCJaJ#h@Uh@U>*CJOJQJ^JaJ/jh@Uh@UCJOJQJU^JaJ/jxh@Uh@UCJOJQJU^JaJ h@Uh@UCJOJQJ^JaJ$h@Uh@U0JCJOJQJ^JaJ)jh@Uh@UCJOJQJU^JaJ/jgh@Uh@UCJOJQJU^JaJ SjI & FEƀPӨgd@Ugd@UFEƀpӨgd@U{|{|}kfffffffffgd@UI & FEƀPӨgd@UI & FEƀñfgd@U }!"rs89FG34<=>hFEƀӨgd@Ugd@Ugd@U()+,-[\pqȿɿҿҮҮҿҮҮ~ҿҮҮfҿҮҮN/jh@Uh@UCJOJQJU^JaJ/jh@Uh@UCJOJQJU^JaJ/jh@Uh@UCJOJQJU^JaJ/jh@Uh@UCJOJQJU^JaJ h@Uh@UCJOJQJ^JaJ$h@Uh@U0JCJOJQJ^JaJ)jh@Uh@UCJOJQJU^JaJ/jh@Uh@UCJOJQJU^JaJAB4J&'MNOgh+is`uqr4J@Vatvwx:ǵǵǝǵǒǵǵǵǵǵDžǒmǵ/jh@Uh@UCJOJQJU^JaJh@Uh@U0J%CJaJh@Uh@UCJaJ/j h@Uh@UCJOJQJU^JaJ#h@Uh@U>*CJOJQJ^JaJ h@Uh@UCJOJQJ^JaJ)jh@Uh@UCJOJQJU^JaJ$h@Uh@U0JCJOJQJ^JaJ*hist_`qr34LMz{?@`agd@Ugd@Uatu'(9:KLYZgd@Ugd@Ugd@U:KATr4Cw(ghf!y!!"R(e((()))***䑩~f~/jh@Uh@UCJOJQJU^JaJ$h@Uh@U0JCJOJQJ^JaJ/jh@Uh@UCJOJQJU^JaJ)jh@Uh@UCJOJQJU^JaJ&h@Uh@Uhx'CJOJQJ^JaJ#h@Uh@U>*CJOJQJ^JaJ h@Uh@UCJOJQJ^JaJh@Uh@UCJaJ(12 @Aqrgd@Ugd@U    vw();<wxe!f!gd@Ugd@Uf!!!""##&&Q(R(((((**j,k,--u.w.112233gd@Ugd@U**L**,,,,,,,..A.B.C.p.q.//000=0>0223)3555٬فiWW#h@Uh@U>*CJOJQJ^JaJ/jm h@Uh@UCJOJQJU^JaJ/j@ h@Uh@UCJOJQJU^JaJ$h@Uh@U0JCJOJQJ^JaJ/joh@Uh@UCJOJQJU^JaJ(h@Uh@UCJOJQJ^JaJmH sH h@Uh@UCJOJQJ^JaJ)jh@Uh@UCJOJQJU^JaJ333388888I=J=>>??4@5@D@E@IBJBmDnD"H#HHHH}I(gd@Ugd@Ugd@U5555566,6-6.6F6G6~66666668+8p9999ҿҮҮҿҮҮ~ҿҮlX?X0jh@Uh@U0J%6CJOJQJU^JaJ'h@Uh@U0J%6CJOJQJ^JaJ#h@Uh@U>*CJOJQJ^JaJ/j h@Uh@UCJOJQJU^JaJ/j' h@Uh@UCJOJQJU^JaJ h@Uh@UCJOJQJ^JaJ$h@Uh@U0JCJOJQJ^JaJ)jh@Uh@UCJOJQJU^JaJ/j^ h@Uh@UCJOJQJU^JaJ9::::;:<:&;';L;M;N;e;f;g;>???4@5@D@E@ͺ͎͢tͺ͢^^MBMh@Uh@UCJaJ h@Uh@UCJOJQJ^JaJ*h@Uh@U0J%6>*CJOJQJ^JaJ2j*h@Uh@UCJOJQJU]^JaJ'h@Uh@U0J%6CJOJQJ^JaJ/h@Uh@U0J%6CJOJQJ^JaJmH sH $h@Uh@U0JCJOJQJ^JaJ0jh@Uh@U0J%6CJOJQJU^JaJ2j h@Uh@UCJOJQJU]^JaJE@#H7H~IIKK'M;MMMMSST TVVf\z\].]]] ``3`4`5`L`M`ccddShghkkXlYlttԷԫԷԷԖ~kԷԷԷԷԷ$h@Uh@U0JCJOJQJ^JaJ/jh@Uh@UCJOJQJU^JaJ)jh@Uh@UCJOJQJU^JaJh@Uh@U6CJaJ#h@Uh@U>*CJOJQJ^JaJh@Uh@UCJaJ h@Uh@UCJOJQJ^JaJh@Uh@U>*OJQJ^Jh@Uh@UOJQJ^J*}I~I,J-J.JKK5L6L7L&M'MMMMM[O\OIRJRSSTT T TVVgd@Ugd@Ugd@U(gd@UVVV1Z2Z[[e\f\]]]]]]aGC$Eƀڨgd@Ugd@Ugd@Uaa c cccddddffRhShiiiiikkgd@Ugd@UFEƀڨgd@UkYlZl[l*o+oDpEpnrorttkulumu}w~wxxExFxN{O{|||}}gd@Ugd@Ugd@Ut~wwxExxxxxx(y)y*y9y:yyyﳘvYD,/j h@Uh@UCJOJQJU^JaJ)jh@Uh@UCJOJQJU^JaJ8h@Uh@U0JCJOJPJQJ^JaJmH nH sH tH Cjh@Uh@UCJOJPJQJU^JaJmH nH sH tH 4h@Uh@UCJOJPJQJ^JaJmH nH sH tH =jh@Uh@UCJOJPJQJU^JaJmH nH sH tH h@Uh@UCJaJ#h@Uh@U>*CJOJQJ^JaJ h@Uh@UCJOJQJ^JaJyyyy||xRf<PӊՊڎ{&Rfؕڕ+>˛KLƺƯƦƔƦƔƔƔƦƔƦƦƔƔrƔ/jh@Uh@UCJOJQJU^JaJh@Uh@U>*^J#h@Uh@U>*CJOJQJ^JaJh@Uh@U^Jh@Uh@UCJaJh@Uh@U6CJaJ h@Uh@UCJOJQJ^JaJ$h@Uh@U0JCJOJQJ^JaJ)jh@Uh@UCJOJQJU^JaJ,x?@QR;<ӊԊՊَڎyz{$gd@Ugd@Ugd@UQRٕؕڕ*+JKL()012$gd@Ugd@U2ǡfI & FEƀPӨgd@UI & FEƀPӨgd@Ugd@UgΤϤTkfffffaf\$gd@Ugd@Ugd@UI & FEƀPӨgd@UI & FEƀPӨgd@U ϤU«ͭNp ns rxs78[\]ɿ﬘﬘﬘k/jkh@Uh@UCJOJQJU^JaJ)jh@Uh@UCJOJQJU^JaJ'h@Uh@U5CJOJPJQJ^JaJ$h@Uh@UCJOJPJQJ^JaJh@Uh@U>*^Jh@Uh@U^Jh@Uh@UCJaJ#h@Uh@U>*CJOJQJ^JaJ h@Uh@UCJOJQJ^JaJ*TU«NOPop>? gd@Ugd@U$gd@U eI & F EƀPӨgd@UO & F 1$7$8$EƀPӨH$gd@Un_O & F1$7$8$EƀPӨH$gd@UO & F 1$7$8$EƀñfH$gd@U_O & F1$7$8$EƀPӨH$gd@UO & F1$7$8$EƀPӨH$gd@Usrs _TTTTTTT 1$7$8$H$gd@UO & F1$7$8$EƀPӨH$gd@UO & F1$7$8$EƀPӨH$gd@U ]rstĺźQRӼ780YZòززززpgp\gزh@Uh@UCJaJh@Uh@U^J#h@Uh@U>*CJOJQJ^JaJ/jh@Uh@UCJOJQJU^JaJ/j8h@Uh@UCJOJQJU^JaJ h@Uh@UCJOJQJ^JaJ(h@Uh@UCJOJQJ^JaJmH sH )jh@Uh@UCJOJQJU^JaJ$h@Uh@U0JCJOJQJ^JaJ578<=OPgd@Ugd@U$gd@U 1$7$8$H$gd@U=QOPd"#v9gҿҮ{k{`{VVVh@Uh@U>*^Jh@Uh@U0J^Jj{h@Uh@UU^Jjh@Uh@UU^Jh@Uh@UCJaJh@Uh@U^J#h@Uh@U>*CJOJQJ^JaJ h@Uh@UCJOJQJ^JaJ$h@Uh@U0JCJOJQJ^JaJ)jh@Uh@UCJOJQJU^JaJ/jFh@Uh@UCJOJQJU^JaJuv9:fgyz*+,gd@Ugd@Ugd@U$gd@Ugy>?@[\%̡̡wweeSKF h@U5h@Uh@U5#h@Uh95CJOJQJ^JaJ#h@Uh@U5CJOJQJ^JaJ#h@Uh@U>*CJOJQJ^JaJ/jh@Uh@UCJOJQJU^JaJ$h@Uh@U0JCJOJQJ^JaJ/jhh@Uh@UCJOJQJU^JaJ)jh@Uh@UCJOJQJU^JaJ h@Uh@UCJOJQJ^JaJh@Uh@U6CJ]aJ "#12 23,-tu$a$gd@Ugd@U$a$gd@U$a$gd@Ugd@U"#$1a-1     67no[m   #u&h@Uh@UhCCJOJQJ^JaJ&h@Uh@Uhj)XCJOJQJ^JaJh@Uh@U5>*CJaJ)h@Uh@UB*CJOJQJ^JaJph h@Uh@UCJOJQJ^JaJh@Uh@UCJaJh@U h@Uh@U h@UCJh"Wh@UCJ,aJ,h@UCJ,aJ,.u`a(3.H] 7k j [^j `[gd@Ugd@Ugd@Ugd@U$a$gd@Ukl^}~!))yCD?gd@U j [^j `[gd@Ugd@U<`av ;        _ .i   ^ `gd@Ugd@Ugd@U j [^j `[gd@Ugd@UX67TO{no[mn*gd@Ugd@U j [^j `[gd@Uy  !" # ##$]%&&'&&'((;))P*C+W+X++gd@Ugd@U j [^j `[gd@U # #&&'&((C+W+--//W1p13335 699<<<>>>AAgDhDGGIJL$L@OAOtQuQTTvUwUVV8Y9Y[[]]^_aa1c2cPcddNfOfhhh,j-jkkmm.mnnph@Uh@UCJaJh@Uh@U5>*CJaJ h@Uh@UCJOJQJ^JaJ)h@Uh@UB*CJOJQJ^JaJphL+],---Z.//`/0W1p1q11233335 6 668899gd@Ugd@Ugd@U j [^j `[gd@U9T:;<<<=">>>>z?AAABCkCCgDhD0E}FGG HI}Igd@U j [^j `[gd@Ugd@U}IIIJ JLL$L%LLM\MMTN@OAOOMPPtQuQRRTTwTUgd@Ugd@Ugd@U j [^j `[gd@UUvUwUUDVVVrWCXX8Y9Y0Z[[[\]]]^q^^__`aagd@U j [^j `[gd@Uaab1c2cPcQc*dddd~eeNfOfftgghhhhvii,j-jjjgd@U j [^j `[gd@Ugd@Ujkk7llmm.m/mmmnnnooppppdqqHrIrrsssgd@Ugd@U j [^j `[gd@UpppHrIrsstyuzuuxxyyyyyyyz  QRadinwxyˮːuuuˮːuuu^,h@Uh@U5B*CJOJQJ^JaJph4h@Uh@UCJOJPJQJ^JaJmH nH sH tH :h@Uh@U5CJOJPJQJ\^JaJmH nH sH tH #h@Uh@U5CJOJQJ^JaJh@Uh@UCJaJ h@Uh@UCJOJQJ^JaJh@Uh@U5>*CJaJ)h@Uh@UB*CJOJQJ^JaJph$sttt1uyuzuuuvv.wwwxxx!yyyyyy $Ifgd@Ugd@U j [^j `[gd@Ugd@Ugd@Uyyyyyyyz zzR^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Ifl$%   %644 la]p zzzz8kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@UzzzzzzjFkd$$Ifl $%  %644 la]p $Ifgd@UFkd$$Ifl;$%  %644 la]p zzzz{{&{{ $Ifgd@U^kd $$Ifl0$ d# %644 la]p{{{{{{|A88888 $Ifgd@Ukd $$Iflֈ$ @ d  %644 la]p<|||u|8kd!"$$Iflֈ$ @ d  %644 la]p< $Ifgd@Uu|v|x||||||}R^kd#$$Ifl0$ d# %644 la]p $Ifgd@UFkdn#$$Ifl$%  %644 la]p }}1~2~4~,kd$$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U4~6~~~~ $$Ifa$gd@U $Ifgd@UA8888 $Ifgd@Ukd%$$Ifl7ֈ$ @ d  %644 la]p<,kdJ'$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U%,E $$Ifa$gd@U $Ifgd@UEFHJA8888 $Ifgd@Ukd($$Iflֈ$ @ d  %644 la]p< ",kd)$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U"$  $$Ifa$gd@U $Ifgd@U !#%A8888 $Ifgd@Ukd1+$$Iflֈ$ @ d  %644 la]p<,kd~,$$Ifl8ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UT_fr $$Ifa$gd@U $Ifgd@UrsuA88 $Ifgd@Ukd-$$Ifl;ֈ$ @ d  %644 la]p< $$Ifa$gd@U $Ifgd@U^kd/$$Ifl;0$ d# %644 la]pA8888 $Ifgd@Ukd/$$Iflֈ$ @ d  %644 la]p<,kd21$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uit{ $$Ifa$gd@U $Ifgd@UozA8888 $Ifgd@Ukd2$$Iflֈ$ @ d  %644 la]p<z,kd3$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U) $$Ifa$gd@U $Ifgd@U)*,TA88 $Ifgd@Ukd5$$Ifl;ֈ$ @ d  %644 la]p<TUWY؈ $$Ifa$gd@U $Ifgd@U^kdf6$$Ifl;0$ d# %644 la]p؈وۈ݈A8888 $Ifgd@Ukd37$$Iflֈ$ @ d  %644 la]p<щ҉ԉ,kd8$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uԉ։NJ $$Ifa$gd@U $Ifgd@UNJȊBA8 $Ifgd@Ukd9$$Ifl8ֈ$ @ d  %644 la]p<BCEpqsuR^kd;$$Ifl;0$ d# %644 la]p $Ifgd@UFkd;$$Ifl$%  %644 la]p ŋ,kd\<$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U=HO[ $$Ifa$gd@U $Ifgd@U[\^`A8888 $Ifgd@Ukd=$$Iflֈ$ @ d  %644 la]p<ƌҌӌ,kd>$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UBCEGR^kd@$$Ifl;0$ d# %644 la]p $Ifgd@UFkdC@$$Ifl8$%  %644 la]p ˎ̎Ύ,kdA$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UΎЎq} $$Ifa$gd@U $Ifgd@U5cA8888 $Ifgd@UkdB$$Iflֈ$ @ d  %644 la]p<cj,kdD$$Ifl(ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U $$Ifa$gd@U $Ifgd@UbA8 $Ifgd@UkdlE$$Iflֈ$ @ d  %644 la]p<bceR^kd.G$$Ifl;0$ d# %644 la]p $Ifgd@UFkdF$$Ifl;$%  %644 la]p ~,kdG$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U3468R^kdI$$Ifl;0$ d# %644 la]p $Ifgd@UFkdHI$$Iflv$%  %644 la]p  ,kdJ$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UEPW $$Ifa$gd@U $Ifgd@UƔA8 $Ifgd@UkdK$$Iflֈ$ @ d  %644 la]p<ƔǔɔCNR^kdM$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$M$$Ifl;$%  %644 la]p NUabd,kdfN$$Ifl*ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Udf• $$Ifa$gd@U $Ifgd@U!juA8888 $Ifgd@UkdO$$Iflֈ$ @ d  %644 la]p<u|,kdQ$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U[R^kdR$$Ifl0$ d# %644 la]p $Ifgd@UFkdMR$$Ifl$%  %644 la]p ,kdS$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U̗͗ϗї{ $$Ifa$gd@U^kdT$$Ifl;0$ d# %644 la]p $Ifgd@UA8888 $Ifgd@UkdU$$Iflֈ$ @ d  %644 la]p<,kdV$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U.9@W $$Ifa$gd@U $Ifgd@UWXٙA8 $Ifgd@UkdCX$$Iflֈ$ @ d  %644 la]p<ٙڙܙ(WR^kdZ$$Ifl;0$ d# %644 la]p $Ifgd@UFkdY$$Ifl+$%  %644 la]p W^opr,kdZ$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Urt̚ךޚ $$Ifa$gd@U $Ifgd@Ui|A8888 $Ifgd@Ukd\$$Iflֈ$ @ d  %644 la]p<|C,kdl]$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UCDFijln#R^kd._$$Ifl;0$ d# %644 la]p $Ifgd@UFkd^$$Ifl+$%  %644 la]p #*CDF,kd_$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UFHޝ $$Ifa$gd@U $Ifgd@Uޝߝ8EA8888 $Ifgd@UkdHa$$Iflֈ$ @ d  %644 la]p<ELXY_,kdb$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U_`bߟR^kdWd$$Ifl;0$ d# %644 la]p $Ifgd@UFkdc$$Ifl $%  %644 la]p    ,'gd@Ukd$e$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U QRabdijlM^kdf$$Ifl;0$ d# %644 la]pFkdqf$$Ifl$%   %644 la]p $Ifgd@Ugd@Uln8kdg$$Iflֈ$ @ d  %644 la]p< $Ifgd@U89;WjFkdui$$Iflv$%  %644 la]p Fkdi$$Ifl;$%  %644 la]p $Ifgd@UWXZ\/QXq $$Ifa$gd@U $Ifgd@U^kdi$$Ifl0$ d# %644 la]pqrtv A8888 $Ifgd@Ukdj$$Iflֈ$ @ d  %644 la]p<  !#,kdl$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U#%ͣ $$Ifa$gd@U $Ifgd@UͣΣУң%/A8888 $Ifgd@UkdQm$$Iflֈ$ @ d  %644 la]p</6BCƤ,kdn$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UƤǤɤޤߤ7cR^kd`p$$Ifl0$ d# %644 la]p $Ifgd@UFkdo$$Iflv$%  %644 la]p cj,kd-q$$Ifl(ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UUel $$Ifa$gd@U $Ifgd@UA8888 $Ifgd@Ukdzr$$Iflֈ$ @ d  %644 la]p<,kds$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uا٧ۧݧ(?F $$Ifa$gd@U^kdu$$Ifl;0$ d# %644 la]p $Ifgd@UA8888 $Ifgd@Ukdu$$Ifl;ֈ$ @ d  %644 la]p<,kd.w$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uy $$Ifa$gd@U $Ifgd@U«ͫA8888 $Ifgd@Ukd{x$$Iflֈ$ @ d  %644 la]p<ͫԫ,kdy$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U¬ɬ $$Ifa$gd@U $Ifgd@U_jA8888 $Ifgd@Ukd{$$Iflֈ$ @ d  %644 la]p<jqϭЭҭ,kdb|$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UҭƮ $$Ifa$gd@U^kd}$$Ifl;0$ d# %644 la]p $Ifgd@U   A88 $Ifgd@Ukd|~$$Iflֈ$ @ d  %644 la]p< !#%ȯϯ $$Ifa$gd@U $Ifgd@U^kd$$Ifl0$ d# %644 la]plwA8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<w~,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U !#%R^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkd0$$Ifl$%  %644 la]p !:;β,kdr$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UβϲѲųR^kd4$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Ifl:$%  %644 la]p  ,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U 4579Ǵδ $$Ifa$gd@U^kdN$$Ifl0$ d# %644 la]p $Ifgd@UA8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<6,kdh$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U679UVXZ-OR^kd*$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Ifl+$%  %644 la]p OVopr,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Urt"U $$Ifa$gd@U $Ifgd@UUVXZ A8888 $Ifgd@UkdD$$Iflֈ$ @ d  %644 la]p< ,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uҹӹչ׹%1R^kdS$$Ifl0$ d# %644 la]p $Ifgd@UFkdސ$$Ifl:$%  %644 la]p 18,kd $$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UR^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkdm$$Ifl$%  %644 la]p ̻ͻϻ,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uϻѻ?OVq $$Ifa$gd@U $Ifgd@Uqr޼A8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<޼߼BMR^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkdI$$Ifl$%  %644 la]p MT,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U $$Ifa$gd@U $Ifgd@UA8 $Ifgd@Ukdؙ$$Iflֈ$ @ d  %644 la]p<ALR^kd$$Ifl0$ d# %644 la]p $Ifgd@UFkd%$$Ifl$%  %644 la]p LS_`b,kdg$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Ubd*1= $$Ifa$gd@U $Ifgd@U=>A8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<+8R^kdv$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Ifl$%  %644 la]p 8?GHJ,kdC$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UJL $$Ifa$gd@U $Ifgd@U/A8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p</02RSUWR^kdR$$Ifl;0$ d# %644 la]p $Ifgd@UFkdݢ$$Iflv$%  %644 la]p ,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U  $$Ifa$gd@U $Ifgd@UZ_A8888 $Ifgd@Ukdl$$Iflֈ$ @ d  %644 la]p<_frs ,kd$$Ifl8ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U  '(*,R^kd{$$Ifl0$ d# %644 la]p $Ifgd@UFkd$$Iflv$%  %644 la]p ,kdH$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UL| $$Ifa$gd@U $Ifgd@UA88 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<&J $$Ifa$gd@U $Ifgd@U^kd$$Ifl;0$ d# %644 la]pJKMO,7A8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<7>WXZ,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UZz{})4;T $$Ifa$gd@U^kdI$$Ifl0$ d# %644 la]p $Ifgd@UTUA8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<TjR^kdر$$Ifl0$ d# %644 la]p $Ifgd@UFkdc$$Ifl $%  %644 la]p jq,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U E $$Ifa$gd@U $Ifgd@UEFHhA88 $Ifgd@Ukd$$Ifl;ֈ$ @ d  %644 la]p<hikm-DKd $$Ifa$gd@U $Ifgd@U^kd?$$Ifl0$ d# %644 la]pdegi`wA8888 $Ifgd@Ukd $$Iflֈ$ @ d  %644 la]p<w~,kdY$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uy $$Ifa$gd@U $Ifgd@U$A8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<$%'\]_aR^kdh$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Iflv$%  %644 la]p "./,kd5$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U  zR^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Iflv$%  %644 la]p ,kdĽ$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U{R^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Ifl;$%  %644 la]p  ,kdS$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U !#^_acR^kd$$Ifl0$ d# %644 la]p $Ifgd@UFkd$$Iflv$%  %644 la]p .,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U./1\]_aR^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkd/$$Ifl$%  %644 la]p ,kdq$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UFcjv $$Ifa$gd@U $Ifgd@UvwxA<<<3 $Ifgd@Ugd@Ukd$$Iflֈ$ @ d  %644 la]p<_NPR5b+i+++<<<<= ===9=DvDxDǶǶǶǶljnǶǶǶǶǶǶ4h@Uh@UCJOJPJQJ^JaJmH nH sH tH 4h@Uh@UCJOJPJQJ^JaJmHnH sHtH #h@Uh@U5CJOJQJ^JaJ h@Uh@UCJOJQJ^JaJ4h@Uh@UCJOJPJQJ^JaJmH nH sH tH :h@Uh@U5CJOJPJQJ\^JaJmH nH sH tH +R^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkd $$Ifl$%   %644 la]p 8kdM$$Iflֈ$ @ d  %644 la]p< $Ifgd@UjFkd$$Iflv$%  %644 la]p $Ifgd@UFkd$$Ifl;$%  %644 la]p  ': $$Ifa$gd@U $Ifgd@U^kd$$Ifl;0$ d# %644 la]p:;=?A8888 $Ifgd@UkdQ$$Iflֈ$ @ d  %644 la]p<,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U $$Ifa$gd@U $Ifgd@UA8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<,kd8$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U{ $$Ifa$gd@U $Ifgd@UA88 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<[gn $$Ifa$gd@U $Ifgd@U^kd$$Ifl;0$ d# %644 la]pJUA8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<U\,kd$$Ifl'ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UOT[t $$Ifa$gd@U^kd9$$Ifl0$ d# %644 la]p $Ifgd@Utu A8 $Ifgd@Ukd$$Ifl8ֈ$ @ d  %644 la]p<  9:<>R^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkdS$$Iflv$%  %644 la]p ,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U5:AM $$Ifa$gd@U $Ifgd@UMNA8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<NYR^kd$$Ifl0$ d# %644 la]p $Ifgd@UFkd/$$IflI$%  %644 la]p Y`lmo,kdq$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uoq $$Ifa$gd@U $Ifgd@UyA8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<yz| R^kd$$Ifl0$ d# %644 la]p $Ifgd@UFkd $$Iflv$%  %644 la]p p,kdM$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UpqsR^kd$$Ifl0$ d# %644 la]p $Ifgd@UFkd$$Iflv$%  %644 la]p ,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U!m $$Ifa$gd@U^kd)$$Ifl0$ d# %644 la]p $Ifgd@Umn'A8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<'(*?@BDzR^kd$$Ifl0$ d# %644 la]p $Ifgd@UFkdC$$Iflv$%  %644 la]p ,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UUx $$Ifa$gd@U $Ifgd@UA8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p< 9:<>R^kd$$Ifl0$ d# %644 la]p $Ifgd@UFkd$$Iflv$%  %644 la]p OPQ,'gd@Ukda$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UQM^kd#$$Ifl;0$ d# %644 la]pFkd$$Ifl$%   %644 la]p $Ifgd@Ugd@U8kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@UjFkd$$Iflv$%  %644 la]p Fkd=$$Ifl;$%  %644 la]p $Ifgd@U $$Ifa$gd@U $Ifgd@U^kd'$$Ifl0$ d# %644 la]p:A88 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<:;=? # $$Ifa$gd@U $Ifgd@U^kdA$$Ifl0$ d# %644 la]p#$&(pA8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<,kd[$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U $$Ifa$gd@U $Ifgd@UA8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<,kd$$Ifl7ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uk $$Ifa$gd@U $Ifgd@UOZA8888 $Ifgd@UkdB$$Iflֈ$ @ d  %644 la]p<Za,kd$$Ifl6ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uq| $$Ifa$gd@U $Ifgd@UfqA8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<qx,kd)$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U5R^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkdv$$Iflv$%  %644 la]p 5<DEG,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UGI $$Ifa$gd@U $Ifgd@UA88 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p< $$Ifa$gd@U $Ifgd@U^kdR$$Ifl;0$ d# %644 la]pA8 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<R^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkdl$$Ifl+$%  %644 la]p BC,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U%R^kdp$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Ifl$%  %644 la]p %,,kd=$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U   alR^kd $$Ifl;0$ d# %644 la]p $Ifgd@UFkd $$Ifl$%  %644 la]p lsC,kd $$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UCDF_`bdR^kd $$Ifl;0$ d# %644 la]p $Ifgd@UFkd $$Ifl$%  %644 la]p ,kd[ $$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UITR^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Ifl9$%  %644 la]p T[,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U !#%R^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkd7$$Iflv$%  %644 la]p   ,kdy$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UR^kd;$$Ifl;0$ d# %644 la]p $Ifgd@UFkd$$Iflv$%  %644 la]p JK,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UhsR^kd$$Ifl;0$ d# %644 la]p $Ifgd@UFkdU$$Ifl+$%  %644 la]p szD,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UDEG_`bdR^kdY$$Ifl0$ d# %644 la]p $Ifgd@UFkd$$Iflv$%  %644 la]p ,kd&$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UrR^kd$$Ifl0$ d# %644 la]p $Ifgd@UFkds$$Ifl:$%  %644 la]p ,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Uw $$Ifa$gd@U $Ifgd@UA8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<jk,kdO$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U !#%R^kd!$$Ifl;0$ d# %644 la]p $Ifgd@UFkd $$Ifl+$%  %644 la]p 3,kd!$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U346LMOQR^kd#$$Ifl;0$ d# %644 la]p $Ifgd@UFkd+#$$Iflv$%  %644 la]p ,kdm$$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U5BIQ $$Ifa$gd@U^kd%$$Ifl0$ d# %644 la]p $Ifgd@UQRTwA88 $Ifgd@Ukd&$$Iflֈ$ @ d  %644 la]p<wxz| A H `  $$Ifa$gd@U $Ifgd@U^kd'$$Ifl;0$ d# %644 la]p` a c e  ' A8888 $Ifgd@Ukd($$Iflֈ$ @ d  %644 la]p<' . G H J ,kd)$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UJ L  0 7   $$Ifa$gd@U $Ifgd@U  t A8 $Ifgd@Ukd;+$$Iflֈ$ @ d  %644 la]p<t u w       R^kd,$$Ifl0$ d# %644 la]p $Ifgd@UFkd,$$Iflv$%  %644 la]p      ,kd-$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U     #  $$Ifa$gd@U $Ifgd@U# $ & (   A8888 $Ifgd@Ukd/$$Iflֈ$ @ d  %644 la]p<     ,kdd0$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U    g $$Ifa$gd@U $Ifgd@UghjlA8888 $Ifgd@Ukd1$$Iflֈ$ @ d  %644 la]p<,kd2$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U5>EM $$Ifa$gd@U $Ifgd@UMNPeA88 $Ifgd@UkdK4$$Iflֈ$ @ d  %644 la]p<efhj $$Ifa$gd@U $Ifgd@U^kd5$$Ifl0$ d# %644 la]pA8888 $Ifgd@Ukde6$$Ifl ֈ$ @ d  %644 la]p< ,kd7$$Ifl ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U=>@B $$Ifa$gd@U^kd8$$Ifl;0$ d# %644 la]p $Ifgd@U\gA8888 $Ifgd@Ukd9$$Iflֈ$ @ d  %644 la]p<gn,kd;$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U@ $$Ifa$gd@U $Ifgd@U@ACEA8888 $Ifgd@Ukdf<$$Iflֈ$ @ d  %644 la]p<346,kd=$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U68%> $$Ifa$gd@U $Ifgd@U>?ACA8888 $Ifgd@Ukd?$$Iflֈ$ @ d  %644 la]p<,kdM@$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U $ $$Ifa$gd@U $Ifgd@U$%A8 $Ifgd@UkdA$$Ifl%ֈ$ @ d  %644 la]p<RWR^kd\C$$Ifl;0$ d# %644 la]p $Ifgd@UFkdB$$Ifl$%  %644 la]p W^yz|,kd)D$$IflUֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U|~05<z $$Ifa$gd@U $Ifgd@Uz{}ZeA8888 $Ifgd@UkdvE$$Iflֈ$ @ d  %644 la]p<el,kdF$$Ifl%ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U $$Ifa$gd@U^kdH$$Ifl0$ d# %644 la]p $Ifgd@UA8888 $Ifgd@UkdH$$Iflֈ$ @ d  %644 la]p<,kd*J$$IflEֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U $$Ifa$gd@U $Ifgd@UNA8 $Ifgd@UkdwK$$Iflֈ$ @ d  %644 la]p<NOQklnpR^kd9M$$Ifl;0$ d# %644 la]p $Ifgd@UFkdL$$IflI$%  %644 la]p = > @ ,kdN$$Ifl9ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U@ B      $$Ifa$gd@U $Ifgd@U    Q!!A8888 $Ifgd@UkdSO$$Iflֈ$ @ d  %644 la]p<!!!!!,kdP$$Ifl8ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U!!E"X"_"g" $$Ifa$gd@U $Ifgd@Ug"h"j"l"%#8#A8888 $Ifgd@UkdQ$$Iflֈ$ @ d  %644 la]p<8#?#G#H#J#,kd:S$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@UJ#L##### $$Ifa$gd@U $Ifgd@U####g$z$A8888 $Ifgd@UkdT$$Iflֈ$ @ d  %644 la]p<z$$$$$,kdU$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U$$$%7%>%W% $$Ifa$gd@U $Ifgd@UW%X%Z%\%%%A8888 $Ifgd@Ukd!W$$Ifl(ֈ$ @ d  %644 la]p<%%&& &,kdnX$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U & &&&&& $$Ifa$gd@U $Ifgd@U&&&&A88 $Ifgd@UkdY$$Iflֈ$ @ d  %644 la]p<&&&&F'Q'X'`' $$Ifa$gd@U $Ifgd@U^kd[$$Ifl;0$ d# %644 la]p`'a'c'e'+(6(A8888 $Ifgd@Ukd[$$Iflֈ$ @ d  %644 la]p<6(=(S(T((,kd"]$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U(((((((d)|)R^kd^$$Ifl0$ d# %644 la]p $Ifgd@UFkdo^$$Ifl$%  %644 la]p |))))),kd_$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U))) **-* $$Ifa$gd@U $Ifgd@U-*.*0*J*A88 $Ifgd@Ukd`$$Iflֈ$ @ d  %644 la]p<J*K*M*O***** $$Ifa$gd@U $Ifgd@U^kdKb$$Ifl0$ d# %644 la]p****+[+A8888 $Ifgd@Ukdc$$Iflֈ$ @ d  %644 la]p<[+b+j+k+m+,kded$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@Um+o+++++ $$Ifa$gd@U $Ifgd@U++++Z,e,A8888 $Ifgd@Ukde$$Ifl+ֈ$ @ d  %644 la]p<e,l,,,,,kdf$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U,,w---- $$Ifa$gd@U $Ifgd@U----..A8888 $Ifgd@UkdLh$$Iflֈ$ @ d  %644 la]p<.....,kdi$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U..//// $$Ifa$gd@U $Ifgd@U////00A8888 $Ifgd@Ukdj$$IflEֈ$ @ d  %644 la]p<0000'1,kd3l$$Ifl4ֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U'1(1*1G1H1J1L111R^kdm$$Ifl;0$ d# %644 la]p $Ifgd@UFkdm$$Ifl;$%  %644 la]p 11111,kdn$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U112%2,292 $$Ifa$gd@U $Ifgd@U92:2<2>2`2w2A8888 $Ifgd@Ukdp$$Iflֈ$ @ d  %644 la]p<w2~2333,kd\q$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U33 3"3$3g3333 $$Ifa$gd@U^kdr$$Ifl0$ d# %644 la]p $Ifgd@U333334>4A8888 $Ifgd@Ukdvs$$Iflֈ$ @ d  %644 la]p<>4E4[4\4^4,kdt$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U^4x4y4{4}44445 $$Ifa$gd@U^kdv$$Ifl0$ d# %644 la]p $Ifgd@U5555S5c5A8888 $Ifgd@Ukdv$$Iflֈ$ @ d  %644 la]p<c5j555>6,kd*x$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U>6?6A6e6f6h6j666R^kdy$$Ifl;0$ d# %644 la]p $Ifgd@UFkdwy$$Iflv$%  %644 la]p 66.7/77,kdz$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U7777777>8I8R^kd{|$$Ifl;0$ d# %644 la]p $Ifgd@UFkd|$$Iflv$%  %644 la]p I8P8y8z89,kdH}$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U999+9,9.90999R^kd $$Ifl;0$ d# %644 la]p $Ifgd@UFkd~$$Iflv$%  %644 la]p 99:::,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U:0:1:3:5:::; ; $$Ifa$gd@U^kd$$$Ifl;0$ d# %644 la]p $Ifgd@U ;;;;;;A8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<;;;;;,kd>$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U;;<<<< $$Ifa$gd@U $Ifgd@U<<<<<=A<<<3 $Ifgd@Ugd@Ukd$$Iflֈ$ @ d  %644 la]p<== ====='=+=2=R^kdM$$Ifl;0$ d# %644 la]p $Ifgd@UFkd؅$$Ifl$%   %644 la]p 2=9=:=<=8kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U<=======jFkd܈$$Ifl;$%  %644 la]p $Ifgd@UFkdg$$Ifl;$%  %644 la]p ====>N>U>e> $$Ifa$gd@U $Ifgd@U^kdQ$$Ifl;0$ d# %644 la]pe>f>h>j>> ?A8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p< ??,?-?/?,kdk$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U/?1?W???? $$Ifa$gd@U $Ifgd@U??????A8888 $Ifgd@Ukd$$Iflֈ$ @ d  %644 la]p<????@,kd$$Iflֈ$ @ d  %644 la]p< $Ifgd@U $$Ifa$gd@U@@ A&A-AJA $$Ifa$gd@U $Ifgd@UJAKAMAOAB$BA8888 $Ifgd@UkdR$$Ifl ֈ$ @ d %644 la]p<$B+BCN;g^bng6E7y#3f3ZC]8:|SUnOӍo`گӝO*%]Hb]4gMQZw%'~VD *{i`w?$c<|yά7gš\Cxoޭ1Y)ɺ`sŽ̀ߏ/m:olE#H[?Y`|ߘ Wq_#f .L9 ̺G~jzgvcE|{]F=lx%?Crpޒ/7>pq\?f}غa)m;n} Vs0kga *лA;A05zT\0RsZ3+$SlI.8ˎ&f_x<^kat$|hCHC F$-4hXc\&Ԅ;F]=Y?VS OnzPC?ʫ>3蘀?[Ya8Wќq?4L\O =EO`v7;άJ# K${֨$˼Tooa?|4K+q-{wQ-{x*L6ԈlV[8NVh` Sso,;_aqQڷ sPq☸SQx"ge~1A` ȭ~#3}Wk1&Vwz!GL 2՘4l-~F+XbB7zq1);X(yxn6U5]4n$`t5d|wb+4 Ouջ %0y--{uj10FXM gwJ6Pn I[HCP[]w޾wB r5x TԀfkvL9Ү 8 Ij.b OM]5 F=934Q~-3ilD`N"Al::Srk]Gfo:@}`/]jAA֚-jQX[RX\8WwTwڥNgbvd7ZMׅ, q f?ث˨X]Fw }6J-|v4D6[_t0K K+XŘ]UdZ$*mdj%n@w)uƈt첒NV鋲.Ȯ pCx I?(E 4Y F fVxc,m; cdIί`㖴dWaI0LqV$f_3T8YI+fdWd4/" (|A8K7ޠ?X=2x&(vL"|i`Vw懤uop*p "rhzFpf _].K&._$- G1=50̹8 \o! H ݴbQWT&dkȰE |Wt!,ɞ:Wor#84~)!FͿH)a,w8mq6bS웘}Y"C"OtoQYj K vaR@x}DF ]ACxZfQx.0.9E*sIo|̄)'Aŗ~gb|T#z !`O #AY zl'{3;ԽYZ=&֑`t6H."YVJimmtZ̡T|2W _w2Ԡʥ  qӃX#⴩Ƶ2˝@-$oRcId#H6eܝpg Pc/^\t"oAZ6 L $1HlJf{l$ȎrYNJ! A~K$:FsT ݢ_h/j@IAba\p]LbĦkOG&p1`09gKUS k#΀Q]~anE9+˭6 GV4ߛpixxc:P[);Z 'l53hrRs14k- J{eL7dCM~ё P<jp4&;+O:t͹6]Nj75/I-~LiCxxX"ހ0bLZSTgR+)%:jZ C&!7l UG3ϙcҽ.are`rwiʗI,zĖl i9[Jd8Ƌ2w( I:|g'ڍ }" E| QM7FeL-R{I8!t[5\,|uE-k#@@pYr)Q@9VR5ȏ{,/Au~Ϝ^-{prHkHk)MҨ/I?n+h-KJ 0O# {w3w^ &/@@ÉkGTtr~#)qiX'FF=/s%­Fd{9=T<5yC03DQxY-(?lB- Ġ:ާY9kڈWME;>hu>c^򶼹TcCC"(Lu뽊X6Qڂ=CG#L,'XFΈrT \=gRD7S@SRCm+em g6:);s:j JhZ6M< tdib :/l'Z V8l&rt:ʐcѽ^Hci+ "@ۼĠhpva+'>J@xy1J,F|Yu:mw~C:hπ< @ݐ]4uR ])j+%]o:1 F-sfqes CttƣSBYoH@SoP4pKaiA8S>vcUN^[fV !ST 7f as➚5Dξڮi mNO@%vuBc]gU}JuZiн rڌjĊ"j:b†S8jh"w#1X0MP2txQQ~  SljRAHíl5%RQt{ 'spN*Zj҄X{>"'bS PpIiq?w.1\wwH!?uҪS!@ ""mP0o:;m+=[ #\ABJ S Si;1 $\rd*VL]oK.睡ii _;`}f{V-TߔLlEʌݐ[C+K7@;'H0ߗz=\s̀Zб"Jќ%]pXZ)'5iVk:$q{gm\6w;V65|M<cyc1BأsJJLXf2‰QvXgj}sFbZ\GR X;'2v.Xû@0u^"(c!:ŧ&k[e߲SCI (s[ADle!a(^b51&<~=%q't~DkfjCEYXPI3X64e6lօ#&Cb# vu z;e$fNG̑Xj,O[rDi&)Q;bEjjS4;xv0K|Җ1׆W J V$ ĴNY7@6oEa=tΗQi(5v߭">ߌޭ'j\Guݢ|Off=3E3Əfsыs\8ş*yX!ڦZe[Bʄٓ7|kY̬#bNhs a_;G(yvT j{^{E>S h*^1{@,mRL%#إʸ$6 y'up[Bz Bsw0EVB\1s<4/9E<Z /:4At%W4hteIPG^+ no_]2h >~RM_8dA/'hLoL)W|Z3N(8fZh#9n 1EAw|gg^jf^Dǽ"4ո jb eF 8pIB9htnݥ9=vXX&P3 S6#gkYlڵ\9AKBqYY+E8-I |:D`_܂4d^%\blF'U۪xmp͋»meI ;o$)f@~_bVy{զʐ|9SahdB}TNXfIHD"xnʳ0]IKG0+rն #QUzʣ!G"ZqH5TĤG&2be=Y{!j+Q Nei:<,;qx: Miff![N\Y4ud5ԩOl̜ڌ"H [`zTg6|,p H-]r.%͟VjEyVG+ M4Y4E2 {A۲KӿV#NZ&䇑ꕵcXwIh|*gatе7B0PNJW> Eh%"-I^$*58"SsQ |:#y~zRQBKD;rOq~ u6kQ 0Uǒz圱˗P 9sC\ h4] $UFs=gU0$OL,egFSNi,;8(,-!QKE9ЀV'ەhYV0_EcNq\$M~qlE B.k(О`[|_C6@jv+\c"h=MM-0;AVkQΤs tXu>{*c| e UcT˧J{RG 7ȇ]Q!e[ Ks],c(B,)b |('& ;2va"AD"T-9WU8 KIi,M*"D[MֿO`H#e\῰@;xe7A@71e&X"0y /=k x`w Ywf}ژjUo#+a͖rhu4D{V4'+JmxF6Ww<)\]i dyڐwA]O6m|)I%tJ_km|J _f z^rN %ie^uLMk2Xbp抄ze*C J8C,v|']:PI/\WB!6Hc>)3: إ0+K䙴H5 U{%toT>Fn t/lL-@ D $EC4;aP:=eec6򁁿Ěi`''sxV&\{vvzlѵg[H-N٦3tl u0+c먬nĆZi: bZa̢ Y%&eC DP/¡ATY3ꑳxBjCt)_87>KRk AhdrDF%ZX--Zҕ(5#Vc(4GX#tlcY%*kP N?]6FP$Ia H[40g*W'u`ҘX<$f( 8[xߨ{XW?sZraޗgl x[ܑlm3rAbu-O_}?]9[7m,rn:Alɹg]>E1ݏ D@}RUE-HARíSfS GGA$+pr)2 w{y<-G5c˒S{JI6qF ?#LXb_<%g'ͅ:k$-Z4S7SfH} fwAIP\2V}dB@0 {2sjh4waH>$tKj73dfC&LY$9.=glN2~Kr2 ?~e٨FaY拴ǃeﷄmR-S HkI䒄CcJmH҃.+uc=Jnr]=E+6 9էO|VL6#j^&:Ж4q(jx,ţ\]_P-Y0/}6PکbAl4`7`mLlm.ޝ]x-%$FD&fλ}?B23-Rֳªg{]@ƬZ&?^p#fI̱!~^ 1OcjWF>@qgH@Ǚ|r O5 3n*m^C^p&2u$ni5!\3a-+:'OЩԂ ?tm3?H|]# D_qWUM.$J:C|{D.:heo]VP`zK; g-rJ-eeI˜Ϻs97B`i LraILLK*b']r-WM1N Ӳd-C]gR趾~hw;'y9h*="jʼnŢ60]K@oǹ,#Y_]f3ɠ1*S4K /jt {i"|0I|GgdsI&&.fqxMx<ƶ1h^*?y Kqn3}t@R:Аh6~~{C١Ƈ*ߥ`tzF,Vc<3bFe,'xՓ+.8 h^i6)vg]QFP~<3Ƒ/7Vowvw^&gI #zƁi46:|6Y \0Zmvp.Xq#@eόcN+y<604XLlpv5j#~Zkۅ7FF28 z.4Qm`gYFg ~-FݠG˖ [ \6ƛxY*DXbX #pG14[b `N-j3T>ʣrd4ťw04TW`sVٮLNI|-ǨRi)S&u|\V s%Uc a{xteBLtI!TO_8ћWLR1z`a) e 'RJT_П%v8SɚI]_$G׫k)ɚ+K>̃ױEE h'-kAKuD)D2L;^ @A*u0H;_&)l-l}b瞭J!vɢG:|Ϸ75-m irpd!GULYc@EmS4X&v~궉CV)^mjDMok萢/*zpvJk>8DrVE".ch6ˤ~Ř L~Ũ?:M8Fe#Kl>"sd)7Y\ƸaW˦eh*L*lUb{oX`5nESut}ɵ'˼>k)̵DtueomZ!m\IdV4{Y $8S^"3jͤv=c"#[(WXr/s.~Öu=O'V)FVtJr!smBrBڀو@AaaΉĜϊŅfpLu°81ư!ưȿ=אɸn%pvGM_ˠzmbKGDH cmPPJCmp0712HsaIDATx^} |5\cQC6q–`TD#ЀJ UDQdY(X\PV-Jv: LpVo?Q@P yAv 3lV3 7\2ˬ=?k _߁wzOz#>?-e z ? ґ>Ça?V@G@#(9!^O|=8#X: }}6q'#Bl#h `$/ [ӿ?ai`>yQ,z6 ^{@c@? 0x.9!*"!"+#Co8̀:w^2,@Ø(ENI,E8'\49W/{hbmKF9P+}&𥷰Pڐ۟d7| l{K?Wöd#  3] 3;&D//! ˆz8(Z0DdȒcrrҷB_p?(<n_OCи2 L%cD =.#vT_jGNY铡8Ty!KNEll!oءMQ:,/!Ⱦ GOݗ_^ qkcFf$I?+qQV~Gu/h) F:OI1D'PYY=Zڰa=6mܸaM߰qO;z:`czk XN27ߌEKdIKmq 6ⵐX« 6nH,W7lؕX:d87gOM IK "}0"?"bǠ"jVٴ~&^[ w}K+|뵎4r 9u_[fll@"Mx"'3Ȉ&@KGZS3ۗ9+GeڡCMH~&)SڔP 5mL|aD IjӮV=>o׮/5%o\uZ57᭼X:4\җ<Ȥ{lE@e%?Dc;"!x N"#jM%JZhx#Xƒ+?_{KvmK I6mMYˆp-o%:`$FD3#bHLxj43{j4T]^\((lʲp6L47%!.yɣmYirf1Y!A$Fmd@|Oz7@#&k3y?(dq)$DUlrqs(kF x1>7d!H,fje,ax"Y50nD(I`"]q~ նog=ϨWKQL Jk"c̠o5Ւi!-p֠?'ZI'~)H8>D aUWӵ^<3wxė/ X,_ثz=I`j; kKN_v~~0p F@zr0}mZø%2o(d}^I(yφP}AJH /~IٚiN,uF)jH` H bL\b*GR\ۈI'јjkg[u@.IC*ޅ Wz7v@jGXJ2m.L͍a H# "&Y,%ŷM[%E)$*dL=S=}S}ȗT^P@жA\o{(гBE#cFiFNI(R,d6CN*xېowlNʴm79/'qPCS.oO} "&(s^HT1B"'P9rm)I(ďiAH(~$X*HDM4~lL2pa}R4G(@EK1ޑ+/ջ3tK %ĶEERGQbC*HC92#3Q ^ <*G%޸GHa@қ Y %,YZ9og- +c+ $|ϏeĜr̭Kp{i՘KNgʻ>kOj;rOvQF"EDRΤEo)DA&Tbf㤔R'DE<_`2<)-E;vG4,g~TOyIMFM$'!—UzBhG!F/C b) nBJ/Pu8_ Ͽ/_|Ghkg5|YO?0]|_z L75\h`I6DeCJC(RTha3XZٰSU!%s74Jo$5Y8<Q+5]A,II/Hٞ4l?E{=3)x֘ g(?#YVLw96CJkf4D4VY7eBՈ$9QPɆ%) eOL:YA$T SR{g҃;g]G xF 430l Z YhxZaKG]g8{OS Ǖ]GOgNQ,K(p-HPsec"," $xJ\[%( gY4")Xׁ$/E$Js~yXAY { ?CM.iNmSN mxiPyK2t&hS@i,>3Ei"Jz͡"OVgrFDYEScN%"*`\*Y3?oCA q=߰a H#'Sw?vW^u3\tu^%T^ki+_;6j0r'@ SidVQ5i-t?~s(6- [UUg^1[1JKOq|hJ|zsU7N8k?.eo /4w/g[Kmپ={;V0z-_/jrZ U>ΊCk1Wz SG`_lٮC‚춬1S̈:\*=CV/Xֹ }dmkS|OoJWgP12% 5woJ"ѷN?oZL4niK7bOǞbs\^,aLS5h*YSꃟXپ04oU>~>0$FЗ0frаyONbs9uJ%)Rޡ8³!8D2 :ϒrU9 7:o\CYvOɷ܈8AIN?}c?7u_V4]>~6\LF:6a:V`) hJBO,e/:?pg` g׀SY41(yY!W +×_ړ"dN.)κjY;+'Pr4+7\nq!,ա+c)0 KݽRed0ƎbîЫcgC1 ,5ndݺ;qS 5e eIWpR;>TRTb* ^,uZ˲:4dx2Vi&%~ &DamvDDc%1߷_:}:ԁ{4G,^I6GE,ݭH2[##'Oco!n_lP_DuAud矟xH{VKMRP"-}{!4VHh/CPCKM[ոOg`!gM-/miꗾFP% {b8F2_nǂ7&UX> T+*H{㊇ތzpӎuҳvM'S{+#b:"s^E̦ey>AǙLTKgda)oJ`%w'_֭54jb橠i~ͪN4w<&qs(b6cê5C"8uX0 ܞXZIO~C ^rz:|_aHX- 6@FvKCV}Fg*ٸi$l.n8yHMhp2fKA+E(EHw|A>n=Ј'u^fEjBfJ g&!ǍideV Yyz?l\`HɦxC$џNt,q %7{ܼsF+%\Eu ?7S-MX R(\Cpvv vߖUfj>e /)ҥ} JJ82RkGxl@[׺[3oiO5Д:`¸ڐ%znL ᧀ$kUm4C;8"%ŕ nv$ <*I )Y).X,R3ux^:눛ПID܉kb0I6zi1[$V/% pb]'? %n*m" l$FjFG<6 ҴnӦ{KSWιc{ggKZfZYIZ=|^48pid+9K1g:-X >o嗶ч_UCTUdSLX "W7 z1坏ǏdՓPI:Z#l82e#-U3qW2~rThԒA78#>ʳ ol}#@˼`jZ>ũҤscށӏ=8\:c!i#9&#i JKpF&+ĉgGXI~ xm!$!j#ebqIcxc[m ?3z)G,BWr aҜZq~.R *3!iO@&4VjnÝp&#c'1R: ndL B@^SAg>-d:ԥhHNJ"3_\zݗbq1Tw6oUG٠d, " +ɌK>CRJ,Dp].#379;:H)BĎ˒#G|\ddE仴cNoi9ʤ[Z?Y)Jn|x]uUW]ߣe>9*j@y"CY9r 2ɡd |H ROT5^fl>]U/!y?^U\䱧[u:*O* '[.F%JhaC]%G;/5 'W=r2Xi%ϓPhgn͵۰B|eh4,\''\kH7ڷ#D= !@f؀!vW;yP{'yjciꥋxJE[ءsM{3m&@e^Iy"JSZYO\RVTLc*Tv0u饺'Zl\Q*IL#8XgD*LY75HXl@ Z&پPc{V%` #SҼKW]:70Ace1Jޖwɏ(P7tϕ" 7^^uyC^\D]eks$pa|YR4Xm`IFpftA^ߵfQD@l (N+kc?i6kʚb)Wlr)&}6 @. þv[`"w>=f͚{MͶ}mk}ХKO$%OuYr晧԰TULTEXa 6 \SyRy*GTbԌ[40# %+GIBgI1Y_Ub`5"KdQf0\,,0Wpo %CRdey3i6`)*rAMiVJ{ˉۘ\zQ@IzC.uX5Oך)Q'mM~طE]z9녦WwYڢS/VP06 :(,zKS0PT|ifs%jyplw;unm2º7aY Je[v6l,S?1[ejn%kaG(x KU_NIAǎ;'k:5J/Z1nccԦ%Q[Vq8CJuu_bx&7\=֟L0! IG&@b'^zixD64 lLxACX%k4̍LLAАxi! VL0F+:y=%:/h4D{`&1!W*f"(x~ XH=FK/et $X!EewK:=?,u PF KX:(4Nd%"-='Rϛ2IiYva vx*X@̢QbLP׭aa#.Ib?|( 6/IpW/jM~88."#&k3zo|e2El9#ld) \oR)a#ʫR h㈥uG(z t@mb3NʻUbH );"[oB i+w.0u[oKS.8'h7.M&ZbiG>M,%[) }r1"AqU[IobN"RA64w~jJt-79ܨ ~RqFU0c>{tM+n6.D( bPCHt5jΚP/H V%-Z6ίpl9ɺ3׭>?+qp-Ե4 P"whr mkvg?ULEyӺLK{G$`i 8 td1,\1:ByF"kGBP|eXe#a$ Zq6.|%c *7mco( *5xɭn-q&6V0bCIPbJi;#a*Vip^ ,%>fj:j[3LIuD,A]#$$!Uopl[;؍,|P"<@LDI) MI!x HE)AbƵ18qiK8Hrܛ~ g?/^bM0]q[~}Cvam`K!j - S|rA孾sg$rff_dEjۋ7^yX"xg?~y4y^~}~۶ֵNlw!: 7;uc-(ఀyqfInSJka2$*40@K29RJkdH%!ٰȏ3ѡ(&S☍ b܈zuO-NocqD;; +3,!fIXWԷ/ʖ|A'oSv^fzӧf+@` ^ Kuc-rp BI9`Α˯ayQeT5;eX тʉ,nEctό(Kˡ4̟ x;\q rى&AwLʚ/v xqfkio[-~8G4=/':-^<V#+GU # C"MN,uR*pt^g?`]hzS-dE}{-Å%V9]'C$esf^vI98I~]n6HcГ*x-L^,^ZaH2˄B3a =q ^dDž53`&V'/3+3p:dL,m1׊Yd0}qoW̏Kî0,xU-EpN8sN8*PM2AxKF?1ᴪ HbaIVav[˫n}%]KZfR8!P&lbRKFA~#6e|֯L{XIxi!C 0ܛ'pmF+wQhI$apAt)tOǐ&6`iRb7r uXr0M8x]Qќg;[u`u0t`VZ_ z@aP@SvuDEvl83acX~jNlJZR𵘀V#V*e~(zu X;jt ^qYKĞ0̏= , \] XBHi\)AIʗ kصA@a / ӞKOic^2zD!6HI@7V/EG"X_wy;QPVA|VSet5C)dA``P~9G$`2F7(tV_\L%s(Di,K =Kݝe9s O ePpɏKMRi 8Er(*v1+O1߱{́%k% x Jt0<f)x`|\sM@ҰœyɊlKe ~>4FH0M ޹%&9QeQJMV R nxsIvW*j_ bיۀɥPkKEJ<[}di&;ˁ3R|J#@8a /ѤIF-hһ!Er(-raK2L XjsL_>c=;?ϣ&~"֭͘>9 &@07o9OFp '25!Q`aSRW4y(wPڨ)#%l~KQmY4֑#?LJ #l*/m:[%9;v&%_3y&TJ=TZ8uF03  zމ͡M?KN@qC%%jNl%87` iKFjmS,cN3 Io.} w 5oFȗ Z0XhK8&i͟3wyV/IXqxĺ=I쥼QTVc2{_P 陂TM\ѱD_j%MaBֿ Iei%酈{GzDM3bK~8 u91$*//9dӻ9,:#vP{Ms}2Z\Ŕgο< PR1o7&S6c is/(|9g:7^1~Eگy+K֜׻OC$\;eBSКۍ ;&ֹY9ȴl sZcQ]^V8AbXIR 9.?y.n9=RYa;>ѱcRI<uE[žLgtI/"rfZKܸG9؊3<=)N:ob뢔dhM~"KoNu(}?\ /7a:&)뚬նϙFJ7lu AT }f"QTE~5'߻Y|6),V ߤ.KKX{6ڝ&:Vkcdd |f ";`H@la {˚'GK̊y3x[0u_r¼͝I/)^b-m:G.C>kGPXB{ַ `k S!JU pnk"Xe}.A@L˜zNSRyU9Ob;z:uJ "*ˬ*Z] "? ޴]$xYʛYݼ}F DFWt[bvwwM%X`2<1M=ZJ1݃gbuxzhX:Ez\Wx"Kڜ_Xok\B`B6|Sা/)yR86qs}ۀѣϽӷ;RhE8K*pDHc) T!oYVzd mܮ #f ]:w- ΄ 1{:aTy`L3=7?.&KD*iEaj6`|Kd L^D%sN N(\^2'sg\QgN>mSût]p3R [S/i1q0qS$.__1M~dyIwLHDDUo (V: 04]R:|6%dT[ HHxzq֎e/S1'%♾u]'S\40e[+Nj,eI$8LBРn& V =\vFn: ˍ#]7cӌaKӦP} oh5pԥ`*f0l6FMޟ4MS.~q;WY8D-,)H`1>i4z&]7We:NwD=7?2̅vrrt/ as, `0o֫`K:;T[R5p'\@^H[D,%jH3R#>8vo%"vZUP6D#wa[ށ X:Q3 ϛ6-oxpG܎ÿ.2ʛOHzxƔaKWM]锋_"gC~iߋ@M6RR5U_0 Ē+"qlQIALaKVR 6'˒DJRRC XXa‹1a K[U 9l3/3pOzIH:@\vXWKQjzrp/g_<7 @r鐪Eo.&Q-AzK,Ztާ=53RWÇ=z=?= FdAxJ-ǒZEu~,2j5v;e9՗nӸ" B(`LO[Pb@Iɗ6n0a3Gq,E5!6cv0>ꇝ-͙kN_ XPM7J'ֶXyq4/BlT@]z;僾xBVz&ov'ޱa* _ac][$F(='w-f4Ӈ 9¤d&?aSf撷zkjOM=OsI?>nM[}ͼ$,o2&rU8ֽ3Ǧ7.kP*fLbr=aBU᪫ɯz~;{`"pyA5x|)oԭ8S4-N:>%2SdKu 11X7%{*؀LJLRˌ-zM2eưMtpˊ .O1JHMv2[C:5p⿴9|涿]] #>|X91!}U1cjocY_amF@>u.hz) X\E=<9qgWxtLԸ3}w?lGR:_Sq& 3ӿͬ7O?w8Ng aL#%ēbs.+ hȯMqe`'@RC;.B`-=4\~0)AWi3}^ -bcNpc/}לĴvM5ɴ8#&v(V))gKQ\c_$WSūGLEcy v\H)kMM[V3u X霦'xógGtmoKػ`~) SQQ8&ڰb9AAz;o ̨OfK3>>q3\Ϲ)4H:(Ptp>/dG ,O̓E؄bnX-lcs3 mNxjRl,3y# g[7))]'qK<Qi aĐ&((%DKlH)qJ0>.0'-F+&ͣ*59wEW_2$vƝ4KJpaϞxw@CD8nė}ڽ^4s|Jհ2rrDNLWiŘA<`g"7bJ;/J]罠Wx:F}eWnT7%?cA%/aKpnlE8hpe؁)z3Z +hH$"…Dc%0 @B1UU$߯5{3̙bRH&09l$\Ӳuk l3%a5kw$Iw~9YH4rZRhP "Ώ<])z `J k.  -A,:Mu%jܕX}o85r˶}_<PO^ұlڴk<:s2ۡKmZ`*Na./H$RMA/yP;1RuB,('yUD 9w3 h rO|o"o^I)4-@EDRS>8: p$Sn,\I=8MA'eL՛ S,)V]/֔9=vgf;u9w ឮfj"y)v g8-,`wd-Ztܑ1(&PJv rOr^:s. 9=; # 87c|b@KٽۋzϺ8:ꤓN:_m̷@)ϚDPM =m*d$Akzp/](hIKae.\λdI{OKDl"@I6.i.DnL>RЊ+<NZ}j^0`mW7m2s&3gWT̆[-!p%7 b3=HwqǴ_w D\ fLlG iͫ!Z`lϳAXMMsαTU)wbdfoYaK(C*84)!*$ͭ:'iǒ%2-:_$c\RNm8缰q~A/!'-mGΜ9VnvEۊ9s:.N>tK.BH6jz8ط6p;N)J?ws}pjK!8AR(vgw+ l a3c3%f8ޭpaPSʛEFܘK7 ?{K4B~-OgU!KV}K!gXRv|ĖḄăBEsSl+}۷goq>%p0LnE{@i`-Є):1݋ZK0a*1 O繓WrX[I…*%>W8)gXU/c&iu'}1zHH72QkF՜v:kQVG68 ' 7an21x-SWq1>:&1̖l$g%|+z sjUۊ_MM9HjE , ?lbMq6O}{B$A)=ܤ}~(mw,uRr_7fkCy4_ ePai~45 k=*.7ǴcQWiFLl{~jkI 4{pSZl@6'pD2B[q=cu h3dqu( 7~0Dvtl=EsN{b&15 靧-'$'w}5pA}qP2lM+7d@1oT2默VQx'>62(-Ivt34<\ߔ;P HRXeKJ}s/ ©g=[4l-f,Zݣ>$b%0rpڿ[E~>`uqĤpe&Ufˢѕ&5lT\zئ/gY=Yiu0nA7̭v 1`Du?fwwe 1E;Fu\'h*=G铿2?hZ bqENB0 I&N\7ɾU{R{@./2sc:tt2/R|Ik]nͫ[1vɄnDH}K+;XT, qVI ]D3&_,7QžY/[8̂ˆLwM5.(uD4NO/W,E:&OyPW{]J ׳)Q q`M+``D'覀G~ *Pc!kH 4yU售?_3Xch*#^ =uÿ.1}w}wWLoKvGafF>өwHMg,2a.uKP ~ Л}]I3Xu{g wd]سY%c:\6sWD:Q8Ifݡd]N!d5&Q H=ີo?}EYl_`/E9 DZOo%Ƞ Q*8n9ԡ0ggfulJ,UϞ)C1^LƄFsl Xk2FwsZB E/mPIA!f>$.}4=@Hѵ=]l i$RWa9ɳT4/x2aE$dHT!n DA<-\޺:{KCuxg}m@1C*H,SnL7{)IVrm~]ks@j=( й{ܟonٳyd#=ŲX'^&NN刕틖_t}yהLY6X^UpMaXό8(dv;ұ0tu^ *rjL!,3lMÖ}#g/RN_3- KiVo5\ؿMjoYhL'?rϜo<ʋ,lY~.iހ:x™˫)\UЯiB^ܭeo&r5luv (\|i{[Vޝwh@UQy&Rn( 'osMQU0)L,*]kj82 Rꊿ;^\U4p[NO493no#6`$̂.ߟq#̝4i#m/ϯxuR*hOHLR}_yKh(8Ȳ'V K-!ۖH,a+G%|@Ϳ_{W @ mה`rIMZ+d1flhr'U;%KK[F'BN<;m5P \Uu_:mufB\h9&'^uptj,%yU]~C9v=-L~t36W]JΗqo7,{,oXrƭNԾ1Pڰw8A@LgҤSffw!6Q,Uۭ% H2GIFf*bq+.-+XNqe֛RJ/}~vZ9G|aAyَ%sㅕDbKaaX; +ʑE%Z~3M-LɉKɷ=^[U;sn 3*wtJV]eYr.2sVP+}\uz<3u@9^vbJ :@E鑙ࡌm?: yG~_}Ŋ# I^b,VVR\Zp@zdT[2PknR%7:vbFA,,/٨zCט/'sd 4^B[Pχ`"NKkz6V6wTrfG,UHn4,cw)󡱲ΈaX˟g/}c;yg;g oglh>\VvC~%7`P ({yܳ 5/:R澰[ͷ}aM=i,0o^-ܜKlφE! pl̠7KJ%pPY 24E~Ƃ9۱D\3_LwltA~)EaRwRr8rN{ebgܣ,cv|U6W,y(@y;8XP3/^:'٢E-1y cXg㱖]jj严l^o6q,AE64j ]p̖*gg@.b% ʮ,aEt\j .dA@e "|}p'@:w?Wfg ehoN4/AaѡY]>|P"ǁ^Jw6c~tRvrwZ/36yd)HTU1.`r| =*SIs<K9IK,t7wzaY\+'91ocqRt (8́a,b[ ex81:@L1*ww)CEKA/QKR%D"_U91<>QC K@B &ghY t<\Ɏ%܀ =>Yb9b)Xi˂׫XOheL5W,3Hhy%d8wN<7Uptf5m@':09y-AP9 K"I+CGG```5?2Yz)~<}62ۖ]9 A/uCh v_mbNe׷ Ņ2N~*ظoA%r*d(K"Y1r ,QK&e@d2z| Btbp{qqC,7O0K!g@I3H)tS^xhNV#rn5`SIس7@%đ&H!8gaƀ-'Uk〥]Ke 9\{_5 t?gC0Y R9V-=;$( \H8R;4trKq@dO`M6l6xe9x*L{[a T (qSY ~K )T&+OFOIz-#a^*o^lƽhқ5Қ˱q-;S%dѶ389bMग़-bl' Kl9Y^)<<3ᯱ,UC&\8?k9R6%AFtF&^-|;`_Y R8 ISl0=4I ɨi3  Xl(7 UNe]%t|IcO^\t:VWdBM)m%1+5~dT-ɿkTmuBIQp˖zl`dyZ:,O5dmϽ Wpg_} #aY []ج_;/Ӧ-dm/5r {U}ҵׅC cy?J͖$5}!TU} 6 SV۳oߋw-Y3xz _?#,UJGwY̚Rgby`K K[)YU1ޛ hU%>3GE|}7z"!̬ү^r/}o*lτ(%54s;CQ, 7.8D/ ǎPjk)oHzKGkjX{)Iԣ+2&2?i@=lGMtJ55)y6AkmBn2z3/Y~!>b Nґ\X?+XڶJD9/Gt$׶ H=IENDB`@7Dd XVR  C AIOC"`b6 =0q5v63"nn6 =0q5PNG  IHDRv8}PLTEd:(X"j4Y+xs8cUy|PLٰOMMMVD%aFEنLLLCFDDzzzyyzzyzzz{ަ⽼ccc隚OAXWW8ك\I6q,yXXXcbbboonfYXXIpon]2O>ZƷ内0MYňքGmIV?ooop/ݛ=/7ce@}]nnnӶ5폏c󏏐նNHopͩ8#kNeN|ѽ9&q꡴q}\&q>%rҵd-~'rqr?HoܙXO\VԎcԄHmӟWZş(hhƐTLRy0M}ce!k!k|а-~5}>q<{ډʋaRt|:͙bKGDH cmPPJCmp0712Hs2IDATx^}`Wmcladz؞]"I$d@DL6ـLc{q9sYxrݙߟsi=W[- D[ޫT*y$T@?xKOi3Ttzje${6$g t:P!ރG-     gSZΤtn|tݓW=e.z&}sL>gҷ]7wI(, g9Wͻ/~/ۼot;mM6d3l.e9yR~s_>?0~˶o}@XL}^~o22l/8߭S#Nk]97r9'x{ [T <ò웗J\J 'p)kX# "dsB64eJ,kA ab5>^&2ݻ-luH{]ُFB1SJ8R3u8^rvMF+]ž &:P9F:;tdc.iC#~7"bڄoSC68r_3_N75xOVE|kHA۵q~!ЩW/& ?{wIC#Cvw5u]IGu^6#A{kkuW|ˣC|S蓨ӓR(d E82R^tG!5Y[ >3Řq=,uM*^׈H ~ܐ<ެegڶrNzaHMW*!q4'VRnX3dMk;xt' ,͞>p{~O-=xZn3 2$ S"@  ?9VuQM&۽sg?#Nn|EDC3Lw4IM4H0H}*q,W!lhE#&bj҅1^׀2| qЛ8_z ?QbcwsS߱`i((+]8dD_ilMPA ,vơuiF64o(a| 4{+,\s M3 8ah{C0JVgN(Ƹo 퍳x|H;Dzu,--^w%x;]3:ާ҅* IE%H-Eخ/ :#w4H`p4[uͮ+APPSD-6htJAR\JX7l2%k ͨ,#Iyq#u)UpuԸF)H4xػ:QMwi*UJ/> 5ñ|7i6!5;ᢚq n8q+,RgԭS/|K%ސc|T2iiUE\_q[+BhA!}R0Y%'$ؕp 75;d`˪1^#tݮIUTmlwv=N3QQj#`Rsi^Vb T0]d۝Sib-ė/C&-Ғg_)Y y=i'9].= g[j .PIcظy΅'UvA]IPFyA;F<+U_r(-;PA 2ixw:Br = o Jtx+D?< ڵ616>OKZ'%Y4Bh]ƭ}/y8C+9T(*{"Tqk@K$ u5QרI?^ #\s9΍Z{e.{# &W2XRqej;➵f2hR9n,āӺ7iucX 'ƒ. Q0yah r)9z8B7NX. MT&"klMX5صb9^>yiL $d}mU+x`MG%~LK*xe5S qԑݕܕPok5QC5FMȕiԃc*5a|Äx&'go P[Z,f1fzvf3s!:M4FNiT*͓=H Bd9uU:8?ऺGdGc1QF !N*r_IF8q6]67ƃfrCJBvUuli|KO@<}U1:8i]_(>RF*RB+B/xӪtQ)"\VFNAЄbc4FL43Mz<:2StxwL52MKGa@@͏>ÎO|٣<׀R=#ȗJ~M9[Α§*Oh!kGC[@|jJ.2ɗѩ Fii`y!i T QI42u `O;V+kv'F5 m rP&Չ&r7o40(˷`2BWk*JR+VE,%l^*:D M̥en~%% (l{jU~oH``-wl]ŴJi2 H)]F D\›jeS)-=A 8O _2!GIFT2/'EжєP8uz`"#f FعU.rjDK#)+losG6'ZzըqTG`dqycW}k/.^JIIm4Kuz^[`Ψ);kAB&X z5lm(ଲRVV_nrKĥJRvMXԁd0['`1祾DwWeNK5V$ 278͗{$ao*KҋZ:F_/}r*2S'3>-b-Ed]TW+]6ƬVVb ^fQy<~̅KDTwę:Z!fCI`Ȕ$wD4.E\*X# p}KEC@Td.UuqvtobRq_twq;Ǐ[8kJFFdAhnGS@2d-[lOrDۧ-!be,0+u~$҈DԎ C#;V$u"9 J$t́D H]H I&H)XǞ.@afo~sYT#ȋ9^ Vy{u$(d)G75~̠ ^njtbQ1^>Gd jrPL?KBlqpGeãSr, w ųzg ~Qz7Djžiބؑ,Gɕ]s2Z< JHWWضߑ TF:|f%a:\J1t2Wy[2ڦ/y`lp?tOIPmϯE@P}%lM 6r49 6:YwHOy upf iK xF]om[U`Nbo2&҈aWt<+\&DrġÚ]<0GS*\N9dJ[yQ#MWG2Ś[|-qԌi_Z%P6:(mlUv/9z,J]eu'wMcGj%ݕ9 uda4˩;kvT/F|_h[2`9Y֟KmD2y/p=a k|-=Hq$P;O=(5W J(hZ@w*NLVTHbuSg1p{?PF,8DN{waa-5_Xq"&Mc>.&9V9FgS%%!/zZe!=o~D 9K&bAmOPySѱSvoPU t.ζg  M(/3ԴVAc}RAuuz)'1IF(R/Rd*O-#5ktʛ +NE uUTZ7w<= 3j7G=/`ηQǦr(#q(KAqpx?)EVd#HauF$dxR.-:՘-cƧks2_R|5T% zVVq1=>}ccmV]};R)Yⷠs}cn/ة{^mw`M}EKj%%0=T-'e-ɚ^W쌒cj{K9LmHH '@DUWTi=V<~K%O/Zm;ZHv!(XiwcO\dIӡ̻C\vhNf nO!z(U;̀E yK6jC'l~*îlnz?-֔/ȃB:-p9Tq.c΁Gdjg &fb mU] t2yOlkQEظ~IO6ׁe(H B+4uI0_R I%W^= 9$ujMazMQDdEnR!Fc] Vh|^$eh^*.uǣD'z{.9wy+f.كKM"2/Dd$V9 pjإ Qkaٞu;ۓ*&0t/B>sT{ Ql.Yo mSr c-΂1p){sߓbdK| Zda MogYI:uE.Wyu [ikk"es4F"1-cLӉ-+YϠ)g>qbXIm2^Ĭ="w ŠMAdA3ZO£QA`ш=?d:g|~Ѝcv \zݻ2i= 3Ob!k`׏쎒v͕VdI,C&dp3i YyLSNmGbp5ǡ՞|MFPGs] u|Z?KZH0rdAU6tG"?I䲽Q|_^j4ޒrbf"-R1#2e ե*h]0*-.,1IEd?QְSe]o>̪18@E/<ڪ* X{4JUpKr;'HFUO+`|!+y3,量t@(Ѝ==q郪^\oGʫzkuU2oR<,9]v{{ƻC`,Z%_]ЌW dYtԺ)UY-]q%cLv %XnbZ@F/F7"6L^7K\^CvA^ۀ_01.uT!E6XN~bzpŋxU16i]L?-\Bӎxp&)Jy^BTZ[X*ur=)h3Idy2pW–H:YVQRer8A*SAIO ڑݖR␜L2Nj몆eT n-r6SgZt`cgw⫴!v+LTTh[ŞLI8_?4mkY+\՟l?p3<XA@oZxOOw+Up$}ݾe]Ƹ"ʯ.ɇ *e#<ۡ-z>Et;WY'{.%ABȡYKihH:N'z,]"W L2 Ԣst$@ 1{{}z 'zP4mp}XFyڄ~M{f: @t?Л}!P"sfdm)E1[zO1H|nv2&\05oylyyZxSJG&}|n}{E^  J7F< nY:յ[?B[,Y 25B{2c(i#l'>ag(g khT`'܆ƳZg@y`ջ p\ ޅw܇[- .f·(|eR^{u#OC+Eqo[a*iv`FyB'`6?ܯ>EydGDz6$}+YМnک]-Zl"Bt4Z kD. WK5R8ӎ:~V {^|BVGxw7Nv^-џg`\1w_E.1˔%7x:liTWKH8ryL}+| ɳw!-Z6*_ǝZx[4ص]"GsyMNC^Ļϖ69l-\8G"/ g/'eѷ 6V]M LwFָmq|]R ?g hN UYE6[M|^]3PyelB/'S4 ?Dt#RbBcsrTv^Kå&^+6'2ßG5P "0Yy#/x9uY&>VmּbE7ȋ32oXt; ByFY]s728`=kaMv v_ǹ1N{W6}^4 ŀrWDZF_gN">{<e/"q!9*yK9u`.Jҋ<)H4ز_!g ֒Rfr4ΞgE{@{jAR({⍉ mM~ѳh?>o0}_=&#/ك^aS_ަ\fu7ᨇ2T:ɮu#g, n;D/QBRpZr=ndaɎMzހ863Gʏt@W1FtQ<"cޅCifm\xw{(&d gwHB@ڼoݾ͙tCQJePOa/:=U2 {>W-3ER)1 nd|,71Qʵ6ڒ8lx”KJ7Vd$g(Ǽ7G>tAwPݸKċ?xT(.N+e%N ke%Ui2x9Rtp¯ X8J6/X3 e`[2c[̶|ib7ڪ߹<['8OF2V/;pğK|Ujԝ)/S.YCfGҊH5IJrvDP6I~%))D.DyK@69I9JNlG.Sr"P/HIK$&.޶" wPу]m_pq{VKպnDvM;bq jɠvpqaP k}? % dvveøPx蛗25tӗM7Yn fVVM_}@!gO+IR& z?XEI`ž*){ϜJ+Jݠ+HLbP.@%x@>_El<CvjOFvMefc N;Հss_8qL~ya1eL0*eӚRi=cgw8:Su,꣡T2(/CWp.r`@u]VvK_?F0NcaF1 "]i1RGϷݨGd`q6aK2rN l7]h<U9y؍!xlքpYzQ}9yIMXsA|tB7('lc~;*; 9Ou3j*3gS5EJE)[M9W-=bLv.rE6DUK9?tQŒ@_\:>F1_?P> P{wwjϗy7x\jo~jucF'͛sH$ 0ooO@,T]ws%FRTх6i dCKސ cfk~ƱH^@@@@@@@@@@@@@@@@@P#б򕕇3{瓢^skեkڟ3X" >C_*ܓ΁? >z                      C@Ɔ^o>gd:+j?Ӄi7g$k=6ig+|K!e ,IENDB`DyK !http://marinemetadata.org/meta-tyK Bhttp://marinemetadata.org/meta-tDyK  http://icoads.noaa.gov/climar3/yK @http://icoads.noaa.gov/climar3/}DyK _Toc175549315}DyK _Toc175549315}DyK _Toc175549316}DyK _Toc175549316}DyK _Toc175549317}DyK _Toc175549317}DyK _Toc175549318}DyK _Toc175549318}DyK _Toc175549319}DyK _Toc175549319}DyK _Toc175549320}DyK _Toc175549320}DyK _Toc175549321}DyK _Toc175549321}DyK _Toc175549322}DyK _Toc175549322}DyK _Toc175549323}DyK _Toc175549323}DyK _Toc175549324}DyK _Toc175549324}DyK _Toc175549325}DyK _Toc175549325}DyK _Toc175549326}DyK _Toc175549326}DyK _Toc175549327}DyK _Toc175549327}DyK _Toc175549328}DyK _Toc175549328}DyK _Toc175549329}DyK _Toc175549329}DyK _Toc175549330}DyK _Toc175549330}DyK _Toc175549331}DyK _Toc175549331}DyK _Toc175549332}DyK _Toc175549332}DyK _Toc175549333}DyK _Toc175549333}DyK _Toc175549334}DyK _Toc175549334}DyK _Toc175549335}DyK _Toc175549335}DyK _Toc175549336}DyK _Toc175549336}DyK _Toc175549337}DyK _Toc175549337}DyK _Toc175549338}DyK _Toc175549338}DyK _Toc175549339}DyK _Toc175549339}DyK _Toc175549340}DyK _Toc175549340}DyK _Toc175549341}DyK _Toc175549341}DyK _Toc175549342}DyK _Toc175549342}DyK _Toc175549343}DyK _Toc175549343}DyK _Toc175549344}DyK _Toc175549344}DyK _Toc175549345}DyK _Toc175549345}DyK _Toc175549346}DyK _Toc175549346}DyK _Toc175549347}DyK _Toc175549347}DyK _Toc175549348}DyK _Toc175549348DyK http://www.jcomm.infoyK .http://www.jcomm.info/DyK Fhttp://www.wmo.ch/pages/prog/amp/mmop/documents/JCOMM-Strategy-v1.pdfyK http://www.wmo.ch/pages/prog/amp/mmop/documents/JCOMM-Strategy-v1.pdfDyK http://www.ceos.org/yK *http://www.ceos.org/DyK http://www.iode.org/yK *http://www.iode.org/ADyK 3http://www.wmo.ch/pages/prog/www/WIS-Web/home.htmlyK fhttp://www.wmo.ch/pages/prog/www/WIS-Web/home.htmlDyK *http://www.ngdc.noaa.gov/wdc/wdcmain.htmlyK Thttp://www.ngdc.noaa.gov/wdc/wdcmain.htmluDyK @http://www.wmo.int/pages/prog/gcos/Publications/gcos-92_GIP.pdfyK http://www.wmo.int/pages/prog/gcos/Publications/gcos-92_GIP.pdfDyK 'http://www.wmo.ch/web/www/TEM/gts.htmlyK Nhttp://www.wmo.ch/web/www/TEM/gts.htmlDyK (http://www.wmo.ch/web/www/WMOCodes.htmlyK Phttp://www.wmo.ch/web/www/WMOCodes.html)DyK -http://physics.nist.gov/cuu/Units/index.htmlyK Zhttp://physics.nist.gov/cuu/Units/index.html)DyK -http://www.unidata.ucar.edu/software/netcdf/yK Zhttp://www.unidata.ucar.edu/software/netcdf/1DyK /http://wo.jcommops.org/cgi-bin/WebObjects/ArgoyK ^http://wo.jcommops.org/cgi-bin/WebObjects/ArgoDyK http://www.oceansites.org/yK 6http://www.oceansites.org/DyK http://www.ifremer.fr/gosud/yK :http://www.ifremer.fr/gosud/1DyK /http://www.cgd.ucar.edu/cms/eaton/cf-metadata/yK ^http://www.cgd.ucar.edu/cms/eaton/cf-metadata/DyK http://www.hdfgroup.org/yK 2http://www.hdfgroup.org/DyK hhttp://ioc.unesco.org/oceanteacher/OceanTeacher2/01_GlobOcToday/06_OpOc/04_GOOS/Prospectus/contents.htmyK http://ioc.unesco.org/oceanteacher/OceanTeacher2/01_GlobOcToday/06_OpOc/04_GOOS/Prospectus/contents.htmDyK Hhttp://www.iode.org/marinexml/files.php?action=viewfile&fid=4&fcat_id=3yK http://www.iode.org/marinexml/files.php?action=viewfile&fid=4&fcat_id=3DyK http://marinemetadata.org/yK 6http://marinemetadata.org/DyK http://dublincore.org/yK .http://dublincore.org/-DyK .http://www.iso.org/iso/en/ISOOnline.frontpageyK \http://www.iso.org/iso/en/ISOOnline.frontpageDyK http://dmac.ocean.us/index.jspyK >http://dmac.ocean.us/index.jspDyK http://www.fgdc.gov/yK *http://www.fgdc.gov/DyK http://www.isotc211.org/yK 2http://www.isotc211.org/DyK http://gcmd.nasa.gov/yK ,http://gcmd.nasa.gov/]DyK :http://www.wmo.ch/pages/prog/www/ois/pub47/pub47-home.htmyK thttp://www.wmo.ch/pages/prog/www/ois/pub47/pub47-home.htmDyK http://www.odas.org.cn/yK 0http://www.odas.org.cn/DyK http://www.opendap.org/yK 0http://www.opendap.org/9DyK 1http://ftp.wmo.int/pages/about/Resolution40.htmlyK bhttp://ftp.wmo.int/pages/about/Resolution40.htmlDyK Khttp://www.iode.org/index.php?option=com_content&task=view&id=51&Itemid=95yK http://www.iode.org/index.php?option=com_content&task=view&id=51&Itemid=95DyK Rhttp://www.oco.noaa.gov/index.jsp?show_page=page_status_reports.jsp&nav=observingyK http://www.oco.noaa.gov/index.jsp?show_page=page_status_reports.jsp&nav=observingDyK http://www.godae.org/yK ,http://www.godae.org/DyK http://www.ghrsst-pp.org/yK 4http://www.ghrsst-pp.org/1DyK /http://wo.jcommops.org/cgi-bin/WebObjects/ArgoyK ^http://wo.jcommops.org/cgi-bin/WebObjects/Argo5DyK 0http://e2edm.meteo.ru/e2edm/index.php?section=1yK `http://e2edm.meteo.ru/e2edm/index.php?section=1DyK http://www.icsu.org/index.phpyK <http://www.icsu.org/index.phpADyK 3http://wo.jcommops.org/cgi-bin/WebObjects/JCOMMOPSyK fhttp://wo.jcommops.org/cgi-bin/WebObjects/JCOMMOPSDyK http://icoads.noaa.gov/etmcyK 8http://icoads.noaa.gov/etmcs$$If]!vh5%#v%:V l%65%/  / a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l;%65%/ /  a]p s$$If]!vh5%#v%:V l %65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l7%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l8%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l;%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l;%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l8%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l8%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l(%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l;%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l;%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l*%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l+%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l+%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l %65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/  / a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l;%65%/ /  a]p s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l(%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l;%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l:%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l+%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l:%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l8%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l %65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l;%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l;%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/  / a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l;%65%/ /  a]p s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l'%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l8%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lI%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/  / a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l;%65%/ /  a]p s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l7%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l6%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l+%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l9%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l+%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l:%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l+%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l %655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l %655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V lU%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V lE%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lI%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l9%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l8%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l(%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/ /  a]p $$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l+%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V lE%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l4%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l;%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l%65%/  / a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<s$$If]!vh5%#v%:V l;%65%/ /  a]p s$$If]!vh5%#v%:V l;%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<K$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l %655@5 555d /  / / / / /  a]p<=$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l&%655@5 555d /  /  / / /  a]p<s$$If]!vh5%#v%:V lv%65%/ /  a]p $$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V l%655@5 555d /  /  / / / /  a]p<$$If]!vh55d##v#vd#:V l;%655d#/ /  /  / / /  a]pK$$If]!vh55@5 555d #v#v@#v #v#v#vd :V lE%655@5 555d /  /  / / / /  a]p<,D@D 9NormalCJ_HaJmH nHsH tHn`n @U Heading 1$<@&25CJ KH OJPJQJ\^JaJ mH nHsH tHp`p @U Heading 2$<@&456CJOJPJQJ\]^JaJmH nHsH tHj`j @U Heading 3$<@&.5CJOJPJQJ\^JaJmH nHsH tHp`p @U Heading 4$$ 01$@&a$)5>*CJOJPJQJaJhmH sH tH ``` @U Heading 5$@&+5B*OJPJQJ\aJmH phsH tH h`h @U Heading 6$@&35B*CJOJPJQJ\^JaJmH phsH tH n`n @U Heading 7$$@&a$35B*CJOJPJQJ\^JaJmH phsH tH T`T @U Heading 8$@& CJOJPJQJaJmH sH tH ^ `^ @U Heading 9 $@&)B*CJ(OJPJQJaJmH phsH tH DA@D Default Paragraph FontRi@R  Table Normal4 l4a (k@(No List4@4 9Header  9r POP 9Marge$ 7G$a$PJhmH sH tH .)@. 9 Page Number4 @"4 9Footer  !6U@16 h/ Hyperlink >*B*phPC@BP h/Body Text Indentx^CJPJlR@Rl h/Body Text Indent 2h^h`CJOJPJQJmH sH tH <P@b< @U Body Text 2 dx>Q@r> @U Body Text 3xCJaJ\`\ @U Balloon Text(CJOJPJQJ^JaJmH nHsH tHFV`F @UFollowedHyperlink >*B* phjoj @UDefault 7$8$H$5B*CJOJ PJQJ ^J _HaJmH nHphsH tHF`F @UTOC 1 OJPJQJaJmH nHsH tHN`N @UTOC 2 ^ OJPJQJaJmH nHsH tH^`^@UTOC 3 ! ^'CJOJPJQJaJmHnHsH tHuN`N @UTOC 4 ^ OJPJQJaJmH nHsH tHN`N @UTOC 5 ^ OJPJQJaJmH nHsH tHN`N @UTOC 6 ^ OJPJQJaJmH nHsH tHN`N @UTOC 7 !^ OJPJQJaJmH nHsH tHN`N @UTOC 8 "^ OJPJQJaJmH nHsH tHN`N @UTOC 9 #^ OJPJQJaJmH nHsH tHRB`BR @U Body Text$$CJOJPJQJaJmH nHsH tH.X`Q. @UEmphasis6]B' aB @UComment ReferenceCJaJX`rX @U Comment Text'$CJOJPJQJaJmH nHsH tHTZ`T @U Plain Text($CJOJ PJQJ ^JaJmH sH tH nY`n @U Document Map)-D M (CJOJPJQJ^JaJmH nHsH tHV^`V @U Normal (Web)*dd[$\$PJmH nHsH tH@j`qr@ @UComment Subject+5\<  <@0e    ]^_`?@RS`axy 45*+  NOKL @$A$%%%%%+(,())*E**.+/+#,$,,,s-t---//113344557788c:d:;;>>y?@@@AmBnBBB6D7DEEFFSH\H]H^HyHzH{HHHHHHHVII"JJJFKKKBLLLMMMMENNNhist_`qr34LMz{?@`atu'(9:KLYZ12 @Aqr     v w   ( ) ;<wxefQ R     ""j$k$%%u&w&))**+++++00000I5J566774858D8E8I:J:m<n<"@#@@@@}A~A,B-B.BCC5D6D7D&E'EEEEE[G\GIJJJKKLL L LNNNN1R2RSSeTfTUUUUUUYY [ [[[\\\\^^R`S`aaaaaccYdZd[d*g+gDhEhnjojllkmlmmm}o~oppEpFpNsOstttuuwwxxxx?{@{}}Q~R~~;<ӂԂՂنچyz{QR؍ٍڍ*+JKL()012ǙgΜϜTU£NOPop>? nsrs 578ùĹ<=OPʿ˿uv9:fgyz*+, "#12 23,-tu`a(3.H] 7kl^}~!))yCD?<`av;_.i    X  6 7  T    O{no[mn*y  ]&'  ;!!P"C#W#X##]$%%%Z&''`'(W)p)q))*++++- . ..0011T234445"6666z7999:;k;;g<h<0=}>?? @A}AAAB BDD$D%DDE\EETF@GAGGMHHtIuIJJLLwLMvMwMMDNNNrOCPP8Q9Q0RSSSTUUUVqVVWWXYYYZ1[2[P[Q[*\\\\~]]N^O^^t__````vaa,b-bbbcc7ddee.e/eeefffgghhhhdiiHjIjjkkklll1mymzmmmnn.owoppp!qqqqqqqqqqqqr rrrrrrrrrrrrrss&ssssssstttutvtxttttttuu1v2v4v6vvvvwwwwwwwxxxxy%y,yEyFyHyJyyyzz z"z$zzzz {!{#{%{{{{{{{{T|_|f|r|s|u||||||||}}}}}}}}}}}i~t~{~~~~~oz)*,TUWY؀ـۀ݀сҁԁցǂȂBCEpqsuŃ=HO[\^`Ƅ҄ӄBCEGˆ̆ΆІq}5cjbce~3468 EPWƌnjɌCNUabdf!ju|[̏͏Ϗя{.9@WXّڑܑ(W^oprt̒גޒi|CDFijln#*CDFHޕߕ8ELXY_`bߗ   QRabdijln89;WXZ\/QXqrtv  !#%͛ΛЛқ%/6BCƜǜɜޜߜ7cjUel؟ٟ۟ݟ(?Fy£ͣԣ¤ɤ_jqϥХҥƦ   !#%ȧϧlw~ !#%!:;ΪϪѪū 4579Ǭά679UVXZ-OVoprt"UVXZ ұӱձױ%18̳ͳϳѳ?OVqr޴ߴBMTALS_`bd*1=>ոָظ+8?GHJL¹ù/02RSUWٺ Ż޻߻Z_frs  '(*,߽L|ľžǾ&JKMO,7>WXZz{})4;TUTjq EFHhikm-DKdegi`w~y$%'\]_a"./  z{ !#^_ac./1\]_aFcjvwx ':;=?{[gnJU\OT[tu  9:<>5:AMNNY`lmoqyz| pqs!mn'(*?@BDzUx 9:<>OPQ:;=? #$&(pkOZaq|fqx5<DEGIBC%,   alsCDF_`bdIT[ !#%  JKhszDEG_`bdrwjk !#%346LMOQ5BIQRTwxz|AH`ace'.GHJL07tuw#$&(ghjl5>EMNPefhj      = > @ B        \ g n        @ A C E    3 4 6 8 %>?AC $%RW^yz|~05<z{}ZelNOQklnp=>@BQEX_ghjl%8?GHJLgz$7>WXZ\  FQX`ace+ 6 = S T        d!|!!!!!!! ""-"."0"J"K"M"O""""""""#[#b#j#k#m#o########Z$e$l$$$$$w%%%%%%%&&&&&&&'''''''(((((')()*)G)H)J)L))))))))*%*,*9*:*<*>*`*w*~*++++ +"+$+g+++++++3,>,E,[,\,^,x,y,{,},,,,----S-c-j--->.?.A.e.f.h.j.....//////////>0I0P0y0z0111+1,1.10111122202123252223 333333333334444444455 55555'5+52595:5<5=555555556N6U6e6f6h6j66 77,7-7/717W77777777777788 9&9-9J9K9M9O9:$:+:<:=::::;;;;2;=;D;W;X;Z;o;p;r;t;;;;w<x<y<{<|<~<<<<<<<<<<<<<<<<<0000000000000000000000000000000 0 000000 00 00 00 00 00 00 00 00 00 0 0 0 0 0 0000 00 00 0 0 0 00000000 00 00 00 00 00 00 00 00 00 00 0 0 0 0 0 0 0 0000 00 00 00 00000000000000000000000000000000000000000000000000T0T0T0T0T0T 0T0T 0T0T 0T0T 0T0lS0QS0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0A^0QS00 0 0 0 0 0 0 0 000 0 0 0 0 00000QS0303(030J0J0J0J0J0J0J0J0J(030P0P0P0P0P0P0P0P0P0P* 0P* 0P* 0P0P0P0P0P0P0P0P0P0P0P0P0P0P(03000(03000000000000(0300000000000(03000000000000000QS0 0 0 (0 0U0U0U0U0U0U0U0U0U0U0U0U0U0U0U0U0U(0 000000000000000000000000000000(0 000000000000000000(0 0 0 0 0 0 0 0 0 0 0 0 0 0 (0 000000000(0 0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x0x(0 06(06(06(06(06(06(06(06(06(06(06(06(06(06(06(06(06(06(06(06(06(06(0606(0 0gD0gD0gD0gD0gD0gD0gD0gD0gD0QS0J0J0J(0J0TM0TM0TM0TM0TM0TM0TM0TM0TM0TM0TM(0J0kT0kT0kT0kT0kT0kT0kT0kT0kT(0J0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z0Z(0J0n0n0n0n0QS0Ls0Ls0Ls0Ls0Ls0Ls(0Ls0"w$0"w$0"w$0"w$0"w0"w0"w0"w$0"w$0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w$0"w$0"w0"w0"w0"w0"w$0"w$0"w$0"w$0"w0"w0"w$0"w$0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w0"w+ 0"w+ 0"w+ 0"w+ 0"w0"w0"w0"w0"w0"w(0Ls01$01$010101010101$01$01$01010101010101(0Ls0000& 0% 0% 0' 0' 0' 0' 0' 00000000000$00000(0Ls$0`0`0`0`$0`$0`$0`0`0`0`(0Ls$0a$0a$0a$0a$0a$0a$0a$0a$0a$0a$0a$0a(0Ls$0$0$0$0$00QS0000000000000QS00000000000000000000000000000000z0z(0z0 0 0 0 (0z0Q0Q0Q0Q0Q0Q0Q0Q0Q0Q0Q0Q0Q0Q0Q0Q(0z04040404040404040404040404040404040404040404040404040404040404000(00A0A0A0A0A0A(00000000000000(00` 0` 0` 0` 0` 0` 0` 0` (00000(00<0<0<0<(00000000000000000000000(00!0!0!0!0!0!0!0!0!0!0!0!(00(0(0(0(0(00*0*(0*0,0,0,0,0,0,0,0,0,0,(0*0+30+30+30+3(0*0C50C50C50C50C50C50C50C50C50C50C50C50C50C50C50C50C50C50C500@0@0@(0@0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B(0@0Y0Y0Y0Y0Y0Y0Y0Y0Y0Y0Y0Y0Y0Y(0@0K_0K_0K_0K_0K_0K_0K_0K_0K_0K_0K_0K_0K_(0@0c0c0c0c0c0c0c0c0c0c(0@0.g0.g0.g0.g0.g0.g0.g0.g0.g(0@0j0j0j0j0j00$l0$l0$l0$l0$l0$l0$l0$l0$l0$l0$l0$l0$l0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l0$l0$l0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l0$l0$l0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l0$l0$l0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l 0$l000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0@0h00@0h00@0h00@0h00@0@0@0@0@0@0@0@0@0@0Ph00<e    ]^_`RS`axy 45*+  NOKL @$A$%%%%%+(,())*E**.+/+#,$,,,s-t---//113344557788c:d:;;>>y?@@@AmBnBBB6D7DEEFFSHyHzH{HHHHHHHVII"JJJFKKKBLLLMMMMENNNhist_`qr34LMz{?@`atu'(9:KLYZ12 @Aqr     v w   ( ) ;<wxefQ R     ""j$k$%%u&w&))**+++++00000I5J566774858D8E8I:J:m<n<"@#@@@@}A~A,B-B.BCC5D6D7D&E'EEEEE[G\GIJJJKKLL L LNNNN1R2RSSeTfTUUUUUUYY [ [[[\\\\^^R`S`aaaaaccYdZd[d*g+gDhEhnjojllkmlmmm}o~oppEpFpNsOstttuuwwxxxx?{@{}}Q~R~~;<ӂԂՂنچyz{QR؍ٍڍ*+JKL()012ǙgΜϜTU£NOPop>? nsrs 578ùĹ<=OPʿ˿uv9:fgyz*+, "#12 23,-tu`a(3.H] 7kl^}~!))yCD?<`av;_.i    X  6 7  T    O{no[mn*y  ]&'  ;!!P"C#W#X##]$%%%Z&''`'(W)p)q))*++++- . ..0011T234445"6666z7999:;k;;g<h<0=}>?? @A}AAAB BDD$D%DDE\EETF@GAGGMHHtIuIJJLLwLMvMwMMDNNNrOCPP8Q9Q0RSSSTUUUVqVVWWXYYYZ1[2[P[Q[*\\\\~]]N^O^^t__````vaa,b-bbbcc7ddee.e/eeefffgghhhhdiiHjIjjkkklll1mymzmmmnn.owoppp!qqqqqqqqqqqqr rrrrrrrrrrrrrss&ssssssstttutvtxttttttuu1v2v4v6vvvvwwwwwwwxxxxy%y,yEyFyHyJyyyzz z"z$zzzz {!{#{%{{{{{{{{T|_|f|r|s|u||||||||}}}}}}}}}}}i~t~{~~~~~oz)*,TUWY؀ـۀ݀сҁԁցǂȂBCEpqsuŃ=HO[\^`Ƅ҄ӄBCEGˆ̆ΆІq}5cjbce~3468 EPWƌnjɌCNUabdf!ju|[̏͏Ϗя{.9@WXّڑܑ(W^oprt̒גޒi|CDFijln#*CDFHޕߕ8ELXY_`bߗ   QRabdijln89;WXZ\/QXqrtv  !#%͛ΛЛқ%/6BCƜǜɜޜߜ7cjUel؟ٟ۟ݟ(?Fy£ͣԣ¤ɤ_jqϥХҥƦ   !#%ȧϧlw~ !#%!:;ΪϪѪū 4579Ǭά679UVXZ-OVoprt"UVXZ ұӱձױ%18̳ͳϳѳ?OVqr޴ߴBMTALS_`bd*1=>ոָظ+8?GHJL¹ù/02RSUWٺ Ż޻߻Z_frs  '(*,߽L|ľžǾ&JKMO,7>WXZz{})4;TUTjq EFHhikm-DKdegi`w~y$%'\]_a"./  z{ !#^_ac./1\]_aFcjvwx ':;=?{[gnJU\OT[tu  9:<>5:AMNNY`lmoqyz| pqs!mn'(*?@BDzUx 9:<>OPQ:;=? #$&(pkOZaq|fqx5<DEGIBC%,   alsCDF_`bdIT[ !#%  JKhszDEG_`bdrwjk !#%346LMOQ5BIQRTwxz|AH`ace'.GHJL07tuw#$&(ghjl5>EMNPefhj      = > @ B        \ g n        @ A C E    3 4 6 8 %>?AC $%RW^yz|~05<z{}ZelNOQklnp=>@BQEX_ghjl%8?GHJLgz$7>WXZ\  FQX`ace+ 6 = S T        d!|!!!!!!! ""-"."0"J"K"M"O""""""""#[#b#j#k#m#o########Z$e$l$$$$$w%%%%%%%&&&&&&&'''''''(((((')()*)G)H)J)L))))))))*%*,*9*:*<*>*`*w*~*++++ +"+$+g+++++++3,>,E,[,\,^,x,y,{,},,,,----S-c-j--->.?.A.e.f.h.j.....//////////>0I0P0y0z0111+1,1.10111122202123252223 333333333334444444455 55555'5+52595:5<5=555555556N6U6e6f6h6j66 77,7-7/717W77777777777788 9&9-9J9K9M9O9:$:+:<:=::::;;;;2;=;D;W;X;Z;o;p;r;t;;;;w<x<y<<<0000000000000000000000000 0 000000 00 00 00 00 00 00 00 00 00 0 0 0 0 0 0000 00 00 0 0 0 00000000 00 00 00 00 00 00 00 00 00 00 0 0 0 0 0 0 0 0000 00 00 00 0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0 @0@0I @0d @0d @0d @0d @0d @ 0d @0d @ 0d @0d @ 0d @0d @ 0d @0d @0I @09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@09@0I @0@@0@@ 0@@ 0@@ 0@@ 0@@ 0@@ 0@@ 0@@ 0@@0@@0@@ 0@@ 0@@ 0@@ 0@@ 0@@0@@0@@0@@0I @0+I@0+I*@0+I@0BL@0BL@0BL@0BL@0BL@0BL@0BL@0BL@0BL*@0+I@0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR@" 0HR@" 0HR@" 0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR@0HR*@0+I@0j@0j@0j*@0+I@0l@0l@0l@0l@0l@0l@0l@0l@0l@0l@0l@0l*@0+I@0 v@0 v@0 v@0 v@0 v@0 v@0 v@0 v@0 v@0 v@0 v*@0+I@0{@0{@0{@0{@0{@0{@0{@0{@0{@0{@0{@0{@0{@0{@0I @0@0@0*@0@0M@0M@0M@0M@0M@0M@0M@0M@0M@0M@0M@0M@0M@0M@0M@0M@0M*@0@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ@0ܛ*@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0*@0@0@0@0@0@0@0@0@0@0@0@0@0@0*@0@0@0@0@0@0@0@0@0@0*@0@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p@0p*@0@0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@$0@0*@0@0_@0_@0_@0_@0_@0_@0_@0_@0_@0I @0@0@0*@0@0L@0L@0L@0L@0L@0L@0L@0L@0L@0L@0L*@0@0c @0c @0c @0c @0c @0c @0c @0c @0c *@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0*@0@0'@0'@0'@0'@0I @0D,@0D,@0D,@0D,@0D,@0D,*@0D,@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@00@# 00@# 00@# 00@# 00@00@00@00@00@00*@0D,@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U@0)U*@0D,@0b@0b@0b@0b@ 0b@ 0b@ 0b@ 0b@ 0b@ 0b@ 0b@ 0b@0b@0b@0b@0b@0b@0b@0b@0b@0b@0b@0b@0b@0b@0b@0b*@0D,@0Xq@0Xq@0Xq@0Xq@0Xq@0Xq@0Xq@0Xq@0Xq@0Xq*@0D,@0Yw@0Yw@0Yw@0Yw@0Yw@0Yw@0Yw@0Yw@0Yw@0Yw@0Yw@0Yw*@0D,@0~@0~@0~@0~@0~@0I @0 @0 @0 @0 @0 @0 @0 @0 @0 @0 @0 @0 @0I @0@0@0@0@0@0@0@0@0@0@0@0@0@0 @0@0x@0x@0x@0x@0x@0x@0x@0x@0x@0x@0x@0x@0x @0@0% @0% *@0% @0 @0 @0 @0 *@0% @0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0*@0% @0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0 @0@0*,@0*,*@0*,@0-@0-@0-@0-@0-@0-*@0*,@021@021@021@021@021@021@021@021@021@021@021@021@021*@0*,@0 7@0 7@0 7@0 7@0 7@0 7@0 7@0 7*@0*,@0;@0;@0;@0;*@0*,@0=@0=@0=@0=*@0*,@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@@01@*@0*,@0L@0L@0L@0L@0L@0L@0L@0L@0L@0L@0L@0L*@0*,@0R@0R@0R@0R@0R @0@0;U@0;U*@0;U@0MW@0MW@0MW@0MW@0MW@0MW@0MW@0MW@0MW@0MW*@0;U@0]@0]@0]@0]*@0;U@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_@0_ @0@0Pk@0Pk@0Pk*@0Pk@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm@0Xm*@0Pk@0@0@0@0@0@0@0@0@0@0@0@0@0@0*@0Pk@0@0@0@0@0@0@0@0@0@0@0@0@0*@0Pk@0q@0q@0q@0q@0q@0q@0q@0q@0q@0q*@0Pk@0ّ@0ّ@0ّ@0ّ@0ّ@0ّ@0ّ@0ّ@0ّ*@0Pk@0H@0H@0H@0H@0H @0@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ@0ϖ@0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ @0ϖ@0ϖ @0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ @0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ@0ϖ`#03," 08 7aaa{{~` * 1[P4QQARRBSTTGUUdVWW.XXYZZ[2\\``9:*59E@ty]g #pxDDv N19nJVQ[dcXf}Lœ}haf!3}IVak2T uk+9}IUajsyzzz{|u|}4~E" rz)T؈ԉNJB[ΎcbƔNduWٙWr|C#FޝE_ lWq #ͣ/Ƥcͫjҭ wβ 6OrU 1ϻq޼MLb=8J/_ J7ZTjEhdw$ .v:Ut MYoypm'Q:#Zq5G%lCTsD3Qw` ' J  t   #   gMeg@6>$W|zeN@  !!g"8#J##z$$W%% &&&`'6((|))-*J**[+m++e,,-../0'11192w233>4^45c5>667I899: ;;;<=2=<==e> ?/???@JA$BB=CZCwDDD      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuwD&?&`&=+>K>HHHI5IQISITIVIvIIIIIIIJJJ J"JBJ_J{J}J~JJJJJJJJK%KAKCKDKFKfKyKKKKKKKKKKKL!L=L?L@LBLbLmLLLLLLLLLLLM,MHMJMKMMMmMMMMMMMMMMMMN$N@NBNCNENeNsNNNNNNNNNNN OO7O9O:O:>A>A>HHHHTTTTTTTTTTTTTTTTTTTTTTTTTTTTX________________ww}}}}bU!!"ssssssssssss99999LL33XXiiiiiiiiiiiirrrrraaaaaaaaaaaa:::::rrrrrrrrrrrr                        ""$$$$Y&Y&0(0(7(7(8(8(--A.A...5858585858EEEEEEEEEEEELLLLLLLLLLLLNNNNNNNNNNUUUUUUUUUU>X>XBXBX\\\\\\\\\\pppppttttttttttttxxxxxxxxxxxxxxxxxxxxxxxxAAppppppppppppgggggg    $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn<@@@@@@  !"#$%&@'()*+,-./01234567@8@9@:@;@<@=@>@?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmno@p@q@r@s@t@u@v@w@xyz{|}~@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ @ @ @ @@@ !"#$%&'()*+,-./0123456789:;<=>?@A@B@C@D@EFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijkl@m@n@o@pqrstuvwxyz{|}~@@@@@@@@@@@     X&X&;>;>B>B>TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTX________________ww~}~}cV++++++++++++""#EEEEEMM44YYrrrrrrrrrrrrssssssssssssJJJJJJJJJJJJ' ' ' ' ' ' ' ' ' ' ' '             ""$$$$Z&Z&1(1(8(8(9(9(--B.B...C8C8C8C8C8EEEEEEEEEEEE L L L L L L L L L L L LNNNNNNNNNNUUUUUUUUUU?X?XCXCX \ \ \ \ \\\\\\DpDpDpDpDpttttttttttttxxxxxxxxxxxxBByyyyyyy¹¹¹¹¹¹¹¹¹¹¹¹ɿɿɿɿɿɿɿɿɿɿɿɿ  88888xxxxxxxxxxx  0000000000000000000000000000000000000nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn<=!w "y! d l߱t=!!D/!!!,!b!!\v "$!,!!w "!!v "t!c!v "tݼ !!l!!?"!@!!|t "- d!!h!7!º!ú<"ĺĭ!ź, ƺ!Ǻb Ⱥ'!ɺ>!ʺ%!˺\!̺!ͺp!κ3!Ϻt "кd!ѺԞ!Һ,'!Ӻ y!Ժt!պ|!ֺw "׺=!غ\`"ٺ$!ں,!ۺ4!ܺ 5!ݺT[!޺[!ߺ, l !! ! !lo!o!Dq q c!,d!4܈!t܈!ܑ!!,\"l\"001TG)"G)","l"""<"|" < |  "ԉ " "y "4z "tz "!!<!t" " " ! $! d!D ! ! !T!!!Z!\Z!Z!v!$w!dw!?!T?!?!t.!.!.! !4"t#< $| % &4!'t!(!)!*!+!?!@>>EETTTMeMeffFu&&[$$(]FFL  !!' 5dyy    TTYbc c F"F"R#R####&&&++7 < <,<,<<      !"#$%&'()*+,-./012345768:9;<=>?@ABCDEFGIHJKLMNOPQRSTUVWXYZ[\]^`_acbdefhgijklmnopqrstuvwxyz|{}~IIN[[ ! ! WW''',,1,B,B,<<< E|GGG6H6H 11c---t[t[aabmimimllff""^^ff11l!l! " """/\6\6e8l8l8>>>EETTTPePe f fRu))g''4bKNN&&0  Am||    Xajjf f I"I"Y#Y####&&&++#7<<2<2<<  !"#$%&'()*+,-./012345768:9;<=>?@ABCDEFGIHJKLMNOPQRSTUVWXYZ[\]^`_acbdefhgijklmnopqrstuvwxyz|{}~=*urn:schemas-microsoft-com:office:smarttags PlaceType=*urn:schemas-microsoft-com:office:smarttags PlaceName9*urn:schemas-microsoft-com:office:smarttagsState8*urn:schemas-microsoft-com:office:smarttagsCity9*urn:schemas-microsoft-com:office:smarttagsplaceB*urn:schemas-microsoft-com:office:smarttagscountry-region>q*urn:schemas-microsoft-com:office:smarttags PersonName \8qqqqqqqqqq  X \ 3 6 !!!!,"0"A"L"n%v%**\0j033p440737z:}:.;1;;;<<G<H<CCE Ecc ddddh!hSiYippxppppqqww15CIagQUnr59ؤܤ:B37?E`j28=CagкֺrxouǽCI"} 8?;B@"J"<$F$//;;C;e;l;K>U>EEEEEEFFFG GG\GbGGGHHJJJJJJJJKKKKWWXXpe}eeeff+g8g)i1i{jjrrouuuvvh}k}cf,/FIƟ͟ޟipiqcjïɯſɿHLPTt fsrxTZW]ntbj%)-1ruin(2KQ pvmsZ`NU5 C ##$$5%=%&&((`)d)i)o)))))**#*)*g+k+p+v+22>>BBEEOFRFFF{HHOO PP[T^TUUYYZZ__gghhhh!i%ijjjjjjk&kxssitmtntttttttIuRuyvvvv{{||WZcm_bIMUd@F SZ̊Ҋ&,!Ӎٍ=Cِܓ7>isz}]d&-.1  !&,LPU[?ESW\b(/]dILknt2@!'17PYcjy|P ^   $Q]MW-7oy,6{*6% ( k"p"""E#P#I(N(--[-b-----....j/n///90=022|4444669999y<y<{<{<|<|<~<<<<<<<<BC 27+/##% %C,F,g7k7S>>ddCPOZċLPos`cS[˧+?Eor(/e$h$&&z88YYffggJyLyǙʙ nvfpR\??kkZu\uz**y<y<{<{<|<|<~<<<<<<<<<<<<33333333333333333333333333333333333333333333333333333Sa 5  %%))t--11>>nBBSH[HHHM0S\ɫ :qrrrs&sstluuvwwwLxxyJyy$zzzz%{{{{{T|u|||}}i~{~o,ցȂŃ=`ӄq5eK8EWɌCfj{.XܑWt̒iFnH8Ybߗ R;\/v%қ%CɜcjUu(FyҢ£_qҥƦ%l%;Ѫū99Z-t"ױ%8ѳ?rBTAd>+Lù2Wٺ Zs,|&,)UTq Hm-i`y/z{cx{[J\Ou5NNq| s!*Dx >?kOaqfxI,asFdI[% hzGdr6Q5|eL7w(El5j    \ n    8 C%R~0<ZlQpEl%Lg$\ Fe+ =   d!O"""[#o###Z$$w%%&&''(())*~*+g+++3,},,,S-- .A.j..>0P0101112522333444=555N6j6 7177778 9O9$:=::t;;;y<y<{<{<|<|<~<<<<<<<<<<<<<<<y<y<{<{<|<|<~<<<<<<<<<,i  V \.Kn>T ~gw'VU.Kn6`4R#@E'-lU6|8RGI@IqLnx4MHo3AV4N2`rꀠce pub~rYh^`CJOJQJaJo(hHh^`OJ QJ ^J o(hHohpp^p`OJ QJ o(hHh@ @ ^@ `OJQJo(hHh^`OJ QJ ^J o(hHoh^`OJ QJ o(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohPP^P`OJ QJ o(hHhh^h`o(hh^h`o(.0^`0o(..0^`0o(... 88^8`o( .... 88^8`o( ..... `^``o( ...... `^``o(....... ^`o(........hh^h`o(hh^h`o(.0^`0o(..0^`0o(... 88^8`o( .... 88^8`o( ..... `^``o( ...... `^``o(....... ^`o(........hh^h`o(hh^h`o(.0^`0o(..0^`0o(... 88^8`o( .... 88^8`o( ..... `^``o( ...... `^``o(....... ^`o(........hh^h`o(hh^h`o(.0^`0o(..0^`0o(... 88^8`o( .... 88^8`o( ..... `^``o( ...... `^``o(....... ^`o(........h^`OJQJo(hHh^`OJ QJ ^J o(hHohpp^p`OJ QJ o(hHh@ @ ^@ `OJQJo(hHh^`OJ QJ ^J o(hHoh^`OJ QJ o(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohPP^P`OJ QJ o(hHh ^`OJQJo( ^`hH. pLp^p`LhH. @ @ ^@ `hH. ^`hH. L^`LhH. ^`hH. ^`hH. PLP^P`LhH.h^`CJOJQJaJo(hHh^`OJ QJ ^J o(hHoh  ^ `OJ QJ o(hHh[ [ ^[ `OJQJo(hHh++^+`OJ QJ ^J o(hHoh^`OJ QJ o(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohkk^k`OJ QJ o(hHh ^`OJQJo(h ^`OJ QJ o(oh pp^p`OJ QJ o(h @ @ ^@ `OJQJo(h ^`OJ QJ o(oh ^`OJ QJ o(h ^`OJQJo(h ^`OJ QJ o(oh PP^P`OJ QJ o(h ^`OJQJo( ^`hH. pLp^p`LhH. @ @ ^@ `hH. ^`hH. L^`LhH. ^`hH. ^`hH. PLP^P`LhH.808^8`0o(() ^`hH. pLp^p`LhH. @ @ ^@ `hH. ^`hH. L^`LhH. ^`hH. ^`hH. PLP^P`LhH.h ^`OJQJo(h ^`OJ QJ o(oh pp^p`OJ QJ o(h @ @ ^@ `OJQJo(h ^`OJ QJ o(oh ^`OJ QJ o(h ^`OJQJo(h ^`OJ QJ o(oh PP^P`OJ QJ o(h^`OJQJo(hHh^`OJ QJ ^J o(hHohpp^p`OJ QJ o(hHh@ @ ^@ `OJQJo(hHh^`OJ QJ ^J o(hHoh^`OJ QJ o(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohPP^P`OJ QJ o(hH^`o(.^`.pLp^p`L.@ @ ^@ `.^`.L^`L.^`.^`.PLP^P`L.h^`OJQJo(hHh^`OJ QJ ^J o(hHohpp^p`OJ QJ o(hHh@ @ ^@ `OJQJo(hHh^`OJ QJ ^J o(hHoh^`OJ QJ o(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohPP^P`OJ QJ o(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohpp^p`OJ QJ o(hHh@ @ ^@ `OJQJo(hHh^`OJ QJ ^J o(hHoh^`OJ QJ o(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohPP^P`OJ QJ o(hHV \6UE'-2`>T 'IqL~rce pGI4MR#6|83AV         ] h/+6wCJR]$l;lGr9 gN]L7M@URryHHTnqqqqqqqqr rrrrrrrrrrrrrss&ssssssstttutvtxttttttuu1v2v4v6vvvvwwwwwwwxxxxy%y,yEyFyHyJyyyzz z"z$zzzz {!{#{%{{{{{{{{T|_|f|r|s|u||||||||}}}}}}}}}}}i~t~{~~~~~oz)*,TUWY؀ـۀ݀сҁԁցǂȂBCEpqsuŃ=HO[\^`Ƅ҄ӄBCEGˆ̆ΆІq}5cjbce~3468 EPWƌnjɌCNUabdf!ju|[̏͏Ϗя{.9@WXّڑܑ(W^oprt̒גޒi|CDFijln#*CDFHޕߕ8ELXY_`bߗ  Rabdijln89;WXZ\/QXqrtv  !#%͛ΛЛқ%/6BCƜǜɜޜߜ7cjUel؟ٟ۟ݟ(?Fy£ͣԣ¤ɤ_jqϥХҥƦ   !#%ȧϧlw~ !#%!:;ΪϪѪū 4579Ǭά679UVXZ-OVoprt"UVXZ ұӱձױ%18̳ͳϳѳ?OVqr޴ߴBMTALS_`bd*1=>ոָظ+8?GHJL¹ù/02RSUWٺ Ż޻߻Z_frs  '(*,߽L|ľžǾ&JKMO,7>WXZz{})4;TUTjq EFHhikm-DKdegi`w~y$%'\]_a"./  z{ !#^_ac./1\]_aFcjvw ':;=?{[gnJU\OT[tu  9:<>5:AMNNY`lmoqyz| pqs!mn'(*?@BDzUx 9:<>OP:;=? #$&(pkOZaq|fqx5<DEGIBC%,   alsCDF_`bdIT[ !#%  JKhszDEG_`bdrwjk !#%346LMOQ5BIQRTwxz|AH`ace'.GHJL07tuw#$&(ghjl5>EMNPefhj      = > @ B        \ g n        @ A C E    3 4 6 8 %>?AC $%RW^yz|~05<z{}ZelNOQklnp=>@BQEX_ghjl%8?GHJLgz$7>WXZ\  FQX`ace+ 6 = S T        d!|!!!!!!! ""-"."0"J"K"M"O""""""""#[#b#j#k#m#o########Z$e$l$$$$$w%%%%%%%&&&&&&&'''''''(((((')()*)G)H)J)L))))))))*%*,*9*:*<*>*`*w*~*++++ +"+$+g+++++++3,>,E,[,\,^,x,y,{,},,,,----S-c-j--->.?.A.e.f.h.j.....//////////>0I0P0y0z0111+1,1.10111122202123252223 3333333333344444455 55555'5+52595:5<5=555555556N6U6e6f6h6j66 77,7-7/717W77777777777788 9&9-9J9K9M9O9:$:+:<:=::::;;;;2;=;D;W;X;Z;o;p;r;t;;;;w<x<<@__,i __<@UnknownScott Woodruffmsic_clarklFH G: Times New Roman5Symbol3& : Arial;" HelveticaG  MS Mincho-3 fgWSimSunArial Unicode MS3TimesY New YorkTimes New Roman5& zaTahoma{GFOGMB+TimesNewRoman,BoldTimes New Roman?5 z Courier New;Wingdings#1h`Q{{!4::2qHX ?92dWorld Meteorological Organization Intergovernmental Oceanographic Commissionc_clarkc_clarkL           Oh+'0$0<L \h   hWorld Meteorological Organization Intergovernmental Oceanographic Commissionc_clarkNormalc_clark6Microsoft Office Word@&P @L(@rƒQ({՜.+,D՜.+,P hp  1UNESCO: eWorld Meteorological Organization Intergovernmental Oceanographic Commission Title  8@ _PID_HLINKSAmpDhttp://icoads.noaa.gov/etmc i5A3http://wo.jcommops.org/cgi-bin/WebObjects/JCOMMOPS K>http://www.icsu.org/index.php %%;0http://e2edm.meteo.ru/e2edm/index.php?section=1 w:8/http://wo.jcommops.org/cgi-bin/WebObjects/Argo 5http://www.ghrsst-pp.org/ E2http://www.godae.org/ l/Rhttp://www.oco.noaa.gov/index.jsp?show_page=page_status_reports.jsp&nav=observing n,Khttp://www.iode.org/index.php?option=com_content&task=view&id=51&Itemid=95 R)1http://ftp.wmo.int/pages/about/Resolution40.html s=&http://www.opendap.org/ ,9#http://www.odas.org.cn/ Q :http://www.wmo.ch/pages/prog/www/ois/pub47/pub47-home.htm Rhttp://gcmd.nasa.gov/ \ http://www.isotc211.org/ EGhttp://www.fgdc.gov/ o0http://dmac.ocean.us/index.jsp R.http://www.iso.org/iso/en/ISOOnline.frontpage |&http://dublincore.org/ h  http://marinemetadata.org/ eHhttp://www.iode.org/marinexml/files.php?action=viewfile&fid=4&fcat_id=3 0hhttp://ioc.unesco.org/oceanteacher/OceanTeacher2/01_GlobOcToday/06_OpOc/04_GOOS/Prospectus/contents.htm DQhttp://www.hdfgroup.org/ =~/http://www.cgd.ucar.edu/cms/eaton/cf-metadata/ Shttp://www.ifremer.fr/gosud/ .0http://www.oceansites.org/ w:/http://wo.jcommops.org/cgi-bin/WebObjects/Argo ^-http://www.unidata.ucar.edu/software/netcdf/ Z-http://physics.nist.gov/cuu/Units/index.html &q(http://www.wmo.ch/web/www/WMOCodes.html fe'http://www.wmo.ch/web/www/TEM/gts.html ) @http://www.wmo.int/pages/prog/gcos/Publications/gcos-92_GIP.pdf D*http://www.ngdc.noaa.gov/wdc/wdcmain.html vc3http://www.wmo.ch/pages/prog/www/WIS-Web/home.html RUhttp://www.iode.org/ NThttp://www.ceos.org/ OFhttp://www.wmo.ch/pages/prog/amp/mmop/documents/JCOMM-Strategy-v1.pdf qchttp://www.jcomm.info/ 3 _Toc1755493483 _Toc1755493473 _Toc1755493463 _Toc1755493453 _Toc1755493443 _Toc1755493433 _Toc1755493423 _Toc1755493413 _Toc1755493403 _Toc1755493393 _Toc1755493383 _Toc1755493373 _Toc1755493363 _Toc1755493353z _Toc1755493343t _Toc1755493333n _Toc1755493323h _Toc1755493313b _Toc1755493303\ _Toc1755493293V _Toc1755493283P _Toc1755493273J _Toc1755493263D _Toc1755493253> _Toc17554932438 _Toc17554932332 _Toc1755493223, _Toc1755493213& _Toc1755493203  _Toc1755493193 _Toc1755493183 _Toc1755493173 _Toc1755493163 _Toc175549315j  http://icoads.noaa.gov/climar3/ \P!http://marinemetadata.org/meta-t   !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Root Entry FQ(Data y1Table` WordDocumentBSummaryInformation(DocumentSummaryInformation8!CompObjq  FMicrosoft Office Word Document MSWordDocWord.Document.89q