ࡱ> 3     ` @hbjbjss GWVp>|>|>|(f| 4Δv v v hޭ j AΔ  %b ( L  . 4 \C1 !  $ h ~} - - ~} ~} ||  @{ $L L L ~} |b  L ~} L L  8  ~ /nv v 4 N <    8 @S &b L l Nu 0@S @S @S ܬ p@S @S @S ~} ~} ~} ~} ΔΔΔ+āΔΔΔ+ΔΔ|||||   Model Requirements for the Management of Electronic Records Update and Extension, 2008 MoReq2 Specification This specification has been prepared for the European Commission by Serco Consulting with funding from the IDABC programme   Model Requirements for the Management of Electronic Records Update and Extension, 2008 MoReq2 Specification This specification is available in electronic form at the following urls:  HYPERLINK "http://dlm-network.org/moreq2" http://dlm-network.org/moreq2  HYPERLINK "http://ec.europa.eu/transparency/archival_policy" http://ec.europa.eu/transparency/archival_policy and other websites. Translations into selected languages are expected to be available at these sites. It is also available in paper form from the Office for Official Publications of the European Communities as INSAR Supplement VIII. CECA-CEE-CEEA, Bruxelles- Luxembourg, 2008 Reproduction autorise, sauf des fins commerciales, moyennant mention de la source. Reproduction is authorised, except for commercial purposes, provided the source is acknowledged. Legal notice: The copyright of this publication is owned by the European Communities. The European Commission does not guarantee the accuracy of the information included in this report, nor does it accept any responsibility for any use made thereof. Neither the European Communities and/or their institutions nor any person acting on their behalf shall be held responsible for any loss or damage resulting from the use of this publication. Contents  TOC \h \z \t "Title,1,MR1,1,MR2,2,MR Annex Heading 1,1,MR Annex Heading 2,2"  HYPERLINK \l "_Toc201478390" Preface: MoReq2  PAGEREF _Toc201478390 \h 1  HYPERLINK \l "_Toc201478391" 1. Introduction  PAGEREF _Toc201478391 \h 2  HYPERLINK \l "_Toc201478392" 1.1 Background  PAGEREF _Toc201478392 \h 2  HYPERLINK \l "_Toc201478393" 1.2 Relationship between MoReq and MoReq2  PAGEREF _Toc201478393 \h 2  HYPERLINK \l "_Toc201478394" 1.3 Purpose and Scope of this Specification  PAGEREF _Toc201478394 \h 3  HYPERLINK \l "_Toc201478395" 1.4 What is an ERMS?  PAGEREF _Toc201478395 \h 3  HYPERLINK \l "_Toc201478396" 1.5 For what can this Specification be used?  PAGEREF _Toc201478396 \h 4  HYPERLINK \l "_Toc201478397" 1.6 Intellectual Property Rights  PAGEREF _Toc201478397 \h 5  HYPERLINK \l "_Toc201478398" 1.7 Emphasis and Limitations of this Specification  PAGEREF _Toc201478398 \h 5  HYPERLINK \l "_Toc201478399" 1.8 Considerations for Individual Member States  PAGEREF _Toc201478399 \h 6  HYPERLINK \l "_Toc201478400" 1.9 Customising this Specification  PAGEREF _Toc201478400 \h 6  HYPERLINK \l "_Toc201478401" 1.10 Organisation of this Specification  PAGEREF _Toc201478401 \h 7  HYPERLINK \l "_Toc201478402" 1.11 Compliance Testing  PAGEREF _Toc201478402 \h 8  HYPERLINK \l "_Toc201478403" 1.12 Mandatory and Desirable Requirements  PAGEREF _Toc201478403 \h 9  HYPERLINK \l "_Toc201478404" 1.13 Comments on this Specification  PAGEREF _Toc201478404 \h 9  HYPERLINK \l "_Toc201478405" 2. Overview of ERMS Requirements  PAGEREF _Toc201478405 \h 10  HYPERLINK \l "_Toc201478406" 2.1 Key Terminology  PAGEREF _Toc201478406 \h 10  HYPERLINK \l "_Toc201478407" 2.2 Key Concepts  PAGEREF _Toc201478407 \h 13  HYPERLINK \l "_Toc201478408" 2.3 Entity-Relationship Model  PAGEREF _Toc201478408 \h 19  HYPERLINK \l "_Toc201478409" 3. Classification Scheme and File Organisation  PAGEREF _Toc201478409 \h 23  HYPERLINK \l "_Toc201478410" 3.1 Configuring the Classification Scheme  PAGEREF _Toc201478410 \h 24  HYPERLINK \l "_Toc201478411" 3.2 Classes and Files  PAGEREF _Toc201478411 \h 28  HYPERLINK \l "_Toc201478412" 3.3 Volumes and Sub-Files  PAGEREF _Toc201478412 \h 31  HYPERLINK \l "_Toc201478413" 3.4 Maintaining the Classification Scheme  PAGEREF _Toc201478413 \h 34  HYPERLINK \l "_Toc201478414" 4. Controls and Security  PAGEREF _Toc201478414 \h 40  HYPERLINK \l "_Toc201478415" 4.1 Access  PAGEREF _Toc201478415 \h 40  HYPERLINK \l "_Toc201478416" 4.2 Audit Trails  PAGEREF _Toc201478416 \h 45  HYPERLINK \l "_Toc201478417" 4.3 Backup and Recovery  PAGEREF _Toc201478417 \h 48  HYPERLINK \l "_Toc201478418" 4.4 Vital Records  PAGEREF _Toc201478418 \h 49  HYPERLINK \l "_Toc201478419" 5. Retention and Disposition  PAGEREF _Toc201478419 \h 52  HYPERLINK \l "_Toc201478420" 5.1 Retention and Disposition Schedules  PAGEREF _Toc201478420 \h 52  HYPERLINK \l "_Toc201478421" 5.2 Review of Disposition Actions  PAGEREF _Toc201478421 \h 60  HYPERLINK \l "_Toc201478422" 5.3 Transfer, Export and Destruction  PAGEREF _Toc201478422 \h 61  HYPERLINK \l "_Toc201478423" 6. Capturing and Declaring Records  PAGEREF _Toc201478423 \h 67  HYPERLINK \l "_Toc201478424" 6.1 Capture  PAGEREF _Toc201478424 \h 67  HYPERLINK \l "_Toc201478425" 6.2 Bulk Importing  PAGEREF _Toc201478425 \h 77  HYPERLINK \l "_Toc201478426" 6.3 e-Mail Management  PAGEREF _Toc201478426 \h 79  HYPERLINK \l "_Toc201478427" 6.4 Record Types  PAGEREF _Toc201478427 \h 84  HYPERLINK \l "_Toc201478428" 6.5 Scanning and Imaging  PAGEREF _Toc201478428 \h 85  HYPERLINK \l "_Toc201478429" 7. Referencing  PAGEREF _Toc201478429 \h 90  HYPERLINK \l "_Toc201478430" 7.1 Classification Codes  PAGEREF _Toc201478430 \h 92  HYPERLINK \l "_Toc201478431" 7.2 System Identifiers  PAGEREF _Toc201478431 \h 95  HYPERLINK \l "_Toc201478432" 8. Searching, Retrieval and Presentation  PAGEREF _Toc201478432 \h 97  HYPERLINK \l "_Toc201478433" 8.1 Search and Retrieval  PAGEREF _Toc201478433 \h 97  HYPERLINK \l "_Toc201478434" 8.2 Presentation: Displaying Records  PAGEREF _Toc201478434 \h 103  HYPERLINK \l "_Toc201478435" 8.3 Presentation: Printing  PAGEREF _Toc201478435 \h 104  HYPERLINK \l "_Toc201478436" 8.4 Presentation: Other  PAGEREF _Toc201478436 \h 106  HYPERLINK \l "_Toc201478437" 9. Administrative Functions  PAGEREF _Toc201478437 \h 107  HYPERLINK \l "_Toc201478438" 9.1 General Administration  PAGEREF _Toc201478438 \h 107  HYPERLINK \l "_Toc201478439" 9.2 Reporting  PAGEREF _Toc201478439 \h 108  HYPERLINK \l "_Toc201478440" 9.3 Changing, Deleting and Redacting Records  PAGEREF _Toc201478440 \h 113  HYPERLINK \l "_Toc201478441" 10. Optional Modules  PAGEREF _Toc201478441 \h 118  HYPERLINK \l "_Toc201478442" 10.1 Management of Physical (Non-electronic) Files and Records  PAGEREF _Toc201478442 \h 119  HYPERLINK \l "_Toc201478443" 10.2 Disposition of Physical Records  PAGEREF _Toc201478443 \h 123  HYPERLINK \l "_Toc201478444" 10.3 Document Management and Collaborative Working  PAGEREF _Toc201478444 \h 123  HYPERLINK \l "_Toc201478445" 10.4 Workflow  PAGEREF _Toc201478445 \h 129  HYPERLINK \l "_Toc201478446" 10.5 Casework  PAGEREF _Toc201478446 \h 133  HYPERLINK \l "_Toc201478447" 10.6 Integration with Content Management Systems  PAGEREF _Toc201478447 \h 138  HYPERLINK \l "_Toc201478448" 10.7 Electronic Signatures  PAGEREF _Toc201478448 \h 142  HYPERLINK \l "_Toc201478449" 10.8 Encryption  PAGEREF _Toc201478449 \h 145  HYPERLINK \l "_Toc201478450" 10.9 Digital Rights Management  PAGEREF _Toc201478450 \h 146  HYPERLINK \l "_Toc201478451" 10.10 Distributed Systems  PAGEREF _Toc201478451 \h 148  HYPERLINK \l "_Toc201478452" 10.11 Offline and Remote Working  PAGEREF _Toc201478452 \h 151  HYPERLINK \l "_Toc201478453" 10.12 Fax Integration  PAGEREF _Toc201478453 \h 153  HYPERLINK \l "_Toc201478454" 10.13 Security Categories  PAGEREF _Toc201478454 \h 155  HYPERLINK \l "_Toc201478455" 11. Non-Functional Requirements  PAGEREF _Toc201478455 \h 162  HYPERLINK \l "_Toc201478456" 11.1 Ease of Use  PAGEREF _Toc201478456 \h 163  HYPERLINK \l "_Toc201478457" 11.2 Performance and Scalability  PAGEREF _Toc201478457 \h 167  HYPERLINK \l "_Toc201478458" 11.3 System Availability  PAGEREF _Toc201478458 \h 170  HYPERLINK \l "_Toc201478459" 11.4 Technical Standards  PAGEREF _Toc201478459 \h 171  HYPERLINK \l "_Toc201478460" 11.5 Legislative and Regulatory Requirements  PAGEREF _Toc201478460 \h 172  HYPERLINK \l "_Toc201478461" 11.6 Outsourcing and Third Party Management of Data  PAGEREF _Toc201478461 \h 173  HYPERLINK \l "_Toc201478462" 11.7 Long Term Preservation and Technology Obsolescence  PAGEREF _Toc201478462 \h 175  HYPERLINK \l "_Toc201478463" 11.8 Business Processes  PAGEREF _Toc201478463 \h 179  HYPERLINK \l "_Toc201478464" 12. Metadata Requirements  PAGEREF _Toc201478464 \h 183  HYPERLINK \l "_Toc201478465" 12.1 Principles  PAGEREF _Toc201478465 \h 183  HYPERLINK \l "_Toc201478466" 12.2 General Metadata Requirements  PAGEREF _Toc201478466 \h 183  HYPERLINK \l "_Toc201478467" 13. Reference Model  PAGEREF _Toc201478467 \h 188  HYPERLINK \l "_Toc201478468" 13.1 Glossary  PAGEREF _Toc201478468 \h 188  HYPERLINK \l "_Toc201478469" 13.2 Entity-Relationship Model  PAGEREF _Toc201478469 \h 200  HYPERLINK \l "_Toc201478470" 13.3 Entity Relationship Narrative  PAGEREF _Toc201478470 \h 203  HYPERLINK \l "_Toc201478471" 13.4 Access Control Model  PAGEREF _Toc201478471 \h 205  HYPERLINK \l "_Toc201478472" Appendix 1 Reference Publications  PAGEREF _Toc201478472 \h 208  HYPERLINK \l "_Toc201478473" Appendix 2 Development of this Specification  PAGEREF _Toc201478473 \h 209  HYPERLINK \l "_Toc201478474" Appendix 3 Use of this Specification in Electronic Form  PAGEREF _Toc201478474 \h 212  HYPERLINK \l "_Toc201478475" Appendix 4 Acknowledgements  PAGEREF _Toc201478475 \h 214  HYPERLINK \l "_Toc201478476" Appendix 5 Correspondence to Other Models  PAGEREF _Toc201478476 \h 218  HYPERLINK \l "_Toc201478477" Appendix 6 Date Processing  PAGEREF _Toc201478477 \h 222  HYPERLINK \l "_Toc201478478" Appendix 7 Standards and Other Guidelines  PAGEREF _Toc201478478 \h 223  HYPERLINK \l "_Toc201478479" 7.1 Standards  PAGEREF _Toc201478479 \h 223  HYPERLINK \l "_Toc201478480" 7.2 Other Guidance  PAGEREF _Toc201478480 \h 224  HYPERLINK \l "_Toc201478481" 7.3 Accessibility Guidelines and Resources  PAGEREF _Toc201478481 \h 224  HYPERLINK \l "_Toc201478482" 7.4 Digital Preservation Guidelines  PAGEREF _Toc201478482 \h 225  HYPERLINK \l "_Toc201478483" 7.5 Graphical Model of Relationship of MoReq2 with Other Guidance  PAGEREF _Toc201478483 \h 225  HYPERLINK \l "_Toc201478484" Appendix 8 Changes from the Original MoReq  PAGEREF _Toc201478484 \h 231  HYPERLINK \l "_Toc201478485" 8.1 Changes that are not Backwards-Compatible  PAGEREF _Toc201478485 \h 231  HYPERLINK \l "_Toc201478486" 8.2 Relationship between Sections  PAGEREF _Toc201478486 \h 231 APPENDIX 9 METADATA MODEL published separately Preface: MoReq2 Update and extension of the Model Requirements for the management of electronic records Since it was first published in 2001, the original MoReq Model Requirements for the management of electronic records has been used widely throughout Europe and beyond. Throughout the European Union, prospective users of electronic records management have recognised the value of using a model specification such as MoReq as the basis for procuring Electronic Records Management Systems and software suppliers have responded by using MoReq to guide their development process. MoReq is now regarded as an unqualified success. It has been cited many times on many continents and it has a central role on the electronic records management scene. However, information technology has changed since 2001. There has been growth and evolutionary change in many technology areas that affect the creation, capture and management of electronic records. This new version of MoReq, called MoReq2, addresses the impacts of that technological change. It also takes account of new standards and best practice that have been developed over the last several years. Accordingly, it is written as an evolutionary update of the original MoReq. MoReq2 for the first time also allows for a software testing regime to be implemented. It is written specifically to support the execution of independent compliance testing and a suite of compliance tests has been developed and published in parallel with the model requirements themselves. The need for rigorously-worded, testable, requirements has led to many changes of wording and expression in MoReq2. Finally, the years of experience in using and applying MoReq has pointed out the need for national variations, to take into account different national languages, legislation, regulations, and record keeping traditions. For this reason, MoReq2 introduces for the first time a moderated mechanism called chapter zero to allow member states to add their unique national requirements. MoReq2 was prepared for the European Commission by Serco Consulting with financing from the European Union's IDABC programme. The development process was overseen by the European Commission working closely with the DLM Forum and drafts were reviewed by DLM Forum experts at key stages in the development. These reviews were in addition to input and review by dozens of users, consultants, suppliers, academics and professional bodies from around the globe, giving MoReq2 an unprecedented level of authority. As such MoReq2 will be of great value to all those involved in the management of electronic records in Europe and around the world. Introduction Background The need for a comprehensive specification of requirements for electronic records management was first articulated by the DLM-Forum in 1996 as one of its ten action points. Subsequently, the European Commissions IDA (Interchange of Data between Administrations) programme commissioned the development of a model specification for electronic records management systems (ERMSs). The result, MoReq, the Model Requirements for the management of electronic records, was published in 2001. MoReq was widely used in throughout the European Union and beyond. However, there was no maintenance regime for MoReq; and there was no scheme to test software compliance against the MoReq specification. Demand for both updates to MoReq and a compliance testing scheme grew. The DLM Forum entered into discussions with the European Commission. This culminated in the Commissions Secretariat-General (Directorate B e-Domec and archives) launching an open competition for the development of this document, MoReq2, in 2006. Development was carried out during 2007 by a small team of specialist consultants from Serco Consulting (formerly Cornwell Management Consultants plc), supported by an Editorial Board of experts drawn from several countries, and numerous volunteer reviewers from both the private and public sectors. Appendix 2 contains further detail on the methodology used, and appendix 4 acknowledges the contributions of the review panel members who kindly volunteered their time, intellect, and experience. Relationship between MoReq and MoReq2 MoReq2 is intended to replace MoReq. The specification for MoReq2 is contained in the Scoping Report for MoReq2. It describes the aims of MoReq2 as follows: The overall aims for the MoReq2 development are to develop extended functional requirements within a European context, and to support a compliance scheme by: Strengthening from MoReq what have in the interim become key areas and covering important new areas of requirements with clarity; Ensuring that the functional requirements are testable and developing test materials to enable products to be tested for compliance with the requirements; Making the requirements modular to assist application in the various environments in which they will be used. To provide compatibility, MoReq2 is to be an evolutionary update to the original MoReq, not a radically different product. The concept of evolutionary upgrade is key. MoReq2 is almost entirely compatible with MoReq (minor incompatibilities are clearly indicated); it is based on the same concepts, and as a document it uses a similar structure. Purpose and Scope of this Specification This specification is the second version of the Model Requirements for the management of electronic records. (MoReq2). It focuses mainly on the functional requirements for the management of electronic records by an Electronic Records Management System (ERMS). This specification is written to be equally applicable to public and private sector organisations which wish to introduce an ERMS, or which wish to assess the ERMS capability they currently have in place. While the specification focuses on functional requirements, it recognises that non-functional attributes are central to the success of an ERMS, as with any information system. However, these non-functional attributes vary enormously between environments. Accordingly, they are identified but described only in outline. Other closely-related requirements, such as document management and the electronic management of physical records (such as paper files and microfilm) are also addressed, but in less detail. Related issues such as digitisation and other means of creating electronic records are outside the scope of this specification. Similarly, it makes no attempt to cover the practical implementation of an ERMS. This specification is written with the assumption that ERMS users include not only administrators, records managers or archivists, but also general office and operational staff who use ERMSs as part of their everyday work while creating, receiving and retrieving records. As this specification contains model requirements, it is designed to be entirely generic. It does not consider any platform-specific or sector-specific issues. Because it is modular, user communities can add to it additional functionality specific to their own business requirements (see section 1.6 and appendix 3 for guidance on using and customising this specification). What is an ERMS? An ERMS is primarily an application for managing electronic records, though it may also be used to manage physical records. The emphasis of this specification is firmly on the management of electronic records. The management of electronic records is complex, requiring a large range of functionality, meeting business needs, to be implemented well. Typically, a system to meet these needs an ERMS requires specialised software, though increasingly records management functionality is being built into operating system software and other applications. Specialist software may consist of a single package, a number of integrated packages, custom-designed software or some combination; and in all cases, there will be a need for complementary manual procedures and management policies. The nature of an ERMS will vary from organisation to organisation. This specification makes no assumption about the nature of individual ERMS solutions. Users of this specification will need to determine how the functionality of an ERMS can be implemented to meet their requirements. ERMSs are expected to be used over considerable periods and increasingly to interact with other applications. There are therefore many ways in which an implementer may want to connect an ERMS with other software applications. It may be necessary to create interfaces for the capture of individual records from other business applications (see section 6.1) and for the applications to access records in the ERMS (see section 4.1). This applies particularly with business applications such as CRM (Customer Relationship Management) and line of business applications. Chapter 10 includes specific coverage of interfaces with CMSs (Content Management Systems), Workflow and Casework systems and fax integration. Chapter 6 covers interfaces with e-mail applications in section 6.3 (e-mail management) and scanning and imaging in section 6.5. An interface for validation of metadata is covered in section 6.1 (Capture) and with report generators in 8.3 (Printing). MoReq2 is written primarily to describe application software that is designed expressly to manage records. However, it may also be used as a statement of outcomes together constituting electronic records management. Thus the statements in MoReq2 saying The ERMS must or should may also be read as shorthand for The using organisations application system and/or the supplier platform must or should Readers of MoReq2 need to decide which requirements are necessary in their environment. The full set of MoReq2 requirements may be appropriate for integrated application systems. However, a subset may be more appropriate in the situation, for example, where records management features are needed as part of a case management or line of business application. The optional modules 10.4 Workflow and 10.5 Casework, specifically apply to line of business applications. However much of the functionality described in the requirements throughout MoReq2 can also be applicable and should be considered when implementing these business systems. For what can this Specification be used? The MoReq2 specification is intended to be used: by potential ERMS users: as a basis for preparing an invitation to tender; by ERMS users: as a basis for auditing or checking an existing ERMS; by training organisations: as a reference document for preparing records management training, and as course material; by academic institutions: as a teaching resource; by ERMS suppliers and developers: to guide product development by highlighting functionality required; by record management service providers: to guide the nature of the services to be provided; by potential users of outsourced record management services: as an aid in specifying the services to be procured. In addition, when used with the testing framework documentation developed in parallel with MoReq2, it is intended to be used: by ERMS suppliers and developers: to test ERMS solutions for MoReq2 compliance; by ERMS users: to test ERMS implementations for MoReq2 compliance. The specification is written with an emphasis on usability. Throughout, the intention has been to develop a specification which is useful in practice. Intellectual Property Rights All intellectual property rights in MoReq2, including use of the name MoReq2, lie with the European Commission. Accordingly, permission must be given before any translation of MoReq2 or chapter zero to MoReq2 is published see the formal notice on the title page. To apply for permission, refer to the DLM Forum website at  HYPERLINK "http://www.DLM-Network.org" http://www.DLM-Network.org. Emphasis and Limitations of this Specification The MoReq2 specification is designed explicitly with pragmatism and usability in mind. It is primarily intended to serve as a practical tool in helping organisations meet their business needs for the management of both computer-based and paper-based records. While its development has taken traditional archival science and records management disciplines into account, these have been interpreted in a manner appropriate to electronic environments. Thus, MoReq was developed with the needs of managers of both electronic and physical records in mind. The requirements in MoReq2 should, if implemented, result in a system which will manage electronic records with the desired levels of confidence and integrity, by combining both the advantages of electronic ways of working with classical records management theory. Examples of this pragmatic approach include the incorporation of requirements for document management, workflow, metadata and other related technologies. Although MoReq2 covers a wide range of types of records, it is important to understand that ERMS solutions address mainly records that are often referred to as unstructured records. . In simple terms, unstructured records are those that contain information presented in a form primarily intended to be used by human users. Examples of unstructured records are letters, memoranda, e-mail messages, pictures, photocopies, scanned images, audio recordings and video recordings. Structured records by contrast contain information in a form intended to be used primarily by computer applications (examples include accounting system records, manufacturing scheduling system records, and air traffic control system records). While an ERMS can, in principle be used to store such structured records, it rarely is. In most situations, structured data is stored under the management of a data processing application (in the examples above these might be a general ledger system, a manufacturing scheduling system, and an air traffic control system). ERMS solutions are used almost universally to store and manage unstructured records. The instances in which an ERMS is used for structured records occur often in case management environments see section 10.5. MoReq2 does not cover the practical aspects of the management of records. Intentionally, the specification addresses only the capabilities required for the management of electronic records by software. The specification avoids discussion of records management philosophy, archival theory, decision taking, management control etc.; these issues are well covered in other literature, some of which is listed in appendix 1. As a particular example, the specification mentions in several places that certain functions must be limited to administrative roles. This is not to say that administrative roles have to take policy decisions, merely that they must be the only users empowered by the organisation to execute them through the ERMS. It is important to note that records management policy must be integrated with the organisations business and technical requirements and that an administrative role can only implement, from a records management and system perspective, decisions taken by more senior management. Finally, this specification is intentionally user-centric; it uses, as far as possible, the type of terminology commonly used by those working with electronic records. For example, the specification describes electronic files as containing records, for ease of understanding, even though electronic files strictly do not contain anything. See section 2.2 for further details. Considerations for Individual Member States As explained in the section on scope, section 1.3, this specification attempts to cover a wide range of requirements for different countries, in different industries and with different types of records. The wide scope is intentional; but it leads to a significant limitation, namely that this single specification cannot represent a requirement which precisely maps onto existing requirements without modification. Different countries have their differing traditions, views and regulatory demands for managing records. In some cases these will have to be taken into account when applying this Model Requirements Specification, especially when using it to specify a new system. For this reason, MoReq2 allows for individual European Union countries to add a national chapter, or chapter zero, that sets out national requirements such as: Translations of key terminology and key concepts; National legislative and regulatory requirements; National standards and guidance on accessibility; Potentially, other national requirements; National resources for further information. Customising this Specification The requirements in this specification are intended to serve only as a model. They are not prescriptive for all possible ERMS implementations; some requirements will not apply in some environments. Different business sectors, different sizes of implementation, different organisation types and other factors will also introduce additional specific requirements. As a result, this specification must be customised before use for procurement purposes. The customisation for procurement should: add or remove requirements as specifically required by the organisation; adjust requirements that can be made more specific. For example: requirements that specify one of several possible outcomes can be changed to specify a single required outcome; requirements for volumes and performance. include details specific to the organisation, such as the software environment; indicate clearly which requirements are: unchanged from MoReq2, new, deleted, adjusted. This specification has been prepared so that it can be used in paper or electronic form. It has been prepared using Microsoft Word 2003, and is published in the following formats: Microsoft Word 97-2003 (Version 11); Microsoft Word 2007 (Version 12); Adobe PDF (Version 1.4). Use in electronic form has a number of benefits; details are given in appendix 3. Organisation of this Specification The specification is organised into chapters which are divided into sections. The next chapter (chapter 2) provides an overview of some of the key requirements, starting with terminology which is central to this specification. Chapters 3 to 9 contain the core ERMS functional requirements in detail. Each chapter contains a logical grouping of functional requirements. However, given the nature of the subject matter there is inevitably some overlap between chapters. Chapter 10 is divided into several sections, each of which represents requirements for an optional module of an ERMS. Some of these sections (e.g. the section on distributed systems) will be essential for some organisations, but unnecessary for others. Chapter 11 contains non-functional requirements. Chapter 12 identifies requirements for managing metadata; definitions of the metadata elements needed to support MoReq2 are in appendix 9. Chapter 13 contains a formal reference model of ERMS as understood in this specification. This model can be used to understand key aspects of the specification, such as formal definitions of terms (e.g. class, sub-file, volume) and the relationships which exist between them (for instance what can be stored in an electronic file?). The appendices contain details of reference documents, administrative and other information. Appendix 9 contains the MoReq2 metadata model. It is published separately from the rest of MoReq2 to ease cross referencing and because of its length. In response to demand from many sources, testing materials have been developed to complement these requirements. The testing materials are published alongside the electronic copies of the requirements. The structure of MoReq2 is designed to support testing of compliance with the requirements, e.g. each section of chapter 10 represents one optional test module. For more detail on MoReq2 testing see  HYPERLINK "http://www.DLM-Network.org" http://www.DLM-Network.org. . The requirements are presented in the form of tables, with one requirement per table row. This is illustrated in figure 1.1.  Figure 1.1 Each requirement bears a number, and each is expressed in natural language. Compliance Testing Testability Each requirement is followed by an attribute labelled Test. This indicates whether it will be possible to test compliance with the requirement. Possible values of this testability attribute are described below, with examples: Y The requirement can be tested formally. An example is The ERMS must allow at least three hierarchical levels in the classification scheme. This can be tested by attempting to set up a hierarchy with three levels. N The requirement cannot be tested formally. An example is The ERMS must support the organisations business classification scheme. There is no way to test this in the general case. P The requirement can be tested but the coverage of the test is partial, and/or it is possible that lack of compliance can be discovered. An example is the ERMS should not limit the number of levels in the hierarchy. There is no way, formally, to test for the absence of a limit. However, the requirement is considered testable with partial coverage, for example by testing for a large number of levels; and during the testing it is possible that a limitation on the number of levels might be noticed, indicating that the ERMS does not comply with the requirement. Systems beyond the ERMS This specification is accompanied by the MoReq2 Testing Framework. The framework provides documentation that allows the compliance of an ERMS against MoReq2 to be tested. Several MoReq2 requirements rely on hardware and software that is beyond the boundaries of the ERMS. For example, MoReq2 includes: requirements about e-mail integration that rely on features of e-mail software; scalability and integrity requirements that rely on features of database management software; scanning requirements that rely on scanning hardware. Clearly it is not possible to test any ERMS with all possible hardware and software that might be used. Therefore, and as a matter of definition, such requirements will be tested with a combination of software and hardware specified by the ERMS supplier. The resulting compliance test certificate will specify the software and hardware that has been used for the test; compliance will extend to that environment only. Potential users of the ERMS wishing to know the compliance with any other software and/or hardware will need to assess it on a case by case basis. Mandatory and Desirable Requirements MoReq2 contains both mandatory and desirable requirements. This level of mandation is indicated as follows: the word must indicates that a requirement is mandatory; the word should indicates that a requirement is desirable. In all cases, the level of mandation is dependent on its context. So, for example, a mandatory requirement in an optional module is mandatory only in the context of that optional module. In some cases, a requirement is mandatory only if a desirable requirement is met. This is always clear from the context; for example the following:  REF BK2696 \n  3.1.17: The ERMS should support the export of all or part of a classification scheme.  REF BK2697 \n  3.1.18: Where the ERMS supports the export of all or part of a classification scheme (as in  REF BK2696 \n  3.1.17) this must include associated metadata [& ] means that the functionality required by  REF BK2697 \n  3.1.18 is mandatory if, and only if, the desirable functionality required by  REF BK2696 \n  3.1.17 is provided. Comments on this Specification Information on how to submit comments and observations can be found on the DLM Forum website:  HYPERLINK "http://www.DLM-Network.org" http://www.DLM-Network.org. Overview of ERMS Requirements This chapter starts by defining some key terms (section 2.1). This is followed by a narrative description of some key concepts (section 2.2), and an entity-relationship diagram of the model on which this specification is based (section 2.3). Key Terminology MoReq2 requires certain terms to have precise meanings. Wherever possible, the meanings align with common usage, or usage generally agreed within the records management community. However, in some cases the usage is specific to MoReq2. All the terms are defined in the glossary (section 13.1). Key definitions that is, the definitions that are crucial for an understanding of MoReq2 from the glossary are reproduced here for ease of reference. The definitions reproduced here are identical to those in the full glossary. In the definitions below, terms in italics are defined in the glossary, section 13.1. capture (verb) (1) The act of recording or saving a particular instantiation of a digital object (source: InterPARES 2 Project Terminology Database). (2) Saving information in a computer system. Note: in the context of MoReq2, capturing records is used to mean all of the processes involved in getting a record into an ERMS, namely registration, classification, addition of metadata, and freezing the contents of the source document. The term is used more generally to mean inputting to the ERMS and storing other information such as metadata values. case file A file relating to one or more transactions performed totally or partly in a structured or partly-structured way, as a result of a concrete process or activity. Note: there is no universally-accepted definition of these terms, nor of the distinction between case files and the other kinds of files often managed by an ERMS. This definition is therefore developed for, and intended to facilitate the understanding of, MoReq2; its applicability in other situations is not guaranteed. Note: the records in a case file may be structured or unstructured. The key distinguishing characteristic of case files is that they result from processes which are at least partly structured and repeatable. Examples include files about: applications for permits; enquiries about a routine service; investigation of an incident; regulatory monitoring. Note: typically, other characteristics of case files are that they often: feature a predictable structure for their content; are numerous; are structured or partly structured; are used and managed within a known and predetermined process; need to be retained for specific periods, as a result of legislation or regulation; can be opened and closed by practitioners, end-users or data processing systems without the need for management approval. class (noun) (in MoReq2 only) The portion of a hierarchy represented by a line running from any point in the classification scheme hierarchy to all the files below it. Note: this can correspond, in classical terminology, to a primary class, group or series (or sub-class, sub-group, sub-series etc.) at any level in the classification scheme. Note: in MoReq2 class is also used to mean all the records allocated to a class. classification In records management, the systematic identification and arrangement of business activities and/or records into categories according to logically structured conventions, methods, and procedural rules represented in a classification system. Source: ISO 15489 (see appendix 7). classification scheme (In MoReq2) A hierarchic arrangement of classes, files, sub-files, volumes and records. component A distinct bit stream that, alone or with other bit streams, makes up a record or document. Note: this term is not in general use. Note: the phrase distinct bit stream is used to describe what is usually called a file in information technology; the word file is avoided here to prevent confusion with the records management meaning of file. The key concept is that a component is an integral part of the content of a record, despite the fact that it can be handled and managed separately. Note: examples of components include: An HTML document and JPEG images that make up a web page; A word processing document and a spreadsheet, where the record consists of the word processing document that contains an embedded link (a hyperlink) to the spreadsheet. Note: components have to be distinct, that is separate from each other. If a word processed document contains an embedded spreadsheet (as opposed to an embedded link to a spreadsheet) then the spreadsheet is not considered to be a component; in this case, the word processed document complete with its embedded spreadsheet is a record made up of one component. Note: an e-mail message with attachments may be one component, as several components, or as several records, depending on the format in which it is stored. If the message is stored in a format that includes the body and all its attachments, then there is only one component. If the attachments are stored separately from, and linked internally to, the body of the e-mail message, then each attachment and the body of the message is a component. If the attachments are stored separately from the body of the e-mail message but they are not linked internally, then each attachment and the body of the message is a separate record; good practice suggests that these records should be linked to each other manually. document (noun) Recorded information or object which can be treated as a unit. Source: ISO 15489 (see appendix 7). Note: a document may be on paper, microform, magnetic or any other electronic medium. It may include any combination of text, data, graphics, sound, moving pictures or any other forms of information. A single document may consist of one or several components. Note: documents differ from records in several important respects. MoReq2 uses the term document to mean information that has not been captured as a record, i.e. classified, registered and locked against change. The word recorded in the definition does not imply the characteristics of a record. However, note that some documents become records. electronic record A record which is in electronic form. Note: it can be in electronic form as a result of having been created by application software or as a result of digitisation, e.g. by scanning. ERMS Electronic Records Management System. Note: ERMSs differ from EDMSs in several important respects. See section 10.3 for more details. file (noun) An organised unit of records grouped together because they relate to the same subject, activity or transaction. Source: shortened and adapted from ISAD(G) (see appendix 7). Note: this is the Records Management usage of the term file. It differs from the IT usage, for which MoReq2 uses the term component. metadata (In the context of records management) Data describing context, content and structure of records and their management through time. Source: ISO 15489 (see appendix 7). Note: some models are based on a different conceptual view of metadata. For example, they may treat audit trail information as being entirely metadata. These alternative views are valid and valuable in their contexts, but are not helpful in specifying the functionality of systems, and so are not considered here. record (noun) Information created, received, and maintained as evidence and information by an organisation or person, in pursuance of legal obligations or in the transaction of business. Source: ISO 15489 (see appendix 7). Note: local national definitions may also apply. Note: a record may incorporate one or several documents (for instance when one document has attachments), and may be on any medium in any format. As a consequence, it may be made up of one or more components. In addition to the content of the document(s), a record should include contextual information and, if applicable, structural information (for instance information which describes the components of the record). A key feature of a record is that it cannot be changed. Note: both electronic records and physical records can be managed by an ERMS. sub-file Intellectual subdivision of a file. Note: sub-files are often used in case file management environments. Typically, each sub-file is named, and each sub-file is used to store a specified kind or kinds of records for one instance of a case, such as invoices, assessments or correspondence. They can, however, also be used, in a similar fashion, in non-case file environments. volume A subdivision of a sub-file. Note: the subdivisions are created to improve manageability of the sub-file contents by creating units which are not too large to manage successfully. The subdivisions are mechanical (for instance, based on number of records or ranges of numbers or time spans) rather than intellectual. Key Concepts The key concepts required to understand this specification are: record and electronic record; authoritative record; electronic file, sub-file and volume; classification scheme; class; ERMS; capturing records; user roles. Record and electronic record As explained in section 2.4 of the DLM Forum Guidelines (appendix 1), records can be viewed as consisting of: content; structure; context; presentation. The content is present in one or more physical and/or electronic documents that convey the message (the informational content) of the record. These are stored in such a way as to allow future users to understand them and their context. This view implies that a well-managed record consists of, in addition to the content of its document(s), information about its structure and metadata that provides information on its context, and its presentation to users. However in MoReq2, the term record is used to refer to the informational content the document(s) from which the record is made, without the metadata. The presentation depends on a combination of the records contents, structure and (in the case of electronic records) the software used to present it (see glossary). In the world of physical records, the vast majority of records are on paper and are included in files, physically constituted of one or more volumes of records inserted within paper folders. Procedural controls should prevent users from changing the records, or their positions within the file. Similar concepts apply to electronic records. A record is made from one or more electronic documents. These documents can be word processing documents, e-mail messages, spreadsheets, moving or still images, audio files or any other type of digital object. The documents become records when they are set aside, that is, captured into the ERMS. Upon capture, the records are classified, that is they are assigned codes corresponding to the classification scheme class to which they belong, allowing the ERMS to manage them. The records usually are assigned to a file though not always, see below. For preservation purposes, it is necessary to appreciate that electronic records are often made up of several components (the word component is used in MoReq2 to avoid the IT word file, so as to reduce the likelihood of confusion with records management files). Each component is an object managed by a computer operating system, and they may be in different formats; but they are all needed together to make up a record. Not all records have more than one component; for example, most word processing documents are made of only one component. An example of a record with several components is a web page with text, graphics and style sheets; it is not unusual for a web page to contain one HTML component, dozens of JPEG image components, and a handful of CSS (cascading style sheet) components. An essential quality of records is that their informational content is fixed. One consequence of this is that no action carried out on electronic records can be allowed to interfere with the relationships between its components; in other words, all actions carried out on any record must preserve the correct relationships between all its components. So, for example, whenever any record is moved or copied, it must be moved or copied in a way that keeps all its components and all their relationships. Authoritative Records ISO 15489 describes an authoritative record as being a record that has the characteristics of: authenticity; reliability; integrity; usability. As explained in ISO 15489, the aim of all records management systems should be to ensure that records stored within them are authoritative. Summarising, an authoritative record: can be proven to be what it purports to be; can be proven to have been created or sent by the person purported to have created or sent it; can be proven to have been created or sent at the time purported; can be depended on because its contents can be trusted as a full and accurate representation of the transactions, activities or facts to which it attests; is complete and unaltered; can be located, retrieved, presented and interpreted. The requirements in MoReq2 are designed to ensure that records stored in a MoReq2-compliant ERMS are authoritative. However, compliance with these requirements alone is not sufficient; the existence of, and compliance with, corporate policies is also required. Electronic File, Sub-file and Volume Paper records generally are accumulated in physical files, contained in paper folders. The paper files are aggregated into a structure, or classification scheme. In an ERMS electronic records can be managed as if they are accumulated in electronic files and stored in electronic folders. Strictly, electronic files and folders need not have a real existence; they are virtual, in the sense that they do not really contain anything; in fact they consist of the metadata elements of the records assigned to them. Further, in many cases, there need be no real distinction in the electronic system between file and folder. However, these details are not generally visible to ERMS users; ERMS application software allows users to view and manage folders as if they physically contained the documents logically assigned to the files. This user-centred view is carried forward into this specification. The rest of this specification therefore describes electronic files as containing records, for ease of understanding. Note however, that while this specification provides functional requirements for the management of electronic files, it does not prescribe the manner in which the concept of electronic files is implemented. In some environments it is useful to divide files into sub-files. The division into sub-files is an intellectual one; that is it (generally) requires human input to decide into which sub-file a record should be stored. Sub-files are most often used in case processing environment. An example would be a file for the sale of land, with sub-files for each of the business activities involved in the sale (such as advertising; contracts; dealing with lawyers, etc.). A sub-file is therefore a division of a file by type of content. As a result, a sub-file can be used to permit the application of a different retention and disposition schedule to a set of records within the file. Regardless of whether sub-files are used or not, files are sometimes divided mechanically into file volumes, according to predetermined conventions. The term mechanically implies simple adherence to such conventions, which are not based on the intellectual content of the files, but on size, number of records contained in them, or time spans. This practice originated with paper files, in order to restrict them to a manageable size and weight. It can be continued with electronic files, to limit them to a manageable length for appraisal, transfer, or other management purpose. It is especially appropriate for the management of files which are open for long periods and/or which grow to contain a large number of records. While the distinction between files and file volumes is clear, the implications are less clear. This is because the implications of choosing to divide files into volumes vary according to implementation needs. The variation arises as: some files are closed within a limited time, and so the unit used for management purposes is the file (even though a file may consist of several volumes). Examples are a file of a specific small procurement, or a file of one project; some files have an unlimited life span (or nearly unlimited life span), and so the unit used for management purposes is the volume. Examples are a file of records about a geographic region, or a file dealing with a subject which is not sensitive to time, such as some policies, or an invoice file where a new volume is started every year. In relatively rare cases, records may be stored outside of files  by being assigned to a class. This is explained in  REF BK4218 \n  3.2.17. Classification scheme Records management aggregates files in a structured manner, and good practice dictates that this structure should reflect business functions. The representation of this aggregation is referred to as a classification scheme. The classification scheme is commonly a hierarchy. The remainder of MoReq2 focuses on the hierarchical view; other approaches are outside the scope of MoReq2, and a hierarchical arrangement is a prerequisite for MoReq2 compliance. Just as files appear to exist even though they are really no more than aggregations of records, so higher levels of the classification scheme hierarchy seem to exist, though they are no more than aggregations of files and/or lower levels. As with files, this specification states requirements for the hierarchy without mandating the manner in which it is implemented. Files can appear at any level of the hierarchy. This is illustrated in figure 2.1, which represents a fictitious classification scheme, showing its classes and the files allocated to the lowest level classes. This fictitious scheme is much simpler than would be a real classification scheme.  Figure 2.1 Note that this figure is intended only to show selected possible relationships between levels, files and records. It does not show all possible levels or all possible arrangements. Class MoReq2 uses the term class to describe the portion of a hierarchy represented by a line running from any point of the hierarchy to all the files below it. The term class therefore corresponds to a group or series (or sub-group, sub-series etc.) in some texts. Visually, a class of a hierarchy corresponds to a branch of a tree. A class may thus contain other classes, just as a series contains sub-series and sub-sub-series. Continuing the above example, the shaded boxes and thick lines in figure 2.2 are one example of a class.  Figure 2.2 MoReq2 also uses the term class to mean all the files, records etc. assigned to a class much as the word bottle can be used to describe both a container and that container full of a liquid. This double usage is intentional, and the appropriate interpretation of the term is always clear from the context. MoReq2 uses the terms child and parent to describe the relationships between entities. A child of one entity is an entity that is below it in the hierarchy (in other words, is a descendant entity). A parent of one entity is an entity that is above it in the hierarchy. So for example, the children of classes can be other classes, files, or (in rare cases) records. MoReq2 allows for records to be assigned to, or stored directly in, a class without being in a file. This is intended for relatively rare circumstances, as described in the body of MoReq2. Electronic Records Management System (ERMS) An ERMS is primarily an application for managing electronic records, though it may also be used to manage physical records. An ERMS is often closely integrated with an Electronic Document Management System (EDMS) or a business application. Technically, an ERMS manages records, while an EDMS manages documents (which are not records). However, especially when used to support day-to-day working, it can be difficult to separate their functionality. This is explored further in section 10.3 which deals with Document Management. Capturing Records Documents made or received in the course of business become records when they are set aside, that is, captured into the ERMS. During capture, the records are classified, that is they are assigned codes corresponding to the class to which they belong, allowing the ERMS to manage them; and they are also assigned a unique identifier. In many cases, documents that are set aside, or captured, become records by being bound to a business process, as often happens in a workflow. For example, when an invoice is raised it should automatically cause a record to be captured. In other cases there may be a policy that every document relating to a business matter must become a record, even if it does not formally participate in a business process. In yet other circumstances however, the process of capture will be initiated selectively by a user. Determination of which documents should be captured into a records system should be based on an analysis of the regulatory environment, business and accountability requirements and the risk of not capturing the records. An example is a memorandum in an organisation which deals with policy issues; the organisation may define that only memoranda deemed to be significant will become records (i.e. insignificant memoranda, such as those relating to meeting arrangements, will generally not form records). In some situations, the drafts will be deemed to be significant and will become records, whereas in other situations drafts will not become records. MoReq2 is intended to cater for any of these scenarios. In other words, MoReq2 describes an office system for general use, not simply a records management system for particular kinds of application or for the exclusive use of archivists or administrators. User and Administrative Roles MoReq2 uses the concept of user to mean any person with valid permissions to work using the ERMS. Therefore anyone who is allowed to log on to the ERMS is a user, including administrators. However, the distinction between administrators and other users can be complex and is sometimes unclear. MoReq2 therefore uses the concepts of roles in defining many requirements. Different organisations will implement an ERMS differently. For example, a small organisation may implement an ERMS with a single administrator, while a large organisation may need several different administrative positions, each with different access permissions. For this reason, it is not helpful to identify specific access profiles in this generic specification; instead, MoReq2 uses the concept of roles. MoReq2 identifies two kinds of roles: user roles and administrative roles. In practice, most organisations will have more than one person in these roles; and many organisations will define further roles. Example roles with possible access permissions are outlined in the matrix at section 13.4. In brief, however, a role in MoReq2 is something like a user profile it is not a job or a position, but a set of responsibilities and functional permissions shared by several users. MoReq2 recognises examples of two administrative and two user roles. Administrative roles take actions related to the management of records themselves; their interest is in managing records as entities rather than their content or business context. They also manage the ERMS hardware, software and storage, ensure backups are taken and manage the performance of the ERMS. Unlike administrative roles, user roles have access to facilities which an office worker or researcher needs when using records. This includes adding documents, searching for and retrieving records; their interest is primarily in the contents of records rather than their management in other words, they are interested in the business processes evidenced by the records. Entity-Relationship Model This section contains an entity-relationship model at figure 2.5 which can be used as an aid to understanding the specification. Section 13.3 contains a narrative explanation. An important aspect of this model is that it need not represent actual structures stored in the ERMS. It represents a theoretical view of the entities associated with records. An ERMS uses these relationships to produce behaviour equivalent to the structures in the model. See section 2.2 for further explanation of this point. The relationships between the following key entities are depicted in the following entity-relationship model: Class; File; Sub-file; Volume; Record; Component. Other entities are also included. In the diagram, entities files, records and so on are represented by rectangles. The lines connecting them represent the relationships between the entities. Each relationship is described by text in the middle of the line; this text should be read in the direction of the arrow. Each end of the relationship has a number which represents the number of occurrences (strictly, the cardinality); the numbers are explained in the key. So, for example, figure2.3 means one record is made up of one or more components (note the direction of the relationship arrow).  Figure 2.3 A curved line crossing two or more relationships indicates that the relationships are mutually exclusive, for any given instance. So, for example, the curved line in figure 2.4 means each record is stored in either a volume or in a sub-file but not in both.  Figure 2.4 Note that the entity class is related to itself by the relationship is made up of. This relationship describes, in formal terms, the relationship between classes in a hierarchical classification scheme, where a class may be made up of one or more other classes. If this relationship (sometimes called a recursive relationship) is removed, the model applies equally to non-hierarchical relationships. In the remainder of MoReq2, terms printed in blue bold text indicate the first usage of a term defined in the glossary. In the electronic version this is a hyperlink to the definition, so pressing CTRL + click on the term navigates to the glossary definition, and pressing CTRL + click on the glossary definition navigates back to the term.  Figure 2.5 Classification Scheme and File Organisation This chapter lists requirements for management of the  HYPERLINK \l "Gl_ClassificationScheme" classification scheme and of the organisation of  HYPERLINK \l "Gl_File" files. It first lists requirements for setting up the classification scheme in section 3.1. It then lists requirements relating to  HYPERLINK \l "Gl_Class" classes and files (section 3.2) and  HYPERLINK \l "Gl_Volume" volumes and  HYPERLINK \l "Gl_SubFile" sub-files (section 3.3). Section 3.4 lists requirements associated with maintenance of the classification scheme. A classification scheme is the foundation of any  HYPERLINK \l "Gl_ERMS" ERMS. It allows an  HYPERLINK \l "Gl_ElectronicDocument" electronic record to be stored together with other  HYPERLINK \l "Gl_Record" records that provide its context, by defining the way in which the electronic records will be organised into electronic files, and the relationships between the files. A significant difference between MoReq2 and its predecessor is that MoReq2 allows the declaring of a record directly into a class, as well as into a file. The original MoReq did not allow declaration directly into a class; it allowed only declaration into a file. MoReq2 thus allows a record to be  HYPERLINK \l "Gl_Capture" captured into any of the following: Class; File; Sub-File; Volume. Records will most commonly be captured into volumes; for the rationale that requires capture in files and sub-files see  REF BK4201 \n  3.3.1,  REF BK4199 \n  3.3.2 and  REF BK4200 \n  3.3.3. Capture of records into classes is illustrated in figure 3.1, which adds such records (shaded in grey) to figure 2.1.  Figure 3.1 This change has been introduced to reflect the requirements of high-volume case management systems. It is, however, not meant to remove the necessity for a hierarchical classification scheme, or for the existence of files. Inappropriate use of this feature will introduce the risk of later difficulties in managing records, and users of MoReq2 are advised to use this functionality only after careful analysis. Most users of MoReq2 are unlikely to require this functionality, and so MoReq2 includes the requirement that this functionality can be disabled. MoReq2 compliance requires support for hierarchical  HYPERLINK \l "Gl_Classification" classification. This is because: hierarchical schemes are able to ensure an effective, stable and clear organisation of records; hierarchical schemes are the most widely used in Europe. It also maintains compatibility with the previous version of MoReq. Many requirements use the concept of class. In many cases, it may be possible to apply the requirement to non-hierarchical classification schemes; but this may not always possible. It is essential that the classification scheme (technically, a records classification scheme) is closely aligned with the business needs of the organisation. Good practice suggests that the organisation first identifies a business classification scheme before designing a records classification scheme. Configuring the Classification Scheme RefRequirement Test The ERMS must support and be compatible with the organisations business classification scheme.NThis requirement is not testable in the general case; it is included as a reminder to users of MoReq2 of the need to align the classification scheme used by an ERMS with the business needs of the organisation. These needs should be reflected by the arrangement of records external to the ERMS. The ERMS must maintain internal integrity (relational integrity or otherwise) at all times, regardless of: maintenance activities; other  HYPERLINK \l "Gl_User" user actions; failure of system components. PIn other words, it must be impossible for a situation to arise where any user action or any software failure results in an inconsistency within the ERMS or its database.  The ERMS should allow  HYPERLINK \l "Gl_AdministrativeRole" administrative roles to label each classification scheme with a Title, and Description, and must automatically label each classification scheme with an Identifier.YThis  HYPERLINK \l "Gl_Metadata" metadata will support functions such as  HYPERLINK \l "Gl_Export" export of the classification scheme and of records. The ERMS must be able to support a classification scheme which can represent files and records as being organised in a hierarchy of classes.YThe use of a hierarchical classification scheme is mandatory for compliance with MoReq2. This is in order to enable the inheritance of retention and disposition schedules and other metadata and also to facilitate navigability.Support for at least three levels is the minimum requirement; more levels will be needed in many environments.  The ERMS must allow management of the classification scheme by an administrative role only, subject to requirement  REF BK2765 \n  3.1.6.YIn this requirement,  management refers to the operations described in section 3.1 and section 3.4. The ERMS should allow management of individual classes by specified  HYPERLINK \l "Gl_UserRole" user roles and/or by a specified  HYPERLINK \l "Gl_UserGroup" group of users.YIn this requirement,  management has the same meaning as in requirement  REF BK2715 \n  3.1.5. This is intended for two settings: large classification schemes which are too large to be maintained centrally (and which therefore have central management for the higher levels and distributed management for the lower levels); classification schemes that include classes for the management of HYPERLINK \l "Gl_CaseFile"case files, which need to be managed in the business unit dealing with the cases on allocation of  HYPERLINK \l "Gl_AuthorisedUser" authorised user privileges. The ERMS should not limit the number of levels in the classification scheme hierarchy. PIn most settings, it is unlikely that the number of levels needed could be more than ten. The ERMS must support the creation of a classification scheme at  HYPERLINK \l "Gl_ConfigurationTime" configuration time in readiness for the capture and/or importation of electronic records. YThis requirement is intended to allow a classification scheme to be created while the ERMS is being configured, and before it is used for the management of records. The ERMS must allow the titling mechanism(s) to be defined at configuration time by an administrative role.Y The ERMS should allow the input of textual scope notes (also known as descriptions) to all classes, files, sub-files and volumes.YScope notes are narrative intended to clarify the intended contents and/or exclusions of classes, files sub-files and volumes for the benefit of users. If a formal MoReq2 XML schema has been published, the ERMS must be able to  HYPERLINK \l "Gl_Import" import and export records etc. in a form compliant with that schema.Y The ERMS must support the importing of all or parts of a classification scheme, at configuration time or at any other time. YThis requirement is intended to allow a classification scheme to be created while the ERMS is being configured, and before it is used for the management of records. Where any part(s) is (are) imported, this may be to add to an existing scheme, or to create a new classification scheme if none exists. When the ERMS imports all or part of a classification scheme it must allow the import of the associated metadata,  HYPERLINK \l "Gl_RetentionSchedule" retention and disposition schedules and  HYPERLINK \l "Gl_AuditTrail" audit trails if these exist.YIn ideal cases, the classification scheme that is being imported will have class metadata and retention and disposition schedules. In other cases, these may be absent or incomplete. Where the ERMS imports the metadata of a classification scheme, it must reject any class that does not have a title, and create an exception report for an administrative role listing the classes that were rejected.YIn an ERMS that is not MoReq2 compliant it may be possible for a class to have no title (a null value); but such a class would be impossible to use within a MoReq2-compliant ERMS. Where the ERMS imports the metadata of a classification scheme, the ERMS must assign to each imported class a hierarchical code in one of the following ways, according to an option set by an administrative role: following the same rules as would be used for the manual creation of the classification scheme; keeping the original codes in their entirety (only possible if the structures are compatible); appending the original codes to the codes in the receiving scheme.PIf a hierarchy that is being imported already includes hierarchical class codes (for example 4/6/4) it may not be possible to use these as codes in the ERMS, as consistency and uniqueness cannot be guaranteed.There are many possible scenarios for such an import, with different kinds of incompatibility between hierarchical numbering schemes. MoReq2 does not prescribe the outcome of an attempt to select an option that is logically impossible because the schemes are incompatible.If the existing codes cannot be used, they can be treated as appropriate to the situation, e.g. copied to a metadata element called old class code.  Where the ERMS imports the metadata and retention and disposition schedules of a classification scheme, it must validate them using the same rules as would be used for the manual creation of the classification scheme (see chapter 12). Where this validation process finds errors (for example the absence of mandatory metadata, or format errors) it must bring these to the attention of the administrative role performing the importation, identifying the metadata involved.YIn ideal cases, the classification scheme that is being imported will have metadata (e.g. metadata for its classes) that complies fully with the MoReq2 metadata model. In other cases, the metadata may be non-compliant. In these cases, several outcomes are possible; MoReq2 does not mandate any one outcome. Possible outcomes include: The entire importation is cancelled and the administrative role is informed of the reason for the cancellation; Importation of the class that has non-compliant metadata is cancelled and the administrative role is informed of the reason for the cancellation; The administrative role is required to choose between correcting the error and cancelling importation of the affected class; Importation continues even though part of the metadata is non-compliant, with non-compliant data being replaced by default values specified for the affected elements and an error report produced. Informing the administrative role does not require that the importation process be a foreground, or real-time process; it will be acceptable for the process to be a background, or batch, process. The ERMS should support the export of all or part of a classification scheme.Y Where the ERMS supports the export of all or part of a classification scheme this must include associated metadata, an administrative role being able to select which metadata is exported.Y Where the ERMS supports the export of all or part of a classification scheme this must include all associated retention and disposition schedules at the option of an administrative role.Y Where the ERMS supports the export of all or part of a classification scheme, this must include all or selected audit trail data, the selection to be made by an administrative role.Y Where the ERMS supports export (for any of the above requirements) it must use a fully-documented method to relate the entities to each other.YThe documentation of the method must define how the records, files, classes etc., and their relationships to each other, are expressed. See also  REF BK3176 \n  3.1.22. Where the ERMS supports export (for any of the above requirements) it should export the information in XML or equivalent open standardised  HYPERLINK \l "Gl_Format" format.Y Where the ERMS supports the copying of all or part of a classification scheme this must include all associated metadata.Y Where the ERMS supports the copying of all or part of a classification scheme this must include all associated retention and disposition schedules.Y The ERMS must allow administrative roles to add new classes at any point within any class, so long as files or records are not stored at that point.YMoReq2 does not allow files and classes to exist at the same level within a class (in other words, files and classes cannot be mixed at a single node in the classification scheme hierarchy). This is for reasons of good records management practice. The ERMS should support the definition and simultaneous use of multiple classification schemes. YMost organisations will mandate that a single classification scheme be used for the primary classification of all the files in the ERMS. This requirement allows some of the files in the ERMS to belong to one classification scheme while other files belong to another. This may be required, for example, following the merger of two organisations, or when different collections of records in a single organisation require different management regimes.Classes and Files This section lists requirements which apply to classes and files. Classes and files are different kinds of construct. Classes provide a framework for classification, while files aggregate records; classes are building blocks of classification schemes, while files are not. Despite these major differences, it is helpful to list some requirements together, as they are common to both. RefRequirement Test The ERMS must support the capture, maintenance and  HYPERLINK \l "Gl_Presentation" presentation of metadata for files and classes in the classification scheme, compliant with the MoReq2 metadata model. Y The ERMS must restrict the ability to add to file and class metadata as set out in the MoReq2 metadata model.N The ERMS must provide a mechanism for allocating automatically a hierarchical  HYPERLINK \l "Gl_ClassificationCode" classification code (where such a code does not already exist  see  REF BK2773 \n  3.1.15) to each class, file, sub-file and volume in the classification scheme.YSee also  REF BK2270 \n  7.1.1. The ERMS must allow user roles to allocate a title for each  HYPERLINK \l "Gl_Electronic" electronic class, file, sub-file and volume.YThis requirement applies to  HYPERLINK \l "Gl_NonCaseFile" non-case file environments. Where case file management is needed, an alternative naming approach is needed. This is specified in section 10.5. It must be possible to use both the classification code and textual file title separately or together.Y The ERMS must allow an administrative role to configure the classification code at configuration time or later.Y The ERMS should allow configuration of the classification code to include: the format of the identifier associated with each level of the hierarchy, e.g. numeric, alphabetic; the first value of this identifier at each class, e.g. 1, 1000; the interval to be used between successive classes, e.g. 1, 10; the presence or absence of leading zeroes; any global prefix, e.g. corporate/; any global extension, e.g. country suffix; the separator between each identifier, e.g. /, -.Y The ERMS must store the date of opening and the date of closing of a class or file within the class or files metadata.YThe date of opening and closing of a class or file provide important context for the records classified within it. See also  REF BK2106 \n  3.3.9.When a class or file is  HYPERLINK \l "Gl_Open" open, it is possible to capture records into it. When a class or file is  HYPERLINK \l "Gl_Closed" closed, it is not possible to capture records into it. The ERMS must store the date of creation of a new class, file, sub-file or volume in the metadata of the class or file.YIn the case of  HYPERLINK \l "Gl_PhysicalFile" physical files, it is possible for the date of opening to be earlier than the date of creation stored in the ERMS. This can arise if a physical file is created and opened, in physical form only, before it is created in the ERMS. In the case of electronic files, it is possible for the date of opening to be earlier than the date of creation stored in the ERMS. This can arise when an electronic file is imported into the ERMS from another system. Whenever a new class or file is opened, the ERMS must automatically include in its metadata those attributes which are inherited due to its position in the classification scheme.YFor example, if a file titled Public meetings is in a hierarchical path titled: Regional plan development : Public consultation : Public meetings and an administrative role adds a new file titled Written consultations at the same level as the Public meetings file then the new file must automatically inherit the prefix Regional plan development : Public consultation.Note that inherited metadata does not have to be stored explicitly; it can be inherited implicitly. See appendix 9.3 for details. The ERMS must allow an administrative role to modify inherited metadata values, to the extent permitted by the MoReq2 metadata model.YInherited values often provide a default, or starting position. This can be changed, so long as the change is compatible with the metadata model. Any addition to the inherited metadata of a class should be inherited by default by all its child classes and files.Y The ERMS should support the allocation of controlled vocabulary terms compliant to ISO 2788 as descriptive class or file metadata subject terms, in addition to the other requirements in this section. Y The ERMS should support the allocation of controlled vocabulary terms compliant to ISO 5964 as descriptive class or file metadata subject terms, in addition to the other requirements in this section.YRequirements  REF BK2093 \n  3.2.13 and  REF BK3635 \n  3.2.14 are identical save that the former specifies a monolingual thesaurus and the latter a multilingual thesaurus. The ERMS must not impose any practical limit on the number of classes or files which can be defined.P The ERMS should be able to export a list, or  HYPERLINK \l "Gl_Repertory" repertory, of all files or of files classified against a specific class (and its child classes) in XML format and/or in a human-readable format.P The ERMS must allow an administrative role to configure a class so that it can, or so that it cannot, store records directly.YIn other words the system must be able to be configured so that records do not have to be held in files, sub-files or volumes.Volumes and Sub-Files In a system that keeps paper records, subdivision of large files is essential for reasons of ergonomics and the physical survival of folders, binders, jackets etc. Typically,  HYPERLINK \l "Gl_PaperFile" paper files are limited to 2cm in thickness, by the establishment of volumes. When the file (in reality the first volume of the file, despite being referred to as a file) reaches the size limit 2cm thick in this example it is considered to be a closed volume and a new volume is opened. This is not true of electronic files an electronic file can usually grow to almost any size without such difficulties. However, in practice, there can be benefits in splitting large electronic files into volumes. These benefits are, for example: when users need to work remotely (that is, over low-bandwidth connections, or after downloading records to a portable PC, or onto a storage device with limited capacity); when files are never closed, because they are (for example) geographically linked. Similarly, paper files are often divided into sub-files especially in case management environments. The sub-files are used to organise the file contents, often according to  HYPERLINK \l "Gl_DocumentType" document type. Correspondingly, there are sometimes benefits in dividing electronic files into sub-files, for example: improving the ease of navigation through a file; providing a means to manage records that have retention requirements that differ from others in the file, such as those covered by privacy legislation. This section includes requirements relating to the use of volumes and sub-files, both of which are typically used to subdivide files which might otherwise be unmanageably large. However, Moreq2 does not mandate that these subdivisions be implemented; it merely requires that MoReq2 compliant software must be able to provide them when needed. Sub-files were not recognised in the previous version of MoReq. In summary: Each file may contain one or many sub-files; Each sub-file may contain one or many volumes; Volumes of different sub-files are created independently; All the sub-files of an open file can be open or closed by users as required; Only one volume can be open in each sub-file. For more detail about sub-files and volumes, see section 2.2. RefRequirement Test It must be possible for an administrative role to configure the ERMS at configuration time or later to remove the ability to create sub-files and/or volumes within files across the classification scheme.Y It must be possible for an administrative role to configure the ERMS at configuration time or later to allow only sub-files to be created within files within specified classes of the classification scheme.Y It must be possible for an administrative role to configure the ERMS at configuration time or later to allow only volumes to be created within files within specified classes of the classification scheme.YThe intention of the three requirements above is to allow organisations to allow or prevent the use of sub-files and/or volumes in different parts of the classification scheme. The use of both brings the maximum flexibility, but this flexibility brings complexity and possible confusion for users. Where a part of a classification scheme is configured to allow sub-files, then all files in it must contain at least one sub-file. Where a part of a classification scheme is configured to allow volumes, then all files (or sub-files if allowed) must contain at least one volume.Therefore the system should remain transparent to users, for example: when a sub-file contains only one volume, it is acceptable for the sub-file and volume to be indistinguishable to end users; when a file contains only one sub-file which itself contains only one volume, it is acceptable for all three to be indistinguishable to end users.The intention of this is to emphasise that the ERMS need not impose on users the structure of file, sub-file, volume. The ERMS must allow the use of sub-files and volumes, while allowing users to think in terms of files only if this suits them.The essence of this is that the user only sees what is essential from a business process point of view and is not encumbered by potentially confusing choices. The ERMS must support the concept of open and closed electronic volumes, as follows: only the most recently created volume within a sub-file can be open; all other volumes within that sub-file must be closed.Y The ERMS must prevent the user from adding electronic records to a closed volume. Y The ERMS must allow administrative roles to add an electronic volume to any electronic sub-file which is not closed.YThe process of adding a new volume consists of closing the volume that is currently open and creating a new open volume. The ERMS must allow administrative roles to add sub-files to any electronic file which is not closed.Y The ERMS must allow users to  HYPERLINK \l "Gl_Close" close a sub-file at any time.Y The ERMS must store the date of opening of a new volume or sub-file in its metadata. Y Whenever a new volume or sub-file is opened, the ERMS must automatically store in its metadata those values of its parent files metadata which are common (as defined in the MoReq2 metadata model). YRecords in a volume can be accessed regardless of whether the volume is open or closed. Whenever a new volume is opened, the ERMS must automatically assign to it an identifier that is unique within its parent sub-file.PThe identifier could be a simple sequence number, starting at 1 for each sub-file. The ERMS must store the date of closing of volumes and sub-files in their metadata. Y When classifying a record the user must be presented with the most recently created volume in the chosen sub-file by default.Y The ERMS must allow the creation of multiple concurrent open sub-files within any file.Y The ERMS must allow an administrative role to delete an empty volume.Y The ERMS must allow an administrative role to delete an empty volume and re-open the previous volume in the sub-file, in a single action, logging the event in the audit trail.YThis is intended to correct an error which has resulted in the incorrect closure of a volume. The ERMS should allow a template of sub-files to be created by an administrative role for a specified class, such that the template specifies the sub-files to be created automatically for each new file that is subsequently created in that class.YThis is intended primarily for case management environments. As an example, a template in an insurance company might specify, for the class dealing with client insurance policies, the following sub-files: policy and amendments, internal correspondence, correspondence with medical specialists, billing, other client correspondence. Thereafter, every new file created in that class would automatically be created with these sub-files. The ERMS must automatically close any open sub-files in a file whenever their parent file is closed.Y The ERMS must allow users to close volumes individually.YMaintaining the Classification Scheme This section starts with requirements for reclassifying, combining, splitting and copying classes ( REF BK2123 \n \* MERGEFORMAT  3.4.1 to  REF BK2717 \n \* MERGEFORMAT  3.4.4). All these facilities are intended for exceptional circumstances only, such as organisational mergers or other re-organisation, or to correct clerical errors, or when the classification scheme is not well suited to the business. These facilities are not intended for routine use with a well-designed classification scheme. The requirements should be read together with  REF BK4595 \n \* MERGEFORMAT  9.3.3 and  REF BK3929 \n \* MERGEFORMAT  9.3.4. The section concludes with other requirements related to classification scheme maintenance ( REF BK2707 \n \* MERGEFORMAT  3.4.17 onwards). RefRequirement Test The ERMS must allow an administrative role to relocate a class within the classification scheme in a single transaction. YIn this context, relocation means reclassifying the class or file, that is moving it to another point in the classification scheme. The relocation can be to the same level in the classification scheme, or to any other level. Relocation implies several additional requirements that are described later in this section. The ERMS must allow an administrative role to combine two classes in a single transaction. YIn this requirement, combine is to be understood as follows: if a class is combined with another class, all the children and contents of the former class are relocated so that they become children and contents of the latter class; the former class is closed. The ERMS must allow an administrative role to divide a class into two in a single transaction. YIn this requirement, divide is to be understood as follows: if a class is divided: a new class is created as a child of the same parent class as the class being divided (this assumes all the requirements of creating a new class, such as metadata capture and inheritance); the user specifies a point in the contents of the class that is to be divided; all the contents of that class beyond that point (that is, with a higher classification code) are relocated to the newly created class.The contents of the class being divided can be any of the kinds of content allowed, namely classes, files, or records. The ERMS should allow an administrative role to copy any class within the classification scheme in a single transaction.YIn this requirement, copy is to be understood to mean creating a copy of the class and all its contents at another point in the classification scheme leaving the original in place. The copy can be to the same level in the classification scheme, or to any other level. Copying implies several additional requirements that are described later in this section.This facility is intended for use when replicating branches of a classification scheme, an act that is sometimes required (for example) when designing a part of the scheme that is not designed on a functional basis. Use of export followed by import will not be considered sufficiently easy to meet this requirement. When any classes are relocated or copied the ERMS must ensure that the newly relocated or newly copied files and all their contents are reclassified with the classification codes for their new location in the classification scheme.YThis means that every class, file, sub-file, volume, record and  HYPERLINK \l "Gl_Component" component that is relocated or copied acquires a new classification code and fully-qualified classification code.The rules for the allocation of the new codes are the same as the rules that would be followed when creating new classes, files, records etc. The ERMS must not require an administrative role who is relocating, dividing, combining or copying classes to perform separate export and import actions.YThe essence of this requirement is ease of use; the users must not be forced to execute a series of unrelated actions to achieve the desired outcome. The ERMS must not allow any relocation or copying that would result in a data structure that is contrary to the rules implicit in the MoReq2 Entity-Relationship model (see section 13.2) or explicit in other requirements. Specifically, it must not allow any relocation that would result in: storing any sub-file(s) or volume(s) in a class of the classification scheme that has been configured not to allow sub-files or volumes (see  REF BK4201 \n \* MERGEFORMAT  3.3.1,  REF BK4199 \n \* MERGEFORMAT  3.3.2,  REF BK4200 \n \* MERGEFORMAT  3.3.3); storing any record(s) directly in a class that already contains any file(s) or vice versa; storing any file(s) in a class that already contains any class(es) or vice versa.Y The ERMS must ensure that during relocation all electronic records remain correctly allocated to the class(es) and/or and file(s) being relocated; and that any sub-file(s), volume(s) and file(s) remain correctly related.P The ERMS must ensure that during copying all copies of electronic records remain correctly allocated to the new copies of the class(es) and/or file(s) and that copies of any sub-file(s), volume(s) and file(s) remain correctly related.P When any classes, files, volumes, sub-files or records are relocated or reclassified any closed files must remain closed, retaining their references to the classification scheme (classification codes) before the change.Y When any classes, files, volumes, sub-files or records are relocated or reclassified any open files must either: be closed, retaining their references to the classification scheme before the change, and cross-referenced to a new file in the changed scheme in metadata; be referenced to the changed scheme, but clearly retaining all prior references to the classification scheme before the change in metadata; according to the choice of the administrative role performing the relocation.Y When any classes are relocated or copied the ERMS must enable the optional inheritance of metadata by the classes and their contents (or the copies) from the new parent class.YThis includes such elements as access permissions and security classifications. When any classes are relocated or copied, the ERMS must be able to apply any inheritable retention and disposition schedules from the new parent class to the relocated or copy classes and their contents, in addition to the existing retention and disposition schedules.YThis is the minimum functionality required; the ERMS may offer additional ways to treat the retention and disposition schedules.This may result in conflicts between schedules; if any conflicts arise these should be dealt with as in section 5.1 (especially  REF BK2988 \n  5.1.18 and  REF BK2183 \n  5.1.33). When any classes are relocated or copied the ERMS must require an administrative role to enter as metadata the reason for the relocation or copying.YEntry of a reason is mandatory, as relocation and copying are exceptional, potentially endangering the integrity of the records if not carefully managed. When any classes, files, or records are relocated or copied the ERMS must log their status prior to the relocation or copying in the audit trail.Y When any classes are relocated the ERMS must log the values of their metadata prior to the relocation.YBoth of the above requirements are in support of the need to be able to determine the history of records that have been relocated. The ERMS should enable an administrative role to mark a class or file as inactive to prevent any new files being added to that class or records being added to that file.Y The ERMS should allow an administrative role to delete an empty class.Y The ERMS must prevent the deletion of an electronic file or any part of its contents at all times. YThis requirement is subject to the exceptions of:  HYPERLINK \l "Gl_Destructon" destruction in accordance with a retention and disposition schedule  as explained in  REF BK2190 \n  5.1.25; or deletion by an administrative role as part of an audited procedure  as explained in section 9.3.  The ERMS must allow an electronic file to be closed by user roles. YThis is different than the corresponding requirement in MoReq, which limited this function to  HYPERLINK \l "Gl_Administrator" administrators. The ERMS should be able to close an electronic file volume automatically on fulfilment of specified criteria to be defined at configuration, including at least: volumes delineated by an annual cut-off date; for example, the end of the calendar year, financial year or other defined annual cycle; the passage of time since a specified event; for example, the most recent addition of an electronic record to the volume; the number of electronic records which the volume contains.YOther criteria may be desirable in particular circumstances, for example when the size of the volume reaches the storage capacity of a removable disc. The ERMS must make the contents of closed classes, files, sub-files and volumes as accessible for viewing as those that are open, without making any differentiation between open and closed.YIn other words, users who are searching for or browsing through information using the ERMS must not have to be aware of whether files etc. are closed or open; and the same search facilities and access rules must apply. The ERMS should allow users to create cross-references (that is, see also type links) between related files. Y The ERMS should support the ability to create multiple entries for an electronic record, in several electronic classes, files, sub-files or volumes, without duplication of the record or of the  HYPERLINK \l "Gl_Document" document on which it is based.YMoReq2 does not specify how this is achieved. One way of supporting this requirement would be to use pointers when capturing more than one record based on the same document. The ERMS must provide reporting tools for the provision of statistics to administrative roles on aspects of activity within the classification scheme, including the numbers and sizes of classes, files, volumes, sub-files or records created, closed or deleted within a given period. YReporting should be both overall and by any specified user or class. The ERMS should provide ad hoc reporting capabilities on aspects of activity within the classification scheme.P Any user working with a class, file or record must be able to discover the context of that class, file or record, or in other words, the metadata and parent file or class(es); and must be able to navigate to these parents from the class, file or record.YIt must be possible to discover the context without having to leave the class or file, in a way that allows work with the file to be continued without interruption. Whenever any  HYPERLINK \l "Gl_keyword" keyword of any file is changed, the ERMS must require an administrative role to enter the reason for the change.Y Whenever any keyword of any file is changed, the ERMS must keep a clear trace of its status prior to the change so that its history can be determined easily.YThese controls over keyword changes are required to mitigate the risk of records being concealed by changes to keywords. Because keywords are used to find records, it is necessary to track any changes to keywords to avoid the possibility that a user would attempt to hide a record by changing its keywords.Controls and Security This chapter brings together requirements for a wide range of controls which relate to the security of records. These requirements provide features needed to protect the characteristics of records defined in section 7.2 of ISO 15489. It is essential that organisations are able to control who is permitted to access records and in what circumstances, as records may contain personal, commercial or operationally sensitive data. Restrictions on access may also need to be applied to external users. For example, in some countries where freedom of information legislation permits access to selected public records, customers may wish to view records. Also some organisations may wish to share parts of their ERMS repository with partner organisations. Requirements for these controls are listed in section 4.1. Any access to records and all other activities involving them and related documents or data also need to be logged in the audit trail to ensure legal admissibility and to assist in data recovery. Requirements for these audit trail controls are listed in section 4.2; these requirements address principally the record characteristics of  HYPERLINK \l "Gl_Authenticity" authenticity and integrity defined in section 7.2 of ISO 15489. Security of records also includes the ability to protect them from system failure by means of backup, and the ability to recover the records from backups. These requirements are listed in section 4.3; these requirements are related to the record characteristic of usability defined in section 7.2 of ISO 15489  HYPERLINK \l "Gl_VitalRecord" Vital records are mission-critical records that need to be recovered rapidly after a disaster. These are addressed in section 4.4. Access Organisations need to be able to control access to their records and typically this is achieved by the specification and implementation of security policies, i.e. access to records is granted based on the business role an individual plays in the organisation. Users are usually managed centrally and simultaneously granted access rights to a number of corporate systems, including but not restricted to the ERMS. It is not considered best practice to manage permissions in an ERMS simply by allocating individual permissions on individual entities to individual users. Access rights will therefore normally be granted to  HYPERLINK \l "Gl_Role" roles and/or groups to allow them to save and refer to records in specified classes or files within the classification scheme. In addition to the entitlement to access specific parts of the classification scheme, permissions also restrict the actions that a user, role or group can perform on entities within the ERMS, such as inspecting their metadata or their contents, modifying or deleting them and creating or viewing entities of a particular type. For example, a user role can search for and read records, but role-based security organisation may restrict the capability to search and read to particular sub-sets of the classification scheme. Permissions can be applied to groups and be inherited by the group members. Applying permissions at the group level, rather than the user level improves the management of the ERMS over time as new users arrive, and existing users change and leave. Through the assignment of roles in the ERMS multiple permissions can be granted to a user or group automatically. Later, when the user or group is removed from the role, all the permissions are automatically rescinded. The ERMS must be able to limit the setting of these access rights to certain roles. In the table in 13.4, this is shown as belonging to administrative roles. Note, however, that administrative roles are only implementing, from a system perspective, policy decisions taken by more senior management. The security polices and their allocation to individual end users, are typically based on the business needs of users to access information, the organisations records policy and laws and regulations, such as information laws, data security laws, archival laws and industry regulations (see section 11.5). In some environments, ERMS access permissions are managed entirely within the ERMS. In others, some permissions are managed using separate software, such as a network operating system utility. Either is acceptable for compliance with the following requirements. The roles identified are indicative only. It should be the organisation that sets the number and the make-up of the roles that it uses and even whether it uses roles at all, according to its own requirements. RefRequirement Test The ERMS must not allow any person to carry out any action in the ERMS unless the person is an authorised user who is successfully identified and authenticated.YMoReq2 does not specify the nature of the authentication mechanism. In many situations, a user-id and password mechanism is considered to provide sufficient authentication. Organisations using MoReq2 for procurement purposes need to ensure that an appropriate level of authentication is included. The ERMS must allow administrative roles to allocate access to records, sub-files, files, classes and metadata to specified users and/or user roles and/or  HYPERLINK \l "Gl_UserGroup" user groups and for specified periods of time. Y The ERMS must not limit the number of roles or groups that can be configured.P The ERMS must allow administrative roles to maintain permissions for all roles and groups. These determine the functionality, metadata elements, records or files to which the roles and groups have access, and the kinds of access allowed.Y The ERMS must allow administrative roles to use permissions to: restrict access to specific files or records; restrict access to specific classes of the classification scheme; restrict access according to the users  HYPERLINK \l "Gl_SecurityClearance" security clearance (where applicable); restrict access to particular features and functions (e.g. read, update and/or delete specific metadata elements); deny access after a specified date; allow access after a specified date. PThe permissions should be used to allocate access according to the organisations security policies.The level of granularity required is indicated in section 13.4. The ERMS should allow configuration to enable access by means of an integrated network log-on.Y The ERMS must allow administrative roles to add and remove users to and from roles and groups at any time.YIt is acceptable for administrative roles to manage groups by means of separate directory management software. The ERMS must allow the allocation of administration rights over different sections of the classification scheme to different administrative roles.YFor example see the access control model in section 13.4. The ERMS must allow administrative roles to mark an individual user as inactive, without deleting the user from the system.YIt is acceptable for administrative roles to manage users by means of separate directory management software.  The ERMS must allow administrative roles to define the same access rights for user roles as for users.YThis feature allows administrative roles to manage and maintain a limited set of role access rights rather than a larger number of individual users. Examples of roles might include Manager, Claims Processing Clerk, Security Analyst, Database Administrator.  The ERMS must be able to apply selections of access requirements across roles.YFor examples see section 13.4. The ERMS must allow an administrative role to set up and maintain groups of users.YExamples of groups might be Human Resources, Northern sales team.  The ERMS must allow a user to be a member of one group, more than one group or no group. YIt is likely that some users will have different access requirements for different parts of the classification scheme. In all cases, users are assigned to groups by administrative roles in response to business needs and policies. The ERMS must allow administrative roles to set up ad hoc lists of individual users in order to control access to specified parts of the classification scheme or records.Y The ERMS must restrict systems functions and related events to administrative roles only.YThis is needed to protect the authoritativeness of electronic records.  The ERMS must allow only administrative roles to set up  HYPERLINK \l "Gl_UserProfile" user profiles and allocate users to groups and roles. YSee also section 13.4. The ERMS must allow roles with ownership of records to specify which other users or groups can access those records.YSee glossary for the MoReq2 usage of the term  HYPERLINK \l "Gl_Owner" owner. If the organisational policy allows, ownership should be with administrative roles. The ERMS must restrict the ability to make changes, such as adding, amending and deleting  HYPERLINK \l "Gl_Profile" profiles for groups, roles or users to administrative roles. YThis includes attributes such as access rights, privileges, password allocation and management. The ERMS must allow administrative roles to set up and manage rules to govern users access to ERMS functions, so that different roles have access to different combinations of functions. The ERMS must allow such rules to be set up with at least the level of granularity (i.e. the amount of breakdown) shown in the illustrative access rights table in section 13.4.YDifferent organisations have different functional access control requirements. It is therefore not appropriate to attempt to define a generic model. Accordingly, this requirement specifies instead the level of detail of control that an ERMS must offer. The ERMS must allow administrative roles to create roles additional to those shown in 13.4.YAn organisation could define roles with specific access rights such as:  HYPERLINK \l "Gl_CaseWorker" case worker, manager etc. The ERMS should provide an application programming interface to provide access to records by initiation from another application system.N If a user performs any search that includes content searching (typically, but not necessarily, a full text search or free text search), the ERMS must not include in the result list any record for which the user does not have the permissions to access.YThis requirement is needed to prevent users employing text searches to investigate the contents of documents to which they are not allowed access.  If a user requests access to, navigates to, or searches for, without searching for content, any object such as a record, volume, sub-file, file or class which the user does not have the permission to access, the ERMS must provide one of the following responses (the response to be selected at system configuration or at a later time): provide no information about the object, thus providing no indication of whether the object does or does not exist; confirm the existence and (optionally) the owner of the object (display its file or record identifier) but not its title or other metadata. display title, type of entity (class, record etc.), date of creation and owner only; display title and other metadata of the object.YThe option in the first bullet of this requirement specifies the same outcome as for content searches (see  REF BK2127 \n  4.1.22). The other three options intentionally offer other possibilities, appropriate in some organisations; they are shown here in order of decreasing security. They should be configured by administrative roles.This requirement applies only to access attempts that do not involve searching on record content. Searches on record content are addressed in  REF BK2127 \n  4.1.22, with which this requirement should be read. The ERMS should allow the responses specified in  REF BK2128 \n  4.1.23 to be selected for a class as an alternative to a system-wide setting at configuration time or later.YAudit Trails An audit trail is a record of actions taken which involve the ERMS. This includes actions taken by users or administrative roles, or actions initiated automatically by the ERMS as a result of system parameters. See the glossary at section 13.1 for a formal definition. The audit trail shows whether business rules are being followed and ensures that unauthorised activity can be identified and traced. In order to support accountability it is essential that the ERMS is able to log in the audit trail any action where any degree of automated or machine assisted processing is implemented within the system. Section 10.5 Casework provides examples of such an interface. The audit trail is a key factor in enabling the ERMS to fulfil these requirements by maintaining a complete log of all the actions on every record (subject to the constraint of the level of security of the technical environment). The volume of audit trail information can become large if all actions are audited. Consequently, in some implementations, management may decide that selected actions need not be included in the audit trail (after the date of the decision). In many implementations, the on-line audit trail is periodically moved to off-line storage, the off-line copy being subject to deletion if and when the relevant records are disposed of, or if and when policies and legislation permit. These are matters of management policy and/or legal/regulatory requirements. MoReq2 therefore includes system requirements to allow these actions, but does not establish the extent to which they are used. RefRequirement Test The ERMS must keep an unalterable audit trail capable of automatically capturing and storing information about: any action taken on any record, any aggregate or the classification scheme; the user undertaking the action; the date and time of the action. YBy way of illustration, the actions logged in the audit trail must include, but need not be limited to: capture of all electronic records; re-classification of an electronic file within the classification scheme (see  REF BK2123 \n \* MERGEFORMAT  3.4.1); any change to any retention and disposition schedule; any  HYPERLINK \l "Gl_Disposition" disposition review actions carried out by administrative roles; the placing or removal of a  HYPERLINK \l "Gl_DisposalHold" disposal hold on an electronic file; any change made to any metadata associated with classes, electronic files or electronic records; amendment and deletion of metadata by a user; changes made to the access permissions; creation, amendment or deletion of a user or group; export or  HYPERLINK \l "Gl_Transfer" transfer; creation of a presentation; deletion/destruction of records. The term unalterable in this requirement means that it must be impossible for any user or administrator to change or delete any part of the audit trail. The level of assurance needed will depend on the organisation; the level of assurance that can be achieved will depend on the level of security of the underlying operating system and system software.The audit trail may, however, be subject to re-organisation and/or copying to off-line storage if required by, for example, database software, so long as its integrity remains intact.  Where the ERMS supports the transfer of audit trail data to off-line storage, the ERMS must support secure processes for managing the off-line data and demonstrate how off-line data can be brought back on-line as and when required; and the ERMS must ensure it is not possible for this mechanism to be used as a means of by-passing the controls imposed by the ERMS (for example, by simply moving audit trail data out of the ERMS and changing or deleting it externally to the system).P The ERMS should be able to log automatically in the audit trail any access to any record or  HYPERLINK \l "Gl_Aggregation" aggregation and whether the access was to read, print or otherwise present it.YThis is normally only required in highly secure environments. The ERMS audit trail parameters must be configurable so that administrative roles can configure which actions are automatically logged.Y All changes to audit trail parameters must be audited in the audit trail. YIt should never be possible to turn off the auditing of changes to audit trail parameters so that the ERMS does not record in the audit trail who changed them and when. Once the audit trail parameters have been set, the ERMS must track actions automatically and must log information about them within the audit trail.Y The ERMS must maintain the audit trail for as long as is required by the organisations records policy. NThis often will be at least for the life of the records to which the audit trail refers. However, there may be situations in which other policies apply, for example periodic scrutiny of the audit trail followed by its destruction and replacement by a certificate of scrutiny. The ERMS must log in an audit trail all actions performed on records, volumes, sub-files, files, classes and retention and disposition schedules, regardless of whether the action affects one or more of them. P The ERMS must log in an audit trail all changes to metadata values that apply to the metadata elements listed in the MoReq2 metadata model.P Any annotation of or amendment to a record must be logged within the records audit trail.Y The ERMS must automatically log in an audit trail all changes made to administrative parameters. YFor example, if an administrative role changes a users access permissions or reconfigures the audit trail. The ERMS must ensure that audit trail data is available for inspection on request, so that a specific event can be identified and all related data made accessible.Y The ERMS must include features that allow all authorised users, including those who have little or no familiarity with the system, to search for information in the audit trail. PThis is an ease of use requirement. The users may be external to the organisation, such as external auditors. Nonetheless, from the ERMS perspective, they will be users. The ERMS must allow users to search audit trails for specified events, objects (classes, records etc.), users, groups, roles, times, or time intervals.Y The ERMS must be able to export audit trail data for specified records, volumes, sub-files, files and classes without affecting the audit trail stored by the ERMS in any way save for the addition of an audit trail of the export process. YThis functionality is to enable, for example, external auditors to examine or analyse system activity. The ERMS must be able to capture and store, where applicable, any attempted violations of access control mechanisms (i.e. a users attempts to access a record, volume, sub-file or file to which he is denied access).YFor an illustration of circumstances which can allow attempts at violation, see  REF BK2128 \n  4.1.23. This cannot apply when the system is configured to hide from a user all knowledge of information to which the user does not have access permissions.Backup and Recovery Business and regulatory demands require that an ERMS be provided with comprehensive controls for regular backup of the records and metadata. It must also be able to recover records if any are lost because of, for example, system failure, accident or security breach. Regular automated backup and recovery can be provided by the ERMS, by integration with the services of an Electronic Document Management System ( HYPERLINK \l "Gl_EDMS" EDMS), by a database management system operating with the ERMS, or by some other software. In this section, references to the ERMS can mean any of these, as appropriate to the setting. In practice, backup and recovery functions may lie more with the organisations IT operations area than by being divided between ERMS administrative roles. RefRequirement Test The ERMS must provide or allow automated backup and recovery procedures that allow for regular backup of all or selected classes, files, records, metadata, administrative parameters, and the audit trail of the ERMS; and their recovery when needed. Y The ERMS must allow administrative roles to schedule backup routines by: specifying the frequency of backup; selecting classes, files or records to be backed up; allocating storage media, system or location for the backup (e.g. off line storage, separate system, remote site).Y The ERMS must allow only authorised administrative roles to restore from ERMS backups. Y When an ERMS restores from a backup, full integrity of the data including the audit trail must be maintained after the restore.PRecords which have been correctly disposed and are present in the backup should not be restored except in exceptional circumstances, Where the ERMS features checkpoints and database roll-forward facilities, the ERMS must allow only authorised administrative roles to roll it forward.PVital Records Vital records are the records that are considered absolutely essential to the organisations ability to carry out its business functions, in the short term, in the long term or both (see also the glossary). This can be either mission-critical in terms of its ability to cope with emergency/disaster conditions or to protect its long-term financial and legal interests. The identification and protection of such records is of great importance to any organisation and it is likely that it is these records that will need to be recovered first in the event of a disaster. Records may be considered as vital records either for the organisation as a whole or part of the organisation. RefRequirement Test The ERMS must allow administrative roles to indicate that selected files or records contain, or are considered to be, vital records.YThis indication should be included as a metadata element. The ERMS must provide two separate back-up operations: full backup, which backs up all (specified) ERMS data; vital backup, which backs up only the ERMS configuration and files and records identified as vital.YTwo back-up operations are used for the following reasons to allow: vital back-ups to be scheduled more often than full ERMS back-ups; vital back-ups to be taken onto different media and stored separately from (and possibly more securely than) full back-ups.It also provides for better managed ERMS restoration where restoring from vital back-ups can occur entirely independently of, and at a different time to, full restoration. As specified in section 4.3, backup can be performed either by the ERMS or by integration with some other software. After recovering from a vital back-up the ERMS must be fully operational.PAfter restoring from a vital back-up many files and records will not be present. Other than this, however, the ERMS must not be in any way limited in its operation or the functionality that it provides to users. The ERMS should provide for two methods of restoring from a full back-up: restoration to a clean environment, in which the data from the full back-up overwrites and replaces the ERMS during the recovery operation; restoration over an existing environment, in which the data from the full back-up is merged back into an existing ERMS environment.YThe first method of restoration will be common in organisations where vital back-ups are not taken. The second method of restoration will occur when an ERMS has previously been partially restored from a vital back-up and returned to normal operation; it then becomes necessary to merge in the full back-up without overwriting either the vital files and records that were previously restored or any new entities that have been added, or changes that have been made, to the ERMS in the interval since it was returned to full operation.If the ERMS supports two methods of restoring from a full back-up as outlined in  REF BK4375 \n  4.4.4, the  vital back-up (if it exists) will always be restored first. There is no need to consider the restoration of a  vital back-up over a  full back-up.When undertaking a two-part system restoration in this way it may be necessary for administrative roles to resolve manually any conflicts that arise. For example, the classification scheme may be altered in one back-up when compared to the other.  The ERMS must allow administrative roles to indicate that selected files or records are no longer considered vital. This action must be logged in the audit trail.YFor example a lease agreement or contract might expire and therefore no longer be considered vital.Retention and Disposition This chapter lists requirements for the use of retention and disposition schedules to govern the retention and eventual fate of records from ongoing operations. Retention and disposition schedules define how long the records have to be kept by the ERMS, and how they may be disposed of. Requirements for retention and disposition schedules are listed in section 5.1; a formal definition is in the glossary. The processes that can take place at the date specified by retention and disposition schedules are described in subsequent sections. Requirements for review processes are listed in section 5.2, and requirements for transfer, export and destruction are listed in section 5.3. As explained in section 2.2 under the heading Electronic File, Sub-File and Volume, records can be managed in classes, files, sub-files and volumes, as appropriate to the business requirement. According to circumstances, retention and disposition schedules apply to classes, files and/or sub-files and/or volumes. Retention and disposition schedules can also be applied to  HYPERLINK \l "Gl_RecordType" record types, for example to apply short retention periods to sensitive personal data, or to apply long retention periods to engineering drawings. The resolution of conflicts between retention and disposition schedules is also allowed for. MoReq2 includes the concept of disposal holds, which was not mentioned in the previous version of MoReq. Disposal holds are used in response to unexpected events to ensure that specified records are not destroyed. The common example is to ensure that records that are, or that may be, required as evidence in legal proceedings are not routinely destroyed as a result of a disposition decision. Retention and Disposition Schedules RefRequirement Test The ERMS must allow administrative roles, and only administrative roles, to create and maintain retention and disposition schedules. Y The ERMS must not limit the number of retention and disposition schedules.P The ERMS should be able to arrange retention and disposition schedules in a hierarchical structure resembling the structure of general and organisation-specific retention and disposition schedules authorised by appropriate mandates. NA hierarchical structure facilitates the management of numerous retention and disposition schedules. The ERMS must allocate a unique identifier to each retention and disposition schedule when it is created.Y The ERMS must allow a unique title to be entered for each retention and disposition schedule when it is created.Y The ERMS must maintain an unalterable history of changes and deletions (audit trail) that are made to retention and disposition schedules including the date of change or deletion, and user making the change.Y The ERMS must ensure that any amendment to a retention and disposition schedule is immediately applied to all entities to which the retention and disposition schedule is allocated.Y The ERMS must require an administrative role changing or deleting a retention and disposition schedule to enter a reason, and must store that reason in the audit trail.YChanges to, or deletions of, retention and disposition schedules must be controlled carefully to minimise the risk of records being destroyed inappropriately. The ERMS must be capable of importing and exporting retention and disposition schedules.P The ERMS must ensure that every class, file, sub-file and volume always has at least one retention and disposition schedule.YThis requirement is included to ensure that no entities are created without a retention and disposition schedule; and to improve usability. The retention and disposition schedules applied by default to every new class, file, sub-file or volume should be inherited from their parent.YWhere this is not possible (for classes at the top level of the classification scheme and if no inheritable retention and disposition schedule applies see  REF BK2988 \n  5.1.18) a default retention and disposition schedule should be applied.  Every record stored directly in a class must always have at least one retention and disposition schedule assigned to it.Y The retention and disposition schedules applied by default to any new record stored directly in a class (see section 3.2  REF BK4218 \n  3.2.17) must be inherited from its parent class.Y The ERMS must allow an administrative role to apply a retention and disposition schedule to any class, file, sub-file, volume or record type at any time. YThe phrase at any time means that an administrative role can replace a retention and disposition schedule or (if the system supports multiple retention and disposition schedules, see  REF BK2196 \n  5.1.16) apply an additional retention and disposition schedule to any class, file, sub-file, volume or record type. One example will be the replacement of a default retention and disposition schedule; another is the application of an additional retention and disposition schedule in response to a regulatory investigation. This may cause a conflict between retention and disposition schedules: see  REF BK2192 \n  5.1.23.  The ERMS should be able to apply a default retention and disposition schedule to record types.YThis implies that record types can exist with no applied retention and disposition schedule. This is acceptable, as each individual record will have at least one retention and disposition schedule applied to it, because each record is held in a file or class and requirement  REF BK2980 \n  5.1.10 mandates that at least one retention and disposition schedule is applied to each file and class. The ERMS must allow more than one retention and disposition schedule to be in force for any class, file, sub-file or volume.YThis is required to manage real-life scenarios, which involve retention requirements arising from a range of mandates and business needs. This is illustrated by one example, chosen from many possible. In this example, a file has a single retention and disposition schedule, assigned for business reasons, as the records within it are not expected to be subject to legal or regulatory retention requirements. The retention and disposition schedule applying to this file also applies to many other files. At some point, it becomes apparent that it may be necessary to retain the file for a longer period than the current retention and disposition schedule allows, due to a business issue related to a safety case. At this point, it seems that the contents of the file may become subject to a regulatory control related to safety regulations; so a second retention and disposition schedule is applied to the file, taking this into account. At a later time, it may become apparent that the safety issue did not exist; in that event the second retention and disposition schedule can be removed, leaving the original one in place and active. The retention and disposition of every record must be governed by the retention and disposition schedule(s) associated with the class, file, sub-file, volume and record type to which the record belongs; and by any applicable disposal hold(s) (see  REF BK2971 \n  5.1.34).YOnce a retention and disposition schedule is applied, it governs the retention and disposition of records associated with the entity to which it is applied (unless it is overridden by a different retention and disposition schedule). The ERMS must allow any retention and disposition schedule, and changes made to it, to be inherited down the hierarchy of the classification scheme, at the option of an administrative role.YWhether or not a retention and disposition schedule is inherited can be selected by an administrative role using any appropriate means. MoReq2 does not prescribe how this is achieved. Possibilities include: the option is selected when the retention and disposition schedule is created (in which case it applies whenever the retention and disposition schedule is applied); the option is selected whenever the retention and disposition schedule is applied (in which case it applies to all child entities); the option is selected when an entity is created for it to inherit the retention and disposition schedule(s) of its parent. Each retention and disposition schedule must include either: a retention period ( REF BK2190 \n  5.1.25) and a trigger event ( REF BK2190 \n  5.1.25); or a disposition date.Y Each retention and disposition schedule must include: a disposition action ( REF BK2191 \n  5.1.24); a reason.Y Each retention and disposition schedule should include a: a description; a mandate.YThe mandate specifies the justification for the retention and disposition schedule. This is often a reference to a law, regulation or corporate policy.  When the retention period applicable to some record(s) because of a retention and disposition schedule reaches its end, the ERMS must automatically initiate the processing of the disposition decision. YThis may mean that the decision is executed (subject to  REF BK2207 \n  5.2.4) or it may mean that action is required by an administrative role (see  REF BK2192 \n  5.1.23). Some organisations may prefer to implement the latter because of the risks involved with automatic execution.  When the ERMS is initiating a disposition decision (as in  REF BK2193 \n  5.1.22), if any other retention and disposition schedule applies with a different retention period end and/or with a different disposition decision then a conflict arises. It must be possible to configure the ERMS so that it automatically informs an administrative role if such a conflict arises, leaving the administrative role to resolve the conflict.YThe phrase must be possible to is included because it is not required that administrative roles intervene in all situations. It is acceptable for the ERMS to resolve a conflict automatically; but it must be possible to configure the ERMS to require administrative intervention in the event of conflict.A conflict can arise because some retention and disposition schedule(s) indicate that disposition is to be initiated while some other(s) indicate the opposite; and/or different retention and disposition schedules indicate different disposition decisions. In most cases it will be simple to determine which schedule will take precedence.These conflicts can arise in two scenarios: the conflicting schedules all apply to the entirety of an aggregation (such as a file); schedules apply to both an aggregation and to some records within it (because the latter apply to specified record types that occur within the aggregation).Administrative intervention may be required where it is not practical to define rules that correctly resolve these conflicts. For example: two retention and disposition schedules, derived from different legal mandates may specify different retention periods. Normally, the decision will be to retain the records until the end of the later of the two end dates; one retention and disposition schedule may specify a date by which certain records must be disposed of (typically because of data protection legislation). If this date is earlier than the retention date of a conflicting retention and disposition schedule, then the decision will depend on the relative weight of the two mandates and/or on business needs. These situations can arise when a document has a record type permitting the application and inheritance of a disposal rule to that record from the record type rather than from the aggregation in which it is contained. The administrative roles resolution may include any of the following: remove one or more of the conflicting schedules from the aggregation or records affected; change one or more of the conflicting schedules to remove a conflict; remove all the conflicting schedules and apply a new schedule; use the exceptional deletion features specified in section 9.3.All of these actions, if they are not carefully controlled, could raise concerns about good governance of the records. Therefore any of these actions changing retention and disposition schedules or deleting records must be the subject of written procedures. In some settings, further management controls such as the division of the tasks, will be appropriate.If the resolution results in some record(s) remaining in an aggregation that otherwise would not have been retained, the organisation may also need to have guidelines for their storage. This may include leaving the aggregation in place, or the relocation (see section 3.4) of the remaining record(s). The ERMS must allow at least the following disposition actions (as defined in  REF _Ref193708610 \r \h  5.1.20) for each retention and disposition schedule: retain permanently; present for review; destroy automatically; destroy after authorisation from an administrative role; transfer to an archive or another repository (see glossary).YThere are risks involved with implementing the destroy automatically option outlined in the above requirement; organisations will need to balance these risks against the benefits of automation. The ERMS must allow at least the following combinations of trigger events and retention periods (as defined in  REF BK2194 \n  5.1.19) to be specified: passage of a specified period of time after the class, file, sub-file or volume is opened; passage of a specified period of time after the class, file, sub-file or volume is closed; passage of a specified period of time since the most recent record has been classified to the class, file, sub-file or volume; passage of a specified period of time since a record has been retrieved from the class, file, sub-file or volume; passage of a specified period of time after a specified external event (which event is described in the schedule, and will be notified to the ERMS by an administrative role rather than being detected automatically by the ERMS) (for example, after contract signature or 100 years after date of birth); permanent to indicate long term preservation of the records.YWhile the above is generally inclusive, it is possible that some organisations will want to impose additional activating events and/or additional retention periods.Any number of external events can be linked to different retention and disposition schedules. The ERMS should not limit the length of retention periods.P The ERMS must support retention periods of time up to at least one hundred years for requirement  REF BK2191 \n  5.1.24.PThis maximum is suggested as an arbitrary period intended to avoid any practical limitation. While it is improbable that any ERMS will exist for one hundred years, a requirement of this nature will allow records to be transferred to future systems without the need to revise retention and disposition schedules.  The ERMS must be able to restrict the management of the disposition process to administrative roles. Y The ERMS must log in the audit trail and notify to an administrative role all automatic disposition actions.Y The ERMS must automatically notify an administrative role when any review action becomes due.Y The ERMS must allow an administrative role to delegate any notified review action to a reviewer role for action.Y The ERMS must allow an administrative role to amend any retention and disposition schedule (apart from its unique identifier, see  REF BK2951 \n  5.1.6). Y When an administrative role moves electronic files or records between classes of the classification scheme, the ERMS must offer the option to: allow the retention and disposition schedule of the destination class to replace the existing retention and disposition schedule(s); or enable an administrative role to select the appropriate retention and disposition schedule(s).YThis refers to moving records, as is permitted on an exception basis, in  REF BK4595 \n  9.3.3 and  REF BK3929 \n  9.3.4. On the rare occasions this functionality is used, administrative roles will need to take great care over the assigning or changing of retention and disposition schedules, especially for vital records. The ERMS must enable a disposal hold to be placed on a class, file, sub-file, or volume by an authorised user.Y A disposal hold must not prevent any retention period from running and completing,PHowever, see  REF _Ref193708770 \r \h  5.1.36. The ERMS must prevent any entity subject to a disposal hold, along with its contents (child entities) if they exist, from being deleted or being subject to any disposition decision.YDeletion is described in section 9.3. The ERMS must restrict the removal of a disposal hold to an authorised user.Y When an authorised user applies or removes a disposal hold, the ERMS must capture and store the following information about it, at a minimum in the audit trail and preferably as metadata:Ythe date the hold was applied or removed; the identity of the authorised user; the reason for the hold. The ERMS should allow an authorised user to apply several disposal holds, each specifying the same reason, to a group of classes, files, sub-files or volumes as a bulk operation.YThis requirement allows the authorised user to apply holds for the same reason to several classes, files, etc.  The ERMS should allow the lifting of multiple disposal holds (citing the same reason) simultaneously, as a bulk operation, by an authorised user.Y The ERMS should allow a class, file, sub-file or volume to be subject to multiple disposal holds simultaneously, either because they are applied to the entity, and/or because they are applied to a higher-level entity. In either event the restrictions on disposition and other functionality imposed by disposal holds must remain in place until the last disposal hold affecting the entity is lifted.Y The ERMS should allow an authorised user to search and report on all entities subject to a specified disposal hold.Y The ERMS should allow an authorised user to set, change, and delete a reminder that notifies the user of the existence of a specified disposal hold on a specified date.YReview of Disposition Actions In some environments, the retention and disposition schedules are used to govern disposition without a review. In others, retention and disposition schedules trigger a review of the specified disposition action on an aggregation that has reached the date or event specified in the schedule. The review may consider metadata, contents or both in deciding on the disposition action (a further retention period, transfer to another system, destruction or combination of these). The disposition of certain records is subject to laws and regulations. Reviews of disposition actions must be performed in a way which is consistent with these laws and regulations. Reviews must also take account of any appraisal policy and procedures set down for the organisation. Where appropriate, this must be done in co-operation with (and sometimes exclusively by) responsible archival authorities. Further discussion of these issues is beyond the scope of MoReq2. RefRequirement Test The ERMS should automatically notify an administrative role of all retention and disposition schedules which will come into force in a specified period of time.Y The ERMS must support the review process by presenting classes, files, sub-files and volumes to be reviewed, together with their metadata and retention and disposition schedule information.YIn practice, this implies features for navigating forward, back etc. within and between files, and from/to the metadata for files and records.  The ERMS must be able to maintain links between different  HYPERLINK \l "Gl_Rendition" renditions of the same records and enable disposition actions to be carried out on them simultaneously.Y The ERMS must allow the reviewer to take at least any of the following actions for each class, file, sub-file or volume during review: mark for destruction, immediately or at a future date (see section 5.3); mark for transfer (see section 5.3), immediately or at a future date; mark for a further review, immediately or at a future date; mark for indefinite retention.YThis may be achieved by the application of different retention and disposition schedules, or by other means. The ERMS must automatically log the date of a review. Y The ERMS must allow the reviewer to enter comments into the class, sub-file, volume, or files metadata to log the reasons for the review decisions. Y The ERMS must keep an unalterable history of all decisions taken by the reviewer during reviews, including reasons. YThe decisions should be stored as metadata and possibly also in the audit trail.  The ERMS should alert an administrative role if a conflict arises because a file that is due for destruction is referred to in a link from another file. It must pause the destruction process to allow the following remedial action to be taken: confirmation by the administrative role to proceed with or cancel the process; generation of a report detailing the files or record(s) concerned and all references or links for which it is a destination.Y Transfer, Export and Destruction Organisations may need to move records from their ERMS to other locations or systems for archival or other purposes. This is referred to here as transfer. Reasons for transfer may include: permanent preservation of the records for legal, administrative or research reasons; the use of devolved or external services for the medium term or long term management of the records. This action often results in the records being transferred to a different ERMS environment. The term transfer is used even though, initially, only a copy is sent to the other location or system. The records originally residing in the ERMS are retained and only destroyed upon verification that the transfer has been successful. The term export, on the other hand, refers to the process of producing a copy of complete aggregations, files and records for another system, while the records remain on the originating system the process does not delete them. In effect the transfer process takes place in two stages export of a copy with all associated metadata and audit trails, followed by destruction of the original. In each case, the requirement is to execute the transfer, export or destruction in a controlled manner. Decisions must be taken on the metadata and audit trails at the same time as actions are carried out on the records to which they relate. In this context destruction is different from deletion. Deletion of records under other circumstances is covered in section 9.3. RefRequirement Test If a formal MoReq2 XML schema has been published the ERMS must be able to export records in a form compliant with this schema.PSee also requirement  REF BK5006 \n  6.2.1 regarding the bulk import of records. Taken together these two requirements address the interoperability of MoReq2 compliant ERMSs.  Whenever an ERMS transfers or exports any record, it must transfer or export all its components and must preserve the correct relationships between them.P The ERMS must provide a well defined process to transfer records, together with their associated metadata and audit trail information, to another system or to another organisation.P The ERMS should be able to export records and their metadata in the form of a submission information package as defined by the OAIS standard (see appendix7).YSee the similar requirement for dissemination information packages at  REF BK4593 \n \* MERGEFORMAT  11.7.12. Whenever the ERMS transfers or exports any class, file, sub-file or volume, the transfer or export must include: (for classes) all files and records in the class; (for files) all volumes and sub-files in the file; all records in all these files, sub-files or volumes; all or selected metadata associated with all of the above; all or selected audit trails for all of the above. PAlthough the ERMS must be capable of exporting all metadata and audit trails, not all of these are always required by every target system. Whenever the ERMS exports or transfers any records with their metadata, it must include any implicit metadata in explicit form.PIn other words, all the metadata values that apply to any class, file, sub-file, volume or record must be shown explicitly, even if it has been stored only implicitly. See appendix 9.3 for examples. The ERMS must be able to do either or both of the following when exporting or transferring any set of records: export or transfer with the records the retention and disposition schedules applied to those records, in a manner which allows the schedules to be re-applied to the records in the destination system; print one or several reports showing the retention and disposition schedules to be applied to each set of records, and the characteristics of these schedules.P The ERMS must be able to do either or both of the following when exporting or transferring any set of records: export or transfer with the records the access controls for those records, in a manner which allows the controls to be re-applied to the records in the destination system; print one or several reports showing the access controls applicable to each set of records, and the characteristics of these controls.P The ERMS must be able to transfer or export a file or the contents of a class in one sequence of operations, such that: the content and structure of its electronic records are not changed; all components of an electronic record, (when the record consists of more than one component) are exported as one unit; all links between the record and its metadata and audit trails are retained; all links between classes, files, sub-files, volumes and records are retained so that they can be reconstituted in the receiving ERMS.P When the ERMS is transferring or exporting files and/or sub-files and/or volumes, if any of them include pointers to records stored in other files (see  REF BK2111 \n  3.4.24) then the ERMS must transfer or export the complete record, not a pointer.YThis is required so as to make sure that there are no difficulties of pointer resolution between the transferring or exporting system and the receiving system. The ERMS must be able to transfer and export records in the format in which they were captured.Y The ERMS must be able to transfer and export records in any format(s) into which records have been  HYPERLINK \l "Gl_Render" rendered.Y The ERMS must be able to migrate records marked for transfer or export into specified transfer format(s).PFor example, an approved XML or other open format. This requirement is to cover long retention periods where records must be automatically rendered into approved long-term preservation formats after a defined period of time without affecting the integrity and authenticity of the records. The ERMS must retain all aggregations, records and other information that are being transferred, at least until confirmation of a successful transfer process.YThis is a procedural safeguard, to ensure that records are not destroyed before successful transfer-in is reported from the recipient.See  REF BK2225 \n  9.2.30 and  REF BK4978 \n  9.2.31 for requirements regarding the reporting of any failure during the transfer process.  The ERMS must destroy aggregations, records and other information that are being transferred when it receives confirmation that the transfer process is successful, save for metadata that is retained as a  HYPERLINK \l "Gl_Stub" stub.YSee  REF BK2217 \n  5.3.19. The ERMS should be able to export the entire contents of a class of the classification scheme in one sequence of operations, ensuring that: the relative location of each file in the classification scheme is maintained, so that the file structure can be reconstructed; sufficient metadata to rebuild the whole parent class branch is retained and moved with the contents of the class.P The ERMS should provide the ability to add user-defined metadata elements required for archival management purposes to electronic files selected for transfer.Y The ERMS must ensure that, when a record marked for destruction is destroyed, all its renditions are destroyed.YWhere the same record appears in more than one file ( REF BK2111 \n  3.4.24 in section 3.4) then the record and its renditions should be removed from the file when it is destroyed but should not be finally deleted until all occurrences of the record have been destroyed. The ERMS must have the ability to retain a  HYPERLINK \l "Gl_MetadataStub" metadata stub for: classes; files; sub-files; volumes; records stored directly in a class; which have been destroyed or transferred.YIn some environments it is desirable to retain information about records which have been destroyed. The metadata in question should include at least the date of acquisition and all the metadata relevant to identify uniquely each record and its relations to the classification scheme. See the MoReq2 metadata model.This is so that the organisation can still know what records it has held and the dates they were destroyed or disposed of, without incurring the overhead of keeping all the detailed metadata for files and records. The metadata stub (see  REF BK2217 \n  5.3.19) must include at least the following: date destroyed or transferred; fully qualified classification code; title; description; user responsible for destruction or transfer; reason for destruction or transfer (this can be a reference to a retention and destruction schedule or a manually-entered reason); any reference given by the system to which the records have been transferred, to facilitate the retrieval of transferred records.Y The ERMS must allow an administrative role to specify a subset of additional metadata elements which will be retained as metadata stubs.Y The ERMS must be able to export metadata stubs when records are exported.YThis is required to allow migration between ERMSs. The ERMS must allow information to be exported more than once.Y Whenever the ERMS exports or transfers information, it should be able to produce on request a report listing the records exported or transferred according to their security categories.Y Capturing and Declaring Records Overview This chapter covers requirements relating to the process of capturing records into an ERMS. The first section (6.1) covers the standard capture process. The following section (6.2) covers the  HYPERLINK \l "Gl_BulkImporting" bulk import of records from other systems and this is followed by a section devoted to e-mail because of its particular importance (6.3). Section 6.4 concerns record types and section 6.5 covers integration with scanning and imaging systems. Terminology The term capture is used with its natural English language sense, in an information management/ information technology context. Here,  capturing information means saving it in a computer system. This is consistent with the archival meaning of  capture , ( the act of recording or saving a particular instantiation of a  HYPERLINK \l "Gl_Digital" digital object) given in the InterPARES 2 Project Terminology Database. It follows that ERMSs can capture a variety of information. An ERMS can capture records, metadata, and in some cases documents, among others. The fact that an ERMS can (in some cases) capture documents as well as records suggests that the term capture is imprecise, because capturing a record involves more processes than capturing a document that is not a record. For example, capturing a record includes the processes of classification,  HYPERLINK \l "Gl_Registration" registration, and locking against change whereas this is not necessarily the case for documents. Hence the term declare is sometimes used synonymously with capture in the case of records. However, declare can also apply to a document that starts outside the ERMS, or to a document that has already been captured by the ERMS. This lack of precision should have no negative impact on the clarity of MoReq2. More formal definitions are given in the glossary in section 13.1. Capture  HYPERLINK \l "Gl_ElectronicDocument" Electronic documents that are made or received in the course of business processes originate from both internal and external sources. The electronic documents will be in various formats, be produced by different authors and may be received either as single documents or as documents comprising several components (see glossary for the MoReq2 definition of component). Some records are created within the organisation, in the course of its business processes. Others are received through various communication channels, for instance electronic mail, facsimile, letter post (optionally to be scanned), by hand, and at variable arrival rates and volumes. A flexible capture system with good management controls is required to capture documents so that their diverse requirements are addressed. RefRequirement Test The ERMS capture process must provide the controls and functionality to allow users to: capture electronic records regardless of  HYPERLINK \l "Gl_FileFormat" file format, method of encoding or other technological characteristics, with no alteration of their content; ensure that the records are associated with a classification scheme; ensure that the records are associated with one or more file(s) or class(es).PFile format is defined in the glossary. The requirement is to be able to capture any file format.The requirement to capture records in any file format is not intended to be testable, and it does not imply that the ERMS needs to be able to make presentations (see glossary) of all possible formats. MoReq2 therefore does not list the kinds of formats that may be captured, as formats vary over time with the evolution of software. However, for the avoidance of doubt, the kinds of records to be included can be diverse; they might include, for example, the following kinds of records frequently used in office settings: output from desktop applications such as office suites; e-mails (see section 6.3); audio; databases; portable document formats; scanned images; video; web pages.In some situations, the ERMS may also need to capture other kinds of record such as:blogs compressed files (sometimes referred to as archives, applying an IT meaning of the term); electronic calendars; electronic forms; geographical information system data; information from other computer applications e.g., accounting, payroll, computer aided design; instant messaging systems; multimedia documents; records of web-based transactions; records which include links to other records; software source code and project documentation; structured data (e.g. EDI transactions); webcasts; wikis.These lists are not complete. The ERMS must not impose any practical limit on the number of records which can be captured in any class, file, sub-file or volume, nor on the number of records which can be stored in the ERMS.PLarge numbers of records in volumes etc. will tend to make the system difficult to use in some settings, and so is not generally advisable. This requirement is intended to allow for situations in which large numbers are unavoidable, such as some transactional environments. When capturing a record made up of several components, the ERMS must capture all of its components.P When capturing an electronic record that has more than one component, the ERMS must allow the record to be managed as a single unit, retaining the relationship between the components, and retaining the records structural integrity.PExamples of such records are: web pages with embedded graphics; a word-processed document linked to a spreadsheet.In some cases, the components will be related by links that do not work if simply copied into the ERMS repository. For example, many web pages contain links to graphics and other objects with addresses (URLs) that are external to the repository; and linked spreadsheets typically contain links to addresses (operating system filenames) external to the repository. See next requirement. When capturing an electronic record that has more than one component the ERMS should modify the record, if necessary, to preserve the ability to present it. This is likely to mean that the ERMS changes the internal references (links) within some of the components.PThis requirement applies only to file formats specified for the ERMS it is not intended to apply to unspecified formats. Examples may include: HTML pages that include links to graphics and other objects; spreadsheets that include links to other spreadsheets.Making such changes is contrary to the general principle of not changing the content of records, but is unavoidable if records that include components etc. are to be stored in their original formats without losing all functionality and fidelity. The changes will generally be acceptable so long as the changes are logged in the ERMS audit trail (see next requirement). An alternative approach involves rendering the record into some other file format (such as  HYPERLINK \l "Gl_PDFA" PDF/A) that preserves the static appearance; see requirement  REF BK4026 \n  11.7.8; however, even though this avoids changing links, it is likely to result in losing them. When the ERMS changes references within records during capture, it must log automatically all details of the changes made in its audit trail.Y The ERMS must automatically capture the file format (see glossary), including the  HYPERLINK \l "Gl_Version" version, of each component when it is captured and must store it in the metadata of the component.PThis is required to support the digital preservation of records their accessibility over time. See section 11.7.Some information about file format is usually implicit in the components filename extension, e.g. .htm or .pdf; and on occasion it is ambiguous, e.g. .doc can specify several unrelated formats. However, the extension alone frequently does not indicate the file format version and sometimes not even the file format itself. This will be acceptable in many cases, though it may not suffice in cases where long-term preservation is needed, or where precision is needed (for example, precision of colour space). File formats are numerous and are subject to frequent change. It therefore is not realistic to expect an ERMS to capture information for all file formats. It is therefore acceptable for the ERMS to: specify a list of file formats that can be recognised; rely on reference to an established file format registry preferably one designed specifically to support digital preservation. In either case, the using organisation needs to satisfy itself that the range of file formats included is sufficient for its preservation requirements. The ERMS record capture process must validate the values of metadata entered into the ERMS when records are being captured, at a minimum according to the rules in the MoReq2 metadata model.YSee also  REF BK2236 \n  6.1.34 in this section. The ERMS should support validation of metadata elements using check digit algorithms.YFor example, files may be identified by a sixteen-digit credit card number, of which the last digit is a check digit computed from the other fifteen digits using the mod 10 algorithm.Provision of an application program interface for this feature, allowing organisations to introduce their chosen algorithm, should normally be considered acceptable. The ERMS must allow users to capture an electronic record even if the application used to produce the record is not present.YFor example a user may receive a project plan and a CAD/CAM drawing as attachments in an e-mail. If the user does not have access to the project plan or CAD/CAM applications, then the user may not be able to view the attachments. Despite this, the user should be able to capture the attachments as records in the ERMS. The ERMS may provide viewer software that allows the user to view these records; this is not required by MoReq2. The ERMS must be able to capture metadata about records consistent with the MoReq2 metadata model. Y The ERMS should be able to capture automatically values from fields defined by an administrative role within the specified document types, using these values automatically to populate metadata elements as specified in the MoReq2 metadata model. YThe functionality needed for this requirement applies only to specific kinds of electronic objects, for example letters produced using a specified template and a specified word processor.Many documents including some office documents and . HYPERLINK \l "Gl_PDF" PDF files include user-configurable metadata elements. It should be possible to configure the ERMS to capture automatically the values of these elements and retain them with the record. The ERMS must allow the capture of all metadata elements specified at system configuration, and must retain them with the electronic record in a persistently-linked relationship at all times. Y The ERMS should allow users who wish to capture a record but who are unable to provide all the mandatory metadata values for it to store it temporarily in the ERMS.YIn other words, the ERMS should provide a means of storing records without all their metadata, that is without completing the normal capture process. This implies exception reporting and progress monitoring; it does not imply any requirement to treat such records as normal records for the purpose of export, transfer, rendition etc. MoReq2 does not specify how this is achieved.Only the editable metadata values can be changed at a later stage, and fixed metadata (e.g. e-mail transmission data) must remain unchanged. The ERMS must ensure that the values of some elements of the metadata of the electronic record can only be updated by authorised users and administrative roles, consistent with the rules in chapter 12.Y The ERMS must ensure that all records are assigned to at least one class, file (or its sub-file if appropriate), as appropriate, when captured.Y The ERMS should support automated assistance in capturing electronic documents, by automatically extracting as much metadata as possible, for as many kinds of document as possible.NThe rationales for this requirement are to: minimise the amount of data entry performed by users (experience shows that in many environments, a requirement to enter metadata can cause users to reject the system); increase the accuracy of metadata. The metadata elements involved, and the kinds of documents for which this is possible, will depend on the environment. Some guidance is given in the metadata model. The ERMS must support automated assistance in the capture of outgoing and internal documents (e.g. memoranda or word-processed letters in a specified layout and file format) as records, by automatically extracting the following metadata from them: document date (as in the body of the document); recipient(s); any copy recipient(s); subject line (title); author(s); internal reference (typically shown as our reference); to the extent that these are present. YMoReq2 does not specify the software or formats for office documents or e-mail. The metadata extraction may be achieved by locating metadata within the record, by using a template to identify the metadata and populate a blank document, or by any other means. The ERMS must log the capture date and time of a record both as metadata and in the audit trail. YIf the date and time are part of the unique identifier of the record, and as long as they can be explicitly extracted from this identifier, it is not necessary to store the date and time separately.MoReq2 does not specify the accuracy of the time needed. Most ERMSs record time to an accuracy of one second or better.Some legislative frameworks call for time stamping to be performed against a certified device or authority. Where this is the case it should be accommodated in a chapter zero. For every captured record, the ERMS must be able to present on-screen the metadata, including that specified at configuration time. YThe metadata specified at configuration time may consist of any or all elements from the relevant section of chapter 12. The ERMS must ensure that all mandatory metadata is present for every captured record. Y During capture of a record the ERMS must prompt the user to enter any required metadata that has not automatically been captured.Y The ERMS must support the assignment of multiple keywords (or key terms) to each class, file, sub-file and record.YMoReq2 does not require the ability to assign keywords to volumes. The ERMS should allow an administrative role to configure whether keywords are mandatory or optional, at configuration time, for each of classes, files and sub-files.Y The ERMS must allow more than one entity (class, file, etc.) to be created using the same combination of keywords.Y The ERMS should allow a user creating an entity to populate its keyword values by copying them all from another entity, in one action.Y The ERMS should allow a user to enter the identifier of one or more languages for any record.Y The ERMS must provide a capability for the keyword values and other metadata element values to be picked from, or validated against, controlled vocabularies (or lists of permitted terms).YFor example, by means of a pick list or thesaurus. See also requirement  REF BK2813 \n  11.8.11. The ERMS must allow entry of further descriptive and other metadata at the time of capture and/or at a later stage of processing. Y The ERMS must warn the user if an attempt is made to capture an object with a title which already exists in the same entity or to re-title an object with a title which already exists in the same entity.YSee also  REF BK4087 \n  11.8.6.  The ERMS must be able to reserve the ability to amend the title of an electronic record for an administrative role or other authorised user.YThis facility can be used or not used, at the option of the organisation. When a user is capturing a document that has more than one version, the ERMS must allow the user to choose at least one of the following: declare all versions as one record; declare one specified version as a record; declare each version as an individual record.Y The ERMS should be able to provide automated support for decisions on the classification of electronic records by means of at least one of the following: making only a subset of a classification scheme accessible to a user or role; suggesting the classes or files used most recently by that user; suggesting the classes or files used most frequently by that user; suggesting classes or files by inferences drawn from record metadata elements (for example, significant words used in the title or e-mail subject line); suggesting classes or files by inferences drawn from the record contents.P The ERMS should allow the process of capturing a record to be completed by a more than one user. YThe ERMS should allow the capture process to be divided between users; typically this will mean that one user enters some metadata then passes the electronic record to another user, who enters the remaining metadata and classifies the record. The ERMS should provide simple workflow facilities to enable simple routing for checking and approving a document before capture, logging the decisions taken, who took them, and allowing a reason to be entered by each.YNote that this requires only basic workflow features. It intentionally stops short of the full workflow features described in chapter 10. The ERMS should provide an application programming interface to receive and capture in real time individual records and transactions provided by another application or system.NAs mentioned in section 1.4, ERM functionality may be required as part of a wider system This may require the ERMS to receive records from another system, for example, a corporate business application such as Customer Relationship Management (CRM) or a line of business application, via an Application Programming Interface (API) to enable the ERMS to capture individual records. Where possible, the ERMS should issue a warning if a user attempts to capture an e-mail record which has already been captured into the same file or (if classified directly into a class) the same class.YMoReq2 does not define how the e-mail is identified; however, the internet message ID may be suitable.There are several cases in which this is not logically possible, for example where the e-mail record has been captured into a file to which the user is denied access. Where possible, the ERMS should issue a warning if a user attempts to capture a record (other than an e-mail, as this is dealt with by  REF BK2889 \n  6.1.37) that has the same content as another record which has already been registered in the same file or (if classified directly into a class) the same class.Y Where possible, the ERMS should issue a warning if a user attempts to capture a record (other than an e-mail, as this is dealt with by  REF BK2889 \n  6.1.37) that has the same values of identifying metadata as another record which has already been registered in the same file or (if classified directly into a class) the same class. YThe identifying metadata for this requirement is: Title; Date; Author; Addressee. Where possible and appropriate, the ERMS should be able to provide a warning if an attempt is made to capture a record which is incomplete or inconsistent in a way which will compromise its future apparent reliability. NFor example, a purchase order without a valid electronic signature or an invoice from an unrecognised supplier. The ERMS must allow an administrative role (not user roles) to add a record to a previously-closed volume, provided that the date of the record is not later than the date of closure. When this takes place: the ERMS must require that an administrative role adds a reason to the metadata of both the volume and the record, to explain why this exception has taken place; the ERMS must automatically log this in the audit trail. This action must not update the date of closure stored in the metadata.YThis facility is intended to be used to rectify user error, e.g. if a volume was closed unintentionally. For this reason, it is important that the exception causing this action is properly documented.MoReq2 does not mandate how this is achieved. It may be achieved by temporarily re-opening the closed volume, or by other means.Bulk Importing Records may reach the ERMS in bulk in a number of ways. For example: a bulk transfer from a compatible EDMS; a bulk transfer from a compatible ERMS; as a single compatible data file containing a series of records of the same type (e.g. daily invoices); from a compatible scanning or imaging system; records from a hierarchy of operating system folders. The ERMS needs to be able to accept these, and must include features to manage the capture process and maintain the content and structure of the imported records. During bulk import the ERMS needs to capture the same information as the normal capture process namely the records themselves and their metadata. It also needs to classify the records extending the classification scheme if necessary (see  REF BK2677 \n  3.1.12)  and possibly capturing audit trail information. Finally, bulk import needs to allow for the processing of exceptions and errors. At the time of writing, the development of an XML schema for MoReq2 is planned. This schema is expected to implement the MoReq2 metadata model, and to provide an ideal protocol for the bulk import of electronic records from a MoReq2-compliant ERMS. RefRequirement Test If a formal MoReq2 XML schema has been published, the ERMS must be able to perform a bulk import of records in a form compliant with this schema.PSee also requirement  REF BK4695 \n  5.3.1 regarding the export of records. Taken together these two requirements address the interoperability of MoReq2 compliant systems.  The ERMS must provide the ability to capture transactional records generated by other systems. This must include: supporting predefined batch file transaction imports; providing editable rules to customise the automatic capture of the records; validation to maintain data integrity.PMoReq2 does not specify how this ability is provided. The ERMS must be able to capture automatically the metadata associated with records during a bulk import (allowing for manual input of missing or incorrect metadata).P Where the ERMS captures the metadata of some record(s) during import, it must validate it using the same rules as would be used for the manual capture of the records(s). Where this validation process finds errors (such as absence of mandatory metadata, or format errors) it must bring these to the attention of the user performing the importation, in all cases identifying the metadata involved, and logging errors and actions in the audit trail.YIn ideal cases, the record(s) being imported will have metadata that complies fully with the metadata model. In other cases, the metadata may be non-compliant. In these cases, several outcomes are possible; MoReq2 does not mandate any one outcome. Possible outcomes include: The entire importation is cancelled; Importation of the record that has non-compliant metadata is cancelled; The user is required to choose between correcting the error and cancelling importation of the affected class; The data is imported as a temporary incomplete record (this resembles the requirement that capture can be divided between users, see  REF BK2236 \n  6.1.34). The ERMS must be able to import audit trail records that show the history of the imported record(s).Y The ERMS must not import audit trail records into its audit trail; it must store imported audit trail records separately.YThe imported audit trail records must be maintained separately so as to avoid producing a mechanism that allows administrative roles to change or compromise the integrity of the audit trail. MoReq2 does not specify how this is achieved; it may involve storing the imported audit trail as a record alongside the imported records, or as a separate entity recognised as an audit trail imported from another system. The ERMS must provide facilities to manage input queues.YFacilities such as the following are expected: view the queues; pause any or all queues; re-start any or all queues; delete a queue. The ERMS must enable an administrative role to (optionally) set the ERMS to close classes, files and volumes automatically after they have been imported.YFor example, on the merger of two organisations it may be necessary to close down branches of the structure so that records can no longer be added to them.e-Mail Management Definitions As a verb, e-mail refers to a mechanism for transmitting messages between agents (in this context, the term agent has a precise technical meaning; more detail is not required for an understanding of MoReq2). The standard protocol used for e-mailing is defined by the Network Working Group documents RFC 2821 and RFC 2822 (see appendix 7). MoReq2 uses RFC 2821/RFC 2822 as the basis of its working definition of e-mail. As a noun, e-mail is usually used to refer to a document that contains the complete data of a single e-mail transmission. However, although RFC 2822 defines the syntax for e-mail transmissions, there are no standards that define the data format that should be used when e-mail transmissions are captured as documents. In other words, even though e-mail applications from different suppliers can freely transmit messages (because they observe the e-mail protocols defined in RFC 2821/ RFC 2822) it is not possible to capture an e-mail from one application as a document and be sure that another e-mail application will be able to read it back. Each e-mail supplier uses its own proprietary format(s) for capturing e-mail. For this reason, accurate automated extraction of metadata from messages cannot be guaranteed. Use and issues e-Mail is used for sending documents (in the form of messages and as attachments) within and between organisations. The characteristics of e-mail management software (in particular the lack of standardisation for formats explained above), combined with user attitudes towards e-mail, can make it difficult to apply records management functionality to e-mail. Organisations need to be able to enforce procedures and management controls to: capture all inbound and outbound e-mails and attachments; and/or to: capture e-mails and attachments according to pre-defined rules; and/or to: provide users with the capability of capturing selected e-mails and attachments In some countries the legal ownership of e-mail is unclear, and in some situations automatic capture of e-mails into an ERMS may be inappropriate. Where this is the case, the latter two options should be considered during configuration. Furthermore, e-mail has become the default means of communication for many organisations and an important one for others. In some organisations, much e-mail traffic is ephemeral. Each organisation needs to decide which of the above alternatives represents the most appropriate compromise for its situation: The first option results in the capture of any ephemeral e-mails as well as those that are meaningful records; The second option relies on successfully configuring appropriate rules and filters; The third option requires the users to assess the relevance and importance of items and there is a risk that they will not all do so reliably. MoReq2 allows for ERMS support for all three approaches. The procedures and management controls are beyond the scope of MoReq2. RefRequirement Test Whenever an e-mail is captured, the ERMS must by default capture it in a format that retains its header information.Y The ERMS must support the capture of e-mails in an integrated way, such that the capture can be performed by a user from within the e-mail application, without the user needing to switch to the ERMS.YClose integration is essential for effective use of an ERMS. For example the user should be able to drag and drop from the e-mail client into the ERMS, choose a capture command from within the e-mail client or the e-mail client should indicate which e-mails have been captured into the ERMS. The essence of this requirement is that the user must not have to switch to the ERMS application to capture e-mails.MoReq2 also permits, but does not require, the capture of e-mails in other, less closely integrated, ways. It must be possible to configure the ERMS at configuration time so that it operates in one of the following ways when a user sends an e-mail: it automatically captures the e-mail; it determines whether to capture the e-mail according to pre-defined rules; it automatically prompts the user, giving the user an option to capture the e-mail; it takes no action (and thus relies on the user to initiate a capture if appropriate).YRegardless of which way is chosen, it is acceptable for the ERMS to require the user to classify records manually and enter some metadata manually.  It must be possible to configure the ERMS at configuration time so that it operates in one of the following ways when an ERMS user receives an e-mail: it automatically captures the message, unless it has already been captured; it determines whether to capture the e-mail according to pre-defined rules; if the e-mail has not already been captured it automatically prompts the user, giving the user an option to capture it; it takes no action (and thus relies on the user to initiate a capture if appropriate).YRegardless of which way is chosen, it is acceptable for the ERMS to require the user to classify the record manually and enter metadata manually.  The ERMS must support automated assistance in the capture of outgoing and incoming e-mails, with and without attachments, as records, by automatically extracting the following metadata from them: e-mail date sent (and in some settings, time); recipient(s); any copy recipient(s); subject line (title); sender; embedded electronic signature; certification service provider; to the extent that these are present.PThis requirement specifies the capture of sender for e-mail messages. This is not always the same as the author, for example when a secretary sends a message on behalf of an executive. The capture of sender is specified here as a conscious compromise, it being impossible to reliably capture the author automatically. Organisations should consider the need for manual procedures to ensure the correctness of the author metadata. Appendix 9 provides guidance on the interpretation of e-mail metadata.  Users should be able to capture an e-mail record to a sub-file, file or class by dragging it from an e-mail client (technically, a Mail User Agent) to a specified sub-file, file or class in the ERMS.YThe sub-file, file or class can be represented in the e-mail client window or in a separate window. The ERMS must allow a user to choose how to capture an e-mail message with attachment(s) as: the e-mail message only, without attachment(s); the e-mail with its attachment(s), as one record made of linked components; the attachment(s) only, each or any as individual records.YThis applies to sent and received messages.The last of these three options results in attachment(s) being captured without the context of the e-mail with which they were transmitted. Where an e-mail and its attachment(s) are captured at the same time but as separate records, the resultant records should be linked automatically by the ERMS.YThe ERMS should allow a user to navigate the cross-reference link between the records so as to discover each of the attachment records from the e-mail record and the e-mail record from any of the attachment records. Whenever an attachment is captured as a separate record, the ERMS must require appropriate record metadata values to be captured and/or entered for it.Y When capturing an e-mail message, the ERMS must by default populate the Title metadata with the subject field of the message.YAppendix 9 provides guidance on the interpretation of e-mail metadata. The ERMS must allow a user who is capturing an e-mail message to edit the record title.YThis is intended to allow users to correct inappropriate or to clarify imprecise e-mail titles, or to make the titles more meaningful.The e-mail title is separate from the subject line (title) of the e-mail; the latter will remain as part of the message regardless of the content of the e-mail title. If a user captures an e-mail delivery status notification report (where these are supported) for an e-mail which has been captured as a record, the ERMS should be able to link the two automatically.YExamples of delivery status notifications are non-delivery reports and delivery confirmations. The link should allow a user to navigate between the records so as to discover each of the notifications from the e-mail record and the e-mail record from any of the notifications.  The ERMS must enable the automatic capturing of metadata belonging to e-mails and their attachments as outlined in the MoReq2 metadata model.Y The ERMS must allow date sent and date received metadata to be entered manually.YThis is to allow for situations in which the dates held in the e-mail message are not appropriate for the business setting (see introduction to this section for explanation of how this may occur). A configuration option to disable this facility will be acceptable. A user must be able to capture into the ERMS, in a single operation, several manually-selected e-mails as: one record; or as a set of records, one per e-mail; at the users option.Y The ERMS should be able to identify automatically and capture all the e-mails related to an e-mail specified by a user, in a single operation, capturing them as: one record; or as a set of records, one per e-mail; at the users option.YRFC 2822 Section 3.6.4. Identification fields describes how the optional SMTP header fields References: and In-Reply-To: can be used in conjunction with the Message-ID: field to identify related e-mail messages, sometimes referred to as the thread of the discussion. The ERMS must allow a user who is capturing an e-mail message in a proprietary format to save it in multiple, including open, formatsYIt may be useful for an ERMS to enforce e-mail saving criteria based on the retention and disposition schedule. The e-mail contents of files with a short retention period could be stored in a proprietary format, but those with longer schedules could be saved into an open format.  Whenever address fields captured from an e-mail header appear in the metadata of an e-mail record, the ERMS must ensure that it captures the optional display name (if present) of any mailbox listed as well as the address-spec address; for example, Jan Schmidt rather than js97@xyz.int.YRecord Types Record Type describes characteristics of records that are not (and usually cannot be) defined in the classification scheme. This can include specific: metadata attributes; retention requirements; access controls; kind of document (e.g. contract, CV, disciplinary report). A records record type usually corresponds to the document type of the document from which the record was made. RefRequirement Test The ERMS must support the definition and maintenance of record types.Y All records in the ERMS must have exactly one record type.Y The ERMS must restrict the definition and maintenance of record types to an administrative role.Y The ERMS must allow an administrative role to restrict the creation of records of specified record types to specified groups of users, based on their business needs.Y The ERMS must allow an administrative role to define one record type as the default record type, which can be used by all users who are allowed to capture records.YScanning and Imaging When planning for the implementation of an ERMS,  HYPERLINK \l "Gl_PhysicalRecord" physical records in the form of paper or microform often need to be considered. There are two main issues: existing records that are held on paper or microform and may need to be referred to in conjunction with electronic records; documents on paper that continue to be received or created by the organisation, but which the organisation wishes to hold as electronic records in the ERMS. This section deals with the scanning (imaging) of paper-based and microform documents, so that they can be captured into the ERMS as electronic records. It includes several requirements that address details of the scanning process. Scanning can be organised in the following ways: centralised; local or workgroup; outsourced or subcontracted; or in any combination. These ways are described briefly below. Centralised scanning is most appropriate for high-volume capture, typically using fast scanning equipment specifically designed for bulk input, together with specialist scanner operators. Local or workgroup scanning takes place close to the receiving users and is appropriate for low-volume activity, where the person doing the scanning needs a knowledge of the business, or when dictated by the geographic distribution of the organisation. This typically uses scanners with lower capacity and speed; these are sometimes multi-functional devices. Outsourced or subcontracted scanning this can be considered for a number of reasons related to cost-effectiveness: where there is a large amount of scanning to be done as a one-off exercise; where sufficient human resources are not readily available in the organisation; where sufficient accommodation and/or equipment are not readily available in the organisation; where the scanning and/or storage are not site-dependent. The rest of this section sets out key requirements to be considered in provision of an integrated ERMS and scanning solution. The requirements apply only where scanning facilities are part of the ERMS. Many of the requirements can also be interpreted for use when scanning is outsourced. RefRequirement Test The ERMS must be capable of integration with at least one scanning solution.YThe scanning solution provides the interface with the scanning equipment and allows the operator to perform several processes related to scanning such as rotating and despeckling. The ERMS scanning feature should support both monochrome and colour scanning.YMany applications do not require colour scanning. The ERMS scanning feature must be capable of saving images in standard formats, including, but not limited to: TIFF (see TIFF 6.0 Specification); JPEG (see ISO 15444, required only if colour is supported); PDF/A (see ISO 19005).Y The ERMS scanning feature must be capable of saving images at different resolutions.YIdeally the scanning feature should provide a menu of options, programmable for the input of different types of document. The ERMS scanning feature should be capable of saving images in colour or greyscale and at different resolutions.Y The ERMS scanning feature must be capable of handling standard paper sizes, including, but not limited to: A4; A3. YSee ISO 216 for the definition of A4 and A3. The ERMS scanning feature should have Optical Character Recognition (OCR) functionality.YOCR functionality produces text from a scanned image. Some kinds of OCR are sometimes referred to as Intelligent Character Recognitions, or ICR. For simplicity, MoReq2 refers to both as OCR. Where the ERMS includes OCR functionality the ERMS should be capable of managing the scanned image and the text resulting from the OCR as a single record.YIn other words, the OCR text should be regarded as metadata of the record rather than as a record in its own right.MoReq2 does not require that users be able to view the OCR text, as its purpose is to allow full text searching (see next requirement). Where the ERMS includes OCR functionality it should support full text searching based on the text.Y The ERMS scanning feature should be capable of recognising and capturing individual documents in a bulk scanning process.YMoReq2 does not specify how this should be done. Common solutions rely on the recognition of patch codes, patch sheets, barcodes or blank sheet inserts. The ERMS scanning feature must be capable of automatically sending scanned images to a queue after scanning.YFor example, indexing, quality assurance. The ERMS should include a facility for the inspection of the scanned images.YThis includes the ability to accept or reject images; and, when they are rejected, to request a re-scan. The inspection may be carried out by a scanner operator, by a dedicated quality check user, or by other users who perform quality checking only as a part of their work The ERMS scanning feature should allow an administrative role to set a threshold for image information content such that below the threshold an image is discarded as representing a blank page.Y The ERMS scanning feature should be able to store scanner set-up parameters (such as single/double sided, resolution, contrast, brightness) for different document types.Y The ERMS should allow users to annotate images.YThis feature can be used to note exceptional scanning problems, or to make notes (much as handwritten annotations are sometimes used with paper documentation). If the ERMS allows users to annotate images that are held as records, it must prevent the alteration and removal of these annotations.YThis is required for records only; it is not required for other images. It is intended to prevent records from being modified (or from appearing to be modified) temporarily. If the ERMS allows users to annotate images that are held as records, it must store with each annotation the identity of the user making the annotation and the time and date, in an unalterable wayYThis is required for records only; it is not required for other images. It is intended to ensure that any annotations are appropriate and traceable. The ERMS scanning feature should log each scanning session with the following details: user login; workstation identifier; time and duration; session identifier; batch identifier(s); number of documents (if applicable); number of images scanned; number of images after removal of blank pages (if blank pages are removed automatically).Y The ERMS scanning feature should be able automatically to capture relevant metadata when scanning zoned forms.YA zoned form is one which includes areas defined in the scanning software as containing data to be scanned. The information outside the defined zones is not scanned, thus reducing image size and reducing storage and bandwidth requirements. Where the ERMS scanning feature includes automatic capture of metadata it should be able to interpret this information for automated classification.YThis feature is especially useful in casework environments, where paper records frequently bear case identifiers that contain sufficient information to classify the record see section 10.5. The ERMS should be capable of the bulk import of scanned images and their metadata.YSee section 6.2 for further requirements regarding bulk import. The ERMS should be able to display thumbnails of scanned images as an aid to navigation and searching.Y The ERMS must allow users to capture scanned images as records.YReferencing This chapter brings together requirements for referencing the entities (classes, files, sub-files, volumes and records) within a classification scheme, Section 7.1 lists requirements for Classification Codes and those for System Identifiers are listed in section 7.2. All of the entities stored in the ERMS repositories (classes, files, sub-files, volumes, records etc.) need identifiers. These identifiers are needed to: Allow the software to process the entities; Allow users to retrieve, refer to, and use, the entities. MoReq2 uses the following terminology to describe these identifiers: An identifier required for software usage is called System Identifier. This can be used by users as well as by software in some cases; A hierarchical identifier applied to entities in the classification scheme hierarchy and intended for users is called Classification Code; Other Identifiers are named as needed, for instance Retention and Disposition Schedule Identifier. The difference between System Identifiers and Classification Codes is illustrated in the following three diagrams. These diagrams are also referred to later in the chapter. Figure 7.1 shows a part of a fictitious, but realistic classification scheme. It shows some of the classes; each class has a class title (as required by  REF BK2665 \n  3.2.4).  SHAPE \* MERGEFORMAT  Figure 7.1 Each class is allocated a System Identifier, as shown in figure 7.2.  Figure 7.2 Note that the System Identifiers shown here are short and simple, purely for illustration. In reality they are likely to be longer and more complicated in structure. By way of illustration, an example of a System Identifier based on the Globally Unique Identifier algorithm is 0c7220e3-5646-44c4-82b0-67832c1efa1c. Classes are also allocated a Classification Code. As specified in the requirements below, this can take several forms; one example is shown in figure 7.3.  Figure 7.3 Here also, the Classification Codes are shown as relatively simple, for illustration. Each class has a Classification Code that can be combined with the Classification Codes of its parent classes to make a Fully-Qualified Classification Code. So, for example, the Fully-Qualified Classification Code of the class Disaster Recovery is 001-001-003. It is constructed as follows: start with the Classification Code of its highest parent in the hierarchy (001, being the Classification Code of the class Corporate Direction); add the Classification Code of its next parent down in the hierarchy (001, being the Classification Code of the class Business Continuity), making 001-001; repeat the previous step until the nearest parent class is reached (in this simple example, there are no repeats); add the Classification Code of the class (003), being the Classification Code of the class Disaster Recovery), producing the Fully-Qualified Classification Code 001-001-003. Records and components are also allocated classification codes, to allow them to be referenced uniquely. The expected usage determines the degree of uniqueness required. System Identifiers generally must be unique within one ERMS instance or network node at a minimum, and network-wide by preference. Fully-Qualified Classification Codes must be unique within a classification scheme, though because they are built up hierarchically, the individual Classification Codes may be unique only within one node (e.g. a class or sub-file) of the hierarchy. Where uniqueness across a network is required, it is desirable that system identifiers should be based on an acknowledged standard that guarantees global uniqueness (that is, uniqueness across all systems at all times). This is also desirable for standalone, or non-networked, applications, so as to allow for possible future growth and for potential merger or acquisition activities. Several such standards have been proposed, none of which has a dominant position; MoReq2 therefore does not mandate the use of a specific standard for this purpose. Classification Codes RefRequirement Test Whenever a new occurrence of any of the following is created in or captured by the ERMS, the ERMS must associate with it a Classification Code: class; file; sub-file; volume; record; component.Y The ERMS must ensure that all Fully-Qualified Classification Codes are unique within a classification scheme hierarchy.P The ERMS must ensure that all Classification Codes and all Fully-Qualified Classification Codes retain the required degree of uniqueness regardless of any relocation (see requirement 3.4.1).Y The ERMS must be able to store Classification Codes as metadata elements of the entities to which they refer.Y The ERMS should allow the formats of Classification Codes and Fully-Qualified Classification Codes to be specified by an administrative role at configuration time. It should allow the following features of Classification Codes to be defined, for each level of the hierarchy: numeric, alphabetic or alphanumeric; presence or absence of leading zeroes; minimum length (in the case of leading zeroes); starting value; increment.YFully-Qualified Classification Codes must consist of a concatenation of Classification Codes separated by a separator character.Y The ERMS should allow the separator characters in Fully-Qualified Classification Codes to be selected from, at a minimum: (space); - (dash); / (forward slash); . (dot).YFor example, a Classification Code of 001-001-003 (as in the introduction above) could therefore be shown as any of the following, depending on the choices made for leading zeroes and separator at configuration time: 1 001 003; 001-001-003; 1/1/3; 001.001.003..Remembering that requirement 3.2.7 allows for global prefixes and extensions these might also be shown as: corporate/1/1/3; 001.001.3.pt. The ERMS must allow an administrative role to specify, when a new class is created, whether its child entities will have Classification Codes generated automatically by the ERMS or provided by the user/an external application. The ERMS must either: generate each Classification Code automatically and prevent users from inputting it manually, and from subsequently modifying it (for example, a sequential number, as in the example above); or: allow an authorised user or an external application to provide the Classification Code, but subsequently prevent them from modifying it.PAn example of the first option is if a new class titled Incident Management is added under the class Business Continuity in the example shown in figure 7.3; in this example, it would be allocated the Classification Code 004, as shown in figure 7.4. Figure 7.4The second option is appropriate in case management settings. When the ERMS generates a new Classification Code automatically (the first option in  REF BK2266 \n  7.1.8), it must generate the next sequential number taking into account: the most recently used Classification Code at that point in the classification scheme, or (for the first at that point) the starting value; the increment specified, see  REF BK2267 \n  7.1.5.YSee figure 7.4 for an example. When accepting a Classification Code from a user or from an external application, the ERMS must validate it for uniqueness within its parent.YSystem Identifiers RefRequirement Test Whenever a new occurrence of any of the following is created in the ERMS, the ERMS must associate with it a System Identifier: classification scheme; class; file; sub-file; volume; record;  HYPERLINK \l "Gl_Redaction" redaction; retention and disposition schedule; document.Y The ERMS must ensure that all System Identifiers are unique within a classification scheme hierarchy and within the ERMS instance.NNote that this requirement extends across geographical locations where a distributed classification scheme has been implemented and across classification schemes when more than one classification scheme has been implemented. The ERMS must be able to store System Identifiers as metadata elements of the entities to which they refer.Y The ERMS should allocate System Identifiers which are globally unique.NGlobally unique means that the System Identifiers are allocated using an algorithm that guarantees no other System Identifier can have the same value, regardless of when it is produced or by which ERMS.This is desirable to allow for re-configurations, such as those caused by corporate re-organisations, acquisitions and mergers etc. If every entity is not allocated a globally unique System Identifier, the probability of difficulties during re-configurations is high. The ERMS should use the UUID algorithm (as specified in ISO/IEC 9834-8 and ITU-T Rec. X.667) to generate globally unique System Identifiers.PThis algorithm, which in some implementations is commonly referred to as GUID (Globally Unique ID), can be used to guarantee uniqueness.Other approaches to the generation of unique identifiers may be used, including the Digital Object Identifier System (DOI),the Uniform Resource Name (URN) scheme and the Archival Resource Key (ARK). The ERMS must not require users to enter or use System Identifiers for any ERMS function. PThis requirement is included because globally unique identifiers tend to be long and not user-friendly. However, it is acceptable for users to be allowed to use System Identifiers if they choose to.Searching, Retrieval and Presentation This chapter lists requirements for searching and retrieval in section 8.1. Requirements associated with presentation are divided into three sections: section 8.2 lists requirements for display, section 8.3 deals with printing, and section 8.4 addresses the presentation of records which cannot be printed. An integral feature of an ERMS is the ability for the user to retrieve files and records. This includes searching for them, whether or not precise details are known, and presenting them. Presentation is producing a representation on-screen (displaying) or printing; it may also involve, as necessary, playing audio and/or video (see glossary). Accessing files and records, and then viewing them, requires a flexible and broad range of searching, retrieval and presentation functions to meet the demands of different types of user. Although some advanced search features can be thought of as being beyond classical records management functions, the required functionality is described here on the grounds that an ERMS without good retrieval facilities is of limited value. All of the features and functionality in this chapter must be subject to access controls as described elsewhere in this specification, including security controls. The ERMS must never present information to any user which that user is not entitled to receive. To avoid complexity, this is assumed and is not repeated in each detailed requirement. Search and Retrieval Searching is the process of identification of records or files through user-defined parameters for the purpose of locating, accessing and retrieving records, classes, files, sub-files, volumes and/or their metadata. The ERMS search and navigation tools are used to locate metadata, classes, files, sub-files, volumes or records. These require a variety of searching techniques to support users ranging from (for example) the sophisticated research user to the casual and less computer literate. RefRequirement Test No ERMS search or retrieval function must ever reveal to a user any information (metadata or record content) where the access and security controls (sections 4.1 and 10.13 respectively) prevent access by that user. P The ERMS must allow users to search for and retrieve: records; every level of aggregation of records (class, file, sub-file, volume); and their associated metadata at any level of the classification scheme.Y The ERMS must allow users to specify any combination of metadata elements as search terms.YThe search facility needs to be able to search on any of the metadata elements, for example, Title. The ERMS must allow users to specify whether a search is to find records or a specified level of aggregation of records.Y The ERMS search function should appear to users to be the same for all searches specified in requirement  REF BK2289 \n  8.1.2. YIn other words, users should see the same interface, features and options whether searching for classes, files, sub-files, volumes or records (though details of the presentation of results may vary according to what is being searched).  The ERMS must allow users to search for the text content of records.YThis includes the text of records that are inherently textual in nature, such as e-mail messages, and (where the ERMS includes OCR functionality) records which have been converted to text by OCR (see requirement  REF BK4122 \n  6.5.7). The ERMS must allow the use of searches to locate an aggregation for the purpose of declaration, as a part of the declaration process. YThis is an ease of use requirement. It requires that search functionality be readily available to users who are in the process of capturing one or more records; in other words users must not be forced to quit a capture process to initiate a search.  The ERMS must allow users to use any combination of metadata elements and/or textual record content as search terms during a search operation.YFor example a search could combine a named author together with a particular text string in the record. The ERMS should provide a search function which operates in an integrated and consistent manner across both record content and metadata.YThis means that the interface and its behaviour should be the same across these kinds of searches. The ERMS must display the total number of items found as a result of the search, and display (or allow the user to request display of) the search results (the hit list).Y The ERMS should allow users to refine (i.e. narrow) a search without having to re-enter the search criteria. YA user should for example be able to start with the hit list from a search, and then perform a further search within that list. The ERMS must allow administrative roles to configure and subsequently change the specification of default search metadata elements including: any element of record, volume, sub-file, file and class metadata, and optionally, text.YThis refers to the default window that first appears when a search is initiated; it generally contains a set of fields for metadata elements that are commonly used in searches. This set comprises the default elements in the requirement. The ERMS must provide a search function that allows the use of all Boolean operators namely: AND; OR; EXCLUSIVE OR; NOT; in any valid combination to combine an unlimited number of search terms.P The ERMS must allow users to search for objects by their keyword(s), where the objects have keywords.Y During any search involving keywords, the ERMS must allow users to select keywords from controlled vocabularies (or lists of permitted terms).YNoting requirement  REF BK4074 \n  8.1.7, this could be during a capture process, or during any other search. The ERMS should incorporate the use of a thesaurus to enable users to search by concept.Y Where the ERMS incorporates the use of a thesaurus for concept searching, it should be compliant with at least one of the following standards: ISO 2788; ISO 5964.Y This will allow retrieval of documents with a broader, narrower, or related term in their content or metadata. For example, a search for ophthalmic services might retrieve health services, eye test or ophthalmology. The former standard specifies a monolingual thesaurus and the latter a multilingual thesaurus. (See  REF BK2093 \n  3.2.13 and  REF BK3635 \n  3.2.14). If a thesaurus compliant with ISO 2788 or ISO 5964 is integrated with the ERMS, the ERMS should allow a user who is searching using a keyword (or other metadata element related to the thesaurus) to use the full features of the thesaurus, such as broader, narrower and related terms and synonyms as an integrated part of the process.YIn other words, if a user is searching for a file, the user may enter a term that is not in the schemes controlled vocabulary, then use the thesaurus features to find the appropriate preferred keyword. An example is if budgets is a preferred keyword: in this case, a user might enter estimates and then be guided to its broader term budgets; or a user might enter accounting records and be presented with a list of narrower terms, one of which is budgets.For ease of use, users must not have to leave the search interface to access the thesaurus to search for related search terms. Refer to the introduction to section 11.8 for a more detailed explanation of the phrase as an integrated part of the process. Where the ERMS incorporates the use of a thesaurus, the ERMS must allow an administrative role to maintain the thesaurus.YMaintenance is needed for the introduction of new terms and terms specific to the business. The ERMS must restrict to authorised administrative roles the ability to change the keywords associated with a file.YThis facility is intended for exceptional circumstances only, such as to correct clerical errors. Changing keywords inappropriately can seriously compromise the accessibility of records, even if logged in an audit trail, and so should be avoided.  The ERMS should provide for partial match and wild card searching that allows for forward, backward and embedded expansion, for both metadata values and content.YFor example: the search term proj* might retrieve records containing project and projection and PROJA; the search term psycho*s might retrieve records containing psychosis, psychotics and psychologists; the search term *byte might return gigabyte and terabyte; the search term organi?ation might retrieve records containing organisation and organization.  The ERMS should provide word proximity searching. YA proximity search finds terms separated by no more than a specified number of words, for example: International and Organisation separated by no more than one word. The ERMS must allow users to limit the scope of any search to any aggregation specified by the user at the time of the search. Y The ERMS must be able to search for, and retrieve, a complete electronic file, sub-file or volume, and all its contents and contextual metadata, and display a list of all the, and only those, entries in the context of that aggregation in a single retrieval process. YThis is needed when a user wishes to copy or print the entire contents of a file to take to a meeting, or to facilitate temporary working, or for any other reason. The ERMS must behave in an identical manner when searching regardless of whether the objects being searched for are stored on-line, near-line or off-line, save that the mechanism and performance for presenting electronic objects may vary. P This requirement applies only when the ERMS uses near-line and/or off-line storage in addition to online storage. The ERMS should allow users to save and re-use search terms.Y The ERMS should allow users to make saved search terms available for use by other users.Y The ERMS should allow users to specify time intervals in search requests, e.g. calendar dates or number of days.Y The ERMS should allow the use of time intervals specified either as dates (e.g. 24 Dec 2008 5 Jan 2009) or in natural language, e.g. last week, this month, as search terms, allowing the use of at least the following words and/or their equivalents in other languages: last; this; next; week; month; quarter; year; names of days of the week; names of months.Y The ERMS should allow users or administrative roles to configure display of the search results, including: the order in which the search results are presented; the number of hits displayed on the screen per view from the search; the maximum number of hits for a search; which metadata elements are displayed in search result lists.Y The ERMS should provide implicit or explicit relevance ranking of the search results.Y When a hit list contains a redaction of an electronic record, or a record for which a redaction exists, (see section 9.3), the ERMS should relate the two, so that retrieval of one shows the existence of and allows retrieval of the other, subject to access controls, whilst retaining separate metadata for the two items.Y The ERMS should allow the configuration of a search engine other than the default search engine.NIt may be desirable for an organisation to implement a search engine other than that which is supplied with the ERMS for system compatibility or other reasons.Presentation: Displaying Records An ERMS may contain records with different formats. The user requires generic presentation facilities that will accommodate the display of a range of formats. RefRequirement Test Whenever a user reaches a view that indicates the existence of a class, file, sub-file, volume or record, the ERMS must be able to present its contents and/or its metadata by a mouse click or keystroke. YThis applies regardless of how the user reached the view by navigating through the classification scheme, by searching, by following a link or any other way and assumes that the user has appropriate permissions.For example: a user executes a search and obtains a hit list showing several records; for any record the ERMS must be able to present the content of any record in the hit list if the user enters a mouse click or keystroke, and must also be able to present the records metadata similarly; a user navigates the classification scheme to a class that contains files; the ERMS must be able to present a list of all the files allocated to that class if the user enters a mouse click or keystroke, and must also be able to present the classs metadata similarly .If the ERMS is storing records in a proprietary application format, it may be acceptable for the presentation to be performed by an application outside the ERMS.  The ERMS should be able to present records that the search request has retrieved without loading a software application associated with the record. YThis is typically provided by integrating in the ERMS a viewer software package. This is frequently desirable to increase speed of presentation.  The ERMS should be able to present all the types of electronic records specified by the organisation in a manner that preserves the information of the records (e.g. all the features of visual presentation and layout produced by the generating application package), and which presents all components of an electronic record together.NThe organisation needs to specify the application packages and formats required, and in some cases acceptable levels of fidelity. In many cases (e.g. in typical office environments) the fidelity need not be specified in detail; however rigorous specification of fidelity may be needed for applications which rely on detailed interpretations, such as records including high-resolution X-ray images.Presentation: Printing This section applies only to records and other information whose content can be printed in a way that is understandable. It does not apply to, for example, audio or video files. The ERMS must provide printing facilities, to allow all users to obtain printed copies of printable records, their metadata, and of other administrative information. In all requirements, printing is understood to include features normally associated with report production, such as multi-page reports, page numbering, dated headings, and the use of any configured printer. Sending screen image dumps to a printer is not normally considered sufficient for these requirements. RefRequirement Test The ERMS must be able to print the content of records and specified elements of their metadata. Y The ERMS must allow the printing of all or specified metadata for any class, file, sub-file, volume or record. Y The ERMS must allow all records in a class, file, sub-file or volume to be printed in one operation.Y The ERMS must allow users to specify a subset of metadata elements (such as Title, Author, Creation date) and print out a summary list of these elements for selected aggregations of records.Y The ERMS should allow an administrative role to specify at configuration time that all printouts of records contents have selected metadata elements appended to them (e.g. title, registration number, date,  HYPERLINK \l "Gl_SecurityCategory" security category) by default.YThis could be used, for example, to ensure that whenever a record is printed, its security category is printed at the same time, as a security measure. The ERMS should allow users, at the time of printing, to amend the default metadata elements that are appended to printouts.Y ERMS must allow users to print hit lists (see section 8.1) resulting from a search.Y The ERMS must allow an administrative role to print all, or a selection of, administrative parameters.YFor example a list of all users with a specific security category or all users in a particular user group. The ERMS must allow an administrative role to print retention and disposition schedules.Y If a thesaurus is integrated (see  REF BK2280 \n  8.1.16) the ERMS should allow administrative roles to print the thesaurus.Y The ERMS must be able to print out a list of each controlled vocabulary (a list of all permitted terms).YIt is acceptable to print the list from thesaurus management software where this is integrated with the ERMS. The ERMS should be able to export a list of each controlled vocabulary (a list of all permitted terms).Y Where a controlled vocabulary of keywords takes the form of an ISO 2788-compliant or ISO 5964-compliant thesaurus, the ERMS should be able to print out the thesaurus entries, showing all terms and their relationships.YPrinting of ISO standards-based thesauri should be compatible with the representational guidelines given in ISO 2788 and ISO 5964.It is acceptable to print this from separate thesaurus management software that is integrated with the ERMS. The ERMS must allow authorised roles to print the classification scheme both as a complete scheme and as any class selected from the scheme.Y A user printing a classification scheme (as in  REF BK2682 \n  8.3.14) should be able to specify the content and format of the resulting printed output.PFor example, the user should be able to specify the metadata elements to be printed, and preferably choose a list, or indented, or graphical representation. The ERMS must allow administrative roles be able to print a list (sometimes referred to as a repertory) of all files or of files classified against a specific class (and its child classes). Y A user printing a list of files (as in  REF BK2091 \n  8.3.16) should be able to specify the sequence, content and format of the list.YFor example, the user should be able to sort in ascending or descending order, on title or code, and preferably on any attribute; and should be able to specify the metadata elements to be printed. The ERMS must allow administrative roles to print all or part of audit trails (see  REF BK2149 \n  4.2.1).Y The ERMS must be able to print the formats specified by the organisation. Printing must: preserve the layout produced by the generating application package(s); include all printable components of the electronic record.YThe organisation needs to specify the formats required.Presentation: Other This section applies only to records and other information whose content cannot be printed in a way that is understandable, such as audio or video files. RefRequirement Text The ERMS must include features for presenting and outputting to appropriate media records which cannot be printed.PExamples include audio, video, and some web-sites. The organisation will need to specify the nature of these records. Administrative Functions This chapter covers the maintenance and system support functionality required by an ERMS. Requirements are listed in this chapter for: general administration (section 9.1); system reporting (section 9.2); changing, deletion and redaction of records (section 9.3). Closely-related features are described in chapter 4, namely; access permissions in section 4.1; backup and restore in section 4.3. These facilities allow administrative roles to manage change in the user population and parameters affecting the behaviour of the system. The ERMS needs to provide administrative roles with the ability to manage events such as maintaining the user base and, crucially, the permissions assigned to users, groups and roles. The system must also provide monitoring capability for system errors. Some of these facilities may be provided by an associated EDMS, database management system, operating system, or by other applications. General Administration This section includes requirements for managing system parameters, system management and configuration, and user administration. In large organisations, the functionality described in this section may be assigned to an operations function rather than to an application administrator. However, in small organisations, it may be assigned to an administrator. RefRequirement Test The ERMS must allow administrative roles to retrieve, display and re-configure systems parameters and settings made at configuration time.YThese settings include, for example, configuration of access rights or classification codes. The ERMS must allow administrative roles to: allocate functions to users and roles; allocate one or more users to any role. Y The ERMS must monitor available storage space, and notify administrative roles when action is needed because available storage is below a level set at configuration time, or because of another error condition.PIt is acceptable for administrative roles to be notified by means of separate system management software.  Where the storage supports error rate reporting, the ERMS should monitor error rates occurring on storage media, and report to administrative roles any medium or device on which the error rate is exceeding a parameter set at configuration time or at a later date. NThis applies particularly to optical media. It is acceptable for administrative roles to be notified by means of separate system management software.  The ERMS should allow administrative roles easily to move users between user groups and roles.YIn particular, it should be possible to move a user without having to delete the user from the ERMS and re-enter the users details.Reporting Flexible reporting is an important feature in an ERMS. It is required so that administrative roles can manage the system; and so that management can monitor the ERMS to ensure that it is used appropriately. An ERMS needs to be able to provide a number of management, statistical and ad hoc reports so that administrative roles can monitor system activity and status. This reporting is required across the entire system, including: the classification scheme; files and records; user activity; access and security permissions; disposition activity. The ERMS must provide a number of standard reports capable of being configured by administrative roles and should be flexible to enable ad hoc reports to be produced on demand. Ideally the ERMS will include a flexible report-writing sub-system. However, it is not appropriate to attempt to reproduce here the requirements for a comprehensive report writing sub-system, so this section gives outline requirements only. The amount and complexity of reporting will be determined by organisational features including the size, complexity and levels of change to the classification scheme, the amount and nature of the records, and the user base. RefRequirement Test The ERMS must allow administrative roles to produce periodic reports (daily, weekly, monthly, quarterly) and to specify ad hoc reports.Y The ERMS must include features for printing reports, viewing them on-screen and storing them in electronic form.YAs in section 8.3, printing is understood to include features normally associated with report production such as multi-page reports, page numbering, dated headings, configurable page headers and footers, and use of any configured printer). Sending screen image dumps to a printer is not normally considered sufficient for these requirements. A user viewing an ERMS report should be able to capture it as a record.YThis will be useful, for example, for storing securely reports that attest to the integrity of the records. The ERMS should allow time periods covered by a report to be configured either as a date range (e.g. 24/12/2008 5/1/2008) or as a time interval specified in natural language (as in  REF BK2294 \n  8.1.29). Y The ERMS must include features for sorting and selecting the information included in reports.YFor example, users should be able to specify which columns of a columnar report are used to sort the report contents. The ERMS should include features for totalling and summarising report information.Y The ERMS should include features for graphical reporting.YFor example, trend-reports showing changes in reported information over time, or histograms. The ERMS must enable report requests to be saved for future re-use.Y The ERMS must enable reports to be exported for use in other applications.YFor example, users may wish to work with the contents of a report using spreadsheet software. MoReq2 does not specify the format(s) to be used for such exports. The ERMS must be able to provide reports on the total number and location of: files, sub-files and volumes; records, sorted by file format and version; files, sub-files and volumes, sorted by access control and security markings (where used); electronic files, sub-files and volumes, sorted by size; electronic files, sub-files and volumes, sorted by storage location; vital records.P The ERMS must be able to provide reports on: the rate of capture of records; the rate of retrieval of records; the rate of creation of new classes and files.Y If the document management option described in section 10.3 is present, the ERMS must be able to provide reports on the total number and location of documents; the rate of capture/creation of documents; the rate of retrieval of records.Y The ERMS should allow the reports described in  REF BK3912 \n  9.2.11 and  REF BK4933 \n  9.2.12 to be for any combination of: across the entire system or for specified classes; specified user groups or users; a specified range of dates.Y The ERMS should be able to provide reports on actions on files and records sorted by user, by workstation and (where technically appropriate) by network address. P The ERMS should allow the reports described in  REF BK3912 \n  9.2.11 to cover a specified time interval within several days.YFor example, showing hourly figures, to allow peaks and troughs of activity to be monitored. The ERMS must be able to produce a report listing files, sub-files and volumes, for all or part of the classification scheme, structured to reflect the classification scheme. Y The ERMS must be able to provide a report on the amount of system storage space currently in use and available.Y The ERMS must allow administrative roles to produce reports on the audit trail. These reports must include, at a minimum, reporting based on any selected: class; file; sub-file; volume; record; user; time period.Y The ERMS should allow administrative roles to enquire on and produce audit trail reports based on selected: security categories; user groups; other metadata. Y The ERMS must be able to report on the outcome of a disposition process listing the classes, files, sub-files, volumes and records successfully disposed of and any failures. Y The ERMS must be able to provide reports on the outcome of an export process listing the classes, files, sub-files, volumes and records successfully exported and any failures.Y The ERMS must be able to provide administrative roles with reports on disposition activity, including disposition actions that are overdue.Y The ERMS should allow administrative roles to restrict users access to selected reports.Y The ERMS must be able to provide administrative roles with a report on attempted access control and other security policy violations.YThis requirement only applies when the ERMS (and/or the operating system) is configured so as to allow an items existence to be visible to a user even though the user is not allowed access to it. It is not relevant when the ERMS is configured to hide the existence of an item which cannot be accessed. Administrative roles should be able to specify the frequency of retention and disposition schedule reporting, the information reported and highlighting exceptions such as disposition overdue.Y The ERMS should provide quantitative reports on the kinds of records to be reviewed within a specified period.Y The ERMS should support reporting and analysis tools for the management of retention and disposition schedules by an administrative role, including the ability to: list all retention and disposition schedules, sorted by reason or date; list all entities to which a specified retention and disposition schedule is assigned; list the retention and disposition schedule(s) applied to all entities in a class; identify, compare and review retention and disposition schedules (including their contents) across the classification scheme; identify formal contradictions in retention and disposition schedules across the classification scheme.Y The ERMS should be able to accumulate statistics of review decisions in a given period and provide tabular and graphical reports on the activity. Y The ERMS should be able to accumulate statistics of the imposition and lifting of disposal holds in a given period and provide tabular and graphical reports on the activity.P The ERMS must produce a report detailing any failure during a transfer, export, destruction or deletion. The report must identify any records, aggregations and associated metadata destined for transfer which have generated processing errors, and any entities which are not successfully transferred, exported, destroyed or deleted. Y The ERMS must produce a report detailing any failure during an importation. The report must identify any records, aggregations and associated metadata destined for import which have generated processing errors, and any entities which are not successfully imported. Y The ERMS should support the import process, by tracking and reporting on its progress and status, including the percentage completed and number of records imported.Y The ERMS should provide the ability to sort electronic files selected for transfer into ordered lists according to user-selected metadata elements. Y The ERMS should provide the ability to generate user-defined reports to describe electronic files and records that are being exported or transferred.YChanging, Deleting and Redacting Records A basic principle of recordkeeping is that records cannot normally be changed, and (except at the end of their life cycle in the ERMS) files, sub-files, volumes and records cannot normally be destroyed. This section deals with the requirements for exceptional situations where the content of a declared record may need to be amended, or a record deleted and replaced. In some situations, administrative roles may need to delete records to correct errors to meet legal requirements. An example may arise under data protection legislation, though other scenarios are possible. The action of deletion may mean one of two things: destruction; retention, accompanied by a notation in the records metadata that the record is considered removed from records management control. In either case, deletion is to be exceptional, and so the ability to delete must be tightly controlled in order to protect the general integrity of the records. In particular, information about deletions must be stored in the audit trail. If local legislation or regulation imposes different requirements, for example relating to the expunging of personal data (see ISO 12037), this should be addressed in a national chapter zero. Administrative roles sometimes need to publish, or make available, records containing information which is still sensitive, without revealing the sensitive information. This can result from data protection rules, security considerations, commercial risk, etc. For this reason, administrative roles need to be able to mask the sensitive information, without affecting the underlying record. The process is referred to here as redaction. When this process is carried out, the result is the original record (unchanged), and a copy of the record which has been masked in some way (the  HYPERLINK \l "Gl_Redact" redacted copy, or redaction of the original record). The ERMS stores both the original record and the redaction. In principle, redaction can apply to any kind of record text, image, audio, video etc. Note that deletion and change are also discussed in chapter 5. RefRequirement Test The ERMS must allow a configuration option which prevents any record, once captured, from being deleted or moved by any administrative or user role; see also  REF BK4595 \n  9.3.3.YThis requirement does not affect transfer or destruction of records in accordance with a retention and disposition schedule, as described in section 5.3. It is intended for environments in which the deletion of records (as described above) is either unnecessary or not permitted. The alternative to this option is specified in  REF BK2353 \n  9.3.2. The ERMS must allow a configuration option, as an alternative to  REF BK2354 \n  9.3.1, that  deletion of a record is implemented as destruction of that record, and that relocation of a record results in moving the record; see also  REF BK3929 \n  9.3.4.YThis is not regarded as good practice in records management. It is included here only for situations in which it is considered unavoidable. In most situations, the option specified in  REF BK2354 \n  9.3.1 should be preferred. This option and the option in  REF BK2354 \n  9.3.1 are mutually exclusive. If the option in  REF BK2354 \n  9.3.1 is selected, the ERMS must behave as follows: If an administrative role  deletes a record (as in  REF BK2348 \n  9.3.5) the record s metadata must be marked accordingly, and the ERMS must hide the content and metadata of the record from all users save potentially for suitably-authorised administrative roles, as if it were deleted; and the ERMS must record this in the audit trail. If an administrative role  re-locates a record (as in  REF BK2123 \n  3.4.1), the ERMS must behave exactly as for a deletion but with the addition that a copy (or a pointer, depending on the storage method used) must be inserted automatically at the new location.YThis assumes that either no administrative roles would have such authorisation, or else a particularly small number. If the option in  REF BK2353 \n  9.3.2 is selected, the ERMS must behave as follows: If an administrative role deletes a record (as in  REF BK2348 \n  9.3.5) the record must be deleted, along with its metadata except for metadata specified as part of its metadata stub (see  REF BK2217 \n  5.3.19); and the ERMS must log this in the audit trail. If an administrative role re-locates a record (as in  REF BK2123 \n  3.4.1), the ERMS must behave exactly as for a deletion but with the addition that the record (or a pointer to it, depending on the storage method used) must be inserted automatically at the new location.Y The ERMS must allow administrative roles to delete classes, files, sub-files, volumes and records outside the disposition process.YThis is intended for use only in exceptional circumstances as described in this section. It must be read together with  REF BK2354 \n  9.3.1 and  REF BK2353 \n  9.3.2. The ERMS must allow user roles to mark classes, files, sub-files, volumes and records as candidates for deletion. YThe administrative role can then decide whether or not to carry out the deletion. In the event of any deletion as defined above, the ERMS must: log the deletion in the audit trail; produce a report for administrative roles; delete the entire contents of a class, file, sub-file or volume when it is deleted; ensure that no documents are deleted if their deletion would result in a change to another record (for example if a document forms a part of two records, one of which is being deleted); highlight to administrative roles any links from another file, or record to a file, sub-file or volume which is about to be deleted, requesting confirmation before completing the deletion; maintain integrity of the metadata at all times.YIn this context the phrase maintain integrity of the metadata means to ensure that no metadata in any entity (class, record etc.) refers to an entity that does not exist. Administrative roles must be able to change any user-entered metadata element.YThis functionality is intended to allow administrative roles to correct user errors such as data input errors, and to maintain user and group accesses. Good practice generally will require that users correct their errors whenever possible; this requirement does not prevent users from doing so. Information about all changes to all metadata elements must be stored in the audit trail.Y The ERMS must allow administrative roles to create one or more redaction(s) of a record while retaining the original record.YIt may be necessary, in some cases, to provide redactions for several parties in which different parts of the record have been redacted.  The ERMS must allow removal or hiding of sensitive information within a redaction for all record formats required by the organisation.PIf the ERMS does not provide these facilities, it must allow for other software packages to integrate with it and do so. It is acceptable for the ERMS to render a record to a different file format to permit the redaction of a copy, provided that the rendition maintains sufficient fidelity.It is essential that, when this feature or any other redaction features are used, none of the removed or hidden information can ever be retrieved from the redaction, whether on screen, when printed, played back or in any other form of presentation. This is regardless of the use of any presentation features such as rotation, zooming or any other manipulation including opening the redaction in a different software package. When a redaction is created, the ERMS must store automatically its creation in the metadata of the redaction and the record, including date, time and creator.Y When a redaction is created, the ERMS must require the user creating it to enter a reason, and must store that reason in the metadata of the redaction and the record.Y Upon creation of a redaction the ERMS should automatically declare redactions as records, classifying them in the same aggregation as the original record and prompting the creator of the redaction for: a reason (see  REF BK4920 \n  9.3.13); security category (where applicable); optionally, an aggregation into which a copy of the redaction will be declared.P Upon creation of a redaction the ERMS should allow the copying of metadata elements to the redaction.Y Subject to access control rights the ERMS should enable amendment of selected metadata values, for example title.Y The ERMS should store a cross reference to a redaction in the same class, file, sub-file or volume as the original record, even if that class, file, sub-file or volume is closed.YThis is in addition to the requirement to file a copy, in  REF BK2343 \n  9.3.14, to allow for cross referencing even in the same file, as the original and redaction may be separated by large numbers of records in the file. When a record is retrieved the ERMS must show, or allow the user to see, the existence of all redactions made from that record and, subject to access and security controls, make them available for retrieval.Y When a redaction is retrieved the ERMS must show, or allow the user to see, the existence of the original record and, subject to access and security controls, make it available for retrieval.Y The ERMS must store in the audit trail any change made as a result of any requirement in this section.POptional Modules This chapter contains requirements functionality closely allied to electronic records management. It covers requirements to support the management of physical (non-electronic) records, document management, workflow, electronic signatures and other functionality. Each of the sections in this chapter corresponds to one optional module of the MoReq2 Testing Framework. These modules are optional in the sense that their requirements are not a mandatory part of the core functionality of a MoReq2 compliant ERMS. The sections in this chapter list requirements for the following areas: management of physical records (section 10.1); disposition of physical records (section 10.2); document management and collaborative working (section 10.3); workflow (section 10.4); casework (section 10.5); integration with content systems (section 10.6); electronic signatures (section 10.7); encryption (section 10.8); digital rights management (section 10.9); distributed systems (section 10.10); offline and remote working (section 10.11); fax integration (section 10.12); security categories (section 10.13). The requirements in this chapter are for optional functionality which may be integrated with an ERMS. They supplement the core requirements in the rest of MoReq2. These requirements are applicable only if the organisation needs to implement the optional functionality. Conformity with the requirements in this chapter is not required for MoReq2 compliance. Therefore mandatory requirements in this chapter are mandatory only when the optional module in which they are located is included in a test. In each case, requirements are presented at a high level. As they do not define the core functions of an ERMS, these requirements are not exhaustive but rather provide an indication of the appropriate activities. Management of Physical (Non-electronic) Files and Records In addition to the electronic records, an organisations records repository may contain non-electronic records. These can include paper-based records and records on other analogue media, for example microfiche or audio tapes. They may also include digital records stored on portable media, such as CDs, DVDs and computer tapes. The term physical records is used in MoReq2 to mean any record that is held in a medium outside the ERMS. This includes not only analogue media but also digital media holding records that are not individually controlled by the ERMS. For example: a CDROM containing 10,000 images which are not individually recognised by the ERMS as records is a physical record; a CDROM containing 10,000 images, and located in a drive or jukebox connected to the ERMS, and with each of the images recognised by the ERMS as a record is not a physical record it is a removable medium on which electronic records are stored. This specification does not address the business need to manage and maintain physical records. Such a need may or may not exist, according to the legislative and regulatory environment. Where it does exist, care needs to be taken to preserve the integrity and accessibility of electronic and physical records taken as a whole. These issues should be addressed by appropriate organisational policies. The ERMS must be able to accommodate references to physical records as well as, and together with, electronic records; and to manage aggregations made up of both electronic and physical records. Classes, files, sub-files and volumes may all contain any combination of electronic records and physical records. This differs from the entity-relationship model in the previous version of MoReq. Physical records can co-exist with electronic records in several scenarios. The scenarios include: A class, file, sub-file or volume contains only physical records. In this case, the entity represented in the ERMS represents a physical container for the records, such as a filing jacket; A class, file, sub-file or volume contains both electronic and physical records. The physical records are stored without a container relevant to records management for example, an engineering drawing stored along with unrelated drawings in a cabinet. The ERMS must provide features to allow physical containers (as in the first option) to be managed. In order to manage physical records the ERMS must be able to capture and manage metadata about them. This metadata enables administrative and user roles to, subject to access controls, locate, track, retrieve, review and dispose of physical records, and to allocate access controls to them in the same way as to electronic records. Similarly, the ERMS must be able to capture and manage metadata about physical containers. RefRequirement Test The ERMS must allow an administrative role to identify classes, files, sub-files and volumes that exist as physical containers.Y The ERMS must allow administrative and user roles to enter and maintain metadata about classes, files, sub-files and volumes that exist as physical containers, as specified in the MoReq2 metadata model.Y The ERMS must allow user roles to enter and maintain information about physical records in classes, files, sub-files and volumes, following the same rules as when capturing electronic records.Y The ERMS must allow classes, files, sub-files and volumes to contain electronic records and physical records together, in any combination.Y The ERMS must allow physical records to be managed in the same way as the electronic records, including any inheritance of metadata.P When a user is browsing, retrieving, or otherwise working with a class, file, sub-file or volume, the ERMS should indicate the presence of any physical container or records in it with appropriate indicators.YA user needs to determine easily whether physical entities exist in order to ensure that all records are managed in the same manner. MoReq2 does not prescribe the nature of these indicators. The ERMS must allow a different set of metadata elements to be configured by an administrative role for physical classes, files, sub-files, volumes and records than for the electronic equivalents. As an example, physical file metadata could include (but is not limited to) additional metadata for: information on its physical location; information regarding the format of the physical container or record. Y The ERMS must ensure that retrieval of any class, file, sub-file or volume simultaneously retrieves the metadata for both electronic and physical entities associated with it in a single operation.Y The ERMS should support tracking of physical containers and records by the provision of check-out and check-in to log their location,  HYPERLINK \l "Gl_Custodian" custodian and the date of check-in/check-out.Y The ERMS should allow the user checking out a physical aggregation or record to specify a date by which it is due to be returned.Y The ERMS should report to a specified user when the date due for return of a physical aggregation or record is approaching and when it is overdue. Y The ERMS should allow a suitably authorised user to change the date due for return of one or several physical aggregations or records, in a single operation.Y The ERMS must ensure that the metadata for physical aggregations and records is always subject to the same access controls as would be the case if they were purely electronic.Y The ERMS should provide a tracking function to allow users to log information about the location and movement of physical aggregations and records.Y The ERMS tracking function should allow for locations of physical entities to be selected from or validated against a list (such as a pull-down list).YWhere the ERMS does not support a list of locations, non-validated free text is acceptable. The ERMS tracking function must allow users to enter the checking out and checking in of physical entities. YIn other words, the ERMS must provide facilities to log whether a physical entity is in its home location or has been checked out. The ERMS tracking function must log information about the movements of a physical entity which includes: unique identifier; current location; an administrative role-defined number of previous locations (the number to be defined at configuration time); date moved from location; date received at location; user responsible for the move (where appropriate). Y The ERMS must allow a user role to see the current location of a checked-out physical entity, its custodian, and the date upon which the check out occurred, subject to access control rights.Y The ERMS must log all check in and check out activities and dates within the audit trail.Y The ERMS must be able to log in the audit trail all changes made to the metadata values of physical entities.YFor example the location metadata element. The ERMS should support the printing and recognition of bar codes for files, sub-files, volumes and records; or alternative tracking systems such as Radio Frequency Identification (RFID) technology. YThis enables the ERMS to track the location and movements of physical records.  The ERMS should support the printing of labels for physical files, sub-files and volumes.YThis enables a label to be produced containing essential metadata which can then be attached to the physical entity. This could include, but is not limited to, such metadata as: Title; Identifier System; Classification Code; Date of Opening; Security Category (if used); Normal storage location. The ERMS must behave in an identical manner when dealing with physical or electronic records in searches, save that: the content of physical records cannot be presented (instead, the ERMS displays its location metadata, see below); different metadata may be shown for physical and electronic records.Y The ERMS should be able to notify administrative roles of any events in the retention and disposition schedule relating to non-electronic records and aggregations scheduled since a restore was executed.YSection 4.3 Backup and Recovery sets out the requirements for restoring an ERMS. When the system is used for managing non-electronic records a disparity may arise following a restore whereby disposition actions have been carried out on the physical objects, but this is not shown in the ERMS. This requirement enables administrative roles to apply remedial action.Disposition of Physical Records RefRequirement Test When the retention period for a retention and disposition schedule ends, if that retention and disposition schedule applies to any physical entities the ERMS must notify an administrative role. Y The ERMS must alert an administrative role to the existence and location of any physical entity associated with any class, file, sub-file or volume that is to be transferred, exported or destroyed. YThis may be either when the retention period for a retention and disposition schedule ends, or when a transfer or export is initiated. Whenever any physical entities are exported or transferred, the ERMS must export or transfer the metadata for them in the same way as the metadata for the electronic entities.Y On transfer, export or destruction of physical entities the ERMS must require an administrative role to confirm the physical transfer, export or destruction before the transfer, export or destruction is completed.YThis normally will require an administrative role to enter manually a confirmation that the physical records have been transferred or destroyed.Document Management and Collaborative Working Electronic Document Management Systems EDMSs are widely used in organisations to provide management and control over electronic documents. Many EDMS functions and facilities overlap with ERMS. EDMSs typically include indexing of documents, storage management, version control, close integration with desktop applications and retrieval tools to access the documents. Some ERMSs provide full EDMS capability, others only provide a subset. Conversely some EDMSs have incorporated core record management functions. EDMSs often form part of a wider system implementation and contain collaborative working tools to enable a number of users to participate in document drafting. Collaborative working is also an integral element of Content Management Systems. See section 10.6 for further requirements regarding these features. By way of clarification, the following table shows typical differentiators between an EDMS and an ERMS. An EDMSAn ERMSallows documents to be modified;prevents records from being modified;allows documents to exist in several versions;allows a single final version of a record to exist;may allow documents to be deleted by their owners;prevents records from being deleted except in certain strictly controlled circumstances;may include some retention controls;must include rigorous retention controls;may include a document storage structure, which may be under the control of users;must include a rigorous record arrangement structure (the classification scheme) which is maintained by an administrative role;is intended primarily to support day-to-day use of documents for ongoing business.may support day-to-day working, but is primarily intended to provide a secure repository for business records.The rest of this section sets out key requirements to be considered in the provision of an integrated ERMS/EDMS solution. The requirements apply only where EDMS facilities are part of the ERMS. A central feature of these requirements is the concept that documents can be stored in (that is, classified to) the same classes and files as records, though this is optional. This allows draft documents to be filed in the same aggregations as the final versions, which will be records. Note that the word document is used here specifically to describe information or an object that has not been declared as a record in the ERMS. RefRequirement Test The ERMS should be able to manage electronic documents and records in the context of the same classification scheme, using the same access control mechanisms.YThe intention of this requirement is to allow users to store documents that are drafts in the aggregations that the eventual record will be classified to. This is optional. Where the ERMS manages both documents and records within the same classification scheme it must clearly indicate which items are documents and which are records. YMoReq2 does not specify how this is achieved. Where the ERMS manages both documents and records within the same classification scheme it must allow user roles to perform the following tasks for any specified class or file: declare all documents as records; delete all documents, leaving only the records; delete all documents that are older than a specified age.Y Where the ERMS manages both documents and records within the same classification scheme it must notify an administrative role if documents exist within a class or file being exported and provide options to: enable the documents to be deleted; declare them as records; export them with the records.Y Where an EDMS is part of an ERMS, or is tightly integrated with an ERMS, the EDMS must be able to pass automatically electronic documents arising in the course of business to the ERMS for automatic capture as records.PThis is especially relevant to case working scenarios see also section 10.5. The ERMS must allow users to: capture an electronic document and declare it as a record in one process; or capture an electronic document, store it, and complete the capture by declaring it as a record at a later time. Y The ERMS must be able to copy the contents of an electronic record, in order to create a new and separate electronic document without automatically creating a new record, while ensuring retention of the intact original record.YFor example, a user may copy a record in order to send a copy to a recipient who is not a user of the ERMS. This copy may or may not be declared as a fresh record according to the context.  The ERMS must allow user roles to check out (see  REF BK3584 \n  10.3.11) any document to which they have appropriate access rights.Y The ERMS must allow user roles to check in any document that they have checked out, giving the user the option of checking it in as a new version or not (see  REF BK3595 \n  10.3.20).Y The ERMS should allow a user who checks in a document to enter, optionally, a textual explanation of the changes made while it was checked out.Y When a document is checked out by a user, the ERMS must prevent any other user from checking it out or changing it (subject to  REF BK4630 \n  10.3.13).YWhen a document is checked out, only the user who has checked it out can edit it.This applies to documents only. As a matter of definition, the ERMS must not allow any record to be checked out and amended. When a document is checked out, if any other user attempts to check it out, the ERMS must prevent the user from checking it out a second time, must inform the user that it is checked out, and must either: show the identity of the user who performed the checkout; or conceal the identity of the user who performed the checkout; the option being specified at configuration time.Y The ERMS must allow an administrative role to cancel the check out of a document.YThis is intended to allow for situations where the user who checked out the document is unable to check it back in. This situation can arise for several reasons, for example: the user checked it out to a PC that has failed or has been stolen; the checked out document has become corrupted; the user has forgotten to check it back in before starting a period of leave. A user must not be able to check in a version of a document that has had its check out cancelled (as in  REF BK4630 \n  10.3.13) as the same document.Y If an attempt is made to close an aggregation within the ERMS that includes a checked-out document, it must report this as an exception to an administrative role.Y Users should be able to capture a document from within the EDMS.Y Users must be able to transfer smoothly to and from the ERMS to declare the document as a record from within the EDMS.NThis requirement is especially important where the EDMS/ERMS is used in a general office environment.  Where there are multiple versions of a document the ERMS must be able to capture the document as a record in all of the following ways, with one being selected as default at configuration time and the user being able to select one during capture: the most recent version; one version that is specified by the user; all versions stored, held as a single record; all versions stored, held as separate but linked records.Y The ERMS must maintain a version number for each document, and must make it clearly visible when the document is retrieved or searched for.Y The ERMS must automatically increment the document version number when a document is checked in as a new version.Y The ERMS should allow the version numbering scheme to be defined at configuration time, allowing at least the following options; simple sequential version numbering, that is numbers of the form 1, 2, 3; major and minor version numbering, that is that is numbers of the form x.y., where x is a major version and y a minor version, with the user deciding whether to increment the major or the minor version, and the minor version being reset automatically to 0 when the major version is incremented.YOther numbering schemes are acceptable. The ERMS must allow document version storage to be configurable by an administrative role, at configuration time or later, at class and file level within the classification scheme, with at least the following default options for each class and file: all versions of all documents are stored in the class or file; only the most recent version (where an administrative role has the ability to specify major or minor versions) of each document is stored in the class or file; a number of versions of each document are stored in the class or file, the number being specified by an administrative role.YThis is to enable version control to be used where a history of document development is required. In areas where this history is not required, the number of versions stored and hence the storage required can be reduced. The ERMS should allow users who are storing a document to override the default value for the number of versions (as defined by  REF BK3700 \n  10.3.22) to be stored for that document.YFor example, the time of creation and author of a document, also metadata identifiable from structured fields within documents if these exist, such as date and subject.  The ERMS must allow a user to enter metadata values for a record at the time of capture.Y The ERMS must ensure that any metadata that is captured is managed in accordance with the MoReq2 metadata model.Y The ERMS should allow an authorised user to map EDMS metadata elements to appropriate ERMS metadata fields. N Where there is any conflict in the metadata between the ERMS and the document-generating system, the ERMS must alert the user.YThis can arise when the ERMS does not have control over the metadata elements in the document. The ERMS should be capable of integration with new EDMS versions or systems as these are brought into use by the organisation.NMoReq2 does not specify how this is achieved. Organisations should consider specifying this capability in more detail. The ERMS must be capable of version control, that is, managing different versions of an electronic document as a single entity.YThis supports the drafting process of a document and enables collaborative working The ERMS should be able to restrict users to viewing: only the latest version of a document; selected versions of a document; all versions of a document; versions that have been captured or registered as records, the choice to be made at configuration or a later time by an administrative role. Y The ERMS should allow users to have apersonal workspace for documents. YThis can be used by users to store personal documents which are not expected to be captured as records, for example, early drafts which are not suitable for corporate access, or other documents. Use of this workspace should be optional (that is, it should be possible to configure the ERMS so that it is not available). Where the ERMS includes personal workspace, an administrative role must be able to limit the size of this on a per user basis.Y Where the ERMS includes personal workspace, access of this must be restricted to the owner.YWorkflow The Workflow Management Coalition (WfMC) an international association for developing workflow standards defines workflow as the automation of a business process, in whole or part, during which documents, information or tasks are passed from one participant to another for action, according to a set of procedural rules. In this definition, a participant can be a user, a work group (for instance a team), or a software application. The requirements in this section cover both basic routing functions, as described in  REF BK4394 \n  6.1.35, and more sophisticated workflow facilities including handling high volume transactions with exception cases, and reporting on system and individual performance. The latter may be provided by integrating a third party workflow product with the ERMS. Workflow technologies transfer electronic objects between participants under the automated control of a program. In the context of an ERMS, workflow is used to move electronic files and/or documents and records between users, departments and application programs. It is commonly used for: managing critical processes such as registration and disposition procedures of files or records; checking and approval of records before registration; routing records or files in a controlled way from user to user for specific actions, for instance check document, approve new version; notifying users of the availability of records; distribution of records; managing records through case work processes. RefRequirement Test The ERMS must allow workflows which consist of a number of procedural steps, each step being (for example) movement of a document, record or file from one participant to another for action or decision.Y The ERMS must recognise as participants both users and work groups.Y Where the participant is a work group, the ERMS workflow feature should include a facility to distribute incoming items to group members in rotation, or on a members completion of the current task, to balance team members workloads. Y The ERMS must allow pre-programmed workflows to be defined by administrative roles.Y The ERMS must allow administrative roles to save workflows for future use.YThis implies that each saved workflow is assigned a unique identifier. The ERMS should allow the administrative role storing the workflow to assign a unique textual title to it.Y The ERMS must restrict amendment of pre-programmed workflows to administrative roles, or authorised users. Y Whenever an administrative role changes and stores a workflow, the ERMS should store a copy of the workflow before the changes as a record, and should automatically assign a new version number to the changed workflow, with metadata specifying the date/time interval during which it was in effect.Y The ERMS must not limit the number of workflows which can be defined and stored. P The ERMS must log all creation of, and changes to, pre-programmed workflows in the audit trail.YThe ERMS should allow user roles to define, use and save immediately new, user-defined, workflows (sometimes called ad hoc workflows).Y The ERMS should include a graphical interface to enable administrative and user roles to define, maintain and edit workflows.Y The ERMS should support the disposition, review and export/transfer process, by tracking and reporting on: progress/status of the review, such as awaiting or in-progress, details of reviewer and date; records awaiting disposition as a result of a review decision; progress of the transfer process. Y The ERMS must notify an administrative role if a record or file within a workflow is scheduled for review or disposition.Y The ERMS must ensure that all records and files retain any links during a workflow process.P The ERMS should manage the files and records in queues which can be examined and controlled by administrative roles.Y The ERMS must allow user roles to initiate and use workflows defined by administrative roles.Y The ERMS must allow users to monitor the progress of workflows they initiate and in which they are participants.Y The ERMS should allow the automatic declaration of a document to be a step in a workflow.Y The ERMS should not limit the number of steps in each workflow.P The ERMS should be able to prioritise items in queues.Y The ERMS should include  HYPERLINK \l "Gl_Rendezvous" rendezvous processing.YThis requires the workflow to be paused to await the arrival of a related electronic document or record. When the awaited item is received, the flow resumes automatically.  The ERMS must support the definition of distinct workflow roles to different users.YExamples of these roles include: a workflow administrative role (having permissions to reassign tasks or actions to another user or workgroup); a supervisor role (having permissions to designate a workflow for exception handling in a specific case); ordinary workflow users or workgroups.These workflow roles are distinct from the ERMS roles set out in section 13.4. The ERMS should enable an administrative role to define the maximum number of steps in a workflow at configuration time.Y The ERMS should allow the administrative role defining a workflow to associate time limits with individual steps, and report items which are overdue according to these limits to a nominated user or administrative role. Y The ERMS should allow the administrative role defining a workflow to choose from a pre-defined list which actions shall be taken by the participants of the workflow.Y The ERMS should allow the administrative role defining a workflow to choose the participants: by name; by roles; by organisational units.Y Administrative roles should be able to allocate permissions to individual users so that they are able to reassign tasks/actions in a workflow to a different user or group.YA user may wish to send a file or record to another user because of the record content, because the assigned user is on leave, or for other reasons.  The ERMS should enable participants to view queues of work addressed to them and either should: allow the participants to select items for action; or present items for attention on a first-in-first-out basis; the option to be specified when the workflow is designed.Y The ERMS should provide conditional flows that depend on user input or system data to determine the direction of the flow.YIn other words, flows which take the record or file to one of a number of participants depending on a condition decided by one of the participants. For example, a flow may take a record to either a credit control participant or an order consolidation section, depending on input from a sales supervisor; or the flow may depend on the value of an order, as computed by the system. The ERMS should allow users to suspend a flow temporarily in order to be able to attend to other work, and to resume it later (including after logging off from the system).Y The ERMS must notify a user participant when a file or record(s) has been received in the users electronic in tray for attention.YMoReq2 does not specify whether this in tray is the participants e-mail account in tray, or separate from it. The ERMS should support tracking of files and records by the provision of bring forward (also referred to as tickler) facilities which enable a user to request a reminder to access the file or record on a future date. Y The ERMS must provide a mechanism to allow users to notify other users of records requiring their attention.YThis may use an existing e-mail system or a standalone or proprietary messaging system.  The ERMS should include the ability to trigger an instance of a specified workflow automatically when a record of a specified record type is received.YFor example, a loan application workflow can be triggered automatically by the receipt of a record with record type loan application form. The ERMS should allow the receipt, in specified folders, of electronic documents or records to trigger workflows automatically (the workflow being determined by the document type or other metadata value).Y The ERMS must provide comprehensive reporting facilities to allow authorised user and administrative roles to monitor quantities, performance and exceptions.Y The ERMS should support the capture of a workflow process as a record.Y When file(s) or record(s) have been processed using one or more workflows, the ERMS must allow users to determine the identifier(s) and the version(s) of the workflow(s) used.Y The ERMS must ensure that all access controls are maintained at all times.PIn other words, it must not be possible to configure any workflow to grant any access to any user that the user would not otherwise have. The ERMS should be compatible with the Workflow Management Coalition (WfMC) Reference Model.Y The ERMS should support the export of a standard workflow process or any of its constituent parts according to any standard XML schema(s).N The workflow audit trail should be integrated with the ERMS audit trail.Y The workflow audit trail must be unalterable.YCasework This section specifies requirements for the handling of case files in a MoReq2-compliant ERMS. See the glossary for a definition and explanation of case files. The term case file is defined in the MoReq2 glossary as a file relating to one or more transactions performed totally or partly in a structured way. In this context, structured means that the transactions follow rules that are (or that could be) documented, that they follow a consistent process (they do not allow for users to invent completely new parts of the process), and that they are repeated across many instances of similar transactions. The contents of the records in a case file may be structured (for instance completed online forms) or unstructured (for instance e-mail messages or scanned images of paper forms), in any combination; the key distinguishing characteristic of case files is that they result from processes which are structured, at least in part. Typical characteristics of case files are that: they are numerous; they are structured or partly structured; they are used and managed within a known and predetermined process; they need to be retained for specified periods, as a result of legislation or regulation; they have similar content and/or structure; they have a known opening and closing date; they can be opened and closed by case-workers (practitioners, clerical staff or data processing systems) without the need for management approval. Because case files are often structured, they generally contain several sub-files, usually configured by means of a template. They may also contain volumes. See section 3.3 for details of relevant functionality, all of which applies to case files as it does to other files. Case management frequently involves another business application system (for example a licence application processing system or an enquiry tracking system). It also often depends on workflows (as described in section 10.4). RefRequirement Test An administrative role must be capable of configuring the ERMS to allow at least one case worker role (see glossary), with the specific feature that case worker roles can have different access permissions for case work classes and non-case work classes.YIn many cases case workers will be able to create, open and close case files as part of their day-to-day business, but they will not have permissions to create, open and close non-case files. In non-case files this level of authority may be granted only to administrative roles. The ERMS should support an optional file titling mechanism, to be configured by an administrative role, which includes names (for instance persons names) and/or dates (e.g. dates of birth) or unique file identifiers as file names, derived and automatically validated from external lists.Y The metadata used for automatically constructing file titles (as in  REF BK2094 \n  10.5.2) must be mandatory metadata or suitable defaults should be provided when the titling mechanism is defined. If the underlying metadata values (for instance names, dates, etc.) which have been used to create the file title are modified, the ERMS should not automatically update the files title.Y The rules for automatically constructing file titles (as in  REF BK2094 \n  10.5.2) should be configurable to be different for different classes.YThe three requirements above can be appropriate for case files. Any list used for validation may be managed within the ERMS or may be external to it.Where a file title has been allocated automatically using a mechanism that incorporates metadata such as a persons name, dates of birth, etc. it is possible for this original metadata on which the title is based to be updated. For example, a persons name may change, a date of birth may have been entered incorrectly, etc. In these circumstances the file title based on the metadata should not be automatically modified to reflect the change as the file title may already have been used (e.g. in correspondence, registered on another system, etc.). Apart from the requirement that the file title is not automatically modified, MoReq2 does not mandate the possible outcomes. Several different outcomes are possible, including: the metadata change is ignored and the file title stays the same; an administrative role is alerted that the metadata has been changed, and the role is able to (optionally) update the file title; the user making the change is warned that the metadata has been used in the file title and asked to confirm the metadata change; the user making the change is prevented from updating the metadata and advised to forward the desired changes to an administrative role who is able to edit the metadata. The ERMS must allow the creation of case files by any user authorised as a case worker.Y The ERMS must allow users to access and open a case file by entering its case-specific file identifier.YIn most case files the file identifier, for instance title or reference number, will be provided by an external system. An interface should enable the user to validate a manually entered identifier against this. This is different from, and additional to, the system identifier and classification code. The ERMS must provide an Application Programming Interface (or comparable capabilities) to enable integration with other business applications. This must include at least the following functionality: the other business application to create, open and close ERMS case files; the other business application to provide the ERMS case file title; the classification code of a newly-created case file to be passed to the other business application; the other business application to pass records to be declared into the ERMS case files; the other business application to apply a retention and disposition schedule to an existing closed file; error handling in case either system initiates an action which is considered invalid by the other system.PIt is as if the business application should act as a normal user the ERMS should not differentiate between the two.MoReq2 does not specify the nature of the error processing. However, specific outcomes are identified in the following two requirements.  The ERMS must, upon receipt of an apparently invalid request from an external business application: not complete any invalid action; not result in a software failure in either the ERMS or the external application.Y The ERMS should, upon receipt of an apparently invalid request from an external business application alert an authorised user so that corrective action can be taken.Y Where the ERMS interfaces with another business application it must be possible for an administrative role to limit the other applications actions to one or more specified classes within the ERMSs classification scheme.YIn other words, it must not be possible for the other application to take any actions that affect classes, files or records beyond the class(es) for the case files. Where the ERMS interfaces with another business application it should be possible for a user to switch easily between the related files in both applications.NIn other words, a user that has used the features of the other business application to locate or identify a case or case file (for example, using the applications postal address look-up features to identify a specific case) must be able to open that case file in the ERMS easily, that is without having to re-type the case file identifier. Likewise, a user who has opened a case file in the ERMS (by browsing the classification scheme, by searching or by any other means) must be able to switch to the corresponding case information in the other business application in the same way. Where the ERMS allows another business application to create new case files it must be able to receive relevant file metadata from the other application.Y The ERMS must allow case files to be configured with metadata elements that are specific to case files.YFor example, a case file may need one or more metadata elements to indicate status or progress. The ERMS must allow users to retrieve, declare records into, and carry out all other valid actions on, case files by using a case file identifier instead of a classification code.PMost case files are identified by a unique case identifier such as an account number or a complaint number. Users must be able to work with these files simply by specifying this identifier, and without the need to use the ERMS classification code (though use of the code will remain possible). When the ERMS receives records with structured content from another business application, it should be able to extract metadata automatically from the records.Y When the ERMS receives records with structured content from another business application, it should be able to use the extracted metadata to declare the records into the appropriate file.YFor example, if an ERMS receives electronic claim forms from a benefits claim processing application, it should be able to extract the claimant identifier and form type, then use these to classify the forms to the correct case file (using the claimant identifier) and sub-folder (using the form type). The ERMS must ensure that all actions performed on any class, file, or record, whether by an authorised user or by another business application, are logged in the audit trail.Y The ERMS must be capable of producing reports on all actions performed on any specified file(s), whether by an authorised user or by another business system.Y The ERMS must be able to produce reports for administrative roles, showing at a minimum: the numbers of records declared into case files automatically from other business systems per time period; the numbers of records declared into case files manually per time period; the numbers of case files opened and closed automatically by other business systems per time period; the numbers of case files opened and closed manually per time period.YIntegration with Content Management Systems This section addresses the requirements for the integration of Content Management Systems ( HYPERLINK \l "Gl_CMS" CMSs) with ERMSs. Modern content management systems include most or all of electronic document management system (EDMS) functionality (see section 10.3); This section addresses only the CMS-specific functional requirements for an ERMS it does not describe the functional requirements for CMSs or EDMSs, and does not include sufficient functionality to make the ERMS perform tasks normally associated with CMSs. CMSs include and extend EDMS functionality across all forms of information (content), not just records. CMSs usually deal with different aspects of managing information than ERMSs. Common characteristics are: publishing information, often to websites or portals, and sometimes to several channels using different renditions; managing information that originates from several sources; reformatting information and/or migrating it to some different rendition(s); relating different versions, renditions and translations of documents to each other; managing components of documents. At the time of writing, the most frequent use of the term CMS, and the most frequent need for integration with an ERMS, is likely to apply to web publishing. However, this section is intended to allow for both web publishing and other sorts of CMS. Content management functionality may be provided by a CMS separate from the ERMS, or by an integrated package that provides both CRM and electronic records management functionality. For ease of explanation, this section describes MoReq2 requirements as if the CMS and ERMS are separate; this separation is not a requirement. The relationship between an ERMS and a CMS is shown, in highly simplified form, in figure 10.1.  Figure 10.1 This figure shows that: Copies of records can be passed from the ERMS to the CMS for processing (the processing usually involves editing, migrating to different renditions, and publication). Records can be passed from the CMS to the ERMS for capture. This can happen while information is being processed by the CMS, or after it has been processed and published. The records may include (though are not limited to) web pages, web sites, and new renditions of existing records. The CMS can also receive information from other sources, so the records it passes back to the ERMS can consist of a combination of information that originated from the ERMS and information from elsewhere. Note that the words can be passed to cover several possibilities: copies of the records are transmitted between applications; the records are stored in a repository that is common to the CMS and the ERMS, and only messages identifying the documents or records are transmitted between the applications; the records are stored in a repository that is common to the CMS and the ERMS, and both act on them without the need to transmit any information; In this section, the passing of copies may refer to any of these (or other such) scenarios. CMS technology is evolving rapidly, so organisations that require CMS integration must specify their individual requirements; reliance on this section alone is not likely to suffice. This section should be viewed as a starting point, to prompt further analysis. RefRequirement Test The ERMS must be able to receive as input from the CMS records, including specified metadata, and must either: automatically capture the records into the appropriate file(s) based on their metadata; or allow a user to specify the appropriate file(s).Y The ERMS must be able to capture as records CMS-specific components and file types, including: content management log files; style sheets.Y The ERMS must accommodate metadata required by the CMS in addition to the records management metadata specified by MoReq2.YFor example, a CMS may use metadata elements to store information needed for content management, such as: IP address; status; language; publication date; effective date; reason for change. The ERMS must be able to store these elements, even though they are not required for records management. It is not necessary for the ERMS to be able to store all the metadata produced or used by the CMS; only the elements specified at configuration time need be stored. The elements to be stored need to be determined based on business need.Note that this is a highly general requirement. It allows for a wide variety of functions to be carried out by the CMS then stored as metadata stored in the ERMS.  When a record is being passed from the CMS to the ERMS for capture, if that record is related to an existing record stored in the ERMS (for example, it is a different rendition or a translation of the existing record), the ERMS must not delete or change the existing record, but must instead store the new record.P When a record related to an existing record (as in  REF BK4299 \n  10.6.4) is being passed from the CMS to the ERMS for capture, the ERMS must automatically link the existing and the new records (as in  REF BK2113 \n  3.4.23).YThis will only be possible if the CMS passes, with the record, the identifier of the existing record, as a metadata value. If the CMS does not pass back this value, then the ERMS cannot fail a MoReq2 compliance test. When a record related to an existing record (as in  REF BK4299 \n  10.6.4) is passed from the CMS to the ERMS and then captured as a record, the ERMS should ensure that the metadata of the new record is, as far as possible, identical to that of the original record by binding it to the same metadata, with only such relevant differences in the metadata as are required to log the changes and actions of the CMS.N When documents are being passed from the CMS to the ERMS in the form of web pages, the ERMS should be able to capture a web page, or a set of web pages, declaring them as a single record.YThe ability to capture a set of pages as a single record may be useful in several circumstances, such as storing snapshot copies of a web site periodically.Capturing web pages is likely to require changes to the references (hyperlinks within the pages, hyperlinks to other web pages, and references to graphical or other components etc.) so as to allow the pages to appear correct and to retain as much as possible of their original functionality. This is unavoidable if web pages that include graphical elements, style sheets, hyperlinks etc. are to be stored in their original formats without losing all functionality and fidelity. The key aspect is that the information-providing content of the web page must not be modified. See requirements  REF BK4636 \n  6.1.5 and  REF BK4638 \n  6.1.6. When records are being received by the ERMS from the CMS, this must be logged automatically in the ERMS audit trail and in the records metadata.Y When a user is selecting records to copy from the ERMS to the CMS, the ERMS must allow the user to use any available CMS metadata values as a basis for selecting the records to be passed.YTo continue the example in  REF BK4265 \n  10.6.3, a user may select records in a specified class with specified values of  effective date and status. The ERMS must allow users to initiate the passing of copies of specified records, together with specified metadata, from the ERMS to the CMS.YThe metadata to be passed can be specified at configuration time. When records are being passed from the ERMS to the CMS, this must be logged automatically in the ERMS audit trail and in the records metadata.YElectronic Signatures Electronic signatures (sometimes referred to as digital signatures) consist of information that is attached to, or is logically associated with, other information, such as an electronic record, and which serves as a method of authentication. The electronic signature typically takes the form of a sequence of characters. It is used with secure algorithms, procedures and keys (a long string of characters analogous to a password) to confirm the integrity of a record, and/or to authenticate the identity of the sender or the source of a record. Electronic signatures should not be confused with a bitmap, or scanned image, of a manual pen and ink signature on paper this is not considered secure, and so is unlikely to add to the evidence about authenticity of a record. An electronic signature, as the term is used in MoReq2, is a form of advanced electronic signature as defined in the European Directive on a Community Framework for Electronic Signatures 1999/93/EC. An advanced electronic signature is one that meets the definition in the Directive, namely that the signature is: uniquely linked to the signatory; capable of identifying the signatory; created using means that the signatory can maintain under his sole control; linked to the data (e.g. record) to which it relates in such a manner that any subsequent change of the data (e.g. record) is detectable. Another, unrelated, standard for electronic signature frameworks is X.509 (see appendix 7). Examples of widely-recognised electronic signature algorithms are the Digital Signature Algorithm (DSA) as defined in FIPS 186-2 (see appendix 7) and RSA/SHA-1. E-mail has become the default means of communication for many organisations and this has resulted in the widespread movement of documents and records in relatively uncontrolled environments. The use of electronic signatures for authentication and integrity confirmation is therefore becoming widely adopted, especially where records of business transactions are involved. Electronic signatures are also used to provide non-repudiation repudiation refers to any act of disclaiming responsibility for a message. Non-repudiation provides proof of the integrity and origin of data which can be verified by any third party at any time. It prevents an individual or entity from denying having performed a particular action related to data such as approval, sending, receipt, knowledge (recognizing the content of a received message) or delivery (receipt and knowledge). The requirements in this section apply only where there is a requirement to manage records bearing electronic signatures. At the time of writing, electronic signatures are still subject to change and uncertainty as new infrastructures and algorithms are tested and introduced. This state of affairs is likely to continue. Users of MoReq2 should therefore confirm requirements and implications for long-term storage with appropriate authorities. There are no requirements in this section relating to individual countries legislation on electronic signatures. By way of illustration, some laws require that a signature be retained complete to have value, while others require only the retention of metadata about a signature. Where these are relevant they may be dealt with in a country-specific chapter zero. RefRequirement Test The ERMS must be able to capture, verify if required, and store, at the time of record capture, electronic signatures, associated electronic certificates and details of related certification service providers.YThis is essential as it will not always be possible to recreate this information at later times. The ERMS must enable administrative roles to configure the system, either at configuration time, or at a later date, to store verification metadata for electronically signed records, including public keys, with the record at time of capture in one of the following ways: the fact of successful verification; specified information regarding the verification process; all verification data.YThis is essential as it will not always be possible to recreate this information at later times. The ERMS should have a standards-based interface which permits the introduction of new electronic signature technologies as they are introduced.NAn example of a suitable standard basis is the XML Key Management Spec (XKMS, see appendix 7).This is especially valuable given the changes occurring in this area.  The ERMS should be capable of checking the validity of an electronic signature, including checking the certificate of a record at the time of capture against an electronic certificate revocation list and should store the result of the check in the records metadata. It should report any invalid check result to a specified user or administrator role.YThis is valuable as it may not always be possible to perform this check on the information at later times. When capturing e-mail messages the ERMS must be able to capture automatically, and preserve as metadata, details about the process of verification for an electronic signature, including: the fact that the validity of the signature was checked; the identity of individual initiating the check (where relevant); the certificate issuer; the serial number of the electronic certificate, verifying the signature; the certification service provider with which the signature has been validated; the date and time that the checking occurred.YThis is essential as it may not always be possible to recreate this information at later times. Because software changes, because certificates expire, and because external authorities can cease to exist, electronic signatures cannot be guaranteed to be verifiable over long periods; hence this requirement to log the fact that a signature was successfully verified. The ERMS should include features which demonstrate that the integrity of records bearing electronic signatures has been maintained.NAn example of this would be the verification of an electronic signature. This demonstration of integrity should apply even if an administrative role has made authorised changes to the metadata of the record. The way in which this might be achieved is not prescribed.  The ERMS should be able to store with the electronic record: the electronic signature(s) associated with that record; the electronic certificate(s) verifying the signature.Y It should be possible for the ERMS administrator to define whether the ERMS will store the validation ticket returned by the system that checked electronic signature.YThe validation ticket is sometimes referred to as a token. The ERMS should enable an administrative role to apply an electronic signature to a file or record or transfer message during an export or transfer process so that the files, records or transfer messages integrity and origin can subsequently be verified. YA transfer message is a message sent between application systems as part of the protocol used to manage transfers between the systems. An electronic signature applied during export or transfer (see  REF BK3314 \n  10.7.9) should be capable of external validation so that the file s, record s or transfer message s integrity and origin can subsequently be verified.YTo do this the ERMS must be capable of exporting an electronic certificate with the organisation s public key, with the record.Encryption Encryption is the process of applying a complex transformation to an electronic object so that it cannot be presented by an application in a readable or understandable form unless the corresponding decryption transformation is applied. This can be used to secure electronic objects, by use of transformations which require the use of secure electronic key codes. The requirements in this section apply only where there is a requirement to manage records which are encrypted. RefRequirement Test Where an electronic record has been sent or received in encrypted form by a software application which interfaces with the ERMS, the ERMS must be capable of restricting access to that record to users listed as holding the relevant decryption key, in addition to any other access control allocated to that record.Y The ERMS must be able to capture and store, at the time of record capture, information relating to encryption and details of related verification agencies.Y Where an electronic record has been transmitted in encrypted form by a software application which interfaces with the ERMS, the ERMS should be able to keep as metadata with that record: the fact of encrypted transmission; the serial number of an electronic certificate (where appropriate); the type of algorithm; the level of encryption used; the date and time of the encryption and/or decryption process, where applicable. Y The ERMS should be able to ensure the capture of encrypted records from a software application which has an encrypting capability.Y The ERMS should allow encryption to be removed when a record is imported or captured. This feature should be configured by an administrative role at configuration time or later.YThis feature may be desired in some large scale record archives which have a requirement for long-term access (because encryption etc. is likely to reduce the ability to read records in the long term). In this case, the organisation would rely on audit trail or similar information to prove that the encryption etc. had been present but has been removed. In other environments, this feature may be undesirable from a legal point of view. See sections 5.3 and 3.1 for more details on Transfer and Importing. The ERMS should have a structure which permits new encryption technologies to be introduced.NDigital Rights Management This optional module does not contain any requirements that are testable in their current form. As explained below, testing will be meaningful only when the requirements are adapted to specified technologies. Digital Rights Management (DRM) and Enterprise Digital Rights Management (sometimes abbreviated to E-DRM) constitute a not yet standardised set of technologies used to protect intellectual property and/or to restrict the distribution of information. DRM is generally associated with the protection of intellectual property (especially in the music, electronic publishing and film industries), while E-DRM is generally associated with placing restrictions on the distribution of business information, for reasons of security or commercial sensitivity. However, the boundaries are not firm and either may be encountered in the context of an ERMS. Accordingly, in the remainder of this section these technologies are referred to as DRM/E-DRM. Examples of DRM/E-DRM include: Electronic watermarking (also referred to as digital watermarking), which embeds visible information about intellectual rights ownership into electronic documents or records. The information is imposed in a complex manner that makes its removal difficult. Steganography, which similarly imposes information about intellectual rights, but in a way that is invisible or, in the case of an audio file, inaudible. Special software is required to read the intellectual rights information. Copy protection schemes, which use a variety of approaches to prevent copying. Features built into documents or records that allow them to be viewed on-screen but not to be printed. Expiry features built into documents or records that prevent them from being presented in any way after a specified date has passed. DRM/E-DRM technologies are at a relatively early stage of development. They are likely to change significantly during the expected lifetime of MoReq2. These, and similar technologies, can be applied to records in many formats, including digitised sounds and moving pictures. These technologies provide a particular challenge in records management as they may make future presentation of records difficult or, in some cases impossible. For example: Some forms of watermark rely on the presence of plug-in software in the viewing application to be wholly effective. A record with such a watermark may be viewable without the plug-in, but it will not be possible to obtain all the watermark information if the plug-in is not available. As time passes the likelihood increases that the plug-in will not be available. An e-mail message contains an expiry feature, and so will no longer be readable after a specified date. This problem is particularly insidious as it may not be apparent at the time the record is captured. At a minimum, user and administrative roles responsible for capturing and managing electronic records should be aware of any DRM/E-DRM features affecting records in the ERMS. Additionally, potential records management difficulties caused by these technologies can be minimised if the DRM/E-DRM features are removed from records at (or around) the time of their capture. However, both of these points are procedural issues, and therefore beyond the scope of MoReq2. The applicable technologies vary widely, and their effect on records varies equally widely. For this reason, it is not feasible to formulate generic requirements that apply to all the technologies. Therefore this section specifies some high-level requirements that must be expanded by users of MoReq2 if they are to be used for specification and procurement. So, for example, if time-related expiry features are expected, the requirements must be adapted to give specific requirements for dealing with the expiry features. RefRequirement Test The ERMS must be capable of capturing and storing records bearing DRM/E-DRM features. N The ERMS should be able to identify the presence of DRM/E-DRM features in a record at the time of capture. Where DRM/E-DRM features are identified, the ERMS should inform the user and provide the following options: keep the DRM/E-DRM features; remove DRM/E-DRM features if possible; stop the capture process.N The ERMS should be able to remove DRM/E-DRM features from records during capture.NThis may be mandatory in some environments, but cannot be mandatory in the general case as it would require an arbitrary ability to circumvent security features. If DRM/E-DRM features are removed this should be logged in the audit trail. The ERMS should include the ability to control access to records based on intellectual property restrictions, and generate charging data for such accesses.NThis brief statement encompasses a wide range of functionality which is beyond the scope of MoReq2. This requirement may be satisfied by providing the ability to link to a separate application. The ERMS must be capable of correctly presenting records with DRM/E-DRM features, to the extent that the DRM/E-DRM features permit.N The ERMS should be able to retrieve and store at the time of declaration, information stored in the DRM/E-DRM features, to the extent that the DRM/E-DRM features permit.NFor example, the identities of the owners of the intellectual property, as encoded in a watermark; or an expiry date.This may be mandatory in some environments, but cannot be mandatory in the general case as it would require an arbitrary ability to circumvent security features. The ERMS should allow new DRM/E-DRM technologies to be introduced.N The ERMS should be able to apply DRM/E-DRM features to records during export.NThis is especially desirable if a DRM/E-DRM feature has been removed.Distributed Systems This section comprises requirements for organisations that require an ERMS to operate in multiple locations. Many organisations operate from several sites. Where the sites are relatively close to each other geographically, or when the network connection between all the sites is good (with sufficient capacity), it may be that a single instance of an ERMS is most appropriate to cope with all sites. In these cases, all the sites operate as if they were co-located, and the requirements of this section need not apply. However, if the sites are widely separated, and/or if the connectivity between them is not good, then it may be necessary to implement a distributed ERMS; in that case the requirements in this section apply. There are several different architectural approaches to distributed systems. These include one instance of an ERMS controlling multiple repositories; several instances of an ERMS, each with its repository(ies), communicating with each other; and other approaches. MoReq2 does not specify an architectural approach; it specifies only the key requirements for such distributed environments and uses the term distributed ERMS to refer to any such architecture. RefRequirement Test The ERMS must be capable of being configured by an administrative role for use across multiple locations.N The ERMS should support a distributed classification scheme across a network of electronic record repositories. Y The ERMS must allow an administrative role to maintain classes, files, sub-files, volumes and records and their associated metadata and audit trails across the distributed ERMS such that maintenance operations can be carried out once to apply to the entire distributed ERMS.PMaintenance means performing transactions as specified in chapter 3, section 9.1 and elsewhere. Where the ERMS supports multiple repositories, it should allow an administrative role to specify which repository stores the master copy of each class (and its child classes, records classified to it, etc.).YFor example, an organisation may decide to implement one repository for each of its locations, with each locations records being stored in the locations repository (this assumes that the classification scheme design supports this configuration). Where the ERMS supports multiple repositories, it should allow an administrative role to specify which repository(ies) automatically store a copy of each class (and its child classes, records classified to it, etc.).YFor example, an organisation may decide that: all repositories have to be copied to the head office repository; in one territory, all repositories must be copied to each other.Note that this implicitly means that repositories need to be synchronised automatically. This includes the repositories: records and documents; metadata. Where the ERMS supports multiple repositories, it should allow an administrative role to specify which repository(ies) the users at each location can access.YFor example, an organisation may decide that: all users can access only the repository for their location; all users can access the repository for their location and the head office repository; all head office users can access any repository while all other users can access only the repository for their location; all users can access all repositories within their territory (i.e. within a specified set of repositories; this is not intended to imply that the ERMS has to recognise the concept of territory). Where the ERMS supports multiple repositories, it should allow an administrative role to specify that all audit trails will be copied to one repository.Y The ERMS must prevent or resolve any conflicts caused by changes made in different locations.PFor example, a potential conflict may arise if two administrative roles in different locations make a different change to the metadata of the same class which is stored in a third location. The ERMS must allow an administrative role to monitor both the entire distributed ERMS as a single entity and individual repositories, providing the same facilities as described in section 9.2.Y The ERMS should be able to produce reports (as specified in section 9.2) that cover multiple repositories.Y The ERMS should support caching of frequently and recently used files, sub-files, volumes and records accessed from locations using remote repositories.YThe following two requirements relate to the performance of the distributed ERMS. They use the convention of expressing variable quantities in angle brackets (for example ) as explained in the introduction to chapter 11. Where the ERMS synchronises repositories, they must be synchronised within of any change (subject to availability of network connections).N The ERMS must be capable of propagating any administrative change across all repositories within .NRequirements  REF BK3535 \n  10.10.12 and  REF BK3533 \n  10.10.13 are example requirements. MoReq2 does not specify response times as these will be system dependant. See section 11.2 for a full description.It is critical that the system architecture allows acceptable response times across all locations. Users of MoReq2 should consider specifying response times for many of the requirements specified in section 11.2 separately for transactions involving information held in remote repositories. Where the ERMS is capable of creating workflows across distributed systems, it must be able to interchange data across these systems to control the workflow process.Y Where the ERMS supports multiple repositories, and where master copies are stored in specified repositories (see  REF BK4318 \n  10.10.4, it should allow an administrative role to change which repository stores the  master copy of each class (and its child classes, records classified to it, etc.); when such a change is made, the ERMS must move the contents from the old location to the new location.YThis will be useful when creating or removing repositories, or when moving records to a different repository following geographical moves involving business functions Where the ERMS supports multiple repositories, it must allow an administrative role to add a new repository.Y Where the ERMS supports multiple repositories, it must allow an administrative role to remove a repository.YOffline and Remote Working The requirements in this section cover all types of mobile and offline usage of the ERMS by users who are not permanently connected to the ERMS (or to the network hosting it). There are several possible scenarios including: users who access the ERMS using portable computers (such as mobile, laptop, or notebook computers) or PCs that are connected to the ERMS intermittently; users who connect to the ERMS remotely through a dial up connection, or any other connection with low bandwidth connection (e.g. for telecommuting or in a temporary location); users who access the ERMS using other mobile devices such as PDAs or smartphones. Portable computers can be used as normal workstations when connected to the ERMS. However users may need to be able to download and synchronise records and data so that they can work on them whilst offline. To enable this functionality the ERMS needs to download not only records and aggregations but also their metadata. The ERMS will also need to synchronise all of the modified data when the user is next connected to the system. In a similar way, portable computers can be connected intermittently to the ERMS, for example when they are used by telecommuters. When they are connected, the portable computer will need to synchronise with the ERMS. Once again there will be the need to download records etc, with the downloaded data being managed on the portable computer in between synchronisations. PDAs, smartphones and other handheld devices can be used to view and access records, in many cases using a browser interface. Inherent limitations, such as a small screen and restricted performance, mean that in many cases such a device cannot offer the full functionality of a portable or fixed computer. However, such devices are often used for mobile e-mail, notes and calendar applications and there is therefore a necessity to synchronise these types of document with the central system. MoReq2 does not specify requirements to allow mobile or offline users to maintain the classification scheme (for instance the creation of new classes) and files (for instance closing a file). It may be possible to develop systems that support such maintenance, and MoReq2 does not prevent this. RefRequirement Test The ERMS should allow an administrative role to specify aggregations containing information that cannot be downloaded by any user.YThis is a security provision to protect sensitive information from being downloaded and hence placed beyond the control of the ERMS. The ERMS must enable a user to download any aggregation or record(s) with accompanying metadata for the user to work on whilst not attached to the network.Y The ERMS must log in its audit trail all activity on downloaded aggregations, records, and documents.Y The ERMS should note in the aggregation, record or document metadata that the entity has been downloaded for offline use.P The ERMS must enable the synchronisation of downloaded aggregations, records and documents upon connection to the system.YThat is, it must update the metadata and provide for conflict handling by prompting the user if a conflict occurs. The ERMS must update the audit trail with information on offline activity upon connection to the system.Y The ERMS must allow a user to capture documents created while offline then to capture them as records later when connected to the ERMS.YIf the record has been created offline then the ERMS must either: when re-connected, prompt the user in the synchronisation dialogue to declare it within the appropriate class, file, sub-file or volume; or: when re-connected, declare it automatically, using the class, file, sub-file or volume specified by the user while disconnected (subject to validation). The ERMS must apply all access and security controls to remotely connected devices.PThe ERMS must not provide any opportunity for portable devices to breach the security rules of the ERMS. For example, a user must not be able to download any information which he could not access online. However, MoReq2 recognises that once information has been downloaded to a device the ERMS loses control of it, and that security breaches in this scenario cannot be prevented by the ERMS.The following four requirements apply only where the ERMS supports electronic document management, as defined in section 10.3. They use terminology defined in that section. The ERMS must allow a user to download documents with accompanying metadata for the user to work on whilst not attached to the network.Y The ERMS must allow users the option of checking documents out when they are downloaded.Y If a user checks out a document and works on it while not connected to the ERMS, the system must allow version numbering to be applied to the document.Y If a user checks out a document and changes its version number while not connected to the ERMS, when the user reconnects to the ERMS it must allow the user to upload the revised document, and must at that time automatically check it in and record the changes and the new version number.YFax Integration While e-mail has taken over from facsimile as many organisations preferred method of rapid communication, there are still some occasions and some locations for which fax is required. This can be, for example, where the original document is not in electronic format and a copy needs to be sent to another organisation, or where a visible representation of, e.g., a signature is required. Some fax servers integrate with e-mail systems so that both incoming and outgoing faxes are dealt with as e-mail attachments. In this case the requirements in section 6.3 apply. Where an organisations ERMS is integrated with a fax service the following requirements apply. RefRequirement Test The ERMS should provide an application programming interface (API) to enable it to interface with a fax server.N The ERMS must be capable of storing faxes in standard formats, for example TIFF v6 image format with Group IV compression.YSee ISO 12033 for implications of compression methods. The ERMS must support the capture of faxes in an integrated way, so that the capture can be performed by a user from within the fax interface (if such an interface exists), without the user needing to switch to the ERMS.Y The ERMS must be tightly integrated with the fax interface to enable users to fax any electronic record that they are currently viewing or working with in the ERMS, from within the ERMS (so long as the record can be presented as a two-dimensional image).Y It must be possible for an administrative role to configure the ERMS so that it operates in one of the following ways when an ERMS user sends a fax: it automatically captures the fax as a record; it automatically prompts the user, giving the user an option to declare the fax as a record; it takes no action (and thus relies on the user to initiate declaration if appropriate).YRegardless of which way is chosen, it is acceptable for the ERMS to require the user to classify the record manually and enter metadata manually. It must be possible for administrative role to configure the ERMS so that it operates in one of the following ways when an ERMS user receives a fax: it automatically prompts the user, giving the user an option to declare it; it takes no action (and thus relies on the user to initiate declaration if appropriate).YRegardless of which way is chosen, it is acceptable for the ERMS to require the user to classify the record manually and enter metadata manually. The ERMS should be capable of automatically extracting fax metadata elements from incoming faxes, as specified in chapter 12, for example: title; sender; time and date; recipient.YThis may be accomplished by means of a fax template, and is only relevant where faxes have a predictable internal structure. The ERMS should be capable of automatically populating fax metadata elements for outgoing faxes, as specified in chapter 12, for example: title; sender; time and date; recipient.YThis may be accomplished by means of a fax template, and is only relevant where faxes have a predictable internal structure. The ERMS must allow a user who is capturing a fax to edit the title metadata element, in order to reflect the content of the fax.Y The ERMS should be capable of providing a fax record type for both inbound and outbound faxes to enable a user to enter metadata.YSecurity Categories Chapter 4 describes requirements for controlling access to aggregations and records by role and group. In some environments, such as those involving national security, healthcare, etc., there is a need to limit access further, using a scheme of security categories and security clearances. These  HYPERLINK \l "Gl_Clearance" clearances take precedence over any access rights which might be granted using the features defined in chapter 4. The requirements in this section apply only in organisations which have this need. This is achieved by allocating one or more Security Categories to classes, files, sub-files, volumes and/or records. The term Security Category is used in this specification to mean one or several terms associated with a record which defines rules governing access to it. Note that this term is used expressly for this specification; it is not generally employed. Users can be allocated a single security clearance which prevents access to all aggregations or records which have been allocated higher security categories. Security categories can be made up of sub-categories. Some sub-categories are hierarchical in nature. Other sub-categories may be arranged differently, typically in a way which is unique to an organisation or sector. MoReq2 describes in detail only the requirements for a hierarchical sub-category. The examples given here are based on national security markings but the same principles apply to markings used in other sectors. There can also be country-specific national security classification requirements. Where appropriate these can be addressed in chapter zero. RefRequirement Test The ERMS must allow one of the following options to be selected at configuration time: security categories are assigned to classes, files, sub-files and/or volumes (and not to individual records); security categories are assigned to individual records (and not to classes, files, sub-files and/or volumes); security categories are assigned both to individual records and to classes, files, sub-files and/or volumes.YSome organisations will wish to control sensitive records individually, while others will wish to control them at the class, file etc. level. The ERMS must allow an administrative role to specify, at configuration time, which roles can specify and change the security category of records and aggregations.YIn some organisations, only the information owners will have this privilege. In others, different roles, such as security reviewers or line managers (if such roles exist) will have these privileges. The ERMS must allow, but not necessarily require, security categories to be made up of one or more sub-categories. YFor example, a security category may be made up of three sub-categories, as in the following fictitious example:Security Class; Caveat; Descriptor.Each sub-category can be thought of as one dimension defining the security of information. So, in this example, any valid combination of the three sub-categories security class, caveat and descriptor can be applied to the record.  The ERMS must require controlled vocabularies to be defined and maintained by an administrative role, these vocabularies limiting the allowable values for each sub-categoryYFor example, the sub-categories might be as in the following fictitious example:Sub-category Allowable values Class Top Secret Secret Confidential Restricted Unclassified Caveat NATO Eyes Only WEU Eyes Only Descriptor Commercial Personnel Management Audit and Accounts In this fictitious example, the sub-category Security Class is hierarchic (see  REF BK2174 \n  10.13.6) while the other sub-categories are not. Requirements for hierarchic sub-categories are common; these are specified below. Requirements for non-hierarchic sub-categories can be complex and are specific to the sector in which they are employed; with the exception of requirements  REF BK2175 \n  10.13.5 and  REF BK4338 \n  10.13.7 they are not detailed here. The ERMS should allow specific implementations of complex or unique security rules.NThese may be provided by suitable application program interfaces. Examples of the need for these include a need to manage records using marking conventions not covered here such as IDO (International Defence Organisation) markings, or access restrictions for medical records.  For at least one sub-category, the ERMS must support a hierarchy of at least five levels, from unrestricted access at the highest level to highly restricted access at the lowest level.YThe sub-category security class in requirement  REF BK2176 \n  10.13.3 is an example of this.  Where a sub-category and the corresponding clearances are not hierarchical, the ERMS must allow one of the following options to be selected at configuration time: the ERMS must require a valid clearance to be entered for each new user; the ERMS must apply a default clearance for new users. An administrative role must be able to redefine the default clearance at configuration time or any other time.YIn other words, the clearances must be mandatory for users. Where the ERMS applies a default hierarchical clearance to new users (as in  REF BK4338 \n  10.13.7) it must apply a default clearance for new users that is the lowest level of clearance in the hierarchy (that is, the most restricted).Y The ERMS must restrict access to records (and classes, files, sub-files and volumes depending on the selection made for  REF BK2178 \n  10.13.1) to those users who have a security clearance equal to, or higher than, the security category.YNote that this clearance may not be sufficient to obtain access. Access to the electronic records may in addition be restricted to specified users, roles and/or groups, using features described in chapter 4. Where a sub-category is hierarchical, the ERMS must use one of the following modes of operation to assign a sub-category to new classes, records etc., selectable by an administrative role at configuration time (or any later time): the ERMS must apply a default value that is selected by an administrative role; the ERMS must use the parent aggregations value as a default; the ERMS must require an administrative role to enter a value.Y Where a sub-category is non-hierarchical, the ERMS must use one of the following modes of operation to assign a sub-category to new classes, records etc., selectable by an administrative role at configuration time (or any later time): the ERMS must apply a default value that is selected by an administrative role; the ERMS must use the parent aggregations value as a default; the ERMS must allow but not require an administrative role to enter a value.Y When a new hierarchical security category or subcategory is defined, the ERMS must apply a default value for all existing classes, records etc. that is the lowest level in the hierarchy; in other words, the default must grant the smallest amount of access permitted by the hierarchy.Y The ERMS should allow security clearance to be allocated to a role and inherited by users. Where a security clearance is inherited from a role, the ERMS must allow a different security clearance to be applied at the individual user level.Y If the ERMS supports security categories for both records and classes etc. (see  REF BK2178 \n  10.13.1), it should be capable of preventing a class, file, sub-file or volume from having a lower security category than any record within it.Y If a user attempts to capture a record that has a higher security category than the aggregation into which it is being captured the ERMS must notify the user so that appropriate action can be taken; the ERMS must allow at least the following actions (subject to their being enabled at configuration time): the security category of the aggregation is raised to that of the record; the user is denied permission to capture the record into the aggregation; the record is automatically sent to a specified user for action; the user is invited to create a new aggregation for the record, with default values of metadata taken from the original aggregation; and then to capture the record into the new aggregation, as one integrated process.Y An administrative role must be able to determine the highest security category of any record in any class, file, sub-file or volume by means of one simple enquiry.YIn some environments, this will be an important feature to aid manageability. Subject to support for requirement  REF BK2178 \n  10.13.1, an administrative role must be able to change the security category of a class, file, sub-file, volume or record.YSee also  REF Bk2351 \r \h  10.13.27. The ERMS should support routine, periodic, scheduled, review of security categories, where a review consists of: allowing a user (with appropriate clearance and permissions) to view specified records and their security categories; allowing the user to change the security categories.YMoReq2 does not prescribe how this is achieved. The ERMS must automatically hold a history of security category values, in the metadata of the records, classes etc. to which they apply.Y When a user changes the value of a security category (either during a review as in  REF BK2168 \n  10.13.18 or otherwise), the ERMS must allow the user to enter a reason for the change, and must store the reason with the history (as in  REF BK3519 \n  10.13.19) as metadata.YSee  REF BK4333 \n  10.13.2 for details of users allowed to change security categories. The ERMS must allow users who have clearance and permissions that allow them to see a record to see the current value(s) of its security category(ies) and any history (as in  REF BK3519 \n  10.13.19).Y The ERMS should support the allocation of a security category to a class, file, sub-file or volume, which is valid for a defined period of time, and should automatically downgrade the marking to the lowest level security category at the end of that period.Y The ERMS should support the allocation of a security category to a class, file, sub-file or volume, which is valid for a defined period of time, and should automatically downgrade the marking to a lower, pre-selected, security category at the end of that period.Y The ERMS should support notification to an administrative role of the expiry of a selected time period for which a security category has been allocated to a class, file, sub-file or volume, and allow the security marking to be reassessed and amended.YFor example the ERMS should send a notification at Date of Birth + x years. This is for use in medical records or for other data protection purposes. The ERMS must automatically log all changes to security category and sub-category values in the audit trail.Y The ERMS must not allow a user to apply a security category to a class, file, sub-file or volume that the user does not have access to.Y An administrative role must be able to change the security category of all records and child entities (subject to the option configured at  REF BK2178 \n  10.13.1) in a class, file, sub-file or volume in one operation.YThis is routinely required to reduce the level of protection given to records as their sensitivity decreases over time. The ERMS must provide a warning to an administrative role if any records are having their security category lowered, and await confirmation before completing the operation. YThis is especially valuable if the security category of an aggregation is being lowered below the level of records that are stored in it. The ERMS must automatically record the history, for example dates and details, of any changes to security category, in the metadata of the relevant class, file, sub-file, volume or record. YThe history must include, for each change made, the date, user, values before and after the change, and reason.Non-Functional Requirements Some of the attributes of a successful ERMS implementation cannot be defined in terms of functionality. In practice, non-functional requirements are important to success. This chapter brings these requirements together. The sections in this chapter list requirements for the following areas: ease of use (section 11.1); performance and scalability (section 11.2); system availability (section 11.3); technical standards (section 11.4); legislative and regulatory requirements (section 11.5); outsourcing and third party management of data (section 11.6); preservation and technology obsolescence (section 11.7); business processes (section 11.8). These non-functional requirements are often difficult to define, and, difficult to measure objectively. It is nevertheless valuable to identify them so that they can be considered, at least at a high level. Some are specific to EDRM, but several are generic to many kinds of IT system. In addition to this chapter, users of this specification will need to consider organisational needs in relation to current technical and operational standards. They will also need to consider the ERMS suppliers support services including documentation, customisation, training and consultancy. Organisations will need to add their own requirements in these areas, depending on their size and structure, physical characteristics and current technical operating environment. This section is intended as a checklist of aspects which users will need to consider. These specific requirements will need to be added to the generic requirements given in earlier sections. Some of the Example Requirements in this chapter use angled brackets to indicate that a user of the specification needs to enter a quantified value or some other application-specific information. For example, means that a user of the specification should enter a length of time, probably measured in minutes or hours, to suit the specific requirement. Similarly, <4 seconds> means that the specification user should specify a time interval; 4 seconds is here suggested as a starting point, for consideration. In the same way, alternative phrases are also found in angled brackets. So for example the phrase should be taken to mean every day, or every weekday, or on a specified number of days per year or similar as appropriate for the organisation. In all cases, xx may mean any number, no matter how large or small. Because the requirements are generic, and because different organisations will have widely differing requirements and priorities, the non-functional requirements in this chapter are not tested in the MoReq2 testing framework. The testable attributes that are given here are to be used as a guideline. Organisations and users of MoReq2 will need to analyse their requirements, set their priorities, and conduct their own tests in these areas. Ease of Use When considering non-functional requirements in developing an ERMS specification, these must include the degree of ease of use required, and how it is to be specified. This will depend on the kinds of user for whom the system is intended, and the amount of training that is to be undertaken. Examples of requirements for ease of use are listed below. RefExample Requirement Test The ERMS must allow an administrative role to configure how much of the classification scheme each user role or group of users is able to access.YFor example a user or group of users, e.g. caseworkers, may be limited to viewing a single class of the classification scheme or even specific files or sub-files.  The ERMS must provide online help throughout the entire system.Y The ERMS must present the classification scheme graphically in hierarchical form, and allow users to navigate it using the graphical representation.Y The online help in the ERMS should be context-sensitive. Y The ERMS should include help on use of the classification scheme, including, at a minimum, easy access to the description metadata for classes, files, sub-files and volumes. PThe ERMS should include a thesaurus to assist users in selecting terms for keywords, descriptions etc.YSee  REF BK2484 \n  11.4.1,  REF BK2483 \n  11.4.2 and  REF BK2813 \n  11.8.11 All error messages produced by the ERMS must be meaningful, so that users can decide how to correct the error or cancel the process.NIdeally, each error message will be accompanied by explanatory text and an indication of the action(s) which the user can take in response to the error.  The ERMS user interface should be suitable for users with the widest range of needs and abilities; that is, designed according to suitable accessibility standards and guidelines, and compatible with common specialised accessibility software. NSee appendix 7 for appropriate standards and guidelines. The ERMS documentation should be provided in a useful format such that users with widely differing needs and abilities are all able to use it.NSee appendix 7 for appropriate standards and guidelines. The ERMS must be easy to use and intuitive throughout. NEase of use may be assessed by a panel of typical users. The ERMS user interface rules and behaviour must be consistent across all aspects of the system including windows, menus and commands. These must also be consistent with the operating system environment in which the ERMS operates. PThe rules should be consistent with other mainstream applications already installed.  The ERMS must be able to display simultaneously multiple records and aggregations. Y The ERMS must support a graphical user interface.Y The ERMS must allow users to move, re-size and modify the appearance of the windows, and to save modifications into their user profile so that they take effect automatically each time the users log on to the ERMS.Y The ERMS must allow users to customise aspects of the graphical user interface. Customisation should include, but need not be limited to, the following changes: menu and toolbar contents; screen layout; use of function keys; on-screen colours, fonts and font sizes; audible alerts.Y The ERMS should allow users to select sound and volume of audio alerts, and to save modifications into their user profile.Y The ERMS must allow persistent defaults for data entry where desirable. These defaults should include: user-definable values; a fixed default value; values same as previous item; values derived from context, e.g. todays date, file reference, user identifier; as appropriate. P The ERMS must allow configurable drop down menus or pick lists of metadata element values for data entry.YThe content of these lists should be configurable by an administrative role. Frequently-executed ERMS transactions must be designed so that they can be completed with a small number of interactions (e.g. mouse clicks or keystrokes). P The ERMS should be tightly integrated with the organisations e-mail system in order to allow users to send records and aggregations electronically without leaving the ERMS. NFor example the user should be able to send from the ERMS mail client. The essence of this requirement is that the user must not have to switch to the e-mail application to send the record. Where requirement  REF BK2442 \n  11.1.20 is met, the ERMS should provide this by sending pointers or links to aggregations and records rather than copies, whenever an aggregation or record is sent to another user of the ERMS.NThere may be exceptions to this, for example, a remote user who does not have consistent access to the central repository.  The ERMS should indicate whether an e-mail message has an attachment.YFor example, by means of an icon. The ERMS should support user-programmable functions. YFor example, user-definable macros.  Where users have to enter metadata from records which are images of printed documents (e.g. scanned images), the ERMS should provide features to allow the use of optical character recognition to capture metadata from the image (zoned optical character recognition). YFor example, the user should be able to select a rectangle of the image that contains metadata such as a date or a title, then convert that image to a metadata value and insert it into the desired metadata element, all in one action. The ERMS should allow users to define cross-references between related records, both within the same aggregation and in different aggregations, allowing easy navigation between the records.Y When viewing or working with a record or aggregation (class, file, sub-file or volume) of records, whether as the result of a search or not, a user should be able to use ERMS features to find information about the next-higher level of aggregation of records easily and without leaving or closing the record.YFor example, when reading a record, the user should be able to find out what class, file, sub-file or volume it is in; if viewing file metadata, the user should be able to find out information about the class in which it is located.  The ERMS should allow a user who has access to a file or record to check whether another specified user, group or role has access to it.YThis is to permit users to specify a user, group or role explicitly. Thus a user can enquire about the rights of another user, in the context of a record or file, without needing to know that users group or role memberships. The ERMS should allow a user to mitigate the risk arising from an error in filing a record by allowing users to place a temporary lock on a record or file with a single click. This temporary lock should bar access to that file or record to all users save for administrative roles; and the ERMS should automatically inform an administrative role that the temporary lock has been applied, allowing the administrative role (and nobody else) to remove the temporary lock.YThis is to allow users to correct an error such as accidentally placing a sensitive record into an unsecured file, perhaps as part of a drag and drop operation. Because users are not able to delete, remove or change records, this requires administrative action.In order to prevent misuse of this facility it is important that users are given guidelines into the use of temporary locking and that administrative roles check that these are not being abused.  Users should be able to copy records from the ERMS into other working environments, such as a desktop folder, using drag and drop, without this action resulting in any change to the record or its metadata.PWhen a copy of a record is dropped into any other environment, it will be acceptable for it to lose its metadata (on the basis that most other environments do not support the MoReq2 metadata model). The ERMS should provide help which provides visual guidance.PFor example, including screen shots and/or animations showing users how to use system features. The ERMS should allow users to mark areas of the help system as favourite areas or similar, so that they can find them easily on later occasions.Y A user working with a file must be able to discover easily and quickly the keywords associated with that file.YIt must be possible to discover the keywords without having to leave the file, in a way that allows work with the file to be continued without interruption. The ERMS should allow users to define classes, files and records as favourites, so that they can find them easily on later occasions.Y The ERMS should allow users to send favourites to other users.YThe favourites can be sent be e-mail or by another mechanism.Performance and Scalability Users of this specification should consider the extent to which the ERMS provides response times in line with user expectations, and whether it is capable of serving the size of user population for which it is intended. Some considerations and example requirements are given below. The response times experienced by users will also depend on factors outside the ERMS, including: network bandwidth; network utilisation; network latency; configuration and utilisation of various server resources. This specification cannot address such external factors, other than to point out that they must not be ignored. Usually, tests in the live environment are needed to obtain a reliable view of performance. Accordingly, these requirements should be interpreted with a standardised understanding of response time. This understanding will vary from environment to environment, depending on the status of the infrastructure. For example, if the ERMS is being specified for an existing infrastructure, it may be appropriate to specify response time in terms of the time between receipt of a keystroke at the server, and the sending of the response; alternatively, if the ERMS is being specified for a new network it may be more appropriate to specify response time in terms of the time between keying a request at the workstation and receiving the response at the workstation. Specific requirements for offline and remote working are covered in section 10.11 and these example requirements will need to be further modified in these environments. The ERMS must be able to perform all functions and operate consistently to meet business and user needs as defined in the example requirements below. RefExample Requirement Test The ERMS must provide adequate response times to meet business needs for commonly performed functions under standard conditions, for example: <100%> of the total anticipated user population logged on and active; <100%> of the anticipated total volume of documents managed by the system; users performing a typical mix of transaction types at various rates; with consistency of performance over at least ten transaction attempts. N The ERMS must be able to return the results of a simple search (the hit list) within <3 seconds> and of a complex search (combining four terms) within <10 seconds> regardless of the storage capacity or number of files and records on the system.NIn this context, performing a search means returning a hit list (see  REF BK2273 \n  8.1.10). It does not include retrieving the records themselves.  The ERMS must be able to retrieve and display within <4 seconds> the first page of a record which has been accessed within the previous <xx> months, regardless of storage capacity or number of files/records on the system.NThis requirement, and that at  REF BK2463 \n  11.2.4, apply only to documents that can be presented in the form of pages. If the documents are unusually large, it may be necessary to extend the acceptable response time.The inclusion of within the previous months implies the use of a staged or hierarchical physical storage mechanism. See also the next requirement.This requirement is intended to allow for rapid retrieval of frequently-used records, on the understanding that frequency of use is typically correlated with recent use. The timescale is to be inserted by the organisation, based on an evaluation of the time after which the heavy usage of records decreases.  The ERMS must be able to retrieve and display within <20 seconds> the first page of a record which has not been accessed within the previous months, regardless of storage capacity or number of files/records on the system.NThis requirement is intended to allow for cases where a form of hierarchical storage management is used, where records used infrequently are stored on slower media than more active records, or stored near-line. The timescale is to be inserted by the organisation, based on an evaluation of the time after which the heavy usage of records decreases. For both this and the preceding requirement, if all the electronic records are stored using a single physical mechanism (i.e. without staged or hierarchic storage) then the phrase within the previous months is irrelevant and should be deleted.The ERMS must allow a single implementation of the system to have an electronic record store of at least or records, and to serve at least users simultaneously with the performance levels specified in this section.NEstimates of storage requirements and record and user population to be inserted by the organisation. Note that in large organisations, large volumes of records may accumulate in some cases this will extend into the billions of records.The ERMS must provide the performance levels specified in this section with volumes up to at least: classes; files per class; sub-files per file; volumes per sub-file; records per volume.NThese are indicative metrics only. Organisations should consider whether other similar metrics apply to their circumstances.It must be possible to expand the ERMS, in a controlled manner, to meet organisational growth up to at least users while providing continuity of service. NThe intention of this requirement is that expansion should be possible with only routine upgrades that do not result in major interruptions in availability.  The ERMS must support the above performance level, including routine maintenance of: roles, users and user groups; security categories; access profiles; classification schemes; databases; retention and disposition schedules; disposal holds; in the face of the anticipated levels of organisational change, without imposing undue systems down time or account administration overheads (see also chapter 9). NIn cases where performance requirements are strict, it may be necessary to quantify the anticipated levels of organisational change.  The ERMS must be scaleable and must be able to be used in small or large organisations, with varying numbers of differently-sized organisational units and across different geographical locations. NSystem Availability In many organisations the introduction of an ERMS and EDMS together will increase users dependence on the IT network to the extent that they will be unable to continue working if the ERMS and EDMS become unavailable. Accordingly, users of this specification who are procuring a system should make every effort to identify user requirements for availability, and then to specify these for the procurement. Example requirements for availability are given below. RefExample Requirement TestThe ERMS must be available to users: from to . NPlanned downtime for the ERMS must not exceed hours per . NThe definition of downtime may depend on the infrastructure and architecture. For example, in some environments, a failure caused by server hardware will be considered as a failure of the ERMS; in other environments such a breakdown will be considered as a different kind of failure, not attributable to the ERMS. A suitable definition needs to be agreed; as a starting point the following is proposed: The ERMS is considered to be down if more than of users are unable to perform any normal ERMS function and if this failure is attributed to any component of the ERMS other than the users workstation. Unplanned downtime for the ERMS must not exceed per . NIn a procurement it may be appropriate to request quantitative evidence about mean time to resolve problems support of this requirement.The number of incidents of unplanned downtime for the ERMS must not exceed per . NIn procurement, it may be appropriate to request quantitative evidence about mean time between failures in support of this requirement.In the event of any software or hardware failure, it must be possible to restore the ERMS to a known state (no older than ) within no more than hours of working hardware being available.NTechnical Standards The ERMS should comply with relevant de facto and de jure standards. Where possible, it is desirable that the ERMS should make use of open rather than proprietary interfaces. Users of this specification may need to specify requirements for standards covering: hardware environment (for server platforms and workstation environments); operating system environment (for server platforms and workstation environments); workstation (client) software architecture; user interface; relational database and interface; network protocol and network operating system; interchange standards; application program interface and developer kits. When using this specification for procurement, it will be necessary to add further details of the technical environment, including all ERMS interfaces (e.g. legacy systems, office systems) and any plans for change. Additionally, users of this specification will need to consider their individual requirements for standards: See appendix 7 for a definitive list of the standards used in this specification. RefExample Requirement Test If a monolingual thesaurus is implemented with the ERMS, it should comply with standard ISO 2788, Guidelines for the establishment and development of monolingual thesauri. Y If a multilingual thesaurus is implemented with the ERMS, it should comply with standard ISO 5964, Guidelines for the establishment and development of multilingual thesauri. Y The ERMS must support the storage of records using file formats and encoding which are either de jure standards or which are fully documented. PUsers may wish to specify file format and encoding requirements for their organisation. The ERMS should store all dates in a format compliant with ISO 8601, Data elements and interchange formats Information interchange Representation of dates and times. Y The ERMS should store all language names in a format compliant with ISO 639, Codes for the representation of names of languages.Y If the ERMS is to manage records in multiple languages or using non-English characters, it should be capable of handling ISO 10646 encoding (Unicode). YLegislative and Regulatory Requirements The ERMS must conform to legislative and regulatory requirements, which typically vary from region to region and between industries. MoReq2 does not address the need to maintain physical records. Such a need may or may not exist, according to the legislative and regulatory environment; where there is such a need, care needs to be taken to preserve integrity and usability of electronic and physical records taken as a whole. These issues should be addressed by appropriate organisational policies. The following requirements will require localisation, in a chapter zero. In addition, users of MoReq2 will need to consider requirements that are specific to their industry, market sector, etc. RefRequirement Test The ERMS must conform to locally-applicable standards for legal admissibility and evidential weight of electronic records. N The ERMS must comply with locally-applicable records management legislation. N The ERMS must not include any features which are incompatible with locally-applicable data protection, freedom of information or other legislation. N The ERMS must comply with any locally-applicable European, national or local regulatory requirements, guidelines or codes of practice for the industry, business function or sector. NOutsourcing and Third Party Management of Data Many organisations use external service providers to store and manage records. In some cases, these are records that are no longer active (or have low recall requirements) but which need to be retained for a legislative period demanded by legal/government stipulation, industry regulators or for long term preservation. Other organisations use Application Service Providers (ASPs) to manage active records as well as those that have been archived. Organisations send their documents or records invoices, customer correspondence, mortgage application documents etc. to be indexed and stored by the ASP. The documents are then available for retrieval and presentation by the organisations staff over the internet or through a wide area network. The management of electronic records by a third party requires that the contract with the service provider has clearly defined procedures and controls in place in order to meet regulatory requirements, adhere to best practice for legal admissibility of electronic records, and meet the business demands of the client for access and availability. The contract will need to include provisions that: the service providers management must be to a standard at least as good as that of the clients management of its records internally; the client will be able to recover the records from the service provider in the future, and still be able to continue the management of the records to the organisations standards and meet legal admissibility requirements. This sub-section draws heavily on ISO 15801 (see appendix 7). RefRequirement Test A contract or Service Level Agreement (SLA) must be agreed with the service provider detailing the services that are to be used.NAn SLA is a formal negotiated agreement between the client and the service provider. It records the agreed position regarding services, priorities, responsibilities, etc. Details of the procedures for the transfer of records from the client to the service provider, and from the service provider to the client, must be documented.NThis may use communication links between the sites to transfer files and records automatically on a daily or regular basis. The client must be satisfied that the link between the two sites is secure and the protocols are in place to check all records are received, and reports produced listing any discrepancy.  The service provider must be able to provide the client with copies of the audit trail of the processes for logging and storing of the records/files. N The service provider must demonstrate that the files/records and metadata stored can be easily transferred back to the clients ERMS without any loss of structure, metadata or content of the records.N The service provider must have procedures in place to allow the client to transfer individual files and records.N The service provider must be able to provide ready access to the managed records by the client. The service provider must either deliver a presentation of the record, or the original record to the client to a contracted agreed time and price.N The service provider should be able to provide the client with the ability to request, view and print records and or files from the clients office.NThis can be achieved, for example, by a network connection.  The service provider should be able to provide the client with the ability to request on-line the downloading or transmitting of records and or files between the clients ERMS and service providers storage facility.N The client should be able to request reports on the records held by the service provider and details of retention and disposition schedules etc. This facility should be provided on-line from the client s offices. N Services specified in requirements  REF BK2500 \n  11.6.7,  REF BK2499 \n  11.6.8 and  REF BK2498 \n  11.6.9 should: have contracted response and/or turnaround times; operate in a secure environment. N The client should check that the proposed location of the work is acceptable and that the location meets security criteria appropriate to the clients needs. N The client should check that the proposed procedures and storage management processes involve no greater risk to the records than the clients own procedures.NThe service provider will need to demonstrate that all the clients records are backed up and in the event of system failure they can be recovered to a contracted timescale.  The client should check that the service provider will provide suitable operational staff where the security of the records is important.NIt is an advantage if all employees of the service provider sign a confidentiality agreement as part of their conditions of employment. Each shipment of records to/from the client and the service provider should be accompanied by a control document stating the identity and number of records and files.N Third parties providing transportation services should be organisations that meet the quality and reliability criteria of the client. NLong Term Preservation and Technology Obsolescence Background Electronic records held over a long term face technological risks from three directions: media degradation; hardware obsolescence; format obsolescence. These are discussed briefly below. More detailed consideration is found in ISO 18492, and in a large number of guidance publications produced by cultural memory institutions and others. Media Degradation The risk from media degradation arises because all digital storage media have a limited lifetime. The lifetime varies between media, and also according to environmental conditions. The following precautions can be taken to avoid loss of information due to media degradation: ensure all media is stored, used and handled in suitable environmental conditions; routinely replace media (by copying information from them to fresh media) before the expected end of life; keep several copies of each record, and systematically compare the copies periodically. This approach is typically used in specialist long term data archives; it requires automated systems, further description of which is beyond the scope of this specification. Hardware Obsolescence Storage peripherals tape drives, disc drives have a limited life expectancy. As they near or exceed this life expectancy, they typically require more maintenance, while at the same time becoming expensive to maintain and repair; eventually they become unrepairable for practical purposes. Information stored on obsolete devices will be lost permanently when the device fails unless it has been copied onto other media. Format Obsolescence Format obsolescence presents the most difficult problem for any period longer than a few years. The problem arises because the many protocols and software components involved in the processing chain between media and presented information are constantly evolving. They include encoding standards, file formats, and software. Their evolution is rapid, and often does not retain compatibility this is especially true over periods longer than a few years. Currently, the following techniques are recognised: migration (converting information to new formats which can be accessed by current hardware and software); emulation (moving the information to new hardware but with a additional software component which emulates the old hardware, thus allowing execution of the old application software); technology preservation (continual maintenance of the original hardware; not practical in the long term); encapsulation of data and software (a theoretical approach which is involves packaging together records, metadata, ERMS and other software in a standard software wrapper). There is at the time of writing no simple, generic method which will guarantee long term access to electronic records. The consensus is that: the most appropriate strategy is to hold information only in widely-accepted, stable, open formats (i.e. formats which are comprehensively documented in publicly-available specifications) which have a long expected life, such as XML and PDF/A; migration and/or emulation are likely to be the safest options; in practice, both will require attention to preservation metadata see below. The requirements in this section support these approaches. Further sources of information are given in appendix 7. Specific Requirements RefRequirement Test The ERMS storage media must be used and stored in environments which are compatible with the desired/expected lifespan, and which are within the tolerance of the media manufacturers specification.N The ERMS must support the monitoring and replacement of storage media to guard against media degradation.YThis requires the ERMS, or the storage sub-system it uses, to report on media error rates and to permit the replacement of media that is faulty or that is nearing the end of its life, without compromising the records. The ERMS should include features for the automated periodic comparison of copies of information, and the replacement of any copy found to be faulty, to guard against media degradation. P The ERMS must allow the bulk migration (rendition) of records (together with their metadata and audit trail information) to new media and/or systems in line with the standards relevant for their format(s).Y The ERMS supplier must have a system upgrade programme in place to ensure that the existing information can continue to be accessed without changes to the content. N Any system modifications that have been made to the ERMS for organisational requirements must remain in place following a system upgrade.N The ERMS should be able to report on the file formats and versions of components.YFor example, the ERMS should be able to produce lists of components in specified file formats. This facility would be used in conjunction with a software intelligence, or preservation monitoring, function that aims to identify file formats that are at risk of obsolescence. The ERMS should be able to render (see glossary) records from their original format(s) to any specified long term preservation file format(s) at the time of capture, at any subsequent time, or on export.PIt is acceptable for the rendering process to be undertaken by a program external to the ERMS so long as the context and links are maintained at all times. Wherever possible without compromising the integrity of the records, the ERMS should be able to render components from their original format to any specified long term preservation file format(s) at the time of capture, on a subsequent occasion, or on export.PIt is acceptable for the rendering process to be performed by a program external to the ERMS so long as the context and links are maintained at all times.Where components are rendered, it is essential that the integrity of the records that they form is maintained. The feasibility of this approach generally will depend on the capabilities of both the rendition process and of the software application or viewer used to present the records. For example, if the records are web pages that include (say) GIF image files, it would be acceptable to render the GIF images alone only if the following are all true:the GIF components are rendered to a file format that can be presented by the application used to access the web pages; in this example, it is likely that JPEG would be suitable;the references to the GIF images in the web pages are amended as part of the migration process so that they refer instead to the new JPEG images;the original components (the unamended web pages and unrendered GIF components are retained alongside the new components.The ERMS must at least support all these actions, and should at best perform them automatically.This example is chosen solely for illustration; it does not indicate that there is any reason to migrate GIF images at the time of writing. Whenever records or components are rendered, the ERMS must allow the administrator performing the rendition to enter a reason.Y When a record has been rendered into a preservation file format, the ERMS must provide suitable facilities to retrieve the original format and/or renditions, as appropriate.PSee also  REF BK4028 \n  5.2.3. The ERMS should be able to export records and their metadata in the form of a Dissemination Information Package as defined in Appendix 7 of the OAIS standard, ISO 14721.Y The ERMS should hold at a minimum the following metadata items for a rendered component: the original file format and version; date of rendition.Y The ERMS should be able to extract from a component, and then store as metadata, technical metadata stored in components.PThis metadata would be in addition to the metadata specified in the MoReq2 metadata model. For example, it might include technical; details of an image, such as the TIFF v6 formats metadata or the byte order (little endian or big endian), image length, and image width. If the ERMS uses any proprietary encoding or storage or database structures, these must be fully documented, with the documentation being available to administrative roles.YThis implies it may not be sufficient for the supplier to retain a copy of the documentation; in the timescale being considered, the stability of the supplier is not assured. It may therefore be desirable for a copy of this documentation to be lodged with the user organisation or with a neutral party.  The ERMS should be able to manage a range of preservation metadata elements for the records and their component parts. PSee appendix 9. The source code of the ERMS should either be open, or a copy of the source code should be lodged in escrow with a neutral party.NBusiness Processes Experience has shown that the success of ERMS installations depends, among other factors, on whether it is compatible with the way people work in real life situations. Even if an ERMS contains all the features needed for records management, document management etc., an implementation will only succeed if users find it easy to use. If users find it difficult to use, it will be rejected despite its capabilities. In recognition of this finding, this section describes requirements intended to promote flexibility and ease of use. Accordingly, most of the requirements are desirable rather than mandatory. The requirements may be met by workflow software that is integrated with the ERMS. Some of the requirements below call for the ability to perform a specified function as an integrated part of a process. In all cases, this means that a user who is performing a process should: have the option of performing the process, or of not performing it; be able to initiate the function easily, preferably with a single click, and without needing to re-enter information that has already been entered; be able to choose, at the end of the function, either to cancel the original process or to return to it at the same point and with the same status as before the function was initiated (without needing to re-enter information that has already been entered). This is illustrated in figure 11.1.  Figure 11.1 All of the following requirements are to be interpreted as being dependent on user access rights. RefRequirement Test The ERMS should allow a user who is allowed to change the security category of any record, file or class to check its existing category and permissions as an integrated part of the process of changing it.Y When an administrative role user is warned about the lowering of a security category of a record (see  REF Bk4177 \r \h  10.13.28) the administrative role should be able to examine the record and/or its metadata as an integrated part of the process.Y Whenever a new file or sub-file or volume is created, and where a physical container exists for it, the ERMS should allow the user to print an appropriate label for the physical container, as an integrated part of the process.YThis enables a label to be produced containing essential metadata which can then be attached to the physical entity. This could include, but is not limited to, such metadata as: Title; System Identifier; Classification Code; Date of Opening; Security Category (if used); Normal storage location. Whenever a user deleting any information receives a warning about existing links (see section 9.3) the user should be able to examine the links and the linked information and/or its metadata as an integral part of the process.Y The ERMS should allow a user who is redacting a record, to achieve the following in a single integrated process: create a redaction; decide where in the classification scheme the redaction should be filed, and declare it as a record; link the redaction to the original record; link the original record to the redaction.Y When a user is declaring a record, the ERMS should allow the user to check whether a document has already been declared as a record, as an integrated part of the process.YThis should apply to any kind of document. The ERMS should warn a user who is capturing a document as a record if that document has already been captured, informing the user of where it is allocated (class, file etc.) and giving the user the option to continue with or abandon the capture.Y When a user is capturing a record, the ERMS should allow the user to: browse the classification scheme (to find the desired class, file etc); look at the metadata (permissions, keywords, descriptions etc) of any classes and files; before the capture is completed, as an integrated part of the process.Y Whenever a user sees any class, file, record etc. on screen, as the result of a search, while browsing the classification scheme or in any other context, the user should be able to perform any valid action on it directly, without needing to navigate to another part of the ERMS, including at least: opening it; determining its parents in the classification scheme; viewing its metadata or audit trail; viewing and following its links; sending it by e-mail; changing its security category; viewing users and roles allowed access to it; printing (or presenting) it; redacting it; relocating or deleting it.Y The ERMS should allow an authorised user to change the security category of any record, file or class, including the updating of all affected metadata element values, in a single process.Y If a thesaurus compliant with ISO 2788 or ISO 5964 is integrated with the ERMS, the ERMS should allow a user who is entering or updating a keyword value (or other metadata element value related to the thesaurus) to use the full features of the thesaurus, such as broader, narrower and related terms and synonyms as an integrated part of the process.YNote that  REF BK2817 \n  8.1.18 contains a related requirement for searching.Metadata Requirements This chapter presents functional requirements for managing metadata. The MoReq2 metadata  model is presented in appendix 9. Section 12.1 covers the principles of metadata and section 12.2 lists the general metadata requirements. Metadata includes, in the context of this specification, indexing information and other data needed for effective records management, such as access restriction information. A formal definition is given in the glossary. A more detailed explanation of the role of metadata in records management is found in ISO 23081 (see appendix 7). Principles Scope It is not possible to define here all the metadata requirements for all possible kinds of ERMS implementation. Different kinds of organisations and applications have particular needs and traditions which vary enormously. For example, some organisations will need indexing focused on account names and transaction dates, while others will need strict hierarchical numbering; some will need volumes, which relate to financial years, while others will not; some will need access controls for security reasons, others for intellectual property reasons, and so on. This chapter of MoReq2 therefore suggests minimum requirements which are intended as the starting point for customisation and expansion. These minimum requirements are closely related to lists of specific metadata elements which the ERMS must be able to capture and process. These elements make up the MoReq2 metadata model in appendix 9. General Metadata Requirements RefRequirement Test The ERMS must not present any practical limitation on the number of metadata elements allowed for each entity (e.g. class, file, sub-file, volume, record). PThe definition of practical limitation will vary according to the application. For example, some organisations with a simple classification scheme may not need as many metadata elements as other organisations with a complex classification scheme. Where the contents of a metadata element can be related to the functional behaviour of the ERMS, then the ERMS must use the contents of that element to determine the functionality.PFor example, where the ERMS stores file opening date metadata, it must populate that metadata automatically whenever a file is opened rather than requiring a user to populate it. Note that this is a general requirement which stretches across many metadata elements. MoReq2 does not attempt to identify all cases in which this is relevant. The ERMS must allow different sets of metadata elements to be defined for different record types at configuration time. YFor example: invoices may need account number metadata; correspondence needs multi-value recipient metadata elements; records which are scanned images will need metadata relating the scanning and indexing processes. The ERMS must allow an administrative role to define at configuration time whether each metadata element is mandatory or optional.Y The ERMS must support at least the following metadata element formats: alphabetic; alphanumeric; numeric; date; logical (i.e. YES/NO, TRUE/FALSE).Y The ERMS should support metadata element formats, definable by an administrative role, which consist of combinations of the formats in  REF BK2540 \n  12.2.5.YFor example, a case might have a reference number in the format nnnnn/aa-n.  The ERMS must support date formats defined in ISO 8601 for all dates.Y At time of configuration, the ERMS should allow definition of the source of data for each metadata element.YPossible sources are described in requirements  REF BK2531 \n  12.2.9,  REF BK2530 \n  12.2.10,  REF BK2529 \n  12.2.11 and  REF BK2521 \n  12.2.13. The ERMS must allow an administrative role to specify which metadata element values are to be entered and maintained by manual entry or from selection from a controlled vocabulary. Y The ERMS should allow for the values of metadata elements to be inherited automatically by default from the next higher level in the classification scheme hierarchy.YFor example, for a volume, the value of some of the metadata elements must be inherited from its parent sub-file; and for a record, the value of some metadata may be inherited from the volume into which it is stored.  The ERMS should allow values of metadata to be obtained from lookup tables or from calls to other software applications.YFor example, the ERMS might provide name and post code to an addressing application which then returns a street name to be used as metadata. Where the metadata element is populated by lookup tables, if the selection of a value excludes other values in subsequent lookup tables, this should be reflected in the values shown to users in those subsequent tables.Y The ERMS should be able to acquire metadata values from: a document-creating software application (see  REF BK2833 \n  6.1.12); operating system; network software; the user at the time of capture or declaration; rules defined at configuration time for generation of metadata by the ERMS at the time of declaration.Y The ERMS must be able to validate metadata when it is entered by users, and when it is imported. The validation must use at least the following mechanisms: format of the element contents; range of values; validation against a list of values maintained by an administrative role.YAn example of format validation is that the contents are all numeric, or are in a date format (consistent with  REF BK2540 \n  12.2.5). An example of range format validation is that the contents fall in the range between 1 January 1999 and 31 December 2001. An example of validation against a list of values is verifying that an export destination is present on a list. The ERMS must be capable of validating metadata using calls to another application (for instance to a personnel system to check whether a personnel number has been assigned, or to a post code database system) or using an internal look-up table. Y The ERMS must allow an administrator role to configure the validation (as specified in  REF BK2528 \n  12.2.14 and  REF BK2527 \n  12.2.15) to be applied to each metadata element.YDifferent metadata elements will require different validation. So, for example, dates will call for format and range validation while descriptions will not need any validation. For metadata element values that are entered manually, the ERMS should allow an administrator role to configure the element so that it supports one of the following data entry modes: persistent user-definable default values; a fixed default value; todays date (for date elements only); blank element. Additional modes for data entry, not specified above, may also be supported.YA persistent default appears as the default in the data entry field for each item in succession until it is changed by a user. Once changed, the new value remains, i.e. becomes persistent. It should persist at least until the end of a session and ideally between sessions. This applies to all entities for which users may enter metadata values.  The ERMS should allow configuration such that any metadata element value can be used as a search field in a free text search.Y Where a metadata element value is stored in date format, the ERMS should allow searches which recognise the value of the date. YFor example, the ERMS should support searches in a date range. It is not sufficient for the date to be stored as a text field. Where a metadata element value is stored in numeric format, the ERMS should allow searches which recognise the value of the number.Y The ERMS must allow administrative roles to restrict the ability to make changes to metadata values as defined in the access control model (section 13.4). Y The ERMS must allow reconfiguration of the ERMS metadata model by an administrative role, and must log such in the audit trail.PFor example, it may be necessary to add a new data element such as Department Identifier to some document types following an organisational change. The ERMS must allow metadata elements to be configured at configuration time such that values generated from other application packages, the operating system or the ERMS (for example, e-mail transmission data) cannot be modified by users once they have been captured.Y The ERMS must allow metadata elements to be configured at configuration time such that their values cannot be modified by users once they have been captured.YReference Model This chapter provides the reference model for the requirements listed elsewhere in MoReq2. The sections in this chapter are: Glossary (section 13.1); Entity Relationship Model (section 13.2); Entity Relationship Narrative (section 13.3); Access Control Model (section 13.4) Glossary This glossary defines key terms used in MoReq2. Some significant definitions are taken from, or closely adapted from, glossaries presented in the reference publications listed in appendix 1; these sources are acknowledged below each definition. Terms defined within this glossary are shown in italics.  HYPERLINK \l "T_AdministrativeRole" administrative role A set of functional permissions allocated to users allowed to perform administrative actions. Note: in MoReq2 this term is used also to specify the people with these permissions.  HYPERLINK \l "T_Administrator" administrator A role responsible for the day to day operation of the corporate records management policy within the organisation. Note: this represents a simplification. Especially in large organisations, the tasks attributed in this specification to Administrators may be divided between several roles, with titles such as Records Manager, Records Officer, Archivist etc.  HYPERLINK \l "T_Aggregation" aggregation (in the context of MoReq2 only) A class, file, sub-file or volume.  HYPERLINK \l "T_AuditTrail" audit trail Information about transactions or other activities which have affected or changed entities (e.g. metadata elements), held in sufficient detail to allow the reconstruction of a previous activity. Note: an audit trail generally consists of one or more lists or a database which can be viewed in that form. The lists can be generated by a computer system (for computer system transactions) or manually (usually for manual activities); but the former are the focus of this specification.  HYPERLINK \l "T_Authenticity" authenticity (in the context of records management only) The quality of being genuine. Source: Adapted and abbreviated from the definition of record authenticity in the UBC-MAS Glossary (appendix 1). Note: an authentic record is one that can be proven a) to be what it purports to be, b) to have been created or sent by the person purported to have created or sent it, and c) to have been created or sent at the time purported. Source: ISO 15489. Note: in the context of a record, this quality implies that a record is what it purports to be; it does not address the trustworthiness of the records content as a statement of fact.  HYPERLINK \l "T_AuthorisedUser" authorised user A user who has permission to carry out the action be described. Note: the details depend on the context. Different users will have different permissions. MoReq2 does not assume anything about which users or which roles have which permissions. The permissions that authorise a user to carry out an action are granted by the organisation, according to its policies and business requirements.  HYPERLINK \l "T_BulkImport" bulk importing The process of capturing a set of electronic records, usually from another application and usually with some or all of their metadata.  HYPERLINK \l "T_Capture" capture (verb) (1) The act of recording or saving a particular instantiation of a digital object (source: InterPARES 2 Project Terminology Database). (2) Saving information in a computer system. Note: in the context of MoReq2, capturing records is used to mean all of the processes involved in getting a record into an ERMS, namely registration, classification, addition of metadata, and freezing the contents of the source document. The term is used more generally to mean inputting to the ERMS and storing other information such as metadata values.  HYPERLINK \l "T_CaseFile" case file A file relating to one or more transactions performed totally or partly in a structured or partly-structured way, as a result of a concrete process or activity. Note: there is no universally-accepted definition of these terms, nor of the distinction between case files and the other kinds of files often managed by an ERMS. This definition is therefore developed for, and intended to facilitate the understanding of, MoReq2; its applicability in other situations is not guaranteed. Note: the records in a case file may be structured or unstructured. The key distinguishing characteristic of case files is that they result from processes which are at least partly structured and repeatable. Examples include files about: applications for permits; enquiries about a routine service; investigation of an incident; regulatory monitoring. Note: typically, other characteristics of case files are that they often: feature a predictable structure for their content; are numerous; are structured or partly structured; are used and managed within a known and predetermined process; need to be retained for specific periods, as a result of legislation or regulation; can be opened and closed by practitioners, end-users or data processing systems without the need for management approval.  HYPERLINK \l "T_CaseWorker" case worker A user who works with case files.  HYPERLINK \l "T_Class" class (noun) (in MoReq2 only) The portion of a hierarchy represented by a line running from any point in the classification scheme hierarchy to all the files below it. Note: this can correspond, in classical terminology, to a primary class, group or series (or sub-class, sub-group, sub-series etc.) at any level in the classification scheme. Note: in MoReq2 class is also used to mean all the records allocated to a class.  HYPERLINK \l "T_Classification" classification In records management, the systematic identification and arrangement of business activities and/or records into categories according to logically structured conventions, methods, and procedural rules represented in a classification system. Source: ISO 15489 (see appendix 7).  HYPERLINK \l "T_ClassificationCode" classification code An identifier given to each class in a classification scheme. Within each class, the classification codes of its child classes are unique.  HYPERLINK \l "T_ClassificationScheme" classification scheme (In MoReq2) A hierarchic arrangement of classes, files, sub-files, volumes and records.  HYPERLINK \l "T_Clearance" clearance See security clearance.  HYPERLINK \l "T_Close" close (verb) The process of changing the attributes of a file, sub-file or volume so that it is no longer able to accept the addition of records.  HYPERLINK \l "T_Closed" closed Describes a file, sub-file or volume which is no longer open and so cannot accept the addition of records.  HYPERLINK \l "T_CMS" CMS Content Management System.  HYPERLINK \l "T_Component" component A distinct bit stream that, alone or with other bit streams, makes up a record or document. Note: this term is not in general use. Note: the phrase distinct bit stream is used to describe what is usually called a file in information technology; the word file is avoided here to prevent confusion with the records management meaning of file. The key concept is that a component is an integral part of the content of a record, despite the fact that it can be handled and managed separately. Note: examples of components include: An HTML document and JPEG images that make up a web page; A word processing document and a spreadsheet, where the record consists of the word processing document that contains an embedded link (a hyperlink) to the spreadsheet. Note: components have to be distinct, i.e. separate from each other. If a word processed document contains an embedded spreadsheet (as opposed to an embedded link to a spreadsheet) then the spreadsheet is not considered to be a component; in this case, the word processed document complete with its embedded spreadsheet is a record made up of one component. Note: an e-mail message with attachments may be one component, as several components, or as several records, depending on the format in which it is stored. If the message is stored in a format that includes the body and all its attachments, then there is only one component. If the attachments are stored separately from, and linked internally to, the body of the e-mail message, then each attachment and the body of the message is a component. If the attachments are stored separately from the body of the e-mail message but they are not linked internally, then each attachment and the body of the message is a separate record; good practice suggest that these records should be linked to each other manually.  HYPERLINK \l "T_ConfigurationTime" configuration time The point in the lifecycle of the ERMS at which it is installed and its parameters are established.  HYPERLINK \l "T_Custodian" custodian (of a record or aggregation) the person or organisational unit having possession of the record(s).  HYPERLINK \l "T_Destruction" destruction Process of eliminating [] records, beyond any possible reconstruction. Source: ISO 15489 (see appendix 7). Note: Depending on system configuration, this may be the same as deletion, or different from deletion. Note: This is not intended to imply overwriting of destroyed data or other security measures. Such additional security measures can be implemented but are not required by MoReq2.  HYPERLINK \l "T_Digital" digital Describes information made of distinct digits or numerical values rather than continuously variable values. Note: this term is not used in MoReq2 to describe records. Although digital record is more accurate than electronic record, the former is rarely used in practice. See electronic.  HYPERLINK \l "T_DisposalHold" disposal hold A rule that prevents the destruction or transfer of records.  HYPERLINK \l "T_Disposition" disposition Range of processes associated with implementing records retention, destruction or transfer decisions which are documented in retention and disposition schedules or other instruments. Source: ISO 15489 (see appendix 7).  HYPERLINK \l "T_Document" document (noun) Recorded information or object which can be treated as a unit. Source: ISO 15489 (see appendix 7). Note: a document may be on paper, microform, magnetic or any other electronic medium. It may include any combination of text, data, graphics, sound, moving pictures or any other forms of information. A single document may consist of one or several components. Note: documents differ from records in several important respects. MoReq2 uses the term document to mean information that has not been captured as a record, i.e. classified, registered and locked against change. The word recorded in the definition does not imply the characteristics of a record. However, note that some documents become records.  HYPERLINK \l "T_DocumentType" document type Describes documents that share common characteristics. Note: for example, documents with common layout, content, retention and disposition requirements, and/or metadata. Document types could include, for example: application form; correspondence (includes letters and faxes and memoranda); curriculum vitae; e-mail message; invoice; medical report; web page. Note: in this example, e-mail messages are treated differently than other correspondence, as they may have different metadata requirements; this will not be the case in every organisation. Note: each organisation needs to define its document types, according to its business needs; the above are purely illustrative.  HYPERLINK \l "T_EDMS" EDMS Electronic Document Management System. Computer-based application dealing with the management of documents throughout the document life cycle. Source: IEC 82045-1 Document Management. Note: the functionality required for EDMSs is not included in this specification. However, an EDMS is often used in tight integration with an ERMS. See section 10.3 for more details.  HYPERLINK \l "T_Electronic" electronic For the purposes of this specification, the word electronic is used to mean the same as digital. Note: analogue recordings, though they may be regarded as electronic, are not considered as electronic for the purposes of this specification as they cannot be stored within a computer system unless they are converted to digital form. It follows that, in the terminology of this specification, analogue records can only be stored as physical records.  HYPERLINK \l "T_ElectronicDocument" electronic document A document which is in electronic form. Note: use of the term electronic document is not limited to the text-based documents typically generated by word processors. It also includes e-mail messages, spreadsheets, graphics and images, HTML/XML documents, multimedia and compound documents, and other types of office document.  HYPERLINK \l "T_ElectronicRecord" electronic record A record which is in electronic form. Note: it can be in electronic form as a result of having been created by application software or as a result of digitisation, e.g. by scanning.  HYPERLINK \l "T_ERMS" ERMS Electronic Records Management System. Note: ERMSs differ from EDMSs in several important respects. See section 10.3 for more details.  HYPERLINK \l "T_Export" export (verb) The process of producing a copy of electronic records, along with their metadata, for another system. Note: the records remain in the ERMS after export, unlike transfer.  HYPERLINK \l "T_Files" file (noun) An organised unit of records grouped together because they relate to the same subject, activity or transaction. Source: shortened and adapted from ISAD(G) (see appendix 7). Note: this is the Records Management usage of the term file. It differs from the IT usage, for which MoReq2 uses the term component.  HYPERLINK \l "T_FileFormat" file format The internal structure and/or encoding of a record or component which allows it to be presented into human-accessible form. Note: examples include: HTML v3.2 (a file format for web pages); PDF/A v1 (an archival file format for portable documents); TXT (ASCII plain text file format); XML v1.0 (a file format for extensible markup language which itself relies on ASCII plain text). Many proprietary file formats produced by desktop applications such as office suites.  HYPERLINK \l "T_Format" format (noun) See file format.  HYPERLINK \l "T_Group" group (noun) A set of users. Note: a group may include users with the same, or different, roles. A group is sometimes used to define users affiliation to an organisational unit such as a department (in which case it typically will include several roles); it is sometimes used to define membership of a virtual team that crosses organisational boundaries, such as all Procurement Officers (in which case it may consist of only users with a specified role); or it may be used in other ways.  HYPERLINK \l "T_Import" import See bulk importing.  HYPERLINK \l "T_Keyword" keyword Optional metadata used to describe classes, files, sub-files, and records but not volumes. Note: it is good practice for keywords to be picked from or validated against a controlled vocabulary, or to be extracted automatically by the ERMS, but this is not mandatory.  HYPERLINK \l "T_Metadata" metadata (in the context of records management) Data describing context, content and structure of records and their management through time. Source: ISO 15489 (see appendix 7). Note: some models are based on a different conceptual view of metadata. For example, they may treat audit trail information as being entirely metadata. These alternative views are valid and valuable in their contexts, but are not helpful in specifying the functionality of systems, and so are not considered here.  HYPERLINK \l "T_MetadataStub" metadata stub The subset of the metadata for an item that is retained after the item has been disposed of, to act as evidence that the item used to be held and has been properly disposed of.  HYPERLINK \l "T_NonCaseFile" non-case file Any file that is not a case file.  HYPERLINK \l "T_Open" open (verb) The process of creating a new file, sub-file or volume such that it can accept the addition of records. (adjective) Describes a file, sub-file or volume which has not yet been closed, and so is able to accept the addition of records.  HYPERLINK \l "T_Owner" owner The person or role responsible for a record or aggregation. Note: this is the usage in MoReq2; the legal owner of a record is the organisation that holds the record. Note: see also custodian.  HYPERLINK \l "T_PaperFile" paper file A kind of physical file. Note: examples of paper files include, among others, envelopes, box files and ring binders.  HYPERLINK \l "T_PDF" PDF Portable Document Format, a file format primarily for the representation of two-dimensional information. Note: At the time of writing, this widely used file format is proprietary to Adobe Inc., but a recent version of the format (v1.7) is under consideration as an International Standard (ISO/DIS 32000). Inclusion of the term PDF in this glossary does not represent any form of endorsement. Extensions for the representation of three-dimensional information are under development.  HYPERLINK \l "T_PDFA" PDF/A A subset of PDF designed for archival use, as defined in the ISO 19005 series of standards.  HYPERLINK \l "T_PhysicalFile" physical file A device for holding physical documents and physical records. Source: Adapted from PRO Functional Specification (see appendix 1).  HYPERLINK \l "T_PhysicalRecord" physical record A record that is held in a medium outside the ERMS, such that the record itself is not individually under the management of the ERMS. Note: examples include paper records, microform records, and electronic records held on removable media so long as the records are not individually managed by the ERMS.  HYPERLINK \l "T_Presentation" presentation The manifestation of an electronic record presented by the ERMS to which a user can refer. Note: this may include on-screen display, printed and audio and multimedia presentations. Note: the exact nature of the presentation can be affected by the software and hardware environment. Typically different presentations of the same record can vary in details of font metrics, line endings and pagination, resolution, bit depth, colour space etc. In most cases these differences are acceptable. However, in some cases their potential effects have to be considered separately; these considerations are beyond the scope of this specification. Note: in the previous version of MoReq the term rendition was used with this meaning.  HYPERLINK \l "T_Profile" profile The set of permissions allocated to a user or group or role.  HYPERLINK \l "T_Record" record (noun) Information created, received, and maintained as evidence and information by an organisation or person, in pursuance of legal obligations or in the transaction of business. Source: ISO 15489 (see appendix 7). Note: local national definitions may also apply. Note: a record may incorporate one or several documents (for instance when one document has attachments), and may be on any medium in any format. As a consequence, it may be made up of one or more components. In addition to the content of the document(s), a record should include contextual information and, if applicable, structural information (for instance information which describes the components of the record). A key feature of a record is that it cannot be changed. Note: both electronic records and physical records can be managed by an ERMS.  HYPERLINK \l "T_RecordType" record type Describes a record made from a document with the corresponding document type.  HYPERLINK \l "T_Redact" redact The process of hiding sensitive information in a record. Note: this can include applying opaque rectangles to obscure names etc. (the electronic equivalent of censoring paper documents with ink), more secure methods of obscuring information, or removing pages from the copy of a record. Note: in all cases the totality of the original electronic record is not affected. Redaction is carried out on a copy of the electronic record; this copy is called a redaction.  HYPERLINK \l "T_Redaction" redaction (noun) (of a record) A copy of a record to which some changes have been applied to remove or mask but not to add to or meaningfully amend existing content. Source: definition of instance in PRO Functional Specification (see appendix 1). Note: the changes usually result from restrictions on disclosure of information. For example, a record may be made available only after individuals names are masked or removed from it; in this case, a redaction of the record is created in which the names have been made illegible. The process of masking is sometimes referred to as redacting. Note: In the previous version of MoReq the term extract was used with this meaning.  HYPERLINK \l "T_Registration" registration The act of giving a record a unique identifier on its entry into a system. Source: ISO 15489 (see appendix 7). Note: in the context of MoReq2, registration is part of the process of capture.  HYPERLINK \l "T_Render" render The process of producing a rendition.  HYPERLINK \l "T_Rendezvous" rendezvous A point in the workflow where two or more parallel executing activities converge into a single common thread of control. Source: Workflow Management Coalition Terminology & Glossary, issue 3.0.  HYPERLINK \l "T_Rendition" rendition A manifestation of a record or component in or using one or more file format(s) different from the records native file format(s). Note: renditions are usually produced to preserve electronic records, that is to minimise the risk of loss of access to their content over time. For example, records produced in a proprietary file format may be stored as renditions in a standard format such as PDF/A or XML. Rendering a record means rendering some or all of its components. After the rendition, the record may have the same number of components as before or it may have a different number of components. For example, a record consisting of 30 components including 10 GIF image objects could be rendered in several ways, including: Rendition of the record into PDF/A file format: in this case, the initial record has 30 components and its rendition has one; Rendering the GIF components into JPEG file format only: in this case both the record and its rendition have 30 components, and in addition some of the objects in the rendition have to be changed to refer correctly to the newly rendered JPEG images instead of the GIF images. Note: rendition was used with a different meaning in the original version of MoReq.  HYPERLINK \l "T_Repetory" repertory A list of existing file titles within each of the lowest levels of the classification scheme.  HYPERLINK \l "T_RetentionandDispositionSchedule" retention and disposition schedule A formal instrument that defines the retention periods and consequent disposition actions authorised for records described in the schedule. Source: adapted from National Archives of Australia recordkeeping glossary. Note: in the previous version of MoReq this was referred to as a retention schedule.  HYPERLINK \l "T_Role" role The aggregation of functional permissions granted to a predefined subset of users. Source: PRO Functional Specification (see appendix 1).  HYPERLINK \l "T_SecurityCategory" security category One or several terms associated with a record or aggregation which define rules governing access to it. Note: security categories are usually assigned at an organisational or national level. Examples of security categories used in government organisations throughout most of Europe are: Top Secret, Secret, Confidential, Restricted, Unclassified. These are sometimes supplemented by other terms such as WEU Eyes Only or Personnel. Note: this term is not in general use. It has been adopted in MoReq2 instead of the term classification that is often used by the security community to avoid confusion with the records management meaning of classification.  HYPERLINK \l "T_SecurityClearance" security clearance One or several terms associated with a user which define the security categories to which the user is granted access.  HYPERLINK \l "T_Stub" stub See metadata stub.  HYPERLINK \l "T_SubFile" sub-file Intellectual subdivision of a file. Note: sub-files are often used in case file management environments. Typically, each sub-file is named, and each sub-file is used to store a specified kind or kinds of records for one instance of a case, such as invoices, assessments or correspondence. They can, however, also be used, in a similar fashion, in non-case file environments.  HYPERLINK \l "T_Transfer" transfer (verb) The process of moving complete electronic files, along with their metadata, to another system. Source: adapted from PRO Functional Specification (see appendix 1). Note: the files are often transferred together with all other files in a class of the classification scheme when the purpose of transfer is to move the files to an archive for permanent preservation. Note: see also export.  HYPERLINK \l "T_User" user Any person utilising the ERMS. Note: this may include (among others) administrators, office staff, members of the general public and external personnel such as auditors. Note: a user may both have roles and be a member of groups.  HYPERLINK \l "T_UserGroup" user group See group.  HYPERLINK \l "T_UserProfile" user profile The profile of a user. HYPERLINK \l "T_UserRole"user role A set of functional permissions allocated to users allowed to perform actions that manage records. A user may have several user roles but has only one user profile. Note: in MoReq2 this term is used also to specify the people with these permissions.  HYPERLINK \l "T_Version" version (of a document) The state of a document at some point during its development. Source: PRO Functional Specification (see appendix 1). Note: a version is usually one of the drafts of a document, or the final document. In some cases, however, finished documents exist in several versions, e.g. technical manuals. In other cases, the versions are translations. By contrast records cannot exist in more than one version; see also redaction.  HYPERLINK \l "T_VitalRecord" vital record A record that is essential for the functioning and/or survival of an organization during and/or after an emergency.  HYPERLINK \l "T_Volume" volume A subdivision of a sub-file. Note: the subdivisions are created to improve manageability of the sub-file contents by creating units which are not too large to manage successfully. The subdivisions are mechanical (for instance, based on number of records or ranges of numbers or time spans) rather than intellectual. Entity-Relationship Model This section repeats part of section 2.3, for ease of reference. It contains an entity-relationship model which can be used as an aid to understanding the specification. Section 13.3 contains a narrative explanation that describes and explains the model. The entity-relationship model is shown as figure 13.3. An important aspect of this model is that it need not represent actual structures stored in the ERMS. It represents a theoretical view of the entities associated with records. An ERMS uses these relationships to produce behaviour equivalent to the structures in the diagram. See section 2.2 for further explanation of this point. The relationships between files, volumes, records and other important entities are depicted in the following entity-relationship model. This is a formal representation of selected structures which can be used to describe the behaviour of an ERMS. In the diagram, entities files, records and so on are represented by rectangles. The lines connecting them represent the relationships between the entities. Each relationship is described by text in the middle of the line; and this should be read in the direction of the arrow. Each end of the relationship has a number which represents the number of occurrences (strictly, the cardinality); the numbers are explained in the key. So, for example, figure 13.1 means one record is made up of one or more components (note the direction of the relationship arrow).  Figure 13.1 A curved line crossing two or more relationships indicates that the relationships are mutually exclusive, for any given instance. So, for example, the curved line in figure 13.2 means each record is stored in either a volume or in a sub-file but not in both.  Figure 13.2 Note that the entity class is related to itself by the relationship is made up of. This relationship describes, in formal terms, the relationship between classes in a hierarchical classification scheme, where a class may be made up of one or more other classes. If this relationship (sometimes called a recursive relationship) is removed, the model applies equally to non-hierarchical relationships.  Figure 13.3 Entity Relationship Narrative Figure 13.3 shows a simplified model; it does not attempt to represent all possible entities or relationships. Rather, it shows only the most significant ones for this application. For example, it does not show users, roles etc. The remainder of this narrative describes the entities in the diagram, and their inter-relationships. Classification Scheme In order to practice records management principles, an organisation must have at least one classification scheme. This sets out the filing structure (typically consisting of a hierarchy) for a defined part of the organisation. A classification scheme contains several classes. Class Hierarchical classification schemes can be viewed as a hierarchy made up of a number of classes, much as a tree is made up of branches. Each class is connected to the hierarchy at one level; can extend over several levels; and can contain smaller classes. Several classes can start at any single level; but each class starts at one level only. As indicated by the exclusive or relationship, each class can: be made up of classes; or can contain files; or can store records; but combinations of these are not allowed. File Files occur within classes, at any level in the hierarchy. Files can occur only in classes that do not contain other classes. As indicated by the exclusive or relationship, each file can: be divided into sub-files; or can be divided into volumes; or can store records; but combinations of these are not allowed. Sub-file Each file can be divided into sub-files (a configuration option determines whether sub-files can or cannot exist). In practice, some files are not divided into sub-files. Where there is only one sub-file, the concept of sub-file is transparent to users, for all practical purposes. Sub-files are often used in case management applications. As indicated by the exclusive or relationship, each sub-file can: can be divided into volumes; or can store records; but combinations of these are not allowed. Volume Each sub-file can be divided into volumes (a configuration option determines whether volumes can or cannot exist), according to specific rules. In practice, most sub-files are not divided into volumes. Where there is only one volume, the concept of volume is transparent to users, for all practical purposes. The rules may depend on size or number of records, or may depend on transactions or time periods. This practice originated with physical files, in order to restrict them to a manageable size and weight. The practice is, where appropriate, continued with electronic files, to limit them to a manageable length for review, transfer, etc. Where a file consists of only one sub-file, then its volumes may seem to users to be volumes of the file rather than of its sub-file. The terms file, sub-file and volume are, in practice, sometimes used loosely or interchangeably because of the above requirement for transparency. For example, a user will typically ask for a file rather than (more accurately) asking for a volume. This is especially apparent in the case of a physical file that consists only of a single one-volume sub-file. In this case, although the file analytically consists of one sub-file which is made up of one volume, the sub-file and the volume are not always labelled as such (often, the label is only applied when the second sub-file or volume is opened). Retention and Disposition Schedule A retention and disposition schedule specifies the rules for keeping and disposing of records. The ERMS can contain several retention and disposition schedules, one or more of which are applied to each class, file, sub-file and volume; they can also be applied to records, and one retention and disposition schedule may be applied to each record type. Record At the heart of the system lies the most important entity, the records. These are the reason for the entire records management infrastructure, as they form the account of the organisations activities. Records are made from documents. Each record can comprise one or several documents; and each document can appear in several records. Records are normally stored in volumes. However, records can also be stored in classes (this is an exception described elsewhere). MoReq2 allows for a configuration option that prevents volumes and/or sub-files from being used, in which case records would be stored either in sub-files or in files. Each record can only be stored in one of a volume, sub-file, file or class. Record Type Records are assigned a record type. This is used to indicate, and to allow the ERMS to manage, the records in certain ways. Examples of record type might include invoice and web page. Component Each record and document is made up of at least one component; some are made up of more than one. For example, a simple web page may consist of only one component an HTML file in IT terms while a more complex web page may consist of dozens an HTML file, GIF files, JPEG files and so on. Access Control Model This section contains a simple model of example roles within an ERMS. The matrix recognises two main roles, which are themselves divided into roles. The main roles are user roles and administrative roles. These are defined in terms of access to ERMS functionality. The number of roles shown in this model is only illustrative. It is not meant to indicate that any organisation should implement these roles, not that any organisation should implement this number of roles. Each organisation should define the roles it needs; and these needs will tend to vary over time. The roles below illustrate an example of access control rights for specific aspects of system functionality according to organisational responsibilities. There are four example roles defined in the example matrix: Central Administrator this role has control over the configuration of the entire ERMS and the management of the aggregations and records themselves. Local Administrator this is a role with administrative rights over a sub-set of the ERMS or its classification scheme. These roles usually are useful in geographically dispersed organisations. Reviewer this is a specialist role which is primarily concerned with the application of disposition actions defined by Retention and Disposition Schedules. End User the end user role is the standard level of access to the ERMS and comprises those who need to save records into, and access records from, the ERMS for their routine work. Administrative roles are here divided into two roles only as an example; responsibilities can be divided in other ways. For some small organisations this division might be needlessly complicated, as only one person, with a single role, can manage all the administration. For large organisations it might be an over-simplification because more than two roles are needed (such as Records Manager, Records Officer, Archivist and Data Manager or IT Manager). MoReq2 does not attempt to specify how many administrative roles would be needed in any real organisation. The role of Local Administrator is given here as an example of one of these. This role can also have several titles in different organisations. In some cases this may be a Local Records Officer, or a Super-user etc. In any event, administrative roles are only implementing, from a system perspective, decisions taken by more senior management. Such decisions are typically based on the organisations business requirements and records policy. The decisions also are informed by laws and regulations, such as information laws, data security laws, archival laws and industry regulations; these are addressed in section 11.5. This matrix is not intended to imply that administrative roles must take management decisions, though in some environments that may be the case. Administrative roles take actions related to the management of records themselves; their interest is in managing records as entities rather than their content or business context. They may also manage the ERMS hardware, software and storage, ensure backups are taken and manage the performance of the ERMS. Many organisations also need to integrate the management of business processes with the management of records. In this case there is scope to allocate a particular set of administrative permissions to individual business managers. This could include the ability to monitor and manage a specific group of users or area of the classification scheme. Although MoReq2 refers to a user role there will be, in the majority of organisations, a number of different user roles and the ERMS should not limit the number of roles that can be configured. One example of this could be that of a case worker (see section 10.5 Casework). Such a role would have specific permissions within a particular branch of the classification scheme. Unlike administrative roles, user roles have access to facilities which an office worker or researcher needs when using records. This includes adding documents, searching for and retrieving records. Their interest is primarily in the contents, properties or business context of records rather than their management in other words, they are interested in the business processes evidenced by the records. In the matrix, the role of end user shows the access rights that typically are appropriate for the majority of users in an organisation to carry out their business functions. A further example of a user role is given: reviewer. This shows a level of access control that may be allocated to a sub-set of users for the purposes of reviewing records. This matrix is best viewed as a starting point, and as the formal basis for assigning rights. Users of this specification will need to consider additional requirements which are specific to their environment. The formal requirements dealing with this table are in section 4.1; they confirm that the requirement is not for an ERMS to incorporate the sample access matrix shown here, but to be capable of being configured to the level of detail of an access matrix defined by the user organisation which may contain an unrestricted number and type of roles and functions. It must be possible to configure each cell of the matrix as yes or no, but with the table having as many columns as the organisation needs. Other possible roles that might be implemented by organisations include but are not limited to: assistant; auditor; freedom of information manager; manager; records creator; records manager; supervisor. This matrix is divided into sections. These sections group, for convenience, the functions normally associated with classes and files, records, records management and administration. RolesFunctionUser RolesAdministrative RolesEnd UserReviewerLocal AdministratorCentral AdministratorAdd new classesNoNoYesYesCreate new filesYesNoYesYesChange file metadataNoYesYesYesMaintain classification scheme and filesNoNoYesYesDelete filesNoNoYesYesCapture records YesNoYesYesRelocate a record to a different fileYesNoYesYesSearch for and read recordsYesYesYesYesChange content of recordsNoNoNoNoChange record metadataNoYesYesYesDelete recordsNoNoYesYesPlace and remove disposal holdsNoYesYesYesRetention and disposition schedule and disposition transactions NoYesYesYesExport and import files and recordsNoYesYesYesView audit trailsNoYesYesYesConfigure and manage audit trailNoNoNoYesChange audit trail dataNoNoNoNoMove audit trail data to off-line storage mediaNoNoYesYesPerform all transactions related to users and their access privilegesNoNoYesYesAllocate access permissions to local administratorsNoNoNoYesAllocate own access permissions also to other usersYesYesYesYesSet up and manage case management rolesNoNoNoYesMaintain database and storageNoNoYesYesMaintain other system parametersNoNoNoYesDefine and view other system reportsNoYesYesYesAppendix 1 Reference Publications This specification was prepared with reference to the following existing specifications and publications: RefName and Ownership or SourceURL or Publication DetailsDublin Core Metadata Element Set, Version 1.1: Reference Description HYPERLINK "http://dublincore.org/documents/dces/" http://dublincore.org/documents/dces/Functional Requirements for Electronic Records Management Systems (The National Archives of the UK) HYPERLINK "http://www.nationalarchives.gov.uk/electronicrecords/reqs2002/default.htm" http://www.nationalarchives.gov.uk/electronicrecords/reqs2002/default.htmCode of Practice for legal admissibility and evidential weight of information stored electronically (British Standards Institution)Published by British Standards Institution ( HYPERLINK "http://www.bsi-global.com" www.bsi-global.com) as BSI BIP 0008The Preservation of the Integrity of Electronic Records (UBC-MAS Project)(University of British Columbia) HYPERLINK "http://www.interpares.org" http://www.interpares.orgStandard 5015.2 Design Criteria Standard For Electronic Records Management Software Applications (US Department of Defense) HYPERLINK "http://jitc.fhu.disa.mil/recmgt/" http://jitc.fhu.disa.mil/recmgt/ National Archives of Australia Functional Specifications for Electronic Records Management Systems Software- Exposure DraftThe exposure draft is no longer available. A similar document is available from  HYPERLINK "http://www.naa.gov.au/Images/ERMSspecifications_tcm2-1007.pdf" http://www.naa.gov.au/Images/ERMSspecifications_tcm2-1007.pdf Riksarkivet The National Archives of Norway NOARK-4 Norwegian recordkeeping system Version 4 Part 1 Functional description and specification of requirements HYPERLINK "http://www.arkivverket.no/arkivverket/lover/elarkiv/noark-4/english.html" http://www.arkivverket.no/arkivverket/lover/elarkiv/noark-4/english.htmlFunctional Requirements for the Sustainability of Electronic Records HYPERLINK "http://www.nationalarchives.gov.uk/documents/functional_requirements.pdf%20" http://www.nationalarchives.gov.uk/documents/functional_requirements.pdf InterPARES 2 Project Terminology Database HYPERLINK "http://www.interpares.org/ip2/ip2_terminology_db.cfm" http://www.interpares.org/ip2/ip2_terminology_db.cfmDLM Forum Guidelines HYPERLINK "http://dlmforum.typepad.com/gdlines.pdf" http://dlmforum.typepad.com/gdlines.pdf  Appendix 2 Development of this Specification Overview The MoReq2 specification has been developed for the European Commission by a team from Serco Consultancy (formerly Cornwell Management Consultants plc), based in the United Kingdom. MoReq2 is based on a detailed scoping report that was produced by the DLM Forum. The Serco project team included specialist consultants, who authored the specification, a small project management and administration team and an Editorial Board, comprising records management experts from throughout Europe and North America (see appendix 4). A late draft of the entire document was reviewed by a semi-independent reviewer. The test framework documentation was produced by a team from imbus AG. The requirements were subject to several levels of review. First, the Authoring Team members conducted peer reviews of each others work. Then the draft requirements were submitted to a peer review process by panellists representing a broad spectrum of interested parties across the records management community. For ease of reference these were broken down into: Archives Panel; Specialists Panel; Users Panel; Vendors Panel. At selected points, drafts were also reviewed by the MoReq2 Editorial Board The Board met with the Authoring Team on two occasions, providing invaluable direction and guidance; and its members later conducted a third review by e-mail. An interim and a further draft of MoReq2 were submitted to the European Commission for approval. The drafts were reviewed on behalf of the European Commission by a DLM Forum review group consisting of leading experts from a representative portion of the EU member states. The structure of the project team is outlined in figure A2.1; see appendix 4 for details of its members.  Figure A2.1 A project initiation meeting was held in London, involving the authoring team and the Editorial Board. At this meeting, working protocols and other principles were agreed, and some key references were identified. This was followed by desk research and the identification of relevant reference works which are listed in appendix 1. A close examination of the reference works was undertaken to ensure that the revised specification includes all relevant requirements. The original MoReq was imported into a software tool (Telelogic DOORS), a specialised requirements and change management package which was used throughout the authoring process to manage the drafting between the members of the team and to track and incorporate the comments on the drafts from the reviewers. The document was restructured to reflect the MoReq2 scoping document so that the relationship to the original MoReq could be maintained. As the draft of each chapter was completed it was published onto the MoReq2 web site and all panellists were notified. They were asked to provide their contributions in a specially designed comment form which allowed their contributions to be incorporated in the DOORS software for further processing by the authoring team. When the majority of chapters had been issued in this way a semi-complete draft of the entire document was compiled and this was distributed to the Editorial Board for them to identify major concerns in advance of a second meeting of the Board. At this meeting, which was also held in London, consensus was reached between the members on the majority of the issues that had been identified. Following this, the document was redrafted in the light of the agreed way forward. The redraft of MoReq2 was issued to the EC Project Officer and members of the DLM Forum for review. The official assessment of this interim draft was submitted to Serco and discussed at a project progress meeting in Brussels The authoring team studied all the comments received, both from the official review and from all the other panellists individually, these were then implemented or rejected as appropriate. This process was intense and iterative as many of the comments were mutually incompatible or not suitable for inclusion in MoReq2. However the overall quality of the comments was extremely high and this led to a refining of the previous draft. This led to the publication of Draft 2, an essentially complete document, for all panellists to comment on. Upon receipt, these comments were reviewed and implemented or rejected as before. A complete was issued to the EC Project Officer and members of the DLM Forum for review in October 2007. Upon receipt of the EC review comments a final draft of MoReq2 was prepared which was subject to review by a semi-independent reviewer before publication in January 2008. Appendix 3 Use of this Specification in Electronic Form This specification has been prepared so that it can be used in electronic form. It has been prepared using Microsoft Word 2003. The main advantage of using the specification in electronic form is that it can easily be customised. The requirements (chapter 3 to 11) are presented in the form of tables, with one requirement per table row. This is illustrated in figure A3.1.  Figure A3.1 The tables consist of three columns: Ref: a requirement reference number. This is generated automatically by Microsoft Word, as the reference numbers use a heading style. The result is that if chapters, sections or requirements are added or subtracted, the numbering changes automatically; Requirement: the requirement text. This always uses one of the verbs must (to indicate a mandatory requirement) or should (to indicate a desirable requirement); the rationale text. This is always in italic text and provides examples or a further description of the requirement; Test: each requirement is followed by an attribute called testable, abbreviated to test. This indicates whether it will be possible to test compliance with the requirement. Possible values of the testable attribute are described below, with examples: Y The requirement can be tested formally. An example is The ERMS must allow at least three hierarchical levels in the classification scheme. This can be tested by attempting to set up a hierarchy with three levels. N The requirement cannot be tested formally. An example is The ERMS must support the organisations business classification scheme. There is no way to test this in the general case. P The requirement can be tested but the coverage of the test is partial, or it is not formally testable but it is possible that lack of compliance can be discovered. An example is the ERMS should not limit the number of levels in the hierarchy. There is no way, formally, to test for the absence of a limit. However, the requirement is considered testable with partial coverage, for example by testing for a large number of levels; and during the testing it is possible that a limitation on the number of levels might be noticed, indicating that the ERMS does not comply with the requirement. If chapters, sections or requirements are deleted, Microsoft Word will replace any cross-references to them (if there are any) with an error message. These can be located by searching for the text error! By default, the table borders are not visible. They can be seen by use of the Show Gridlines command. Appendix 4 Acknowledgements Project Team Mr Frank BradyEuropean Commission (client)Mr Tim BurrowsSerco ConsultingMr Peter Campbell-BurnsSerco ConsultingMr Keith CornwD]^_adefiy}~ʶp^p^pM9&h#5hH_Y5;CJ$KHOJQJaJ hH_Y5;CJ$KHOJQJaJ#h#5h%5CJ$KHOJQJaJ&h#5h%5;CJ$KHOJQJaJh#5h%CJOJQJaJ"h#5h[:CJOJQJ\aJ h[:CJKHOJQJ\aJ&h#5h[:CJKHOJQJ\aJ&h#5h[;CJKHOJQJ\aJ%jh#5h[CJOJQJUaJh#5h[CJOJQJaJD_`abc$d<x5$7$8$9DH$a$gd%$ 3d<x5$7$8$9DH$a$gd%$d<x5$7$8$9D@&H$a$gd[$d<x5$7$8$9DH$a$gd[$d<x5$7$8$9DH$a$gd[ b#gg?hcxyz{|}~$d<x$5$7$8$9DH$Ifa$gd%$d<x5$7$8$9DH$a$gd%$d<x5$7$8$9D@&H$a$gd% ~     ӿqbS=*S%jh#5h%CJOJQJUaJ*jh4CJOJQJUaJmHnHuh#5h%CJOJQJaJh#5h%CJOJQJaJh#5h%CJOJQJaJ%jh#5h$CJOJQJUaJ,h#5h%56;CJKHOJQJ]aJ)h#5h%6CJKHOJQJ\]aJ&h#5h%6CJKHOJQJ]aJ&h#5h%5;CJKHOJQJaJ/jh#5h%5;CJKHOJQJUaJ      G mmmmm$d<x5$7$8$9DH$a$gd%$d<x5$7$8$9DH$a$gd%ckdVM$$IfTl F " : H#    4 laT G ] ` a b d f g h i l | ij~jXjXjQEQAh%h-t{h%mHnHu h-t{h%#h#5h%5CJ$KHOJQJaJ&h#5h%5;CJ$KHOJQJaJ&h#5h[5;CJ$KHOJQJaJh#5h[CJOJQJaJ"h#5h%:CJOJQJ\aJ h9:CJKHOJQJ\aJ&h#5h9:CJKHOJQJ\aJ&h#5h%:CJKHOJQJ\aJ&h#5h%;CJKHOJQJ\aJG b c d e f { |  q m$ FJ<^J`a$gd%$ FJ<^J`a$gdfgdin$d<x5$7$8$9DH$a$gd%$d<x5$7$8$9DH$a$gd[$ 3d<x5$7$8$9DH$a$gd[$d<x5$7$8$9D@&H$a$gd%      S T U q ׺ז|gJ|5|g. hinh%(hinh%>*B*CJOJQJ^Jph8jNhinh%B*CJOJQJU^JaJph)hinh%B*CJOJQJ^JaJph2jhinh%B*CJOJQJU^JaJph)hfhfB*CJOJQJ^JaJphhV"hf0JCJ^JaJ8jMhV"hfB*CJOJQJU^JaJph#hfB*CJOJQJ^JaJph,jhfB*CJOJQJU^JaJphq jklm±}y}e}`V`KV`VjPhLwUjhLwU hLw'jOhLwhLw>*B*UphhLwhhwhLw0JjhhwhLw0JUhh fjhh fU#h#5h%5CJOJQJ^JaJ h#5h%CJOJQJ^JaJh#5h%CJOJQJaJ hinhwZ7 hinh%hh%mH sH h[h9mH sH h[h%mH sH q V `:cJsE @&gd%$d<5$7$8$9DH$a$gd%gdin     -./034>?@Z[\]^_`ab~ޘގo'jRhLwhLw>*B*Uphj RhLwUhLwCJOJQJ'jQhLwhLw>*B*UphjQhLwUjhLwU hLw'jPhLwhLw>*B*UphhLwhhwhLw0JjhhwhLw0JUhLw;CJOJQJ+456789:;<XYZ[^_opqjThLwU'j{ThLwhLw>*B*UphjShLwU'jShLwhLw>*B*UphhLwjhhwhLw0JUjShLwUjhLwU hLwhLwCJOJQJhhwhLw0J4 !$%ABC]^_`abcdeƼƱƼխՙƼƎƼխzƼ'jiWhLwhLw>*B*UphjVhLwU'joVhLwhLw>*B*UphhLwjUhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'juUhLwhLw>*B*Uph,()*DEFGHIJKLhijknoŭŎjYhLwU'j]YhLwhLw>*B*UphjXhLwU'jcXhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUjWhLwU.789:>?QRSmnopqrstuƼƱƼխՙƼƎƼխzƼ'jK\hLwhLw>*B*Uphj[hLwU'jQ[hLwhLw>*B*UphhLwjZhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jWZhLwhLw>*B*Uph,#$%?@ABCDEFGcdefhiŭŎŃx؃j^hLwUhLw;CJOJQJ'j?^hLwhLw>*B*Uphj]hLwU'jE]hLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUj\hLwU. !$%123MNOQRSTUVrstuxyƼƱƼխՙƼƎƼխzƼ'j-ahLwhLw>*B*Uphj`hLwU'j3`hLwhLw>*B*UphhLwj_hLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'j9_hLwhLw>*B*Uph,T'Jae0cacJ !"$%&'()EFGHKLqrsŭŢآŃxjchLwU'j!chLwhLw>*B*UphjbhLwUhLw;CJOJQJ'j'bhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUjahLwU.   '()CDEGHIJKLhijknoƼƱƼխՙƼƎƼխzƼ'jfhLwhLw>*B*UphjehLwU'jehLwhLw>*B*UphhLwjdhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jdhLwhLw>*B*Uph,  123478>?@Z[\^_`abcŭŢآŃxjhhLwU'jhhLwhLw>*B*UphjghLwUhLw;CJOJQJ'j ghLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUjfhLwU.    ./0145BCD^ƼƱƼխՙƼƎƼխzƼ'jjhLwhLw>*B*UphjtjhLwU'jihLwhLw>*B*UphhLwjzihLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jhhLwhLw>*B*Uph,^_`bcdefg )*+-./012NOŭŢآŃxjbmhLwU'jlhLwhLw>*B*UphjhlhLwUhLw;CJOJQJ'jkhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUjnkhLwU.OPQTUrst !@ABƼƱƼխՙƼƎƼխzoƼhLw;CJOJQJ'johLwhLw>*B*UphjVohLwU'jnhLwhLw>*B*UphhLwj\nhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jmhLwhLw>*B*Uph+B\]^`abcde  &'ĬĢآăĢxآjDrhLwU'jqhLwhLw>*B*UphjJqhLwUhLwCJOJQJ'jphLwhLw>*B*UphhLwhhwhLw0JhLw;CJOJQJjhhwhLw0JUjhLwUjPphLwU hLw/'(),->?@Z[\^_`abc ƼƱƼխՙƼƎƼխzƼ'jthLwhLw>*B*Uphj8thLwU'jshLwhLw>*B*UphhLwj>shLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jrhLwhLw>*B*Uph,   /01245@AB\]^`abcdeŭŢآŃxj&whLwU'jvhLwhLw>*B*Uphj,vhLwUhLw;CJOJQJ'juhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUj2uhLwU.789:<=bcd~ƼƱƼխՙՎƼƃƼގխoƼ'jyhLwhLw>*B*UphjyhLwUhLw;CJOJQJ'jxhLwhLw>*B*UphhLwj xhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jwhLwhLw>*B*Uph+&'(BCDGHIJKLhijknoŭŎj|hLwU'j{hLwhLw>*B*Uphj{hLwU'jzhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JUjhLwUjzhLwU hLw/      # $ % & ( ) A B C ] ^ _ b c d e f g ƼƱƼխՙՎƼƃƼގխoƼ'jy~hLwhLw>*B*Uphj}hLwUhLw;CJOJQJ'j}hLwhLw>*B*UphhLwj}hLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'j|hLwhLw>*B*Uph+ e !!!c""C###\$$%r%%5&&&Q'' (h((6))**** !!!!!!!!!4!5!6!7!:!;!c!d!e!!!!!!!!!!!!ŭŎjhLwU'jmhLwhLw>*B*UphjhLwU'jshLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JUjhLwUj~hLwU hLw/!!!!!!!!!!!!!!!!!!!""""?"@"A"["\"]"`"a"b"c"d"e""""""""""ŻŰŻլ՘ՎŻŃŻގլoՎŻ'j[hLwhLw>*B*UphjނhLwUhLwCJOJQJ'jahLwhLw>*B*UphhLwjhLwUjhLwU hLwhLw;CJOJQJhhwhLw0JjhhwhLw0JU'jghLwhLw>*B*Uph+""""""""""""""""# #!#;#<#=#@#A#B#C#D#E#a#b#c#d#h#i#q#r#s############ŭŎj̅hLwU'jOhLwhLw>*B*Uphj҄hLwU'jUhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JUjhLwUj؃hLwU hLw/#################$$$$ $ $8$9$:$T$U$V$Y$Z$[$\$]$^$z${$|$}$$$$$$$ƼƱƼխՙƼƎƼխzƼ'j=hLwhLw>*B*UphjhLwU'jChLwhLw>*B*UphhLwjƆhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jIhLwhLw>*B*Uph,$$$$$$$$$$$$$$$$$$%% % % %%%%%-%.%/%0%4%5%N%O%P%j%k%l%o%p%q%r%s%t%%%ŭŎjhLwU'j1hLwhLw>*B*UphjhLwU'j7hLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUjhLwU.%%%%%%%%%%%%%%%%%%%%%%%&&&-&.&/&2&3&4&5&6&7&S&T&U&V&[&\&k&l&m&&ƼƱƼխՙƼƎƼխzƼ'jhLwhLw>*B*UphjhLwU'j%hLwhLw>*B*UphhLwjhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'j+hLwhLw>*B*Uph,&&&&&&&&&&&&&&&&&&&&&&&&&&& ' ' ''''-'.'/'I'J'K'N'O'P'Q'R'S'o'p'ŭŎŃx؃jhLwUhLw;CJOJQJ'jhLwhLw>*B*UphjhLwU'jhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUjhLwU.p'q'r'v'w''''''''''''''''''''''(((( ( ( ( ( ()(*(+(,(0(1(D(E(F(`(ƼƱƼխՙƼƎƼխzƼ'jhLwhLw>*B*UphjhLwU'jhLwhLw>*B*UphhLwjhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'j hLwhLw>*B*Uph,`(a(b(e(f(g(h(i(j((((((((((((((((((((((((())).)/)0)3)4)5)6)7)8)T)U)ŭŎjrhLwU'jhLwhLw>*B*UphjxhLwU'jhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUj~hLwU.U)V)W)[)\)))))))))))))))))))***"*#*$*'*(*)***+*,*H*I*J*K*O*P*b*c*d*~*ƼƱƼխՙƼƎƼխzƼ'jhLwhLw>*B*UphjfhLwU'jhLwhLw>*B*UphhLwjlhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jhLwhLw>*B*Uph,~***************************++++ + ++++0+1+2+5+6+7+8+9+:+V+W+ŭŢآŃxjThLwU'jטhLwhLw>*B*UphjZhLwUhLw;CJOJQJ'jݗhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JU hLwjhLwUj`hLwU.*8+++I,,-q--L..,///m00111s22V33334 $ & Fa$gdh fgd>agdl9W+X+Y+]+^+{+|+}++++++++++++++++++++++++++++,,,,,,%,&,',ƼƱƼխՙՎƼƃƼގխoƼ'jśhLwhLw>*B*UphjHhLwUhLw;CJOJQJ'j˚hLwhLw>*B*UphhLwjNhLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jљhLwhLw>*B*Uph+',A,B,C,F,G,H,I,J,K,g,h,i,j,n,o,,,,,,,,,,,,,,,,,,,,,, - - -------1-2-ŭŎj6hLwU'jhLwhLw>*B*Uphj<hLwU'jhLwhLw>*B*UphhLwhhwhLw0JhLwCJOJQJjhhwhLw0JUjhLwUjBhLwU hLw/2-3-4-8-9-M-N-O-i-j-k-n-o-p-q-r-s---------------------..(.ƼƱƼխՙƼƎƼރխoddhhwhLw0JKH'jhLwhLw>*B*UphhLw;CJOJQJj*hLwU'jhLwhLw>*B*UphhLwj0hLwUjhLwU hLwhLwCJOJQJhhwhLw0JjhhwhLw0JU'jhLwhLw>*B*Uph'(.).*.D.E.F.I.J.K.L.M.N.j.k.l.m................./ / /$/%/&/)/*/+/,/-/./J/K/ĬčjhLwU'jhLwhLw>*B*UphjhLwU'jhLwhLw>*B*UphhLwhhwhLw0JhLw;CJOJQJjhhwhLw0JUj$hLwUjhLwU hLw-K/L/M/x/y/z//////////////////////////0000I0J0K0e0f0g0j0k0l0лްլ՘ЍްլynjhLwU'jhLwhLw>*B*Uphj hLwU'jhLwhLw>*B*UphhLwhLw;CJOJQJjhLwUjhLwU hLwhhwhLw0JjhhwhLw0JU'jhLwhLw>*B*Uph+l0m0n0o000000000000000000000000000011111111141516171޼޷ގ޼޷o'jwhLwhLw>*B*UphjhLwU'j}hLwhLw>*B*UphjhLwUjhLwU hLwhLwCJOJQJ'jhLwhLw>*B*UphhLwhhwhLw0JjhhwhLw0JUhLw;CJOJQJ+71:1;1a1b1c1}1~11111111111111111111111111 2 2 2222O2P2Q2k2l2m2p2q2r2s2t2u222jhLwU'jkhLwhLw>*B*UphjhLwU'jqhLwhLw>*B*UphhLwjhhwhLw0JUjhLwUjhLwU hLwhLwCJOJQJhhwhLw0J422222222222222233333 3233343N3O3P3S3T3U3V3W3X3t3u3v3w3z3{33333лްլ՘ՎЃގլoՎ'jYhLwhLw>*B*UphjܬhLwUhLwCJOJQJ'j_hLwhLw>*B*UphhLwhLw;CJOJQJjhLwUjhLwU hLwhhwhLw0JjhhwhLw0JU'jehLwhLw>*B*Uph*333333333333333348494F4G4Q4R4Y47777;;;;;;;;;"<==[>s>>¾¾¹~~w h#5hphqx*h=FhFh\ hhFh\ hh% h!CJhSh%CJ h#5h% h#5h>ah% hl9;hl9h>ajhh fUhLwCJOJQJjhhwhLw0JU hLwjhLwUj֭hLwU*4Y48668W:;[>h>s>\@)AfaagdFFEƀ^F.gd FEƀ^F.gdgd$a$gdS >>??B@C@ABZDDDDHHII+I,I6I7IXL_L/N4NPPFTKTUUVVMWNWWW[[ [!["[2[3[4[8[<[d[e[ \I\z\\\\ ]$]]h#5hp5\h#5hphK$ h#5hFh\h#5hph{LhuhlhFh\h=F h#5h%h#5hpmHnHujh0JUhfZahfZamHnHu h#5hpjhp0JU8)ACZDDD!EEBFiFEƀ^Fgd#5gd(FEƀ^F.gdgdFBFFLGGHsnngd(FEƀ^Fgd#5FEƀ^Fgd#5HHIJKvMNPPPFT{VXnFEƀ^F.gdgd(FEƀ^F.gd XY[ \I\z\\nFEƀ^Fgd#5FEƀ^F.gdgd(\ ]]]s-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5]]]]^@^u^^e____``Paiaaaaabbb9b:bŮЮuv~Űư̰ .:}yyh ohThS~0J5B*ph h#5h_h_hlh#5hS~6hcz\hS~0J5B*ph hcz\hS~ h#5h$W0h$W0h%>^6]mHnHuh#5hS~6]mHnHuhfZahfZamHnHuhlh#5hS~6] h#5hS~/*ʶ׶5iFEƀ^F2gd#5FEƀ^F.gdgdgd(:cpʶ׶ 5=> ^_#%puv`e h#5h&h&hprhljhuUhhj h#5hS~UhQhLw hLwhS~jhS~U h#5hkRhkR h#5h_hGh] h#5h%hV$h#5hS~6]h#5hS~6 h#5hS~05Kqs-FEƀ^F5gd#5FEƀ^F4gd#5FEƀ^F3gd#5s-FEƀ^F8gd#5FEƀ^F7gd#5FEƀ^F6gd#5ѷ?HiFEƀ^F:gd#5gd(gd9TFEƀ^F9gd#5HS\jws-(gd(FEƀ^F=gd#5FEƀ^F<gd#5FEƀ^F;gd#5w#2iFEƀ^F?gd#5FEƀ^F>gd#5gd9Tgd(wsn(FEƀ^FBgd#5gd(FEƀ^FAgd#5FEƀ^F@gd#5Ds-FEƀ^FEgd#5FEƀ^FDgd#5FEƀ^FCgd#506[+snidnnnngdkRgd9Tgd(FEƀ^FGgd#5FEƀ^FFgd#5 Ssninnna\ngdH $a$gdfgd9Tgd(FEƀ^FIgd#5FEƀ^FHgd#5 My gdpro4TfgdH $$a$gdr,gd(gd9TT nFEƀ^FJgd#5gd(FEƀ^F.gd Aa+45Q[\OP} Yoͷ͛zsijheZ5U h#5h%jh#5h<%Uh4Khh$hB*aJphh)1hOh+35B*phhOhOB*phhOhO5B*\phj hUU h#5h+3hS~jh#5hUU h#5hU hUhUhh h#5hS~h+3($,s-FEƀ^FMgd#5FEƀ^FLgd#5FEƀ^FKgd#5,4Acsnia\WN $$a$gdUgd+3gdH $a$gdUgdUgd(FEƀ^FOgd#5FEƀ^FNgd#5PFEƀ^F.gd$a$gdfgd+3gd(gd h @ABWXtu123:;<XYtuv}~GHabcg~yi~jĖh M>h`5U h M>5jh M>5UjMheZh`5UjؕheZh`5U h65jeheZh`5UjheZh`5U h#5hS~h#rhS~0J5>*jheZ5UjcheZh`5U heZ5)ghxyRTVXfFHfhjtvz|&0^丹h?hLw hLwhS~jhS~U h#5hRhR h65j7h M>h`5Uj—h M>h`5Uh#rhS~0J5>*j5h M>h`5U h M>5 h#5hS~jh M>5U4&2Fs-FEƀ^FRgd#5FEƀ^FQgd#5FEƀ^FPgd#5FVjlw"aFEƀ^FTgd#5gd h$a$gdfgd(FEƀ^FSgd#5^djkv9:      " #    D E ^ _ ` d e ط氬up`uTuh#rhf0J5>*jh!h`5U h!5jh!5UhNqyhf6h#5hfCJaJh#5hf5CJaJ hhf h#5hfhf h#5h%h#rhS~0J5>*j&h5$h`5U h5$5jh5$5UheZhS~jh#5hS~U h#5hS~h?     " naXL $$Ifa$gd1 $Ifgdy $If^gd1FEƀ^F.gdf[)gd(FEƀ^FUgd#5" # (   ?6- $IfgdL $IfgdNqyJ$Eƀ^F..IfgdLtkd$$Ifl44Fn]#5&&    4 laf4p     |s $IfgdL $IfgdNqy $Ifgd%qkdT$$Ifl4Fn]#5&&    4 laf4p   % C: $IfgdFJ$Eƀ^F..IfgdLqkd$$Ifl4Fn]#5&&    4 laf4p% > p  iJ$Eƀ^FXIfgd#5J$Eƀ^FWIfgd#5J$Eƀ^FVIfgd#5    ? @ |s $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4p $IfgdL@ A F +-C:1 $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:qkd$$Ifl4Fn]#5&&    4 laf4pe \ ]        )45RST\]^|}~9:I zxplpgcphLw hLwhfjhfUhh0J5>*jhh5Uhh5jhh5Uhh6]j^h!h`5U h#5h!h!h#rhf0J5>*j5h!h`5U h!5jh!5U h#5hf#-./|s $IfgdL $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4pdfC:1 $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:qkdL$$Ifl4Fn]#5&&    4 laf4pfghLM|s $IfgdL $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4pMNO|s $IfgdL $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4pC:1 $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:qkd $$Ifl4Fn]#5&&    4 laf4p|s $IfgdL $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4pbfC:1 $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:qkdX$$Ifl4Fn]#5&&    4 laf4pz|<>@JL *,@AdefuvbĿΥċ{rĿbjhh)h`5Uh#r0J5>*jh#rhs`;5U h#r5hLw hLwhfjhfUh#5hfh4.jmhh)h`5U hh)5jhh)5U h#5hfh#rhf0J5>*jh5h@+5U h55jh55U$fhjx}|1J$Eƀ^FYIfgd#5 $IfgdF $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4p}:qkd$$Ifl4Fn]#5&&    4 laf4p $IfgdLJ$Eƀ^FZIfgd#51qkd$$Ifl4Fn]#5&&    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:ABCH|1J$Eƀ^F..Ifgd'J:qkd$$Ifl4Fn]#5&&    4 laf4p $IfgdL $Ifgd(bjk V]^()67]^_ߛ߃j6hh)h`5Uh2Vhjhh)h`5Uhfh#5hf5\h#5hf6]h#rhf0J5>*jVhh)h`5U hh)5jhh)5U h#5hf h#5hQ4hQ4.H|s $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4p $IfgdL $Ifgd(*,B90 $Ifgd6z $Ifgd6zL$$Eƀ^F ..Ifgd6zqkd}$$Ifl4Fn]#5&&    4 laf4p,-2C:1 $IfgdL $Ifgd(J$Eƀ^F ..Ifgd'J:qkd$$Ifl4Fn]#5&&    4 laf4pPQ|s $IfgdL $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4pQRWB90 $Ifgd6z $Ifgd6zL$$Eƀ^F ..Ifgd6zqkdQ$$Ifl4Fn]#5&&    4 laf4p C:1 $IfgdL $Ifgd(J$Eƀ^F ..Ifgd'J:qkdb$$Ifl4Fn]#5&&    4 laf4p|s $IfgdL $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4pC:1 $IfgdL $Ifgd(J$Eƀ^F ..Ifgd'J:qkd$$Ifl4Fn]#5&&    4 laf4p../ /////000081:1p1r1t11166=8>8A8O8T8U888өӁzvrkdXzh#5hy5CJaJ hhy h#5hyhyhmb h#5hS~ h#5h%h#rh$,0J5>*jhh)h$,5U h$,5jh$,5UhLw hLwhfjhfU h#5h$,h$, h#5hfh#rhf0J5>*jhh)5Ujhh)h`5U!|s $IfgdL $Ifgd( $Ifgd(qkd>$$Ifl4Fn]#5&&    4 laf4pa c C:1 $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:qkd$$Ifl4Fn]#5&&    4 laf4pc d e !!|s $IfgdL $Ifgd( $Ifgd(qkdv$$Ifl4Fn]#5&&    4 laf4p!! !!C: $IfgdFJ$Eƀ^F..Ifgd'J:qkd$$Ifl4Fn]#5&&    4 laf4p!T"""iJ$Eƀ^F]Ifgd#5J$Eƀ^F\Ifgd#5J$Eƀ^F[Ifgd#5""""##|s $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4p $IfgdL###$$|s $IfgdL $Ifgd( $Ifgd(qkdJ$$Ifl4Fn]#5&&    4 laf4p$$${%|%|s $IfgdL $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4p|%}%%Z'\'C:1 $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:qkd$$Ifl4Fn]#5&&    4 laf4p\']'^'()|1J$Eƀ^F^Ifgd#5 $Ifgd5 $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4p))-**iJ$Eƀ^FaIfgd#5J$Eƀ^F`Ifgd#5J$Eƀ^F_Ifgd#5****++|s $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4p $IfgdL+++,,B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkdV$$Ifl4Fn]#5&&    4 laf4p,,,,,B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4Fn]#5&&    4 laf4p,,,--B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4Fn]#5&&    4 laf4p---S.U.B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd*$$Ifl4Fn]#5&&    4 laf4pU.V.[...C:1 $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:qkd$$Ifl4Fn]#5&&    4 laf4p...00|s $IfgdL $Ifgd( $Ifgd(qkdb$$Ifl4Fn]#5&&    4 laf4p00"011B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4Fn]#5&&    4 laf4p111D2F2B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4Fn]#5&&    4 laf4pF2G2L222B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4Fn]#5&&    4 laf4p222}33C:1 $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:qkdG$$Ifl4Fn]#5&&    4 laf4p333z4{4|s $IfgdL $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4p{4|4444C:1 $IfgdL $Ifgd(J$Eƀ^F..Ifgd'J:qkd$$Ifl4Fn]#5&&    4 laf4p44466|s $IfgdL $Ifgd( $Ifgd(qkd$$Ifl4Fn]#5&&    4 laf4p6666>8B8HC>1 $If^gd*<@gd\gd(FEƀ^F.gdjqkd$$Ifl4Fn]#5&&    4 laf4pB8O8T8U8Z8u)L$$Eƀ^F..Ifgd6ztkdS$$Ifl44Fn\#5&&    4 laf4p $$Ifa$gd*<@ $Ifgd*<@88888899<:>:@:f:h::::::::;;;;;;;;;1<2<Q<R<S<]<^<<<<<<<<<þ͎ͦͦþ~͎þnjh+)h`5Ujzh+)h`5Uh#5hS~CJaJhLw hLwhS~jhS~Ujh+)h`5U h+)5jh+)5U h#5hS~h#rhS~0J5>*jhh)5Ujhh)h`5U hh)5+Z8*9,9-9299|0L$$Eƀ^F..Ifgd6zqkd}$$Ifl4Fn\#5&&    4 laf4p $Ifgd6z $Ifgd6z9999;:1 $Ifgd(J$Eƀ^F..IfgdLqkd$$Ifl4Fn\#5&&    4 laf4p $Ifgd6z;;;;;;|s $Ifgd( $Ifgd%qkdB$$Ifl4Fn\#5&&    4 laf4p $IfgdL;;;<<C:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd$$Ifl4Fn\#5&&    4 laf4p<<<V=W=|s $IfgdL $Ifgd( $Ifgd%qkd$$Ifl4Fn\#5&&    4 laf4p<<%@&@@@(A)A8ABB BBBBHBJB|B~BBBBCCNCPCRC^C`CcDdDsDtDDDDDDGGHHIIIIクwshQEjh+)h`5Uj+h+)h`5U h+)5h#rhS~0J5>*jhqZh@+5U hqZ5jhqZ5UhLw hLwhS~jhS~Uh#5hS~CJaJh#5hS~6 h#5hS~jh+)5U-W=X=]===B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4Fn\#5&&    4 laf4p===<>>>B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4Fn\#5&&    4 laf4p>>?>D>>B9 $Ifgd6zL$$Eƀ^F..Ifgd6zqkdJ$$Ifl4Fn\#5&&    4 laf4p>>3?s?iJ$Eƀ^FdIfgd6zJ$Eƀ^FcIfgd6zJ$Eƀ^FbIfgd6zs????iJ$Eƀ^FgIfgd6zJ$Eƀ^FfIfgd6zJ$Eƀ^FeIfgd6z?&@(@)@:qkd$$Ifl4Fn\#5&&    4 laf4p $Ifgd6zJ$Eƀ^FhIfgd6z)@.@@@@1qkd$$Ifl4Fn\#5&&    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdL@@BBBBCCsqkd$$Ifl4Fn\#5&&    4 laf4p $IfgdL $Ifgd( $Ifgd%CCC`DbDC:1 $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqkd$$Ifl4Fn\#5&&    4 laf4pbDcDdDE[F\F||s $IfgdL $Ifgd5 $Ifgd%qkd<$$Ifl4Fn\#5&&    4 laf4p\F]FbFGGC:1 $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqkdY$$Ifl4Fn\#5&&    4 laf4pGGGnGGHH|||s $IfgdL $Ifgd( $Ifgd%qkd$$Ifl4Fn\#5&&    4 laf4pHHHII|s $IfgdL $Ifgd( $Ifgd%qkd$$Ifl4Fn\#5&&    4 laf4pII"IIIC:1 $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqkd-$$Ifl4Fn\#5&&    4 laf4pIII?J@J|s $IfgdL $Ifgd( $Ifgd%qkd$$Ifl4Fn\#5&&    4 laf4p@JAJFJJJB90 $Ifgd6z $Ifgd6zL$$Eƀ^F ..Ifgd6zqkde$$Ifl4Fn\#5&&    4 laf4pJJJKKB90 $Ifgd6z $Ifgd6zL$$Eƀ^F ..Ifgd6zqkd$$Ifl4Fn\#5&&    4 laf4pKKKLLC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd$$Ifl4Fn\#5&&    4 laf4pLLLNN|s $IfgdL $Ifgd( $Ifgd%qkd9$$Ifl4Fn\#5&&    4 laf4pILLLLLLLM MMMM8M:M*j\h+)h`5U h#5h= h#5h%h#5hS~6]h#rhS~0J5>*j h+)h`5U h+)5jh+)5UhLw hLwjhS~UhS~h#5hS~CJaJ h#5hS~(NNNNNB90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4Fn\#5&&    4 laf4pNNNhOjOB90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkdq$$Ifl4Fn\#5&&    4 laf4pjOkOpOOOC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd$$Ifl4Fn\#5&&    4 laf4pOOOqPrP|s $IfgdL $Ifgd( $Ifgd%qkd$$$Ifl4Fn\#5&&    4 laf4prPsPPRzSHCCgd(FEƀ^F.gdjqkd$$Ifl4Fn\#5&&    4 laf4pzS%TxT\UUsnngd(FEƀ^Fjgd#5FEƀ^Figd#5JUKULUYUZUYYYYYY\\\\[^\^__``ccdd.d/d0d5d6deeefffggiifjgjllTmĽӦӢӦӦӦӦӘژӦӦyӦӦr h#5h%h#5h=6]jQh$i5h`5U h$i55jh$i55UhRh#5h=CJaJh#5hy5CJaJ hhy h#5hyhyhmb h#5h=h#rh=0J5>*jhA% 5UjhA% h`5U*UUVW%X1Xsnic$gdk4ugd(gd(FEƀ^Flgd#5FEƀ^Fkgd#51X^XXXs-FEƀ^Fogd#5FEƀ^Fngd#5FEƀ^Fmgd#5XYCYYYYYsnaXL $$Ifa$gd*<@ $Ifgd*<@ $If^gd*<@gdYFEƀ^Fqgd#5FEƀ^Fpgd#5YYYiZkZ>5, $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6ztkdX$$Ifl44F\#5&h`&    4 laf4pkZlZqZ?[A[B90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4F\#5&h`&    4 laf4pA[B[G[\\C:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd$$Ifl4F\#5&h`&    4 laf4p\\\B]Y^Z^||s $IfgdL $Ifgd5 $Ifgd%qkd9$$Ifl4F\#5&h`&    4 laf4pZ^[^\^^_|1J$Eƀ^FrIfgd#5 $Ifgd( $Ifgd%qkd$$Ifl4F\#5&h`&    4 laf4p_____:1 $Ifgd%qkdq$$Ifl4F\#5&h`&    4 laf4p $IfgdLJ$Eƀ^FsIfgd#5_````OaPa|s $Ifgd%qkd $$Ifl4F\#5&h`&    4 laf4p $IfgdL $Ifgd(PaQaVaaB1?$If^`?gd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4F\#5&h`&    4 laf4paa+b-bYP $Ifgd6zR?$Eƀ^FuIf^`?gd6zR?$Eƀ^FtIf^`?gd6z-b.b3bbbB90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkdE$$Ifl4F\#5&h`&    4 laf4pbbbccC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd$$Ifl4F\#5&h`&    4 laf4pcccccxo $IfgdL $If^gd= $Ifgd%qkd}$$Ifl4F\#5&h`&    4 laf4pcccccB90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4F\#5&h`&    4 laf4pcccOdQdB90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4F\#5&h`&    4 laf4pQdRdWdddB90 $Ifgd6z $Ifgd6zL$$Eƀ^F ..Ifgd6zqkd$$Ifl4F\#5&h`&    4 laf4pddd|e~eC:1 $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqkd`$$Ifl4F\#5&h`&    4 laf4p~eeeee|s $IfgdL $Ifgd( $Ifgd%qkd$$Ifl4F\#5&h`&    4 laf4peeebfdfC:1 $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqkd$$Ifl4F\#5&h`&    4 laf4pdfefffff|s $IfgdL $Ifgd( $Ifgd%qkd4 $$Ifl4F\#5&h`&    4 laf4pfffggB90 $Ifgd6z $Ifgd6zL$$Eƀ^F ..Ifgd6zqkd $$Ifl4F\#5&h`&    4 laf4pgggggB90 $Ifgd6z $Ifgd6zL$$Eƀ^F ..Ifgd6zqkdl $$Ifl4F\#5&h`&    4 laf4pgggggC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd $$Ifl4F\#5&h`&    4 laf4pgghJhLhB90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd $$Ifl4F\#5&h`&    4 laf4pLhMhRhiiC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd@ $$Ifl4F\#5&h`&    4 laf4piiidiei|s $IfgdL $Ifgd( $Ifgd%qkd $$Ifl4F\#5&h`&    4 laf4peifikicjejC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkdx $$Ifl4F\#5&h`&    4 laf4pejfjgjll|s $IfgdL $Ifgd( $Ifgd%qkd$$Ifl4F\#5&h`&    4 laf4pll"lllB90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkd$$Ifl4F\#5&h`&    4 laf4plllllB90 $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zqkdL$$Ifl4F\#5&h`&    4 laf4plll"s*sDsHC6- $Ifgd9T $If^gdygdYFEƀ^F.gdjqkd$$Ifl4F\#5&h`&    4 laf4pTmUmtmnn nnnnVnXnZndnfnRqTqqqqqqqqqqqqqrrrrr s s s"s(sDsNs+t,tuuFwGw2y3y-z.z^zaz{{}}}} ~ ~ ~)~㻭h'h'5>*jh'h'5>*Uh'h#5h=6]ht,h#5h=CJaJ hh=hmb h#5h=hLw hLwh=jh=U=DsNsPsZs(t5, $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl44F]#%;f&    4 laf4p $$Ifa$gdy(t*t+t,tnuou|s $Ifgd( $Ifgd%qkd)$$Ifl4F]#%;f&    4 laf4p $IfgdLoupuuuuuC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd$$Ifl4F]#%;f&    4 laf4puuu@vv|1J$Eƀ^FvIfgd#5 $Ifgd( $Ifgd%qkda$$Ifl4F]#%;f&    4 laf4pvvvv:qkd$$Ifl4F]#%;f&    4 laf4p $IfgdLJ$Eƀ^FwIfgd#5vvCwEwFw1qkd$$Ifl4F]#%;f&    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdLFwGwwYxxWJ$Eƀ^FyIfgd#5J$Eƀ^FxIfgd#5 $Ifgd( $Ifgd%x0y1y2y3y:1 $Ifgd%qkd5$$Ifl4F]#%;f&    4 laf4p $IfgdLJ$Eƀ^FzIfgd#53yyyyy|1J$Eƀ^F..IfgdLqkd$$Ifl4F]#%;f&    4 laf4p $IfgdL $Ifgd(y*z,z-z.z{{|sj $Ifgd( $Ifgd%qkdm$$Ifl4F]#%;f&    4 laf4p $IfgdL $Ifgd({{{s|||||s $IfgdL $IfgdF $Ifgd%qkd $$Ifl4F]#%;f&    4 laf4p|||}}C:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd$$Ifl4F]#%;f&    4 laf4p}}}~~|s $IfgdL $Ifgd( $Ifgd%qkdA$$Ifl4F]#%;f&    4 laf4p)~*~+~4~5~6~8~~~~~FHڂ܂ނ.02<>34&'klDFdfhtvĵĭĵĥĥĥĒĒĵĵĵĥĥh#5h=6]hLw hLwjh=Uh#5h=]h#5h=CJaJh= h#5h=h' h#5h'h'h'0J5jh'h'5>*U!jh'h'5>*U9~~~12|s $IfgdL $Ifgd( $Ifgd%qkdX$$Ifl4F]#%;f&    4 laf4p238C:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd$$Ifl4F]#%;f&    4 laf4plm|s $IfgdL $Ifgd( $Ifgd%qkd$$Ifl4F]#%;f&    4 laf4pmnsB9 $Ifgdb L$$Eƀ^F..Ifgdb qkd,$$Ifl4F]#%;f&    4 laf4pDOiJ$Eƀ^F}Ifgdb J$Eƀ^F|Ifgdb J$Eƀ^F{Ifgdb OQRW4690 $Ifgdb L$$Eƀ^F..Ifgdb qkd$$Ifl4F]#%;f&    4 laf4p $Ifgdb 67<')B90 $Ifgdb  $Ifgdb L$$Eƀ^F ..Ifgdb qkdd$$Ifl4F]#%;f&    4 laf4p)*/  B90 $Ifgdb  $Ifgdb L$$Eƀ^F ..Ifgdb qkd$$Ifl4F]#%;f&    4 laf4p B9 $Ifgdb L$$Eƀ^F ..Ifgdb qkd$$Ifl4F]#%;f&    4 laf4p i`W $Ifgdb  $Ifgdb J$Eƀ^FIfgdb J$Eƀ^F~Ifgdb C:1 $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqkd8$$Ifl4F]#%;f&    4 laf4p|s $IfgdL $Ifgd( $Ifgd%qkd$$Ifl4F]#%;f&    4 laf4p C:1 $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqkdp$$Ifl4F]#%;f&    4 laf4p|s $IfgdL $Ifgd( $Ifgd%qkd $$Ifl4F]#%;f&    4 laf4p|s $IfgdL $Ifgd( $Ifgd%qkd$$Ifl4F]#%;f&    4 laf4pʑˑuv456>óȧÓȧ牄tj+hf_Rh`5U hf_R5jhf_R5Uju'h$i5h`5Uh=h#rh=0J5>*j%h$i5h`5U h$i55jh$i55Uh#5h=CJaJh#5h=6] h#5h=hLw hLwjh=U-ƌC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkdD $$Ifl4F]#%;f&    4 laf4p|s $IfgdL $Ifgd( $Ifgd%qkd $$Ifl4F]#%;f&    4 laf4p/1B90 $Ifgdb  $Ifgdb L$$Eƀ^F..Ifgdb qkd|!$$Ifl4F]#%;f&    4 laf4p127C:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd"$$Ifl4F]#%;f&    4 laf4p%&|s $IfgdL $Ifgd( $Ifgd%qkd"$$Ifl4F]#%;f&    4 laf4p&',֐ؐB90 $Ifgdb  $Ifgdb L$$Eƀ^F..Ifgdb qkdP#$$Ifl4F]#%;f&    4 laf4pِؐސ%'B90 $Ifgdb  $Ifgdb L$$Eƀ^F..Ifgdb qkd#$$Ifl4F]#%;f&    4 laf4p'(-C:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd$$$Ifl4F]#%;f&    4 laf4pʑ|1J$Eƀ^FIfgd#5 $IfgdF $Ifgd%qkd$%$$Ifl4F]#%;f&    4 laf4pƒ1qkd=&$$Ifl4F]#%;f&    4 laf4p $IfgdLJ$Eƀ^FIfgd#5 $Ifgd1qkd&$$Ifl4F]#%;f&    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdLsqkd'$$Ifl4F]#%;f&    4 laf4p $IfgdL $Ifgd( $Ifgd%Uޕ`J$Eƀ^FIfgd#5 $Ifgd(J$Eƀ^F..IfgdLޕZi` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#512|s $IfgdL $Ifgd( $Ifgd%qkd($$Ifl4F]#%;f&    4 laf4p238C:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd0)$$Ifl4F]#%;f&    4 laf4p՘֘|s $IfgdL $Ifgd( $Ifgd%qkd)$$Ifl4F]#%;f&    4 laf4p֘טܘMOB90 $Ifgd $IfgdL$$Eƀ^F..Ifgdqkdh*$$Ifl4F]#%;f&    4 laf4pOPUVXC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd+$$Ifl4F]#%;f&    4 laf4p>?YZ/0˞̞͞Ԟ՞>?a5ե֥ץOPpqrƲӥ{o_oj)3hf_Rh`5Uh#rh=0J5>*j2hf_Rh`5U hf_R5 h#5h%h h#5h=6]h2>h=5B*ph'j]0h2>h2>5B*Uphh2>hK 85B*ph!jh2>hK 85B*Uphh#5h=CJaJ h#5h=jhf_R5U%XYZ  |s $IfgdL $Ifgd( $Ifgd%qkd,$$Ifl4F]#%;f&    4 laf4p  ,.C:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd,$$Ifl4F]#%;f&    4 laf4p./0uv|s $IfgdL $Ifgd( $Ifgd%qkdQ-$$Ifl4F]#%;f&    4 laf4pvw|B90 $Ifgd $IfgdL$$Eƀ^F..Ifgdqkd-$$Ifl4F]#%;f&    4 laf4pC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd.$$Ifl4F]#%;f&    4 laf4p|s $IfgdL $Ifgd( $Ifgd%qkd%/$$Ifl4F]#%;f&    4 laf4p?AB90 $Ifgd $IfgdL$$Eƀ^F..Ifgdqkd/$$Ifl4F]#%;f&    4 laf4pABGC:1 $IfgdL $Ifgd(J$Eƀ^F..IfgdLqkd0$$Ifl4F]#%;f&    4 laf4p|s $IfgdL $Ifgd( $Ifgd%qkdp1$$Ifl4F]#%;f&    4 laf4p5 bOHCCCCCgd(FEƀ^F.gdjqkd 2$$Ifl4F]#%;f&    4 laf4pop7<IJ'(+9>յֵ׵;<bcdv۷ﯫo_jW8h<#h`5Uj5h<#h`5U h<#5jh<#5U h!{h=h!{h#5h=CJaJ hh=h=hmbhh#rh=0J5>*j3h5h@+5Uh5h55jh5h55U h#5h% h#5h=jhf_R5U%O TLT(,9> $$Ifa$gdy $Ifgd9T $If^gdygdYFEƀ^F.gdjgd(>?D@7. $IfgdL $Ifgd(J$Eƀ^F..IfgdLtkd4$$Ifl44Fl# &;&6.    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd4$$Ifl4Fl# &;&6.    4 laf4p @7. $Ifgd $IfgdL$$Eƀ^F..Ifgdrkd`5$$Ifl4Fl# &;&6.    4 laf4p  ^`@7. $Ifgd $IfgdL$$Eƀ^F..Ifgdrkdz6$$Ifl4Fl# &;&6.    4 laf4p`afUW@7. $Ifgd $IfgdL$$Eƀ^F..Ifgdrkd7$$Ifl4Fl# &;&6.    4 laf4pWX]A8 $Ifgd(J$Eƀ^F..IfgdLrkd7$$Ifl4Fl# &;&6.    4 laf4pϷiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5vwOPԺպ_` /034|ۯ۟h#5h=6j[Ih<#h`5UjIHh<#h`5Uh#rh=0J5>*jEh<#h`5U h<#5ht,h#5h=CJaJ h#5h=jh<#5U;&LiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5LNOPzq $Ifgd( $Ifgd%rkd8$$Ifl4Fl# &;&6.    4 laf4p $IfgdLzq $IfgdL $Ifgd( $Ifgd%rkd9$$Ifl4Fl# &;&6.    4 laf4p^`@7. $Ifgd $IfgdL$$Eƀ^F..Ifgdrkd :$$Ifl4Fl# &;&6.    4 laf4p`afѺӺA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd:$$Ifl4Fl# &;&6.    4 laf4pӺԺպDEzq $IfgdL $Ifgd( $Ifgd%rkd^;$$Ifl4Fl# &;&6.    4 laf4pEFK߻A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd;$$Ifl4Fl# &;&6.    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd<$$Ifl4Fl# &;&6.    4 laf4p$A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd;=$$Ifl4Fl# &;&6.    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd=$$Ifl4Fl# &;&6.    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdy>$$Ifl4Fl# &;&6.    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd?$$Ifl4Fl# &;&6.    4 laf4p߾A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd?$$Ifl4Fl# &;&6.    4 laf4pul $IfgdL$Ifgd(of $Ifgd%rkdV@$$Ifl4Fl# &;&6.    4 laf4p \^A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd@$$Ifl4Fl# &;&6.    4 laf4p^_`zq $IfgdL $Ifgd( $Ifgd%rkdA$$Ifl4Fl# &;&6.    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd3B$$Ifl4Fl# &;&6.    4 laf4p zq $IfgdL $Ifgd( $Ifgd%rkdB$$Ifl4Fl# &;&6.    4 laf4p@7. $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zrkdqC$$Ifl4Fl# &;&6.    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdD$$Ifl4Fl# &;&6.    4 laf4pQRzq $IfgdL $Ifgd( $Ifgd%rkdD$$Ifl4Fl# &;&6.    4 laf4pRSXA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdNE$$Ifl4Fl# &;&6.    4 laf4p zq $IfgdL $Ifgd( $Ifgd%rkdlF$$Ifl4Fl# &;&6.    4 laf4p  A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd G$$Ifl4Fl# &;&6.    4 laf4p23zq $IfgdL $Ifgd( $Ifgd%rkdG$$Ifl4Fl# &;&6.    4 laf4p349A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdH$$Ifl4Fl# &;&6.    4 laf4pVWzq $IfgdL $Ifgd( $Ifgd%rkdI$$Ifl4Fl# &;&6.    4 laf4pWX]A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdqJ$$Ifl4Fl# &;&6.    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdK$$Ifl4Fl# &;&6.    4 laf4p02A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdK$$Ifl4Fl# &;&6.    4 laf4p234zq $IfgdL $Ifgd( $Ifgd%rkdNL$$Ifl4Fl# &;&6.    4 laf4p|}PQhj`b^`~\^d~   λλλΦΟΛΔηΊ h.5jh.5U hh=h\ h#5h%h#5h=6hLw hLwh=jh=Uh#5h=CJaJ h#5h=h#rh=0J5>*jLh<#h`5U h<#5jh<#5U3IK@7. $Ifgd $IfgdL$$Eƀ^F..IfgdrkdjM$$Ifl4Fl# &;&6.    4 laf4pKLQMOA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd N$$Ifl4Fl# &;&6.    4 laf4pOPQzq $IfgdL $Ifgd( $Ifgd%rkdN$$Ifl4Fl#7&;&6    4 laf4p@A8 $Ifgd(J$Eƀ^F..IfgdLrkdGO$$Ifl4Fl#7&;&6    4 laf4p@@iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#58/ $Ifgd%rkdO$$Ifl4Fl#7&;&6    4 laf4p $IfgdLJ$Eƀ^FIfgd<>@Bzq $Ifgd%rkdP$$Ifl4Fl#7&;&6    4 laf4p $IfgdL $Ifgd(^b@7. $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6zrkd$Q$$Ifl4Fl#7&;&6    4 laf4pbd~U`F7FAAAAAgd(FEƀ^F.gdjrkdQ$$Ifl4Fl#7&;&6    4 laf4p7!_tkdbR$$Ifl44F]#%<f&6    4 laf4p $$Ifa$gdy $Ifgd9T $If^gdygdYgd( z`J$Eƀ^FIfgd#5 $Ifgd(J$Eƀ^F..IfgdL  i` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5   uz/J$Eƀ^FIfgd $Ifgd( $Ifgd%rkd S$$Ifl4F]#%<f&6    4 laf4p*jiJ$Eƀ^FIfgdJ$Eƀ^FIfgdJ$Eƀ^FIfgd678@AS_&'noLM;<>BCξήӧӜӜӒ}ڒӜӜӜyqh=CJaJhc jWhhj 5U h5jh5Uh#5h=CJaJ h.h=jTh.hj 5Uj(Th.hj 5U h.5 h#5h=h#rh=0J5>*jh.5UjSh.hj 5U+j~iJ$Eƀ^FIfgdJ$Eƀ^FIfgdJ$Eƀ^FIfgdEiJ$Eƀ^FIfgdJ$Eƀ^FIfgdJ$Eƀ^FIfgdEdi` $IfgdLJ$Eƀ^FIfgdJ$Eƀ^FIfgdzq $IfgdL $Ifgd( $Ifgd%rkd"U$$Ifl4F]#%<f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdU$$Ifl4F]#%<f&6    4 laf4p@7. $Ifgd $IfgdL$$Eƀ^F..Ifgdrkd`V$$Ifl4F]#%<f&6    4 laf4pkmA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdV$$Ifl4F]#%<f&6    4 laf4pmnozq $IfgdL $Ifgd( $Ifgd%rkdX$$Ifl4F]#%<f&6    4 laf4p<>@7. $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]rkdX$$Ifl4F]#%<f&6    4 laf4p>?DA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd[Y$$Ifl4F]#%<f&6    4 laf4p<=zq $IfgdL $Ifgd( $Ifgd%rkdY$$Ifl4F]#%<f&6    4 laf4p=>C@7. $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]rkdZ$$Ifl4F]#%<f&6    4 laf4pIKA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd8[$$Ifl4F]#%<f&6    4 laf4pKLMabzq $IfgdL $Ifgd( $Ifgd%rkd[$$Ifl4F]#%<f&6    4 laf4pbch;=@7. $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]rkdv\$$Ifl4F]#%<f&6    4 laf4p=>C@7. $Ifgd] $Ifgd]L$$Eƀ^F ..Ifgd]rkd]$$Ifl4F]#%<f&6    4 laf4pvwk   z}/3AFPüǵǫdžrh#5hbB*aJph hhbhbh#rhb0J5>*j(eh.hj 5U h.5jh.5U h#5h0 h#5h.h. h#5hb h#5h%hLw hLwjh=Uh h#5h=CJaJ h#5h=h=*24@7. $Ifgd] $Ifgd]L$$Eƀ^F ..Ifgd]rkd]$$Ifl4F]#%<f&6    4 laf4p45:A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdS^$$Ifl4F]#%<f&6    4 laf4p zq $IfgdL $Ifgd( $Ifgd%rkd^$$Ifl4F]#%<f&6    4 laf4p@7. $Ifgd] $Ifgd]L$$Eƀ^F ..Ifgd]rkd_$$Ifl4F]#%<f&6    4 laf4psuA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd0`$$Ifl4F]#%<f&6    4 laf4puvw"#zq $IfgdL $Ifgd( $Ifgd%rkd`$$Ifl4F]#%<f&6    4 laf4p#$)@7. $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]rkdna$$Ifl4F]#%<f&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd b$$Ifl4F]#%<f&6    4 laf4p#$zq $IfgdL $Ifgd( $Ifgd%rkdb$$Ifl4F]#%<f&6    4 laf4p$%*A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdKc$$Ifl4F]#%<f&6    4 laf4p  zq $IfgdL $Ifgd( $Ifgd%rkdc$$Ifl4F]#%<f&6    4 laf4p *0FAA<gdYgd(FEƀ^F.gdjrkdd$$Ifl4F]#%<f&6    4 laf4p04AFGdykde$$Ifl44F]#%;f&6    4 laf4g̴fp $$Ifa$gdy $Ifgd9T $If^gdyGLFHI)wkdKf$$Ifl4F]#%;f&6    4 laf4g̴fp $Ifgd $IfgdL$$Eƀ^F..IfgdIN_J$Eƀ^FIfgd] $Ifgd]L$$Eƀ^F..Ifgd]egi` $Ifgd]J$Eƀ^FIfgd]J$Eƀ^FIfgd]ghm;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkdf$$Ifl4F]#%;f&6    4 laf4g̴fpMO<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkdg$$Ifl4F]#%;f&6    4 laf4g̴fpOPQ~ul $IfgdL $Ifgd( $Ifgd%wkdFh$$Ifl4F]#%;f&6    4 laf4g̴fpPQw,-0>CL z{12A NPO P       "#Ŀ h#5hf[)h#rhb0J5>*jrh/hj 5U h/5jh/5Uh hLw hLwjhbUh0h]hb6 hhbhbhFT h#5h% h#5hbh#5hbCJaJ4tv;2) $Ifgd $IfgdL$$Eƀ^F..Ifgdwkdh$$Ifl4F]#%;f&6    4 laf4g̴fpvw-A<<7gdYgd(FEƀ^F.gdjwkdi$$Ifl4F]#%;f&6    4 laf4g̴fp-1>CDitkdAj$$Ifl44F\#%;e&6    4 laf4p $$Ifa$gdy $Ifgd9T $If^gdyDI/rkdj$$Ifl4F\#%;e&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdLqrkdk$$Ifl4F\#%;e&6    4 laf4p $IfgdL $Ifgd( $Ifgd%L`J$Eƀ^FIfgd#5 $Ifgd(J$Eƀ^F..IfgdL8/ $Ifgd%rkd'l$$Ifl4F\#%;e&6    4 laf4p $IfgdLJ$Eƀ^FIfgd#56}`W $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5 $Ifgd($%zqh $IfgdL $Ifgd $Ifgd( $Ifgd%rkdl$$Ifl4F\#%;e&6    4 laf4p%&+wyA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdem$$Ifl4F\#%;e&6    4 laf4pyz{RSzq $IfgdL $Ifgd( $Ifgd%rkdn$$Ifl4F\#%;e&6    4 laf4pSTYA8 $Ifgd(J$Eƀ^F..IfgdLrkdn$$Ifl4F\#%;e&6    4 laf4p5i` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5zq $IfgdL $Ifgd( $Ifgd%rkdBo$$Ifl4F\#%;e&6    4 laf4pJLzq $IfgdL $Ifgd( $Ifgd%rkdo$$Ifl4F\#%;e&6    4 laf4pLNPzq $IfgdL $Ifgd( $Ifgd%rkdp$$Ifl4F\#%;e&6    4 laf4pL N A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdq$$Ifl4F\#%;e&6    4 laf4pN O P   zq $IfgdL $Ifgd( $Ifgd%rkdq$$Ifl4F\#%;e&6    4 laf4p   i } FAAAAgd(FEƀ^F.gdw$Frkd]r$$Ifl4F\#%;e&6    4 laf4p $$Ifa$gdn $Ifgd9T $If^gdnFEƀ^F.gd0?@ 78    $#&#D#F#H#T#V#X#Z#$$%%,%-%<%&&&&&&''e-f-»hprh#5hb5\ h#5h h h#5hb]hLw hLwhbjhbUh0h#5hbCJaJ hhb h#5hbD]_:1( $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]ykdys$$Ifl44F]#%;f&6    4 laf4gfp_`e;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkd+t$$Ifl4F]#%;f&6    4 laf4gfp<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkdt$$Ifl4F]#%;f&6    4 laf4gfp  ~ul $IfgdL $Ifgd( $Ifgd%wkd}u$$Ifl4F]#%;f&6    4 laf4gfp };2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkd&v$$Ifl4F]#%;f&6    4 laf4gfp;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkdv$$Ifl4F]#%;f&6    4 laf4gfp;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkdxw$$Ifl4F]#%;f&6    4 laf4gfp;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkd!x$$Ifl4F]#%;f&6    4 laf4gfp<><3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkdx$$Ifl4F]#%;f&6    4 laf4gfp>?@~ul $IfgdL $Ifgd( $Ifgd%wkdsy$$Ifl4F]#%;f&6    4 laf4gfp?A;2) $Ifgd] $Ifgd]L$$Eƀ^F ..Ifgd]wkdz$$Ifl4F]#%;f&6    4 laf4gfpABG<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkdz$$Ifl4F]#%;f&6    4 laf4gfpTU~ul $IfgdL $Ifgd( $Ifgd%wkdn{$$Ifl4F]#%;f&6    4 laf4gfpUV[<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkd|$$Ifl4F]#%;f&6    4 laf4gfp~ul $IfgdL $Ifgd( $Ifgd%wkd|$$Ifl4F]#%;f&6    4 laf4gfp;2) $Ifgd] $Ifgd]L$$Eƀ^F ..Ifgd]wkdi}$$Ifl4F]#%;f&6    4 laf4gfp $;2) $Ifgd] $Ifgd]L$$Eƀ^F ..Ifgd]wkd~$$Ifl4F]#%;f&6    4 laf4gfp$&046<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkd~$$Ifl4F]#%;f&6    4 laf4gfp678\#^#~ul $IfgdL $Ifgd( $Ifgd%wkdd$$Ifl4F]#%;f&6    4 laf4gfp^#`#j#$$<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkd $$Ifl4F]#%;f&6    4 laf4gfp$$$&&~ul $IfgdL $Ifgd( $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfp&&&''<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkd_$$Ifl4F]#%;f&6    4 laf4gfp'''(g,h,~uul $IfgdL $IfgdF $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfph,i,n,..<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkd$$Ifl4F]#%;f&6    4 laf4gfpf-u-......002(2)23334444:4<4>4@4^4`4b4n4p4L5N5l5n5p5|5~5,6-6667777788 888888888::<:Z:\:^:j:l:::<<=="?#?F@G@h8ch#5hb5\hQ\h#5hprhpr h#5hprh#5hbCJaJ h#5hbhLw hLwjhbUhbH...//~ul $IfgdL $Ifgd( $Ifgd%wkdZ$$Ifl4F]#%;f&6    4 laf4gfp///00<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkd$$Ifl4F]#%;f&6    4 laf4gfp000162~u*J$Eƀ^FIfgd#5 $Ifgd $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfp6226373i` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#57383=3z3;2 $Ifgd]L$$Eƀ^F..Ifgd]wkdU$$Ifl4F]#%;f&6    4 laf4gfpz3v4|444`W $Ifgd]J$Eƀ^FIfgd] $Ifgd]J$Eƀ^FIfgd56444 5;2 $Ifgd]L$$Eƀ^F..Ifgd]wkd$$Ifl4F]#%;f&6    4 laf4gfp 5555i` $Ifgd]J$Eƀ^FIfgd]J$Eƀ^FIfgd]5556<3 $Ifgd(J$Eƀ^F..IfgdLwkd$$Ifl4F]#%;f&6    4 laf4gfp66)6+6i` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5+6,6-666~ul $IfgdL $Ifgd( $Ifgd%wkdP$$Ifl4F]#%;f&6    4 laf4gfp66677<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkd$$Ifl4F]#%;f&6    4 laf4gfp77799~ul $IfgdL $Ifgd( $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfp999<<<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkdK$$Ifl4F]#%;f&6    4 laf4gfp<<<==~ul $IfgdL $Ifgd( $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfp====o>~u*J$Eƀ^FIfgd#5 $Ifgd( $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfpo>v>> ?!? $IfgdLJ$Eƀ^FIfgd#5 $Ifgd&t[!?"?#?O??~u*J$Eƀ^FIfgd#5 $Ifgd( $Ifgd%wkdF$$Ifl4F]#%;f&6    4 laf4gfp?D@E@F@G@3* $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfp $IfgdLJ$Eƀ^FIfgd#5G@@ACCC`WN $IfgdL $IfgdFJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5 $Ifgd(CCCPiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5>P@PAPBPPP~ul $Ifgd( $Ifgd%wkd $$Ifl4F]#%;f&6    4 laf4gfp $IfgdLPPPHQIQ~ul $IfgdL $Ifgd( $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfpIQJQOQQQ;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkd]$$Ifl4F]#%;f&6    4 laf4gfpQQQR R<3* $IfgdL $Ifgd(J$Eƀ^F..IfgdLwkd$$Ifl4F]#%;f&6    4 laf4gfp R"R$RMTNT~ul $IfgdL $Ifgd( $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfpNTOTTTTT;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkdX$$Ifl4F]#%;f&6    4 laf4gfpTTT1U3U;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkd$$Ifl4F]#%;f&6    4 laf4gfp3U4U9UUU;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkd$$Ifl4F]#%;f&6    4 laf4gfpUUU V$V;2) $Ifgd] $Ifgd]L$$Eƀ^F..Ifgd]wkdS$$Ifl4F]#%;f&6    4 laf4gfp$V&V0VlWpW;2) $Ifgd] $Ifgd]L$$Eƀ^F ..Ifgd]wkd$$Ifl4F]#%;f&6    4 laf4gfppWrW|WMX<3 $Ifgd(J$Eƀ^F!..IfgdLwkd$$Ifl4F]#%;f&6    4 laf4gfpMXXX6Y8Y\S $IfgdLJ$Eƀ^FIfgd#5 & F$Ifgd8cJ$Eƀ^FIfgd#58Y9Y:Y[[~ul $IfgdL $Ifgd( $Ifgd%wkdN$$Ifl4F]#%;f&6    4 laf4gfpFZHZ]]]]]]]]]]]]^^__ a!adeee'f*f+fwffff5g7gggggg h hh0hhhhhhJj𧓧 hhbhbhFThHo h#5h/h#5hbB*aJphh/ h#5hg{hg{ h#5h%hLw hLwjhZUhkjhkUh#5hbCJaJh#5hb] h#5hbjhbU/[[[\\;2) $Ifgd] $Ifgd]L$$Eƀ^F"..Ifgd]wkd$$Ifl4F]#%;f&6    4 laf4gfp\\\]]<3* $IfgdL $Ifgd(J$Eƀ^F#..IfgdLwkd$$Ifl4F]#%;f&6    4 laf4gfp]]]]]~ul $IfgdL $Ifgd( $Ifgd%wkdI$$Ifl4F]#%;f&6    4 laf4gfp]]]^^<3* $IfgdL $Ifgd(J$Eƀ^F$..IfgdLwkdo$$Ifl4F]#%;f&6    4 laf4gfp^^^^^~ul $IfgdL $Ifgd( $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfp^^^3_5_;2) $Ifgds} $Ifgds}L$$Eƀ^F%..Ifgds}wkd$$Ifl4F]#%;f&6    4 laf4gfp5_6_;___<3* $IfgdL $Ifgd(J$Eƀ^F&..IfgdLwkdj$$Ifl4F]#%;f&6    4 laf4gfp___%`~3J$Eƀ^FIfgd#5 $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gfp%`J`c`d`i] $$Ifa$gd%J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5d`e`j`aa<3* $IfgdL $Ifgd(J$Eƀ^F'..IfgdLwkd$$Ifl4F]#%;f&6    4 laf4gfpa a!aaa~ul $IfgdL $Ifgd( $Ifgd%wkde$$Ifl4F]#%;f&6    4 laf4gfpaaa*b,b;2) $Ifgds} $Ifgds}L$$Eƀ^F(..Ifgds}wkd$$Ifl4F]#%;f&6    4 laf4gfp,b-b2bcc;2) $Ifgds} $Ifgds}L$$Eƀ^F)..Ifgds}wkd$$Ifl4F]#%;f&6    4 laf4gfpccc=d?d;2) $Ifgds} $Ifgds}L$$Eƀ^F*..Ifgds}wkd`$$Ifl4F]#%;f&6    4 laf4gfp?d@dEddd;2) $Ifgds} $Ifgds}L$$Eƀ^F+..Ifgds}wkd $$Ifl4F]#%;f&6    4 laf4gfpddefhA<7gdYgd(FEƀ^F.gd0wkd$$Ifl4F]#%;f&6    4 laf4gfphhhhhitkd[$$Ifl44F]#%;f&6    4 laf4p $$Ifa$gdn $Ifgd9T $If^gdnhhiii.rkd$$Ifl4F]#%;f&6    4 laf4p $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}iiLjNjOj/rkd$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdLJjKjOjPj"k#kAkBkCkMkNkkkqlrlllllll*m+mnnppqqq8qZu[u\uguhuuuuuvvwwwJwKwwڹyjhM<60JU hhM<6 h#5hM<6hM<6hFT h#5hHohHo h#5h%hc h#5hb6]h#rhb0J5>*jhHohj 5U hHo5jhHo5Uh#5hbCJaJ h#5hbh#5hb5\/OjPjjjjqrkdA$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd( $Ifgd%jjkkk.rkd[$$Ifl4F]#%;f&6    4 laf4p $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}kk;ll`J$Eƀ^FIfgd#5 $Ifgd(J$Eƀ^F..IfgdLllm'miJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5'm)m*m+mmmzq $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p $IfgdLmmmmm@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F]#%;f&6    4 laf4pmmmunwn@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd8$$Ifl4F]#%;f&6    4 laf4pwnxn}nnnA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdר$$Ifl4F]#%;f&6    4 laf4pnnnIoJozq $IfgdL $Ifgd( $Ifgd%rkdv$$Ifl4F]#%;f&6    4 laf4pJoKoPoEp@7 $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F]#%;f&6    4 laf4pEppqqqqi``` $Ifgds}J$Eƀ^FIfgds}J$Eƀ^FIfgds}qq8qqqFAAgd(FEƀ^F.gd0rkd$$Ifl4F]#%;f&6    4 laf4pqNrrsstuxvvwsnnnnni\ $If^gdngdYgd(FEƀ^Fgdz^FEƀ^Fgdz^ wwwwwv+J$Eƀ^F..IfgdLtkdS$$Ifl44F^#%;g&6    4 laf4p $$Ifa$gdn $Ifgd9Twwwwwyyzqh $Ifgd( $Ifgd%rkd$$Ifl4F^#%;g&6    4 laf4p $IfgdL $Ifgd(wwwwwxx xx yy.z/z{{{{{{{{{{||||~~~~$%\]wx89STUVʄքކh|vh'h#5hM<6hRrhQEh#5hM<66h#5hM<6h}i hqhU h|hh#5hM<65hfZahfZamHnHuhLw hLwhM<6jhM<6U h#5hM<6h#5hM<6CJaJ9y y*y/z1z@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F^#%;g&6    4 laf4p1z2z7zzz@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd9$$Ifl4F^#%;g&6    4 laf4pzzz{{A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdح$$Ifl4F^#%;g&6    4 laf4p{{{||zq $IfgdL $Ifgd( $Ifgd%rkdw$$Ifl4F^#%;g&6    4 laf4p||$| }A8 $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F^#%;g&6    4 laf4p }r}}&~iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5&~a~~~i` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5~~~$%zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F^#%;g&6    4 laf4p%&+A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdT$$Ifl4F^#%;g&6    4 laf4pwxzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F^#%;g&6    4 laf4pxy~@7 $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F^#%;g&6    4 laf4pTVi` $Ifgds}J$Eƀ^FIfgds}J$Eƀ^FIfgds}VW\˂@7 $Ifgds}L$$Eƀ^F..Ifgds}rkd1$$Ifl4F^#%;g&6    4 laf4p˂wi` $Ifgds}J$Eƀ^FIfgds}J$Eƀ^FIfgds}@7 $Ifgds}L$$Eƀ^F ..Ifgds}rkdв$$Ifl4F^#%;g&6    4 laf4pDŽAiJ$Eƀ^FIfgds}J$Eƀ^FIfgds}J$Eƀ^FIfgds}.248rkdo$$Ifl4F^#%;g&6    4 laf4p $Ifgds}J$Eƀ^FIfgds}4> /rkd$$Ifl4F^#%;g&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdLpr !12KNOij "@BDPR\^|~  ƶ˪Ƈ˪jhhj 5U h#5hhh#5hM<66h#rhM<60J5>*jhhj 5U h5jh5Uh#5hM<6CJaJhLw hLwhM<6jhM<6U h#5hM<6h|v5 !ˆÈqrkd$$Ifl4F^#%;g&6    4 laf4p $Ifgds} $Ifgds} $Ifgds}ÈȈ(*+.rkdL$$Ifl4F^#%;g&6    4 laf4p $Ifgds} $Ifgds}L$$Eƀ^F ..Ifgds}+0.rkd`$$Ifl4F^#%;g&6    4 laf4p $Ifgds} $Ifgds}L$$Eƀ^F ..Ifgds}ĉ.01+rkd$$Ifl4F^#%;g&6    4 laf4p $$Ifgd $$IfgdJ$Eƀ^F ..Ifgd12ghijXYqrkd$$Ifl4F^#%;g&6    4 laf4p $IfgdL $Ifgd( $Ifgd%YZ_A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd=$$Ifl4F^#%;g&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdܸ$$Ifl4F^#%;g&6    4 laf4p zq $IfgdL $Ifgd( $Ifgd%rkd{$$Ifl4F^#%;g&6    4 laf4p !&A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F^#%;g&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd*$$Ifl4F^#%;g&6    4 laf4p- !"/0ޙ&'œΝޞߞʺϮʄjhhj 5U h#5h` h#5h%hfZahfZamHnHuh#rhM<60J5>*jhhj 5U h5jh5Uh#5hM<6CJaJhLw hLwhM<6jhM<6U h#5hM<6/"<@7 $Ifgds}L$$Eƀ^F..Ifgds}rkdɻ$$Ifl4F^#%;g&6    4 laf4p< i` $Ifgds}J$Eƀ^FIfgds}J$Eƀ^FIfgds}:<@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkdh$$Ifl4F^#%;g&6    4 laf4p<=BA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F^#%;g&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F^#%;g&6    4 laf4p6A8 $Ifgd(J$Eƀ^F..IfgdLrkdE$$Ifl4F^#%;g&6    4 laf4p6?FQiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5QZ~i`W $IfgdL $IfgdAdJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5zq $IfgdL $Ifgd( $Ifgd%rkde$$Ifl4F^#%;g&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F^#%;g&6    4 laf4p@7 $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F^#%;g&6    4 laf4p>cjiJ$Eƀ^FIfgds}J$Eƀ^FIfgds}J$Eƀ^FIfgds}jw(iJ$Eƀ^FIfgds}J$Eƀ^FIfgds}J$Eƀ^FIfgds}(8rkdB$$Ifl4F^#%;g&6    4 laf4p $Ifgds}J$Eƀ^FIfgds};=>.rkd$$Ifl4F^#%;g&6    4 laf4p $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}>C/rkd$$Ifl4F^#%;g&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdLĜŜƜqrkd$$Ifl4F^#%;g&6    4 laf4p $IfgdL $Ifgd( $Ifgd%Ɯ˜   .rkd$$Ifl4F^#%;g&6    4 laf4p $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds} ˝͝Ν.rkd]$$Ifl4F^#%;g&6    4 laf4p $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}Νϝӟߟ Lgd(gd9TFEƀ^F.gd0gdY  ʠ¡ġơ"#?@AHIPQX`ejksHIjĽğ㓇}qmc^ h]5jh]5Uh hfZahfZamHnHujh`0JUh#5h^QmHnHuh#5h`mHnHuh#rh`0J5>*\!jh]hj 5U\ h]5\jh]5U\h#5h`\h#lh]hy h#5h`jh5Uh#rh`0J5>*jklxyϤԤ-./5EJХۥLTU|}~˧֧:;Zڷӛӗӓӓӏӄzu h#5jh#5U hh`h`hFThc h#l h#5h#ljwhqZh@+5U hqZ5jhqZ5U h#5h% h#5h h h#5h`h#rh`0J5>*jh]5Ujh]hj 5U+LT $$Ifa$gdn $Ifgd9T $If^gdngdYgd(FEƀ^F.gd0@7 $Ifgd(J$Eƀ^F..IfgdLtkd$$Ifl44F\#%;e&6    4 laf4pZ[\ghKLM[`aƫǫwxϮЮ֮ϰҰӰѲҲ>?/01svw,->?@ҷַFGHI.0bĸӸӮӦӦӦӢӦӦӗӍ h#5h#5h`hP,h' h#5h#lh#l *h#5h`h#5h`h~Pth#5h`mHnHuh#5h`CJaJh} h#5h`h#rh`0J5>*jh#5Ujh#hj 5U2ʪ]iJ$Eƀ^FIfgd|J$Eƀ^FIfgd|J$Eƀ^FIfgd|]_`aīūzq $Ifgd( $Ifgd%rkd)$$Ifl4F\#%;e&6    4 laf4p $IfgdLūƫǫӭ z/J$Eƀ^FIfgd#5 $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p &-8iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#58ScjiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5juvwx8/ $Ifgd%rkdg$$Ifl4F\#%;e&6    4 laf4p $IfgdLJ$Eƀ^FIfgd#5xͮήϮЮzq $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p $IfgdL $Ifgd(Ю֮2HiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5HZiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#57iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#57eiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5ɰаѰi` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5ѰҰӰzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdD$$Ifl4F\#%;e&6    4 laf4pѲҲzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pҲӲز<>@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F\#%;e&6    4 laf4p>?D-/A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd!$$Ifl4F\#%;e&6    4 laf4p/01Oqz/J$Eƀ^FIfgd#5 $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pq8/ $Ifgd%rkd_$$Ifl4F\#%;e&6    4 laf4p $IfgdLJ$Eƀ^FIfgd#5+,-2z/J$Eƀ^F..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p $IfgdL $Ifgd(2<>?@ҷzqh $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p $IfgdL $Ifgd(ҷFGi` $IfgdLJ$Eƀ^F Ifgd#5J$Eƀ^FIfgd#5GHIȻʻzq $IfgdL $Ifgd( $Ifgd%rkd<$$Ifl4F\#%;e&6    4 laf4pbdfprʻ̻{|ӼԼXYZνнѽ4@CHؿڿۿxz¾ӶӶ污ӶӶӊ~ӶӖ¾h0Ah`mHnHuh#5h`mHnHuh#5h`CJaJjh#hj 5U h#5 *h#5h`hLw hLwh`jh`U h#5h`h#rh`0J5>*jh#5Ujh#hj 5U-ʻֻ̻y{@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkdL$$Ifl4F\#%;e&6    4 laf4p{|VXA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4pXYZνϽzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pϽнѽؿٿzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pٿڿۿz/J$Eƀ^F Ifgd#5 $Ifgd( $Ifgd%rkd?$$Ifl4F\#%;e&6    4 laf4p\/rkd$$Ifl4F\#%;e&6    4 laf4p $IfgdL $IfgdFJ$Eƀ^F Ifgd#5rvx/rkd}$$Ifl4F\#%;e&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdLxzqrkd$$Ifl4F\#%;e&6    4 laf4p $IfgdL $Ifgd( $Ifgd%NPQ/rkd$$Ifl4F\#%;e&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdLMQR   :;\]PQijkno !xySTEO  KL,-UVóȧjh`Uh`hfZahfZamHnHuh%h#5h`hkh#rh'0J5>*jh5h@+5U h55jh55Uh#5h`0J2B*phh#5h`CJaJ h#5h`h#5h`0J26B*ph2QR    qrkdZ$$Ifl4F\#%;e&6    4 laf4p $IfgdL $Ifgd( $Ifgd%79A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p9:;zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p[]@7. $Ifgds} $Ifgds}L$$Eƀ^F ..Ifgds}rkd7$$Ifl4F\#%;e&6    4 laf4p]^cY[A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p[\]zq $IfgdL $Ifgd( $Ifgd%rkdu$$Ifl4F\#%;e&6    4 laf4p'(zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p().@7. $Ifgds} $Ifgds}L$$Eƀ^F ..Ifgds}rkd"$$Ifl4F\#%;e&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd`$$Ifl4F\#%;e&6    4 laf4p !zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F\#%;e&6    4 laf4p@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd=$$Ifl4F\#%;e&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4pz/J$Eƀ^F Ifgd#5 $Ifgd( $Ifgd%rkd{$$Ifl4F\#%;e&6    4 laf4pz{|/rkd$$Ifl4F\#%;e&6    4 laf4p $IfgdL $IfgdFJ$Eƀ^F Ifgd#5|z`J$Eƀ^FIfgd#5 $Ifgd(J$Eƀ^F..IfgdLiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5)PRi`W $IfgdL $Ifgd|J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5RSTXYzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pYZ_A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdX$$Ifl4F\#%;e&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p   zq $IfgdL $Ifgd( $Ifgd%rkd5$$Ifl4F\#%;e&6    4 laf4pHJA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4pJKLzq $IfgdL $Ifgd( $Ifgd%rkds$$Ifl4F\#%;e&6    4 laf4p$&@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F\#%;e&6    4 laf4p&',@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F\#%;e&6    4 laf4p)+A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdP$$Ifl4F\#%;e&6    4 laf4p+,-pqzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pqrw @7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F\#%;e&6    4 laf4p !&@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd-$$Ifl4F\#%;e&6    4 laf4p(*@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkd$$Ifl4F\#%;e&6    4 laf4p*+0@7. $Ifgds} $Ifgds}L$$Eƀ^F..Ifgds}rkdk$$Ifl4F\#%;e&6    4 laf4pRTA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd $$Ifl4F\#%;e&6    4 laf4pTUVzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p   ()QR*+klpq-.cdsz|bd9:oqr䰨 h#5hxhxhx6h#5hxCJaJh#5h`6]h#5h`hTAh#5h`h/h#5h`CJaJ h#5h`hLw hLwjh`Uh`?$*.@7. $Ifgdj $IfgdjL$$Eƀ^F..IfgdjrkdH$$Ifl4F\#%;e&6    4 laf4p.0:A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p"$zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p$&0%'A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd%$$Ifl4F\#%;e&6    4 laf4p'()stzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4ptuz@7 $IfgdjL$$Eƀ^F ..Ifgdjrkdc$$Ifl4F\#%;e&6    4 laf4p*UiJ$Eƀ^FIfgdjJ$Eƀ^FIfgdjJ$Eƀ^FIfgdj&7. $IfgdjL$$Eƀ^F!..Ifgdjrkd$$Ifl4F\#%;e&6    4 laf4p $Ifgdj&viJ$Eƀ^FIfgdjJ$Eƀ^FIfgdjJ$Eƀ^FIfgdji` $IfgdjJ$Eƀ^FIfgdjJ$Eƀ^FIfgdjNPA8/ $IfgdL $Ifgd(J$Eƀ^F"..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4pPQREFzq $IfgdL $Ifgd( $Ifgd%rkd@$$Ifl4F\#%;e&6    4 laf4pFGL')A8/ $IfgdL $Ifgd(J$Eƀ^F#..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p)*+zq $IfgdL $Ifgd( $Ifgd%rkd~$$Ifl4F\#%;e&6    4 laf4pmoA8/ $IfgdL $Ifgd(J$Eƀ^F$..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4popqzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F%..IfgdLrkd[$$Ifl4F\#%;e&6    4 laf4p+,zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p,-.zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pDH@7. $Ifgdj $IfgdjL$$Eƀ^F&..Ifgdjrkd8$$Ifl4F\#%;e&6    4 laf4pHJTA8/ $IfgdL $Ifgd(J$Eƀ^F'..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p29z/J$Eƀ^FIfgd#5 $Ifgd( $Ifgd%rkdv$$Ifl4F\#%;e&6    4 laf4p9?GRiJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5RSTY688/ $Ifgd(J$Eƀ^F(..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p $IfgdL89:zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p~@7 $IfgdjL$$Eƀ^F)..IfgdjrkdS$$Ifl4F\#%;e&6    4 laf4p~ Yi`W $Ifgdj $IfgdjJ$Eƀ^F!IfgdjJ$Eƀ^F Ifgdjopsja $Ifgdx $Ifgdx & F ccQ$If^c`Qgdxrkd$$Ifl4F\#%;e&6    4 laf4ppqrsja $Ifgdx $Ifgdx & F ccQ$If^c`Qgdxrkd$$Ifl4F\#%;e&6    4 laf4pr  ".0@PGHKLabq fg ۾۳h#5h`]h#5h`CJaJh#5h`B*ph hh`hFT hwh#h#hLw hLwh`jh`Uh@F0 hwh` h#5h` h#5h% h#5hxhxhx68KFAgd(FEƀ^F.gd0rkd0$$Ifl4F\#%;e&6    4 laf4pKss-FEƀ^F$gd#5FEƀ^F#gd#5FEƀ^F"gd#51i <snni\SG $$Ifa$gdn $Ifgd9T $If^gdngdYgdwFEƀ^F&gdwFEƀ^F%gdwHJA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4pJKLzq $IfgdL $Ifgd( $Ifgd%rkdt$$Ifl4F]#%;f&6    4 laf4p$A8 $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p?iJ$Eƀ^F)Ifgd#5J$Eƀ^F(Ifgd#5J$Eƀ^F'Ifgd#5zq $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p $IfgdL@7. $Ifgdj $IfgdjL$$Eƀ^F..IfgdjrkdQ$$Ifl4F]#%;f&6    4 laf4pceA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4pefgzz/J$Eƀ^F*Ifgd#5 $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4pUiJ$Eƀ^F-Ifgd#5J$Eƀ^F,Ifgd#5J$Eƀ^F+Ifgd#5$7. $IfgdjL$$Eƀ^F..Ifgdjrkd.$$Ifl4F]#%;f&6    4 laf4p $IfgdL8/ $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p $Ifgdj  zq $Ifgd( $Ifgd%rkdl$$Ifl4F]#%;f&6    4 laf4p $IfgdL     A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd $$Ifl4F]#%;f&6    4 laf4p              DSU]^S\#)*#/0@AUﱪﱪ烈hFT h#5h8h8 h#5hZ_hZ_ h#5hXhX h#5hYehYe h#5hlohlo)h#5h`B*CJOJQJ^JaJphhxh# h#5h%h#5h`CJaJ h#5h`h#5h`6]2     z/J$Eƀ^F.Ifgd#5 $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p 7 S c iJ$Eƀ^F1Ifgd#5J$Eƀ^F0Ifgd#5J$Eƀ^F/Ifgd#5c d e j   8/ $Ifgd(J$Eƀ^F..IfgdLrkdI$$Ifl4F]#%;f&6    4 laf4p $IfgdL     zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p     p FA77 gd(oڸ&gd9TFEƀ^F.gd0rkd$$Ifl4F]#%;f&6    4 laf4pp k\FEƀ^F3gd#5 & FgdhFFEƀ^F2gd#5gdwgd9Tgd(K9nnFEƀ^F5gd#5gdwFEƀ^F4gd#51AERWsnaXL $$Ifa$gdn $Ifgd9T $If^gdngdYFEƀ^F7gd#5FEƀ^F6gd#5ADRWGHMNhi@!A!""@#C#$$%%%%&&((F)H)))2*3*++--'010t0u0222222d4q45556ߤh* hFT h#5h* h#5h% h#5h|vh#5h`0Jhxhx6]hxhxCJaJ h#5hxhxh#5hxCJaJh|vh#5h`CJaJ hh` h#5h`h`7WX]?6- $Ifgd6z $Ifgd6zL$$Eƀ^F..Ifgd6ztkd&$$Ifl44F]#%;f&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4pEFzq $IfgdL $Ifgd( $Ifgd%rkdm$$Ifl4F]#%;f&6    4 laf4pFGHzq $IfgdL $Ifgd( $Ifgd%rkd $$Ifl4F]#%;f&6    4 laf4pHA8 $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4pHniJ$Eƀ^F:Ifgd#5J$Eƀ^F9Ifgd#5J$Eƀ^F8Ifgd#5eghi8/ $Ifgd%rkdJ$$Ifl4F]#%;f&6    4 laf4p $IfgdLJ$Eƀ^F;Ifgd#5iz/J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd(4`J$Eƀ^F=Ifgd#5J$Eƀ^F<Ifgd#5 $Ifgd(4i` $IfgdLJ$Eƀ^F?Ifgd#5J$Eƀ^F>Ifgd#5zq $IfgdL $Ifgd( $Ifgd%rkd $$Ifl4F]#%;f&6    4 laf4pf A8 $Ifgd(J$Eƀ^F..IfgdLrkd' $$Ifl4F]#%;f&6    4 laf4pf    iJ$Eƀ^FBIfgd#5J$Eƀ^FAIfgd#5J$Eƀ^F@Ifgd#5    iJ$Eƀ^FEIfgd#5J$Eƀ^FDIfgd#5J$Eƀ^FCIfgd#5 !=!?!@!/rkd $$Ifl4F]#%;f&6    4 laf4p $IfgdL $IfgdXefJ$Eƀ^FFIfgd#5@!A!""""A#B#qrkde $$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd( $Ifgd%B#C#H#$$A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd $$Ifl4F]#%;f&6    4 laf4p$$$x$y$zq $IfgdL $Ifgd( $Ifgd%rkd $$Ifl4F]#%;f&6    4 laf4py$z$$$A8 $Ifgd(J$Eƀ^F..IfgdLrkdB $$Ifl4F]#%;f&6    4 laf4p$ %X%%iJ$Eƀ^FIIfgd#5J$Eƀ^FHIfgd#5J$Eƀ^FGIfgd#5%%%%%%zq $Ifgd( $Ifgd%rkd $$Ifl4F]#%;f&6    4 laf4p $IfgdL%%%R&S&zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4pS&T&Y&&&A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p&&&''zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p'''s(u(@7. $Ifgd6z $Ifgd6zL$$Eƀ^F ..Ifgd6zrkd]$$Ifl4F]#%;f&6    4 laf4pu(v({(((@7. $Ifgd6z $Ifgd6zL$$Eƀ^F ..Ifgd6zrkd$$Ifl4F]#%;f&6    4 laf4p(((F)G)~ul $Ifgd6z $Ifgd6z$Ifgdxorkd$$Ifl4F]#%;f&6    4 laf4pG)H)M)))A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd:$$Ifl4F]#%;f&6    4 laf4p)))0*1*zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p1*2*3***zq $IfgdL $Ifgd( $Ifgd%rkdx$$Ifl4F]#%;f&6    4 laf4p***++A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p+++,,zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p,,,V-X-@7. $Ifgdj $IfgdjL$$Eƀ^F ..IfgdjrkdU$$Ifl4F]#%;f&6    4 laf4pX-Y-^---A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p---..zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p...3/@7 $IfgdjL$$Eƀ^F..Ifgdjrkd2$$Ifl4F]#%;f&6    4 laf4p3/?/E/g/}//`W $IfgdjJ$Eƀ^FKIfgdj $IfgdjJ$Eƀ^FJIfgdj///'0A8 $IfgdwJ$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p'03090[0q0s0`W $IfgdLJ$Eƀ^FMIfgd#5 $IfgdXefJ$Eƀ^FLIfgd#5s0t0u011zq $IfgdL $Ifgd( $Ifgd%rkdp$$Ifl4F]#%;f&6    4 laf4p11122A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p2224353zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p5363;3a4c4@7. $Ifgdj $IfgdjL$$Eƀ^F..IfgdjrkdM$$Ifl4F]#%;f&6    4 laf4pc4d4q4 5FAgd(FEƀ^F.gd0rkd$$Ifl4F]#%;f&6    4 laf4p 5565G5s-FEƀ^FPgd#5FEƀ^FOgd#5FEƀ^FNgd#5G555566 $$Ifa$gdn $Ifgd9T $If^gdngdYFEƀ^FQgd#566 6V6W6667777\8]8r88888888@@@@@DAEARBSBCCDEEEEEJJJ.K/KMM*N+NNN=P>PRR5T6TTUUUNVZVٸ괰hh#5h* CJaJh* hQh#rh* 0J5>*jNh\=Jhj 5U h\=J5jh\=J5U h#5h% h#5h*  *h#5h* hh* ?6 66T6V6?6- $Ifgdj $IfgdjL$$Eƀ^F..Ifgdjtkd$$Ifl44F\#%;e&6    4 laf4pV6W6\666@7. $Ifgdj $IfgdjL$$Eƀ^F..Ifgdjrkd3$$Ifl4F\#%;e&6    4 laf4p66677@7. $Ifgdj $IfgdjL$$Eƀ^F..Ifgdjrkd$$Ifl4F\#%;e&6    4 laf4p77777@7. $Ifgdj $IfgdjL$$Eƀ^F..Ifgdjrkdq$$Ifl4F\#%;e&6    4 laf4p777Z8\8@7. $Ifgdj $IfgdjL$$Eƀ^F..Ifgdjrkd$$Ifl4F\#%;e&6    4 laf4p\8]8r8969FAAgd(FEƀ^F.gd0rkd$$Ifl4F\#%;e&6    4 laf4p699Q::;k;snngd(FEƀ^FSgd#5FEƀ^FRgd#5k;x;;;;s-(gdXefFEƀ^FVgd#5FEƀ^FUgd#5FEƀ^FTgd#5;< >>>?iFEƀ^FXgd#5FEƀ^FWgd#5gdXefgd(?}??@@@@snaXL $$Ifa$gdn $Ifgd9T $If^gdngdYFEƀ^FZgd#5FEƀ^FYgd#5@@@AACA@7. $IfgdL $Ifgd(J$Eƀ^F..IfgdLtkd$$Ifl44F]#%;f&6    4 laf4pCADAEAAAzq $IfgdL $Ifgd( $Ifgd%rkd{ $$Ifl4F]#%;f&6    4 laf4pAABOBQBA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd!$$Ifl4F]#%;f&6    4 laf4pQBRBSBBBzq $IfgdL $Ifgd( $Ifgd%rkd!$$Ifl4F]#%;f&6    4 laf4pBBBB@7 $IfgdiL$$Eƀ^F..IfgdirkdX"$$Ifl4F]#%;f&6    4 laf4pBCZCqCiJ$Eƀ^F]IfgdiJ$Eƀ^F\IfgdiJ$Eƀ^F[IfgdiqCsCtCyCC8/ $Ifgd(J$Eƀ^F..IfgdLrkd"$$Ifl4F]#%;f&6    4 laf4p $IfgdiCCCCLDMDzq $Ifgd( $Ifgd%rkd#$$Ifl4F]#%;f&6    4 laf4p $IfgdLMDNDSDDD@7. $Ifgdj $IfgdjL$$Eƀ^F..Ifgdjrkd5$$$Ifl4F]#%;f&6    4 laf4pDDD8EA8 $Ifgd(J$Eƀ^F..IfgdLrkd$$$Ifl4F]#%;f&6    4 laf4p8EHCHHH@7. $Ifgdj $IfgdjL$$Eƀ^F ..Ifgdjrkd-)$$Ifl4F]#%;f&6    4 laf4pHHH(I*IA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd)$$Ifl4F]#%;f&6    4 laf4p*I+I,IIIzq $IfgdL $Ifgd( $Ifgd%rkdk*$$Ifl4F]#%;f&6    4 laf4pIII:JJhJiJzq $IfgdL $Ifgd( $Ifgd%rkd+$$Ifl4F]#%;f&6    4 laf4piJjJoJJJA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdH,$$Ifl4F]#%;f&6    4 laf4pJJJ,K-Kzq $IfgdL $Ifgd( $Ifgd%rkd,$$Ifl4F]#%;f&6    4 laf4p-K.K/KKKzq $IfgdL $Ifgd( $Ifgd%rkd-$$Ifl4F]#%;f&6    4 laf4pKKKLL@7. $Ifgdj $IfgdjL$$Eƀ^F ..Ifgdjrkd%.$$Ifl4F]#%;f&6    4 laf4pLLLQMSM@7. $Ifgdj $IfgdjL$$Eƀ^F..Ifgdjrkd.$$Ifl4F]#%;f&6    4 laf4pSMTMYMMMA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdc/$$Ifl4F]#%;f&6    4 laf4pMMM-N.Nzq $IfgdL $Ifgd( $Ifgd%rkd0$$Ifl4F]#%;f&6    4 laf4p.N/N4NNNA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd0$$Ifl4F]#%;f&6    4 laf4pNNNnOoOzq $IfgdL $Ifgd( $Ifgd%rkd@1$$Ifl4F]#%;f&6    4 laf4poOpOuO:PPPPzq $IfgdL $Ifgd( $Ifgd%rkd~2$$Ifl4F]#%;f&6    4 laf4pPPP2Q@7 $IfgdjL$$Eƀ^F..Ifgdjrkd3$$Ifl4F]#%;f&6    4 laf4p2Q>QVQiQiJ$Eƀ^FbIfgdjJ$Eƀ^FaIfgdjJ$Eƀ^F`IfgdjiQ}QQQiJ$Eƀ^FeIfgdjJ$Eƀ^FdIfgdjJ$Eƀ^FcIfgdjQQ+R-Ri` $IfgdjJ$Eƀ^FgIfgdjJ$Eƀ^FfIfgdj-R.R3RRRA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd3$$Ifl4F]#%;f&6    4 laf4pRRRSSzq $IfgdL $Ifgd( $Ifgd%rkd[4$$Ifl4F]#%;f&6    4 laf4pSSS2T4TA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd4$$Ifl4F]#%;f&6    4 laf4p4T5T6TTTzq $IfgdL $Ifgd( $Ifgd%rkd5$$Ifl4F]#%;f&6    4 laf4pTTTQUSUA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd86$$Ifl4F]#%;f&6    4 laf4pSUTUUUUUzq $IfgdL $Ifgd( $Ifgd%rkd6$$Ifl4F]#%;f&6    4 laf4pUUUVV@7. $Ifgdj $IfgdjL$$Eƀ^F..Ifgdjrkdv7$$Ifl4F]#%;f&6    4 laf4pVV VKVMV@7. $Ifgdj $IfgdjL$$Eƀ^F..Ifgdjrkd8$$Ifl4F]#%;f&6    4 laf4pMVNVZVhWXFAAgd}FEƀ^F.gd0rkd8$$Ifl4F]#%;f&6    4 laf4pZVgWhWYYZZr[s[[\\ \\\\D\F\H\J\L\b\\\\\]]S___`_a_l_m_``eaxaabbbggggggiƾ~ hh* h#5h% h#5hf[)ho{Nh* 6]h#5h* 6]jmbh* U h&E`h* j9h* UjS9h* Ujh* UmHnHtH uhLw hLwjh* Uh* hM<6h#5h* 5\ h#5h* 0X/XiXX8Ysn(FEƀ^Fjgd#5gd}FEƀ^Figd#5FEƀ^Fhgd#58YY*ZZ\N\d\\\]^snia\na\ngdc$a$gd* gd0gd}FEƀ^Flgd#5FEƀ^Fkgd#5 ^`_b_m__`{abaFEƀ^Fngdo{NFEƀ^Fmgdo{Ngdc$a$gd* gd}bb8ccdegsnnngd}FEƀ^Fpgdo{NFEƀ^Fogdo{Nggggg $$Ifa$gd:9 $Ifgd9T $If^gd:9FEƀ^F.gd* gggMh@7 $IfgdL$$Eƀ^F..Ifgdrkd$$Ifl44Fnu#&    4 laf4pMhUh\hghiJ$Eƀ^FsIfgdJ$Eƀ^FrIfgdJ$Eƀ^FqIfgdghphxhhiJ$Eƀ^FvIfgdJ$Eƀ^FuIfgdJ$Eƀ^FtIfgdhhhhii90 $IfgdL$$Eƀ^F..IfgdqkdŽ$$Ifl4Fnu#&    4 laf4p $Ifgdiiiixlyl6m7m:mBmEmZmm7nrTrVrZr\rsssssssuuuuuuuuuuuvvvvvvwwjh *5U hh* h% h#5h%hLw hLwjh* U h&E`h* jvh* UhXh#5h* h^h#5h* CJaJh* h#5h* h}=ii iiiB90 $Ifgd $IfgdL$$Eƀ^F..Ifgdqkd^$$Ifl4Fnu#&    4 laf4piii@jBjB90 $Ifgd $IfgdL$$Eƀ^F..Ifgdqkd$$Ifl4Fnu#&    4 laf4pBjCjHj\kB9 $IfgdL$$Eƀ^F..Ifgdqkd$$Ifl4Fnu#&    4 laf4p\kkkkiJ$Eƀ^FyIfgdJ$Eƀ^FxIfgdJ$Eƀ^FwIfgdkkkki` $IfgdJ$Eƀ^F{IfgdJ$Eƀ^FzIfgdkkkxlzl>55 $IfgdP$ p$Eƀ^F..Ifgdqkd2$$Ifl4Fnu#&    4 laf4pzl{lllC: $Ifgd}J$Eƀ^F..IfgdLqkdΑ$$Ifl4Fnu#&    4 laf4plmm(miJ$Eƀ^F~Ifgd#5J$Eƀ^F}Ifgd#5J$Eƀ^F|Ifgd#5(m3m5m6m7m:1 $Ifgd%qkdj$$Ifl4Fnu#&    4 laf4p $IfgdLJ$Eƀ^FIfgd#57mnn)n`J$Eƀ^FIfgd^J$Eƀ^FIfgd^ $Ifgd})n0n>n?ni` $IfgdLJ$Eƀ^FIfgd^J$Eƀ^FIfgd^?n@nAnnn|1J$Eƀ^FIfgd^ $Ifgd} $Ifgd%qkd$$Ifl4Fnu#&    4 laf4pnnnn:qkd$$Ifl4Fnu#&    4 laf4p $IfgdLJ$Eƀ^FIfgd^nnopp`W $IfgdaJ$Eƀ^FIfgd#5 $Ifgd}J$Eƀ^F..IfgdLpqqqq:1 $Ifgd%qkd>$$Ifl4Fnu#&    4 laf4p $IfgdLJ$Eƀ^FIfgd#5q6r8r:r*jh *5Ujh *hj 5U h *53wwwwiJ$Eƀ^FIfgdJ$Eƀ^FIfgdJ$Eƀ^FIfgdwwwwyx8/ $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#5&;n&6    4 laf4p $Ifgdyx{x|x}x^y_yzq $Ifgd( $Ifgd%rkd$$Ifl4F=#5&;n&6    4 laf4p $IfgdL_y`yeyyy@7. $Ifgd $IfgdL$$Eƀ^F..IfgdrkdR$$Ifl4F=#5&;n&6    4 laf4pyyy z"zA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#5&;n&6    4 laf4p"z#z$zzzzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F=#5&;n&6    4 laf4pzzz{|zq $IfgdL $Ifgd( $Ifgd%rkd/$$Ifl4F=#5&;n&6    4 laf4p|||||A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#5&;n&6    4 laf4p||| }!}zq $IfgdL $Ifgd( $Ifgd%rkdm$$Ifl4F=#5&;n&6    4 laf4p!}"}#}}}zq $IfgdL $Ifgd( $Ifgd%rkd $$Ifl4F=#5&;n&6    4 laf4p}}}M~O~A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#5&;n&6    4 laf4pO~P~Q~zq $IfgdL $Ifgd( $Ifgd%rkdJ$$Ifl4F=#5&;n&6    4 laf4pCxԁބFAAAAgd) FEƀ^F.gd0rkd$$Ifl4F=#5&;n&6    4 laf4pބ˅ $$Ifa$gd:9 $Ifgd9T $If^gd:9gdYgd) FEƀ^F.gd0އ?6- $Ifgd $IfgdL$$Eƀ^F..Ifgdtkd$$Ifl44F=#%;nF&6    4 laf4p@7 $IfgdL$$Eƀ^F..Ifgdrkd0$$Ifl4F=#%;nF&6    4 laf4p%mi`W $Ifgd $IfgdJ$Eƀ^FIfgdJ$Eƀ^FIfgdA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdn$$Ifl4F=#%;nF&6    4 laf4p@7. $Ifgd $IfgdL$$Eƀ^F..Ifgdrkd $$Ifl4F=#%;nF&6    4 laf4p $A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4p$&(zq $IfgdL $Ifgd( $Ifgd%rkdK$$Ifl4F=#%;nF&6    4 laf4p͌όA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4pόЌьzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4p 8:12-.#C45024>@uv^_Ûěӛ:<>JLXYݡޡbc#$no$E h#5h%h#5h* mHnHuh h$h#5h* CJaJhLw hLwh* jh* U h#5h* I"26A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd($$Ifl4F=#%;nF&6    4 laf4p68:zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4p.0A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdf$$Ifl4F=#%;nF&6    4 laf4p012zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4p*,A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4p,-.zq $IfgdL $Ifgd( $Ifgd%rkdC$$Ifl4F=#%;nF&6    4 laf4pDF@7. $Ifgd $IfgdL$$Eƀ^F ..Ifgdrkd$$Ifl4F=#%;nF&6    4 laf4pFGLA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4p?@zq $IfgdL $Ifgd( $Ifgd%rkd $$Ifl4F=#%;nF&6    4 laf4p@AFהA8 $Ifgd) J$Eƀ^F ..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4pה13i` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5345#$zq $IfgdL $Ifgd( $Ifgd%rkd^$$Ifl4F=#%;nF&6    4 laf4p$%*@7 $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd$$Ifl4F=#%;nF&6    4 laf4piJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk/rkd$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkJ$Eƀ^FIfgd$YkZ\].rkd;$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Yk]b/rkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdL̘ΘИqrkdy$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd( $Ifgd%Иژ.rkd$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Yk]g`J$Eƀ^FIfgd#5 $Ifgd) J$Eƀ^F..IfgdLgqstuv8/ $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdLJ$Eƀ^FIfgd#5v\]^_RTzq $Ifgd%rkdV$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd(TV`}A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4pVWzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4pWXYYZzq $IfgdL $Ifgd( $Ifgd%rkd3$$Ifl4F=#%;nF&6    4 laf4pZ[`ڡܡA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4pܡݡޡ:;zq $IfgdL $Ifgd( $Ifgd%rkdq$$Ifl4F=#%;nF&6    4 laf4p;<AA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4p_aA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkdN$$Ifl4F=#%;nF&6    4 laf4pabcpҤz/J$Eƀ^FIfgd#5 $Ifgd) $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4pҤ>iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5 "8/ $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL"#$Φz/J$Eƀ^FIfgdK $IfgdK $Ifgd%rkd+$$Ifl4F=#%;nF&6    4 laf4pΦϦЦզU7. $Ifgd$YkL$$Eƀ^F..Ifgd$Ykrkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdLUWX]k8/ $Ifgd(J$Eƀ^F..IfgdLrkdi$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Ykkmnozq $Ifgd( $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL   A8// $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4p zq $IfgdL $Ifgd( $Ifgd%rkdF$$Ifl4F=#%;nF&6    4 laf4pŪǪ@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Ykrkd$$Ifl4F=#%;nF&6    4 laf4pǪȪͪ&(@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Ykrkd$$Ifl4F=#%;nF&6    4 laf4p().@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Ykrkd#$$Ifl4F=#%;nF&6    4 laf4p@7 $Ifgd$YkL$$Eƀ^F..Ifgd$Ykrkd$$Ifl4F=#%;nF&6    4 laf4pĬʬiJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkʬЬ׬iJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkiJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk7. $Ifgd$YkL$$Eƀ^F..Ifgd$Ykrkda$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk1iJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk1oqr8rkd$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$YkJ$Eƀ^FIfgd$YkrwͮϮЮ.rkd$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$YkЮծ.rkd>$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Yk~/rkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F!..IfgdL"#$qrkd|$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd( $Ifgd%$E $$Ifa$gd:9 $Ifgd9T $If^gd:9gdX7~FEƀ^F.gd2EвѲ  ܵݵ øƸ  DEHV[EFklm~{|qr  񓎊hLw hLwjhtUh#rht0J5>*jh *hj 5U h *5jh *5U h#5h% hahth#5htCJaJ h#5h h hhthth h#5ht6Ͳϲ@7. $IfgdL $Ifgd(J$Eƀ^F..IfgdLtkd$$Ifl44F=#%;nF&6    4 laf4pϲвѲzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4pʹz/J$Eƀ^FIfgd#5 $Ifgd) $Ifgd%rkdb$$Ifl4F=#%;nF&6    4 laf4pʹڵ۵ܵݵ8/ $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdLJ$Eƀ^FIfgd#5ݵz/J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd( zqh $Ifgd( $Ifgd%rkd?$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd( A8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4p   zq $IfgdL $Ifgd( $Ifgd%rkd}$$Ifl4F=#%;nF&6    4 laf4pe EFAA<gdX7~gd) FEƀ^F.gd2rkd$$Ifl4F=#%;nF&6    4 laf4pEIV[\itkd$$Ifl44F=#%;nF&6    4 laf4p $$Ifa$gd:9 $Ifgd9T $If^gd:9\a½ĽŽ.rkdc$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$YkŽʽ:<=.rkd$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Yk=B.rkd$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Yknpq.rkd@$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Ykqv/rkdh$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdL)*+qrkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd( $Ifgd%+0.rkd$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Yk   .rkdE$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Yk xz{/rkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F..IfgdL{|qrkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd( $Ifgd%GIJ.rkd"$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$YkJO.rkd$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Yk|/rkd`$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdL012qrkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd( $Ifgd%27.rkd$$Ifl4F=#%;nF&6    4 laf4p $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Yk/rkd=$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdL   xyqrkd$$Ifl4F=#%;nF&6    4 laf4p $IfgdL $Ifgd( $Ifgd%yz}  @7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Ykrkd{$$Ifl4F=#%;nF&6    4 laf4p z|}   ABQ  yzabetxrr{)@PQ&hc0 hht hc0hth h#5h%hLw hLwjhtUhth#5htCJaJhtCJaJ h#5htG  A8/ $IfgdK $IfgdwRJ$Eƀ^F..IfgdwRrkd$$Ifl4F=#%;nF&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4p@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$YkrkdX$$Ifl4F=#%;nF&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4p68zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F=#%;nF&6    4 laf4p8:D $@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F..Ifgd$Ykrkd5$$Ifl4F=#%;nF&6    4 laf4p$&0A8 $Ifgd) J$Eƀ^F..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4p;vxi` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5xyzzq $IfgdL $Ifgd( $Ifgd%rkds$$Ifl4F=#%;nF&6    4 laf4pbfFA4 $If^gd:9gd]jFEƀ^F.gd2rkd$$Ifl4F=#%;nF&6    4 laf4pftyzv+J$Eƀ^F..IfgdLtkd$$Ifl44F<#%;iE&6    4 laf4p $$Ifa$gd:9 $Ifgd9Tpqzqh $Ifgd( $Ifgd%rkdS$$Ifl4F<#%;iE&6    4 laf4p $IfgdL $Ifgd(qrFAAgd) FEƀ^F .gd2rkd$$Ifl4F<#%;iE&6    4 laf4p9[s-(gd) FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5)snngd) FEƀ^Fgdj^|FEƀ^Fgd#5)@ $$Ifa$gd:9 $Ifgd9T $If^gd:9gd]jgd) FEƀ^F .gd2MO@7. $IfgdL $Ifgd) J$Eƀ^F ..IfgdLtkd $$Ifl44F=#%;nF&6    4 laf4pOPQzq $IfgdL $Ifgd( $Ifgd%rkd9 $$Ifl4F=#%;nF&6    4 laf4p@7 $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd $$Ifl4F=#%;nF&6    4 laf4p 24i` $Ifgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk45: A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdw $$Ifl4F=#%;nF&6    4 laf4p{|zq $IfgdL $Ifgd( $Ifgd%rkd $$Ifl4F=#%;nF&6    4 laf4p|}A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd $$Ifl4F=#%;nF&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdT $$Ifl4F=#%;nF&6    4 laf4p+,zq $IfgdL $Ifgd( $Ifgd%rkd $$Ifl4F=#%;nF&6    4 laf4p,-2A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F=#%;nF&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd1$$Ifl4F=#%;nF&6    4 laf4p&FAAgd) FEƀ^F .gd2rkd$$Ifl4F=#%;nF&6    4 laf4p$ /034:<>JL.0NPR^`򸱧ßßßhQ4jhQ4Uh#5hQ4hE h#5hQ4hQ4hQ4CJaJhLw hLwjhtUh#5htCJaJ hhththhc0 h#5ht h#5hc0=s-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#54Jsni\SG $$Ifa$gd:9 $Ifgd9T $If^gd:9gd]jgd) FEƀ^Fgd#5FEƀ^Fgd#5rt?6- $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Yktkdo$$Ifl44F =#%x1F&6    4 laf4ptuzA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F =#%x1F&6    4 laf4pHIzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F =#%x1F&6    4 laf4pIJOA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdU$$Ifl4F =#%x1F&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F =#%x1F&6    4 laf4p @7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd$$Ifl4F =#%x1F&6    4 laf4p(A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd2$$Ifl4F =#%x1F&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F =#%x1F&6    4 laf4pFH@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkdp$$Ifl4F =#%x1F&6    4 laf4pHINA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F =#%x1F&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F =#%x1F&6    4 laf4p46@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$YkrkdM$$Ifl4F =#%x1F&6    4 laf4p67<@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F  ..Ifgd$Ykrkd$$Ifl4F =#%x1F&6    4 laf4p-.zq $Ifgd$Yk $IfgdQ4 $IfgdQ4rkd$$Ifl4F =#%x1F&6    4 laf4p./4@7 $Ifgd$YkL$$Eƀ^F  ..Ifgd$Ykrkd*$$Ifl4F =#%x1F&6    4 laf4p'iJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk'`iJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk7. $Ifgd$YkL$$Eƀ^F  ..Ifgd$Ykrkd$$Ifl4F =#%x1F&6    4 laf4p $Ifgd$Yk ,[iJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk[]^c7. $Ifgd$YkL$$Eƀ^F  ..Ifgd$Ykrkdh$$Ifl4F =#%x1F&6    4 laf4p $Ifgd$Yk0RiJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkRTUZ7. $Ifgd$YkL$$Eƀ^F  ..Ifgd$Ykrkd$$Ifl4F =#%x1F&6    4 laf4p $Ifgd$Yk2jiJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Ykjnpz7. $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd$$Ifl4F =#%x1F&6    4 laf4p $Ifgd$YkA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdE$$Ifl4F =#%x1F&6    4 laf4pJKzq $Ifgd$Yk $Ifgd$Yk $Ifgd$Ykrkd$$Ifl4F =#%x1F&6    4 laf4pAB                prŵʩԥԚԒ~ԒԒԒh#5htCJaJhLw hLwjhtU hhthth9h#rht0J5>*j*hZhj 5U hZ5jhZ5U h#5ht h#5h%hQ4hQ4CJaJ h#5hQ4h#5hQ4CJaJ1KLQ@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd$$Ifl4F =#%x1F&6    4 laf4p y{@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd"$$Ifl4F =#%x1F&6    4 laf4p{|@7 $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd$$Ifl4F =#%x1F&6    4 laf4p$*6iJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk6>FLiJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkLY[\8rkd`$$Ifl4F =#%x1F&6    4 laf4p $Ifgd$YkJ$Eƀ^FIfgd$Yk\a_J$Eƀ^FIfgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Yki` $Ifgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk @7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd$$Ifl4F =#%x1F&6    4 laf4psu@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd $$Ifl4F =#%x1F&6    4 laf4puv{ @7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd=!$$Ifl4F =#%x1F&6    4 laf4p  ik@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd!$$Ifl4F =#%x1F&6    4 laf4pklqA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd{"$$Ifl4F =#%x1F&6    4 laf4p+,zq $Ifgd$Yk $Ifgd$Yk $Ifgd$Ykrkd#$$Ifl4F =#%x1F&6    4 laf4p,-2@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd#$$Ifl4F =#%x1F&6    4 laf4pik@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$YkrkdX$$$Ifl4F =#%x1F&6    4 laf4pklq@7 $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd$$$Ifl4F =#%x1F&6    4 laf4p_ iJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk i` $Ifgd$YkJ$Eƀ^FIfgd$YkJ$Eƀ^FIfgd$Yk@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd%$$Ifl4F =#%x1F&6    4 laf4pAC@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd5&$$Ifl4F =#%x1F&6    4 laf4pCDI@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkd&$$Ifl4F =#%x1F&6    4 laf4p@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F ..Ifgd$Ykrkds'$$Ifl4F =#%x1F&6    4 laf4pXZ@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F  ..Ifgd$Ykrkd($$Ifl4F =#%x1F&6    4 laf4pZ[`@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F !..Ifgd$Ykrkd($$Ifl4F =#%x1F&6    4 laf4p@7. $Ifgd$Yk $Ifgd$YkL$$Eƀ^F "..Ifgd$YkrkdP)$$Ifl4F =#%x1F&6    4 laf4p27FAAAAgd(FEƀ^F .gd2rkd)$$Ifl4F =#%x1F&6    4 laf4p7Dy  R    sninnd_R $If^gd:9gd]jgdj^|gd(gd(FEƀ^Fgd#5FEƀ^Fgd#5     v+J$Eƀ^F ..IfgdLtkd+$$Ifl44F]#%;f&6    4 laf4p $$Ifa$gd:9 $Ifgd9T zqh $Ifgd( $Ifgd%rkd+$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd(A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdJ,$$Ifl4F]#%;f&6    4 laf4p`vx024>@HJhjlvx|}       \!]!l!"" """"8":"<"hth#5htCJaJ h#5htjhtUhLw hLwUrt~ul $IfgdL $Ifgd($Ifgd%o,frkd,$$Ifl4F]#%;f&6    4 laf4ptv0A8 $Ifgd) J$Eƀ^F ..IfgdLrkd-$$Ifl4F]#%;f&6    4 laf4p0y{i` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5{|}zq $IfgdL $Ifgd( $Ifgd%rkd'.$$Ifl4F]#%;f&6    4 laf4pl@7 $IfgdML$$Eƀ^F ..IfgdMrkd.$$Ifl4F]#%;f&6    4 laf4plU W i` $IfgdMJ$Eƀ^FIfgdMJ$Eƀ^FIfgdMW X ]   A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkde/$$Ifl4F]#%;f&6    4 laf4p   L"N"zq $IfgdL $Ifgd( $Ifgd%rkd0$$Ifl4F]#%;f&6    4 laf4p<"F"H"F#H#&&''))#*+***++++,,///0000'3(3b3c3r3444477\9^9l9o9/<8<p<|<<<<<<<<<<<<>>> ?DDJJJJDZ hht h]jh%h[ h#5h[hZ h#5h% hLwhth hZhth#5htCJaJ h#5htjhtUhLwCN"P"Z"@#D#A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd0$$Ifl4F]#%;f&6    4 laf4pD#F#H###zq $IfgdL $Ifgd( $Ifgd%rkdB1$$Ifl4F]#%;f&6    4 laf4p###;$A8 $Ifgd) J$Eƀ^F ..IfgdLrkd1$$Ifl4F]#%;f&6    4 laf4p;$`$$$iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5$%V&&iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5&&&&8'9'zq $Ifgd( $Ifgd%rkd2$$Ifl4F]#%;f&6    4 laf4p $IfgdL9':'?'''A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd3$$Ifl4F]#%;f&6    4 laf4p'''((zq $IfgdL $Ifgd( $Ifgd%rkd3$$Ifl4F]#%;f&6    4 laf4p((())@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkd]4$$Ifl4F]#%;f&6    4 laf4p))#)))A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd4$$Ifl4F]#%;f&6    4 laf4p))).*/*zq $IfgdL $Ifgd( $Ifgd%rkd5$$Ifl4F]#%;f&6    4 laf4p/*0*5***A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd:6$$Ifl4F]#%;f&6    4 laf4p***++zq $IfgdL $Ifgd( $Ifgd%rkd6$$Ifl4F]#%;f&6    4 laf4p+++--zq $IfgdL $Ifgd( $Ifgd%rkdx7$$Ifl4F]#%;f&6    4 laf4p---7.9.@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkd8$$Ifl4F]#%;f&6    4 laf4p9.:.?...@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkd8$$Ifl4F]#%;f&6    4 laf4p.../@7 $IfgdML$$Eƀ^F ..IfgdMrkdU9$$Ifl4F]#%;f&6    4 laf4p/0b01iJ$Eƀ^FIfgdMJ$Eƀ^FIfgdMJ$Eƀ^FIfgdM1111117. $IfgdML$$Eƀ^F ..IfgdMrkd9$$Ifl4F]#%;f&6    4 laf4p $IfgdM111i2k2@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd:$$Ifl4F]#%;f&6    4 laf4pk2l2q2$3&3A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd2;$$Ifl4F]#%;f&6    4 laf4p&3'3(30525zq $IfgdL $Ifgd( $Ifgd%rkd;$$Ifl4F]#%;f&6    4 laf4p2545>5o6q6@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkdp<$$Ifl4F]#%;f&6    4 laf4pq6r6w67797@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd=$$Ifl4F]#%;f&6    4 laf4p97:7?777@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd=$$Ifl4F]#%;f&6    4 laf4p77789:FAA<gd) gdKFEƀ^F .gd2rkdM>$$Ifl4F]#%;f&6    4 laf4p:2:b::s-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5:::;s-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5;*;E;o;s-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5o;;;;s-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5;<==> ?X@PAnFEƀ^F .gd2gd) FEƀ^Fgd#5PAABNDE;Fsnnngd) FEƀ^Fgd#5FEƀ^Fgd#5;FFG[HIJJJJsnnnaXL $$Ifa$gd:9 $Ifgd9T $If^gd:9gd) FEƀ^Fgd#5FEƀ^Fgd#5JJJJJ?6- $IfgdM $IfgdML$$Eƀ^F ..IfgdMtkd>$$Ifl44F\#%;e&6    4 laf4pJJJrKtK@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd?$$Ifl4F\#%;e&6    4 laf4ptKuKzK;L=L@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd3@$$Ifl4F\#%;e&6    4 laf4p=L>LCLLL@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd@$$Ifl4F\#%;e&6    4 laf4pLLL[M]M@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkdqA$$Ifl4F\#%;e&6    4 laf4p]M^McM3N5NA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdB$$Ifl4F\#%;e&6    4 laf4p5N6N7NNNzq $IfgdM $IfgdM $IfgdMrkdB$$Ifl4F\#%;e&6    4 laf4pJ6N7NQQRRRRRVVVVuZvZZZu[v[+\,\^^b_c_````a abb~ccddZeeeeOfTfgyyh#5htmHnHuh#5hM>*h#5hMCJaJ hhM h#5hMhMh% h#5h%h#5ht6]hB6Ah#rht0J5>*j+Eh"hj 5U h"5jh"5Uh#5htCJaJ h#5ht,NNN)P@7 $IfgdML$$Eƀ^F ..IfgdMrkdNC$$Ifl4F\#%;e&6    4 laf4p)POPPPi` $IfgdMJ$Eƀ^FIfgdMJ$Eƀ^FIfgdMPPPcQeQ@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkdC$$Ifl4F\#%;e&6    4 laf4peQfQkQARCR@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkdD$$Ifl4F\#%;e&6    4 laf4pCRDRIRRR@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkdE$$Ifl4F\#%;e&6    4 laf4pRRRgSiS@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkdEF$$Ifl4F\#%;e&6    4 laf4piSjSoS TT@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkdF$$Ifl4F\#%;e&6    4 laf4pTTTTT@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkdG$$Ifl4F\#%;e&6    4 laf4pTTTaUcU@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd"H$$Ifl4F\#%;e&6    4 laf4pcUdUiUVVA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdH$$Ifl4F\#%;e&6    4 laf4pVVV`VaVzq $IfgdL $Ifgd( $Ifgd%rkd`I$$Ifl4F\#%;e&6    4 laf4paVbVgVVVA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdI$$Ifl4F\#%;e&6    4 laf4pVVV[W\Wzq $IfgdL $Ifgd( $Ifgd%rkdJ$$Ifl4F\#%;e&6    4 laf4p\W]WbWW@7 $IfgdML$$Eƀ^F ..IfgdMrkd=K$$Ifl4F\#%;e&6    4 laf4pWWWbXiJ$Eƀ^FIfgdMJ$Eƀ^FIfgdMJ$Eƀ^FIfgdMbX|XXXiJ$Eƀ^FIfgdMJ$Eƀ^FIfgdMJ$Eƀ^FIfgdMXXXXYY7. $IfgdML$$Eƀ^F ..IfgdMrkdK$$Ifl4F\#%;e&6    4 laf4p $IfgdMYYYYY@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd{L$$Ifl4F\#%;e&6    4 laf4pYYZrZtZA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdM$$Ifl4F\#%;e&6    4 laf4ptZuZvZZZzq $IfgdL $Ifgd( $Ifgd%rkdM$$Ifl4F\#%;e&6    4 laf4pZZZr[t[A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdXN$$Ifl4F\#%;e&6    4 laf4pt[u[v[[[zq $IfgdL $Ifgd( $Ifgd%rkdN$$Ifl4F\#%;e&6    4 laf4p[[[(\*\A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdO$$Ifl4F\#%;e&6    4 laf4p*\+\,\\\z/J$Eƀ^FIfgd#5 $Ifgd) $Ifgd%rkd5P$$Ifl4F\#%;e&6    4 laf4p\\]"]iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5"]?]X]Y]i` $IfgdLJ$Eƀ^F Ifgd#5J$Eƀ^F Ifgd#5Y]Z]_]]@7 $IfgdML$$Eƀ^F ..IfgdMrkdP$$Ifl4F\#%;e&6    4 laf4p]G^^^i` $IfgdMJ$Eƀ^F IfgdMJ$Eƀ^F IfgdM^^^__a_A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdsQ$$Ifl4F\#%;e&6    4 laf4pa_b_c_``zq $IfgdL $Ifgd( $Ifgd%rkdR$$Ifl4F\#%;e&6    4 laf4p````aF90 $Ifgd9T $If^gdL8FEƀ^F .gd2rkdR$$Ifl4F\#%;e&6    4 laf4pa a aaa4+ $IfgdML$$Eƀ^F ..IfgdMrkdPS$$Ifl4F\#%;e&6    4 laf4p $$Ifa$gdL8aaaabb8/ $IfgdMJ$Eƀ^F ..IfgdMrkdS$$Ifl4F\#%;e&6    4 laf4p $IfgdMbbb.c/czq $IfgdM $IfgdM $IfgdMrkdT$$Ifl4F\#%;e&6    4 laf4p/c0c5ccc@7. $Ifgdi $IfgdiL$$Eƀ^F ..Ifgdirkd3U$$Ifl4F\#%;e&6    4 laf4pcccddA8/ $IfgdM $IfgdMJ$Eƀ^F ..IfgdMrkdU$$Ifl4F\#%;e&6    4 laf4pdddXeYezq $IfgdM $IfgdM $IfgdMrkdqV$$Ifl4F\#%;e&6    4 laf4pYeZeeg2hh/iFAAAAgd) FEƀ^F .gd2rkdW$$Ifl4F\#%;e&6    4 laf4pgg-g:gUgZgggghhhohphzh{hh.i/iAiBialblllmmmmmnnnnooooBpCpppppcrdrssʾʫ}ssh#5ht6]h#5ht6h#5htCJaJh#5ht5\ hhth#5hthZg%hpXhZB*CJOJQJaJphhpXhZ5CJ\ hZhZht h#5hrh#5htmHnHuhr h#5hthfZahfZamHnHu-/i8iAiBici|.M$$Eƀ^F Ifa$gdpXykdW$$Ifl40t" t0644 la< $Ifgdgciii9xkdDX$$Ifl0t" t0644 la<M$$Eƀ^FIfa$gdpXiiicM$$Eƀ^FIfa$gdpXM$$Eƀ^FIfa$gdpXii!j9M$$Eƀ^FIfa$gdpXxkdX$$Ifl0t" t0644 la<!jzj{j9xkdhY$$Ifl0t" t0644 la<M$$Eƀ^FIfa$gdpX{jjjcM$$Eƀ^FIfa$gdpXM$$Eƀ^FIfa$gdpXjjk9M$$Eƀ^FIfa$gdpXxkdY$$Ifl0t" t0644 la<kkk9xkdZ$$Ifl0t" t0644 la<M$$Eƀ^FIfa$gdpXkkalcM$$Eƀ^FIfa$gdpXM$$Eƀ^FIfa$gdpXalblEnnnnnul` $$Ifa$gdL8 $Ifgd9T $If^gdL8gd) xkd[$$Ifl0t" t0644 la<nnnoo;2) $IfgdL $Ifgd(J$Eƀ^F ..IfgdLykd[$$Ifl44F]#%;f&6    4 laf4gfpoooCpDp~ul $IfgdL $Ifgd( $Ifgd%wkdb\$$Ifl4F]#%;f&6    4 laf4gfpDpEpJppp<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkd ]$$Ifl4F]#%;f&6    4 laf4gfppppq q~ul $IfgdL $Ifgd( $Ifgd%wkd]$$Ifl4F]#%;f&6    4 laf4gfp q!q&qq;2 $Ifgd L$$Eƀ^F ..Ifgd wkd]^$$Ifl4F]#%;f&6    4 laf4gfpqq*rdriJ$Eƀ^FIfgd J$Eƀ^FIfgd J$Eƀ^FIfgd drfrgrlr;s~2) $Ifgd L$$Eƀ^F ..Ifgd wkd_$$Ifl4F]#%;f&6    4 laf4gfp $Ifgd ;s_sxssiJ$Eƀ^FIfgd J$Eƀ^FIfgd J$Eƀ^FIfgd ssssxt~3* $Ifgd(J$Eƀ^F ..IfgdLwkd_$$Ifl4F]#%;f&6    4 laf4gfp $Ifgd xtzt{t|ttt~ul $Ifgd( $Ifgd%wkdX`$$Ifl4F]#%;f&6    4 laf4gfp $IfgdLs{t|tvvwwwxxxxyyyyyzz({){8{||||| |||҈Ո?@\^&(UW_`ayh 4 h#5h 4 h#5hU h#5ht>*h#5htmHnHuhLw hLwhtjhtUh#5htCJaJ h#5htEtttt;2 $Ifgd L$$Eƀ^F ..Ifgd wkda$$Ifl4F]#%;f&6    4 laf4gfpt@A)wkdm$$Ifl4F]#%;f&6    4 laf4gfp $Ifgd $Ifgd L$$Eƀ^F ..Ifgd AF)wkd+n$$Ifl4F]#%;f&6    4 laf4gfp $Ifgd $Ifgd L$$Eƀ^F ..Ifgd A`J$Eƀ^F*Ifgd#5 $Ifgd) J$Eƀ^F ..IfgdL3* $Ifgd%wkdn$$Ifl4F]#%;f&6    4 laf4gfp $IfgdLJ$Eƀ^F+Ifgd#5މ߉u*J$Eƀ^F ..IfgdLwkd}o$$Ifl4F]#%;f&6    4 laf4gfp $IfgdL $Ifgd(ߊ`J$Eƀ^F-Ifgd#5J$Eƀ^F,Ifgd#5 $Ifgdj^|<>?@3* $Ifgd%wkd&p$$Ifl4F]#%;f&6    4 laf4gfp $IfgdLJ$Eƀ^F.Ifgd#5@!"#(u*J$Eƀ^F ..IfgdLwkdp$$Ifl4F]#%;f&6    4 laf4gfp $IfgdL $Ifgd((VZ\^ulc $Ifgd( $Ifgd%wkdxq$$Ifl4F]#%;f&6    4 laf4gfp $IfgdL $Ifgd(:<;2) $Ifgd $Ifgd L$$Eƀ^F ..Ifgd wkd!r$$Ifl4F]#%;f&6    4 laf4gfp<=B;2) $Ifgd $Ifgd L$$Eƀ^F ..Ifgd wkdr$$Ifl4F]#%;f&6    4 laf4gfp)+;2) $Ifgd $Ifgd L$$Eƀ^F ..Ifgd wkdss$$Ifl4F]#%;f&6    4 laf4gfp+,1<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkdt$$Ifl4F]#%;f&6    4 laf4gfp~ul $IfgdL $Ifgd( $Ifgd%wkdt$$Ifl4F]#%;f&6    4 laf4gfp<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkdnu$$Ifl4F]#%;f&6    4 laf4gfp~ul $IfgdL $Ifgd( $Ifgd%wkdv$$Ifl4F]#%;f&6    4 laf4gfp<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkdv$$Ifl4F]#%;f&6    4 laf4gfp~ul $IfgdL $Ifgd( $Ifgd%wkdiw$$Ifl4F]#%;f&6    4 laf4gfp2;2 $Ifgd L$$Eƀ^F ..Ifgd wkdx$$Ifl4F]#%;f&6    4 laf4gfp2[~iJ$Eƀ^F1Ifgd J$Eƀ^F0Ifgd J$Eƀ^F/Ifgd Ք)+,*wkdx$$Ifl4F]#%;f&6    4 laf4gfp $Ifgd $IfgdB6AJ$Eƀ^F2Ifgd ,1{}~*wkddy$$Ifl4F]#%;f&6    4 laf4gfp $IfgdL $Ifgd(J$Eƀ^F ..IfgdLyz~ٗݗ>Jęřԙ͞ҞPQPQpqr튆|wg|jZhj hj 5U hj 5jhj 5UhZh+3h#5ht6] hhthth 4hLw hLwhO9jhO9U h#5hO9h"h#5htmHnHu h#5h%h#5ht6h#5htCJaJ h#5hth#5htB*ph'~–lwkd z$$Ifl4F]#%;f&6    4 laf4gfp $IfgdL $Ifgd( $Ifgd%–ǖFHI)wkdz$$Ifl4F]#%;f&6    4 laf4gfp $Ifgd $Ifgd L$$Eƀ^F  ..Ifgd IN)wkd_{$$Ifl4F]#%;f&6    4 laf4gfp $Ifgd $Ifgd L$$Eƀ^F !..Ifgd o'nFEƀ^F3gd#5gd) FEƀ^F .gd2Eus-FEƀ^F6gd#5FEƀ^F5gd#5FEƀ^F4gd#5u͞Ҟsf]Q $$Ifa$gdL8 $Ifgd9T $If^gdL8FEƀ^F8gd#5FEƀ^F7gd#5ҞӞ؞?6- $Ifgd $Ifgd L$$Eƀ^F ..Ifgd tkd|$$Ifl44F\#%;e&6    4 laf4p@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd|$$Ifl4F\#%;e&6    4 laf4p@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkdO}$$Ifl4F\#%;e&6    4 laf4pAC@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd}$$Ifl4F\#%;e&6    4 laf4pCDIA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd~$$Ifl4F\#%;e&6    4 laf4pߡzq $IfgdL $Ifgd( $Ifgd%rkd,$$Ifl4F\#%;e&6    4 laf4pQS@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4pSTYƢȢ@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkdj$$Ifl4F\#%;e&6    4 laf4pȢɢ΢@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd $$Ifl4F\#%;e&6    4 laf4pRT@7. $Ifgd $Ifgd L$$Eƀ^F  ..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4pTUZ@7. $Ifgd $Ifgd L$$Eƀ^F  ..Ifgd rkdG$$Ifl4F\#%;e&6    4 laf4pEG@77 $Ifgd L$$Eƀ^F  ..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4pGHM˥ͥ@7. $Ifgd $Ifgd L$$Eƀ^F  ..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4pͥΥӥ@@7 $Ifgd L$$Eƀ^F  ..Ifgd rkd$$$Ifl4F\#%;e&6    4 laf4p@iJ$Eƀ^F;Ifgd J$Eƀ^F:Ifgd J$Eƀ^F9Ifgd  7. $Ifgd L$$Eƀ^F ..Ifgd rkdÄ$$Ifl4F\#%;e&6    4 laf4p $Ifgd @7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkdb$$Ifl4F\#%;e&6    4 laf4pgi@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4pijoͨϨ@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4pϨШըFH@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd?$$Ifl4F\#%;e&6    4 laf4pHIN@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkdއ$$Ifl4F\#%;e&6    4 laf4p@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd}$$Ifl4F\#%;e&6    4 laf4p/1@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4p127A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4pr|}¬mnlrδϴ_`,-$%()eiDEQY^du~9;<?MR㳯 hhI& h#5hI&hI&hphp6hp h#5hph#5htmHnHuh#5ht6]h=Vh7h#5htCJaJ h#5htjhj 5Uh#rht0J5>*:>?zq $IfgdL $Ifgd( $Ifgd%rkd׊$$Ifl4F\#%;e&6    4 laf4p?@EA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdv$$Ifl4F\#%;e&6    4 laf4p-z/J$Eƀ^F<Ifgdw $Ifgdw $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p-i` $IfgdLJ$Eƀ^F>IfgdwJ$Eƀ^F=Ifgdw¬zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p@7. $Ifgdj $Ifgdj L$$Eƀ^F ..Ifgdj rkdS$$Ifl4F\#%;e&6    4 laf4pvx@7. $Ifgdj $Ifgdj L$$Eƀ^F ..Ifgdj rkd$$Ifl4F\#%;e&6    4 laf4pxy~$&@7. $Ifgdj $Ifgdj L$$Eƀ^F ..Ifgdj rkd$$Ifl4F\#%;e&6    4 laf4p&',@7 $Ifgdj L$$Eƀ^F ..Ifgdj rkd0$$Ifl4F\#%;e&6    4 laf4piJ$Eƀ^FAIfgdj J$Eƀ^F@Ifgdj J$Eƀ^F?Ifgdj j8- $$Ifgdj J$Eƀ^F ..Ifgdj rkdϏ$$Ifl4F\#%;e&6    4 laf4p $Ifgdj jlmnxof $IfgdL $Ifgd( $Ifgd%rkdn$$Ifl4F\#%;e&6    4 laf4p $$Ifgdj  l@7 $Ifgd7L$$Eƀ^F ..Ifgdj rkd $$Ifl4F\#%;e&6    4 laf4plݱ`W $Ifgdj J$Eƀ^FCIfgdj $Ifgdj J$Eƀ^FBIfgd=VA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdK$$Ifl4F\#%;e&6    4 laf4p"ϴѴ@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4pѴҴ״\^A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p^_`ϵеzq $IfgdL $Ifgd( $Ifgd%rkd($$Ifl4F\#%;e&6    4 laf4pеѵֵ@7. $Ifgd $Ifgd L$$Eƀ^F !..Ifgd rkdǔ$$Ifl4F\#%;e&6    4 laf4p)+A8/ $IfgdL $Ifgd(J$Eƀ^F "..IfgdLrkdf$$Ifl4F\#%;e&6    4 laf4p+,-zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p%'A8/ $IfgdL $Ifgd(J$Eƀ^F #..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p'()zq $IfgdL $Ifgd( $Ifgd%rkdC$$Ifl4F\#%;e&6    4 laf4p@7. $Ifgd $Ifgd L$$Eƀ^F $..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4p02@7. $Ifgd $Ifgd L$$Eƀ^F %..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4p238@7. $Ifgd $Ifgd L$$Eƀ^F &..Ifgd rkd $$Ifl4F\#%;e&6    4 laf4p79@7. $Ifgd $Ifgd L$$Eƀ^F '..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4p9:?A8/ $IfgdL $Ifgd(J$Eƀ^F (..IfgdLrkd^$$Ifl4F\#%;e&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4p|~@7. $Ifgd $Ifgd L$$Eƀ^F )..Ifgd rkd$$Ifl4F\#%;e&6    4 laf4p~@7. $Ifgd $Ifgd L$$Eƀ^F *..Ifgd rkd;$$Ifl4F\#%;e&6    4 laf4p`b@7. $Ifgd $Ifgd L$$Eƀ^F +..Ifgd rkdڜ$$Ifl4F\#%;e&6    4 laf4pbch@7. $Ifgd $Ifgd L$$Eƀ^F ,..Ifgd rkdy$$Ifl4F\#%;e&6    4 laf4pEQFA<AgdpgdpFEƀ^F .gd2rkd$$Ifl4F\#%;e&6    4 laf4ps-FEƀ^FFgdpFEƀ^FEgdpFEƀ^FDgdp\s-FEƀ^FIgdpFEƀ^FHgdpFEƀ^FGgdpG[<@MR $$Ifa$gdL8 $Ifgd9T $If^gdL8gdpFEƀ^FJgdpRSXXZ@7. $IfgdL $Ifgd(J$Eƀ^F ..IfgdLtkd$$Ifl44F]#%;f&6    4 laf4pZ[\tuzq $IfgdL $Ifgd( $Ifgd%rkd_$$Ifl4F]#%;f&6    4 laf4pR[\ 1?mn}$% &'tuef~jhqZh@+5U hqZ5jhqZ5U h#5h%h#5hI&mHnHuhxh#5hI&]hLw hLwhI&jhI&UhZh#5hI&CJaJ h#5hI&;uv{8<@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd$$Ifl4F]#%;f&6    4 laf4p<>H)+@7. $Ifgd $Ifgd L$$Eƀ^F ..Ifgd rkd$$Ifl4F]#%;f&6    4 laf4p+,1A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd<$$Ifl4F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdۡ$$Ifl4F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdz$$Ifl4F]#%;f&6    4 laf4p z/J$Eƀ^FKIfgdK $Ifgd#5 $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p  iJ$Eƀ^FNIfgdKJ$Eƀ^FMIfgdKJ$Eƀ^FLIfgdK7. $Ifgd L$$Eƀ^F ..Ifgd rkd$$Ifl4F]#%;f&6    4 laf4p $IfgdL8/ $Ifgd(J$Eƀ^F ..IfgdLrkdW$$Ifl4F]#%;f&6    4 laf4p $Ifgd zq $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p $IfgdLA8 $Ifgd#5J$Eƀ^F ..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p}iJ$Eƀ^FQIfgd#5J$Eƀ^FPIfgd#5J$Eƀ^FOIfgd#5}>iJ$Eƀ^FTIfgd#5J$Eƀ^FSIfgd#5J$Eƀ^FRIfgd#5"#zq $Ifgd( $Ifgd%rkd4$$Ifl4F]#%;f&6    4 laf4p $IfgdL#$%zq $IfgdL $Ifgd( $Ifgd%rkdӦ$$Ifl4F]#%;f&6    4 laf4p@7 $IfgdML$$Eƀ^F ..IfgdMrkdr$$Ifl4F]#%;f&6    4 laf4p>i` $IfgdMJ$Eƀ^FVIfgdMJ$Eƀ^FUIfgdM=?@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkd$$Ifl4F]#%;f&6    4 laf4p?@E#%A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p%&'zq $IfgdL $Ifgd( $Ifgd%rkdO$$Ifl4F]#%;f&6    4 laf4pqsA8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4pstuzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p`b@7. $IfgdM $IfgdML$$Eƀ^F  ..IfgdMrkd,$$Ifl4F]#%;f&6    4 laf4pbchA8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd˫$$Ifl4F]#%;f&6    4 laf4p89zq $IfgdL $Ifgd( $Ifgd%rkdj$$Ifl4F]#%;f&6    4 laf4p9:?A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd $$Ifl4F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p %@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkdG$$Ifl4F]#%;f&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4prt@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd$$$Ifl4F]#%;f&6    4 laf4ptuz@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkdð$$Ifl4F]#%;f&6    4 laf4p y@7 $IfgdML$$Eƀ^F ..IfgdMrkdb$$Ifl4F]#%;f&6    4 laf4py.iJ$Eƀ^FYIfgdMJ$Eƀ^FXIfgdMJ$Eƀ^FWIfgdM8rkd$$Ifl4F]#%;f&6    4 laf4p $IfgdMJ$Eƀ^FZIfgdMfnFEƀ^F[gd#5gd#5FEƀ^F .gd2 !#,7ͽݹݹݵݪݛݓݹݏݹݹݗ h#5h@+h^HhO9hI&jh#5hI&Uhl7hQ h#5hphph@+hBmHnHu h#5hBhBhfZahfZamHnHu h#5hI&jhqZ5U!hfZahfZa0J5>*mHnHu4fCs-FEƀ^F^gd#5FEƀ^F]gd#5FEƀ^F\gd#5Ce_+`FEƀ^F`gd#5gdH $$a$gdMgd#5FEƀ^F_gd#5?sn(FEƀ^Fcgd#5gd#5FEƀ^Fbgd#5FEƀ^Fagd#5?sni\SG $$Ifa$gdL8 $Ifgd9T $If^gdL8gd#5gdaFEƀ^Fegd#5FEƀ^Fdgd#512TUd246BDPRz|"$&028:fhln. 0 N P R ^ `          h#5hI&6] *h#5hI&hLw hLwhI&jhI&Uh#5hI&CJaJhMi h#5hI& hhI&Jr?6 $IfgdML$$Eƀ^F ..IfgdMtkd$$Ifl44Fc#&;l&6    4 laf4pr\S $IfgdMJ$Eƀ^FgIfgdM & F$IfgdMiJ$Eƀ^FfIfgdMg@7 $IfgdML$$Eƀ^F ..IfgdMrkde$$Ifl4Fc#&;l&6    4 laf4pgi` $IfgdMJ$Eƀ^FiIfgdMJ$Eƀ^FhIfgdMA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4Fc#&;l&6    4 laf4pz/J$Eƀ^FjIfgd#5 $Ifgd#5 $Ifgd%rkd$$Ifl4Fc#&;l&6    4 laf4piJ$Eƀ^FmIfgd#5J$Eƀ^FlIfgd#5J$Eƀ^FkIfgd#5/0i`W $IfgdL $Ifgd#5J$Eƀ^FoIfgd#5J$Eƀ^FnIfgd#5012zq $IfgdL $Ifgd( $Ifgd%rkdB$$Ifl4Fc#&;l&6    4 laf4p@7. $Ifgd@+ $Ifgd@+L$$Eƀ^F ..Ifgd@+rkd$$Ifl4Fc#&;l&6    4 laf4p!JNA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4Fc#&;l&6    4 laf4pNPRzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4Fc#&;l&6    4 laf4p )+@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd$$Ifl4Fc#&;l&6    4 laf4p+,1A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd]$$Ifl4Fc#&;l&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4Fc#&;l&6    4 laf4p68zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4Fc#&;l&6    4 laf4p8:Dhl@7. $IfgdM $IfgdML$$Eƀ^F ..IfgdMrkd:$$Ifl4Fc#&;l&6    4 laf4plnxA8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd$$Ifl4Fc#&;l&6    4 laf4p  zq $IfgdL $Ifgd( $Ifgd%rkdx$$Ifl4Fc#&;l&6    4 laf4p     A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd$$Ifl4Fc#&;l&6    4 laf4p     zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4Fc#&;l&6    4 laf4p     @7. $Ifgdf $IfgdfL$$Eƀ^F  ..IfgdfrkdU$$Ifl4Fc#&;l&6    4 laf4p   FAAgd#5FEƀ^F .gd2rkd$$Ifl4Fc#&;l&6    4 laf4p        p}~"!#! #!###%%&&m'n'' h#5hU\ hB6AhU\hU\hB6AhU\CJaJh#5hI&CJaJ hhI&hI&hI&B*phh#5hI&B*ph h#5hfhfhM h+3h4h*uh@hMihi h#5h% h#5hI&18s-FEƀ^Frgd#5FEƀ^Fqgd#5FEƀ^Fpgd#5j p0 $$Ifa$gdL8 $Ifgd9T $If^gdL8gd;"gdLBSFEƀ^Fsgd#5 @7. $IfgdL $Ifgd(J$Eƀ^F ..IfgdLtkd$$Ifl44FL\#%;&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd@$$Ifl4FL\#%;&6    4 laf4pA8 $Ifgd;"J$Eƀ^F ..IfgdLrkd$$Ifl4FL\#%;&6    4 laf4p,f}iJ$Eƀ^FvIfgd#5J$Eƀ^FuIfgd#5J$Eƀ^FtIfgd#5}zq $Ifgd( $Ifgd%rkd$$Ifl4FL\#%;&6    4 laf4p $IfgdLz|A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd,$$Ifl4FL\#%;&6    4 laf4p|}~zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4FL\#%;&6    4 laf4p()zq $IfgdL $Ifgd( $Ifgd%rkdt$$Ifl4FL\#%;&6    4 laf4p)*/A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4FL\#%;&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4FL\#%;&6    4 laf4pA8 $Ifgd;"J$Eƀ^F ..IfgdLrkd`$$Ifl4FL\#%;&6    4 laf4p= U iJ$Eƀ^FyIfgd#5J$Eƀ^FxIfgd#5J$Eƀ^FwIfgd#5U   !iJ$Eƀ^F|Ifgd#5J$Eƀ^F{Ifgd#5J$Eƀ^FzIfgd#5!!!"!#!""zq $Ifgd( $Ifgd%rkd$$Ifl4FL\#%;&6    4 laf4p $IfgdL"""##A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4FL\#%;&6    4 laf4p# #!###zq $IfgdL $Ifgd( $Ifgd%rkdL$$Ifl4FL\#%;&6    4 laf4p###3$4$zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4FL\#%;&6    4 laf4p4$5$:$y$@7 $Ifgd13\L$$Eƀ^F ..Ifgd13\rkd$$Ifl4FL\#%;&6    4 laf4py$$$$i` $Ifgd13\J$Eƀ^F~Ifgd13\J$Eƀ^F}Ifgd13\$$$%%A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd8$$Ifl4FL\#%;&6    4 laf4p%%%%%zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4FL\#%;&6    4 laf4p%%%&&@7. $Ifgd13\ $Ifgd13\L$$Eƀ^F  ..Ifgd13\rkd$$Ifl4FL\#%;&6    4 laf4p&&&n'o'zq $IfgdL $IfgdB6A $IfgdB6Arkd$$$Ifl4FL\#%;&6    4 laf4po'p'u'2)6)A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd$$Ifl4FL\#%;&6    4 laf4p'''((((8):)***,, ,,,11g3377777777Y8f8_AgAYBZB]BkBpB DDkDlDFFGGHH}H~HIIʻʰʬʡʬʕʬʑʻʇʰʰʰʰʰh#5hI&>*h#5hI&6]h^2h#5hI&mHnHuh+ZX h#5hP5hP5h#5hI&CJaJ hhI&hI&h9 h#5hI& h#5h%h#5hU\CJaJ h#5hU\hLw hLwhU\jhU\U26)8):)**zq $IfgdL $Ifgd( $Ifgd%rkdl$$Ifl4FL\#%;&6    4 laf4p****+, ,FA</ $If^gdL8gd]jgd;"FEƀ^F .gd2rkd$$Ifl4FL\#%;&6    4 laf4p ,,,,",q%L$$Eƀ^F ..Ifgd13\ykd$$Ifl44F]#%;f&6    4 laf4gp $$Ifa$gdL8 $Ifgd9T",[-]-^-c-u)L$$Eƀ^F ..Ifgd13\wkdf$$Ifl4F]#%;f&6    4 laf4gp $Ifgd13\ $Ifgd13\c--....z.L$$Eƀ^F ..Ifgd13\rkd$$Ifl4F]#%;f&6    4 laf4p $Ifgd13\ $Ifgd13\..-/F/iJ$Eƀ^FIfgd13\J$Eƀ^FIfgd13\J$Eƀ^FIfgd13\F/d///i` $Ifgd13\J$Eƀ^FIfgd13\J$Eƀ^FIfgd13\///B0D0;2) $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\wkd$$Ifl4F]#%;f&6    4 laf4gpD0E0J000<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkdW$$Ifl4F]#%;f&6    4 laf4gp01133~ul $IfgdL $Ifgd( $Ifgd%wkd$$Ifl4F]#%;f&6    4 laf4gp333d3f3;2) $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\wkd$$Ifl4F]#%;f&6    4 laf4gpf3g33S4:7Y7A<<<gd;"FEƀ^F .gd2wkdR$$Ifl4F]#%;f&6    4 laf4gpY7Y8>99s-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#599y:;;9<snnngd;"FEƀ^Fgd#5FEƀ^Fgd#59<=x>L@ZB^BkBpBsni\SG $$Ifa$gd'K $Ifgd9T $If^gd'Kgd]jgd;"FEƀ^Fgd#5FEƀ^Fgd#5pBqBvBBB:1( $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\ykd$$Ifl44F=#%;nF&6    4 laf4gpBBBC;2 $Ifgd13\L$$Eƀ^F ..Ifgd13\wkd$$Ifl4F=#%;nF&6    4 laf4gpCCCDiJ$Eƀ^FIfgd13\J$Eƀ^FIfgd13\J$Eƀ^FIfgd13\DDDDhD8/ $Ifgd(J$Eƀ^F ..IfgdLrkdV$$Ifl4F=#%;nF&6    4 laf4p $Ifgd13\hDjDkDlDZE[E~ul $Ifgd( $Ifgd%wkd$$Ifl4F=#%;nF&6    4 laf4gp $IfgdL[E\EaEEE<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkd$$Ifl4F=#%;nF&6    4 laf4gpEFFFF~ul $IfgdL $Ifgd( $Ifgd%wkdG$$Ifl4F=#%;nF&6    4 laf4gpFFFOGQG;2) $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\wkd$$Ifl4F=#%;nF&6    4 laf4gpQGRGWGHH<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkd$$Ifl4F=#%;nF&6    4 laf4gpHHH{H|H~ul $IfgdL $Ifgd( $Ifgd%wkdB$$Ifl4F=#%;nF&6    4 laf4gp|H}H~H I!I~ul $IfgdL $Ifgd( $Ifgd%wkd$$Ifl4F=#%;nF&6    4 laf4gp!I"I'IjIlI;2) $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\wkd$$Ifl4F=#%;nF&6    4 laf4gplImIrIII<3* $IfgdL $Ifgd(J$Eƀ^F ..IfgdLwkd=$$Ifl4F=#%;nF&6    4 laf4gpIII J J~ul $IfgdL $Ifgd( $Ifgd%wkd$$Ifl4F=#%;nF&6    4 laf4gp J J JJLNA<<<gd;"FEƀ^F .gd2wkd$$Ifl4F=#%;nF&6    4 laf4gpI J JNNNNPP%R&RTT0TTTTUUYY[[\\\9]<]@]A]]]]]]]^^^^^ ^>^@^B^R^T^x_z_bb2b4b6bDbFb1d2deeGhZhkkmh#5hI&mHnHuhLw hLwjhI&Uh'J:hI&6]hI&CJaJ h;"hI&h#5hI&CJaJ hhI&hI& h#5h% h#5hI&@NNNNNitkd8$$Ifl44F]#%;f&6    4 laf4p $$Ifa$gdg $Ifgd9T $If^gdgNNPOROSO.rkd$$Ifl4F]#%;f&6    4 laf4p $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\SOXOOOO.rkd$$Ifl4F]#%;f&6    4 laf4p $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\OOPPP/rkd$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdLPPIQJQKQqrkd$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd( $Ifgd%KQPQ"R$R%R/rkd\$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdL%R&RSS Sqrkd$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd( $Ifgd% S%SSTT/rkd$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdLTT0TrTTTWN $IfgdLJ$Eƀ^FIfgd;"J$Eƀ^FIfgd;" $Ifgd;" $Ifgd%TTT1UHUz/J$Eƀ^FIfgd;" $Ifgd;" $Ifgd%rkd9$$Ifl4F]#%;f&6    4 laf4pHURUSUTU8rkd$$Ifl4F]#%;f&6    4 laf4p $IfgdLJ$Eƀ^FIfgd;"TUYUUUU/rkdw$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdLUU)VfVVWJ$Eƀ^FIfgd;"J$Eƀ^FIfgd;" $Ifgda $Ifgd%V6WWWi` $IfgdLJ$Eƀ^FIfgd;"J$Eƀ^FIfgd;"WWXXX@7. $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\rkd$$Ifl4F]#%;f&6    4 laf4pXXXYYA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4pYYYYYzq $IfgdL $Ifgd( $Ifgd%rkdT$$Ifl4F]#%;f&6    4 laf4pYYYZZ@7. $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\rkd$$Ifl4F]#%;f&6    4 laf4pZZZZ[@7. $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\rkd$$Ifl4F]#%;f&6    4 laf4p[[[[[A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd1$$Ifl4F]#%;f&6    4 laf4p[[[\\zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p\\\9];]@7. $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\rkdo$$Ifl4F]#%;f&6    4 laf4p;]<]A]]]A8/ $IfgdL $Ifgd(J$Eƀ^F ..Ifgd'J:rkd$$Ifl4F]#%;f&6    4 laf4p]]]t_v_zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4pv_x_z_``zq $IfgdL $Ifgd( $Ifgd%rkdL$$Ifl4F]#%;f&6    4 laf4p```aa@7. $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\rkd$$Ifl4F]#%;f&6    4 laf4paaa.d0dA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F]#%;f&6    4 laf4p0d1d2dddzq $IfgdL $Ifgd( $Ifgd%rkd)$$Ifl4F]#%;f&6    4 laf4pdddMeOe@7. $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\rkd$$Ifl4F]#%;f&6    4 laf4pOePeUeee@7. $Ifgd13\ $Ifgd13\L$$Eƀ^F ..Ifgd13\rkdg$$Ifl4F]#%;f&6    4 laf4peeeffFAAgd;"FEƀ^F .gd2rkd$$Ifl4F]#%;f&6    4 laf4pfXg h\h,is-(gd;"FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5,ijkrmnnnnn_tkd$$Ifl44F\#%;e&6    4 laf4p $$Ifa$gdg $Ifgd9T $If^gdggd]jgd;"mmn nnnnnnnn $Ifgd(> L$$Eƀ^F ..Ifgd(> ~~.rkd$$Ifl4F]#%;f&6    4 laf4p $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> `J$Eƀ^FIfgd#5 $IfgdLBSJ$Eƀ^F ..IfgdLlni` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5nopzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4p A8 $Ifgd;"J$Eƀ^F ..IfgdLrkd>$$Ifl4F]#%;f&6    4 laf4pDFi` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5FGHڃۃzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F]#%;f&6    4 laf4pۃ܃mA8 $Ifgd;"J$Eƀ^F ..IfgdLrkd| $$Ifl4F]#%;f&6    4 laf4pmt|iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#58/ $Ifgd%rkd $$Ifl4F]#%;f&6    4 laf4p $IfgdLJ$Eƀ^FIfgd#5z/J$Eƀ^F ..IfgdLrkd $$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd(`J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5 $IfgdLBSDž҅ԅi` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5ԅՅօSTzq $IfgdL $Ifgd( $Ifgd%rkdY $$Ifl4F]#%;f&6    4 laf4pTUZ܆ކ@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd $$Ifl4F]#%;f&6    4 laf4pކ߆fh@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd $$Ifl4F]#%;f&6    4 laf4phi}FAAAAAgd;"FEƀ^F .gd2rkd6 $$Ifl4F]#%;f&6    4 laf4pLjш҈uvۍލِڐ#$^_ДєҔהؔ345?ñjjbjjbh7mqB*ph)hqh7mqB*CJOJQJ^JaJph hqh7mqCJOJQJ^JaJh7mq5B*ph,hqh7mq5B*CJOJQJ^JaJph#hqh7mq5CJOJQJ^JaJh#5hI&CJaJ hhI&hI&h#5hI&6] h#5hI&jhqZ5Uh#rhI&0J5>*&{͌NۍߍdtkdP$$Ifl44F_#%<h&6    4 laf4p $$Ifa$gdg $Ifgd9T $If^gdggd;"P`J$Eƀ^FIfgd#5 $Ifgd;"J$Eƀ^F ..IfgdL,i` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5+,zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F_#%<h&6    4 laf4p,-2֐ؐA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F_#%<h&6    4 laf4pِؐڐzq $IfgdL $Ifgd( $Ifgd%rkd6$$Ifl4F_#%<h&6    4 laf4p "A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F_#%<h&6    4 laf4p"#$zq $IfgdL $Ifgd( $Ifgd%rkdt$$Ifl4F_#%<h&6    4 laf4p8J$Eƀ^FIfgdLBS $Ifgd%rkd$$Ifl4F_#%<h&6    4 laf4pi` $IfgdLJ$Eƀ^FIfgdLBSJ$Eƀ^FIfgdLBSzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F_#%<h&6    4 laf4p[]A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdQ$$Ifl4F_#%<h&6    4 laf4p]^_zq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F_#%<h&6    4 laf4pєtt$$$Ifa$gd@K$ $Ifgd%rkd$$Ifl4F_#%<h&6    4 laf4pєҔؔ4FTkd$IfK$L$Tl40 64 laf4T$$$Ifa$gd@K$Tkd.$IfK$L$Tl40 64 laf4T45@stuvG>5 $IfgdL $IfgdYTkd$IfK$L$Tl40 64 laf4T $$Ifa$gd@K$Tkd($IfK$L$Tl40 64 laf4T?@rstwxɕʕٕNPnpruy}žÞRSbʿʷʿʷʷʢʿʞʞʿʷʿʷʞ h#5h@h@ *h#5hI&hLw hLwhI&jhI&Uh#5hI&CJaJ h#5hI&h7mqB*ph hqh7mqCJOJQJ^JaJ)hqh7mqB*CJOJQJ^JaJph;vwxzq $IfgdL $Ifgd( $Ifgd%rkd"$$Ifl4F_#%<h&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F_#%<h&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd`$$Ifl4F_#%<h&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F_#%<h&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F_#%<h&6    4 laf4pHJzq $IfgdL $Ifgd( $Ifgd%rkd=$$Ifl4F_#%<h&6    4 laf4pJLVA8 $IfgdLBSJ$Eƀ^F ..IfgdLrkd$$Ifl4F_#%<h&6    4 laf4pPi`W $IfgdL $IfgdLBSJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5žÞzq $IfgdL $Ifgd( $Ifgd%rkd{$$Ifl4F_#%<h&6    4 laf4p$(@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd$$Ifl4F_#%<h&6    4 laf4p(*4A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F_#%<h&6    4 laf4p$&DFHVX  ު^ijYdeíέ6ABîή$&(FHJXZBHJ䕤h:h:CJaJhl jhl U h#5hl hl hl h#5h^Hh^H h#5h^Hh^Hh#5hI&6]hU\ h#5h@h@h#5hI&CJaJhLw hLwhI&jhI&U h#5hI&4 abzq $IfgdL $Ifgd( $Ifgd%rkdX$$Ifl4F_#%<h&6    4 laf4pbchO@7 $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd$$Ifl4F_#%<h&6    4 laf4pOޥiJ$Eƀ^FIfgd(> J$Eƀ^FIfgd(> J$Eƀ^FIfgd(>  %7. $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd$$Ifl4F_#%<h&6    4 laf4p $Ifgd(> `iJ$Eƀ^FIfgd(> J$Eƀ^FIfgd(> J$Eƀ^FIfgd(> 7. $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd5$$Ifl4F_#%<h&6    4 laf4p $Ifgd(> @7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd$$Ifl4F_#%<h&6    4 laf4p@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkds $$Ifl4F_#%<h&6    4 laf4p <@7 $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd!$$Ifl4F_#%<h&6    4 laf4p<ЭiJ$Eƀ^FIfgd(> J$Eƀ^FIfgd(> J$Eƀ^FIfgd(> 8rkd!$$Ifl4F_#%<h&6    4 laf4p $Ifgd(> J$Eƀ^FIfgd(> /rkdP"$$Ifl4F_#%<h&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqrkd"$$Ifl4F_#%<h&6    4 laf4p $IfgdL $Ifgd( $Ifgd%BFH.rkd#$$Ifl4F_#%<h&6    4 laf4p $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> HJqrkd$$$Ifl4F_#%<h&6    4 laf4p $IfgdL $IfgdUM $Ifgd:J\^$&DFHXZ\^|~µطڷ()WXYhxy:E@\ٻ٭ h#5h% h:6]h@Fh:CJaJ *h#5h:h#5h:CJaJ h#5h:hLw hLwj-$hUMUjh:Uh:AG`J$Eƀ^FIfgd#5 $Ifgd;"J$Eƀ^F ..IfgdL8/ $Ifgd%rkd;%$$Ifl4F_#%<h&6    4 laf4p $IfgdLJ$Eƀ^FIfgd#5&'(-z.L$$Eƀ^F ..Ifgd(> rkd%$$Ifl4F_#%<h&6    4 laf4p $IfgdL $Ifgd(-z/J$Eƀ^F ..IfgdLrkdy&$$Ifl4F_#%<h&6    4 laf4p $Ifgd(> $Ifgd(> npzqh $Ifgd( $Ifgd%rkd'$$Ifl4F_#%<h&6    4 laf4p $IfgdL $Ifgd(pr|  @7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd'$$Ifl4F_#%<h&6    4 laf4p  @7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkdV($$Ifl4F_#%<h&6    4 laf4p"$@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd($$Ifl4F_#%<h&6    4 laf4p$%*%'A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd)$$Ifl4F_#%<h&6    4 laf4p'()»zq $IfgdL $Ifgd( $Ifgd%rkd3*$$Ifl4F_#%<h&6    4 laf4p»ûȻ57@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd*$$Ifl4F_#%<h&6    4 laf4p78=żǼ@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkdq+$$Ifl4F_#%<h&6    4 laf4pǼȼͼA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd,$$Ifl4F_#%<h&6    4 laf4p|~zq $IfgdL $Ifgd( $Ifgd%rkd,$$Ifl4F_#%<h&6    4 laf4p~uwA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdN-$$Ifl4F_#%<h&6    4 laf4pwxyzq $IfgdW+ $IfgdW+ $Ifgd@Frkd-$$Ifl4F_#%<h&6    4 laf4p A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd.$$Ifl4F_#%<h&6    4 laf4p>?zq $IfgdL $Ifgd( $Ifgd%rkd+/$$Ifl4F_#%<h&6    4 laf4p?@\8FAAgd;"FEƀ^F .gd2rkd/$$Ifl4F_#%<h&6    4 laf4ps-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5Hs-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5)n'snnnninnnnngd(gd;"FEƀ^Fgd#5FEƀ^Fgd#5 \"#IJKLN9O'ABCDQ<?@HUZH .02>@JL˵˭˥˛ǓǓǓǓǓhLw hLwjh^Uh#5h^h5gh@Fh^5h#5h^]h#5h^CJaJ hh^h^ h#5h^ h#5h%h;"hI&6] h#5h@Fh@F h#5h_h_ h#5hI&6=<@UZ $$Ifa$gdg $Ifgd9T $If^gdgFEƀ^F .gd2gd;"gd( Z[`@7. $IfgdL $Ifgd(J$Eƀ^F ..IfgdLtkdi0$$Ifl44F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd1$$Ifl4F]#%;f&6    4 laf4p@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd1$$Ifl4F]#%;f&6    4 laf4p@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkdO2$$Ifl4F]#%;f&6    4 laf4p@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd2$$Ifl4F]#%;f&6    4 laf4p@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd3$$Ifl4F]#%;f&6    4 laf4pA88 $IfgdJ$Eƀ^F ..Ifgdrkd,4$$Ifl4F]#%;f&6    4 laf4p $Ifgdrkd4$$Ifl4F]#%;f&6    4 laf4pLjln|~gh 2:;~45#$ders#$So  !&@B`bdpr hh^h_ h#5h%h#5h^CJaJ h#5h^hLw hLwjh^Uh^LA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdj5$$Ifl4F]#%;f&6    4 laf4pjkzq $IfgdL $Ifgd( $Ifgd%rkd 6$$Ifl4F]#%;f&6    4 laf4pklqdfA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd6$$Ifl4F]#%;f&6    4 laf4pfghzq $IfgdL $Ifgd( $Ifgd%rkdG7$$Ifl4F]#%;f&6    4 laf4p79A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd7$$Ifl4F]#%;f&6    4 laf4p9:;tuzq $IfgdL $Ifgd( $Ifgd%rkd8$$Ifl4F]#%;f&6    4 laf4puv{A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd$9$$Ifl4F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkd9$$Ifl4F]#%;f&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkdb:$$Ifl4F]#%;f&6    4 laf4p<=zq $IfgdL $Ifgd( $Ifgd%rkd;$$Ifl4F]#%;f&6    4 laf4p=>C@7. $Ifgd(> $Ifgd(> L$$Eƀ^F  ..Ifgd(> rkd;$$Ifl4F]#%;f&6    4 laf4p@7. $Ifgd(> $Ifgd(> L$$Eƀ^F  ..Ifgd(> rkd?<$$Ifl4F]#%;f&6    4 laf4p@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd<$$Ifl4F]#%;f&6    4 laf4p]@7 $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd}=$$Ifl4F]#%;f&6    4 laf4p]xiJ$Eƀ^FIfgd(> J$Eƀ^FIfgd(> J$Eƀ^FIfgd(> i` $Ifgd(> J$Eƀ^FIfgd(> J$Eƀ^FIfgd(> Y[@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd>$$Ifl4F]#%;f&6    4 laf4p[\a@7 $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd>$$Ifl4F]#%;f&6    4 laf4piJ$Eƀ^FIfgd(> J$Eƀ^FIfgd(> J$Eƀ^FIfgd(> mi` $Ifgd(> J$Eƀ^FIfgd(> J$Eƀ^FIfgd(> A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdZ?$$Ifl4F]#%;f&6    4 laf4pDEzq $IfgdL $Ifgd( $Ifgd%rkd?$$Ifl4F]#%;f&6    4 laf4pEFK@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkd@$$Ifl4F]#%;f&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd7A$$Ifl4F]#%;f&6    4 laf4pefzq $IfgdL $Ifgd( $Ifgd%rkdA$$Ifl4F]#%;f&6    4 laf4pfglA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkduB$$Ifl4F]#%;f&6    4 laf4pEFzq $IfgdL $Ifgd( $Ifgd%rkdC$$Ifl4F]#%;f&6    4 laf4pFGLA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdC$$Ifl4F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdRD$$Ifl4F]#%;f&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdD$$Ifl4F]#%;f&6    4 laf4p zq $IfgdL $Ifgd( $Ifgd%rkdE$$Ifl4F]#%;f&6    4 laf4p !&13A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd/F$$Ifl4F]#%;f&6    4 laf4p345 zq $IfgdL $Ifgd( $Ifgd%rkdF$$Ifl4F]#%;f&6    4 laf4p !&@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkdmG$$Ifl4F]#%;f&6    4 laf4p "A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd H$$Ifl4F]#%;f&6    4 laf4p"#$zq $IfgdL $Ifgd( $Ifgd%rkdH$$Ifl4F]#%;f&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdJI$$Ifl4F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdI$$Ifl4F]#%;f&6    4 laf4pacA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdJ$$Ifl4F]#%;f&6    4 laf4pcdepqzq $IfgdL $Ifgd( $Ifgd%rkd'K$$Ifl4F]#%;f&6    4 laf4pqrs89zq $IfgdL $Ifgd( $Ifgd%rkdK$$Ifl4F]#%;f&6    4 laf4p9:?A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdeL$$Ifl4F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdM$$Ifl4F]#%;f&6    4 laf4p "A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdM$$Ifl4F]#%;f&6    4 laf4p"#$zq $IfgdL $Ifgd( $Ifgd%rkdBN$$Ifl4F]#%;f&6    4 laf4p!@7. $Ifgd(> $Ifgd(> L$$Eƀ^F ..Ifgd(> rkdN$$Ifl4F]#%;f&6    4 laf4p!"'A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkdO$$Ifl4F]#%;f&6    4 laf4p78zq $IfgdL $Ifgd( $Ifgd%rkdP$$Ifl4F]#%;f&6    4 laf4p89>@7. $Ifgd(> $Ifgd(> L$$Eƀ^F !..Ifgd(> rkdP$$Ifl4F]#%;f&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F "..IfgdLrkd]Q$$Ifl4F]#%;f&6    4 laf4pQRzq $IfgdL $Ifgd( $Ifgd%rkdQ$$Ifl4F]#%;f&6    4 laf4pRSoFAAgd;"FEƀ^F .gd2rkdR$$Ifl4F]#%;f&6    4 laf4p$s-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5$_,r !& $$Ifa$gdg $Ifgd9T $If^gdggd;"FEƀ^Fgd#5 &',?6 $Ifgd(> L$$Eƀ^F ..Ifgd(> tkd:S$$Ifl44F]#%;f&6    4 laf4pKiJ$Eƀ^FIfgd(> J$Eƀ^FIfgd(> J$Eƀ^FIfgd(> 8rkdS$$Ifl4F]#%;f&6    4 laf4p $Ifgd(> J$Eƀ^FIfgd(> /rkdT$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqrkd U$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd( $Ifgd%*,ABfgde        + - F H a b      ?     ?S/"%&.;ɽ殣 h#5h%h#5h^B*ph h1h^h#5h^6h#5h^mHnHuh#5h^H*hLw hLwh^jh^U h#5h^h#5h^CJaJh^CJaJ=/rkdU$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd'J:J$Eƀ^F ..Ifgd'J:?@ABqrkd^V$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd( $Ifgd%zq $IfgdL $Ifgd( $Ifgd%rkdV$$Ifl4F]#%;f&6    4 laf4pA8/ $IfgdL $Ifgd'J:J$Eƀ^F ..Ifgd'J:rkdW$$Ifl4F]#%;f&6    4 laf4pdezq $IfgdL $Ifgd( $Ifgd%rkd;X$$Ifl4F]#%;f&6    4 laf4pefgbczq $IfgdL $Ifgd( $Ifgd%rkdX$$Ifl4F]#%;f&6    4 laf4pcdeA8/ $IfgdL $Ifgd'J:J$Eƀ^F ..Ifgd'J:rkdyY$$Ifl4F]#%;f&6    4 laf4p  zq $IfgdL $Ifgd( $Ifgd%rkdZ$$Ifl4F]#%;f&6    4 laf4p    A8 $Ifgd;"J$Eƀ^F ..Ifgdf,rkdZ$$Ifl4F]#%;f&6    4 laf4p   * iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5* E ^ ` i` $IfgdLJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5` a b   zq $IfgdL $Ifgd( $Ifgd%rkdV[$$Ifl4F]#%;f&6    4 laf4p     A8/ $IfgdL $Ifgd(J$Eƀ^F ..Ifgdf,rkd[$$Ifl4F]#%;f&6    4 laf4p   ; < zq $IfgdL $Ifgd( $Ifgd%rkd\$$Ifl4F]#%;f&6    4 laf4p< = B  A8 $Ifgd;"J$Eƀ^F ..IfgdLrkd3]$$Ifl4F]#%;f&6    4 laf4p    iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5   / iJ$Eƀ^FIfgd#5J$Eƀ^FIfgd#5J$Eƀ^FIfgd#5/ ?    /rkd]$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd1J$Eƀ^FIfgd#5  nopqrkdq^$$Ifl4F]#%;f&6    4 laf4p $IfgdL $Ifgd( $Ifgd%pu<>?.rkd_$$Ifl4F]#%;f&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F  ..Ifgdz?S/"&;@ $$Ifa$gdg $Ifgd9T $If^gdggd;"FEƀ^F .gd2;@WX}~_s """"%@%T+U+]+^+a+d+r+w+,,X-Y-22|4~4444444444ÿûûôéééááhLw hLwjhUh#5hCJaJ hhhhQE h#5h hhg h#5hghgh^ h#5h%h#5h^CJaJ h#5h^ hh^<@AB?6* $$Ifa$gdg $IfgdzL$$Eƀ^F ..Ifgdztkd_$$Ifl44F[#%h_d&6    4 laf4pA8/ $Ifgdg $Ifgdf,J$Eƀ^F ..Ifgdf,rkdW`$$Ifl4F[#%h_d&6    4 laf4pUVzq $Ifgdg $Ifgd( $Ifgd%rkd`$$Ifl4F[#%h_d&6    4 laf4pVWXzq $Ifgdg $Ifgd( $Ifgd%rkda$$Ifl4F[#%h_d&6    4 laf4pA8/ $Ifgdg $Ifgdf,J$Eƀ^F ..Ifgdf,rkd4b$$Ifl4F[#%h_d&6    4 laf4p{|zq $Ifgdg $Ifgd( $Ifgd%rkdb$$Ifl4F[#%h_d&6    4 laf4p|}~A8/ $Ifgdg $Ifgdf,J$Eƀ^F ..Ifgdf,rkdrc$$Ifl4F[#%h_d&6    4 laf4p~zq $Ifgdg $Ifgd( $Ifgd%rkdd$$Ifl4F[#%h_d&6    4 laf4p\^A8/ $Ifgdg $Ifgdf,J$Eƀ^F ..Ifgdf,rkdd$$Ifl4F[#%h_d&6    4 laf4p^_s#xFAAgd;"FEƀ^F .gd2rkdOe$$Ifl4F[#%h_d&6    4 laf4px@q+FEƀ^Fgd#5FEƀ^Fgd#5G$Eƀ^Fgdz@Pss-FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5/snni\SG $$Ifa$gdg $Ifgd9T $If^gdggd(gd;"FEƀ^FgdLBSFEƀ^FgdLBSTV@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkde$$Ifl4F]#%;f&6    4 laf4pVW\ @7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkdf$$Ifl4F]#%;f&6    4 laf4pA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd2g$$Ifl4F]#%;f&6    4 laf4pzq $IfgdL $Ifgd( $Ifgd%rkdg$$Ifl4F]#%;f&6    4 laf4p@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkdph$$Ifl4F]#%;f&6    4 laf4p<>@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkdi$$Ifl4F]#%;f&6    4 laf4p>?D@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkdi$$Ifl4F]#%;f&6    4 laf4p  !J""FAAAAgd;"FEƀ^F .gd2rkdMj$$Ifl4F]#%;f&6    4 laf4p"""""itkdj$$Ifl44F\#%;e&6    4 laf4p $$Ifa$gd*<@ $Ifgd9T $If^gdg""\#^#_#.rkdk$$Ifl4F\#%;e&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdz_#d####.rkd3l$$Ifl4F\#%;e&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdz##P$R$S$.rkdl$$Ifl4F\#%;e&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F ..IfgdzS$X$%%%.rkdqm$$Ifl4F\#%;e&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdz%@%&0())D*nFEƀ^Fgd#5gd;"FEƀ^F .gd2D*#+a+e+r+w+ $$Ifa$gdg $Ifgd9T $If^gdggd*fFEƀ^Fgd#5w+x+}++,@7. $IfgdL $Ifgd(J$Eƀ^F ..IfgdLtkdn$$Ifl44F\#%;e&6    4 laf4p,,,,,zq $IfgdL $Ifgd( $Ifgd%rkdn$$Ifl4F\#%;e&6    4 laf4p,,,U-W-A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdWo$$Ifl4F\#%;e&6    4 laf4pW-X-Y-..zq $IfgdL $Ifgd( $Ifgd%rkdo$$Ifl4F\#%;e&6    4 laf4p...0/2/@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkdp$$Ifl4F\#%;e&6    4 laf4p2/3/8/00@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkd4q$$Ifl4F\#%;e&6    4 laf4p000y0{0@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkdq$$Ifl4F\#%;e&6    4 laf4p{0|00t1v1@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkdrr$$Ifl4F\#%;e&6    4 laf4pv1w1|122A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkds$$Ifl4F\#%;e&6    4 laf4p222S2T2zq $IfgdL $Ifgd( $Ifgd%rkds$$Ifl4F\#%;e&6    4 laf4pT2U2Z23353@7. $Ifgdz $IfgdzL$$Eƀ^F ..IfgdzrkdOt$$Ifl4F\#%;e&6    4 laf4p5363;3&4*4@7. $Ifgdz $IfgdzL$$Eƀ^F  ..Ifgdzrkdt$$Ifl4F\#%;e&6    4 laf4p*4,46465@7 $IfgdzL$$Eƀ^F  ..Ifgdzrkdu$$Ifl4F\#%;e&6    4 laf4p4444445555 5I7J788W:::::::B;l;m;;;r<y<<<>>>(>V>_>F?N?^?i????@@S@W@-A;AAAAAAAAAAAAABB5B6BsBѶh#-h#-mHnHuh#5h~(mHnHuh.M hXOh~(h~( h#5h~(h#5hCJaJh h#5hjhUhLw hLwB65555i` $IfgdzJ$Eƀ^FIfgdzJ$Eƀ^FIfgdz55566@7. $Ifgdz $IfgdzL$$Eƀ^F  ..Ifgdzrkd,v$$Ifl4F\#%;e&6    4 laf4p666F7H7A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkdv$$Ifl4F\#%;e&6    4 laf4pH7I7J777zq $IfgdL $Ifgd( $Ifgd%rkdjw$$Ifl4F\#%;e&6    4 laf4p77888A8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd x$$Ifl4F\#%;e&6    4 laf4p88899zq $IfgdL $Ifgd( $Ifgd%rkdx$$Ifl4F\#%;e&6    4 laf4p99999@7. $Ifgdz $IfgdzL$$Eƀ^F ..IfgdzrkdGy$$Ifl4F\#%;e&6    4 laf4p999T:V:@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkdy$$Ifl4F\#%;e&6    4 laf4pV:W::::FA<gd;"gd9TFEƀ^F .gd2rkdz$$Ifl4F\#%;e&6    4 laf4p:;;.;;s-(gd;"FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5;;<=d==dFEƀ^Fgd#5FEƀ^Fgd#5gd%>gd;"gd9T=>>@@ ABCiFEƀ^Fgd#5gd;"gd9TFEƀ^Fgd#5sBtB2D?DDDDDDDmEpEJFcFmFpFF,G|GGGGGGHHLLfNoNNNPPxPyPQQpQqQmRnRRRRRSS,T-TJTlTTT UUWWWWWWWWW㭨hLw hLwjh~(Uh#5h~(mHnHuh#-h#5h~(CJaJh;H hh~(h-h~(\h~(h#5h~(\ h#5h~(h#5h~(h+u@CC2DDoEs-(gd;"FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5oEcFFfG|GGGGsni\SG $$Ifa$gdg $Ifgd9T $If^gdggd9Tgd;"FEƀ^Fgd+WFEƀ^Fgd+WGGG^H`H?6- $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdztkd${$$Ifl44F\#%;e&6    4 laf4p`HaHfHHHA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd{$$Ifl4F\#%;e&6    4 laf4pHHHIIzq $IfgdL $Ifgd( $Ifgd%rkdk|$$Ifl4F\#%;e&6    4 laf4pIIIpJrJ@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkd }$$Ifl4F\#%;e&6    4 laf4prJsJxJFKHK@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkd}$$Ifl4F\#%;e&6    4 laf4pHKIKNKKK@7. $Ifgdz $IfgdzL$$Eƀ^F ..IfgdzrkdH~$$Ifl4F\#%;e&6    4 laf4pKKKLL@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkd~$$Ifl4F\#%;e&6    4 laf4pLLLLLA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4pLLLMMzq $IfgdL $Ifgd( $Ifgd%rkd%$$Ifl4F\#%;e&6    4 laf4pMMMNNA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdĀ$$Ifl4F\#%;e&6    4 laf4pNNNjOkOzq $IfgdL $Ifgd( $Ifgd%rkdc$$Ifl4F\#%;e&6    4 laf4pkOlOqOuPwPA8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4pwPxPyPQQzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pQQQRRzq $IfgdL $IfgdLBS $Ifgd%rkd@$$Ifl4F\#%;e&6    4 laf4pRRRSS6- $IfgdLJ$Eƀ^FIfgdLBS $Ifgd%tkd߃$$Ifl4&F\#%;`e&6    4 laf4pSSS*T+T6- $IfgdLJ$Eƀ^FIfgdLBS $Ifgd%tkd$$Ifl4F\#%; e&6    4 laf4p+T,T-TTT6- $IfgdLJ$Eƀ^FIfgdLBS $Ifgd%tkd/$$Ifl4VF\#%; e&6    4 laf4pTTT U Uxo $IfgdL $IfgdLBS $Ifgd%tkdׅ$$Ifl4F\#%; e&6    4 laf4p U UUUUxo $IfgdL $IfgdLBS $Ifgd%tkd$$Ifl4fF\#%; e&6    4 laf4pUUU@VDV>5, $Ifgdz $IfgdzL$$Eƀ^F  ..Ifgdztkd'$$Ifl4XF\#%; e&6    4 laf4pDVFVPVWWA8/ $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLrkdχ$$Ifl4F\#%;e&6    4 laf4pWWWWWzq $IfgdL $Ifgd( $Ifgd%rkdn$$Ifl4F\#%;e&6    4 laf4pWWXXX@7. $Ifgdz $IfgdzL$$Eƀ^F  ..Ifgdzrkd $$Ifl4F\#%;e&6    4 laf4pXXXY@7 $IfgdzL$$Eƀ^F  ..Ifgdzrkd$$Ifl4F\#%;e&6    4 laf4pY5YHYJYi` $IfgdzJ$Eƀ^FIfgdzJ$Eƀ^FIfgdzJYKYPYYYA8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdK$$Ifl4F\#%;e&6    4 laf4pWYYYY*Z7ZpZZZZZZZZZZZ[[J]K]]]S^]^^^^^^E_F_G_H_J__`ccncocpcqc}cccccdd7e8eJeKe̵̵̵̹̦̟̗jFhUMUh:jh:U hhjCh#5h.MUhhhCh.MhX> h#5hX> h#5h h#5h%h#5h~(mHnHuh#-h#5h~(CJaJh~( h#5h~(5YYYZZzq $IfgdL $Ifgd( $Ifgd%rkd$$Ifl4F\#%;e&6    4 laf4pZZZ[[A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkd$$Ifl4F\#%;e&6    4 laf4p[[[\\zq $IfgdL $Ifgd( $Ifgd%rkd($$Ifl4F\#%;e&6    4 laf4p\\\G]I]A8/ $IfgdL $Ifgd(J$Eƀ^F ..IfgdLrkdnj$$Ifl4F\#%;e&6    4 laf4pI]J]K][]\]zq $IfgdL $Ifgd( $Ifgd%rkdf$$Ifl4F\#%;e&6    4 laf4p\]]]b]]]@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkd$$Ifl4F\#%;e&6    4 laf4p]]]_`raFAAAgd;"FEƀ^F .gd2rkd$$Ifl4F\#%;e&6    4 laf4praaKbLcpcs-(gd;"FEƀ^Fgd#5FEƀ^Fgd#5FEƀ^Fgd#5pcrc~ccccccRykd$$Ifl44F^#%<g&6    4 laf4g9p $$Ifa$gdg $Ifgd9T $If^gdggd;"gd'p$a$gd%>ccddd)wkd$$Ifl4F^#%<g&6    4 laf4g9p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzddg g g)wkd$$Ifl4F^#%<g&6    4 laf4g9p $Ifgdz $IfgdzL$$Eƀ^F ..IfgdzKeffff fFfqhrh-i4illvswssssttttltrttzw{www {>{A{O{S{U{Y{{{||}} hlDFdfhtv翸縴jh=Uh#5h=CJaJ h#5h=h= h#5h%h#5hhn&jhU h#5hTbh#5hCJaJh h#5hhLw hLwjh:U< ggnhphqh*wkd^$$Ifl4F^#%<g&6    4 laf4g9p $IfgdL $Ifgd(J$Eƀ^F ..IfgdLqhrh&i-i@iWJ$Eƀ^FIfgd;"J$Eƀ^FIfgd;" $Ifgd;" $Ifgd%@iUifiiiJ$Eƀ^FIfgd;"J$Eƀ^FIfgd;"J$Eƀ^FIfgd;"iiii3wkd$$Ifl4F^#%<g&6    4 laf4g9p $IfgdLJ$Eƀ^FIfgd;"iijjj)wkd$$Ifl4F^#%<g&6    4 laf4g9p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzjjjk_J$Eƀ^FIfgdz $IfgdzL$$Eƀ^F ..IfgdzkxkkkiJ$Eƀ^F IfgdzJ$Eƀ^F IfgdzJ$Eƀ^F Ifgdzkkkkl~3* $Ifgd(J$Eƀ^F ..IfgdLwkdY$$Ifl4F^#%<g&6    4 laf4gGp $Ifgdzllllll~ul $Ifgd( $Ifgd%wkd$$Ifl4F^#%<g&6    4 laf4g9p $IfgdLlllmm;2) $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzwkd$$Ifl4F^#%<g&6    4 laf4g9pmmmm;2 $IfgdzL$$Eƀ^F ..IfgdzwkdT$$Ifl4F^#%<g&6    4 laf4g9pmDnnniJ$Eƀ^FIfgdzJ$Eƀ^F IfgdzJ$Eƀ^F Ifgdznnnnp~2) $IfgdzL$$Eƀ^F  ..Ifgdzwkd$$Ifl4F^#%<g&6    4 laf4g9p $Ifgdzp#pYp~piJ$Eƀ^FIfgdzJ$Eƀ^FIfgdzJ$Eƀ^FIfgdz~ppppiJ$Eƀ^FIfgdzJ$Eƀ^FIfgdzJ$Eƀ^FIfgdzpq q.qiJ$Eƀ^FIfgdzJ$Eƀ^FIfgdzJ$Eƀ^FIfgdz.qIqKqLq3wkd$$Ifl4F^#%<g&6    4 laf4g9p $IfgdzJ$Eƀ^FIfgdzLqQq rrr)wkdO$$Ifl4F^#%<g&6    4 laf4g9p $Ifgdz $IfgdzL$$Eƀ^F  ..Ifgdzrrssusvs/rkd$$Ifl4F^#%<g&6    4 laf4p $IfgdL $Ifgd(J$Eƀ^F  ..IfgdLvswsntptrtqrkd$$Ifl4F^#%<g&6    4 laf4p $IfgdL $Ifgd( $Ifgd%rtt7vwwwy {nigd9TFEƀ^F .gd2gd;"FEƀ^F .gd2 {>{B{O{T{ $$Ifa$gdg $Ifgd9T $If^gdgFEƀ^F .gd2T{U{Z{{{@7. $Ifgdg $IfgdgJ$Eƀ^F ..Ifgdgtkd6$$Ifl44F\#5&;&6    4 laf4p{{{||zq $Ifgdg $Ifgdg $Ifgd%rkdޯ$$Ifl4F\#5&;&6    4 laf4p|||}}A8/ $Ifgdg $IfgdgJ$Eƀ^F ..Ifgdgrkd}$$Ifl4F\#5&;&6    4 laf4p}}}  zq $Ifgdg $Ifgdg $Ifgd%rkd$$Ifl4F\#5&;&6    4 laf4p  A8/ $Ifgdg $IfgdgJ$Eƀ^F ..Ifgdgrkd$$Ifl4F\#5&;&6    4 laf4pz/J$Eƀ^FIfgd;" $Ifgd;" $Ifgd%rkdZ$$Ifl4F\#5&;&6    4 laf4pfgi` $IfgdgJ$Eƀ^FIfgd;"J$Eƀ^FIfgd;"ghm@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkd$$Ifl4F\#5&;&6    4 laf4p?@7 $IfgdzL$$Eƀ^F ..Ifgdzrkd$$Ifl4F\#5&;&6    4 laf4p?M]hiJ$Eƀ^FIfgdzJ$Eƀ^FIfgdzJ$Eƀ^FIfgdzhpi` $IfgdzJ$Eƀ^F IfgdzJ$Eƀ^FIfgdzz~A8/ $Ifgdg $IfgdgJ$Eƀ^F ..Ifgdgrkd7$$Ifl4F\#5&;&6    4 laf4p~ zq $Ifgdg $Ifgdg $Ifgd%rkdִ$$Ifl4F\#5&;&6    4 laf4p"*ƃԄ&(*68<>\^`nprtv҅ԅօcdAEˆÈRVjrFHfhjvx}!"ABRS >@Һɺɺjh=U h#5h;HhLw hLwh;Hjh;HUh#5h=CJaJh=h#5h=mHnHu h#5h=I ",@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkdu$$Ifl4F\#5&;&6    4 laf4pȃA8/ $Ifgdg $IfgdgJ$Eƀ^F ..Ifgdgrkd$$Ifl4F\#5&;&6    4 laf4pzq $Ifgdg $Ifgdg $Ifgd%rkd$$Ifl4F\#5&;&6    4 laf4p@7. $Ifgdz $IfgdzL$$Eƀ^F  ..IfgdzrkdR$$Ifl4F\#5&;&6    4 laf4p`bA8/ $Ifgdg $IfgdgJ$Eƀ^F  ..Ifgdgrkd$$Ifl4F\#5&;&6    4 laf4pbcd?@zq $Ifgdg $Ifgdg $Ifgd%rkd$$Ifl4F\#5&;&6    4 laf4p@AFA8/ $Ifgdg $IfgdgJ$Eƀ^F  ..Ifgdgrkd/$$Ifl4F\#5&;&6    4 laf4pˆÈPQzq $Ifgdg $Ifgdg $Ifgd%rkdι$$Ifl4F\#5&;&6    4 laf4pQRWdh@7. $Ifgdz $IfgdzL$$Eƀ^F  ..Ifgdzrkdm$$Ifl4F\#5&;&6    4 laf4phjt@7 $IfgdzL$$Eƀ^F  ..Ifgdzrkd $$Ifl4F\#5&;&6    4 laf4p~ƋiJ$Eƀ^F#IfgdzJ$Eƀ^F"IfgdzJ$Eƀ^F!IfgdzƋz|i` $IfgdzJ$Eƀ^F%IfgdzJ$Eƀ^F$Ifgdz|}!A8 $Ifgd;"J$Eƀ^F ..Ifgdgrkd$$Ifl4F\#5&;&6    4 laf4p!ARiJ$Eƀ^F(Ifgd#5J$Eƀ^F'Ifgd#5J$Eƀ^F&Ifgd#5zq $Ifgdg $Ifgd%rkdJ$$Ifl4F\#5&;&6    4 laf4p $Ifgdg@BNPr~tu<>@NP tx 9:Қ֚.HLߞ»»h#5h6]hCh#5h\aJ h#5h h#5h%h#5h=B*phh#5h=CJaJhth= h#5h=jh=UhLw hLw=@7. $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzrkd$$Ifl4F\#5&;&6    4 laf4pA8/ $Ifgdg $IfgdgJ$Eƀ^F ..Ifgdgrkd$$Ifl4F\#5&;&6    4 laf4p zq $Ifgdg $Ifgdg $Ifgd%rkd'$$Ifl4F\#5&;&6    4 laf4p  ƔA8 $Ifgd;"J$Eƀ^F ..Ifgdgrkdƾ$$Ifl4F\#5&;&6    4 laf4pƔ.iJ$Eƀ^F+Ifgd;"J$Eƀ^F*Ifgd;"J$Eƀ^F)Ifgd;".=/rkde$$Ifl4F\#5&;&6    4 laf4p $Ifgdg $Ifgd;"J$Eƀ^F,Ifgd;"qrkd$$Ifl4F\#5&;&6    4 laf4p $Ifgdg $Ifgdg $Ifgd%qst.rkd$$Ifl4F\#5&;&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdzty/rkdB$$Ifl4F\#5&;&6    4 laf4p $Ifgdg $IfgdgJ$Eƀ^F ..Ifgdg~qrkd$$Ifl4F\#5&;&6    4 laf4p $Ifgdg $Ifgdg $Ifgd%   .rkd$$Ifl4F\#5&;&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdz .rkd$$Ifl4F\#5&;&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdz689/rkd$$Ifl4F\#5&;&6    4 laf4p $Ifgdg $IfgdgJ$Eƀ^F ..Ifgdg9:КњҚqrkd]$$Ifl4F\#5&;&6    4 laf4p $Ifgdg $Ifgdg $Ifgd%Қך.rkd$$Ifl4F\#5&;&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdz.rkd$$Ifl4F\#5&;&6    4 laf4p $Ifgdz $IfgdzL$$Eƀ^F ..Ifgdz2nFEƀ^F-gd#5gd;"FEƀ^F .gd22\s-FEƀ^F0gd#5FEƀ^F/gd#5FEƀ^F.gd#5&ڟ uآ+u@gd@2rgd;"FEƀ^F .gd2$%&SXڟ۟   tuvv~آùããqj>h@2rhD&"Uh#5h6jh@2rhD&"UjFh@2rhD&"Uh#5h]jh@2rhD&"Uh#5h6] h#5h h@2rhh@2rh0J>*OJQJj:h@2rhD&"U h@2rhw jh@2rhw U,)*+ۤܤЦѦҦԦئ[\z{|/0189:@Aõحßؗwߌh_h@2rh0Jh@2rh0J5B*phjh@2rhD&"U h@2rhcjh@2rhcUh#5h\j@h@2rhD&"Uh#5h6jh@2rhD&"U h@2rhw h#5h6]hQE h#5h h@2rhjh@2rhw Uh@2rh0J>*OJQJ%@ѥҦ[AȩZ%gFEƀ^F1gd#5gdcz\gdFgd@2rgd;"&Z[wxyֱ̱رٱbwƳƸͪͣƕͪͣƇͣxpfh#5h6]hTh5hTh0J5B*phj"h@2rhD&"Ujh@2rhD&"U h@2rhh@2rh0J>*OJQJj0h@2rhD&"U h@2rhcjh@2rhcUh#5h6 h#5hh#5h^QmHnHuh#5hmHnHu'(ds-(gdFFEƀ^F4gd#5FEƀ^F3gd#5FEƀ^F2gd#5HV{s-FEƀ^F7gd#5FEƀ^F6gd#5FEƀ^F5gd#5{s-(gd@2rFEƀ^F:gd#5FEƀ^F9gd#5FEƀ^F8gd#5رRسȴ,S~Ejշ:/Ugd@2rgdcz\gdFƳdzȳֳ׳س;Bƴߴ*+,HMShSTqrs|}~ʸʴ榘ʐʐ概tj0h@2rhD&"Ujh@2rhD&"Uh#5h6jh@2rhD&"U h@2rhc h#5hthth#5h]h#5h6] h#5h h@2rhh@2rh0J>*OJQJjh@2rhcUjh@2rhD&"U,<CEF`abhijv̷ӷշַ-./89:ؿؿ渪ؿؘؿ渊|ؿؿjh@2rhD&"Ujh@2rhD&"Uhlh@2rh0J>*OJQJjh@2rhD&"U h@2rhch#5h6]h@2rh0J5B*ph h#5h h@2rhjh@2rhcUjh@2rhD&"U-X\efg$%&/01"#+,OPklڠ~zszejh5hD&"U h#5hthtjuh5hD&"Uh#5hh{?h5hh{?jh5hD&"UhFh0J h5hh5h0J>*OJQJjsh5hD&"U h5hcjh5hcUh' h#5hh#5h]'U8;snngdFFEƀ^F<gd#5FEƀ^F;gd#5;\fs-(gd5FEƀ^F?gd#5FEƀ^F>gd#5FEƀ^F=gd#51 2Ov 9DCzgdcz\gd5gdFlmtuv  *+,789ip|123;<=Cǹǫاǒ؃h0/HhTh0J5B*phjch5hD&"U h#5hthtjh5hD&"Ujgh5hD&"U h5hch#5h6] h#5h h5hh5h0J>*OJQJjh5hcU1234ABCMV QUg~rih%>^mHnHuh#5hmHnHujYh5hD&"U h5hh5h0J>*OJQJjh5hD&"U h5hcjh5hcUh#5h$W06] h#5h$W0 h$W06 hl6h#5h6]h#5h6 h#5hh0/H h#5h0/H'+fxs-FEƀ^FBgd#5FEƀ^FAgd#5FEƀ^F@gd#5xs-FEƀ^FEgd#5FEƀ^FDgd#5FEƀ^FCgd#5h 0{ p.T,$gd*ugd5gdFFEƀ^FFgd#5gh{|^opq,-.06CM38E|hfZahfZamHnHuhljUh5hD&"Ujh5hD&"UjCh5hD&"Uh#5h6] h5hh5h0J>*OJQJjh5hD&"U h5hcjh5hcU h#5hh0EIJKz{ Zbde~-.6quĽĨәӑӑĽĨәӑxӑӑĽjjh5hD&"U h#5h0/Hh0/Hj7h5hD&"Uh#5h6hTh0J5B*ph h5hjh5hD&"U h5hcjh5hcUh h#5hh#5h6]h%>^6]mHnHuh#5h6]mHnHu), d:kFEƀ^FGgd#5gdGgdpFgd5gdcz\gdF !$-28 !"(27v{"#$*+,0?@غؖؖ~~p~jh5hD&"Uh#5h6]jh5hD&"UhTh0J5B*phj#h5hD&"U h5hch#5h5\h#5hmHnHuh#5h6 h#5h h5hh5h0J>*OJQJjh5hcU, ls-FEƀ^FJgd#5FEƀ^FIgd#5FEƀ^FHgd#5l)9,@gr Edgd%=gd5gd(ZgdGgdcz\FEƀ^FKgd#5@A\]^efg)Wrs78@AEdeƿƿƿƿxpbjfh5hD&"Uh#5h] h#5h0/Hh0/H h#5h h5hh5h0J>*OJQJjh5hD&"U h5hcjh5hcU h%=h%=h%= h2>h%=h2>h%=0J>*OJQJjzh2>h2>U h2>h2>jh2>h2>U&e^wx`fĺĺĺĺĺĔҔwwĔijBh5hD&"Uh#5h6jh5hD&"U h5hjh5hUh#5hhs6]jbh5hD&"Uh#5h6] h#5h h5hh5h0J>*OJQJjh5hcUjh5hD&"U h5hc)G(NmQs?@vgd5gdSNOfghklmQRjklqrs(-=>?rػشўؔц~ػvh#5h5h#5h]jh5hD&"Uh#5h6]j(h5hD&"UhI.h0/H hhh0/Hh#5h6jh5hD&"U h5h h#5h h5hh5h0J>*OJQJjh5hU.rw   3Efjfl?CGLPTVWq۸۱ԛ۸۱ԃ۸۱jh5hD&"Uh#5h6]jh5hD&"Uh#5h6 h5hh5h0J>*OJQJjh5hD&"U h5hjh5hUh#5h5 h#5h h#5h0/Hh0/H0V/Sd.Sr$V> k.[gdugd5gd(ZgdSqrsyz{FGOPLWo,./IJKQRSžشجججج楗ججج{شj{h5hD&"Uh5h0J>*OJQJjh5hD&"U h5hh#5h6h#5h6] h#5h0/Hh0/HhTh0J5B*ph h#5h h5hjh5hUjh5hD&"U0"$%BCDMNOU\bpv-2: 4:ݘ|jh5hD&"Uh5h0J>*OJQJjgh5hD&"Uh#5h6 h#5h0/Hh0/Hh@h0J5B*ph h5hjh5hD&"U h5hjh5hUh#5h6] h#5h0#,./MNOYZ[;<=FGH]dgq  &'(123FJݬ݉{jh5hD&"UjMh5hD&"U h0/H]h#5h6h#5h]jh5hD&"U h5hh5h0J>*OJQJjYh5hD&"U h5hjh5hUh#5h6] h#5h0H# 3wiFEƀ^FMgd#5FEƀ^FLgd#5gdSgd5 T[123789$+.:-:>RSk淰ע昐ׂj_h5hD&"Uh#5h]h#5h6]jh5hD&"U h#5h0/Hh0/Hh5h0J>*OJQJjih5hD&"U h5hh#5h6 h#5h h5hjh5hU.9eRs.^! Oggd(Zgd5gdSklmqrs./KLMUVW]}JOWmõçʘʎʆʎʂ{ʎʎʎmjCh5hD&"U h#5h0/Hh0/Hh#5h6h#5h6]h@h0J5B*phjh5hD&"UjWh5hD&"U h5h h#5h h5hh5h0J>*OJQJjh5hUjh5hD&"U*GH  !@ABOPT[aeghõحإححtحjh5hD&"U&jh5B*OJQJU\phj+hD&"UhjhUh#5h6jh5hD&"U h5hhh#5h6] h#5h h5hh5h0J>*OJQJjh5hU-g46h 1No  B gda1FEƀ^F .gd2gdSgd5 %*2hp%,]fhi   '()/01DHLoߙ߁}hV$jh5hD&"Uh#5h5\jh5hD&"U h#5h0/Hh0/Hh#5h6] h5hh5h0J>*OJQJjh5hD&"U h5hjh5hUh#5h6 h#5h.o     B C O   VWXcyz:;de%0##67 8 899!:#:(:*::::0;ĽШh h#5hh]h#5h'5 h#5h'h#5hh y^jh#5hU hPhjh*uUhGD hjh#5hUh?h+3 h#5ha1ha1 h#5h h#5h%3B D P VXd% r?gd9TFEƀ^F .gd2$a$gdgdS$a$gdugda1gd'p$a$gda1?Yos-(gdSFEƀ^FPgd#5FEƀ^FOgd#5FEƀ^FNgd#5siFEƀ^FRgd#5FEƀ^FQgd#5gdSgd9TiFEƀ^FTgd#5gd9TgdSFEƀ^FSgd#5 mH !!""#gd9TgdSFEƀ^FUgd#5##$$&&&'nFEƀ^FVgd#5gdSFEƀ^F .gd2'G(()+s-(gdSFEƀ^FYgd#5FEƀ^FXgd#5FEƀ^FWgd#5+,C..0f1(22t4#55688 9FEƀ^FZgd#5gdS 9929;9s-FEƀ^F]gd#5FEƀ^F\gd#5FEƀ^F[gd#5;9L9]9i9!:s-(gdSFEƀ^F`gd#5FEƀ^F_gd#5FEƀ^F^gd#5!:":#:):*:3:>:S:ma $$Ifa$gd2gxkdg$$Ifl440%   U   0E&4 laf4 $$Ifa$gda1 $Ifgd2ggd]S:T:U:^:g:n:|:::vjaaaaaa $Ifgd2g $$Ifa$gd2gkd<$$Ifl44F%`  '   .   0E&    4 laf4:::::::NB6666 $$Ifa$gdW $$Ifa$gd2gkdZ$$Ifl44r %           0E&4 laf4:::::::QE9999 $$Ifa$gdW $$Ifa$gd2gkd$$Ifl4r %   0E&4 laf4:::::::QE9999 $$Ifa$gdW $$Ifa$gd2gkd̆$$Ifl4r %  0E&4 laf4::";%;(;,;0;QE9999 $$Ifa$gdW $$Ifa$gd2gkd$$Ifl4r %  0E&4 laf40;1;>;A;D;H;L;QE9999 $$Ifa$gdW $$Ifa$gd2gkd $$Ifl4r %  0E&4 laf40;1;L;M;m;n;;;;;;;<<<<=<l<m<<<<<==B=C=g=h======>>>>>>>>>??I?J?n???@@@\@]@@@@@@@@@A AwAŭh#5h(Skhh$h$0Jjhs`;Uh$jh$Uh#5h%CJhh uh(SkCJaJ h uh% h#5h' h#5h%h#5h%\>L;M;^;b;e;i;m;QE9999 $$Ifa$gdW $$Ifa$gd2gkd,$$Ifl4r %  0E&4 laf4m;n;;;;;;QE9999 $$Ifa$gdW $$Ifa$gd2gkdL$$Ifl4r %       0E&4 laf4;;;;;;;QE9999 $$Ifa$gdW $$Ifa$gd2gkdl$$Ifl4r %  0E&4 laf4;;;;;;;QE9999 $$Ifa$gdW $$Ifa$gd2gkd$$Ifl4r %  0E&4 laf4;;<<<<<QE9999 $$Ifa$gdW $$Ifa$gd2gkd$$Ifl4r %  0E&4 laf4<<.<1<4<8<<<QE9999 $$Ifa$gdW $$Ifa$gd2gkd̏$$Ifl4r %  0E&4 laf4<<=<]<`<d<h<l<QE9999 $$Ifa$gdW $$Ifa$gd2gkd$$Ifl4r %  0E&4 laf4l<m<<<<<<QE9999 $$Ifa$gdW $$Ifa$gd2gkd $$Ifl4r %       0E&4 laf4<<<<<<<QE9999 $$Ifa$gdW $$Ifa$gd2gkd,$$Ifl4r %  0E&4 laf4<<== ===QE9999 $$Ifa$gdW $$Ifa$gd2gkdL$$Ifl4r %  0E&4 laf4==5=8=;=>=B=QE9999 $$Ifa$gdW $$Ifa$gd2gkdl$$Ifl4r %       0E&4 laf4B=C=[=^=a=d=g=QE9999 $$Ifa$gdW $$Ifa$gd2gkd$$Ifl4r %  0E&4 laf4g=h======QE9999 $$Ifa$gdW $$Ifa$gd2gkd$$Ifl4r %  0E&4 laf4=======QE9999 $$Ifa$gdW $$Ifa$gd2gkd̘$$Ifl4r %  0E&4 laf4==0>3>6>9>=>QE9999 $$Ifa$gdW $$Ifa$gd2gkd$$Ifl4r %  0E&4 laf4=>>>r>v>z>~>>QE9999 $$Ifa$gdW $$Ifa$gd2gkd $$Ifl4r %  0E&4 laf4>>>>>>>QE9999 $$Ifa$gdW $$Ifa$gd2gkd,$$Ifl4r %  0E&4 laf4>>>>>>>QE9999 $$Ifa$gdW $$Ifa$gd2gkdL$$Ifl4r %  0E&4 laf4>>? ? ???QE9999 $$Ifa$gdW $$Ifa$gd2gkdl$$Ifl4r %  0E&4 laf4??:?=?A?E?I?QC5555 $$$Ifa$gdW $$$Ifa$gdidkd$$Ifl4r %  0E&4 laf4I?J?n?????QLGB99 $Ifgdggd]gd ugd ukd$$Ifl4r %       0E&4 laf4?@@@kN & F$Eƀ^F[]Ifgd]kd̡$$Ifl44F '% 0r6    4 laf4 $Ifgdg@\@@@akd=$$Ifl4F '% 0r6    4 laf4 $Ifgd] $$Ifa$gd3@@AA $Ifgd] $$Ifa$gd3N & F$Eƀ^F[]Ifgd%wAxAyAAAAAAvBwBBBBBBBBBBB2C3CZC[C\CuCvCwCxCyCCCCC&D'Dܵܫܣ쟔ܣ܀sjZjThhU^Jh(Skh$^Jjh(Skh$U^JhfZah%mH sH h$h$0Jjhs`;Uh$h#5h(Skhh#5h%h jhUjh#5h%Uh#5h%CJh h#5h(Sk h#5h%h$h%0Jjh$Ujhs`;U#AAAJBv( $$Ifa$gd3N & F$Eƀ^F[]Ifgd%kd$$Ifl4F '% 0r6    4 laf4JBBBBmN & F$Eƀ^F[]Ifgd%kdK$$Ifl4F '% 0r6    4 laf4 $Ifgd]B2CwCxCakd$$Ifl4F '% 0r6    4 laf4 $Ifgd] $$Ifa$gd3xCyCCKD $Ifgd] $$Ifa$gd3N & F$Eƀ^F[]Ifgd%'D(DHDIDJDKDLDMDkDnDDEEhEiEjEEEEEEEEEEEEEFFRFSFü|ldüWjh(Skh(SkU^Jh$B*phhfZahfZa0J^JmHnHu(jhhB*U^Jphh(Skh$B*^Jph"jh(Skh$B*U^JphhGB*phh' h#5h%h#5h%CJhh#5h(Skhh(Skh%^Jh(Skh$^Jh(Skh$0J^Jjh(Skh$U^JKDLDMDDv( $$Ifa$gd3N & F$Eƀ^F[]Ifgd%kd$$Ifl4F '% 0r6    4 laf4DEEEmkd$$Ifl4F '% 0r6    4 laf4 $Ifgd]EERFF $Ifgd] $$Ifa$gd3N & F$Eƀ^F[]Ifgd%SFFFFFFFFF\\\\]^^\FEƀ^Ffgd]FEƀ^Fegd] gd0o${F$a$gd0gd]^^ _#`n(FEƀ^Fggd]KEƀ^Fgd0o%{FFEƀ^Fgd0#`aadds-(gd]FEƀ^F gd]FEƀ^F gd]FEƀ^F gd]dNeleyeeeeeeSkd$$Ifl0/ / & t644 lal $Ifgd$#gdM gd$#gd]eeeeeDDPSkd$$Ifl0/ / & t644 lal $Ifgd$#Skdf$$Ifl0/ / & t644 lalellSerco ConsultingMs Alayne CrozierSerco ConsultingMr Steve DaviesSerco ConsultingMr John DeverillSerco ConsultingMr Marc FreskoSerco ConsultingMr Michael HaimerlImbus AG (testing partner)Mr Tilo LinzImbus AG (testing partner)Mr Wasif MehdiSerco ConsultingMr Thomas RumiImbus AG (testing partner)Mr Josephus SchramEuropean Commission (Project Officer)Mr John SeeleySerco ConsultingMs Caroline SeniorSerco ConsultingMr Michael SillImbus AG (testing partner)Ms Natasha SmithSerco ConsultingThe project team wishes to express its thanks to Mr John Worsfold of the Royal National Institute of Blind People (UK) for assisting with the requirements concerning accessibility. Editorial Board The Project Team was advised and guided by the following Editorial Board, constituted of international experts. Mr Miguel CamachoSadiel S.A, SpainMs Marie-Anne ChabinArchive 17, FranceMs Anne Mette DrumNational Archives of Norway, Records Management Department, NorwayProfessor Luciana DurantiSchool of Library, Archival and Information Studies, University of British Columbia, CanadaProfessor Mariella GuercioUniversity of Urbino, ItalyMr Peter HorsmanArchiefschool (Netherlands Institute for Archival Education and Research), The NetherlandsDr Ulrich KampffmeyerPROJECT CONSULT Unternehmensberatung GmbH, GermanyMr Paul MurphyMinistry of Finance, IrelandDLM Forum The DLM Forum provided a Review Group to review drafts on behalf of the European Commission. Mr Richard BlakeUKMs Dolores Carnicer ArribasSpainMr Olivier de SolanFranceDr Andrea HngerGermanyMs Paivi HapponenFinlandMr Toivo JullinenEstoniaMr Gran KristianssonSwedenMr Ian MacFarlaneUKMr Atle SkjekkelandSecretariatMr Jo~e `kofljanecSloveniaMr Malcolm Todd (chair)UKMr Martin WaldronUKReview panellists The project team is extremely grateful to the following individuals and companies who kindly volunteered and devoted considerable amounts of time to participate in the review and validation exercise. Their valuable input into MoReq2 has ensured that the specification can address the needs of the widest community of users. Mr Francisco BarbedoArchives PanelInstituto dos Arquivos Nacionais/Torre do Tombo, PortugalMr. Jan Dalsten SrensenArchives PanelDanish National ArchivesMs Inta FeldmaneArchives PanelNational Archives of Malta Mr Hkan LvbladArchives PanelRiksarkivet/National Archives, SwedenMr. Michal WannerArchives PanelDepartment of the Archives Administration and Records Management, Czech RepublicMr Sergey AfanasievSpecialists PanelRecords Managers Guild, RussiaMs Phdra ClounerSpecialists Paneldocument@work, BelgiumMr Michiel GenSpecialists PanelARMA International, BelgiumMs Kimberley BarataUsers PanelParliamentary Archives, UKMs Kathy BashaarUsers PanelPNC Bank, USAMr Daniel J BeardUsers PanelXerox Corp, USAMs Alissa BurgerUsers PanelRail Corp, Information and Records Management, AustraliaMr Barry CahillUsers PanelNova Scotia Archives & Records Management Department of Tourism Culture & Heritage,CanadaMr Llus-Esteve Casellas SerraUsers PanelAjuntament de Girona. SGDAP, SpainMr Alejandro Delgado GmezUsers PanelServicio de Archivo y Bibliotecas del Ayuntamiento de Cartagena Archivo Municipal parque de Artilleria, SpainMr Paul DodgsonUsers PanelLeicestershire County Council, UKMs Susan EmUsers PanelRoyal Pharmaceutical Society of GBMs Trish FallenUsers PanelInformation Management Practitioner, AustraliaMs Lucia Filimon StefanUsers PanelJoint Research Centre of the European Commission, ItalyMs Fiorella FoscariniUsers PanelEuropean Central Bank, GermanyMs Alison Gibney Users PanelCimtech, UKMr Stefan GradmannUsers PanelUniversitt Hamburg, GermanyMs Frances GreyUsers PanelParliamentary Archives, UKMr Harold C Heard Jr.Users PanelCitigroup, USAMs Sarah HigginsUsers PanelDigital Curation Centre, University of Edinburgh, UKMrs Caroline IvesUsers PanelSalford City Council, UKMr Philip JonesUsers PanelStaffordshire County Council, UKMr Ben KettellUsers PanelCactus Tecnologia, SpainMs Natasha KhramtsovskyUsers PanelElectronic Office Systems, RussiaMr Stewart KirkupUsers Panel Derbyshire County Council, UKMr Pivi LaaksoUsers PanelNational Agency for Medicines, FinlandMs Jessica LilaUsers PanelUSAMr Stephen MacintoshUsers PanelFederal Court of AustraliaMs Snia Oliveras ArtauUsers PanelAjuntament de Girona. SGDAP, SpainMr Matt OMaraUsers PanelMr Adam PopeUsers PanelInformation Handy Man, UKMs Barbara ReedUsers PanelRecordkeeping Innovation, AustraliaDr David ReeveUsers PanelDorset County Council, UKMs Maria Reixach UrcolaUsers PanelAjuntament de Girona. SGDAP, SpainMr Jordi Serra SerraUsers PanelGeneralitat de Catalunya, SpainMs Deirdre SharpUsers PanelNorfolk County Council, UKMr Alan ShipmanUsers PanelGroup 5 Training, UKMs Marija `imunoviUsers PanelSupreme Court of the Republic of CroatiaMr Sundeep VaidUsers PanelInternational Fund for Agricultural Development, ItalyMr Peter Van GarderenUsers PanelArtefactual Systems, CanadaMr Willem VannesterUsers PanelStadsarchief Antwerpen, BelgiumMr Grard WeiszUsers PanelSirius Systems, FranceMr Martin BartonitzVendors PanelSAPERION, GermanyMr Solomon Barron Vendors PanelIBM, UKMr Martin Bould Vendors PanelErgoGroup AS, NorwayMr Reynolds Cahoon Vendors PanelLockheed Martin, USAMr Ian Capon Vendors PanelOpen Text Corporation, UKMr Simon Cole Vendors PanelMeridio, UKMr Jon GardeVendors PanelObjective Corporation, UKMr Graham Hadingham Vendors PanelFileNet, UKMr Joachim Haessler Vendors PanelHaessler Information, GermanyMs Tamara Hoagland Vendors PanelEDRM Solutions, USAMr Mike Huberty Vendors PanelLockheed Martin, UKMr Chris Hughes Vendors PanelTower Software, UKDr Gregor Joeris Vendors PanelSER Solutions Deutschland, GermanyMr Volker JohnVendors PanelSAPERION, GermanyDr Annegret Kampe Vendors PanelDocuware, GermanyMs Mary Kelly Vendors PanelIBM, UKMr Andy King Vendors PanelGetronics, UKMs Karen McKenzie Vendors PanelUK SoftwareMr Chris Palmer Vendors PanelCA, UKMs Shaheen Ramdiane Vendors PanelOpen Text CorporationMr Miroslav irl Vendors PanelICZ, Czech RepublicMr Andrew Snowden Vendors PanelFujitsu, UKMr Dan Taillefer Vendors PanelEMC, CanadaMr Nigel WoodVendors PanelFabasoft, UKTrademarks All trademarks appearing in this specification are acknowledged. Proprietary products are mentioned for illustrative purposes only; their inclusion does not represent any form of endorsement. Similarly, exclusion of other products implies no criticism of these products. Appendix 5 Correspondence to Other Models This appendix summarises how the metadata model specified in appendix 9 can be related to: ISO 23081 Metadata for records; ISO 15836 The Dublin Core metadata element set. ISO 23081 Metadata for Records The entities considered in MoReq2 can be mapped approximately to their equivalents in ISO 23081 as follows: MoReq2 entityISO 23081 entity sub-classComponent-RecordItemTransaction sequenceVolume File/folderSub-fileFile ClassSeriesClassification schemeArchive-ArchivesThese mappings are necessarily approximate. The metadata elements in the MoReq2 model each have a name consisting of two or three parts (as described in appendix 9.6). Wherever possible the second part of the name is taken from ISO 23081-2, but several have been developed for MoReq2, as shown in the following table: ISO 23081 Metadata Group2nd part of MoReq2 Element NameSource of nameIdentitysystem_identifierMoReq2system_identifier_renditionMoReq2DescriptionabstractISO 23081authorMoReq2classificationISO 23081copy_recipientMoReq2counter_signatureMoReq2dateMoReq2external_identifierMoReq2placeISO 23081recipientMoReq2senderMoReq2titleISO 23081Event planabstractMoReq2agentISO 23081dateISO 23081event_descriptionISO 23081event_triggerISO 23081periodMoReq2reminderMoReq2statusMoReq2volumeMoReq2Event historyabstractMoReq2dateISO 23081disposal_holdMoReq2transfer_or_destroyISO 23081transferred_toMoReq2UseadministratorMoReq2inactiveMoReq2languageISO 23081statusMoReq2technical_environmentISO 23081RelationagentMoReq2applies_to_agentMoReq2applies_to_classMoReq2cross_referenced_toMoReq2disposal_holdMoReq2entity_agentMoReq2has_redactionMoReq2has_roleMoReq2has_userMoReq2is_child_ofMoReq2is_member_ofMoReq2is_redaction_ofMoReq2is_parent_ofMoReq2previous_fully_qualified_classification_codeMoReq2r&d_scheduleMoReq2record_typeMoReq2 Further aspects of the correspondence between MoReq2 and ISO 23081 are in appendix9. ISO 15836 The Dublin Core metadata element set The elements defined in the Dublin Core can be mapped to the elements in the MoReq2 model as follows. Where only a partial MoReq2 element name is shown, it indicates all elements that start with this partial name. So for example Description.abstract indicates all of the following: Description.abstract; Description.abstract.keywords; Description.abstract.reason_for_rendition. Dublin Core ElementMoReq2 ElementcontributorDescription.sendercoverage-creatorDescription.authordateDescription.datedescriptionDescription.abstract.description Description.external_identifier.internal_referenceformatUse.technical_environment.format Use.technical_environment.file_formatidentifierIdentitylanguageUse.languagepublisher-relationRelationrights-source-subjectDescription.abstract.keywordtitleDescription.titletypeDescription.record_type-Description.abstract.mandate Description.abstract.reason_for_rendition Description.copy_recipient Description.place.current_location Description.place.home_location Description.recipient Event_history Event_plan Use.status Use.technical_environment (save as above) However, these mappings are necessarily approximate. Further aspects of the correspondence between MoReq2 and ISO 23081 are in appendix 9. Appendix 6 Date Processing The ERMS is required to process all dates correctly, regardless of millennium, century or other date representation issues. This appendix presents a statement of the requirement for year 2000 processing which could be adapted, if necessary, to deal with other dates. This will be especially relevant for Electronic Records Management Systems which may include metadata dates for previous or future centuries. The following is reproduced verbatim, with permission, from BSI DISC PD20001:1998 A Definition of Year 2000 Conformity Requirements. Year 2000 conformity shall mean that neither performance nor functionality is affected by dates prior to, during and after the year 2000. In particular: Rule 1 No value for current date will cause any interruption in operation. Rule 2 Date-based functionality must behave consistently for dates prior to, during and after year 2000. Rule 3 In all interfaces and data storage, the century in any date must be specified either explicitly or by unambiguous algorithms or inferencing rules. Rule 4 Year 2000 must be recognized as a leap year. Appendix 7 Standards and Other Guidelines 7.1 Standards This appendix lists standards and other resources referenced in the specification or applicable to electronic records management. The standards include those that are particularly relevant to ERMSs; they omit generic standards such as those dealing with storage hardware and database languages. The standards include international standards, both de jure and de facto. National standards are omitted from this list. They may be added to a chapter zero by the authority for a member state. Only standards that have a direct bearing on systems design are included; standards that address organisation and ongoing management are not included. In most cases, the short name of the standard (not the fully qualified name) is shown, for ease of understanding. FIPS 186-2NIST Digital Signature Standard ( HYPERLINK "http://csrc.nist.gov/publications/PubsFIPS.html" http://csrc.nist.gov/publications/PubsFIPS.html)ISAAR(CPF)International Standard Archival Authority Record for Corporate Bodies, Persons, and Families (International Council on Archives) ( HYPERLINK "http://www.ica.org/en/node/30230" http://www.ica.org/en/node/30230)ISAD(G)International Standard for Archival Description (General). ( HYPERLINK "http://www.icacds.org.uk/icacds.htm" http://www.icacds.org.uk/icacds.htm)IETF RFC 2821Simple Mail Transfer Protocol. HYPERLINK "http://www.ietf.org/rfc/rfc2821.txt"http://www.ietf.org/rfc/rfc2821.txt)IETF RFC 2822Internet Message Format. ( HYPERLINK "http://www.ietf.org/rfc/rfc2822.txt" http://www.ietf.org/rfc/rfc2822.txt)ISO 216Writing paper and certain classes of printed matter Trimmed sizes A and B seriesISO 639Codes for the representation of names of languages.ISO 2788Guidelines for the establishment and development of monolingual thesauri.ISO 5964Guidelines for the establishment and development of multilingual thesauri.ISO 8601Representation of dates and times.ISO 9834-8Procedures for the operation of OSI Registration Authorities: Generation and registration of Universally Unique Identifiers (UUIDs) and their use as ASN.1 Object Identifier components (see also ITU X.667).ISO/TS 12033Guidance for selection of document image compression methods.ISO/TR 12037Recommendations for the expungement of information recorded on write-once optical media.ISO 12142Media error monitoring and reporting techniques for verification of stored data on optical digital data disks.ISO/TR 12654Recommendations for the management of electronic recording systems for the recording of documents that may be required as evidence, on WORM optical disk.ISO 14721Open archival information system Reference model (OAIS).ISO/IEC 15444JPEG 2000 image coding system: Core coding system.ISO 15489Records Management.ISO/TR 15801Information stored electronically Recommendations for trustworthiness and reliability.ISO 15836The Dublin Core metadata element set.ISO 18492/TRLong-term preservation of electronic document-based information.ISO 19005-1Electronic document file format for long-term preservation Part 1: Use of PDF 1.4 (PDF/A-1).ISO 23081Metadata for records.ITU X.667Generation and registration of Universally Unique Identifiers (UUIDs) and their use as ASN.1 object identifier components. ( HYPERLINK "http://www.itu.int/ITU-T/studygroups/com17/oid/X.667-E.pdf" http://www.itu.int/ITU-T/studygroups/com17/oid/X.667-E.pdf).TIFFTagged Image File Format. ( HYPERLINK "http://partners.adobe.com/public/developer/tiff/index.html" http://partners.adobe.com/public/developer/tiff/index.html)X.509ITU-T Recommendation X.509: Open systems interconnection The Directory: Public-key and attribute certificate frameworks. ( HYPERLINK "http://www.itu.int/rec/T-REC-X.509-200003-I/en" http://www.itu.int/rec/T-REC-X.509-200003-I/en).XKMSXML Key Management Spec. ( HYPERLINK "http://www.w3.org/TR/xkms/" http://www.w3.org/TR/xkms/).XMLW3C Extensible Markup Language (XML) ( HYPERLINK "http://www.w3.org/TR/REC-xml/" http://www.w3.org/TR/REC-xml/) 7.2 Other Guidance ISO/DIS 9241-171Ergonomics of human-system interaction Part 171: Guidance on software accessibilityISO/TS 16071Guidance on accessibility for human-computer interfaces (due to be superseded by ISO 9241-171).WfMCWorkflow Management Coalition Terminology & Glossary. ( HYPERLINK "http://www.wfmc.org/standards/referencemodel.htm" http://www.wfmc.org/standards/referencemodel.htm) 1999/93/ECDirective on a Community Framework for Electronic Signatures. ( HYPERLINK "http://europa.eu/scadplus/leg/en/lvb/124118.htm" http://europa.eu/scadplus/leg/en/lvb/124118.htm) DLM Forum GuidelinesGuidelines on best practices for using electronic information. INSAR (European Archives News) Supplement III (1997). ISBN: 92-828-2285-0. ( HYPERLINK "http://dlmforum.typepad.com/gdlines.pdf" http://dlmforum.typepad.com/gdlines.pdf)7.3 Accessibility Guidelines and Resources This section lists guidelines and resources for developers and purchasers of ERMSs. Whereas other sections of this appendix contain only open and international publications, this section includes information that is originally national and that originates from the supplier community. This is because no internationally-accepted documentation has been identified; this may be added in any later editions of MoReq. For developersW3C Web Content Accessibility Guidelines (for websites and web applications) ( HYPERLINK "http://www.w3.org/WAI/" http://www.w3.org/WAI/) RNIB Web Access Centre ( HYPERLINK "http://www.rnib.org.uk/webaccesscentre" http://www.rnib.org.uk/webaccesscentre)RNIB Software Access Centre ( HYPERLINK "http://www.rnib.org.uk/softwareaccesscentre" http://www.rnib.org.uk/softwareaccesscentre) IBM Human Ability and Accessibility Centre ( HYPERLINK "http://www-03.ibm.com/able/guidelines/" http://www-03.ibm.com/able/guidelines/)ISO/IEC 18019 Guidelines for the design and preparation of user documentation for application software (see especially clause 4.2.6). (Due to be replaced by ISO/IEC 26514.)ISO/IEC 26514 User documentation requirements for documentation designers and developers. (Under development).For procurementACCENT Accessibility in ICT Procurement: EU project ( HYPERLINK "http://www.verva.se/english/international-network/the-accent-project/" http://www.verva.se/english/international-network/the-accent-project/)PAS 78:2006 A guide to good practice in commissioning accessible websites ( HYPERLINK "http://www.equalityhumanrights.com/en/publicationsandresources/Disability/Pages/Websiteaccessibilityguidance.aspx" http://www.equalityhumanrights.com/en/publicationsandresources/Disability/Pages/Websiteaccessibilityguidance.aspx) RNIB Software Access Centre ( HYPERLINK "http://www.rnib.org.uk/softwareaccesscentre" http://www.rnib.org.uk/softwareaccesscentre)7.4 Digital Preservation Guidelines InterPARES project ( HYPERLINK "http://www.interpares.org" http://www.interpares.org) Preserving Access to Digital Information (PADI) project National Library of Australia ( HYPERLINK "http://www.nla.gov.au/padi/" http://www.nla.gov.au/padi/)The National Archives Functional Requirements for the Sustainability of Electronic Records ( HYPERLINK "http://www.nationalarchives.gov.uk/documents/functional_requirements.pdf%20" http://www.nationalarchives.gov.uk/documents/functional_requirements.pdf)7.5 Graphical Model of Relationship of MoReq2 with Other Guidance This section contains a graphical model that shows how key standards are related to electronic records management. It uses a new model of electronic records management at figure A7.1, prepared only for this purpose.  Figure A7.1 The model shows key processes that affect electronic records. The records are represented by the central, grey, circle. The processes (create, capture etc.) are represented by the coloured shapes surrounding the records. The number of processes shown (the granularity, or level of detail of the model) is somewhat arbitrary. Several other representations are possible, and would be more appropriate for different purposes; the above has been chosen specifically to relate to standards. To interpret these processes: Create includes not only the creation of records within an organisation, but also receipt of records from outside the organisation. Capture includes the registration, classification, and the entry of records management metadata. Use includes search, retrieve, browse, render, maintain, review etc. Preserve is the processes required to maintain accessibility over time. Manage includes maintaining access controls and disposition authorities. The order of the processes shown is not significant, because they can occur in different sequences in different settings. Simplifying greatly, the key standards applying to electronic records management can be related to these processes as shown in figure A7.2.  Figure A7.2 The relationship shown above between the standards and processes is repeated at the end of this section in a form that does not require colour. This model traces the extent of the standards relevance very approximately using coloured lines superimposed on the processes. Each coloured line represents one or several standards. Where possible, the standards are shown by their common name (e.g. PDF/A, OAIS) rather than by their less-descriptive standard number (e.g. ISO 19005, ISO 14721); refer to section 1 of this appendix for formal titles. Note that any model of this kind can only give a rough indication it is not possible to show all details of all the interactions of processes and standards; to some extent the inclusions and omissions reflect a subjective view. Only the standards that are considered as the most important are included in this diagram; others are excluded. The criteria for inclusion and exclusion are judgemental. The model is explained below. Standards that are applicable across many processes are explained below, followed by the standards relevant to each of the processes. ISO 15489 and MoReq2 ISO 15489 and MoReq2 both cover the entirety of the processes affecting electronic records. Accordingly, they are shown as encircling all the processes. XML XML is shown as being relevant to almost all processes all except store and destroy. Its relevance varies greatly according to the environment. In principle however, it can influence the format of record creation then the way in which the metadata is stored and expressed at capture and during later use; it is an important standard facilitating the interpretation of metadata and content in long term preservation; it can be used to provide a common schema for transfers between systems; it can be used to describe access and schemas and disposition authorities. Metadata Metadata standards are relevant to the processes of capture, use, preserve, transfer and manage. These include ISO 23081 (which covers all aspects of records management metadata), Dublin Core (which specifies a standard set of metadata for discovery), ISO 639 (controlled vocabulary for language codes), ISAD and ISAAR (approaches to the use of metadata for record keeping and archival description) and ISOs 2788 and 5984 (thesaurus standards). Create The major standards consideration in the process of records creation is the format of the record. Many format standards exist, including RFCs 2821/2822 (for e-mail), ISO 216, TIFF and JPEG (for scanned images), and PDF/A. Capture Metadata standards of all kinds apply strongly to the capture process. Some of the format standards affecting capture are also relevant from the point of view of extracting metadata values automatically. Standards affecting legal issues also apply to capture, namely ISO 15801 and ISO 12654. Use The standard governing GUIDs (globally unique ids), X.667, affects the way electronic records are used, as do standards relating to legal issues, ISO 15801 and ISO 12654. Preserve The key standard for digital preservation is OAIS; this provides a framework for the design and management of preservation activities. ISO 18492 also provides general guidance. Most preservation work relies greatly on the use of metadata standards; and a key standard is PDF/A, which describes a preservation format. Standards for electronic signatures, X.509 and XKMS also have a bearing on preservation issues. Transfer The use of metadata standards is essential to transfers between organisations or between systems. Manage Metadata standards can support the processes of managing access and retention. Also relevant are the legal standards, ISO 15801 and 12654. Store ISO 12142 addresses a small aspect of storage, related to storage on optical discs. Destroy ISO 12037 addresses a small aspect of destruction, namely expungement; this is only relevant is some environments. The relationship between the standards and processes is shown below in a tabular form that does not require colour. This table shows the processes in columns, and the standards in rows. Where a tick () is shown at the intersection of a row and a column it indicates that corresponding standard is related to the corresponding the process. StandardCreateCaptureUsePreserveTransferManageStoreDestroyISAAR(CPF)International Standard Archival Authority Record for Corporate Bodies, Persons, and Families (International Council on Archives).IETF RFC 2821Simple Mail Transfer Protocol.IETF RFC 2822Internet Message Format.ISO 216Writing paper and certain classes of printed matter  Trimmed sizes  A and B seriesISO 639Codes for the representation of names of languages.ISO 2788Guidelines for the establishment and development of monolingual thesauri.ISO 5964Guidelines for the establishment and development of multilingual thesauri.ISO 8601Representation of dates and times.ISO 9834-8Generation and registration of Universally Unique Identifiers (UUIDs) and their use as ASN.1 Object Identifier components (see also ITU X.667).ISO 12033Guidance for selection of document image compression methods.ISO 12037Recommendations for the expungement of information recorded on write-once optical media.ISO 12142Media error monitoring and reporting techniques for verification of stored data on optical digital data disks.ISO 12654Recommendations for the management of electronic recording systems for the recording of documents that may be required as evidence, on WORM optical disk.ISO 14721Open archival information system  Reference model (OAIS).ISO 15444JPEG 2000 image coding system: Core coding system.ISO 15489Records Management.ISO 15801Information stored electronically  Recommendations for trustworthiness and reliability.ISO 15836The Dublin Core metadata element set.ISO 18492Long-term preservation of electronic document-based information.ISO 19005-1Electronic document file format for long-term preservation.ISO 23081Metadata for records.ITU X.667Generation and registration of Universally Unique Identifiers (UUIDs) and their use as ASN.1 object identifier components.MoReq2Update and extension of the Model Requirements for the management of electronic recordsTIFFTagged Image File Format.X.509ITU-T Recommendation X.509: Open systems interconnection  The Directory: Public-key and attribute certificate frameworks.XKMSXML Key Management Specification.XMLW3C Extensible Markup Language.Appendix 8  Changes from the Original MoReq 8.1 Changes that are not Backwards-Compatible MoReq2 has been written to ensure, as far as possible, compatibility with the original MoReq. The major innovation in this edition is the storage of records directly in classes, without the use of files. This is covered in section 3.2; it should be noted that the ERMS can be configured to disable this option. The ability to create sub-files as well as volumes within files is also new to MoReq2 (see section 3.3). This does not raise any backwards compatibility issues, but is a major new requirement. Also the definitions of presentation and rendition have reversed from the previous MoReq. See the glossary for a full definition of both terms. 8.2 Relationship between Sections The structure of MoReq2 mirrors that of MoReq, subject to some changes and several additions. This section shows the correspondence between sections in MoReq and MoReq2. MoReqMoReq2Chap.TitleChap.TitlePreface Preface: MoReq21 Introduction1Introduction1.1Background1.1Background1.2Purpose and Scope of this Specification1.3Purpose and Scope of this Specification1.3What is an ERMS?1.4What is an ERMS?1.4For What can this Specification be Used?1.5For what can this Specification be used?1.5Emphasis and Limitations of this Specification1.7Emphasis and Limitations of this Specification1.6Using this Specification1.9Customising this Specification1.7Organisation of this Specification1.10Organisation of this Specification1.8Mandatory and Desirable Requirements1.12Mandatory and Desirable Requirements1.9Intellectual Property1.6Intellectual property rights2Overview of ERMS Requirements2Overview of ERMS Requirements2.1Key Terminology2.1Key Terminology2.2Key Concepts2.2Key Concepts2.3Entity-Relationship Model2.3Entity-Relationship Model3Classification Scheme 3Classification Scheme and File Organisation3.1Configuring the Classification Scheme3.1Configuring the Classification Scheme3.2Classes and Files3.2Classes and Files3.3Volumes3.3Volumes and Sub-Files3.4Maintaining the Classification Scheme3.4Maintaining the Classification Scheme4Controls and Security4Controls and Security4.1Access 4.1Access4.2Audit trails4.2 Audit trails4.3Backup and Recovery 4.3Backup and Recovery 4.4Tracking Record MovementsDeleted (covered in section 10.1)4.5AuthenticityDeleted (covered in chapter 2)4.6Security Categories10.15Security Categories5Retention and Disposal5Retention and Disposition5.1Retention Schedules5.1Retention and Disposition Schedules 5.2Review5.2Review of Disposition Actions5.3Transfer, Export and Destruction5.3Transfer, Export and Destruction6Capturing Records6Capturing and Declaring Records6.1Capture6.1Capture6.2Bulk importing6.2Bulk Importing6.3Types of DocumentDeleted (covered in section 6.1)6.4E-mail Management6.3e-Mail Management 7Referencing7Referencing8Searching, Retrieval and Rendering8Searching, Retrieval and Presentation8.1Search and Retrieval8.1Search and Retrieval8.2Rendering: Displaying Records8.2Presentation: Displaying Records8.3Rendering: Printing8.3Presentation: Printing8.4Rendering: Other8.4Presentation: Other9Administrative Functions9Administrative Functions9.1General Administration9.1General Administration9.2Reporting9.2Reporting9.3Changing, Deleting and Redacting Records9.3Changing, Deleting and Redacting Records10Other Functionality10Optional Modules10.1Management of Non-electronic Records10.1Management of Physical (Non-electronic) Files and Records10.2Hybrid File Retention and Disposal10.2Disposition of Physical Records10.3Document Management10.3Document Management and Collaborative Working 10.4Workflow10.4Workflow10.5Digital Signatures10.7Electronic Signatures10.6Encryption10.8Encryption10.7Electronic Watermarks etc.10.9Digital Rights Management 10.8Interoperability and OpennessDeleted (covered in chapters 5, 6 and 10.6)11Non-Functional Requirements11Non-Functional Requirements11.1Ease of Use11.1Ease of Use11.2Performance and Scalability11.2Performance and Scalability11.3System Availability11.3 System Availability11.4Technical Standards11.4Technical Standards11.5Legislative and Regulatory Requirements11.5Legislative and Regulatory Requirements11.6Outsourcing and Third Party Management of Data11.6Outsourcing and Third Party Management of Data11.7Long Term Preservation and Technology Obsolescence11.7Long Term Preservation and Technology Obsolescence12Metadata Requirements12Metadata Requirements12.1Principles12.1Principles12.2Organisation of the Remainder of this ChapterApp. 9.1Introduction12.3Classification Scheme Metadata ElementsApp. 9.7.1Classification Schemes12.4Class and Electronic File Metadata Elements App. 9.7.2Classes, Files, Sub-Files, Volumes12.5Metadata Elements for Electronic File or Electronic File VolumeApp. 9.7.2Classes, Files, Sub-Files, Volumes12.6Electronic Volume Metadata ElementsApp. 9.7.2Classes, Files, Sub-Files, Volumes12.7Record Metadata ElementsApp. 9.7.2Classes, Files, Sub-Files, Volumes12.8Record Extract Metadata ElementsApp. 9.7.3Record Redactions12.9User Metadata ElementsApp. 9.7.8Agents (Users, Groups and Roles)12.10Role Metadata ElementsApp. 9.7.8Agents (Users, Groups and Roles)12.11Customisation Notes for Metadata RequirementsApp. 9.9Customisation Notes for Metadata Requirements13DD(D9D:DJD[DPSkd$$Ifl0/ / & t644 lal $Ifgd$#Skd8$$Ifl0/ / & t644 lal[D\DmD~DDDDPSkds$$Ifl0/ / & t644 lal $Ifgd$#Skd $$Ifl0/ / & t644 lalDDDDDDDPSkdE$$Ifl0/ / & t644 lal $Ifgd$#Skd$$Ifl0/ / & t644 lalDDDDDDDDDDDDEE(E)E-E0ECEDE}E~EEEEEEEEEEEFFDFGFLFTF\FFFFHGIII2LDLMMMMyOzOJQh#5h%>*huh%mH sH  hTSh% h#5h%h#5h'B*phhRf h#5h'hpXh%CJhpXh%CJmHnHuh'mHnHuh#5h%mHnHuh#5h'mHnHu6DDEEE(ECEPSkd$$Ifl0/ / & t644 lal $Ifgd$#Skd$$Ifl0/ / & t644 lalCEDEWE}E~EEEPSkd$$Ifl0/ / & t644 lal $Ifgd$#Skd$$Ifl0/ / & t644 lalEEEEEEEPSkd$$Ifl0/ / & t644 lal $Ifgd$#SkdR$$Ifl0/ / & t644 lalEEFFFFFPKFgdM gd$#Skd$$Ifl0/ / & t644 lal $Ifgd$#Skd$$$Ifl0/ / & t644 lalFHGZGlGmGGGYkd$$Ifl0 %& %644 la]p $Ifgd$# gd$#obGGGGG HfHDYkd$$Ifl0 %& %644 la]p $Ifgd$#Ykdy$$Ifl0 %& %644 la]p fHgHHHHH IDYkd$$Ifl0 %& %644 la]p $Ifgd$#Ykd$$Ifl0 %& %644 la]p  I I"IUIVIeIIDYkd$$Ifl0 %& %644 la]p $Ifgd$#Ykd$$Ifl0 %& %644 la]p IIIIIII6Wkd$$Ifl0/ %> x44 la]p $IfgdM gdMobgdM Ykd$$Ifl0 %& %644 la]p I6JBJDJlJzJ|JJJFWkd$$Ifl0/ %'> x44 la]p Wkd$$Ifl0/ %'> x44 la]p $IfgdMJJJJJ KKFWkd$$Ifl0/ %'> x44 la]p $IfgdMWkd$$Ifl0/ %> x44 la]p KKHKVKXK|KKFWkd$$Ifl0/ %'> x44 la]p $IfgdMWkd$$Ifl0/ %'> x44 la]p KKKKKKKFWkd&$$Ifl0/ %'> x44 la]p $IfgdMWkd$$Ifl0/ %'> x44 la]p KLLLL.L1LFWkd2$$Ifl0/ %'> x44 la]p $IfgdMWkd$$Ifl0/ %'> x44 la]p 1L2LDLMMMM $IfgdMgdMgdM Wkd$$Ifl0/ %'> x44 la]p MMNN*N $IfgdMrkd> $$Ifl4F/ %&> &    44 la]f4p*N+N &    44 la]f4pgNhNyNNN $IfgdMrkd!$$Ifl4F/ %&> &    44 la]f4pNNNN!O $IfgdMrkd0"$$Ifl4F/ %&> &    44 la]f4p!O"O6OHOgO $IfgdMrkd"$$Ifl4F/ %&> &    44 la]f4pgOhOzOOO $IfgdMrkd|#$$Ifl4F/ %&> &    44 la]f4pOOOOO $IfgdMrkd"$$$Ifl4F/ %&> &    44 la]f4pOOOPP $IfgdMrkd$$$Ifl4F/ %&> &    44 la]f4pPP/P;PIP $IfgdMrkdn%$$Ifl4F/ %&> &    44 la]f4pIPJP\PhPxP $IfgdMrkd&$$Ifl4F/ %&> &    44 la]f4pxPyPPPP $IfgdMrkd&$$Ifl4F/ %&> &    44 la]f4pPPPPFQ $IfgdMrkd`'$$Ifl4F/ %&> &    44 la]f4pFQGQfQrQQ $IfgdMrkd($$Ifl4F/ %&> &    44 la]f4pJQMQNQOQrQQQQQ+R,RyUzUVVVVWWWW_``aaaaabbbBbCbObPb\b]bsbtbbbbbbbbbbbbbb~cdd]dźůŝŝŝŝŝŝŝŝŝŝŎh#5h'B*phhpph#5h'CJaJ h#5hweh' h#5h=` hJh'hQE h#5h'h#5h%^Jhuh%mH sH  hTSh% hTShq48 h#5h%hq48 h#5hq488QQQQ+R $IfgdMrkd($$Ifl4F/ %&> &    44 la]f4p+R,R &    44 la]f4pjRkRwRRR $IfgdMrkd)$$Ifl4F/ %&> &    44 la]f4pRRRRR $IfgdMrkd*$$Ifl4F/ %&> &    44 la]f4pRR SSOS $IfgdMrkdD+$$Ifl4F/ %&> &    44 la]f4pOSPSfSrSS $IfgdMrkd+$$Ifl4F/ %&> &    44 la]f4pSSSSS $IfgdMrkd,$$Ifl4F/ %&> &    44 la]f4pSSSSS $IfgdMrkd6-$$Ifl4F/ %&> &    44 la]f4pSS TT1T $IfgdMrkd-$$Ifl4F/ %&> &    44 la]f4p1T2THTTTcT $IfgdMrkd.$$Ifl4F/ %&> &    44 la]f4pcTdTuTTT $IfgdMrkd(/$$Ifl4F/ %&> &    44 la]f4pTTTTT $IfgdMrkd/$$Ifl4F/ %&> &    44 la]f4pTTT U,U $IfgdMrkdt0$$Ifl4F/ %&> &    44 la]f4p,U-U &    44 la]f4paUbUzUUU $IfgdMrkd1$$Ifl4F/ %&> &    44 la]f4pUUUUU $IfgdMrkdf2$$Ifl4F/ %&> &    44 la]f4pUUUV*V $IfgdMrkd 3$$Ifl4F/ %&> &    44 la]f4p*V+V;VGVKV $IfgdMrkd3$$Ifl4F/ %&> &    44 la]f4pKVLVaVmVV $IfgdMrkdX4$$Ifl4F/ %&> &    44 la]f4pVVVVV $IfgdMrkd4$$Ifl4F/ %&> &    44 la]f4pVVVVV $IfgdMrkd5$$Ifl4F/ %&> &    44 la]f4pVVVW!W $IfgdMrkdJ6$$Ifl4F/ %&> &    44 la]f4p!W"W2W>WbW $IfgdMrkd6$$Ifl4F/ %&> &    44 la]f4pbWcWrW~WW $IfgdMrkd7$$Ifl4F/ %&> &    44 la]f4pWWWWW $IfgdMrkd<8$$Ifl4F/ %&> &    44 la]f4pWWWXDX $IfgdMrkd8$$Ifl4F/ %&> &    44 la]f4pDXFXhXXX $IfgdMrkd9$$Ifl4F/ %> &    44 la]f4pXXXXY $IfgdMrkd.:$$Ifl4F/ %&> &    44 la]f4pYYDY\YY $IfgdMrkd:$$Ifl4F/ %&> &    44 la]f4pYYYY+Z $IfgdMrkdz;$$Ifl4F/ %&> &    44 la]f4p+Z,ZBZNZjZ $IfgdMrkd <$$Ifl4F/ %&> &    44 la]f4pjZkZZZZ $IfgdMrkd<$$Ifl4F/ %&> &    44 la]f4pZZZZZ $IfgdMrkdl=$$Ifl4F/ %&> &    44 la]f4pZZZ[[ $IfgdMrkd>$$Ifl4F/ %&> &    44 la]f4p[[([6[>[ $IfgdMrkd>$$Ifl4F/ %&> &    44 la]f4p>[?[P[^[s[ $IfgdMrkd^?$$Ifl4F/ %&> &    44 la]f4ps[t[[[[ $IfgdMrkd@$$Ifl4F/ %&> &    44 la]f4p[[[[[ $IfgdMrkd@$$Ifl4F/ %&> &    44 la]f4p[[[\ \ $IfgdMrkdPA$$Ifl4F/ %&> &    44 la]f4p \ \\(\B\ $IfgdMrkdA$$Ifl4F/ %&> &    44 la]f4pB\C\X\f\r\ $IfgdMrkdB$$Ifl4F/ %&> &    44 la]f4pr\s\\\\ $IfgdMrkdBC$$Ifl4F/ %&> &    44 la]f4p\\\\\ $IfgdMrkdC$$Ifl4F/ %&> &    44 la]f4p\\\ ]] $IfgdMrkdD$$Ifl4F/ %&> &    44 la]f4p] ]1]?]R] $IfgdMrkd4E$$Ifl4F/ %&> &    44 la]f4pR]S]e]s]] $IfgdMrkdE$$Ifl4F/ %&> &    44 la]f4p]]]]] $IfgdMrkdF$$Ifl4F/ %&> &    44 la]f4p]]]]] $IfgdMrkd&G$$Ifl4F/ %&> &    44 la]f4p]] ^^ ^ $IfgdMrkdG$$Ifl4F/ %&> &    44 la]f4p ^!^/^=^K^ $IfgdMrkdrH$$Ifl4F/ %&> &    44 la]f4pK^L^_^m^y^ $IfgdMrkdI$$Ifl4F/ %&> &    44 la]f4py^z^^^^ $IfgdMrkdI$$Ifl4F/ %&> &    44 la]f4p^^^^^ $IfgdMrkddJ$$Ifl4F/ %&> &    44 la]f4p^^^^_ $IfgdMrkd K$$Ifl4F/ %&> &    44 la]f4p__#_1_=_ $IfgdMrkdK$$Ifl4F/ %&> &    44 la]f4p=_>_P_^_j_ $IfgdMrkdVL$$Ifl4F/ %&> &    44 la]f4pj_k_y___ $IfgdMrkdL$$Ifl4F/ %&> &    44 la]f4p___``8a}xgdkdgdMgdMgdM rkdM$$Ifl4F/ %> &    44 la]f4p8aZaaabb'bBbni__VV $Ifgdg gdkdozfgdJKEƀ^FigdkdozfFEƀ^FhgdkdBbCbMbObqhh $IfgdMkdHN$$IfTl4]0M$   t0644 lapTObPbWb\bull $IfgdMkdO$$IfTl0M$   t0644 lapT\b]b^bsbsjj $IfgdMkdO$$IfTl40M$   t0644 lapTsbtb{b|bbsjjj $IfgdMkdP$$IfTl40M$    t0644 lapTbbbbsjj $IfgdMkdQ$$IfTl40M$ `  t0644 lapTbbbbxoo $IfgdMkd@R$$IfTl40M$   t0644 lap Tbbbbxoo $IfgdMkdR$$IfTl40M$   t0644 lap Tbbbbull $IfgdMkdS$$IfTl0M$   t0644 lapTbbbbull $IfgdMkdaT$$IfTl0M$   t0644 lapTbbcdd.dNd]dukkf]]] $Ifgdggd] gdkdozfkdU$$IfTl0M$   t0644 lapT]d^dgdyddcZZZ $IfgdkdkdU$$IfTl44FP F"#06    44 laf4p T]d^dgdydddddddddddddddddddddeee e ee#e$e%e*e1e2e3eFeGeNeOePeVe`eaebekeleseteuevewexeyeeeeeeeeeeeeeeeϸۭϸۭۭϸۭۭۭϸۭۭϸۭ۸ۭϸۭϸۭۭh#5hLwCJaJ *h#5hLwmHnHuhLwmHnHuh#5hLwmHnHu h#5hLwh#5h=`mHnHu h#5h=`h#5h%CJaJDdddddmddd $IfgdkdkdV$$IfTl4FP F"06    44 laf4Tdddddmbbb $$Ifgd=`kd0W$$IfTl4FP F"06    44 laf4TdddddeZZZ $$Ifgd=`kdW$$IfTl4FP F""06    44 laf4p Tdddddk``` $$Ifgd=`kdX$$IfTl4FP F"06    44 laf4Tdddeek``` $$Ifgd=`kdRY$$IfTl4FP F"06    44 laf4Te e ee#ek``` $$Ifgd=`kdZ$$IfTl4FP F"06    44 laf4T#e$e%e*e1ek``` $$Ifgd=`kdZ$$IfTl4FP F"06    44 laf4T1e2e3eGeNek``` $$Ifgd=`kde[$$IfTl4FP F"06    44 laf4TNeOePeVe`ek``` $$Ifgd=`kd\$$IfTl4FP F"06    44 laf4T`eaebelesek``` $$Ifgd=`kd\$$IfTl4FP F"06    44 laf4Tseteuevewek``` $$Ifgd=`kdx]$$IfTl4FP F"06    44 laf4Twexeyeeek``` $$Ifgd=`kd)^$$IfTl4FP F"06    44 laf4Teeeeekbbb $Ifgdkdkd^$$IfTl4FP F"06    44 laf4Teeeeekbbb $Ifgdkdkd_$$IfTl4FP F"06    44 laf4Teeeeee\\\ $Ifgdkdkd<`$$IfTl4FP F""06    44 laf4p Teeeeeeeeeeeeefffff f!f"f+f2f3f4f;fBfCfDfKfRfSfafjfqfrfsfxffffffffffffffffffffffffffggggg"g#g$g:gDgEgNgTg]gngwgggggg *h#5hLwmHnHuh#5hLwCJaJ h#5hLwh#5hLwmHnHuSeeeeekbbb $Ifgdkdkda$$IfTl4FP F"06    44 laf4Teeeeekbbb $Ifgdkdkda$$IfTl4FP F"06    44 laf4Teeeffkbbb $Ifgdkdkdbb$$IfTl4FP F"06    44 laf4Tffff fkbbb $Ifgdkdkdc$$IfTl4FP F"06    44 laf4T f!f"f+f2fkbbb $Ifgdkdkdc$$IfTl4FP F"06    44 laf4T2f3f4f;fBfkbbb $Ifgdkdkdud$$IfTl4FP F"06    44 laf4TBfCfDfKfRfkbbb $Ifgdkdkd&e$$IfTl4FP F"06    44 laf4TRfSfafjfqfkbbb $Ifgdkdkde$$IfTl4FP F"06    44 laf4Tqfrfsfxffe\\\ $Ifgdkdkdf$$IfTl4FP F""06    44 laf4p Tfffffkbbb $IfgdkdkdLg$$IfTl4FP F"06    44 laf4Tfffffkbbb $Ifgdkdkdg$$IfTl4FP F"06    44 laf4Tfffffkbbb $Ifgdkdkdh$$IfTl4FP F"06    44 laf4Tfffffkbbb $Ifgdkdkd_i$$IfTl4FP F"06    44 laf4Tfffffe\\\ $Ifgdkdkdj$$IfTl4FP F""06    44 laf4p Tfffggkbbb $Ifgdkdkdj$$IfTl4FP F"06    44 laf4Tgggg"gkbbb $Ifgdkdkdk$$IfTl4FP F"06    44 laf4T"g#g$g:gDgkbbb $Ifgdkdkd6l$$IfTl4FP F"06    44 laf4TDgEgNgTg[gk``` $$Ifgd=`kdl$$IfTl4FP F"06    44 laf4T[g\g]gngugeZZZ $$Ifgd=`kdm$$IfTl4FP F""06    44 laf4p Tugvgwgggk``` $$Ifgd=`kd\n$$IfTl4FP F"06    44 laf4Tgggggk``` $$Ifgd=`kd o$$IfTl4FP F"06    44 laf4Tgggggk``` $$Ifgd=`kdo$$IfTl4FP F"06    44 laf4Tgggggk``` $$Ifgd=`kdop$$IfTl4FP F"06    44 laf4Tgggggggh hh"h+h8hAhQhZhghphhhhhhhhhhhi$i'iXi@jTjvjjjjkk$k&k/kBkHkYkfkkk l lll(l5l@lBlLlUl]l_lglilǻǻٯٯٯٯٯٯ٨ٯٯٯٯٯٯhpXh%mH sH  hTSh%h#5h%mHnHuh#5h2mHnHu h#5h2h' h#5h' h#5h%hLwmHnHuhLwh#5hLwmHnHu h#5hLw>gggggk``` $$Ifgd=`kd q$$IfTl4FP F"06    44 laf4Tgggghk``` $$Ifgd=`kdq$$IfTl4FP F"06    44 laf4Thhh hhk``` $$Ifgd=`kdr$$IfTl4FP F"06    44 laf4Thhh"h)hk``` $$Ifgd=`kd3s$$IfTl4FP F"06    44 laf4T)h*h+h8h?hk``` $$Ifgd=`kds$$IfTl4FP F"06    44 laf4T?h@hAhQhXhk``` $$Ifgd=`kdt$$IfTl4FP F"06    44 laf4TXhYhZhghnhk``` $$Ifgd=`kdFu$$IfTl4FP F"06    44 laf4Tnhohphhhk``` $$Ifgd=`kdu$$IfTl4FP F"06    44 laf4Thhhhhk``` $$Ifgd=`kdv$$IfTl4FP F"06    44 laf4Thhhhhkbbb $IfgdkdkdYw$$IfTl4FP F"06    44 laf4Thhh'iXivjkfa\R gdkdozfgdM gdkdgd]kd x$$IfTl4FP F"06    44 laf4TvjjjjiKEƀ^FlgdkdozfKEƀ^FkgdkdozfKEƀ^Fjgdkdozfjjjjjkktf] $Ifgdkd$IfgdkdoF|kdx$$Ifl440&?? t0644 laf4 $Ifgdggd]kk$k&kvm $Ifgdkd$IfgdkdoF{kdCy$$Ifl40&?? t0644 laf4&k'k/kBkqh $Ifgdkd$IfgdkdoFkdy$$Ifl40&?? t0644 laf4gFBkCkHkYkqh $Ifgdkd$IfgdkdoFkdWz$$Ifl40&?? t0644 laf4gFYkZkfkkkqhh $Ifgdkd$IfgdkdoFkdz$$Ifl40&?? t0644 laf4gFkkkk lqhh $Ifgdkd$IfgdkdoFkdu{$$Ifl40&?? t0644 laf4gF l lllqh $Ifgdkd$IfgdkdoFkd|$$Ifl40&?? t0644 laf4gFll(l5lqh $Ifgdkd$IfgdkdoFkd|$$Ifl40&?? t0644 laf4gF5l6l@lBlqh $Ifgdkd$IfgdkdoFkd"}$$Ifl40&?? t0644 laf4gFBlClLlUlqh $Ifgdkd$IfgdkdoFkd}$$Ifl40&?? t0644 laf4gFUlVl]l_lqh $Ifgdkd$IfgdkdoFkd@~$$Ifl40&?? t0644 laf4gF_l`lglilqh $Ifgdkd$IfgdkdoFkd~$$Ifl40&?? t0644 laf4gFiljlrllqh $Ifgdkd$IfgdkdoFkd^$$Ifl40&?? t0644 laf4gFilrlllllllmm_n|n\pp6qڿڿ𦝋~i^hpXhT\n0J^J(jhpXhT\nB*U^JphhpXhT\nB*^Jph"jhpXhT\nB*U^JphhpXhs`;^JhpXhin^Jj6hpXhU^JhpXhi0J^JjǛhpXhU^JjhpXhiU^JhpXhi^J h#5h%hpXh%^J$[\iɃtt $$Ifa$gdpXkd$$IfTl40&CA t0644 laf4TɃʃσ|tt $$Ifa$gdpXkd+$$IfTl40&CA t0644 laf4T|}:tt $$Ifa$gdpXkd$$IfTl40&CA t0644 laf4T:;P>tt $$Ifa$gdpXkd$$IfTl40&CA t0644 laf4T>?j  {vvm $Ifgdggd]gdzkdd$$IfTl40&CA t0644 laf4T>?Cj   ijklĈňƈ"#$CDE~ۉ܉݉ƹƍ~uƍjujhYUh fWh%0JjhYUh fWjh fWUhpXh fW0J^JjhpXhU^JhpXh fW^JjhpXh fWU^Jhs`; hfhs`;h#5h2h>a hfZahfZamHnHu h#5h2 h#5h%hC h#5hin( $$Ifa$gdpXlkd$$IfTl4&O% t0644 lalf4T% $$Ifa$gdpXlkd%$$IfTl4&O% t0644 lalf4T%& $$Ifa$gdpXlkdj$$IfTl4&O% t0644 lalf4T< $$Ifa$gdpXlkd$$IfTl4&O% t0644 lalf4T9:;[kl?@ACNO»ؕؑwcw_؍Wjhc9>Uh.-'jhpXh-T>*B*Uphh.-h.-0Jjh.-h.-0JUhs`;h-CmhthLwhU0JjhLwhYUjhLwhc9>U hLwhc9> hLwhq hLwh%hpXh%5 h#5h%h fWh fWh fW0Jjh fWUj?hYU"<= $$Ifa$gdpXlkd$$IfTl4&O% t0644 lalf4TZ $$Ifa$gdpXlkd$$IfTl4&O% t0644 lalf4TZ[k $$Ifa$gdpXlkd $$IfTl4&O% t0644 lalf4TklB $$Ifa$gdpXlkd$$IfTl4&O% t0644 lalf4TBC $$Ifa$gdpXlkd$$IfTl4&O% t0644 lalf4T $$Ifa$gdpXlkd$$IfTl4&O% t0644 lalf4Tލߍ   3GHTmopq-./12589w.PQ¾ʾ¬ʥՂ~~sjh#5hUh?hwZ7jhYUhc9>h20JjjhYU h#5hc9> h-Cmh2jëhUh2jh2U h#5h2hC h#5h%hs`;hc9>h%0Jjhc9>UjthYUhc9>-30 $$Ifa$gdpXgdzlkd=$$IfTl4&O% t0644 lalf4T0145!ikd$$IfTl%% t0%644 laT $$Ifa$gdpXikd$$IfTl%% t0%644 laT5wPR^AjOQFEƀ^FngdzFEƀ^Fmgdzgd gd{Qo.{F $$a$gdqgdzgdCQY[]jpORܔ%)+,468KONU4<bfã%,T_Ƨȧاڧ񨤝 h#5hghg h#5h%h#5h25OJQJh#5h2mHnHuhv0h#5h256h'js:hR)Uh?h`/h#5h25 h#5h2h@h2>Oܔ%s-(gdzFEƀ^FqgdzFEƀ^FpgdzFEƀ^Fogdz+-9ɖIKONU4<bfã%,gd{9K$gdm:$gd;bgdR) gd{Qo/{F$a$gdR)gdz,Ƨȧڧ$2>NPfjl $$Ifa$gdpX $$Ifa$gdpX$x$Ifa$gdpXFfd $Ifgd{9K $Ifgdggd]$gd;b$gdm:gd{9KڧNPjDXZҪԪ(*d~(BDntв<BrRrt̴δ:PR̵εdvxӼӼӼӼӼӼӼӼӼӼӼӼӼӼӼӼӼӼh4#h'h;bhpXh%OJQJhpXh%7OJQJhpXh%5OJQJ\ h#5h%hpXhg67hpXhg5CJ\aJElptx|DHLNFfi $$Ifa$gdpX$x$Ifa$gdpXFff $$Ifa$gdpXNPRTVXZj "$&(*:Ffo $$Ifa$gdpX$x$Ifa$gdpXFfl $$Ifa$gdpXЫdfjnrvz|~(*.26:>@Ffu $$Ifa$gdpX$x$Ifa$gdpXFfr $$Ifa$gdpX@BDVέFf{ $$Ifa$gdpX$x$Ifa$gdpXFfx $$Ifa$gdpXnprtvxz|Ff Ff $$Ifa$gdpX $$Ifa$gdpX$x$Ifa$gdpXFf~ tvxz|~вҲֲڲܲ޲rFfu Ff $$Ifa$gdpX $$Ifa$gdpX$x$Ifa$gdpXrtvx|~  *RVZFfa $$Ifa$gdpX$x$Ifa$gdpXFfk $$Ifa$gdpXZ^bfjnrt:<@DFHLNPRfFfM $$Ifa$gdpX$x$Ifa$gdpXFfW $$Ifa$gdpXĵȵʵ̵εdfhjnprtvx Ff9 $$Ifa$gdpX$x$Ifa$gdpXFfC $$Ifa$gdpX 4`bfjnrvxz|Ff% $$Ifa$gdpX$x$Ifa$gdpXFf/ $$Ifa$gdpX `z|68LNZ\|~йҹ޹Ժ8LN  5žx0{ hTSh% h#5hRhR h#5hh h#5h`/h`/ h#5h2hChV`L h4#h%hpXhbzOJQJhpXhbz5OJQJ\ hShbz h#5hbzhbzhpXh%5OJQJ\ h#5h%hpXh%OJQJ0\`dhlptx|~Ĺƹȹʹ̹ιйҹFf Ff $$Ifa$gdpX $$Ifa$gdpX$x$Ifa$gdpXFf ҹ޹Ժֺںܺ8:>@DFHJLNVFf Ff $$Ifa$gdpX $$Ifa$gdpX$x$Ifa$gdpX5n0 $Ifgdggd- gdV`Lo[ gdV`LoZgdV`LgdV`LFf $$Ifa$gdpX|||| $Ifgdgykd $$Ifl40&  t0644 laѿ_VJVJ $$Ifa$gdpX $IfgdV`Lkd $$Ifl4\&&) t0644 laѿҿտaXLXL $$Ifa$gdpX $IfgdV`LkdL $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la=AiaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laijnaXLXL $$Ifa$gdpX $IfgdV`Lkdw $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd0 $$Ifl\&&) t0644 la#'VaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laVW[txaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd[ $$Ifl\&&) t0644 la;aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la;<@VZwaXLXL $$Ifa$gdpX $IfgdV`Lkdͽ $$Ifl\&&) t0644 lawxzaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd? $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la #'AaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laABD[]aXLXL $$Ifa$gdpX $IfgdV`Lkdj $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd# $$Ifl\&&) t0644 la aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la  2aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la237]aaXLXL $$Ifa$gdpX $IfgdV`LkdN $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkdy $$Ifl\&&) t0644 la'aXLXL $$Ifa$gdpX $IfgdV`Lkd2 $$Ifl\&&) t0644 la'(,FGiaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laijn{|aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd] $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la !FaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laFGKRVtaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 latuyaXLXL $$Ifa$gdpX $IfgdV`LkdA $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la#'6aXLXL $$Ifa$gdpX $IfgdV`Lkdl $$Ifl\&&) t0644 la67;MNoaXLXL $$Ifa$gdpX $IfgdV`Lkd% $$Ifl\&&) t0644 laoptaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`LkdP $$Ifl\&&) t0644 la  "&;aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la;<@^baXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd{ $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd4 $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la!8<SaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laSTXbfpaXLXL $$Ifa$gdpX $IfgdV`Lkd_ $$Ifl\&&) t0644 lapquaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la"'aaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laabgaXLXL $$Ifa$gdpX $IfgdV`LkdC $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la 38NaXLXL $$Ifa$gdpX $IfgdV`Lkdn $$Ifl\&&) t0644 laNOT_doaXLXL $$Ifa$gdpX $IfgdV`Lkd' $$Ifl\&&) t0644 laopuaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la!$@aXLXL $$Ifa$gdpX $IfgdV`LkdR $$Ifl\&&) t0644 la@AFRWcaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 lacdiaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd} $$Ifl\&&) t0644 la aXLXL $$Ifa$gdpX $IfgdV`Lkd6 $$Ifl\&&) t0644 la ;@haXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 lahinaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la BaXLXL $$Ifa$gdpX $IfgdV`Lkda $$Ifl\&&) t0644 laBCF\_uaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 lauv{aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la0aXLXL $$Ifa$gdpX $IfgdV`LkdE $$Ifl\&&) t0644 la016cnaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la0n:]^\] ]!]>]?]]]]]]]^^1^2^^^__@_m_p_q_____ ` `_`g`````aa9a:aVaaaaabbbbbh$7hO4 htlhtl htlhtlhtlhMQ h#5hMQh{QhAyhpXh%mHsHhH_Y h#5hH_YUhpXh%mH sH  hTSh% h#5h%?aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la /:]aXLXL $$Ifa$gdpX $IfgdV`Lkdp $$Ifl\&&) t0644 la]^c|aXLXL $$Ifa$gdpX $IfgdV`Lkd) $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la 7aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la78>U`aXLXL $$Ifa$gdpX $IfgdV`LkdT $$Ifl\&&) t0644 laaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la\\#\aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laReference Model13Reference Model13.1Glossary13.1Glossary13.2Entity-Relationship Model13.2Entity-Relationship Model13.3Entity-Relationship Diagram Narrative13.3Entity-Relationship Narrative13.4Access Control Model 13.4Access Control Model ANNEXESAPPENDICESAnn. 1Reference PublicationsApp. 1Reference PublicationsAnn. 2Development of this SpecificationApp. 2Development of this SpecificationAnn. 3Use of this Specification in Electronic FormApp. 3Use of this Specification in Electronic FormAnn. 4AcknowledgementsApp. 4Acknowledgements1Project TeamApp. 4.1 App. 4.2Project Team Editorial Board2Validation OrganisationsApp. 4.3 App. 4.4DLM Forum Review Panellists3TrademarksApp. 4.5TrademarksAnn. 5Correspondence to Other ModelsApp. 5Correspondence to Other Models1Correspondence to Dublin Core Metadata ModelApp. 5.2ISO15836 The Dublin Core metadata standard2Correspondence to Pittsburgh metadata model--Ann. 6Date ProcessingApp. 6Date ProcessingAnn. 7Standards and Other GuidelinesApp. 7Standards and Other Guidelines1StandardsApp. 7.1Standards2Other GuidelinesApp. 7.2Other Guidance3Accessibility GuidelinesApp. 7.3Accessibility Guidelines and resources4Long Term Preservation GuidelinesApp. 7.4Digital Preservation Guidelines Appendix 9 Metadata Model Appendix 9 contains the MoReq2 metadata model. Because of its length, and to ease cross referencing, it is published in electronic form only, at www.dlm-network.org/moreq2 .  DLM is an acronym for Document Lifecycle Management (it formerly was an acronym for the French Donnes Lisibles par Machine, in English: machine-readable data.) The DLM-Forum is based on the conclusions of the European Council (94/C 235/03) of 17 June 1994 concerning greater cooperation in the field of archives.  MoReq is available from  HYPERLINK "http://www.DLM-Network.org" http://www.DLM-Network.org. It is also published in paper form, with ISBN9289412909.  The Scoping Report for MoReq2" is available from  HYPERLINK "http://www.DLM-Network.org" http://www.DLM-Network.org.  It can be held that all properly managed electronic records are structured, as they all are linked to metadata, audit trail data etc. in a structured manner. On this basis it would be more accurate to refer to unstructured records as records containing unstructured content; however, this usage is not common and so is not adopted in MoReq2.  At the time of writing, development of an XML schema for MoReq2 is about to start. See  HYPERLINK "http://ec.europa.eu/transparency/archival_policy" http://ec.europa.eu/transparency/archival_policy for details.  See  HYPERLINK "http://www.interpares.org/ip2/ip2_terminology_db.cfm" http://www.interpares.org/ip2/ip2_terminology_db.cfm.      PAGE 231  MoReq2 Specification Version 1.04 8 September 2008 Page  PAGE i   #\$\)\2\7\@\aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la@\A\F\`\e\\aXLXL $$Ifa$gdpX $IfgdV`Lkd8 $$Ifl\&&) t0644 la\\\\\\aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la\\\\\]aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la]]]]]]aXLXL $$Ifa$gdpX $IfgdV`Lkdc $$Ifl\&&) t0644 la]]#]:]A]X]aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laX]Y]`]]]]aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la]]]]]^aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la^^^-^4^E^aXLXL $$Ifa$gdpX $IfgdV`LkdG $$Ifl\&&) t0644 laE^F^H^U^^^g^t^^aXLXXLL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la^^^^^^^^aXLXXLL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la^^^^^^aXLXL $$Ifa$gdpX $IfgdV`Lkdr $$Ifl\&&) t0644 la^^^__=_aXLXL $$Ifa$gdpX $IfgdV`Lkd+ $$Ifl\&&) t0644 la=_>_@_m_v__aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la______aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la_____`aXLXL $$Ifa$gdpX $IfgdV`LkdV $$Ifl\&&) t0644 la`` `,`3`R`aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 laR`S`U`_`h`r`aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 lar`s`u````aXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la``````aXLXL $$Ifa$gdpX $IfgdV`Lkd: $$Ifl\&&) t0644 la```aa8aaXLXL $$Ifa$gdpX $IfgdV`Lkd $$Ifl\&&) t0644 la8a9a:aVabbJcca\WRMHCgdgdvKgdjcgdtlgdUMgdkd $$Ifl\&&) t0644 labbbkbbJcKcLcdceccccccccccccccccccc d d d!dIdJdKdedfdgdhdidjdµɊɊztjjh+ 0JU h+ ^Jj h6h+ U^J hVh+ hHh+ 0J^Jje h6h+ U^JhHh+ ^JjhHh+ U^J hg)h+ h+ jhg)h+ 0JU hfh+ hvKh+ hvKh+ 0JH*jhqh+ 0JU(chdef"g#g%g&g(g)g+g,g.g/g2g3g@gAgBgEgFg\g]gjgg  gdg#y  gd%4gd8P &`#$gd%gdvKjdeeeeeef f^f_f`fffffffffffffgg"g#g$g&g'g)g*g,g-g/g1g3g4g:g;g޸zpjp h+ 0Jjh+ 0JUjh+ UmHnHujhUhhHh+ 0Jj h+ Ujh+ Uh#5h+ 5h#5h+ >*B*phj h#5h+ UaJh#5h+ aJjh#5h+ UaJjh+ 0JUh+ h#5h+ (;g>g?g@gBgDgFgGgNg[g\gigjggggggggggggggggg>h?h@hིࣘ}kgch$7hB9#h+ B*CJ$OJQJ^JaJ$phh hg)h+ hfmHnHu h6Hmh+ jh6Hmh+ U hN-h+ h+ B*phh8Ph+ B*ph)jh8Ph+ B*UmHnHphujh+ UmHnHuh+ h+ 0Jjh+ 0JUh+ 0JmHnHuggggggggggggggggggggggggggggggd6Hmgd%ggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggghhhhhhhhhh h h h h hhhhhhhhhhhhhhhhhhhh h!h"h#h$h%h&h'h(h)h*h+h,h-h.h/h0h1h2h3h4h5h6h7h8h9h:h:h;hh?h@hgdjc901hP:p%. A!n"n#n$% <001hP:pg). A!n"n#n$% 901hP:p. A!n"n#n$% @=_ӑEx斷"^e Y0x] |UNW:iӤsp&@`Ҡd1!1: &&Qd# #3 Gc\Dd`ՑםwU8è~߫WݕN_UI:_^_BAi 'd㱄e(28spyHCyB>"N{o^~?%}xӶv09q) '-Iz8Aݳqd->?g_p",dXiK>X*JʿF+Ŋ>Ʌy8_0ay9\h'Ďu +w;WnXwi P_`WkzcY$Yqw&þERɖ HYz.Z Ox~OǛ:bDCFŅ1gS"'kof-2;%',9Dmݶ5j+vA۵NG?w*%-Kb;iZownU̵6_&Ncq I,c]䩆IKseI ˚J޼IPD9}cΏ)ߛSnb5orYu6"ZDI vh yq@WI`zq(#1%qQZ8 @z$gNXgOJUp1ut j" GcFX]iVphMrslw&m0Ͱ}w;lO$|N8phEb,=D=X9Xi^#{" F#gSE#GVDK͂6FHPA$zێͣxBLj4v,vl([GڊԶgmТZ-p;Y$:5@Bk%5 Ksރ 5@s޼K\5@s {opikܰ458D, 1Ȯ h 40] $ A 4hA$X䃻gV5`0x((d4h3+|k950=pUIт.=0IA ,AI XY,*,"$@G=0+w#g=KXbvK=@mC`IՃœXvz ɯMVK ;/H2(O'ۓ|=RN]rb.Y%k,%('@$=g?/Kh,07="jݻh=H_&=֋к h%z`9Q>7aR%ܸ뮰޸^H&8iG(g} \S)*p5y'hWV.sߣ65gڮ2C{D7jɑ˴Zv89?7KryBn`5<}-Kv.2E/Ҭnn֬%ٷu͵-PM_-\\ۯv%jXP7nNp?` Z7KZBZhxD: t7*x?ps%(ܸ>7Jɝ hVy5 =~Z_Vro Z_ۥFXL֍ _AV`isa~*uz!gTcO_Gul~)q-mb\vTK.t!c"DVy]Q1X<*FrIt}6Q W ci ?R);*5Juޱ0Ï=B1Li̷=7[Ac?_._/-fKb,vяڻ~F^C~h/瘟/V,OKo<%gcP>Icp/gZiE}PDB.;y3á*>y3KXrFw xPܗ裹rs^PAdzEe5e[Z|SKR{"NjhO;h"춿$;֟Ok-~bl2 #_žc)cۡL^&rķ߱+JM,}s\wouEg驊PΔ~*xoSū+4yc,_?tmk\V,tס }OǺjmZA_Ǻ]>8{A gg#rv{r1Z_1Lqg?O8r6Z^h)gC;Ab;#✽Ᏻ;M6fJ9{l}|)EsNU}bl)g7gb\~/~V/p6byp7C+3*qYm( =92 ̵g~lT٣T9#8{DCCj vUGR3IۡE?ZvmoQ!GJ\xݔcWC\)엫qviuS> ET?~TE)}g\]UuyT/~ p6byp_`dg[|pp:ⅳ-nmpIKW$7{r6y2ogoo Jr{ q6E<It-%T3Ŀ7 |j`l"+!&l9/Mpl)x" "_(.繵 ןC8yo\vK`G ?&ߍZGM q^tګu1$: v; =Zw//=vð5F^;3_GϢ]:a<»/u}@pwQgLKlaT_lUsm-r"i]q!_FbtWB*,~iY寎o9u(W7a]WE,Jy)'^DmFux'/}O9Uأܾ ;<n;뭃k6Ǽ/ieR]ϴx~ॹ]y ife+Zx i0,7^º$SQ0;~1"w|NkmO7 xFe o|qnJ11 =H#DxTz~-_o<ڇj(c>R Fh$KbascQ *BKNwes~ǥ aH'6טQs)A9=ಸ抛U#V?[8 p' sOtKN(+KPWjuFz9N[k3|N\'Lb}%0יc3Dss%sΙah6`;^pǺ':k9ʆk`8?Υ8qc, ,c;c ',||sŝN p"puऎM"w^j8?䂴_cL|';N1yco8o ^Sv,;7N:N=ʇan%{w#}7FmB-WGǍǍǍZ=vr2;#y bǎ,X5v9;SN_csϱ;ts"wyg7n;Kx =yg>s\<X}b%<+Ūb.V2 XH'I󓪟T>_ɨra >z5wRfG}-r9MnkYp~iM7 OV%p= n .z>H]y'0$CIA6yy䦋L] =4T- .cջ?$qb_絩{P 4_&PMc +t9t }g5;8o+pߎ]Gc4)OZeqrnֵ5O}3Rf]7kO.OQG=4_[9pm-`ާmm.gu2YV Q 5=tmݨ0ؔQL ܼuNCn7V}މL`=S´o7~-6=jDsD_]c ^P@q?UWoDq(Ë: ؃Wϛn,ƻf)2f[?~f7{or}u˂DY^¥g,-~7Ây}9=Ԓӈ5ٛ` *F諅-.֊=z)ڪY+)gL>YjVW6To\wV)ɎNuܭQ?TO^L︟'OyʁfAFٰyϸ_\u2Q/5gGO9+' ߃UR {fCw~q6'Qk2! 3tO~o_P/X:a+<7vw?|--ޓ}҈eX/U8UUakUf=Epcl*n|*/)g ڥ:r_ @l5pBK?6 P R|%#'ĠҭSJw^>.=>755-PS+!$bͿs^8jՠJ>6~P7nq =Zƨ+N[s}~c5@ }Yo :P@Iϋx ,WLZg^_\Y{oIpd╕0[SY$VB쿲/x3 Cg>bT(xD,Kaiְ(a 98/Aڣ^_a {nOյQioHv} J}ite%ˮ_rvC1ڃ^wѝ5vI $ySa :!%חh=+n^*(װkZ [NV$N ] MS¥$+vjp=-`·fBW= _~y>ul6g33/>;wl/xޯx}<\[#[N#ȈwvWux'~k;N34P_sf8{{͌1fW'w3~ *%帪֭@mCN ػ߆̨ڰn/`o/!:z7ͷx]MGW\BlͿ%Zoud388i4m@'(3﷟?[a 4:L?1v XLjf󥹢3՟jܛO+Wmmqtb:)?BЌGK]kƿ7īs==P.O3&|j>ԠF̺ vh;FLR2]l<L7yOċfglhڦO2Nl7{tFLz3n]`_$ǽ|8:~5R1U)>i?έ3|_)>`iN26{#h ⶦ0uen)"Iw[sϿȳESNg =N â 4 ǎl|c};4Δmz-׳d4;LΑI t1}#}~0Gv\̑7?w_,F4J [y "?p ۿO~w>䷟|'O>g~-:b6_·4d v:.-|wu:w++C a/\|[ LVw+vJ̫4!ƥ$Sd}x{BAR53ga橾6},b6> n2qIDz9R^/$c#tdB4WN]"k=ڬ夝}ھwO=;}i]3(k」y$Շxw4$3im0$8N1G/џ;{VZ\֋!3?s5e#P'T\ԏȷDAsKIzOR"?C\0zNQ|_ݲNQ7W;oM>S ;BCTRJQ)W``#XW FE_s" . 8":$ܣ]'9!MG9:I}Ŕvmb7DӪDg'od fzj+zZg$)_1_Bx (9 9QGh2]`n"<ۧ#ã 9ܖ̣UY~2U^P"+ORHpjx7$3'!.Ά }/rs" f&=\v q{ܾao l+_ (5sV?qe|٩>]vox+ r߀ :5j?J+:3S=4MFw{ƞ-n&AjM$8ȩUϰ/vx{q=fq2v%GrrU=ACc{`ҁe oN`8z#豭*~;91\=ȱS;&̼\0ó$-ݪ ?䓟Op Ͻ=Zz.V#.|4o/~Qxy~#q ̭IϠejD{q9BV&̫3${|L1g }?$)"ϗkKc~G|װB|})K s?hr$IB[Z=mwkZWxZGpPɢ37h Sb0eL:WhʸKOi63@r"_N Y,-# Dzd#y>-Tk`~SF!ƾc;C辿CdxWn~/Impc]y?||0|})vNMX1'رj 䜗[`f&.4P<C\G=V܃ ߪ(3 r s]ՊkXZq/pa000pkn8L+Cx{=Ȝ4ʇRJޔ;l> VܿL&d ;泐Ƃds6#6 gw@tL-̕ "?ps|vˡJpP9*pҁvN?ݸ>5;=m=̽ (RY|\˨6~07 'eb>i2NCLd=牳&Yjk`^j;(PgvYnVP%َX7pMR s0c?K7}IG>Ї N|y/{L8g5$'@TCF;7`?ؕ@߹Slƽ{7BY&WvotLq V{%:V0B읲rBvGLyN|pL3g۬h}Y/t<=xf0g XqqP({{AwV1 )3SjwݢWナ:^veDhIq3twNHO8OqIuLЯFxx&M6Q7+_f_rv\L_dS7*{[}=p~߫ê9<ËN9vlϪLsړ: ?vyJfF]X_W:vڄ{[ٳ"NPn9W G{#:}@r=.0ig\w\PiE{?LOcbr ڟQ:)PLJl =Y3\'KN _wtLʋIEG: }JtT Vc99@}\5+ʏsLg9_ ? Tۜ~~ouj`=iӬ=/)ḤHmBHHɺc$9EIt'ň 7jU:24_NpyWW3Eu`[IF=:LOD(98S.ps"~lṾCMSLSLLGϙ2gEsE[R9 rtFE3{MD9 PGY}fqVߩ {xCAi!!_>h&:FۅrREwOײ|6\X>ad$ '<އN˫Z/Pb?Z2ީ|Y-~-_jcBp/1 $ j|&W*Mb..1Fs KEqfZWyLţ*=M9 ȆyܛWRh5*Dl=-s7_2W0>*jXi宼[>XƄ͙H*z:f0jV{Uo1+U L{U=C8Wd~a7KA4@ex*W~C{,Wƿ?y ++Wup=3K%Zý'(A,/@ŭ= T(&Wp3P,e&Iʱr!w&U}'L`=(4~N \j&N%/bL1A~x(loI|f:.}Z8 IUީ<662{PfRhJgw3rWHP-0 +>#1Syi˛^j t&ut uA Qj^1'?tӦs^R6%^SYg/dL֤ٿӃ[ϙBr ;A>5Lϗ}nADrKo8KkF)1 Œ!ŧԁ02$J<dfuJǬtݽ/ɥP]0IRIW.~##:-mF,f;I~{9ZɅmVɏL/ [~t~zV |qvN9 ,|=Ep)VrB{0NFA}W$6O`yN.NrZ!Zlo=l322xB*tS1ݡهd'&>tiVɽ{Ϟ nz.Y脺#D8eWBZ"B"T{Hy\YYĐb=ҟ%ÿShQʉiVkoT2% m9Ϋ e/,WQ{; Pep?-^w/ߐ'b TI-RRN$ׄ3ϲ!P Uw%M%'l86VMbWh{L0qwåK({ 7I*zOYd~Mcܺ^$h˧;kBJDʇY'p{(׆okd#olЂ4|4'[5#%F\:{]Lq[ƋM b/QV<_T(-Ym*-l!vnZ &gU2yt*pMf962fJr*概k2hv]z@]zVY/m\2`|.lCVrlszjq躍k!!3wZb xu_K)꡵{W{2M!NyYj2Je}m]8ܽD$Ms-RlQ1`+It%ABqHشwXH Y`HIr2-l,Yί^By{ <,EtBsުOMgjT82D— li2D=\Rb:|3,l%G >bҪR7O~ $Ϥ_*X{=ċv9eдi/,m $o!@'AW SDh3)U|cȖ"셿<ao q8P r\\VԻ#9^R܁OLQM-8o]f@a>{g Raôc:W^DMALAK=` {n3VeiiA%; ħ Cml%@8u͟GWB6{5Sr'̯EW4BZv,2X*q/ITm9uL8= `*7|rlb qhܐ@_%K ͧF`f:&y nهWJ:Oӧ[UN'ܻvAAĪŏ,qboSsnC2Ξyqb|C93׉Q26Lʶ4 X[7,;?tЃ&_=|蠖Awٳov{(Ĭna- YYL`J:4Dn3J >y- 2iڍcƵpS) t܋Tӥl+ gV(l<=|arzRRGOʈt47WfB{0ٔla){OɠzCi_ \=W8{Rީqfhrë}B|tÂ@ri@%Xz6hi(Rưd :NfFxxӫOC/ .[}||]mhl5 maG%ǨHJᴯ@Vܵc.f@'gU3X| Ⓙ.ŋiE;O O_ATM?y87='@(Zk '+T̏up<#X$xmhT:e s{*:sd 9R+e|vq^3TL%LNCeb z||J%AqzyX=Y̩W*2Gj+Ł2;0FJ`n;Ot3t,8=sL=e}-]f19"=P6@֋38L_-9n9) |)c09!ؼS& O.3Ͽv¡'_As2Ҝ82˖gTh""Mxr6ЎL0ުM?{p*Uj%OQ[h<,}پ~V'H˲unGM^}C!AANm9qG0D_%CU/:$\8JUDFy&KLӝ{y&J{n6GO^S|Z~$o`0-dL.F[ϊAұ7rP 2DW_揪oֵ1{ekIuyG{8m2'33% fPO cѳf6K;RuNe_>bn#6pa|ˎ=F2nH,@XG2w=cp'Wi / {'B%HCY-3/.TX3 IJUJBh!]rPz8@n߈ifǛNń@Fwƃ%9O-ơT+M}QL8q<(D Cave,2pΛgH1ͧuzҪ\Vs]&o'!AcFS LHTv /st^}m%a*SU"ضC>Ϳvת5uT-S*:N\Ȧ^}"8(棗CVE})7h |Z~|Zk9F*Sv6.{kz|id]fk¡+e u G!ncI kONS`4z?#Cl1+t,áRN0DwUΝ<;}|9v&/_ 3`! 93?V#h=l^/]ǟK1n^ =3} -禴]HcV7<Ĥi֞yO#rN9:rF V!;2}N t2;s'h0JzY Qrin~~' 6*E4m ֻs|`Ҏ'\I/Vۯ\#nU?nQ1vO5`]>$!JȕejwSǺ*I_9^:kŰnjLM@mw@ؓx8F/VE-xbɞ!2IRj@#SXĎAnTGඊybWiӳ/o>˄F=L.FFy:" !sއS-UsK@ȁth8L: |i{[6ۛ˘򀻬pZPoƝ 0KR 0FvW6ֺ <ՖXen +FyzϤ/Afdo);K{S\S!7-*K@47%$*I|lxh&CYĉ IB}ce3YN5 Vý-`q+R :X,@AgӮXNy^|\E|4J(:i"1@t,oiJT&ƆrhΖFsL3%ii&v-hԔ8ф{HwwhyjW?ʿhPQB;tDwE>vic.n fW\E~U\DẎJt%{ "brAf_+}s@߽): q>G/wV;k@=>5^)V` >moۿ٧\Çc3O2`wl#8Y!ϊ!ZXy_ O_@l Я, }7Kho=={NŰ i5 {Ht|Iك+=!uiG$+t̺n)dMf%sU зHxAguAIWfpՉ-}vqלde]}y& ꧂K.#Uzwue!KSUJћK^j!%?|k#3l(ȭR@E&~-E" L}n'~u]c% sg(ՂJ ?SɀG cTK7#2 ǒs=މFW[bVc-~~#-G,#㪪W{PԪ=ΐJ3>rs28(-9d'6L/lOz^^tū&P f <aZ4!%`F HtL5ͺ+1UX9ʹLXU8X"_~30g||H \ANzIi4:!CLԒ.`q>/Ld"Szl~dx/e, !P(elk&3zkʏ'vex)EG]ͫusrV푿F^]K?Urgxy[鳋=yzg:"i1*D]lnfsi0ncA1)q5k) J>.qm,Q5K.#É=gʹ)L|z@ObiO1!l*a[ "]1}*^vMьߋᄟ-&S![?WY˂IuV>V^ :@(r D^N89 ]7uXh[i0^K7 %K]ѱ鿴I~t* ̶q0$y {]p+$HVk' 0q)Xa4?i-}[I;ްUhƏ. Uޣd;KM}&>A&|xKšݓ%ڠmFQ&ӻ➲|ۉED"MJ#~B7X?I\.\{dXO80/I9AJzTSPJ%j}CL~({q{p}^z"}n">T]9NMɳdD1Rߏt_跆BjojzVty0IhJU4@'O03EaI9+ JF"bw!"F?BDzNz;mMgt tKօ͡}pt1{hs-r(̄}-!slXV!& 4yG Ԓima\ ј/k-k H _(n9"<4M;Y6f<Ϯ&Z} YLify&dTs46)sj|Z=*_[Mܔ "yLȵ*m@8ùBca"AW-^tl–3}FT>vN x>?-Fp@tH !  {"ph4b.2WQP4[?%tŐH!JT)A{SAbQUB'[3U2%ǥKq8j=>x. J7(JsRi M8 xcYs2e|ޭ _lMp)q/ FEl %QWMFb8LA,:nrq5}4g1rt%;q%YO^K'y{(DSNq \d*/r$?Ź~W7F{);0at_9L%. S67LTΠE5^W .E$.JiѽO+anQZSe a?5>HRtRкS5֫&2c7N:BpȮ,@vb|cX/,Y{Sx BXςuP(k_ H3MlȧĊL$STQk&Ȟ]=;4k#$/CKMLN0c-㵝`ϤH8 P>m`#z^ ziW+mO{_nбŒ٫fHxJ,op, V-Vſ|EGCSAWƂY6 c래y4I $cAaA9kU ,*3=Mv/,\赌IB$Kx}o:L|;Ѓ+ %8<Ka>*E-H6K$ca| @]3'y ފ+ i8 94hSrIxƙmWs5!*& Nѵc+Bcn^ܝ6i<9u ܥ+@no7= tlCz3t"Wڳ{A\=CطW+{Sۭ_;%B ?J/乢찳J-̡:8 |F/E3ΫyΝ 7z82'WE7A+Fp6;Ui|#ssgϼuc[0Bgê:H<2hzVof#Xb|:8Bub+iS 3\FlIns"#(g-II#}![s@pSVUr9E:>aY,],S|ni zMf] Oabz 178}|2B84Cp=(7RDe9po'Nò˒gU9"v86/NZY{ޅ#g_z‹SB<$ӷ|ҠKy?eW,FY#{! >^zqHQQ[CrP,XECݙL8'7̠R[+_\!+$:m~-Fe{YuOK9m}S4޻ʥif9q#3{y$<7>♳I8mڝRhtU=&\⪼!C.q6Wfe ]z*J|k<mʹZu NBXOн_ mBse}\K*[yaG~HIs_Io.>A1 ɉ{dҌآ8hΤJ^c LDjb;Bh./x{qr`XIQ5C'W߄;&:|Fz\O([#{8b+{~ vZxt'(2"XM@\^[iT%X/RׇY(م\*}zϾvR^^W!R VVe"@b;v"7;AsCqWHE9U2wC-p&m@dNL92Y| |檳';\\Zoj~ZT2}P9_&:;p脓sstJ"2 7*KSMbmR߾y\s1(DJˇ՗=-0euhl :ZKۯw= %%i*Ey߃d lX5K ~wpK9:b3l-^_0C1|Ohd5UU= z Oul }u']BB:f=C ͘gX_C|Jߏ~P 5-=IQH]`WQvll l'+$%JRo[`=o|{ Cx)-ʳB{od?z%U`Vt޼K}S8Cqy9hA 'T1|NG}OV"|ڳV f?r⢦(X9D!O&:"e*Ә֢'Zjו]d ޾0$i9@i!xQ!'نTz.ڥNwھWJ ,r5Yug{C)m7 --]ܡDěp<>*BT?JvM `4+-g)mf L>,/vE{lC*G_CX|cy}D 49`ץ-z)= puR䘡)5έNU[@<]@|9R b~fKp+)~L7;,SA1X3F@KK#tŽMk *kT->劧2 LɬL<N/uy{v_> ?U07S[`*-}2ckɦC'>9!.PrKuNնޥaeM?`#/qMXpOcyC{ZJNwʗܥϻlkFM(P𰌢 !th&ZqH[|Ԓw_k=ujު [2K Ch=&X2rV<( ծoՋ#cHל̉Vhy' ":[e%C:*v~8sZȍ)^[i6{+|Ut,!vK5=•rjx2|UcIϤy4|m+پ]6*\I :}Z3{ >_yk'YXLk}Sʍ \{|~͸Kɴ|uonWOPoZ-=q×.aJذ?z?n? =9_&:pq`vϣ: !8Е@ēr}윖eۮ> ZϿӖX1N|_,F&j]h<*\j{[%BN2?[`yN!qg6y"peL$j{hsCd{oobf2{C!ہc|yJD0ۛ),Wkpu_jZa+ϱjeq޼]\9Yj,,<[қkY'զgGzz;ىCƟ<41qht^po+9;4\O"UA<~s}"y-ƂOLnoܕ\I *ڷMnp}:>XɌ,6%e˗qớWS`½`cվm6zVzRl?'z6d{7U9W⅕߼ѮzzJx$[Qa}epo_QLA/3rʩk,{,?*y/M/ js8xhmɣ 2P%? ZRm1Bf V}q߸ƱS2. E\5757}owGFsV ҿ{?Z<>5eףl ͒E?tZ`}^`m wB$xr_WlS=+-VWNBō98;p>v7=]ZVb!w=\Gn!;6N+aB{h1}-uo5E筋p/^D>khJRP'r.GuT 9qKIjB܃BԢ96HRoF6mJs˄Xob7֥ m4jiuuD^nd7 z%(\Zس$1E'IMW-TmO{N2͞ GRTr 52J}cJkJ r_nM{o/H>{wN rʓqS_~eO7m5 ƂTY|"?./^6!PNV|3A]y66/czTKJM{QSӏl25שd%o$83*fQ5Acy%c*D곲:a}0lX#Z"<$̺YrpdiJɸoL0ykÛEVF k"}&qh6hҪ￸)}E7kr<}T(hT}{ {[@w(N:og8W`*}L*㾱aTQKfmˁ9qk3,^$ '1֍}6K98 ^!-y٥u?-У}mzKey}^KIlro4_jlt.Hg֥@f#!d⪚uC)$ԛ=n)}۔}c KɼG6F\_ky&;yl Z^k3GB^K5k6q;-ytiҸWit%foKs!_6\SzEsْD? {8W9o!^[B>M/*B45޽&w_,7 R|M6+Uphlhv`(mgtc9rU=+2:TDzMjj7-QTKʭ{&{\HzZz%#nIМYAVԏ+/_^ƴt+,Si)Wj?ɍ0Pz5Fٔ ]bx6%~rU}1MvXP%s- !d*hy6i͛ߪArؗA xj=`ȕL6BՍ}lmqoj馨i}SV=?+Э=5|jmZX&>8J?PNRPzίy-sa''+(Pzl}Lלл:~}*Mj~!qoU4` mxDZ)T.oNQ{6-')GhK؜Y7={8W܂⒏_GՅZ`fO-.B϶jrg#QK~T#[@zE}poȿWB ϙU#<=1b^x#q`n$~{'hXګŊ[C])Ї,*>]Ԛi;o=0DҥSz7{V0ZjN~߸B1.+26v~uxibk'v{@{?'( =oqϪaʨ#Q ?\1m?jF:3FqypR2Bt6s\8 䑉D[!جB~qo^ŧ$ac#ez}0%49 {-*tڰ`;ϩvW1e(e)Z+蓊VW6vm¹ԭ#˼a]Db8Rwی{;՛.HA<;caf8!.߽ˤ7n)w<&L˻}GPdCr~mws[ a&:`M%5C<"\.<=:fA<'rIk:XIKHYY[R?qaaRh\*{n_W[dn7C TR8;åCp;* 6~mtw~η!Bb1|+7G lD #SXY3\TA^D:/{⽁F/Zz13xG[GQ$w_ͯ.ϭ,\ߩ1;GCϰ 9O#ir@=DzM}H=ݵ{5bq5[\V2O0$'2u]sUOʹ W[]vs͎T]p1)W!!PmpPB9@4x/7#ĕ+7 kz-GG`.懁~ kް5?~l_o޾q7/ v m>LIENDB``! ġ{F5>;p x];sv>@$ 1DSCI)H*pfO ƾfnμ5?a:r*O7" (-Y}<@Q W7ө@Pcz=u$?wO|{_}%[p/:g7oo?++_JY.f't? tb֤~vh}wK:qCm>14?D>.EXU|/ׯÇ`6WgOxa{ ޽*޼yr#Vv|W? o[?߿Weܿ?Bpo>p(r(p(^WQZoM(EVXDi(>GTTZMc G=A~ 2DTQՕ1>h+^-Gkt^!(\-ژ "AM [u5ѯhW !ʿͮIqd]+1CٖA oh8riHkRlC&q3Ъ׮XoI"4̈D!Xnb{ jPPlS+J- !0^Uv+ܼh\6 Ac'C_QP{Ԑ/K*rl_*$5NqXǒThE6B *ॴZȔk)8UMҩ $x'^ /]Hu_ȩA0p^ʦ>n(x˨ qC mSU_בm7wR$@F5/tn/C$EZCDrDI:o40Z<j!(_9i3S>QVd{%G֋,DYcBFMe ^ ]n뾣F/Em`jzʟJp:^sjM%&ߏF't ʢn=jx9Z)RM7xxv:Ia5ե-db_JvP̀X(aV?"4G+*bֿ^ /oʆWׁA8uelRbUm=Ŷɤ׷ԞMeO So3޲ƈ~74b;_ܣm9e:(NRuV|NEڠ;Ve-VwG񸳸m7gc]y>ٱ1N+z1Ǻ]XÎ5NpƸW3xfAh^p8z>l`3x ) ;ҫ>PE(o# Qn;@RgPgPfM.{#m3 / "6/G Zyb!'Vf.M7ċ/dz@'b'!x ٭0y~-nhSW+QIx!% U-:<Ռ1LtWNˆcO)2b5d/g'grE&pAa;36Q/7ċ5>Mk8;7z$z<^a2މTU3S ;'cQT$^W//&'GL7<*{Zy!9_"Vx ˓l+ρT/yi,*8SLnE&SLx9S*L wkӑdkpĎ Y2e-;ZZn$ ^=;XK=::6W^qNřMFihaⵜRazR]J&?seeY]!fk<{x/!몗C*~S{u>H^D^(P0/'TN̝ëF= ˺x4ܑEMc'=^-_ZzzyE](wx !J ~Gé?^5,'eZ3~x9jWE_Pb&6VQkڏ@h-^ܔ w3'rkȯk2rď$י&A@ĸY=f+0dٻaҪ`E܄b)\d/I)# j{xLnюG+PG#ۋTis[xa$ FQs. MË-YB "d<1u4X^%4@Z&^0nWFk𚆔Z>'Ǧ= E{8Wg-҄X֣55,ÙM6k\A "{I^7?:z!'[QdUwÐ[k=VgbcS}`Malqz؋${o$"îԏVh1U? `{=O7Ȧ' x7:=g3ΞC#AvFcw-"iXxf>l'$~vd{ĔE.~Wr+͒]4tnsPߨ=8(9::cf C>KMOWÍ|Df*O^ pu*W@ }Esh~'2Qj4d'g|Y|gHҎiIP@ġAK6=P2Bȕ(c,7 z])KX͆3&Jׄ1sJ$/SeJG5sC+ ^GTk'*jС)Rm?[-zK!6=T|Oj ՗Q%Ox0^^DO(L ãF\4Oū$P`C z<~<@cYE !&=Oo@S[Gŀ}_ˇXp89;4B&&4SJ\XK%961dNV^F:"\pLx)޼҆F2 S%5w_"< >U8qRF$42<;N&^.NȠ)`2;/XW{f1 2 UnD  Y3hT/QLk.S/L3-@0~ǚuXW\\'4;dHp^i,ThMq.^*45.TS"hRE' 1ln5>9W 4} &Mm| ] Dy*v`UPjSw{U2{W;x?S3w 53GOx5B iy&=s#Š~hClr s ď*r^-";GM|'[DqL FBKTt]׵Rz"6tʛ)FEۖHhSv:o *˓2H"mˋ@̫SܲԠ#!~vxpzvy JRViUaMk!2&(]arpB/NBKPm 5ઁ f0O/iޗox)pB3)g|Sa[ªT$^Mnnnx|rdf7o 0UED{涆_<]bқP %5ьqGMq)*&(usXA )&d)W!o%({s5ZnXа1DݚD} S>OC$gGt w֢N_NJxU +1oP䜕>rY…M|d2D'w(n70a$\…x| e~z cKDdlyNJLcj-l' UN[R3VRn&]fE4wEe]zqM嗕\2 $-k`B MT_+wgR\7ٺwDh&h4aMDi%y_;D/-d6#@^&ZeݪE$#D嵡cbςm.]رxa y-o%ʨlbMX_8WNS+<в#F4l#B9t| 1Jh<6bRo&^ o:Xrm>#ܓSh\EIHdP-N5?5\2}?IyXb&bsHNƽYCb. }Lh BMgF`oҚ̢*B#ÍLӐt]sB+43Za٩+FAb5 hMX>g@5è!GGdTk"jAU++)ᕨh?![.t xd%Ty6x5ǚJAmksU?YR՞<˕X 3*:*}czs3_ N4KV*7Wye^\j\\璼f)fn# jt6N/( MX M<3JJqG8 %,rҝX@^k=]|||^'!o%LjtVwxVx-z aO]Hq(c!~} ]&.{!9IIZ0ʒsK $Y>,D\̠ZöO /HLLȩA]+LSlH?^QN`kI2iȉ"ՋXW^ϟ8gnx?^ @) Ee  w<4\JжerxUjcy>FOjEG=d[Ǝ\1]ym]YeLIq`X" >ߕ[˺>[,{πfxʳċ;]E@CIO5YE2E({QuX!w)O~%pAҋ-/1譝wAsgWeDu.Z=^Z@:v);KY~E4rZ']*(/rb//a寓תe$(D5U9 tC6^e=ě^49ݩ{xQ,yԥ{)F9{){xeHW^9ENN9u^^xvw| N~8Y8b*x 'Dv+TVMDd 3F6  3 FA"LSˋb&F I-LD@=LSˋb&F I-PaC nLx}tUU}Y!1Nz&+ GSgtXƂ] vF.eQIЫ}g#z$d aַ{{9}vo:qg:a_~2n0܆kKx "IN~ƍ|S_7H@.xἜfw{MUzF (7Rx,fE4QJj|-(3[D\d;Fj*50Whv`F,&x1ʌ#uF8jDPeDcLO*&x; ow+:_⳺# A; P,w wYTufgPM#m`lxo G;Ův%cqm xOyl4mkĆ9O\-q"N@BbrA!? ?oO*l N92;7p)]gW>b w7Tx"˓8[f=O#o XM(&ϪwuO*×Fua,9Fc $dյU^Mv`+ֺyIN5_ #[- k(2\qr?56m8ݖPhtZU*w*ts^ʭ*W7-A\r9|rNxUs ,$jsOE\;՝fP9(3 ȹϟ4ʕλC*0`8<ǵ? ]j+1 ,uDz I 4hB:y+2q`ƓqDz\2"uTu`G Vy*m_ɫT)*2Nb1򲿒W({+ n SfWSfJb'Hn#ۄb>k.ۥ[߫ 7«nipLnPeO=Hwwɡ;BSPf:ʾ [&`H9C=>~o,ź2E]roɣdPfqJdb1zV{PqȭE|6b!r6(<К+﵌8͐hr8SʩR^l yrX858329~e3+j)G" 4^Yq`ʹ,uSԑ{Qþ~[mQtZުrj#^>2wc'o4?Y:ȯN|,rO牼~zU"gO8{t"u6~<^/G~5ʂ)GĦ  M9ؤo,69fL+F$ڟWFm&$,n wٿXM e+gwqC|(n{ \b[b|:]4HT]$l>f{/A3ߖZ|wwZU!? Ds< VߴUՉ-2W(ᳶ|ʌb-֤J ww}G_iR0D/"ن`t8[6ػ C{‹h{ LVTM*"3M Shל \awKدsgvBؕ3(2.Os5"UȯUdE9<7 XHFk"CQ@_oeTȐh,JvĊn!b,;woXW݇I+Wcb*r|0D :?ϕGVz+| /AuIGL 9xc29Q_&zVfВWeNb3'wrQƗr J\b2'(ߍ1[琿G~go7㲥`<}#Vp67a}} iP r)riW yǏ7!fft1٫r+H:Wa;.F_7^(xob-=ܒ<oFZヒk?ʩ9JQk;5w᳴Skm,N%cF7ln?f8:BrvM7|^iЏ]]!7i (a_@ֆO1勯u7f%8iggIX܃Q"Pҧ/ʚ?] ?WZ?aQʫ/2D|7բ./*|P7h[UbPFa(ywNߏ~3P09>A7^w xODڎmUk򩭼C#(a?f_zrgyF=VVK%ʩHEy#+(JrxO!W.GcG!S=B>g.Rlc_wrc1יI=XNݸN@,JAWwz|uNbo5xOs| Q;W:pgw}{x}c .M2^}>uiC6m/DI6* j%ND3~8r'?~ K]|U!Fy9&帼e'oxu?p0mM0n@=^^}'bJΊth;f{EyXCGtpjH~^ -y/ܷ u%e]sI3x?&Ǭ6]׏L1)^Dye|I6T6W&Xqxж*WuV^з-}V`_<%Id|?ȥCb~e8Dr`Nh_GG{H2QՑk }=1I}5JXN ΢%ؐ77ܾ>{09Mxw~-77S770qt?< ~QܻSgw'FWQ/ j"Cm|4x*\6NίƹD /y՗x^ٯu]6|]-ft>wVǝ[dnA=~uӲeBoN޼s&117e.* 3Ʌ>DzkߟŤ>+:b~PU>d;J׽[2Wzu3PQ }ކox@"j0 )F-Q^VMnWoWjNq?b[c eHE O .Ū|I^-\O`ՔBgj^~c<]@חbȫ >/L,%VZ'_}v}e{#fH{v(v~"}|RȢUhɜ Zف=PtuTK1/-ùq{1p&յ|z;;}F.ub3NjD0eZhWW5Nūfc(Jؖٴ9_W~>rVRn,hL}4ЃsMģakw;gߤ"Ӈ>bt ?>V/2|(q\ö1XBd0zQx㋥ iVU{LERDDvE'P_iEŠGHx_z'>F+f^nWv_Hr>6n6"?]u.Ԑdqy6C>nmt3vK8St~.eoI˼:'m{J4ǨF&؇ڰ$ sna%S`WXh9t?ߑ$)܂(di as<9&H^@-ef6c?]d+DrrN#r Bm#2;Ñŭd/-7eM?/_ٟvknڍíR_IcY~Z^JX `qb8O+QSvUXN߻ՉmnUu'a*f0uaU ʚ#u,ӎ+ M ?5'Y7;!sF:cx!ʫtE?|o' y8ߘ{'(gU2xL8CpbN+VCye9[85BkU_WLcgCQ⍦dr|fs܈a ۹˶ i#A3n+iXq,O߯Tz E؜:Z( vUugiy5c;=۱b[IB1CmSTfxP±NN *2ArmLH7펧=2q2]]9x%r~Ȥ?8X)WM)|| TRO UgKK̅ ؖպ4ӎJ+K=i+Lx 3|t[7qcI80ǞgМs6~z.<,z69,^_zd܆:awbmi) &ʩMfmSFr̦NeB)KU.rڹN{yUZ~[̾^e/'vQ_«WY):ٕ(|!RWFvd/7!(%iM~(%&~&2ltYڿJl'Y']KQ^0,,@^}6ë31nT:6}|cM}*^Zjk΋yAlPuTNbXk^˞OȵvW+NkZ_*5=Pï|JڡI;} 9};1Gl2w<1ʙrșo8ӼZ߾j0#X̲񔻡HEe둲bDXŨkq}*yF> ~Ն?^̾ʷ|WԯWx 7\} n-C0v< ƶ>v/B9Ne},&vVxxԜ_ Alv^9~|I3m9wvY%^CO H m=B wغ  ~$.];ιAq8̤>mʕ^OuYḞŭ|;&P%_+Axg +AGĻl݊hF#o(13;ij[啬Jm?I59Ӽʡ ?M՘cwg Êow[!X=wط.@ sF 4e^1\sSŏZxU6{Ɣ4z?UwÕ!رmُA 1'igj%o{cO;Z bk>Y6^U=Fdmfc0š |nW6nx#n};_mWq~5f_W k:TZν7+m ݞ0cW_}%K:c~n~nؼz)\V':nX 9;VyeQgEDCucޏ`W= MIJ Fb; /'Mν Ɛ}?صƈtu'.Oş'iζ]Y+x%ve7S9K:y+:lj<į33܀e>"[cvx0~$9oi!攳+s&:R054֝OW:eHcܰӰDb|a2#0Q}r"+[\ևa9]ܿӲwl+6Z^9װcqEʑ5YG ㊋10ړxy6c_|*0cu 4jl 3ΫBOĪU*6 L_0^3Y:ozh:bw{&P^[ƝΘ6mWr}e62/j͍v9a}ڼhb;ދ5kvlsH. $,~Z򥸒T~Q]ҕƺctڞ.= hW^r1d1B,ڱ- V$Kc/ǟXPȃpr6Nn0\dGԨl a{`"(l{D˼*^HQ7W,U^ecɱ!df$4*H5!l$,uJ>s0^?ͼ)n;s2 ]:^IޤQuy%/x[SKlEKb1WQx5ΟSa1IʎsP2OSFTi^(sVNuٲ uSօCuYU?vYm#{Wl!e_ըk]%Taў+gx9QTȘlu}5^:+{7G~4^U92#A)RCbշgy!v !+eF]*[kgXk3$N8HHge?2 Bmݫ&6J' !l} T+$V^$%ۘnYxĆë[,WP*{9”Wt?N:m׍W?j3BsӦ$̏O/OyGi|rJN˚dȲ{J$+X]5߯)E~LStZB ?'H~ٿkm%JUlq 9JⱭ%[ʩ{МWeށ3[}i?zeaŎ͸Gag=18k:^Lj~:ًuòѿz^-3$](t'}8:aU7-:x(|w?޵0,^A}x/^<5@#{CsH(u9`yUIGzce1x$}:=.:7݅ɱ QB%XWs~bNx7 O ְ6IľĴm݇;[Xu16NT FbPH{Am}C=nI `>cwp؍#p矢_%mrM wf#5'f^_=sv4g_cjb߿{ÐT2sy)~(Þz5dLj?Z-׉duiY*ޔSM3ū2`Ǜ:im)?ޚ9 $_zݮMt`r|So}XI8¼Kc` El܉@?xT[k7ҏ> DaHw4:;TZ^6uiz"mۍG3)5vaǏwݏ0NW|{9{xmy]Aps:MNAB19w}1gx~#]XD Qdy}OwuﻵS?|zKh:c/Ȟ S.fwqwBiF<,5X7c ߣbLI1^IuCb~нnj4J[j87qZUXRS19'q5!;SMK rN5]㈣xW*m1!Amsx_I43]'RD4Um#5uO;QifEmU+IUK"1o{4;9|S(z8  ҇J"[ɽ6M-EjWԼ";_n%knP͑3ôU R^unp//y.cVCW bcQn?f^5GMe#t͹+ ,]$~_j,{zb22N1Sss*~8M%gHUT|*-6onӚwK5:Nn,'ƽ u_*DmcrH'V%>҇W)3:bMu$)٘6) R`9e\cǁ8lIBaBs>(98^5ȪxʫjBLu{Ǜb'Jc'}\ 0#qZӹڛ:ν yuy_,Ìδ!(#5Gw݊xאc4ֶ_2$Y_\~xw?=/NDߞ ߍ0d}5;Q6B0v^r1ۮIO4cո! }axyUxv?n+imy8OhWMԋ~b_,ʤVePWA8ٴŪoȭ+;$c~©ԓ뼺ʅۿձʫѩ>B߫@eR<Ï+KVşx%Ӫ\](/.T݇Z2/Ft3D*ښWm}:ٿd郎Yi8pȨ/ǎ܊ܵ IY}͸ Cy.K0ΌW8xƂ"Sj2׮r,Nsq;G_j׿-r~nڊc޽";+&ZpJ^% əh֙RK70JIp52 96cM}[wlZ>ap#oKroyq2[)n)l=?5AÁ…r%'fy}6<}/ZXR{N’sPLQ&19FnȨ& _pGEOb8b%{T;M:|qn9{G|QNg:y -~YAH8A+Ȳ!j8>$Rlo Ɵs2fc_b͘x͸sa\pd?ߍ!|{7ޚ؀TݻAmVT,߷3Oc*Gxmx@8UvupmQ| $l3Q0z]ףϡz\t5 +4 N ϯU^ ![/S#*NMy3̫~_},Es{0\yɟp=pmfDON:tF͸xdɕb-u'l*̝05RNy59(aX#s~UR0<۶bMZ tV2vë߯Qoz"^+v;J1Ŵt*kβ7l9ǩ1'rI[g{q"ʍ\ߕv&/x(-.1J+`)`QR#fz:a#Ƹ:Z~V b3fO}xjI'oliCwq~Uߚ_4IJwRgկL^^J[$.'ŴWC\~D%Z F« /?CWjҚȤ0#1$AjKX­eRuəpeWG3SP0hO5;rf pr+)h!7~ G'YNx/NegFds?7++f}RGyU/a%ebm<44 {&eaMy ;PwbݤNǡK#;-,҆ G)aʏi/oF~sluvp {; -ޏV]&k \!hZXgd,}Oc.A[DAxk=S`X,Af$o:PokȶWYĊ )jΫbmey8Ou"bmk_洐dennoDYF;˼~yÝ!e}ZN]Ռ?jjb_5{ϟW(|ԠҚ %v~B{LI죬|\2Y2 Ao:㩛/Ds-MOLEn/ǓѴӃД=!Uan2I'{&uzYȶs9s'yv.9nɑ= Ѹ~CKeNQ{nz9|r]dÿYoyA}?ljV z:kY 5p|xQ*Kt}8Z,5ȭ4X5SReEU^z_gbv|</ 5f)7Ũ8 c`5eBQLnD!0A{d}KJ7YkdUү\j_e +3$^sOG~յʫR^w!w' #ynGobNxLި3Ϋu+ѹ:tIv.{Pfx!vo,O,:'cڀH=9xqW\} Fx#5C̛K,w֌(Zc>nC zMn38uZTe 5FrLuũf>\s4fG8>>75{fy~dч1ԇPv$$',4T[emK< mxoqߗg?DG' w.W%xSSKIDԏ{}iLxw z)wƨ%rn(kh̦qY6@r=lC7ʃp=Hܹ[d> R1$kes|Z0S.:QvO,JjiZ3INIGm857Wy%jZZ{b4D50L,u aʭ4əat}?6 ߣńW{~=- uɭ0ܚ eg>vZ|)R֤k-TQ'N#?SbPOwGy5φkx}Qm~DmނDY۴ C/Wy5 B;2פ3Ϋ_*ndf:n[rQMΑpKz _.nފڴ? <#;a7]?x}@,i䶓=bb=e<)"#XQ N  z}ג;w=kAӘL u?ƇcsANFIC[r|nu' L,3nq5t֟Jl-QЬ^ԭ_ۅS)2SHH[nY6Al{ xU/Xrܿ}ه}M05(xi,ʺ ED||c)uPOfB*wݔ}%6='/g=#Ѩ÷xf<7xѳjr&r/յ"ri.xV3uFgoG"(7 1|.[ rhB|ٔo/GۋhTʷ@z; jS_ێ}7_`P1.?w}JzqF38(8 Gk%عhCHݹ> lWe;*H|ZUڦIm!-qwY c)h/UOţ?AB}d#.X]z?{BqyP,8+N9%uo5q}hCj}Q柈gؗx~1 m\\]tmRb iwGi؆g&~g2mr_>%/`gG%L$^oݏ^]I,ԳY,u4uXd磭T!E4_'oiZW3xo3OW7z).F>B3ZVlZ6+'ᕜZ2+(ɴ}Qr)(1;*g3R2߉\Jƪas嵶0##v ` c6ŬuD5`oRJ0]sYkXXD}ZQı0vɘGYlwm7I3فwAȤ,N:wlW2WK[A5m&Aefe\3ڈh2'Ps%۬ܪf_44Vc&s1\˙Vy yLVS'ᚯᙀ8quUU\-oJ"px%J5C1=9_ Ș&;z/Bkdq0f'?.vѷ`[!b9V%[v8VS$ڈ?ʊjn7S ]]Bt^Brh} =}N};>?۸J~Y% kJ󑶀w}JWF~uQT+6!QQ$&dG93ׯdF+ Ok؀糜{~:IWfdԒ˫(C* WRa~(ѽn'8l|sȽ/G +{E]1mcxÏ0~|&Wa^~XP{J%:H|;YD: 9|y)B"˴ {O> `n^9$O-!ķ&ws x-L ߌW'LRؘ@Y&/FNQcC] 4>F6r vu\A;UQY,J\R/K=Uy ݳ*HmdzM}+&u\N-SA5cObcToD6s;8g'mDӗJ. Js8g]x{x4ǖS%Z2 \2}N|[F:zDeN'/'eXwИ+D8uJ!" [|fǟy-| ?RgjWk7Gcݗ#Gb[@6ǔ&rLILXlc!a#__e627/*R;Q4[V<.Xgd{,-:[42C,Ͱ~J^k3F!s6NZ[r[k![ em*g^V^I‚hDUwFcY፰vdOeKx lr0He2C0v@197x!c^ OzchiQaPwGH#M`7/=ya1<1F-oJL`^4~xS6}\W\~xNL,7zƉ5k Iln DY`2T=@yۡ7Ҽ]C{>,.x5jbߓPX'F+?2£Xx?w=7߭cxXƆ{wZ6 _(>Q||#/nn{bGA{~;``-`m{F)>B w!]Ⱦ®K-|XuaunƲkWWYx_XO}mx뢿)_o\+]i+&~bU[{ݪXӻby~X| H #'P M_G^9ZcG,?t"ﷱF 8c-AV^Ǿc{9nݣw܁݇v6| y/=̇xW`ρÊCL(_;C#Gpt.đcǏ1= [q`?p[8o{y:P}쩷Y!m;y[x{#7~ػk3܂y=;qhvܶlƁ[qxٽw|-(lvnV4}*+۷āMt4 #İ8WL$$If!vh5 55: #v #v#v: :V l H#,5 55: 4TDyK http://dlm-network.org/moreq2yK <http://dlm-network.org/moreq2DyK yK bhttp://ec.europa.eu/transparency/archival_policy}DyK _Toc201478390}DyK _Toc201478390}DyK _Toc201478391}DyK _Toc201478391}DyK _Toc201478392}DyK _Toc201478392}DyK _Toc201478393}DyK _Toc201478393}DyK _Toc201478394}DyK _Toc201478394}DyK _Toc201478395}DyK _Toc201478395}DyK _Toc201478396}DyK _Toc201478396}DyK _Toc201478397}DyK _Toc201478397}DyK _Toc201478398}DyK _Toc201478398}DyK _Toc201478399}DyK _Toc201478399}DyK _Toc201478400}DyK _Toc201478400}DyK _Toc201478401}DyK _Toc201478401}DyK _Toc201478402}DyK _Toc201478402}DyK _Toc201478403}DyK _Toc201478403}DyK _Toc201478404}DyK _Toc201478404}DyK _Toc201478405}DyK _Toc201478405}DyK _Toc201478406}DyK _Toc201478406}DyK _Toc201478407}DyK _Toc201478407}DyK _Toc201478408}DyK _Toc201478408}DyK _Toc201478409}DyK _Toc201478409}DyK _Toc201478410}DyK _Toc201478410}DyK _Toc201478411}DyK _Toc201478411}DyK _Toc201478412}DyK _Toc201478412}DyK _Toc201478413}DyK _Toc201478413}DyK _Toc201478414}DyK _Toc201478414}DyK _Toc201478415}DyK _Toc201478415}DyK _Toc201478416}DyK _Toc201478416}DyK _Toc201478417}DyK _Toc201478417}DyK _Toc201478418}DyK _Toc201478418}DyK _Toc201478419}DyK _Toc201478419}DyK _Toc201478420}DyK _Toc201478420}DyK _Toc201478421}DyK _Toc201478421}DyK _Toc201478422}DyK _Toc201478422}DyK _Toc201478423}DyK _Toc201478423}DyK _Toc201478424}DyK _Toc201478424}DyK _Toc201478425}DyK _Toc201478425}DyK _Toc201478426}DyK _Toc201478426}DyK _Toc201478427}DyK _Toc201478427}DyK _Toc201478428}DyK _Toc201478428}DyK _Toc201478429}DyK _Toc201478429}DyK _Toc201478430}DyK _Toc201478430}DyK _Toc201478431}DyK _Toc201478431}DyK _Toc201478432}DyK _Toc201478432}DyK _Toc201478433}DyK _Toc201478433}DyK _Toc201478434}DyK _Toc201478434}DyK _Toc201478435}DyK _Toc201478435}DyK _Toc201478436}DyK _Toc201478436}DyK _Toc201478437}DyK _Toc201478437}DyK _Toc201478438}DyK _Toc201478438}DyK _Toc201478439}DyK _Toc201478439}DyK _Toc201478440}DyK _Toc201478440}DyK _Toc201478441}DyK _Toc201478441}DyK _Toc201478442}DyK _Toc201478442}DyK _Toc201478443}DyK _Toc201478443}DyK _Toc201478444}DyK _Toc201478444}DyK _Toc201478445}DyK _Toc201478445}DyK _Toc201478446}DyK _Toc201478446}DyK _Toc201478447}DyK _Toc201478447}DyK _Toc201478448}DyK _Toc201478448}DyK _Toc201478449}DyK _Toc201478449}DyK _Toc201478450}DyK _Toc201478450}DyK _Toc201478451}DyK _Toc201478451}DyK _Toc201478452}DyK _Toc201478452}DyK _Toc201478453}DyK _Toc201478453}DyK _Toc201478454}DyK _Toc201478454}DyK _Toc201478455}DyK _Toc201478455}DyK _Toc201478456}DyK _Toc201478456}DyK _Toc201478457}DyK _Toc201478457}DyK _Toc201478458}DyK _Toc201478458}DyK _Toc201478459}DyK _Toc201478459}DyK _Toc201478460}DyK _Toc201478460}DyK _Toc201478461}DyK _Toc201478461}DyK _Toc201478462}DyK _Toc201478462}DyK _Toc201478463}DyK _Toc201478463}DyK _Toc201478464}DyK _Toc201478464}DyK _Toc201478465}DyK _Toc201478465}DyK _Toc201478466}DyK _Toc201478466}DyK _Toc201478467}DyK _Toc201478467}DyK _Toc201478468}DyK _Toc201478468}DyK _Toc201478469}DyK _Toc201478469}DyK _Toc201478470}DyK _Toc201478470}DyK _Toc201478471}DyK _Toc201478471}DyK _Toc201478472}DyK _Toc201478472}DyK _Toc201478473}DyK _Toc201478473}DyK _Toc201478474}DyK _Toc201478474}DyK _Toc201478475}DyK _Toc201478475}DyK _Toc201478476}DyK _Toc201478476}DyK _Toc201478477}DyK _Toc201478477}DyK _Toc201478478}DyK _Toc201478478}DyK _Toc201478479}DyK _Toc201478479}DyK _Toc201478480}DyK _Toc201478480}DyK _Toc201478481}DyK _Toc201478481}DyK _Toc201478482}DyK _Toc201478482}DyK _Toc201478483}DyK _Toc201478483}DyK _Toc201478484}DyK _Toc201478484}DyK _Toc201478485}DyK _Toc201478485}DyK _Toc201478486}DyK _Toc201478486DyK yK 8http://www.dlm-network.org/DyK yK 8http://www.dlm-network.org/ Dd :$\  C HAC"" kbI@=kbIp'YQxZ}lTU?yi3 Bږ"XTWV "DĨ5ͺmq-?L0j1{̝7o39s{9wߝ* epNyjz(K 6n:W `߇~@Qн7\e{ݩ~=0Aհ0❁`IJB? DcIcuy7| ^Vp,L1ԅ`lF^a$c6wkL_ϓs MCcn+׵j`cS[}a7y3bԯ~<ؒ|,y}خ wIw)_[8vhbf\H H~k~Ig#dwj~~f%lxXկq+c<'_8D=}ݘ !3O๖dn~(`bj*ﶱO84~,q0/8zpl([ּ:݌e._r㩷& WDwt/o0:ǽ& ?/6h65d5ľt`  -h<[VAlUkE+/qU؂$&*-ݳ*|it=Ja|#?q _/}|!{c%!b.0sgP[ $nQP,>]d}j9nsU|vm#̵Ƙ,${/tV_vaXua> Oϱnx1WmGK~̜<9yՙYsbɿ -.<"y 52kõj !n쯅drαIk spҪܠgt֜XYN_fqUu܆Bƛ&mYͲ5SWn!#JX8VaK`z?0&a,9쒰OXN+3zy6sӜg6?A`X>_}UKB yB7cc1gL'yolutҏ3^b_G נFVN%ץAE3_Dnxe2H{Ϙ(QςZQOoW-H-P2}^^!;-kռ=/-Qo~$.:( q=iCm6PDZ74PC"00Xb߅HIxϨE17|:{eSI˹ܬ›:5HyK/$_4uܧ1-c Ǵ!:; fϻw Q!䝦U_wkO8_t~d~ wOx";MQ#)~5E&WS$DԺaʞp"'ͯp{&׉ps`''*pB1ݎ_{s;5S Ӗ_ʮQj/g_IK!--__^EK8?_FODq GY6\f>c(o?ʯO\ϯDמ}q=>l3h~AH^Rz7ƪ1}~/bRRT9+29PbˁXlpEcD 8:]W/~=<:9uܑW#ye\ڵ^TPz  <0|w g y/o4h$Zwba߀s>U,,xp].@j*X<),g#ZiX,tp^ct79N3Bߪe\m*bKO@YV1'B=/'V#_̪s9 OYDyK yK 8http://www.dlm-network.org/&Dd /F>  # A"`"+&x=X)b3&;&@=%x=X)b3&;Da 8$v5<%x] |Ed292&7! $2FH &rFpIccEDUQuEV O]Wu偫t:0Iz|~WtW}W]_EBC+7A>JH{!Pj"t!!$KNHqψ vB~'r;BB=+B}Dώ"p CpE C1~vB$-Pg;H ޥ.\ א}]ⵢn.vE\D㵻A{}YdBDr:VsT6ktz>GRg~T&'7ydSgY6[&LgVŊ: pT\}-)D8acdng<ɔ6:xM6|mA(kN.c-/$2VJ%HCY]xvff|ݠ^KXivcn> .I::n8w<LOS3>>/h>J>1|}b);_+O?SGx,X'"uI'D`O+u)IHDEP9K'vJ='G-B@D(>O137+{;Y|}"JO} .}x,E]>a}"@> v83j;O\\aLP6'.KVaoo$\'&)r-w2dĿ2qaAoMo!>Ƴ{Nƍ]Oﵬ&kYiQ:/\ɴͧ@‚lX^@*3@zߕ``5 >G^K>1Y;ذXh ڜ d,9`Ϧsn  vb! Gx\<4bz:Qr.,pS 3(k ÂSBLr=) Nz,rB&l  /ziv{Q?r|} ЇYv_Uq޿ WUT>qO:9[ ,x\KdH5Ox)O >KǖzǖiƖsǖ޺+|Ɩ2. 8KǖCbE*/2ز>4j.麰Ўk9R+g ^6^B;ba:y g0,t[و_)6*>d.,dpBm,HPc:X0 ր>+k_5EFhШ] uaRXԞ~/U󄈨 2.5 } z3Kj_[R4ԨXwQ \"yK@*λkzl YNhefz{֔$oT,|=d.7;ϡB`tP5Tb0o(;sE'$U GE"Dg fP(o2P!|^e-u 9bs qr{VLk*"2PԒaf1@Lﰘas7XUǻ >b?΀rNqBwĦbxGt̀x Q?Ĩc((ڼD,x:ta^аr&33쭛 10^ GH'qS ?D"a5a*!MPub9/7n3n7I:!cKd) 7}$d,(w#ءMj;Bw ->+w3\# ?6\mt{P.%"Qf>kʥ}uriH:砛\,㢟~ҷy,x3@;S`hvXe^1E0}"J}bOxމ )'lO|z uPH,X o|'i7t}s{,'D⋣')>C(GSYЏhK}⯻ O|}ȁCc>1mj]ecz]-:}bO0lpLZO7~|P m=L'A8|N/)ZXtY.K=A>tR~xD ''n4h{BmP= *1ѣfg $~}pR}>etkݖIX^; Ig 36$x\O(vzF߅>Q!bNB#'Bys}L}b70!0骓ŦM Or~hN( 3uy^.E(}b|wNp'vIcbN؉;u`;6u݇łuޱSN(^tc&k dN%O'j4vJSb'B'0w/f;~clynw5[h{,RДǂP:C0]7 K}Ls"mlPBs'v=&{Z%wh/ Elڡ1_ǂgB%w(L:[ʤK=eCHC!Trܡy濼_}sܡG-R1+ۏP:sVt9Cuiܡ,4whF;B'Ek&u<{̿D.6CǸ_8b,Xw9',:}"Z{.V2<[qFO}`}j;m^A{QpaC&s qZ󽩩?Y'94ݫA:rwc}OZG}=IOҿx&BD}7Q,SY~v`,XU'G۴AP8'= ;e)R#Q!m8Dۧў!h3VuыGG5Q*: $t|1G*qFݔtpX-vJL܉6ʡ pɾ7KƹvЎs%D$U=dph9(YnTĂ|:94NCPz{'%w(c\ШP֛ٳjc0¡XWAen̡xn83Џ-AД̡+͔C߳(z넝N ysh,a:C#Y*Ϟ%ϡmhCvshCg̔C,M9ϵ%^Uȡ'9Ի?>rCst[=NÂ)9! J1X sZ;Ў1  sh rˎڒCM<%.k>z_/U4xvʺ2,XM;=dD$¡(f&(Cx>4̡p_(ߔC\[r3r p׶ &%RpܤSnĂu=$T8ԟ=ZC@9$CvshCDʡr(kK=kA6{4g必v/[4%]["}w,Cӵ9THOn9Ix\c9W u;u-j;P /&?8t5~S3jRqɇCwx>yҘCq9'o)bNn}b2y)#ܩ&Ї) wV}^[)c ֿ&Nl, %r'+K;hwJ(ܩï1 sgdʝΔ܉ڂ;o5S3z4\aȗ9=emsƟvgD;1 v91V.P%"q3ЩQM9ϵw?q';P1vJcw{Jï\=trgfOJc)IeS?Jcwc0w/8ؽ&ϵߙ5sHw Ħw J䏿)RHbƬ%R%0C#!$Ƭ/&Cg^̢([#&g;.}&ō<77*"!c xAÁ0NW6tӍ<~A,$EB$,4 `%ιd,D,+( \?yNF\ibE/8` 8.,4|ǭYBB u'ϷG z`စhM,8psI+ZƂ`eg6@,gU\ܛ5ch"Wê VXiG׫^^.-ԨXC0#F/慏 xxaab BmK  Q XX6/,.b 6L 1   %/ / -w=}Ź(GldF*r7\Icrb1n!aBF9`$/ oHRH=Kئ)b\̵Sܫ>$rHS Fh4`L}12o,bdh<9difϹ3+\6H9*)F9g9sg]Ig]Kq绍:Sz#0r_A9o& 2F^dAp[t5>y&}Bp~~`}A_'99p&hqn,XGGtҳ蠛t\)K#zA`K:y^k1w]=# ޵ ]+厘UMNʰ`=4u{bGܻI{{7w;Bm7ρ>GsG!i<#p\cײx28Ĝq|}8}XX2>ޞKBb3Q&XwW$7>U`A p%Am[17glw"[g%+xs1֫tX'bzAH !xnH. /9E~rƵY}XlNkB`,hp*`j+ |DY׌s*)t|+}'ɶsLC;8-)B]vlca ]`=WH .@Ƚx`#ܯa1U!̡a CW.*s+ېCAAHs::S YACYvGx|U'bP؟AJق_. ?Nx0NۧC(^>% 1O<'h?'z:S{T]`Le(ݗt|hyuiȭC v"WW pw(_xmʡ6g8tVC# rrǔ:,X͡AʻtRNUT8ԟϡ78(u*CCvP=ӔC\[r$'gcs(i%VШyg*UO]948eD$ϕ¡̿z,VP@8trbr(kK<9޴(?9T_R+?V)9jH5,X7gJ~ʚb̿/IQmym6)c; sh9 m[๭mXڀm^:ڀV6* XuxS87/ˡA/ dvHR_?`/`o/3qtՒ]KGb ɡ{,H:CiRe)R{,e~0(e(vBmPxhLS'jϹ=H!*>! ><|Sr)'l s~NSBJr.J$ǩO4S(> z×'v@ %*s00o\l|!i6/XEpߑf0o:Ŷ,kiG]F͏y| o.,oD _P$G -_y|>z{-[Z0bؼ|I{.,WD3&x>|GJpӫѽ{iQfÇA٦ |K9\ {^{Xi~m^{pb"0_>,'D;׻@|e,d_„)aڽk7X@"| +ZHc!2bpJXȫ[YXo\,`0Ix!x` -Mr`9L\V)7Yg]C3Obs(Bn ZHXNWuڸXx K| }U#@5sa >A{AeEfv}Xޡ\E\ngLg(Mdǩ43(sOl٘]es 7^=PIqwqn6h^bKʘ\`1wzf |"W G)*\Y 5-ͪi)of7BqE)$ۇcpl7o > Ksh:uvmme Ɓ@Cy/'ѡL{55?gO?cY? ;_Dd ->  # A"`"*mKP&qS@=mKP&qSϼ hp;x] xEyf&LBxBLȄDc"AQPj\0+q/(>BEQwOv|"V x]|s'L$wp*==UUBFBI#l,![ b&LHwR9!BZ 1O2! Pehb"  4 $ʉ =㱳TXi2m&|=v^Άs;MdsLE,Uh|kip{*^7!MZe+@ vY,M.[Gn?Th~_n3,ʈrD`0;!M!b/R 9|wȎ6Ąml#/:FBj$ {5n0bsŞ:npS&ܤ`:?5K>pʧ PowG7c\#N@> Ҭ=[I\\ZW`p:h QhGVʥdt2:P pY#ZDG=懹Kqbqb!yx5̘?`cA~4v1{m}L_`N1QmWb>qFL@V1Pc,LZV'bhLw;/oiNGJfI{͒Cc+Q,:wJ.՘ms&qN.: ͝)!&ࠟaS yH=ܞccPL6XІbضi]m&fW`911&Rc uõu/2j}(X~VpLi.1lWkZ]xL(&",lx `?t8 8):&h_cchL{LOo]^bcƘHW f3dQ-\Kb"DWD!-!3Ą ivBC{NcߴMmD16\u mNcp\eq-ʾbc"CcLtSf6C]ג-c"CG1q0`lS:CLvA;B; zkcWІ\hCJ,닽$=)11&O6]QK?ȵ]<&2uO&܃D:CLVT; 8&w%k< w*6TChL|9?&X`'ߩƘ@7Ğ/#) K1ѓD;a<#_4@|?#X5d wcjnlPpk^'Lލד]Y{w3q#lۚ &Hlo7gROAHK]Cޮ\1Kbz(/7P7,9Lnÿ 7\=zd&Jc宬TUq&:p/`g`K̺_=k7; Rg~~b D\! An\O , l8V?aLl_&>*ﲀ}iJ9uV B&\~:vk6߁6ԘXϸ^'~˽k{f+s=\K8,5*~ qL'zk$ v.s+8G[[GCp9`hOAr4>Gj9xNgq y#sh輬; U8ȘܺҤ..]-ۇ.Zr/kT]onW>B V/Tנּ6_NfFɁ!w[́@$~$~XaXޑDcX~|m?L@8;5I}$fWR~\+yR'пc "OMyRKɓ <͓5O21O>\̓'7YyR( ~{/4z|`]5C<1 z%^mdrȝ78;'ȡ}9 o~q;оC5kü šCANAĽfC8t=88nɖF[:Ci5}9. ЃVCs6F]eCs(jNߪV8q(b9php8 ks}ɡ_ui( vh'6ʜ3]ʜh]ﮥbHk˸/Xw7$Cw%χaƲ˷'*|hPTX,q1g>E+h̕m J4LuwwIs)ѾhNtE͙.Klγ#s-Igxpy8$ʡ]>ĵ|a (X͡9t:6-qpp@Ρ:IC] !ʡQ CKz 9⾎Гug%o ["~ŵ j˕%Wx bCȡsl3о^yfWvC/:H|hcCq0p#=Kơ#ϡ2^LPS ji|hS5q)Cwx·l} GkS}'8tk H14st\;cRs{[ϝ; Zn;L>~`r̟f`pk!f3}d3 w9XOox KU3?3ʝʝ[Rs'BUϕF(WZG+QPr`?DshN䈧<8W}+U9h~ J4WSɕ;{ @r4WJ-Jw8hty:2W¹8scyaŲgp,rΟcyw}2OM@ #5JBϟEYgVF\i?+!:6:68gyó"Aik2pC(>k~>ps37},)~Nɉ8mpKۿ+TF0sAA䚽01b!FmW0YFxyZy&#[Z;LjM a$=LLA;0R2LLmQj3P4F⡲ahkf-8u5J{\]F8Fb/CHdę̴OMrS/=F>|12̪#0hF|Zc$^|ds0F>B/F~ ,vMqG~_s|l'gs|@&۹fX gLm R@&x:ظ'vnN*qHma圝b^ц0*Gp`%c%QX)V65Jl΁ڃkOkKtAMʵűvZ2kG ߔ$ͥ28h.4f[Z$EFRMh,]>c^a5yM613LoRs`̮x\RĂˬ iE ~,VЅc!Mgi6A,,u;t^sҁVVX* 꼀)/`!c0J ;WU}8Ѧ M ' O8q,dsT)Xxܳ?qϦzJ-cڴ`!S_#5^պs,d 8gz+xjƦRbav)P7LfσR}8z뼏+NXav&0{niCNV=i-a%٩+a`o|!k+}9V; V8cs`Xֆ0үuXS Vq+ +3P:V/.Oz_@>2@=7žnVY^o׍{VR}ۯXX(Ԕ X8/MsG,])2}7l ;Z0H. bvx%,uWXoX@R,ߝW,I5>:XGJ_EAAKsr8HZ Ikܕ.ow'еoOT9Tt*PQLX,^;BIDd $ 2 0  # A" Pؚ1Ӫ @= Pؚ1ӪaBHg x]}pT?{oC $D(MY,TYƀhS 8 UZ@fL mQJ;IZ8 h5*A)wݽ{odq1w}o;s~9Y4،R2j`nRU /'4 pOD~4l7h&p+A@0ǂ>%4mѽuVuXZALShM gĄ.TX<"X5v 1H04Xi&w36;pKz)lk1Rho:؂uCΖPc׸p> zRG3u# @pN[=>-\\ɋ|3]g8G:ߌu&(Rԗ׽;ONMN5ڢ>!q9 `!l|:͍oZѦW=}nOLR8Z&j*xӿiF:YKp4Dh B2,֣͂HAJ}~`f!t0DW5ƀ'U׈qΟ9_%l[F+Ђω!M`T3^ 9iv'M+AKFLyAߟt0JtM7gZ]8e)Ծluym[7wX a6bw6w=ʓ`ȻGlNt}Ҳ稶_|;(J͍9Z9UsyϤ alj70E"Ӫ&îf=cpB&9*P;K7nغm!b}̻ՏQ5}:o>=o>;Bn|N"&lK,nuYyr#~’U=MU][pYn T O77SR(O'U=5miK͜c Oj4wz~I!̽fM[%Y}զ۰-E`2>IDVݦO%nxԓޖ'{~q2qS]oΑ"'-Sw?(z44^4#9?_只jQw({Npi4 ɲcq6רHjVNrY9NYp ~0c2Ը Bp"kH} z{;``7NA73A*P/{B<>"1)א=+y׈Wv<.ʣ>xLJ5կ׼^̃Yau1A{'MKǾ<B TA2:ş#18>M>p\'ʅ5ּQLE3Il:q&(uv~µK^eچth,Do Em!#PQ8#|l3~`Ο}]mk5I5RruNgmَ:OXf~f+zUV R_/pdЅ6Rho(W ZAb|ߵ|߿}}>TFVဢMO?郛yZH?dXn]'MHys5ô>mF؀vh}u)X[ɘyC2ra 3?KSZ`,oymOX멚3!wsO/ cA1ujh2׏e-ʻ^"1E'5_lxnGky}#ouvٕF!ޫ N~xc s#N, ;A3/`iU )o1m[-ȫYnnJ$:KoO֘MO1'vCPclXFt]x%"hX.^/X5~j8uP].׾3[5:Q?.xOv}dqOp7ZVŔ QB彙w ~g,LR[Hl|,wv6}nkt/4O>N[UcMA;綤uT쵛k{©Ǒ>.cj)/u/+-e_0E*|,1acGm ,\{>X`3\qg+ޛUĸjۙΉ{S>&Xqg2;X:}p~#x"WW^8N*dAQq4q ?<*s +v͂Gs;詬F:{ᎃUzbLe8{|;)W'i\hE͵SFۣw+ 7ʊ]싕z /7:/lԟ/ e_l6fkV]sU}BWq1ڇV\O/VbCI|>y_L]C>RNedОhG{I#4e -LN|lh1rҬ+/:3'/6Y`tx\9i`sT;Vرd^Ν憥B94|`c9iI:V}F:''-n[Ȝ4?.RNZeCE>9in;'-|kԜx(0x vˑ9rYrȆR-qޮ(2ݠԖJ܇ܷۘp"g^XۀD7'~h]2wGO|~ůo/)ɓ~{];F |k =ġw> l.mChܺ41|ýDd > >  # A"`"+>:@b$-2vɲ @= >:@b$-2vɲA /Q x\ pE~;n~F#fpAb.%WMypJ"T3d$BE]ga:FJ@ ${3=_vKY7v P TGl<@r u u V<HCeF[R96wilL[8n5'՝4u8 7ʙKaJZprR[lg, 4]DߞR4 34jLKùTz8&˧C4:(P}_3~ ,MmezƉoD>͇}u7+I 7f(R@3z% ~k7-cӥ]ʓ^x/mc`y{GH`m֕w dc2ʯccU,Ozo/Rw$nĴooCٔ]=)$7vj { ]d3U~\pn-BLe%<&כ-N*b^Y<{%]/Ep j*1NJLjY5W|lh唝JvtgH;Q{ODvCu`1j٧lU3Q>-8U28Q.J;jԵʘ*NT8v賣\@;xe0Xf?"E یHu.VLZ\uE2ҩ]Gp|\ķ{37jpAeKO9uȀ` 4:tY?1:tp! :[5f]͛r"*A=NJː?ST֔S㘮؃ݷ=,J8h{T}8k}9v-})E?>CR߇(}h!:K}HJlb h!>7P"x*U~'|3)۰#Ի.5fJ{lO2dk&YYKt>{Q y&0nfW;k>+}yy>Ou8ʧ:%<3 lhLt;;nAETMwOw,wm%t^} !N9ϊ@C(GqOl5:#{sfďC~6 Atžǜ:fNGĜ FKw̩e~߃?2goҷrn.Ze|ʖOЌO#©[Br.hWzLlmw'<Éٲ-̎Z'Q]tzyvkϖW RXp #MKPmvLl[+Q6%<Ϥu Ja,?4mo3΍N*[b [}Gڿk$#8FSK8tƛ6iwp(g KV ߻~/oѶzMwDgߕ_qLW&u;i87>Q~X6{}])ʋ\^cF!zCг/>J8?vb&pAք 1_Pք7q~|̈ oMPo}~uQ(Bj㭤_E_-F6j;W=Gi׏EEf#t0Be94 \PLDj\Խtji \jpqA~֝ ?.d a;Vb= iÞT__%er8E/>é!}$]_jħv)*" gQDI"I2>]q&9*ٚkHĘ$!z$czs1#A'l#F#Rs#:T2kዑQh0b9qqZxa_{1El}F1ÙH0H%P#8d7.9SqtaJ+FCE?y5OΩmv?C2/ߡ>G^[@e9ZlDw|]i'򻅑~`ظ0?6~`؈՝S-.iH{HNsڱ~qq9q=\P1shr5=pC騡sc%<J9i LypREtJ87"75y lv7[wdQ/|o#3~'@2[[қ97hp;}=LgI7aloc`fՈzJO~_+|{Dd #&9>  # A"`"H{f9(}&XH${@={f9(}&XH|S^zx} |E~͑dr$€Q@DfBf+.x. ˱"t%. jPPEtS[w׃UꙞNaUz* cl*>_+`bIV߮b>1 `b,E+[3P{¹wv'A\:dւ͟е㭒k'vYї: g ʲUw9Bqv R8z *)uC upN~n`Fe:ӍgUZT4vyt}fp*ǎ"W*SU9(|߼etRe.Y?s |WzVɧT Z)_V[xT>} hHpZ2 C U궰Xιq!3 Om߯z=}}HrON۳pi6 Y!.8Ӵ/˖ۈCW tm#6`9{>k\pslWG⯯ͭLNr-sqd2EE& m̑l^sec^]eCyI<>*r_wnR>dp.$ T- .ՏPpqϓU^x,lJzaUՋq^x{%a@1G§.#Ufκ"I$LәyUEMPE1QpC=zW~^êQv`LLQ1z )l^>| ^/szXspv#VWC0v'szf9kkq~e0&YK>yKaySdmMb=ܽzI7f1&9cN;s>XڬI|?]/֌Q8(b_v +_|!/aQ#K{畓}U`%Ӗ`Ez:rq[#qijEe/2b)QJ^QML=eWe?p^jʋ8/qtU(`&SkPڀ~6Sx7JyE?]x7Fǻ~]Ԧ{Fre{PףCHNQs|S^hcT4s|l֭oҦuS)ZS.W57ڴ­M۴6ޘ)N4Aqe'/n6ɗiD+S5/e`z44/oϋKqu(;Uv'Phn#ٚlciu\[St;q"6vm$cm$ҞSN%GSthjSiSʍnSB_{Ơ-I)\)lJ9QmJlJllJ_I6m$|r0n6Bk6_mJ~ _eS>ϦaSr%`SmN RlSr*lJyV6Epo0pߐUm"u%ݎrrЖ4]Ϧ (]C}i,mn}&>wmҡ9nƍ_cwǍ?6n}oPϠ<π<)}iO\M>ˑ1TGh!}ǧ2/i>/'WNiHOqJ}|eBL_)7W9hrt>y:ȳ{ܧp{cg?3K~oY-2_l m1I7ET}|"'>ބõsFJ`g vޗOUw 2 އ_;}AF[QA&8Fq9g;)}to8΍_kpcF WЇS|^tSB i~n>Vb[7On9jm>Nxޣoh\7_=߄qS3e\X/ ̗Dž;n|&G;n4v\Xs\*y1Or¥qaи ƅ,_ qad91.2f:fDfƅO<+Sg,3f3:3x13J1SgT}~ъ¦o/DNzpx~OVʝ)"k6#zC-FSTtDqFb@uzv*cvƦ?R=G+0Q;Fiދ,!WgC]5Cqǹ~w(nWb7Hp碠MNͿr1^E{leVeVSPV+@y9rZđnw#yǫ'?*,+{kDeU9F]J ^w꨻1KwY2Gdݥח^%&u#j$ȑ8Gq4'7KҝJPZGA%h F~|{)tvE8݁zO@U4,Nip:$/^ Jrtl_'Z{߇RH[{UPڶ.Ii`[6믑rMI,^Fa1>U>RX8e5Lc!;/8ˍ?eWTy񴤯\S*8rg6\>?ö#~3ܩZ?Fj>u)P|J}U' q1eR}(_k&K\]GpW\ m,t[2>0ٟțo:߇gzTW `69HA4xZE;6SN[6![bm< I }p΍RV[/񣮜㖠nB߷-~"*a3d])NrT{^wy7*:[8-q-u{~Ǯn*3yp1*UV~q=P>ռC?/x?>@* ]d۝8 u#bK#h ۝ ۝ ۝ qa3l`ΧS̡lwϏ:>lwg%c?f9mwVak6!f ].n4uK#mw_hl,r^۝;Z(?^!\/ ׭`;*߻4xs~G]KQkMo^靯-f$]ܛX |(Kn@&"77dA,aK{l8s1Ls~-8C6>yQsŷls^'AQfo/6y^Y^#ԴyZHCkϯtImGUUc G+FmIdVF^Rs76,l lfنkj?ȧc'u۰{N1E hv6i;f9mvan6!;B(bLa>>lNO6\NH_kۆa m͉چ*l}_+~N˟56,lǜhb5j-|3lN7Qfw-^1k6_a6_a6_a6kM(w--;V1_?6_1_nKkH{.s|.WE_Q\wc;alچ) #i%ެ/sͳ0rt>yο8yp26L_s#m5ln؆Z@|m85oJ7tʋ 5m(=gZm8P?a;ܙ]gm0|pJ:PU=.66Oڊk~uCy rt^+m;;bCm(_7aava66 61 ~x uG^y;V-۰2>mx;=)7֊ZmxJVX+"m 7h\VY}R {Ċ O}0׊hb~oVl{|!6~ t5 kF}ܒmɮq,m6a6_a6_a6_a=.lD[wb cjk@Hu;lLgNi&|?*qao\1޻?YCccj8:q: ć;区Ӹ!G9⏃} x{^1iSި;N1㵴1^aRcXc 'P4mͩ ^̜F&9x_o#dK(^P ?AxMHCO!jW0brtf#=lcUPڮi{h5mҝ!viGi쳅x${b'{^xo_> Ձ{;VXGmCxxݙ1:vȑ0!'|) :3q_6}0~/Z A8!5jh$,IX' 5P~i؂4tȑ&Au?xq$pA O ^%O빎 EH6$Z呯pGV-J{ZW -'Zi,*pTcJq[ؒ(c gW%\lt fۙ#VX,f!\.p+s86\gZfC|&!eBFff&u4:#<#<#<#<#<#<#Д gFc(81 1xcH81~< 8xp1;z;GSऎcN,8)1 NjxچC9U8wNc?QI2w =0M' ƣa,$G7c'?|8IO3@F/%9 (+7-u @a?47RC9C% G:Otc^:>5+RC7!SrH}LC4cF鳯!gsH}h~elk# ȕxODe#sȘqȠQ'!þ߰gGf:bXVohGxGxGxGxGx/az|&LuO~W^wz'b)^M}i.|ncj{G_][i^MZap[hO t3lکBkJ{Y}M佂vRa S!/z,_GY )#<#vWdQ!ڄLyP~NSg=l xObMe Mҥ'7Ycw5l5lzi$AOzI'Qo>=䲈r:z,Q>SR|v#C' y -MI53ҵ8OR>kOR~"AshI7O/單M?c]$!OVGѣ/*.(7XV=J6&8"П ]8!aZ ֣mubM=*U/C/.mFzt"a\0Qu9D=QGzCf%Ggq=ꈢG*=PQ8/"nң-k4=J{ C`Ч7YMtKDN}82|6X. TmZ`G7aN]44iu>p⋖φSԩ5uj(೾ذ!?ԩC:]P?b߼ЮQ-Q?F}޾Ӡ)aN3@Υ0(٨G[GTcTeߔIڟ'}jwvL;$wFwHuk:|gLl;[ll 9ov*cv?>a gM>)x35)m{kT\C\%no]3!nvNpn\& wfcѸ#/{#HW|鯣? iS(hwcۗC)4v[&,ߓ=K%?t=%L{oXmK ?bǐviMlc[D\߱_٨PU6% mtMC2[]V/}JV/2>.C(숔N=m MQ=w;yYt.@ ?D_S;6ͩKQw SǭC܃P3[˩u{ rf 0l8)z)|(U~)/z s;o's|筜VQ8(bGZprʕOU GtN}/ul;fV`n_>h !zK0/Cƹܠ~ ^)o6Yg$[ tXe慲LBPz44/fϋ1(ߢMNqjRDG$ =ۼ6om gSEPB|MnčR nP-JLCTzۡO[ ʾ̈́]5Ʀ,ЃK}rۡQQQ%*]Cq.th1_tʗQ sπPvTo;4|^Fٿ^,?J [ۃ࢛mL3)݃MFCw=a [2⻇u "cqoCqn"E.U~ ]&c]ML_r%/?3 *~9Zkw5Cyg]]"^vyPY>?! ;'ʣ~c3Tq]Cl4٨2+ololffz*_W (|8TЉ#^F@]3g4tלqkθuz/9:?gYVÙ8wug,;mC@v)m}[@mo!.I.]x H| B6Vc%*Cf)}NqMWڃlg };"3*9_ɯⳇї: g }C5Q]F0~uo)i<+tbhl g*ts_UtwߴZZ] Gn:oV v + 7bSX-}>U>RX8fYMg* k6~yv/%EV|oϚl|<+mGfS~FSlIr\3]HrienIDߪ*8ǹx|>SIkS/f7nΥޕ w5 h~0@w;([m֑c}׃7Rs΄QT9FH;4Mq噸-[}|YXCU!q4Qߦa~jICW7 4n֨-hJ jWk\Y]5$xRFklN(ˏjuG4AЙCƏw /]9dxPO2>mL9ae:Ÿ[Z?>t?L/?IXʟtʟ?9٦G +Tᘣ33Rћ~e{ ct;1 Ax c crۅ,PS .q|)qwh*d::C uG^yU sU ?ۇώg@ʋбW<.uH5+d)_GYyl8~ ڏWV+ ,E>Oh Ioq&sO)Q4Nh6=Oy_F]z@Y}5uT^^Teey| =r]y e ۱^jip?e ˢK}To\Ly0@ ávy3Ton]V>kOR~޶ionKb nu "ADoNq -R??Z<(_u zZ6 !Ջ>ܑxxoׁ]1܏7F˽쐾lMO$eگ (uMl]6jnIY[[)x<]<=^OOgt9|`b|wh|ƾF\l6|ȹJשL];\zho)ewXZԷ}\ŝ]ߑfo^VrJ^(ODۛmV(W-=75xᏳ9xm\ǖ5Ov~qh}NUφƝ]Bm_g}?v=f)}l/0Q+=jܪwu1iqqnxqͫ_ܝ]S/qP͈/woŋv~1;rj{88S?6SUnFrc7C8x劜ZJn>sOWdl;3Vp^FK^o E@Yg873M/?&d4^ؕ2b2U Be(h؋ R^KC=ȯy9ܷiv}FCGe}gŕE;7(ߤC;)q2 nP\eCi25ϋqxAqoA7=/0n-+Y&Tu!Du_t/GJL{'2OV2)LW?4?Sbc 6r,o'k6#/VЇQQ?^mToSڗCyìMzꏐ7G0z΢4UE;al]lݻGyz"-uIN/b#*ǰ~ӏzٮߏZ@Rׇ?5ǝR=0D-x]M>;zůՊz[|Hoi??1E_ڔCi{[{pc}>_@o՝61EgYZ|wRY1泌n;zJ?[A~}B<őr۹ޛ_unhYBjmtʁ9覰hYu>/T7R`|{ry9.4k`Or>K=3یbYuqia[JY6Yrz5E=݀,1g٩2ռ}5LffGfbfXmFfmFfmFfm渰͘?vo2m3nj6m&l3&$l3%t|fH63iY;@6^DmFmIWL(@ Il-;;u{<,1[5F ` YBedy eO[T0Bk^-:$oF7o;e1uO_͖DtMZӡ|΍w4 FKh)xaQm]m>/hӗ5QG4]ۡx;'x;4C/݄r|~u~$(nZhTޗӡ++kp΍2zـ+z!*SyqdEwCwwe2a.c'Řs r0n.mX{1ŽFQ4Pz/LkEyo/1|ΙYʽd^^[edGpMD($^_ܣ{|XkGT.`Z}4>VJ; Yj܉1~2+uGuGfXw&u#Y3]lt讧y'wS'xzzr:݇ޏt9JܸHwr:`CSC|^\^<7*^P%Dzo܊q'7}c7Nʾs7rh_9TzS}ـJ{֎:Zլ) iW^|U]K6u_.Cz/m *t޵6.Ji쳅$րk5`[I[Ȣ;淣c~o{q=Za9wW;봪P;bLE }r]pq噸-[}|YXCU!qqW0G&aM:iMC4 hfy/{@C'9E,/'EePXq?|nܕ/"zߛxIުe{҇^JrO_kZ{=SÔRX=}鷼V@PQm(Lh{.M l -ú /~![lJʙ"n-_H]c_R~6`h;ric/W7xEqW!,;ȍLkCbA^> E\l9~8E,ANZSO)ڇ0x[f8uP)!Aî`@WMa'WụUI?ZPֿn?qp;xDes,r?Pʶ伎':&sGsUv Թ Tq H}C}!7v3>KOt1OY<ԛvꢡ@Cz@Z8;/ߝX?~[?\eHDq>o}_ء87Z ǩL?y-~1.6;SkF rJ=3 x5'l33q{?'ga+ql59Ypɛ\ [V].wg{UZf얔i YYyVֈ_瓣ߏSF68xSmL^&Se+ְeư9m,3mL/21͹4!(M( #4-- r'x8=l86чy?"6>UhlbTӰUla[7VQV4> ~w~PqY(h!}[F;uH?oF?/J6ݔ7_5{ 4,itÃ7Vzd%*CV)8J[+A\e.rqUrt(]gՇyWȐϽ6a`ވƏ;%:mg^ mwMLʟWG[KkX7@ͪa߮po{>f_w +Gkz'imL{da _p Ծ?eWTy񴤣\S*~YM>'x w*h-I|IGSU= AD<]l'XuҪhANY&zMךݜK+?ʛkA7^ .A~׾&jw9Lg*S+-=Fy8o~,Celi1\fx\"_KTq'sљ_aG^+ݿunx*gx~]cxv#S_J*=8l6]K~wv\A6YSx?X3Nqmn6y+&sRKα" weqH؁:y!><ӫZ޷͉pD:;i#, ?r&Xc &&Xk& CQx065i^ιXqv9~ԕUqcyMOcIE9l̵pŒ}Ry] mKJx-qvrTxcSˬQfې1UB417r>ռ?TWq~ >@*v b\zm:%3niԦ>4=c=gT:/{F[ ǶÍQ3@\;^Ꝡ lhף3u*mTڿ^s(3 7,ʔQ(9Eqcyu;h!ܱ|w@(797Vkpc1Qռhwq4^+eT6ϣ3q7PnicܻhVH9گ^ozôw.z?44)9(;͹׾9:L7rnEos+hέ>Z)\z_'dwcn-Ź(s+A9,>u9f `ngp$0+dz-C5¡x?dt"V{H]IqcCWN~?]f ?G4GΧHMGKV~>{=/wɳy:%byDy"WV*Qܶ|IoEvȦC)x_GLߏ1(~Lk.X{ߏm^ۡvLݘM㻱3tkkrpM>!{2[1.xY`տ[M)Ӱ{U5}p|rt^?ߌt| k6ߦHoƬ1|{m[V7cVE]Mu7k)VXzJq⛟>:\75o}i+]+]/>CW|kר\@=:]ceXǺ怿EY{i},K_hXu-WzVA=:>paL wzp\Ʌޓ`?ąӐ dJ\uS{NCr0..c4Pw~V8P!K\( q4BGC<_r.QlPIei˅2q/a..kh녳6rn Ԃ K\¹iȅ%[8ɨ,Q\8 ?w@pv`ۂz| 煸00 P|ùP]8\]3wgduB\`k~G0PW$ q<͸ѓR䳝njdre܏Hgd?"yX U{]xGؿg99GYҐ#ԯ?8~+(Es[;vJ. ][rCsC!Gq)qd 7y9]}|r:;K٭#p$S#r>'nK q$# 9Bv#{8GR]ؾ9]NW<c;p5]z!}u~pj*9ĥ=]#O&GV"\Vu4egs_kp77:#15R.˗:G HZV@:wo+h6hzW16]r0?~]FTXqE!椋9bN.椋9bN.1']IsŜt1']9.d YB%d YB%d YB KIOF,1'=YbNz2Ĝdd9sғ%'/k,1'=d9zǒ% YB%d Yi)KI7+CI%d YBV˔%taZœg262sX_9ȈsV?~zݳg+k)>m[F׭{_9;~ۢI>Vu[/_^`6 'uDI< 63OREW9Z>π*> |ώV_t8⣒V>+9N]ss̟CH<0v݂6v_{ݯ[ƒZ*0OdHzz]A=~Ho dyeY2wjԉY<#:9# ,E>W>dkGZ(j!_\-8L<>h)֪K>k+zc g.g6srYFFS0L}\xGxGxGxGxGxGL5 TLG3|#2g}L#:&p>SL%'_b>8bXgt@F/T>S">S&>SIJ SIg\}gyGxGxGxGxGxG91}J=N+W:큔>!N_O{7)r~`BEо:Q_U $')}|J>GvVWN" %3K/|m~zR>ϥZB %nMj)oI#}h4_b;{|oD9Ii)بL:~gKG_[[j)!zSan$_%kylQ8(bG!\rEE-W%7H9rUscz7ϥݾ}A`^4 K=7Orn'97^\$ˋMɖiRF2UBYJ^xSL=ex|^Fٿ4QM1J}< ( P+6ϼh[~4](0?Ws:ʎʜn2Mg$fko4'J={ѦNCh; qwհy[8 I誵a18Ul.r 6 9r#j4vߥ+1U_w}ozE~Կ+\$@~OgŽW݁qIPu1zHNcD~G~V=ꑺݧzDG꺸iI|~_߿]_VXRд.RœbECLM +1&Q#rg᤟׻>tE;DG;D;zoP|W5}Z'!>Oqۚ?ƾ;vd2Iaݬc8uOng؏?<(ms1c Nu]f揥hgoʍo97'q}Ӝ:#2M;Ʀ2UoɎ|d./HgK KDgNRghEx&/x-7$>?{% 4K*V}7>5)<^ ^2?{zwՊwIl} <XnvZAqUV}f#Rx~tÜѼ}_0e/>Ѵ_LqӴaP/C 0ܠDL'0[g$[ aLarϋ_p^ܤ_$ȋӸ'?v(#[Cn$N]j)mBxnPOC;4wj΍[5qCixFo;Degx ^>wt'O] TBZ+Ș"_QhJ1=٢5~nm ZgWcl7?g˱mw$d~v 52׼6Svpr;tYFn2rK7zȨ ;d q!G)=&k ߹J|d䖶ýQYww7Zot\|@$ȞgLKFGP;2C`` 7Z"Eq-吽XlKE[-w.d̅v "M|Ϫ=Kdgl/=ٸ½Q Yܳ틋o?dCx!`/߾vO!SvH|;6ΗyJO\k\-m_<nܛywYwZ o d^ٗa>Ap4Wb\ Kn~q3 cd9p5իd//sp{5ķGoO\|_C~ޏgD'w'd섬 M|"J&yJ;Oj.sK ')œ[{,2 Vpc16npqpodAVk⛫77.m|s⛁{BTȚ l3jU᫋o=d>z|qAC gq} _Cx%g>o'!k;L_H|;6ɞҒZwnid%x2rK VȲN!C _ _E\|Cpg *"UW{BF_ lepf͌&\ v|3⛊{ *` 7S#*|ŷ2Cz\xWH]ń[2%{ۙzm մ0G~ c@c%c}w,.ymB7'tW%~q2K6zȨ wIӱ>^A提##>q}{@l_}O9֗w%&vW%~q2KB(‰wIӱ>7:.K sdO3&%p#o( !k0 o ߢBr^g,p"-;2B\`n&gU%| _3^l\|OZȨZ`{ YM|Tŷ2A!<o_\|q類)d} liS߱uG)uW%~q2Kܸ72 +ݻX Sȼ/3.1p" /{},i⛯7?.ŐKm1|⛃{g@ ȚlskW᫏9| _3^#8]k k =Wo ߞl_'.OpN Y;=c}wl|%zt#\1~ (.ýNpBsRo]tOx o8d1x`78| 2 |p5U\ ًnnqS!c*dMps5ժŷ2m=\]ڸއ !zjLﳸ̯!kP᫈|v>\Epo_ Y} BLq {nof\|SqUqd]lSfj{DAz^gupD{$.pJX Y+!G4}A\|C旐%%}Aێ{߂ -`}z4w>@Q\yFDA@TPTLFFj*dME-Y7J6*FF;r pgr+{9wۓ S7>t0_`ѧX?O~z_lXYo|_7T|4U[5[Uf)M/Ah$@+t&4 |T"hnlE_τȅV.LU>I嫂ihFVsT[ Rh8̩׬kB:`k5| [ ZhՂ֬ק1t OG_:nX*RoƗ[ `K-Hh>yc XK&ҙP3+TBhAef|ț,he-fVs(TJhVA eT9|kZv| F*_ 4[݊2Zk5Rj5Ъ[-QGC&c5Ra,ҬGC_;ڡX*_UΗh%[)K_ aV)M"o44mD:j|y <*.D`d|yT,̀F2S+SQʡY JQ rXWqZV+SSQ&Xwy/B".2NSIf?QF?za2N*mFv֩/˧-O'a0iV/i( F83΄_/ʷh[Pla2l*fAfX*]gf9QF9؎2>;φ(V1l0*_W&h7&jd|5T {gul`5| v*=hBe]N廍q Zv>dzO nvbvq|0X?OlX?x,=lw3Ab}'+p~doMS)fCzb}6h5H;>P P6\ +ِ2*u|`{PbzxU[5[U0OoB.Ah$@+D OWލ2vV +7 VT9|U< (4ت`NwyKQ R9U|TVh^uqlf_3ykQ Z5U|}T>`XJa%0d|}Tnu|`Ic}1=<_ Vo%V-m^h䍅F,b-NX|f*_!4]2V3T\͂F 39|*_%4]2V sTRC-;JaUF_#nE`k5|[hՀ֨ףCJ`6mlvClU>i/K:/|0OoB"o44mu"d'OG@څ(lX/ʗȀVز`y|e 2*_94+]2*V+QJ4AJ`e|u :*_4[݂2ZQ.#Eh\E]թu*:|v?[/SI廃mhV:UoaM/lHXOoBF!o84¡D O/ʷh[Pla2l*fAfX*]gf9QF9؎2>;φ(V1l0*_W&h7&jd|5T {gul`5| v*=hBe]N廍q Zv6t?7NX?f0I?ya{,;_±{o8͕7Suܢtn1Ľa=<ʵgn޲5]yn>0I3\ Ғws vXS0^}dsCrG0|*x󞫍Oه {ܶ8oK@q揕h=s*! O(saX;n3ؠvLqG^G$HTswWrG^Uen &ҘqTG D?`%ǙpO(~S&bGLٍaB?"4q]/|C\ns",>B#Zr G(}d#KaC|iGkGݎ,VoG~cV?UZUoyVIc؎i; *l /c} o>Iڑ۰#:KPG, 'OVdLY͙."7p~-]yۀ:,i2X\u-u>(>\qo~(ɟcp⧻|@ߣ|ݚh.3[Sl-k7m]2V'z^})L;jzגѐ8e?YBʜVxkNW>aόW_Dx viwcis3. ROuߟ濹ֆ;Q0|r2+(Klvbm=l䯣(a?׶[3s_6lwx]£7]Sm a~q/s2 _$Fg?KK kF1(1V#R'n> vl6P-|^:`d{!Jd4a>_M>N*.H`E~&a\Z 皳)zd9|%tU YWc9&&!_"t|T+f7j+76ꛏt_nڪ&ǧd ;D;dv_nMKw2?K"v'ğ}j}y\뉍@T{;9Y$m]G|??$ᘨjo<Έ}%}Soz/'yT0r۟m74?җ* v]|ЮK 6 v `k>yJ&q|L}'ě:Vh%>|ֻ$jE dqir],/ُ3w'7w9mP|µ$BN'or~scg{Ltc-#o^=T_)͐鼣uRlPZ> ];p%gib;z8e 3c1PS[b^aF}psko'u|؇QWCr!sLCօ0XO.&kXS}jWw4cz?`ߑh9ά|V *mHqwe4pޑgsE4x7ŝ297$~]i'*)^ ºUfju0 aڄmwm# Z"soM` ׎]| 5m4\+ ru~,~{1.V{<)9 <Oע@{~-- >bcl/V<Hھc*cұצ=~O!vOGr.l' »6u!DǦww}V/!tĻY4yw?{ϲy,G, i˙?   # A"`"* YinC&(V2*@=* YinC&(V28 8$v5<*x} |E%LNL $+L4W`%@ * ."CbPYE },*I$5I U;3U}߷_Uw !̅rw(!o|$VBc B!$]1R$98:! d0@zy(q=B!$1PBcv|Nhvm=Dh7, g?+LmqI=B>f'r?+Cȣ d"!LuT6tȂz2|n5gQtVgv@; >vZl>[d:q} _$0=_pѿ{OKx's})X}-'ٛv`!2 rP>aP 3QƚWҳD]>a}"TG>Qvx{ o;O\%EA?6 ql'6'ʡj3'2\1̑UX~Y:_>tuEp=Q.E}"LG>v8} o;OL?0NAV(Z&1!ܷFΏ{q˭bȐvs$B(ˆ΋c4HWHhhB6O93 fWSXC} 13O-[].dĿÂZlp<q<:tNp~r,E]+AL)>f>o;~@K9q'~>B`>q^1?rk`|}"NOī10tuL\/K'eӑOl;F\ v8|/C?.A?N3wx P mB38=/qyr^DFHT 34N.EH}"AG>qء+_;y!|b)/Џd[97A )~Ї{_@-'j,X_V'4>! <7Oq'.}"IG>;;$OLb>m@(:,:L0LQp8t^Ɩ:[Eѱ(ela- ;~ 4MXh 眪f DjLe9XhC,L}~zr:Bׅ [Z^p/)h 5a!:c1[ *lk°AB^G;+ˋ􊅭;QAhBGXHS~#esl.:MBGbym׿eXvUuW +]|&_5=H瀅 u^*ss:CB 3LxqaEIܐzWЁШPj9C6nw;='Cho(ٻ=]rw52 OejOuROI:4 $,"'v SGze-HPbx!S&(y/:gh;ċЇ?|bs3%{vX `L _}BL)8H<.Dg't7wCy'Z(+)f3tQc;p2Yze(r{7%1 c;ALaC7\V݌wpbF?NrVrB7bx;~0,tUx#Q?Dc00u瀅꼰N  ןeX!cy'4MxݤfD}^y!KQ5фt7O~KACBRYܴn5uǮÂM=5M&Ig ];Br*YŸ=u72P&o;Bt7~|:𝑳Op8drXS>0%k# 2_ sXޯF /5>@| <$KO4>'')$8>{?}"D}bO8?'ހ>QkV|[CMJcC|y}Lg(w$R޲O>q8f'CЩtG4>vo| '.Z[}Բ9 `}"_OQ 35,>O>_~2|Hm@Ol K_lpz0D(,sy:,X;} xxH}}u7DQrC 1EEVcOK`V}bZQ8`7v''$$ϙWq'>_G+fN`O; 4hB}yz'A6AAO\7k`">Q''PO sBY}b:Wr;,b>m@m. X'l O'v@B"sO.?^l|jٔk`8: 5 u`:CIvuu) ' uwCO1C@hM5Ub6;}Nϭ>`w4XOb:C1yTb"''l4vJVb'o;O`n?in91~w9 Í4}F)dbʊvczb2^}3}܏u)DD_9 9 1J9 =(9 i7x'aWi9 _1J9 O>0vX|r@Ee:s@Ns?2)RyQ1pr<'0{rK;Hڑ<|otzw&0?H4ʟsIHk6[E{Z̦Ul׈gVy|6.}gc(GWWjP#gĹxq^(5`d`zݔkes`?@,&3\ ] r>{-!=ǂ߁Υ~/s;2Ktg;8fp/m<3+ ĸe!}8 ~}3PQ3L)XQ#GGσ2]pnK=s0h8iFhg<8:%9:}VX38:<mlG/dGyqtGGhh&_Ꮮ<9ύf~GO[5Shϡd]|=ΝhޢpavS,'^75iPz+ $r'] zKfEPo; Co3SҐC\[rh\Yr N+_jVm,X_j;fȡV8 >$KC=se`,ЇςzaڒC/ez8gq#φ> ʤp8+c cHjSP3΁.eX>p/4Yc ¡X_/22ܓC[)~a&n~g]N9c¡MVqۄ5`7Fihue:CsY*^8pP_8pʡƆڒCq!cVMh>>B9;¡M>hʡ(ZS_S<3qU~O@"wwRDSMU8 ¡JLCsmɡ8ʡ3lzI¡sGLaP& ȝ¡9Xʡ+m 9-?!⹶УYjGp:> }抅>#..XO@'' 3k/HR<䶂b`+el]cIsC38p o;F8š7Fs(Q^'sFOsG8th`Rľ;Iq ;$N盏 N 4A>HTz)գ;pb&kgILg(3.Y*ni+;o;۫?Cb:CzsY*G^Ï qgtv3>rDؐ;\[pfʝ~[SrgU NucTA;Pٿ,W/cfʝ# wz!=8˼ 3- 5ݼ~лH_* MC!>fWocȊ X/vȡi@VHvoYU .3FT f>o;=/g0( _5yr({+?-6?<3ZH$4v!̅ӂ0O#pOqu-$21ҷi<0b-`zFtOW~QzŽ[>fx1oԊ02Yq%K#d!F0Y썑X{M#W6p@0Q6H, 1Rxdb,aQ6'Xzd9fE jH! jF\Y}e`dBƬ 1= ~1bR02F5*RH:Y_A=Ku~ۯ|+xƬECgyQۭP6#0Rb@}5Ο ΐwhD{baed8Wd͉'+?J BT ` Dgh ,rbQ+B9` 8.,  :B7#łW@)OG kMZ Xq!c!\Bb,6@,<`Rl'5 cHhWä FXPG|-8~ {h|/!cC,Ԃ>-+^9cT]_W,LX &X0H { #)#,^TpZXXFiłp4 (,x}7,(",-*(/J4^@^pZ> {sQ8Y_w$IwWosSEV?T3=c;'=iLj,#$ _hHD7 #T0g^1#uX,#8 #10<@)I#{2 #Ovӳ;FŢ_ 5#9w: R|溥o=6]p=)}Q s|^5IAb$FDfRy⹧02{sANVbs g%{#wW^6J>8d9W.^>ځUH@:| Kd)oH^&C{1ء#['mWjlZ{r¾7w-{{J#jL) cYgw-}Ľk7w-{{J#&ٗǢi{bsm;%8v-̬8GOgf{ X<3;c9]U' :J];ȇs:λ?CAnayDƧ-ؒkKb3QƚT$>/rc+,S'ngE_`n2>L ׄ=C81&c>qaς {>%/3JsY 5 1v3mNma/k9m^uSk+!,e]3b̩xϛ CΡ30uc{f :c؟AHe) @Cþam 9 +>a)|zq([҆"+!q4C >[.Q>7 ֗U P~u ~`I>o;5PxTy}b#0DGY[y,X?="K:CIg,E]8>rPb>m`\+|+ ` -qeibr?U8E+P¡[uJmeT-P?g:C)rgѲT89y[CoRlS8A r/zJ9ȆڒC'(>şCILUp4ЍQ 9="lNmԫ`7'3ȝdeT8TmCD)m 9]bzgTCsmɡ_`Oy?g}QLՖDggTi 3%? eϑߗK0#&6`3+\;BΡ6 7Ik.^|9Oy%z"IǛm|A$ C +ֈ+pm6@+j3juZU>Qg 15T zZq o;`\K\#4+\[q'sy~p{~+~9 }_˝Kvsc ȡ{,H:Ca\&Rԥȡ{,e~ (U(v?#~2EfN5W>pB0?Ї48, g9di(NcFPSBJr"T '<ЋOl~  o;|q/q޻@l=WmWD\l7YS.6>4U%bkɾ#-0Mxݢދ 66/rbvԄ>t#AĂ~\fXxU\k±@X|{:7kCTJ|y|8%bAw½dL4?fzݤGTz^f S]X|2Z/HcaB$田uG7Xڰ@eD,|e,d?Bhᔰлn:bs`9LJ4 sUrТ@$ nr~>8U!06,q?׋X@`E>A̙(ad'+g$ ͷp\>(}ß^0K\!C'C_hZдT] ;T 8JWj/uzYq:g^r;A31]VQ^p.\.ΗG߆.҆?7mmNaM@UXȰKcO£4k_xa Ͻii:WpڵR1ccc|v_K]+QS3cf`l!Ø0ft=?06%"΃e>AqZo9Xw_q'ő?=l\ђ19>b%pDT@P$㥦Cp⤙rnbK}IсHp\qE:)$ؾ9X ^kl|+֏#OE5 %f>ŋ;kW dE^͎>¾C.{5ѵSf /&sxkF`3||G>Ǫi3t/N<(KQXsc}47cX vC \4q9o)\!m~_/gn3autZwѺλ+`_h O0t]$V? KQOx+hA?q 6C}X|ԬCf'U`zj_^K:CI*SgZY}skb;;=v ?ۜ}\Lp-?X3N7$Kp,X'4>߲@{@޺_q'<֋O;FăOc>m@IЏ)tw>1 p)>`>q›]6 ÂDFhd_s3U5u)zlC7vܼ> C?X8N-\y)~>ЇUЇl=t=3 ևg8>3ULy>Y}sw)h3ݣ{2 o;O}&B?} Z"TDaa,aTGhTnCbzh>'u]@֬x\ }@+`'Hy,G x(ϝ4<&ϝʏy?s9>aD{#F&a$쎑SoŐWa&rH&1s3$as?pa$ #}=0ҡr,#7TkHGIk#Ͼw,&2x7a#tH)rugbX#+5a$F2Ĉwko2Èz' F3/’unyUF29`S1kq].KRߞasSadF^Hߎ r4[k׏$kηgsunt͑9 eS$*{}6HZyO8$)Dn   # A "` "':`~)jGx'9@=':`~)jGxĨ'T@Y0'x] xչ>n6͆dI B$,$^6GKBDz xP?R6*z@ A[(JV XK+ΙL< 3gw;?s]qL{2mVBj y\Cvv!sTX1[G(B~ 4DV[I 737l;!NMFpfHs}s}q$;^/A ෋|Fz89>#6;ʚoT㽌'"2K~v GҸ)D{| n ]Pdܣf٧!==DZ?ǒ#R3\ϏIȃKV$.c=]CfvW[[ 1 .p0? DsX.%^GxJ~\ Ɖoo&wOy>75K/.]ɗm85WJ|A׆m_:NΏRx-0FSH|.c x[^\)qG|E eC/. ؘ/a>,Jo{^3ZukߵBgNx"NE%D{3~N G-߂|NtΦ+>u+_%1<ЊkXIrj `V+$,TG?$1tr'Lk}vL.eAᕱV7bVbe7 Zc%Q-ʱaXؓ1> Sl`cVXI+u ]Vv]JRcc\+-=-Ԡp?b7j#$ʝˌ5W OޭfXIx52/3.1k]k]L6JXxEV`%%8V0>Aи~Xq@Xxʁj?;δbZoxbkʈ<^AP+VF@XɳRUU-<ڂ k]v. z^sK|Co h{<7_~?xޯǽ.É5=Eۿ`eR.Z䮿_98t,~EF9_l*IM4|*_]$u(E0e4 oq3/ 8.t=ko$.32^GH? _-W.``k[O~_kQ=~G,3%8¼UFgE0E8cS,g`1@z`Z|'*eVEFZCrh7S{ݶ[~hZ<Z<.rct!D؎fj@kV{Yxi&F|ms9r q;c?B^(uhk])T Plg1jcumUB `_ *b IE !bI]0A!vYɁ1a (Kص5? x9rx\ra?؏)8XʵTTTY9[L<Рpva?$_ROTT.t )0r`$?(ՀAhis}n AVwYAD+k{da ͵hQѢE]PQ{ݽˡ~x,\wGq-:'C^W7WdV3S8~?YROgm6gf@lr6g.8U9/W3.pgԓ1R(?bYF!y{NM`-P1o C୴v=|;@F{oө.>[`,y (΅sh"}b5z>Eq@qq#,x`:LcqXqX~4rh?eR;et?,m{ GM/I*iScf8ax8':cRSs>N ׃Ԯ7kiGբupr`qqq?< 1@n/su7=9d;8N[ۓwЎ?I"_%ޚ i cq}y~&76KJ#zu ߿zȠؾ"lc1)W9'I}XE>Mse}zߟ=KyUkݾH5#F@Z!ROkۈr4룮_ϸZt}>.mgL_t}x:X`Q]rxu8.u8u<_t}l Jib]/T !&|X'+zdwӅB,P&웽iB!$9](PC\[5z"@]q$]6jV눑@trQn;Ci܇]ff\xެEtAu=oԴ|>-~KE'~;,QhY~߸s,,`9z]/z^E8 {?(y.yu\IGM]z_nzTr=;GA.%]gœ W塢k#*t%a]!x%uHכwL_0fe]/0Uקjdt]_W]Ԝկ눑 0" ;&:#5d=R0-ÿWoP]KFv9IRܓ0y-ex(w5\0 ?^{$W!QH8dУõA9#O O*R<`גGo-\MkG0ꄠk_CV^kT|4Dܪxm"<۟q }e¼Wµ7^_^y1M'1Ih7wn/mV*&_Ki$[_*r*19ם\L_ac|bWa/6_y_.V]vO`qq.k53pOMv'_[g^LT ed՝0kTJ a^n36#] OcC2!q*Cp!!FI{Q1n̙y%d"i}b w>p!s0$ kr̂@=:n5P&iWM0?=҄iQC'nR_`kIlGM*|-oCިf2p_;L毡_5ɁyjK{W\KSp<p} X1.-)c&_g浵;{kR ٲo{.d-p "l~I>V1gx<|,ǃ>F~X~‚ǃ88N% I#WՠN !c)N>Ώ>q(=pBb'#qywkozkyh?>&[4fN6Paǔ9vp4Jm]e4j/muh)qeרE&}_8G8'4w%¼#w5wց ׿*3 _1H+YwI+;q;X"xpD F014tD1l*:vV^FƋ_Z$瑌?5zWA<[zJ8`e.f8e ¿:  ab327=WSw^goZff!=mkӋ1Şxoq1q_rLᷭ8^6A.3iE9`-p@-Hz˷=qtLl0V$Z} c4wHb;LkOƙz]0NsK|gra;ؓ1> Sl}wUwu軹VZJ{2ZJcwș$ݨwɂQwșy[+wewS0+zCw;viŴ+z3ڵ.U݈;]ﻪjgUUlDֆm^C~?wj~8ki2c3Լ+kL 16#{6M<6Cӣ2,~8vҸMDo┴3sץ?ˈH$_3uK軮x\(D0S_NyW,vz@⅍i\Orߪ'%_^׬ Χ sত(!߰^}[BsLPvl3rڶF 7FknJƭYEܘ\π\wQJEb޵F5[l.6c T xnHY7~ XYfe%8¼UiO*SZnSLU]Iw9LZ^k=^a+SK h/wt^v6_nCBSůu@4zKc_#I#=@<59XL!PT1G~4-kt2,KժFfDFTϪr/U5AkKUR~gUl3Р7jɯ5PC\kCCh4NB6N\'P'RayJ0<\ЦW_ Hb`p#m w=`xibAVM4?`COlHvgV?kTj5`*K\jƚl (P-_զ 4g - Lr ܙ6d̀JmeU3qsZNy&^m D[Ӥk`;Һ.|@cr?o"۷tKK`#>*o'C飏kz(i"Vm-hcvk-Xғqٝyٯ'd鬺7[ZemVv:ͯm֓`"FP? B?z-*" *q%hᮅFHS}$@m<5ohK]M=$}/M@AM*#yG'lKbzx=P1oIzy}#LJѪ9zbAZ iVE'I˜ UuZ $ܻ%˗ˬKn;h{k'UƺΤ̺I.H o9UD?~j7~1T#o nȿCEqkՠu:j݊xuj(u=fۦuU}2s`1N#}h43K/h]^kE8 D{?(y.y\IFM]z_nh]Tr=;GA.kݱ%gœ iWߡukuҵ%ua\!Pnm&~Z3Ӻ́ZYY`i:_Zu.B9N#+1aDi.c|&:!/K~@?gqʖ;,Q?`?ZY%ٹlw/= ™]׈}W% H?_̿y(σ+y^*Ƈjq90#Il-uȯwc BlO{-Lbs_ ~῟SlݵN ̿_R~2 Z0 0 jaq/ ~mZ9d!Q!6!_2c)68?lCO]i>9!<821C0o09daϚN [S ~]Nr!Ho }-;9:b~X6'吅9N!R9Caamq1/#Ę>wgS733J5Dq 8U 0oQyC FH" a_%Q/\;eܴ21rI͘2W+n Ɨ&|M|}J7M> 0vB_lNp >jWik9 ;$yjQkם5&90O y+}1bTV_uBݿp kƽ]rVuT~<@h뱮A o:֙3cr.𸿴tVT<~:v>uo81HSb,uzo}tXЁ+'X{QNJ/ұcH8NJ#N,N;vIpyjpDnni6膓}'->8X"8?ǡppBs$#qyRz y=~ vh\Os$)shv ?h^ۈ8l7(S"J4/QLĠpp{J0yG,1jz;j1U˔'})ż##gE%#O DO3v?ߩQ;up5lY+Dd =$>   # A "` "+C/t٫(xBD`*yb@=*C/t٫(xBD`$+Y YX0*x} xUt$t^  !Hk<]"#htW%22 ;w2HF?a9u+UթJw9}ﭮ;[!B'$QOI!< Dx=%8ݞ[ ёёmB]d$!NNO;HC\:2 ^ُۡ6тmAö'6x]f\8+yqXW"xPo5T"\\kvBއv݇r]/+vKbbC4,~(}r JPE.bGEsb߂ ɥيóZsTs_^ttП_geP}!\ {`)Jo%9'8IN5{z?\#!O֍+_5K9W󾮚\/~Qp¤q>$>ȕd-ݥ#.ʰ>J?|$Dz/j|ҏ>Gt  ឮuc׬r+>:'\D8ȷ /@yX0 F}<9e{kP+/NY1pb'<;; 4 g9u<>cT,u2❷k8bIJbVA`DbrhV>s+(V^McPksɡXvd(V4+ŊeX+gov$b+VV,QKF~|i._lXAgR +0Xa|PXIaXA_Rgce\Ys 1mpL!x%XIVcenrg"N.EdV_w`yǦz9=ȹxꇓƊXAEVJJP0,`%bJbeam7yƿv#vGL c>{n_]*M /^c>+E|}{w4T8H&Ln(M^05݄]ܸi친եR +jOɊm u>c*vAyi=N}ziwv߾Åuxzz=g:%wCYA&>]NVr')`d fjgv^]v5\Rw ϯ?Fg;#ߥ!WKamgnXp4e?ٿK ϟf$?UQ?}O#=/a?lsgQ?;$/ˍP2@2v=؏>^]>*0m4&Xu x@'^;>8ʔ@Ȉbi#o_^wi~{}voAGE-}gH9[wZ*ܺ4?gk_޳[B|/ ,dy`cA3P89Ɂ>֡`+5nA8_v9Nd(ly~c950t{SJ!9:9ƟrU+|l+u,AJ;^~Ô]S$dy|J2o dd{_p`Ȓ9Pd A8Ϟ~L(??Axg3NVedΨ2eWVJ(`՚nD&2? ^0rBF^yvclv#㴀^N&ⴣkqa̠6T66,9~1h?PS^#?;Fjʵ3vi9H<.~|ymZRtBlD濵dҼ=K'ۿd7ikkq`+oކ-N(Y+~ 0ۿL_Ö=Km~kMo- eMO(_dfYkf6?Dq6xdi_}J_}Az^PJamƺJk(ی# 3svzo-eOasl%c} n(cvXߢX,\ -~@*޿$yF_$>R&J G=edںw(Q"D^vRFڳ&2|=i b;}?*c=3Jyffs'-4leN*_%=_斊kXy:_׮`W5~)ߟ=!K0Q&ӧ{DܔI<+w19GJ|q*9A}Oj1|*?#?se仟1uWP>7ʖF2%CAv=eE 8XO8N識\[R%ɽЧJ_oŪiM߀ți~sꜧwCKy&WnTT_;Q3_-a2?v|o;:֎'Dzɰ6;-O6__L8[3$8Ўc]+'ڬR7g#,<߳Gzq[Jv5OH"7y[׏yA9Uj)^꫟u:bz6;^Axm ^ׅ׏">^[U[L;Ln듆a$|Jiy]LDD|9V:b,Fc~HPfz {'MW?b$TFޜHF'70H(7CynF2r7CPqPq~C>^ϋb^?U+ΗUj{+AuGTU>w]>[g9q{9Kׯn=_Vד̔ ЊE_ ܭp G;Ck Z/WV#s]+ѣ`Zϰo}π\%c]qaYj~m_\RU0U~-\-r*'YKwWAۯ __Y+ԕĆzBkگ9wk_,~[EʵSx̮~ ~_v2vm>_>UD7w^ӵdB6='_fX[N)k^hg^SH _X- ` '6ahq> q =,KˈKLdq!qD/.ocG󇂽nfBx룔΃m=lNh2X`,8U3!?__A Wuց(Wn"ȍ?<@c u ׾$jKzA|q;`ݪJ˓h.\56L|fs5Όy\/@0uwF'{n\!|pZ:ˏuM`L/ kB{+ ?xW͂u5(2?us?':ݶtW/5!/gϒ78D'~sL}֙Z^X^B L63\ qƢ7 q31x5t3riaO>Mi1ߗ,l>ѪU vц5k~ t2kʏd? 㟽g 6OoxϪh^/|1Ng @ٿJ>,:B6r:Hpu,cMYP:ӱpy]c!N+ڵ ,NրO 2qH`j۬S 'XNӱ'|qR ߏ:vq(<o0RkRquzn𾅷.[ͳp{6nыc c?nJ.p܄N츩}8 dM/Y^,cm: ȸ=>O޸zuM`_7 A` 랳HV1uݑ+cmz~6]߂kM}Ckwpe|j F1H;ɯj[ν{_0xp ? _p^/ Ð]Ć8Hl("6Ć<wVo:&PӉ^ 7TLa^#Xp`?/fc+z Ml;%_ZBʁvЮ!LF`\opv@\{6{Sn#ݥH1 ~(8>>[W,֘¤DozbHo8]1 KѨDo >Ň\n1ۏ;w&r׬rѫVέL\D8ȷ JfkY1& 3 fu}1s*XkqRݙ}3EDݽg{5ɯC%Zc] 2DuY>Y\wTw\򅧿P%6t\3)]Ow((:_wʚK?)ݡ'B>Wd>X'z͹AGmS?%-5Vu|Lw)>cSt/o{7jŒ+|lS;Ow1w1~ ձ]Vù0=~h <: t6f&c-[H2SF٧W dkTX7>_`=N}z/pㅊW> \W;;8]0{bΫa_] .8~St-J#ѻSߣ;/js{]}P"E_C#dwxu ,%>\4@]_(R{{e/aa0ɰ&h 6BF`.ijVU>kϢ샣L^̈b^lG?{{voAGE-y-ҼuwέPs4/ܺ4?gk_޳[BbA"EN /s; *SJI3y s9bNpWR9rd7782+r!9#NGa|,ʐTQGnQ%{ASu/8r#H̜Aȃq9Y#P;8zt~TgȜQ+eekx>\y|AG PN9;s)H><<~D{R'{]{u~?`05^W#++;ķLgyqcȲV45Ϳ~۸ mEo'\ _&ޯa˞6d㦷Wc3_ehCߩ~J__:ٓ 4/.u2 3s˟=[Py19I1!7S2&y"Ƅ| -* A.0|0/a_X*{_H xƶMYrbGEqg&S8l.9=GV&􌮲e=P~ С_ߣe}]Pl~}anx%66$@ ʼnw('XrblĹ sQɦM4SNr"UʰigʁŸ"ŏC\xo1S~ȏX( ;t&EN֨5rIJqGG17v-FN@sEܸQWmqYb?7V]meۺp47n;Qjk.ymmhnRn+?C| Q7E,ephq Ƌl$r#/b}Ѥ c0Pg }+>~W ?6ʇ|u[ rrC;,$QJQʃc}Ķ6϶-ө|!_g Cj oH!+c}*CW כPaz;;9{pe@`1"5|=Y S>?OƏ%U8O\7Q{]^D7.7ʹnK&z+@ɮsݩ)[Vy>wKqq9"(j\]-u{\<\}\b\3QC^/\^Žຕ<{;׽-u0q]}/[En׵u(u4t9H"+c?5Rp \7iLC1ňts\<K6S{O~>ˋb;U+!Uj{+A:GTU>w\>[g9q{\9Kn=_V̔P ׭ЊE_ gܭp @;Ck7+ԟEȜ= zo3x*A 뚍CͲP{k]XڕB])rcv+߮d4rذ+O[]9b]2nͮpv唅ڕrk]h+vj/O+\ٕڕb])"ѻ.^dB65ڕ 3gsayhd,쳻N)kW^h gW^SH +X-va~ '6ahqL8c}PLlw6B b_W8* /0D_niRIQwc+ºFCxsJHrƏ1&c&F?b]}Bd/گǒ~uF_ܼ^$#5ȶ$/ ~){\|S%Z.Prj@\Z.P- Trj@\Z.P-(j@\쏖 TJ-- T,/j@\Z.P- Trj@H- Trj@\Z.P- TJ\m 4<,i@\Z.P- Trj@\Z.P- Tzrj@E- T\!hl-(rj@\Z.P-*r|%Z.P- T\!hih-(rj@\Dԏrj@c)f4۠6ȱ ZN`-'X lf4۠-7<mlf4 6Y_—vwr wZУ C>yX73!97/=|g#4zX&Nh27Y`,&ciZC&ccS`m 7ǶR|&ҽܨc z<QXWY|K䡷_/s>[UWI~yօk*W"ܸ8ݏaƏ1 z_+/|n\R/4!%g4q8Dpͫ;S_ua6m_ҁu(DJ\w?B \% *{|jUC݃%{|NܟH7:5kt2{cUYt|l70 /W{/Ʃ߫S(w W NJQ :ܛ'Ŀ1b|N"5'X8ȟKr[xpp^=o#f{2?8?Ҿ ?gS+;~($t_"aAH?o`-2~b#7~^C?ؗ6BPoº,U̿9#fwda$|x-a /#77#7}h1|e|j F1H;a)VC=gȽ{_Rd^A‹pU#IcH8H$ "FH<wVg9*&PӉ^ 7TLa^#Xp`?/fz Ml;.cq,wlL^`Q'2e .1 :ظ77Mba2:ؚ$$If!vh555#v#v#v:V l44,5554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4po-Dd ;$33>   # A "` ",9E|f;w,@=,9E|f;wt4c @Y0,x} tUIя y$̃t$ ! &ґa@P$$!@0g&8 _~1Ȋ2*ìw:T%Ϊ9_o"Az*H&rk$8]~TU ^.1фeot+;*$M gw;W m*SEx k೼ > x?rI[r Pn5BD\,\tOGȥ> 1>ys:{V&gK1x 0 y**Z\'Wbx"ȦkITTT bϸwp>lR3eYrvdzY@]*&^3 H{'-b,똡ߥ螫Eϋ>uLILR\^| ?NpKh+Wz 1E>-Z3 |ŇqiJUGǼBLf| Z_d<#.$|l{վjqLK1*c[/߷ c b}u_LH  qާ=CC-qmGx*v};^6;GMEmPA$ؒvX +B^氂1eX^x+0+'>o/:YXY`XE+V{`RH HΞ=]KVV+fD+ 2VΜ3Sd`}UfXIVµm+a{VVW)` beهK\u]a$+A͟-F VXdzԣ(V$yW +VBÊȮl ɮdiࠕpp/ܿ7 *R%缾 +ڰ2aXq '[xÊSʄWZb̰,wooƴ:;RJVVXAA +W+V-˝370u!uFk~~P b=YMsc3?rdΏ"c3y#?^}Oȑ:]i)/:Ƀrܱgzʝs_|ihk\rx+$ >(W\Z&.u#r1򟁴.VIY{/}Ng6?Ôi1.ANbЧ7yT=*̫Jg=h?@{ u\K:H&m!H;LfjI$Q%s)Ig K ?g| QؾTS-}Hx[L ?<.ihoeǓX^lዽ6k-ON|1NyyN~rOz(xPn~]?yJσϋ:X%HJnjC?`1 r..کEe!(cEΗ.j+^4T*5 *A:׫3C^ܣe`a$?Rb}F+h9e:H j6=XdxX~,"[( -h̏0o@3kA\yF;%=Kdn=p58LsE-K4>S' ՞K>/g}^=w8\L=KqC:G?(E<-u!}J-`e/. 068"xGv2~"_b>@c8:sJr\|,{8F܍%r;Cz(=/vru\9X%%u^``ER!|W(Oh+2TUh*8Qu p/`62>@  >U|T|)S"<elJnZWv9͹FY"ݼ- -LQ#$G?N|; S\hPE`\A?09?&컍P$?8L|WCz'wqPr} x^,zɂ?0Ix)ϳ۝啇!9]78y0'8ȕ9X'8s{IJH< X`~9CSmgѕms7(~m/V;y[mrVnEzj\mm Ugk{[u>z_on넶rz:6~ىelzAkW]̯Wތc_4HW]l1:5m5g5| B-Cү?~RƨϷUpm*bnm:b*`d`$wHywJ\>&g蟵1)v3VO |u|qODF<y!c=Ao%ݘr(J<Jzז(*K6VT^כTU44^[#[^NýoQlH'f0tfCIfNfIwL]_kzNM+Bwީ?\^qy,qC#ОQ^kG4^fz)rs>!l"ͽ kKHC;=|_9~uX"$<{9~WsFˡOWuq3~ɔE$Nҟ-ެ4ړ-NOrO~r로ӘAIN`9\=y@y^q.|0n-&V0_l+7wCg9&J|=SyB8Z8+|=BBpl9Sߊ<^kx ;ώ??xvvvכSH;\qLJ%2cC/?~0"I!_={I_lY'}1g=+Nk~faQj_ί[b.eiG^P[E y4pɃo8isvOJ`=(Q"c9\=w<HAYHb^)εpǵpG˪xê]uU9xʰ<`?q* JG^_h-x1cwx}^_%눑1aDJ>zA^_3>^9ooq |!'ɜ͜•~5ŃP /sq|rx]Ϗ/x}F9|Q|T\`*> W+kAepzB;Wy`4;Z ISX3>sUz goϥ)^O~R^՟fUƈa$th?"Rg,#/3^G K1a$Y#ۍf浐d#6K%ahdG+%*ïvοFm8P@@~P`/s<yتK89g]6'ן{*~ÑB@:HA"c9\=y@y^q /"%TF??Q|$?pI8Z ^?PڨhggQ6$9 [ ?ΕH&0/$@إ?b@xĦ(#` D@~U?P4@ߴ ޤps #Y1ÈS#]ln'[)'^c*% !IxMG4/Aש`U}Zrc wq . ȸ!.YyzfLuf=bY>$JW? wH|6퐆nzC(3Std֘G~5[kv}˝j_3aǥ{d*gvW g53W/g==w"~Ruk~;+_?/ uڥ_mV*-Lu gs +sokگ"~5o;o0/\;Cn)Hk &F~J}d&>}dŬdIGf%Y@iU HļbCu.`,p;|_H7 8q/V~n/M< 3Y$¼il^Ncl|uÁi# %ycG_vj^Lyu(y| g;t—+گDyگJ}8>`pfdp.-eM,H'Ɨ:r)g 0_)\Y}]׮E]^!~%'QQ?M%]NF!vf4ѧ]@xzc  W\XB$=iMFܔoWxv,'?-^OqR7%ak"O6zϻ]ޓ=b$0T>6E}gOs>R?sQgŗ̞|ʤOV (4ȍy8ڦy%oNesGkZc\Zt c1N;y]c)NZ+Fvddn N0O N_Q$tIr:Dc1Np}qf#ۃ'01'8Qڃs=q $-3-8SvKvCƳvS>{)1]GɴMߜT/)Onz6Zvt/7rS?_)k:_WϏKd>elw\?^;1yϫO;ܞ˅(͙\DPYy/@ 7W_07ğWKߐ)J`2}C)D^ }CNIߐSdfM} ;ǣ%uT񻁔1HkrBx .שH Hϳyqxbo!ʈg%[Uޢ"Ho;v_-yzkh[[ۼBLfŅ֯:؜t۝l>j̊w.۪WʑK c .jћUЛ%osxup`3<8zm/zhS̽혆 "7@u߮Uwla/N};_t9tLuV%2TwV2e,9g.r*V9%10Cݭ3tsiK7߸ ?Cy/y8b.Y]h4̕pp,.۝T:! CӦ; w-1m͘VgG ߡ.EН+uInܲ9s#KwhO9A_q /qG+V?^ W쒌u.[=.}zcv+Q+oa{dr}I3~d1% IKRXp?[ܡKlQ* ߽2e{zm/*u=)gEmۋ 2C|FxCx xə!_xڲFH; /O=pXĀ:YTFm`-AlE2fx=1;u#7+V9.3LCm{%s5aWlQ ?CZ^]`++]P3oS4@ 8DØ(№ܧW<NjOPŧWLh*÷*bSP6H>^<Ӳzm)=|kp^.bc|q1pb#Ny"џ1yQi^4r&RL$V&i952TN9N90џ#1O G^X![8TQG~n-qsP9G8rHƞ~ݩr0$rw>E^yeYj{e[ z iKЖZP| _tWp߰y~3G靠###p‘&|& k/AYp;3k͑< M2X÷Wl7> GWjWp앧~ٶکjsc"_o[퓫=u|(m}O[z:_._o_/;Q,B>W1رWߍPEz>J! y/V ILtd?̫SVC1 > =O 6aÿ~*,ÍVƸ^xn4:_؛ύymdhDߞcc^w# *#9~S>=185/CT;.S|5I+^"0'{/M_^lK+y^ ':;&+1w} `]5;&S iPwE|wj,׼v=`PxZ8+,W]VI.n"Z6q\ *l[mK a<( D9J?0Ӹݛq;͡O>qa$tgoRn^DFvK^USGtXla쏑= #Jm{%d⾄,uj ҴQu9auUJ\Ye*Ҳj1M(qdYHb)qεpǵpGu˪ê]uU9;`?\qs* \JGXdu[-\2r_F#s$m׭uTrGxufaQx,YiY ץ[-Դ_ec;u^C:֛kL\j%_Qs9H|lx=Ysk֫\wAjvφ$uLG֙FR9*.EBhץ)Kq~\R՟~fUuƈa$th]]"uR떎,׽̸1<'dty!fd#6[>U2v%*ïrFmIM{A YđE 69^%m(>t#O5)q&^H9Q#_Xγ(Gf;^8r` 82+MGpu҂4 G8rboGl8d8r DT_;8K#d8Rߴ ٵ|d9Ǟc⏑Fb)R 4SFT2Kj ˗ɐ$<&cZ4V/A4X(j =O̯@=l\dsw5c=o .^#_VrZy-C*$y-4kkpL ƭ[cjpJ6y—اJ`Wf]iRJnSdؕVjW"׮,Y`ޮ|gvG6ybWpP{R]˽jWsvgW2o?=w&LaWv8]y9)rZîv布ڕ9IvŮ?/Fb>$`K跬cQSLA$}=&Q_ZO_z\rd̻*6ynZncim |E:p@Aq8ntve0 _}8K_% si!_n80 xd1oqkN׋#oE|c1"xNr%RՕo0/T5_:#_DoF|i#_ڈ/mė6KF|i#4;#_ڈ/mėm}F|i#41K_ڈ/fbė6KF|i#43K?#_Ĉ/mėhėfF|i#_ڈ/}1F|i#_ڈ/F|i#_ڈ/mė6KF|i#_ڈ/mė6Ky4F|i#thė6K#_z_8ėn4K#_ڈ/mė6KP|_?f_ڈ/mė6KG(_H_ÑF|i#_ڈ/=M_3Ĉ/MF|i#ŗ6la `53oę7q!m0la j^J/ro;ڐb܆d; 9ِO] SdؐjC^N\ְ! 96dN !m0la ;.~$15LiY-*dƀcT1B $6ƀ}ƀ-4*K$bU: 0fg+񅱙.=}mq mlK.|=ǵp6 09.5 Z52"_p`f ?b׀گG~9h<:˕HWW¼PWF|xW'h@KyGz.6 Zf }KQe~UMlS).3b;%d8n(\q%c :wsIZRAw%a;k"g{g.ـipӝ1P[m`T=6E}^=rܿ>RsQ^ŗ̞{ʤOV (4ȍ՘ڦܿw%LekFkZcԒs队Hb\w1TRs۲Ft>ddn N0O N_ŵ+En8 ]*p,>8X7\u@pc!>m@8<ĉ>m],ޣt*[-{l`ZH\\NIIz#I!v#qJH"w\uo.P8-Վ y'2&ln.~.c1]ʩp ñ6z6U}THgv/>Xd{%zK9|'5ڽ}? N$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh555#v#v#v:V l45554f4p$$If!vh5;5n5#v;#vn#v:V l44&6,5;5n54f4p{DyK  Gl_Redaction$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l44F&6,5;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l44F&6,5;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l44F&6,5;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4pDyK Gl_SecurityCategory$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5m5#v;#vm#v:V l44E&65;55i4f4p$$If!vh5;5m5#v;#vm#v:V l4E&65;55i4f4p$$If!vh5;5m5#v;#vm#v:V l4E&65;55i4f4p$$If!vh5;5n5#v;#vn#v:V l44F&6,5;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5x515#vx#v1#v:V l44F&6,5x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4p$$If!vh5x515#vx#v1#v:V l4F&65x5154f4puDyK  Gl_Redact$$If!vh5;55#v;#v#v:V l44f&6,5;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l44e&6,5;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p{DyK  Gl_Custodian$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&6,5;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If<!vh55#v#v:V l4 t0655a<$$If<!vh55#v#v:V l t0655a<$$If<!vh55#v#v:V l t0655a<$$If<!vh55#v#v:V l t0655a<$$If<!vh55#v#v:V l t0655a<$$If<!vh55#v#v:V l t0655a<$$If<!vh55#v#v:V l t0655a<$$If!vh5;55#v;#v#v:V l44f&6,5;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l4f&65;554f4gfp$$If!vh5;55#v;#v#v:V l44e&6,5;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p}DyK Gl_Rendezvous$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l44f&6,5;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4poDyK Gl_CMS Dd  >   # A "` " l/\C|/-v:V E@= l/\C|/-v:VhHv0 YD x[ll18Yāda)LdcpS.HTT+%#PR1SZmC P(kAREe}l{w}޽= YU@O4K4ǕDӈW]*?i%hbsSuofy4@"Q9xۮ5ᶫ!+Dۙ&}3w,_ z>Ȫ.z\ {6(G1uYdݮEG[6 VA^V4  hc) (z51߳mv!-ơeR'c&Z4<&C7]V.d 8tBY\zd]hCs)c?;EnKNW@uC,Um,I;qIFv2Or=eGhn3ِ'qX7gyef2S1Of)vb`.St>Nt *ܑMU9G?ꠔhw :8>zJ`{Q:x1J^wK7^zJDYﵨzݙ}y zWQFs^?+7zU_RO{5=J9+J,!ZMjM?PiĀ:/DQ ȳO1xywx4 &|G֮Yٮlu[ 4-3zP'َ=Z 0o0i[2N(&aTt>/R`SQ3$z:1BA+ָs]];G1AI͝rHʝ1!XqlɝLǝwfɝpWٸnyeF+ws`t)N -S6ql;wÄ> &]s%r'םvi;[To| >ѸGW9:6Aʜ7]SEfy4}mmTL% UG_(pTkU a}BHM<5 lgWC}?m'$'T'oٮ:gI8k{,l.5!MO}DMdP;_%hl~_>;V]אj+߫< yr燃*Mqøݾ}tS+5ou8yo6Aڠ˿18P_;_ּY?9}k9ւk#' ɷǏr.Htadz,mYH킘oOoV3ۋD{qSpGd䉰~][ێJesd }J*=Eօ/v }έ O@ot5{f=Ep@I"ӛ/Pu~~;~G{5C^ƃ9mk7q~^m3X;毮^3XwפC_5W bא5Bg*/Ծ|˵Z=]֤[4BQ 0&k.c-C5Cɷ 喝Smuj3ʓ|)T6T>=ϴT˜T=1}UlF=Փ\w:ڈl.0f`vt#j;PӅvf+~f" 8/:QWy55"a_3=dB-,ހ;CÏGoY/KiD_t ]?C͉D݉:٭ =I k_S[u:~To_gd~Q!rv8e/K 洶8x,//1Mrd>*x;uSü8ڌqzt>@:CnO? a`?:[ou9wXSuM8nm])۠{Mh}.3uM6`ό9SaON-S=NJ3:%N 8؂SMZlyy Ax0\PÖV;_|Pe ͘ύ(񣌹uʡu\<[enK<y^^ 9Ip8; `kgE[F`W.mAN[%gΩl9*cFyTI(7ʶ=u$ia <ж'\w(w(xwKT -W˾}Ҝ_,e9QR[t|XRE<±R~aw[╤,㕤W'vkj:^Κ:J-$pR"'fH2fHᘡ_45cW~cz惻bB—2.bYf}/Y{2_3kaEEm`v,E [Ţx~7rL1~;~ct 9|;7ߎ߰o7~#7c=~rxZ_ ;8U7 ja8IsH$$If!vh5;55#v;#v#v:V l44l&6,5;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l4l&65;554f4p$$If!vh5;55#v;#v#v:V l44&6,5;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l4&65;554af4p$$If!vh5;55#v;#v#v:V l44f&6,5;554f4gp$$If!vh5;55#v;#v#v:V l4f&65;554f4gp$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4gp$$If!vh5;55#v;#v#v:V l4f&65;554f4gp$$If!vh5;55#v;#v#v:V l4f&65;554f4gp$$If!vh5;55#v;#v#v:V l4f&65;554f4gp$$If!vh5;55#v;#v#v:V l4f&65;554f4gp$$If!vh5;5n5#v;#vn#v:V l44F&6,5;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4p$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;5n5#v;#vn#v:V l4F&65;5n54f4gp$$If!vh5;55#v;#v#v:V l44f&6,5;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l44e&6,5;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l44f&6,5;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p{DyK  Gl_Clearance$$If!vh5<55#v<#v#v:V l44h&6,5<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p{$IfK$L$q!vh55 #v#v :V l4655 / 4f4T{$IfK$L$q!vh55 #v#v :V l4655 / 4f4T{$IfK$L$q!vh55 #v#v :V l4655 / 4f4T{$IfK$L$q!vh55 #v#v :V l4655 / 4f4T$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4poDyK Bk2351$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5<55#v<#v#v:V l4h&65<554f4p$$If!vh5;55#v;#v#v:V l44f&6,5;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l44f&6,5;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5h5_5#vh#v_#v:V l44d&6,5h5_54f4p$$If!vh5h5_5#vh#v_#v:V l4d&65h5_54f4p$$If!vh5h5_5#vh#v_#v:V l4d&65h5_54f4p$$If!vh5h5_5#vh#v_#v:V l4d&65h5_54f4p$$If!vh5h5_5#vh#v_#v:V l4d&65h5_54f4p$$If!vh5h5_5#vh#v_#v:V l4d&65h5_54f4p$$If!vh5h5_5#vh#v_#v:V l4d&65h5_54f4p$$If!vh5h5_5#vh#v_#v:V l4d&65h5_54f4p$$If!vh5h5_5#vh#v_#v:V l4d&65h5_54f4p$$If!vh5h5_5#vh#v_#v:V l4d&65h5_54f4p$$If!vh5;55#v;#v#v:V l4f&6,5;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l4f&65;554f4p$$If!vh5;55#v;#v#v:V l44e&6,5;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l44e&6,5;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l44e&6,5;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4&e&6+5;554f4p$$If!vh5;55#v;#v#v:V l4e&6+5;554f4p$$If!vh5;55#v;#v#v:V l4Ve&6+5;554f4p$$If!vh5;55#v;#v#v:V l4e&6+5;554f4p$$If!vh5;55#v;#v#v:V l4fe&6+5;554f4p$$If!vh5;55#v;#v#v:V l4Xe&6+5;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4p$$If!vh5;55#v;#v#v:V l4e&65;554f4pDd e>  # A "` "`dDn2'y@=`dDn2'l#R0Hx] tUݝIAD0@G&@Nh^tt!B'CC@F'lU6;G"AQ]3쪌hz9_u]ݡs֭uFA$+*B ф<K{# Br̄-s Q̈́,߯ NAW* ) xQAGG?k˔KA鵣a$7¨uBqQ6iT;ŒyyL8?nLĺ; ra lj4ױHp鬳%7Ⳕ\:Xz>uۦ6dbnCB%UBFh@*Ww2T*PWo|@ ^=χϿ1gěSІCX>5c6 m;Cu ͥ:KW#i;ͮBAK׽e 7:#WDZ6,w?@gL7zOW[A> }},g6nGGNf]t2&ǂ&'ˆmƨO>?*Ò?5|dC<Mc>{1+giRL%mI o: } .8,+p/ |+2:|0Vnw֑U,(x|*&w=-|AH7s4dϳݰ ɿC?,seߝĻA_nu&ЭazwŴpޭ-ۮx75:K s;"dAnLU{] ;˷|ȞgyW݈ =ǻe<ÝȻcUϻtM_#qwcnwcVݗ@tyЭ߂n v]LI7ޭo5P]DyKW3ai&۔kIҼU\y=2^4D)~96xݠdc^d\;> _8gpTP6\ wCCC}JpI[Q@53\Hυ3h9(FHk*7yKԓY=Xz6$ ,ҥ;U5A3uƩi3?CgX&X9c!1뱼3h=gHu)'8{\mMɶʵc~XOuUlk S39ܝ1mx87Hq| z&GXv˧| |:|>m tAl Iz̍ԝպ;kle?;+ucʖ3*[.UHҼʖKԍ,˜ϻ\ϻdi]ҼܦMlw.)׏7@9qkLK"ΕׁНC+54/vZ®aWvڋ]vF}t ~`ړ1'HN%hN=hM6"&h=&ԁKqQ_?5?8>d֤ (zfs~4zioDup=X$՜[/ݬm4/b`vj< ܵi%ƧH?Ƨ:>iOZOW ס#""9'S`j:gǫmBU`s&P9$sd4 "]´O"{'YZ:`p#_ rB ]1?B4Xv }QII8k` wsFIa~^E9pյn@"T>x~aL{&l4.7DvoƕUX x:lA|S&Y0fgf-r< ̦L>S*s,#y-YjO{&93~HiB4\gDC@66~Ep4`pHcpW l`*UqCn3lw| UjeVA@ 70f_4ڳGAjA!td{— _i "8|eC_9|MWb䎯{tȍq@X|Wb2_Íier y F!0Oi|-c䔃Ԃ4CfW 0~6[ _'~ |}-Q+_Â|JᬟFtꯁJrkX૽c.|U,RXXE @~(\(|^H yy/ P].\_tD(OR4^^(LY5>d@]ݠ | /@YCWrkG|oK ֹR(;"m'bqkďIcclf{oQ?Xg@Poc}e}e-/AvۧX,b|Mk+W=7[+*`eZrZf73Kb|}xB_UVxWD~ ᮨ}z_;r_%+f6[F5҉i*w|]񅯘+@A3̵>)*fY6f*1ެ񅯂ڽ7k5Fk>tuo4_Eר hYkqz5h'FvF_:۸m)a 0:*[^|.ѡ]"˅_xW d_ /:&<3P:: z1~ulU2%߹2qG#}{ˈi/"@wa1k$rcy5^rh,;[A#}oee4ܗQKa'- DxfXH\ b5-{~uQsͬ#Owi!~gWޣ~~qdB]Q __+_UԀlmve} QqM[ʣ8?Py\H9ُ\ )Oa_B_gԅ/,v摲Me5 e /`V9ESPZL/ۙ%b|MC2~ke5"M^dhˈߋDr{ׄ DWOXFAA|MtkB'ؐť"˶8dmEnmC˟OTm{޴öek5'8 YX.qsms\ }A/_xҭӠ?XWTٜSP%!>bERPhZOB:$$If!vh5<55#v<#v#v:V l44g&6,5<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4g9poDyK Bk4177$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4gGp$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4g9p$$If!vh5<55#v<#v#v:V l4g&65<554f4p$$If!vh5<55#v<#v#v:V l4g&65<554f4p$$If!vh5;55#v;#v#v:V l44&6,5;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4p$$If!vh5;55#v;#v#v:V l4&65;554f4pDyK T_AdministrativeRoleDyK T_Administrator}DyK T_Aggregation{DyK  T_AuditTrailDyK T_AuthenticityDyK T_AuthorisedUser{DyK  T_BulkImportuDyK  T_CapturewDyK  T_CaseFile{DyK  T_CaseWorkerqDyK T_ClassDyK T_ClassificationDyK T_ClassificationCodeDyK T_ClassificationSchemeyDyK  T_ClearanceqDyK T_ClosesDyK  T_ClosedmDyK T_CMSyDyK  T_ComponentDyK T_ConfigurationTimeyDyK  T_Custodian}DyK T_DestructionuDyK  T_DigitalDyK T_DisposalHold}DyK T_DispositionwDyK  T_DocumentDyK T_DocumentTypeoDyK T_EDMS{DyK  T_ElectronicDyK T_ElectronicDocumentDyK T_ElectronicRecordoDyK T_ERMSsDyK  T_ExportqDyK T_Files{DyK  T_FileFormatsDyK  T_FormatqDyK T_GroupsDyK  T_ImportuDyK  T_KeywordwDyK  T_MetadataDyK T_MetadataStub}DyK T_NonCaseFileoDyK T_OpenqDyK T_OwneryDyK  T_PaperFilemDyK T_PDFoDyK T_PDFADyK T_PhysicalFileDyK T_PhysicalRecordDyK T_PresentationuDyK  T_ProfilesDyK  T_Record{DyK  T_RecordTypesDyK  T_RedactyDyK  T_RedactionDyK T_RegistrationsDyK  T_Render{DyK  T_RendezvousyDyK  T_RenditionwDyK  T_RepetoryDyK "T_RetentionandDispositionScheduleoDyK T_RoleDyK T_SecurityCategoryDyK T_SecurityClearanceoDyK T_StubuDyK  T_SubFilewDyK  T_TransferoDyK T_UseryDyK  T_UserGroup}DyK T_UserProfilewDyK  T_UserRoleuDyK  T_Version}DyK T_VitalRecordsDyK  T_VolumeLDd $ 2 0  # A" P;: 0)S @= P;: 0)SaBHj x]pvnw/r%1jјs CgQ"(0cPK B1fZ 0c+Ԏ;vX`:jqlK[V[V)w^re^۽}{߾CuX$ *f!y\P;9YpD(籧{^vlL4ǿ$s,H3Z\.@6ݻLg];:RNx8پiv,۴fςqHk#"5|.a,wm",5ދ|KKYq6ºEV(cp| ?W43]7`HoEe|e;fܰ>K8az|VQ}́[ 6k )KA 3t}9 v97q\:,͹g47~*Fl^5T{T<ġ|6^OP?͓FwdUGs@)!d(,a=D*gH[l)Bh f=6qJ486gWvݣD@|hZ91aɁL5jƪVPӕ?' /ihtHɑ7/{Fܴvպ #?AkA "Eq­%c&YYoк͚)(OF!y:is_ы;6Y껆zJA1PrnΡ̩ĞSw9Nj'5(|1/e [ 6Õ1ԗMSұL5)_YBډH5p؏YW^oYfM- XF! 3gP6h>SqBg*sM-јEb;g6Ά*mw<.ĨQ.ڽM 4N4 zw7D,*>ogO'+N%IOYQTCUu,9s v<: kJ &0J7]le)fk[l9iʈ.CYz;fKHܩ'׽OtuJi*{ݻ/_*EصOJ~Pbl1^=άuկG{wx bxÃ^>z^J:T{Js(&]3maFzfG=qS+퍣,H{nyے 8H*<v'(A_N}q 畼=T[f^oQƵpX`}^ ^yxq=KN{F}Grҕ0.q4Qn݅: 5nMܾR_^@j]Kya`7NA73A*P/{B<>"1:א]K(N)`Wv<.ʣ>xLJ5?կ׼^2̄MY`]uQKG]=#ئhhwgׅ(܍yf5xB2:(yh`d+UYs#%!扤Tblg= XJ4Ϸנ u{,A8XrBZ<0s+vpf:eEcȝH ׅ7;m7VF|23Y)S8Ve[-bp`J} 6C6g}CRhRnP-lz:f9B48^s]Sq^Wz{z~dkKzWe ժ\RzK/.WP/Z9TJy-pFūo lvtj˦`.ѢZ`HX!l8"tJ!Acc 6bÆ]l\l->\bd'BY$ _h\|Sc*?zH\E?}Go>b||߷@ξ]>E~d77]>~Rܸ߯P'Sri/}Xf۾5׍MbSuգ X[OɘY=^N7 C^]2C6m?3t^h4ẓHlyvڀ>X}FlL-~9 o8, i<*VeTIeޏPb*3Sé2lقٔw{#{ulʰzsRHY@eA,Tޛ9y7obYeb ~;<=x{>0[,ouTyw {hBޙ>%;b|_N}lBTV#y ;ƿ%fYdĪ{;;[ެƝ-wWkv"m=>y^W}uMsVQĝn%N*2_vVH(Y-+/eGaW288U :: ŠfA}Շ#O񤏞jsM18Ňs*.fǽsAYQq…V`ql?؀bu>|48h\㠬8ޥR_lO/=6ҵA_߱/,ouJk[b.Ŷ?!X? /ǜ*~||kNUݢÒ57ڹC1]kEf.6" 74kP ON\lh!rҬ+%~9i~k[ oNZ.X,Ɯ4Վ!v>C2{<{NRŒ}IN@Ɨ*:''5nǜ4.SNZe}E.9inw6WNZ*IU9Pl9iavˑYrȓR-1.?/2ݠԖJ܇ܷۘpꪓ3/Y-~|\<w%hkrͽ;?$Ou{sW= ġwnKw4]GиuiNBㇽDd > <>>  # A"`"+>:@b$-2vɲ@= >:@b$-2vɲA /Q x\ pE~;n~F#fpAb.%WMypJ"T3d$BE]ga:FJ@ ${3=_vKY7v P TGl<@r u u V<HCeF[R96wilL[8n5'՝4u8 7ʙKaJZprR[lg, 4]DߞR4 34jLKùTz8&˧C4:(P}_3~ ,MmezƉoD>͇}u7+I 7f(R@3z% ~k7-cӥ]ʓ^x/mc`y{GH`m֕w dc2ʯccU,Ozo/Rw$nĴooCٔ]=)$7vj { ]d3U~\pn-BLe%<&כ-N*b^Y<{%]/Ep j*1NJLjY5W|lh唝JvtgH;Q{ODvCu`1j٧lU3Q>-8U28Q.J;jԵʘ*NT8v賣\@;xe0Xf?"E یHu.VLZ\uE2ҩ]Gp|\ķ{37jpAeKO9uȀ` 4:tY?1:tp! :[5f]͛r"*A=NJː?ST֔S㘮؃ݷ=,J8h{T}8k}9v-})E?>CR߇(}h!:K}HJlb h!>7P"x*U~'|3)۰#Ի.5fJ{lO2dk&YYKt>{Q y&0nfW;k>+}yy>Ou8ʧ:%<3 lhLt;;nAETMwOw,wm%t^} !N9ϊ@C(GqOl5:#{sfďC~6 Atžǜ:fNGĜ FKw̩e~߃?2goҷrn.Ze|ʖOЌO#©[Br.hWzLlmw'<Éٲ-̎Z'Q]tzyvkϖW RXp #MKPmvLl[+Q6%<Ϥu Ja,?4mo3΍N*[b [}Gڿk$#8FSK8tƛ6iwp(g KV ߻~/oѶzMwDgߕ_qLW&u;i87>Q~X6{}])ʋ\^cF!zCг/>J8?vb&pAք 1_Pք7q~|̈ oMPo}~uQ(Bj㭤_E_-F6j;W=Gi׏EEf#t0Be94 \PLDj\Խtji \jpqA~֝ ?.d a;Vb= iÞT__%er8E/>é!}$]_jħv)*" gQDI"I2>]q&9*ٚkHĘ$!z$czs1#A'l#F#Rs#:T2kዑQh0b9qqZxa_{1El}F1ÙH0H%P#8d7.9SqtaJ+FCE?y5OΩmv?C2/ߡ>G^[@e9ZlDw|]i'򻅑~`ظ0?6~`؈՝S-.iH{HNsڱ~qq9q=\P1shr5=pC騡sc%<J9i LypREtJ87"75y lv7[wdQ/|o#3~'@2[[қ97hp;}=LgI7aloc`fՈzJO~_+|{Dd #&9tt>  # A"`"H{f9(}&XH${@={f9(}&XH|S^zx} |E~͑dr$€Q@DfBf+.x. ˱"t%. jPPEtS[w׃UꙞNaUz* cl*>_+`bIV߮b>1 `b,E+[3P{¹wv'A\:dւ͟е㭒k'vYї: g ʲUw9Bqv R8z *)uC upN~n`Fe:ӍgUZT4vyt}fp*ǎ"W*SU9(|߼etRe.Y?s |WzVɧT Z)_V[xT>} hHpZ2 C U궰Xιq!3 Om߯z=}}HrON۳pi6 Y!.8Ӵ/˖ۈCW tm#6`9{>k\pslWG⯯ͭLNr-sqd2EE& m̑l^sec^]eCyI<>*r_wnR>dp.$ T- .ՏPpqϓU^x,lJzaUՋq^x{%a@1G§.#Ufκ"I$LәyUEMPE1QpC=zW~^êQv`LLQ1z )l^>| ^/szXspv#VWC0v'szf9kkq~e0&YK>yKaySdmMb=ܽzI7f1&9cN;s>XڬI|?]/֌Q8(b_v +_|!/aQ#K{畓}U`%Ӗ`Ez:rq[#qijEe/2b)QJ^QML=eWe?p^jʋ8/qtU(`&SkPڀ~6Sx7JyE?]x7Fǻ~]Ԧ{Fre{PףCHNQs|S^hcT4s|l֭oҦuS)ZS.W57ڴ­M۴6ޘ)N4Aqe'/n6ɗiD+S5/e`z44/oϋKqu(;Uv'Phn#ٚlciu\[St;q"6vm$cm$ҞSN%GSthjSiSʍnSB_{Ơ-I)\)lJ9QmJlJllJ_I6m$|r0n6Bk6_mJ~ _eS>ϦaSr%`SmN RlSr*lJyV6Epo0pߐUm"u%ݎrrЖ4]Ϧ (]C}i,mn}&>wmҡ9nƍ_cwǍ?6n}oPϠ<π<)}iO\M>ˑ1TGh!}ǧ2/i>/'WNiHOqJ}|eBL_)7W9hrt>y:ȳ{ܧp{cg?3K~oY-2_l m1I7ET}|"'>ބõsFJ`g vޗOUw 2 އ_;}AF[QA&8Fq9g;)}to8΍_kpcF WЇS|^tSB i~n>Vb[7On9jm>Nxޣoh\7_=߄qS3e\X/ ̗Dž;n|&G;n4v\Xs\*y1Or¥qaи ƅ,_ qad91.2f:fDfƅO<+Sg,3f3:3x13J1SgT}~ъ¦o/DNzpx~OVʝ)"k6#zC-FSTtDqFb@uzv*cvƦ?R=G+0Q;Fiދ,!WgC]5Cqǹ~w(nWb7Hp碠MNͿr1^E{leVeVSPV+@y9rZđnw#yǫ'?*,+{kDeU9F]J ^w꨻1KwY2Gdݥח^%&u#j$ȑ8Gq4'7KҝJPZGA%h F~|{)tvE8݁zO@U4,Nip:$/^ Jrtl_'Z{߇RH[{UPڶ.Ii`[6믑rMI,^Fa1>U>RX8e5Lc!;/8ˍ?eWTy񴤯\S*8rg6\>?ö#~3ܩZ?Fj>u)P|J}U' q1eR}(_k&K\]GpW\ m,t[2>0ٟțo:߇gzTW `69HA4xZE;6SN[6![bm< I }p΍RV[/񣮜㖠nB߷-~"*a3d])NrT{^wy7*:[8-q-u{~Ǯn*3yp1*UV~q=P>ռC?/x?>@* ]d۝8 u#bK#h ۝ ۝ ۝ qa3l`ΧS̡lwϏ:>lwg%c?f9mwVak6!f ].n4uK#mw_hl,r^۝;Z(?^!\/ ׭`;*߻4xs~G]KQkMo^靯-f$]ܛX |(Kn@&"77dA,aK{l8s1Ls~-8C6>yQsŷls^'AQfo/6y^Y^#ԴyZHCkϯtImGUUc G+FmIdVF^Rs76,l lfنkj?ȧc'u۰{N1E hv6i;f9mvan6!;B(bLa>>lNO6\NH_kۆa m͉چ*l}_+~N˟56,lǜhb5j-|3lN7Qfw-^1k6_a6_a6_a6kM(w--;V1_?6_1_nKkH{.s|.WE_Q\wc;alچ) #i%ެ/sͳ0rt>yο8yp26L_s#m5ln؆Z@|m85oJ7tʋ 5m(=gZm8P?a;ܙ]gm0|pJ:PU=.66Oڊk~uCy rt^+m;;bCm(_7aava66 61 ~x uG^y;V-۰2>mx;=)7֊ZmxJVX+"m 7h\VY}R {Ċ O}0׊hb~oVl{|!6~ t5 kF}ܒmɮq,m6a6_a6_a6_a=.lD[wb cjk@Hu;lLgNi&|?*qao\1޻?YCccj8:q: ć;区Ӹ!G9⏃} x{^1iSި;N1㵴1^aRcXc 'P4mͩ ^̜F&9x_o#dK(^P ?AxMHCO!jW0brtf#=lcUPڮi{h5mҝ!viGi쳅x${b'{^xo_> Ձ{;VXGmCxxݙ1:vȑ0!'|) :3q_6}0~/Z A8!5jh$,IX' 5P~i؂4tȑ&Au?xq$pA O ^%O빎 EH6$Z呯pGV-J{ZW -'Zi,*pTcJq[ؒ(c gW%\lt fۙ#VX,f!\.p+s86\gZfC|&!eBFff&u4:#<#<#<#<#<#<#Д gFc(81 1xcH81~< 8xp1;z;GSऎcN,8)1 NjxچC9U8wNc?QI2w =0M' ƣa,$G7c'?|8IO3@F/%9 (+7-u @a?47RC9C% G:Otc^:>5+RC7!SrH}LC4cF鳯!gsH}h~elk# ȕxODe#sȘqȠQ'!þ߰gGf:bXVohGxGxGxGxGx/az|&LuO~W^wz'b)^M}i.|ncj{G_][i^MZap[hO t3lکBkJ{Y}M佂vRa S!/z,_GY )#<#vWdQ!ڄLyP~NSg=l xObMe Mҥ'7Ycw5l5lzi$AOzI'Qo>=䲈r:z,Q>SR|v#C' y -MI53ҵ8OR>kOR~"AshI7O/單M?c]$!OVGѣ/*.(7XV=J6&8"П ]8!aZ ֣mubM=*U/C/.mFzt"a\0Qu9D=QGzCf%Ggq=ꈢG*=PQ8/"nң-k4=J{ C`Ч7YMtKDN}82|6X. TmZ`G7aN]44iu>p⋖φSԩ5uj(೾ذ!?ԩC:]P?b߼ЮQ-Q?F}޾Ӡ)aN3@Υ0(٨G[GTcTeߔIڟ'}jwvL;$wFwHuk:|gLl;[ll 9ov*cv?>a gM>)x35)m{kT\C\%no]3!nvNpn\& wfcѸ#/{#HW|鯣? iS(hwcۗC)4v[&,ߓ=K%?t=%L{oXmK ?bǐviMlc[D\߱_٨PU6% mtMC2[]V/}JV/2>.C(숔N=m MQ=w;yYt.@ ?D_S;6ͩKQw SǭC܃P3[˩u{ rf 0l8)z)|(U~)/z s;o's|筜VQ8(bGZprʕOU GtN}/ul;fV`n_>h !zK0/Cƹܠ~ ^)o6Yg$[ tXe慲LBPz44/fϋ1(ߢMNqjRDG$ =ۼ6om gSEPB|MnčR nP-JLCTzۡO[ ʾ̈́]5Ʀ,ЃK}rۡQQQ%*]Cq.th1_tʗQ sπPvTo;4|^Fٿ^,?J [ۃ࢛mL3)݃MFCw=a [2⻇u "cqoCqn"E.U~ ]&c]ML_r%/?3 *~9Zkw5Cyg]]"^vyPY>?! ;'ʣ~c3Tq]Cl4٨2+ololffz*_W (|8TЉ#^F@]3g4tלqkθuz/9:?gYVÙ8wug,;mC@v)m}[@mo!.I.]x H| B6Vc%*Cf)}NqMWڃlg };"3*9_ɯⳇї: g }C5Q]F0~uo)i<+tbhl g*ts_UtwߴZZ] Gn:oV v + 7bSX-}>U>RX8fYMg* k6~yv/%EV|oϚl|<+mGfS~FSlIr\3]HrienIDߪ*8ǹx|>SIkS/f7nΥޕ w5 h~0@w;([m֑c}׃7Rs΄QT9FH;4Mq噸-[}|YXCU!q4Qߦa~jICW7 4n֨-hJ jWk\Y]5$xRFklN(ˏjuG4AЙCƏw /]9dxPO2>mL9ae:Ÿ[Z?>t?L/?IXʟtʟ?9٦G +Tᘣ33Rћ~e{ ct;1 Ax c crۅ,PS .q|)qwh*d::C uG^yU sU ?ۇώg@ʋбW<.uH5+d)_GYyl8~ ڏWV+ ,E>Oh Ioq&sO)Q4Nh6=Oy_F]z@Y}5uT^^Teey| =r]y e ۱^jip?e ˢK}To\Ly0@ ávy3Ton]V>kOR~޶ionKb nu "ADoNq -R??Z<(_u zZ6 !Ջ>ܑxxoׁ]1܏7F˽쐾lMO$eگ (uMl]6jnIY[[)x<]<=^OOgt9|`b|wh|ƾF\l6|ȹJשL];\zho)ewXZԷ}\ŝ]ߑfo^VrJ^(ODۛmV(W-=75xᏳ9xm\ǖ5Ov~qh}NUφƝ]Bm_g}?v=f)}l/0Q+=jܪwu1iqqnxqͫ_ܝ]S/qP͈/woŋv~1;rj{88S?6SUnFrc7C8x劜ZJn>sOWdl;3Vp^FK^o E@Yg873M/?&d4^ؕ2b2U Be(h؋ R^KC=ȯy9ܷiv}FCGe}gŕE;7(ߤC;)q2 nP\eCi25ϋqxAqoA7=/0n-+Y&Tu!Du_t/GJL{'2OV2)LW?4?Sbc 6r,o'k6#/VЇQQ?^mToSڗCyìMzꏐ7G0z΢4UE;al]lݻGyz"-uIN/b#*ǰ~ӏzٮߏZ@Rׇ?5ǝR=0D-x]M>;zůՊz[|Hoi??1E_ڔCi{[{pc}>_@o՝61EgYZ|wRY1泌n;zJ?[A~}B<őr۹ޛ_unhYBjmtʁ9覰hYu>/T7R`|{ry9.4k`Or>K=3یbYuqia[JY6Yrz5E=݀,1g٩2ռ}5LffGfbfXmFfmFfmFfm渰͘?vo2m3nj6m&l3&$l3%t|fH63iY;@6^DmFmIWL(@ Il-;;u{<,1[5F ` YBedy eO[T0Bk^-:$oF7o;e1uO_͖DtMZӡ|΍w4 FKh)xaQm]m>/hӗ5QG4]ۡx;'x;4C/݄r|~u~$(nZhTޗӡ++kp΍2zـ+z!*SyqdEwCwwe2a.c'Řs r0n.mX{1ŽFQ4Pz/LkEyo/1|ΙYʽd^^[edGpMD($^_ܣ{|XkGT.`Z}4>VJ; Yj܉1~2+uGuGfXw&u#Y3]lt讧y'wS'xzzr:݇ޏt9JܸHwr:`CSC|^\^<7*^P%Dzo܊q'7}c7Nʾs7rh_9TzS}ـJ{֎:Zլ) iW^|U]K6u_.Cz/m *t޵6.Ji쳅$րk5`[I[Ȣ;淣c~o{q=Za9wW;봪P;bLE }r]pq噸-[}|YXCU!qqW0G&aM:iMC4 hfy/{@C'9E,/'EePXq?|nܕ/"zߛxIުe{҇^JrO_kZ{=SÔRX=}鷼V@PQm(Lh{.M l -ú /~![lJʙ"n-_H]c_R~6`h;ric/W7xEqW!,;ȍLkCbA^> E\l9~8E,ANZSO)ڇ0x[f8uP)!Aî`@WMa'WụUI?ZPֿn?qp;xDes,r?Pʶ伎':&sGsUv Թ Tq H}C}!7v3>KOt1OY<ԛvꢡ@Cz@Z8;/ߝX?~[?\eHDq>o}_ء87Z ǩL?y-~1.6;SkF rJ=3 x5'l33q{?'ga+ql59Ypɛ\ [V].wg{UZf얔i YYyVֈ_瓣ߏSF68xSmL^&Se+ְeư9m,3mL/21͹4!(M( #4-- r'x8=l86чy?"6>UhlbTӰUla[7VQV4> ~w~PqY(h!}[F;uH?oF?/J6ݔ7_5{ 4,itÃ7Vzd%*CV)8J[+A\e.rqUrt(]gՇyWȐϽ6a`ވƏ;%:mg^ mwMLʟWG[KkX7@ͪa߮po{>f_w +Gkz'imL{da _p Ծ?eWTy񴤣\S*~YM>'x w*h-I|IGSU= AD<]l'XuҪhANY&zMךݜK+?ʛkA7^ .A~׾&jw9Lg*S+-=Fy8o~,Celi1\fx\"_KTq'sљ_aG^+ݿunx*gx~]cxv#S_J*=8l6]K~wv\A6YSx?X3Nqmn6y+&sRKα" weqH؁:y!><ӫZ޷͉pD:;i#, ?r&Xc &&Xk& CQx065i^ιXqv9~ԕUqcyMOcIE9l̵pŒ}Ry] mKJx-qvrTxcSˬQfې1UB417r>ռ?TWq~ >@*v b\zm:%3niԦ>4=c=gT:/{F[ ǶÍQ3@\;^Ꝡ lhף3u*mTڿ^s(3 7,ʔQ(9Eqcyu;h!ܱ|w@(797Vkpc1Qռhwq4^+eT6ϣ3q7PnicܻhVH9گ^ozôw.z?44)9(;͹׾9:L7rnEos+hέ>Z)\z_'dwcn-Ź(s+A9,>u9f `ngp$0+dz-C5¡x?dt"V{H]IqcCWN~?]f ?G4GΧHMGKV~>{=/wɳy:%byDy"WV*Qܶ|IoEvȦC)x_GLߏ1(~Lk.X{ߏm^ۡvLݘM㻱3tkkrpM>!{2[1.xY`տ[M)Ӱ{U5}p|rt^?ߌt| k6ߦHoƬ1|{m[V7cVE]Mu7k)VXzJq⛟>:\75o}i+]+]/>CW|kר\@=:]ceXǺ怿EY{i},K_hXu-WzVA=:>paL wzp\Ʌޓ`?ąӐ dJ\uS{NCr0..c4Pw~V8P!K\( q4BGC<_r.QlPIei˅2q/a..kh녳6rn Ԃ K\¹iȅ%[8ɨ,Q\8 ?w@pv`ۂz| 煸00 P|ùP]8\]3wgduB\`k~G0PW$ q<͸ѓR䳝njdre܏Hgd?"yX U{]xGؿg99GYҐ#ԯ?8~+(Es[;vJ. ][rCsC!Gq)qd 7y9]}|r:;K٭#p$S#r>'nK q$# 9Bv#{8GR]ؾ9]NW<c;p5]z!}u~pj*9ĥ=]#O&GV"\Vu4egs_kp77:#15R.˗:G HZV@:wo+h6hzW16]r0?~]FTXqE!椋9bN.椋9bN.1']IsŜt1']9.d YB%d YB%d YB KIOF,1'=YbNz2Ĝdd9sғ%'/k,1'=d9zǒ% YB%d Yi)KI7+CI%d YBV˔%taZœg262sX_9ȈsV?~zݳg+k)>m[F׭{_9;~ۢI>Vu[/_^`6 'uDI< 63OREW9Z>π*> |ώV_t8⣒V>+9N]ss̟CH<0v݂6v_{ݯ[ƒZ*0OdHzz]A=~Ho dyeY2wjԉY<#:9# ,E>W>dkGZ(j!_\-8L<>h)֪K>k+zc g.g6srYFFS0L}\xGxGxGxGxGxGL5 TLG3|#2g}L#:&p>SL%'_b>8bXgt@F/T>S">S&>SIJ SIg\}gyGxGxGxGxGxG91}J=N+W:큔>!N_O{7)r~`BEо:Q_U $')}|J>GvVWN" %3K/|m~zR>ϥZB %nMj)oI#}h4_b;{|oD9Ii)بL:~gKG_[[j)!zSan$_%kylQ8(bG!\rEE-W%7H9rUscz7ϥݾ}A`^4 K=7Orn'97^\$ˋMɖiRF2UBYJ^xSL=ex|^Fٿ4QM1J}< ( P+6ϼh[~4](0?Ws:ʎʜn2Mg$fko4'J={ѦNCh; qwհy[8 I誵a18Ul.r 6 9r#j4vߥ+1U_w}ozE~Կ+\$@~OgŽW݁qIPu1zHNcD~G~V=ꑺݧzDG꺸iI|~_߿]_VXRд.RœbECLM +1&Q#rg᤟׻>tE;DG;D;zoP|W5}Z'!>Oqۚ?ƾ;vd2Iaݬc8uOng؏?<(ms1c Nu]f揥hgoʍo97'q}Ӝ:#2M;Ʀ2UoɎ|d./HgK KDgNRghEx&/x-7$>?{% 4K*V}7>5)<^ ^2?{zwՊwIl} <XnvZAqUV}f#Rx~tÜѼ}_0e/>Ѵ_LqӴaP/C 0ܠDL'0[g$[ aLarϋ_p^ܤ_$ȋӸ'?v(#[Cn$N]j)mBxnPOC;4wj΍[5qCixFo;Degx ^>wt'O] TBZ+Ș"_QhJ1=٢5~nm ZgWcl7?g˱mw$d~v 52׼6Svpr;tYFn2rK7zȨ ;d q!G)=&k ߹J|d䖶ýQYww7Zot\|@$ȞgLKFGP;2C`` 7Z"Eq-吽XlKE[-w.d̅v "M|Ϫ=Kdgl/=ٸ½Q Yܳ틋o?dCx!`/߾vO!SvH|;6ΗyJO\k\-m_<nܛywYwZ o d^ٗa>Ap4Wb\ Kn~q3 cd9p5իd//sp{5ķGoO\|_C~ޏgD'w'd섬 M|"J&yJ;Oj.sK ')œ[{,2 Vpc16npqpodAVk⛫77.m|s⛁{BTȚ l3jU᫋o=d>z|qAC gq} _Cx%g>o'!k;L_H|;6ɞҒZwnid%x2rK VȲN!C _ _E\|Cpg *"UW{BF_ lepf͌&\ v|3⛊{ *` 7S#*|ŷ2Cz\xWH]ń[2%{ۙzm մ0G~ c@c%c}w,.ymB7'tW%~q2K6zȨ wIӱ>^A提##>q}{@l_}O9֗w%&vW%~q2KB(‰wIӱ>7:.K sdO3&%p#o( !k0 o ߢBr^g,p"-;2B\`n&gU%| _3^l\|OZȨZ`{ YM|Tŷ2A!<o_\|q類)d} liS߱uG)uW%~q2Kܸ72 +ݻX Sȼ/3.1p" /{},i⛯7?.ŐKm1|⛃{g@ ȚlskW᫏9| _3^#8]k k =Wo ߞl_'.OpN Y;=c}wl|%zt#\1~ (.ýNpBsRo]tOx o8d1x`78| 2 |p5U\ ًnnqS!c*dMps5ժŷ2m=\]ڸއ !zjLﳸ̯!kP᫈|v>\Epo_ Y} BLq {nof\|SqUqd]lSfj{DAz^gupD{$.pJX Y+!G4}A\|C旐%%}Aێ{߂ -`}z4w>@Q\yFDA@TPTLFFj*dME-Y7J6*FF;r pgr+{9wۓ S7>t0_`ѧX?O~z_lXYo|_7T|4U[5[Uf)M/Ah$@+t&4 |T"hnlE_τȅV.LU>I嫂ihFVsT[ Rh8̩׬kB:`k5| [ ZhՂ֬ק1t OG_:nX*RoƗ[ `K-Hh>yc XK&ҙP3+TBhAef|ț,he-fVs(TJhVA eT9|kZv| F*_ 4[݊2Zk5Rj5Ъ[-QGC&c5Ra,ҬGC_;ڡX*_UΗh%[)K_ aV)M"o44mD:j|y <*.D`d|yT,̀F2S+SQʡY JQ rXWqZV+SSQ&Xwy/B".2NSIf?QF?za2N*mFv֩/˧-O'a0iV/i( F83΄_/ʷh[Pla2l*fAfX*]gf9QF9؎2>;φ(V1l0*_W&h7&jd|5T {gul`5| v*=hBe]N廍q Zv>dzO nvbvq|0X?OlX?x,=lw3Ab}'+p~doMS)fCzb}6h5H;>P P6\ +ِ2*u|`{PbzxU[5[U0OoB.Ah$@+D OWލ2vV +7 VT9|U< (4ت`NwyKQ R9U|TVh^uqlf_3ykQ Z5U|}T>`XJa%0d|}Tnu|`Ic}1=<_ Vo%V-m^h䍅F,b-NX|f*_!4]2V3T\͂F 39|*_%4]2V sTRC-;JaUF_#nE`k5|[hՀ֨ףCJ`6mlvClU>i/K:/|0OoB"o44mu"d'OG@څ(lX/ʗȀVز`y|e 2*_94+]2*V+QJ4AJ`e|u :*_4[݂2ZQ.#Eh\E]թu*:|v?[/SI廃mhV:UoaM/lHXOoBF!o84¡D O/ʷh[Pla2l*fAfX*]gf9QF9؎2>;φ(V1l0*_W&h7&jd|5T {gul`5| v*=hBe]N廍q Zv6t?7NX?f0I?ya{,;_±{o8͕7Suܢtn1Ľa=<ʵgn޲5]yn>0I3\ Ғws vXS0^}dsCrG0|*x󞫍Oه {ܶ8oK@q揕h=s*! O(saX;n3ؠvLqG^G$HTswWrG^Uen &ҘqTG D?`%ǙpO(~S&bGLٍaB?"4q]/|C\ns",>B#Zr G(}d#KaC|iGkGݎ,VoG~cV?UZUoyVIc؎i; *l /c} o>Iڑ۰#:KPG, 'OVdLY͙."7p~-]yۀ:,i2X\u-u>(>\qo~(ɟcp⧻|@ߣ|ݚh.3[Sl-k7m]2V'z^})L;jzגѐ8e?YBʜVxkNW>aόW_Dx viwcis3. ROuߟ濹ֆ;Q0|r2+(Klvbm=l䯣(a?׶[3s_6lwx]£7]Sm a~q/s2 _$Fg?KK kF1(1V#R'n> vl6P-|^:`d{!Jd4a>_M>N*.H`E~&a\Z 皳)zd9|%tU YWc9&&!_"t|T+f7j+76ꛏt_nڪ&ǧd ;D;dv_nMKw2?K"v'ğ}j}y\뉍@T{;9Y$m]G|??$ᘨjo<Έ}%}Soz/'yT0r۟m74?җ* v]|ЮK 6 v `k>yJ&q|L}'ě:Vh%>|ֻ$jE dqir],/ُ3w'7w9mP|µ$BN'or~scg{Ltc-#o^=T_)͐鼣uRlPZ> ];p%gib;z8e 3c1PS[b^aF}psko'u|؇QWCr!sLCօ0XO.&kXS}jWw4cz?`ߑh9ά|V *mHqwe4pޑgsE4x7ŝ297$~]i'*)^ ºUfju0 aڄmwm# Z"soM` ׎]| 5m4\+ ru~,~{1.V{<)9 <Oע@{~-- >bcl/V<Hھc*cұצ=~O!vOGr.l' »6u!DǦww}V/!tĻY4yw?{ϲy,G, i˙?Gx} |l.fu!>!$lny!4GԊ~EKc![NVS[/G+ՊVF?׹*|D9 ߟoΏO?mc'r+Ll=JvK[wy0oʁv^b`o񟍣[OjWnqI/ؔus;qnen]94LhWVvŸ`|󧿍H?n]9%W2Rюg5^s4_?/ACCjynr׹orӼƿ] \,V*+8\ n|}j}}Ax\]b?>[/} ></%ta'w:샯16XI'+V'ұ/1_`|7 S+-X||>ӷ_ ]ٮ<`ާOo0~]}M|j>b2 rE?1s0N'96r{?jM+;I!N%$>dvǷ]n=ţnOwI;Ihwbq}suFϹ,,s9XG`l[߲z8rprr1μs\KcvnOb}:ï0b}:#gӋ 3r{3,. | >ÞVjz~!| Ѽd׃Q o!o/5@-ÿ%үehZi@/!߰|oێt% Ob4OӦ~Gg쟥'>uRboLEĵ ͳ'#s#j\k_dr f'q,C̾V??.u!~#",\es,ez|&>g,C|.H 򢔿}_z5|k%ct/_j5;+FL-_X X|(L,Np~6S =?跾:?Vp~9?^Iݙz, 4bqyc #GIwg4fiL Y5-ۚ5-~ekZZXfm >ƾx?`jS|f*6}vo )kH|z/hY'CߺS/O|c_d/蘒_15+ :E&Ǵ;}G|tdk~qv^_ʢ_q[냟Fq}DRm>[cnhQ-:5ٖU}4j|=./6P8 +]SUO*oz&c)Sm8ܩcӽJф~1TjJc? gGxNˍ:}k'6'{'{7Qv_?n'^skozNҼ+2Ÿt \㸒<N}a0C'F{GzG&rszIljYlczl>ؾ*9݁agW?yNٛit1w'F/f1ܑ~4I1m e ӷS{L1(G>qSb3vՠbg1?$k1N(g髟νq R$?pCt:8駜龘v+RCc:˘>ǩٱMMN6;i)b>lG>q4BLO!#)b鿉'N-4+4<œ{MtLqC xo׾x]kB5x.G{xϟ㽺QD߳ =t 1qDGsCL<'ܛrxCyf«c(ЎeValz~?RcwX#+Q }\_ܞqwqi^_qkh ӽ)8"CJ$Xf$y}}]w6nyέ'hz!ʻ{=j/F=<;a^"7k0P߳cÇڰKp>gv=iWώ߳h 5L5U|}-{{p}ϵ+}Oܙ́PyV|&p_re3>LX=woc-Gf{Lm3a>o|OoO66f76;9o{}|+-7lc$96᝗}7|˂mF~=</P/ ex7Z7J&Ġ֎:I;))[~ۈS~Cfߦ6~V=Ҽw٫+1p#׈^&ucudF Es2ijOAn>9Y3. [{i {6\wg~C^^9b}3so?62j88ӧ&|;`KԦ盜[qlC]Lѹ?(hbdo﷛2uOl j)AX5f+wؓ\cۋeJϘI|84?HqaJ5 5n4=Aw[Mf[6/=ȳ g0}#O)*'0=e}oMU|h_2UkZΧmiߜd.l(TckBwU^5m{2UٿeM˸{?BۧX~2e.Nu`^PSՕf,F K 30=|f?ʵ} n zHC>{.GK.ǀ[ [J'*``h;b*6%i8WGq)e 3-B[rSH ?8XF[k+!%2$dz0CK;J1$d=|/bHpJaHp:i .Y_ĐSJOgHp!%On+!% 3 \10ߙV*\ 0 %й .YV}  .Y/NeHpw .Yj Hp,o$dk .Yo+`Hpz %2$de][- .YO>%HpN2?O3$d]J\~>͐u gHpi[\^ `HpJ4CK֙I .Y/>TAг\M$Hp4/ \~!% .Y{$d}7O3$d]SFuH fHpz r)AK- .Yq|!%$d}t:CK[Gç\~}"AKA.!Hpz<SF$d  .Y?=!%# .Y>A .Yw 4CK \n.aHpzW1|!%kE .YĐai$d:!%mC .Y'$dƐAi .Y7CHzh/CK .Y Hpz-tCK{ç\'Hp61 .Yv\GuC\~;>͐`kAKW@0$dR6|!%,/NaHpL4CK* %2\~ zCKߦç\ t .YfHpz_|!%z` %N;/zN{ℑe wq;:{ w:A!oM N+t .X'窕2`$? suK\'pR\_lepu`? .X.P+oep@@o!B .X< 뻠gZ(C _B/ %pT2` S+gpq 볡!kgZ`} 3`]( .X p*\5>N` .Xw'O3`0 ;uiG`:y A sdp[ܓ\~ : 3`O3` 0 닠_gpz84C /`}\1> ?apzD4C ֻOA ַAu$4C {S+ \^ T`= qgO&pz=s A 2`mO3`(JbW\v\%pz9N .Xo& \^C c .X`!4C ֝\A B /|!FV` C )3 .Xo$p<\9>V`,/~!롳 .XCu n̅O3`P; 6 .XWfpz0T>44C \~> Ӡ73`mkO3`Z@"m .Xg~>s@q3A KoZL`.x^ksۤ@^Ekʊq1n\M NxyIy8a( lBks:48aw0r_`q͇: ZARv0Rt4q#@R}{Z7Sb2yl'7K fF&N lҾG ԏS{xׅ݅׿:ok4i G.d7D'#c#p|?c'6,p϶w߯{Sn x䟎=@|cq4϶Q9JJldjgY=99#E&~}Kx^PDsGSEYZ?pINh?/r[ߙ(單A9㧰Qŋ.~Ic߾}:}#u ~Luj+x_z컻<M"r#7NŏӵuڭQ"ry1"#΋ ^ǏsҵV'˽m/S۳h{,^%ߔmϚTrڞ}=V۞DFG3(oT鴇=GCc-:FGM淋Eж(yEfy5~Skve"wŦ2w9ʢ 7ozE{ЩEdڢ}f?-J从ڙ9u %Wv>+gk+Ykcr>w'[{Gc+FKCy-l&(h/ȳyH+7fmyhUxOIَrc|9 >\C66|=t|9\Û?h; #-,/}Ҿf2]^w{1o,|jd혾cy\F ~!>Ow3=_,}{x_i{G~3#1G[o&c.1R|q>~k^͆-=SkVQ/^9ܿ@\Hk?e,3v-W]k#MڵڵY0iJ ڵ C-?U;C3#c,-eAǻoY÷,wYvż|3uϜ ;ӭL\g|(ԟwm[6G{ݿ7Q(QV;ܪ;--fHz5wTm>oM3^CEqe]e:$96pfg}<{0w-//5%s;$MIq7dgmyպM|`ctݬ?3\odSdK}RL2YJ,?GQV%ʬjd_Uex*m8ZWYVUkO`nط}&j }}_þam>*3}wa۰m(6u\[j߬]޾l/pUwW2XeԢ,ʜUj 7{M=up.uB;9`A } ¾o/4o`!اLNm Q%_}[}\}%\?9Ծ)]{pJx6LþaoÔB)pgaY(c:e6O ^վӪwFM=8zFuzZu>*3} ?¾t,P:ԾA٦1զ:'RS UԀ}-8[}[}\}}m6oԮ=a-Y,{mmO2w6oƺ(e2O UվE5Ʀ^RcKP]T g۱eQejBd_fmxkmjap.5Pͬ ط͂}¾Ͱo3 mL[^վ,"{ ^}/¶ Q/ƺQbu \^j_q]Wօ:zUp.Bui]>*3}Xޅu](Å Qfq]}ۃopMNw[Uط m}`߫m}]{͂};`Nط};`kp]c(c9ʺ er7}WׇouM8P>`ξQXb5 eoW}%W6ͦNfK-VL ط˂};avطm};a.ڧu] }>}`]}Tf8n* e݀2ۧWվwKM8zKCzcC>*3}X;eEYQfuC}AUx7cS=v ԩBӂ}]o>m&j }`>l`ξ;|;mG(y'Ծޮ o_צ'R;ހ}Tf8|5֭F(ew ȾihS6'Rg6`> :a_'웪O1m^| dtߌv(1Zbw:is[}ta5a`\mXy;0^b^0[܏όl]znr g8n%ur/Iz5RՇ (qq ac4s-0&ߝ( v+ҋSv~F?.6e44cVw~;G NR(v]p]Og ,׬Ykխ+/RU4uzTx/Z@VѾL$WT^ds}fn[T}~K 07^ߔ~Wl|_b^/ٺmy\%&WIA<ʣwz"7.na\\q'r:ڸx;W0|h2|ԣ#o_2ڡXT"f!ESIg`?3Xyoy9ʍM5lx&M]۝vghw~W?rTwi.M7Q7$۝^;8y"#9G(76uIFȞ^Z"Od{VDFk[i<__+H>DZi;DƪiMى|k4>SN{ңҎ|'5vV5Fkr2N?yQ_Ҏ|VbYX?^Xu]DnϏWRbs}J9gxVGMV<^$~B'C$/3gE_VO%r+F[1)"sCl}[J_,b}׵1U$VWɮ(0p?yH=G(Ï<~RL?E)WИ<~VbYX&tQ4g|SLOtGD>Erw"(fx;/xM9(^_J6ˇ st祋Ŀ;{}c,:.tJ=G> }~7yJt1Xwg1g5ʾmx]R~c`ۦjm"ɹG(?m?vmTc{fw;q8#Fd]dFU7 w}Qes]dsM)=3Mn2cT7fzW71Ku1w7 MncT7f9zW7QՍַ3[;s{Fy7u^ߔ&_71hSO{/^4y|]bTfz'cPϡjuiƘ4'u?FucìwuSh._]~}诛ՍYnޝC1L!^<4ES䯋ՅY=wkwct_];+TgI]c1-W<9" ׋SCʵYί޵#cЎ 1oGZvyyЎ #cԎ]] A] 3] L.bh,'W{Mw"ϟ}/fRF}?Xn?+Ҷrd;3BG,z^Š(6o;&QR{Qo/b^Êշ6~UU>6\򀌪I/D^`VRY9C}ώQ6OG6/UOB|}&*S32B}&yfybm3z~%|lxоm&<Ҕ7if WfM]cMG軱W_fhzzmD)lfotaiއ;Uij}kD/pH2l#S߆2ijOIQ:*^{F^aå~{t/~φnO~KS?9ksozOuo9}jb`Gd.nY6ԅ1ݠyBqwSMU߷ɻTm)xn7y>Ǟ4tj^,Sz")>+ٲXq"%@9Ndl'S(5dkZnw~q{/noeTEJGR|+iߜ۞8؆blؚPU(uoOېAoiY2=2b+.*ɔ8ՁyU@MWW۔nb԰$0Smx佴8 ?Þؤ?ӴR1fXLV"˯_/ϸuMwo!7X!'Dž-łz>H#uoin+=!Koa~k\.kAK֫3$dtCKÁ?'Hpr,_<ߜFI .Yo9tC$d}#Hpzt#CKև涕!%s\z2CK_n+w뀿"Hpv\k\9 %CcHpm!% \^ ːˍmgHpɺxKTi+]u:ςfAKֿɐ \~z*CK_ֵ4Z.cHp4CK .Y=!%w .Y/N!Hpj|_ fHpz %O3$d lD"C .Y?=!%kpDO %\?>͐p0>͐  .Y ]uO3$d] ; %vwç\ VD*A .YofHpɺxn(AKˡ3\6>͐ xb0AK֋m .YofHp͐,`BW1$d?|!%Z|oÐn|!%y .Y_=!%s .Y$d}tCK/eç\l"Hp"ɄO3$d8 \^} %Ǡg0$dm:|!%@J:j\v9\t WtM NYh+ Nx<ӱ@0a|;  ; ℺Nǃ; _MBMt*v0fWt:&'M8 :;7L*JS+g"Z@JuiZ!wA ?_8\;0' {,r#C &paC?urZy!C O\> .Xg .X?|/~!!V_ pV $pf\,T+'Ƀ\ .X{2`5!.XPO-C 0|\>?\v?`pYh8A ֗@7C օ>@~!Q# .X@ gpz(4C K\ .Xןfpz04A 렓`=I= ǠK \^v` U1`=>.~A \nO3` `}/ .X§\>,l$phu:A M0`2>&`Lσ~!뜓 .XoF"p2\:>9.X@fpz\4C \nu)iN%pn .X{OO3`h>  \> z3C ֶ&4C O.X/u .X?7`yΤ6Mjm U6`'^떉7[w0&6Com>k|8!F|Ay48!x`l#EMc[,`'}T{[Z.[%[Os1vw"wks&[{.F!x;|GGV$WWTՕt{EC3);t7_G|g6/scϨ啄wJ(+plc{_+)?O9kK}T~w/Sh}Oӽ;}'8NʍHa:n ڂd f?WnX͕6^KmuaO\'ͼp)h)Zڗ(3gZ̞T}_鹼 uj>I1hxς>A"py#'>fXp?ϐc#pOm^Z"p粭9_F]zl.kPwŽ7-..(Xа`Լ4׊Ñ]ȠoO.FFx\$wm(QN|)Na+mY>._@|7yc?{hs?=Ӹs،#ϲB{7k߃|=[DhDGGk;ROf{&Y_g=,(XhAK)#?>ڞ5Zۓ=z=<ӑ癎$fPͩZim{_13֡Yxau]3$#P.,(vay #r|uz?͠M2޹\ߜe}`_YNis!mm˼a{Swf9ԏ6{A OTv i#Z?psfhjĒjBYN=mr>G{Үm럓:4v˺3EX##EGG]%̵Pgvw3;=VrGr07UGG>rc|9;>C66|=t|9\Û?h; #-,/}Ҿf25]^w{1o,7}jd혾cy\F ~!>|Ow3=w,}{xwi{G~3#߽1|G[o&c.1Ӵ{0@yf׷|((Ocwkٰgj9+v'ErܮEsg5 {\.mhϻ;<e;*}G[}GqQq~L >~4>wT_־j3Qik(Ku=2^g$]}N?쬠o[]rѕ>dbwnG[)) <ZɗvcLugƂbl]pO*TۀI2 ÔQc(c<ʪD@M}{쫪 o_]MT'R* ժʀ}{- vþݰضľ]c/`װk51Ge.,ֽ e܆Bk+CUվw_Mep.B}Tf8*3}kokkD'<}N o߆)6q8{mR>8%`ξS,; eBY)٫wZuxΨgW'RϨ.TOGeOaAwʴWڷ9>9TT;\cjjo}o뱏뱯ö&-վ',ط= }¾- }Tf8Xe4Q⩡jڷ&}KjpjQsby;ֵ ;rLWM}ۂˬ o_~M-NYYطm}a߳m}k^}¾Wa߫E>*3}`Xw1X.AkC+jҺ]^gSN^^W. Ge˻ ePV!, o{}v Bu;`v mo{m7o}Yo v¾ol{`ξre,GYWUPw7'RWW27 cbQF̱ dZxʦԉpe ՒivYo'þo'leb_k`G#k g X~]2VPfPwcCxniw4'Roi(TolGeo"uǢ(k"ʬn3Ⱦ Oxzlj8:SVxuZ#ط }`Gľ{=]؂}}o>m2woǺ(e݁27վ;u^;\jP g_=ƺ(eգP71}3mF;\BuZc:a_'}`}Si>KU5Αq#Amgv;Ry49ɭN>Kհ0[WUij6,Ye</zz-fgD}}ي=fc.}?VaC̀n9Fy64u=w= u0WDd TP  # AC""/e#p{Q@=/e#p{Q (DUx] pT>{$1.TU)J!I%H}`'6U j bCKx2}X3hS|:hLq Zn잽fuu=7wsϞc@(b,Kel<|V4Ki]]3VR1=ui1RePR$3ZLcp]I/yw{-toưX(q=׵1ݨk2o,LƯGC }q(8>/0v4929okg@Ofli,FK›5@wxRǢi\6R ~Lq:t2S? -q/+U>.rq)bWWr,G}9ocu}4y.eicB;cefo)gww1b],3]Ivk&>>ǟony:4S$n"pnxGA#!ª7}z:ᖋz>1S-5O>Ą,|Ye>],CE]?=Vjv}->Y W8+Xngϖv~R9Og 28,3`y9~<ҘFWEv5'vS+#m6Cmncf1=Gϧr1غu.Slǚ?¹E{)eI5ŵ8/ˌќNآ;"C<[E3k'_'>¯; *E3 sk;Մ~¿a _O8=/N%ὗ A[̧))g|z6Np>SR)įZ(+rwB^zoqsWx6ZbܨY(ϰd@t;lZ;s(lcZ6|M {;Y? maӨ֫Xxl6neˍ*r)[>k5`wzaK Mkk(/5T4|y+ڈef> bnm%1|GݖIQ?eS?3Y{xO{q)7C!‹q)?Us~iNOx0.9?Ɖ4KyMx*.O:?ƶ4Ky6Z2,qHA;jzE"|>_=N{{}K/T8&iO㐶ߵ7o=+5`],'➂wDzwfO=fXXVsiYΑ}iƨP_%Zآ;"8G"]8Ζs;?;|xKd)w^#~?weX(lV:(oԒy/=[ƨ`TZ=O)\+Z(qp,;wkvmN_׎;en-wl&CrP{G/A_Δ%}hQKye̻y堔w' k/wZ2UM/d_T=/Op}nmԒy7>zl"٭%󮿸z!9(}_@aݺ?CpGbn.5VjͅvU{qm;5Ų;=ĞiOf^sMo#?T#{;|ĂKoAo/wMew>?C=oz Įܸ iQoS麜Γ%DߜhGp}Y,3sb&s 8Xy230u]$C3|[crr7=Q\P,696b̜qAt&Qonl(qyU={xzjO,Yeh{)a'O(xx5M)}PKg,ΣZVq^?<|' `Qh KzI9EL Žv1#„f--PF<ݞ&~qBW 1_XvVj' +<>\9£: B[U$sŕE"v .jb%y.| .9 g-S(wm \HDh{\~-QP,5JUիQUEȈY[O9䙕aϻ&H@e߅^sp<=ڟ6xsB 9H12bp7M?9sQ x5#Dٞ.AcZPԉmX⨀:bEF 435k(0?ݞ7އvnl4ʶ&6tkmh*#a-{'M?ig}},;?kŏ ?kſ;b˿f]8y?},v?ߚv# 5{9oRQ\ğ7)(fo.4~g@7&hҼXzހđ+@= 4`m4{S~6wY)@`5{vӍ`14/k<[Tb쵋#ǗIqf4{Lq>v|k_L|k'­ ԫ k<Ϣ8&2] %WEP@Xm3XR[!9EC }p.<3KS/ׂHyVr>tmWT򇨄_a&Z:܉{Q2ʡT9w~FAMdz]޻dn ڜ{c&g$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59alg$$Ifl!vh5/ 5#v/ #v:V l t65/ 59al$$If]!vh5 5#v #v:V l%65 59/ a]p $$If]!vh5 5#v #v:V l%65 59/ a]p $$If]!vh5 5#v #v:V l%65 59/ a]p $$If]!vh5 5#v #v:V l%65 59/ a]p $$If]!vh5 5#v #v:V l%65 59/ a]p $$If]!vh5 5#v #v:V l%65 59/ a]p $$If]!vh5 5#v #v:V l%65 59/ a]p $$If]!vh5 5#v #v:V l%65 59/ a]p x$$If]!vh5> 5x#v> #vx:V l5> 5x/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p x$$If]!vh5> 5x#v> #vx:V l5> 5x/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p $$If]!vh5> 5x#v> #vx:V l,5> 5x9/ a]p $$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If]!vh5> 55#v> #v#v:V l45> 559/ a]f4p$$If!vh5\5]#v\#v]:V l4] t065 / pT$$If!vh5\5]#v\#v]:V l t065 / pT$$If!vh5\5]#v\#v]:V l4 t06+,5 / / / / pT$$If!vh5\5]#v\#v]:V l4 t06+5 / / / / pT$$If!vh5\5]#v\#v]:V l4 t06+5 / pT$$If!vh5\5]#v\#v]:V l4 t06+,5 / p T$$If!vh5\5]#v\#v]:V l4 t06+,5 / p T$$If!vh5\5]#v\#v]:V l t065 / pT$$If!vh5\5]#v\#v]:V l t065 / pT$$If!vh5\5]#v\#v]:V l t065 / pT$$If!vh5 55K#v #v#vK:V l4406,59f4p T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,59f4p T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,59f4p T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,59f4p T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,59f4p T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,59f4p T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5 55K#v #v#vK:V l406+,,5f4T$$If!vh5?5?#v?:V l44 t065?f4$$If!vh5?5?#v?:V l4 t065?f4$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gF$$If!vh5?5?#v?:V l4 t065?f4gFDyK yK `http://csrc.nist.gov/publications/PubsFIPS.html$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4g޲FTDyK yK Bhttp://www.ica.org/en/node/30230$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4TDyK yK Hhttp://www.icacds.org.uk/icacds.htm$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4TDyK yK Hhttp://www.ietf.org/rfc/rfc2821.txt$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4TDyK yK Hhttp://www.ietf.org/rfc/rfc2822.txt$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4TDyK yK vhttp://www.itu.int/ITU-T/studygroups/com17/oid/X.667-E.pdf$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4TDyK yK vhttp://partners.adobe.com/public/developer/tiff/index.html$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4TDyK yK ^http://www.itu.int/rec/T-REC-X.509-200003-I/en$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4TDyK yK 6http://www.w3.org/TR/xkms/$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4TDyK yK <http://www.w3.org/TR/REC-xml/$$IfB!vh5]5#v]#v:V l4 t0_%5]5aBf4T$$If!vh5C5A#vC#vA:V l4 t065C5Aaf4T$$If!vh5C5A#vC#vA:V l4 t065C5Aaf4TDyK yK bhttp://www.wfmc.org/standards/referencemodel.htm$$If!vh5C5A#vC#vA:V l4 t065C5Aaf4TDyK yK `http://europa.eu/scadplus/leg/en/lvb/124118.htm$$If!vh5C5A#vC#vA:V l4 t065C5Aaf4TDyK yK Phttp://dlmforum.typepad.com/gdlines.pdf$$If!vh5C5A#vC#vA:V l4 t065C5Aaf4T$$Ifl!vh5&#v&:V l4 t065O%alf4TDyK yK .http://www.w3.org/WAI/$$Ifl!vh5&#v&:V l4 t065O%alf4TDyK yK Nhttp://www.rnib.org.uk/webaccesscentre$$Ifl!vh5&#v&:V l4 t065O%alf4TDyK yK Xhttp://www.rnib.org.uk/softwareaccesscentre$$Ifl!vh5&#v&:V l4 t065O%alf4TDyK yK Nhttp://www-03.ibm.com/able/guidelines/$$Ifl!vh5&#v&:V l4 t065O%alf4T$$Ifl!vh5&#v&:V l4 t065O%alf4T$$Ifl!vh5&#v&:V l4 t065O%alf4T$$Ifl!vh5&#v&:V l4 t065O%alf4TDyK yK http://www.verva.se/english/international-network/the-accent-project/$$Ifl!vh5&#v&:V l4 t065O%alf4TUDyK yK http://www.equalityhumanrights.com/en/publicationsandresources/Disability/Pages/Websiteaccessibilityguidance.aspx$$Ifl!vh5&#v&:V l4 t065O%alf4TDyK yK Xhttp://www.rnib.org.uk/softwareaccesscentre$$Ifl!vh5&#v&:V l4 t065O%alf4TDyK yK 6http://www.interpares.org/DyK yK 8http://www.nla.gov.au/padi/~$$If!vh5%#v%:V l t0%65%aTDyK yK http://www.nationalarchives.gov.uk/documents/functional_requirements.pdf~$$If!vh5%#v%:V l t0%65%aT]Dd ##:b  C  AS"`"!?k6,@={!?k6t49wXXIx}XSI+"*EEzƆ PT vP^@]{]T`Ůk?{<;w̙SgnBG!HraYUMY k+=RŲB,V:,F,mƈZaѲU޳1aǢhSݵPţe u ^ֶ [ڶaWҫ"e>PzT W/gY۷=؝HHcy9Mt0eIzON|2Ү;}ԩOC t|S5wn5m]?epJ5NЛ :a~%s*zϳ&@giu^ ZBYX a n\MPQX,Tȑt~#\ّ VF#t6FƐzMAO#$w3ʼn )2g} JYϟ[RLY̊dUMj"Y_ڵy}.Ķ_cUٻzn NX-i'n BU5}ZEŪK..] eH.surVOֽ͖oZSN+qQXWqkuVֺ@Z :|B& ܅#rDaK;Tcj~ٽ25jxeW}o{|8ur/45Kq0L$@ԫDIT>Yx]7;4~Uc$bǧzxɖب>xanXrðGQ{{|T,~JDp=ҧ8 r(u"5]/}?=$T/_r8m_kւm]}8ZrOs `~Y%; 3~%~Q?{[_=,wKX+w<$.!o"Bx.,$d|Y=Iغo10goF86)}RgX&cgr̙8g5"|]6lԃٕţ=_|O˿^Wk[6EUӞ)^p0ϭǥ]]>˻<7Ҟե۳۽;fT/x\o0|py ɱxLZYK#ĵ-P^jC7KnMn4ֽ˳k),[{tg}{䍫@X,Wm(b语a+`-+$ 3`6fya՚yRh%+WPOɅ*f.d9Ŋ~]zH5Ͽ)zoR޻0IhNQRsa ٰs-$s38zC70&gh9dg?KYJSEô՟5 %v8k0k@YsͧvBݿκWTYz~WQbvaa[g\>uEճƬ>biNsaMTe~[{٠,aM4xRϝ7Wb:.;Wa u]7ai!{VXarMhi[" }`D8r?BKiuY+KF_Nrjjj^|B?et=5j׿$3? 3@{o^tXZ%duzF ݕ˪q5/'tTuiMHܕR8t>:peDE'\<fvH3x8ìx "fEfk)DJqf!y=e3f_- 7,`v@4(h#Q+`Ϣ>fuŌYq 5{&3#Ռs2G~MíOxHKiu_B utQNZ[mormi2֕cmUJ[VJ2x E}7O 9CUḇ3Do%>gI}kΒ9!@&&GϑF8G*ISΜ%S;G9GW 9r)I-8R+I銋P}p8?Z{Ώ?C, i@m}vi6&$\|$y)p)T [gȺ zs6gI2 CqJ$SgDg+bO%%)qYr+\ 5g,R3dU.&o”4~KIk tvFkjzؕ~:ʩ~+vq6&|L;r.9bC8ќ#TZqgX.pR($ O91@dZ8vNh-qiC!GO\PI;sfs8\ڷx4FDZGQЛwX;sĄc.4wƇϢf٢ޜoOLs었օy|OqON@Nx(gx'B6\ZKyW(Y-Ey׉^I朚q8~lQ5ڭ6GӰjW1~HV  z0[=KC/Tؒv TAPpLTH7SҦ\!c.R=WF"}r}P`ɵJ\zWNVZ=kzQs/O<Uu ŭ\fg"ӏ۟I6cRefqrr!˹cŏ56RG/վתS=Lm/WU2Zw%7ȪjX$`$&Ijqvu's犙_}]An2;avp1me>=~gKμLʌma&3?sj~\xknL o+ӎi[2.w:3?čeR{BiͼӹdyL{^ӓ E2)d1y>L!+'dv\<sg5`^nw~-4*`^!؟Bk^،YܘW{k | Q m_ScVU 5p{@&jyL}FJmU#wnj=$kƫA?$Q[kw6!9~L1)6c?zoaJêM%EpswDB 1,0Ogt| s\ȔbF˩ d#*o<{Fasb靇랓y`ٿ Zݬ4^V:_xe$iXA/Ʌ8ԗ^Ӌ^+>,B^j^%!%j$mP% * B ѶWX5nI>Ԙ񂴥>bdv5>'59)?F8z_9rI+j-xF6]VA3"xpg"}qFGn'"SWhh8h[o99嫁ts^L{9iW^h c(?^4p|AF.`9V/8yA:]{эɨ 8YL~Fl@+6i~&犉mrŹ`hy) ll3u#IJ^,xA,a8ۭ:xg,G:8JWupvwtX (tЯQ D-V)O4IU?Uo'L;o+VKj)XY<o[qVvtDD ""0Ĵ! a-'J2`rr}<[NJgg &@BL9YE^ <SDBNþuIOǰdRb:,'NqC!c$>e Gt &H+t̾JͲ%lKGܬĠa.ONǖKIIe/#kGӺet,, ttY@MN(ӑL Itґs4Ǎ~ < YNz2o9:$5_NMӅ _3~T^Ծg=O\!mc:La1 #$U@cv#I;aDGNP=w-A+AعA;sسrʠ1EARvmrZƇbٵAiAJ K;ֲqf :þt$>ۆ:=zJ1m_X-'Q.'%2prroz&3ujSd"{Q&V 6ed u,&oiV&zc%ZOԕļ37$9 N$>r\\I'U$q#`%R$G+&9^v\I,wɱJxPa9' fjY[7ȵrȠr8t."rnRDV$zVrUH>̈́E!τRz># Ȗ}9 ~2?̗~uR2L&2Kj&L_B?D%@_7nKSk9=]Lb9O/&rm1SX.%$IZBĎYb ꔅуY6 1 z.#Gf2kl, Q?, c\Ht,Я~!Y* m,lpd2ҶY5ZF?pRR,%4:Kɓd9YBgdVKa;nKK+vyˡltxH2+𥳐v|z2PF rkk!?/GD]V^5)"1Y؝^Dd!3/N]AM|7|_Izc[Jr]ώDB`Ɯbq]+dT6uWt)yq݆r/+&2*$jf& ı.+ o&.^A31 2! +L&FP֓@R{|%8NwصbrMN L~3%3y*dRt5'MI7"5 $!&bӤ'J:$8DI?5 !&]ICΤ'yɶ&7MH)=/[OIm l5dG cُRaWv6ēNADağ@:l% g/!CkF;I1{;@N ba׾ عd{ أI2{fH[Q#Ql#2ݔb7"zD6$ Vd5ۇg%){ad},ba28d_)Db2LH UX 2ęBCZ.LdrHbUdd ]BRew&c@lJ4HuѹJN<[C9p l׹,psl9"{ChεhGCՁƵ\f'q˝F>Pyx` LW:/TffS?ʌZa~t*␩¦KǦ0 #Mg`A/8m30t/]lo8맣gߗ}41i~(4y)s *rpj$w/tvj#\8'SF|鯺qO&œMXF:XxX9&Pks'w^&t{OZg­n&J{x[&ҧz2ԖzzB}=@dɀF?d?f`JMf?O_t3TuJ6qGN'g­NiNSf*SyYi0©6ݜ%Bq-tq' r Maӏt|2tA yJNŒH7}ʂ,7i5' nw8x[ܰ0 al.ͣ7zGfZ7h:gb Yp[{ㆋ`aqDpMrOpdz"9,#gGܱc/qN#G}yrOur<{xwsmB}zy8 /`¶6/ +BъY ͳQvݝn'"zb]< <=0tF|W?Mҵ1af;R# s'q R}6NNHrj4'v2|ϤЩw:N:%[TdD7D'ߩ $ )PxH}QGlt #̓,Dxd:#َ7l''ı ;O輎:V׫Cde YxrEV:%ŎK)G9Bv9ƑQ1\rI*'Љ!FN])xR*q&H)$)pZFr1 WlD:b)8D8m#:;n j~|.ژ>1e\컹A?sw0cA{4_7 r+J0UdcMCk>t@ӠpGi81OG>8)ߜ\~7M/G'Ct}rnlj>jGBB.٬\ܚʇpI.VS?l\Zf BE-ųu1wsp 䟴E\춴Ɗ\ĹJ|J[㑮>0@|?+pDlU_j % ɱG$=1}.2az.!ڜGlb]RjŌo*~gg)Κc%!avfů p=,{`f :t2ǡe*dKqm a'U7Ǭ*|r0F72=5._ayJcxX䦆e'l}ܜ~jDžOvp2%ګq|$ƭR\,WáO>iE'*j;xzUv\4*Ua 䢈A\/Qa8.dUCUÃ76N;^gRU<7TaQ(qE%6h#[DMQ"$)J̃@%vPKxH]xHS5JH6q$PI\<)ҖG<DDZ)ԓJkJD?5CC%5F]ᨽ ~w̰ XvTT %qtpJD样RE\웬D0.+;DZqUr%sKa9L 9.f 1G1A?z7sQН)/pe> ] ]3ޮ.qubvM? / q EqB/x%/ gGŇ{ŗ)~-U\XЮLlbwb#:fv]A+T2[ݘՂ0P0Y&Ha )aV 1k+ _;(07)nn=`WD?a7 Ke%1Ivv]Qva?*S4'7}w}r5v LZ/䖦@m6)~B 9/[ +̚cNbFFk3xf_tJ?է|@} ty*< 1ݙ\[3BR?h9mɈтӧu_ri)S` Ra/Fઆ#` vW#a vRc@cko1ƬUi " vcY<6f_˝~ߍ%mи>ebm2+yF~ v+36s__rl"m;P?EkZ~wƱUj6B?l` Y KOK>J#ѓNfR_%Gj(R=O͐xY}!XkTJ_ L|3X1A&}HԠacנ,c5l n{@0G]AX,>=}UhpJKO7JߘP!Dh!"5BE!:k`=0bt54p>f.Xێc5shp5us q>x>XXj8mj<5nG9jvA&QǪѱ6cF_sU}t&1׶_ykcb))e~)gvc~)1 yk$yfS~6%- Xe[~I+ڿ3?@x% ~[I';J%2~m|Lϕ[ףOشޖ_~MsIK~ o*9JJԓ<@ܴLia^.'cʯg%;?ޯ^wߖ @]֔jBױ_N ]s`T{ޟgBL w ]6 i7 uÑr!(v w \ kܱj( @3)㴯}Jܡ$Eaw8eJkKJqg;F)78RuM)軣kQ)F헹~㧹!enPJ!1r/.CaCyhG${9Wlu W EpW"0 K#W<ۣ m=,Jr]{ jy{DeHi<)}㜞 GBw=i32ieӉ_' '"1 N\Qa+FP׹v X 0m /:@lݦ+*d( e b 7c\Q|HI>LtrER,wuE7}]e(FuE~OR]x(\ \1]ףy>]vpl!n`4]%tsR^vS#Bڹ Kz #etÃ2 iN2w!:*Gz}eXP/;Ȑ끭Iqi fR$u@ӡx(@Pv@F]f8w'Ǯ|i6dD̆ !0wvǪ!P=rï!H(pt4Gu AnѓXsX/9ud竲8 Y87YhD& "7S&[&[E#\9ø2Yk2nM3eKed7ɆȒO !)M1>HJV?,׸CqqܸTi~\TU:?M2R5xܳq7CYC-KCυ:%FhAcw⭤}J-ZSH6J-{"x댴|r:iY|L|p|xH.҈x?Hj\K˯|7I މ!}!mLRZo*Swm(*?Ȋɦ 7 [ k WǸa7n8s~yXzsm~_7w}I}4[a¸ eIöJg 'K&OM8D2̉:i٧:'qowHƝx.;acwnpOy$Q& NBKw.B?c<y" ,O@O%<᫉DW/i^4Db7ƫ"Q<c#x77Mf7, o|5QQl]742O폧m>?~|p|4D D)C5k_ǂ<"P<[䅑#u ßG`!?l}qbXyy?x@z$v\ºӑ慙'ZSQn']a,&'_DB "H/wHrNj8t$(rGe^ݏrO[Mg''XaUG=Mx''$.L,{&NZ(K M*Kz-;dv5 4!NҚaGoH+R‡%wNK:0\K)/1quxYwbÏ%oO0ߜp=lCڰ a'z}-nwֶ{&M0DNebpabRĹeIJ OKzt2,?0,/)5L$ 6:Y1&YòYeuH 3IL ~EQ"Cl_\l2pNrg͇xm/G3cg lU1.`TO x]Nx&7(\gs.% ߐ8|NA[W' ' |!<"Id~#sT QL! 䅮" RR^f#!˺ b׵wԵ+UWן=s;Ny3'{,lLSL0*3 Xf P3:)iƓ;k?7>vMǘ{9_;k FOؿ&zk ۃͰ8)l{OM]!p55  :=!?sC>܄0XI/95V?[!BU&>0uM۲O(v氓V$ f$dM*)IUGyc߶jD ٟ;OOub?1IZd02͓AexSD/G/| bCL'@*NWPЮ8`5*%Ϧ.WF]Rj:*n\gبYtc+۝@c-$JW]N S;g :]RC:KQN0.| r n:哋.d*F.\:Cv7 Zbt~h!Z C#ƋP]abth8tJ[P8rR ?m_r;l(ƻ3ܛ} .A%NpN? XL;e5 #ΐy9Z ѡ+PzmygRDD]ʕ(b\ )tU(˽*$5tDVu[W7]6i%MZ 4Z^ݘ l9JIVߍU2_)a{}wqz{ͪ_ݫ>N}VW=W;K;\gXgs.3?ǔ[v.mRc2KSozMI]5-T׎TGmؓQF+,cox#s{Ϣri<{K<*5Aj^^Hk:M)-;/-߻8mδ޷x[~nY;[=Ug^^ު "l|Q7|$:_s]\ȒAtd{ź&APb?[3"~.Z|p2t [NtK p9l|;ߐ<& ߣ:=gߧ) PGLdS¼hg `\L٢'>?!:WcuaPv5O# #0^ZZ1*Ö(hJlΨOɰ f4$, V2xцBm#2 p bkxG ~0W1|E^ޡ%g~~/o9x gMݠ,4vT7Y(%úB Z5*LI1n04uLQ-MRw.gAaYBCR/"aR4Qwh< =f9=^h%*'=>^JgA=!)vg!j̮E㊒1oJ8d皳k9O9('K<.$Ngo$g#f?"bk쳭y67xۘM0_Npl8:#0gzQ^D'bq.͸8oL<3";X.c" {(;ؚClv dv~hW\(GzR4+`_*ڞVcj*M顟TR[1_Ճ"\/B[.bԴ[:ܟX yhbql5Iaβnt@'fGBSkhE=L+F]Ա)aMwfbt=(Bn JX.u ;S&OӁwyA"nEt(F_AEZ)eFؽVCHz@ӑn #3zvǟihVtΟa9 MaÅׅH찤h#"L =zV Y@JxKM]߹Nwقy9sNkNɚcԀs]SSN\;{.i+D&rd9IE0׆ 3Eqw nId2rGrsgrm\koʉDG\s}Meæ5܍YpnS/՚\&Ҕm79C/s_X-A??|5n0Yq+LuMO8ܫXweƹ1ϱya\6i9L9\Sǿ9X ?}Y 7Dί3;k ikSPQFv`4OEs qp(7B]мD#Xߝyܖ)AMBP`> %އS}|lam īɇ!Ϗ;gaJ΢^myAܘ\߯,*oq;"(V?Fmx h~Z }&Q"(U& r (KtgD%BT>-K_z{2vhu*ƇDekQ8 ԴK8W?GIp8U9gHp3 u{~ - _1o~uƇ>t_ѐ|X!C"_CGH;Ν{ %0Lŏ '7'&mÛԧ0%riЌ5gp9*þф>/P>]<_9x 5?Zdh1!ؼ|4A;\Z\ OX4X6u~onhw-X(-t7=*kB!" A!e WH@Dѯ*0^KFBDP{eTO;A~q&3;fF!6: `Ǣ @~E˻Mֈ`Y终hnﻨ ZZ]8.RnEsX"ȠC.C=JG a{(ntDCBF(!rT]wpVzm_'﷑fNڷlnZf W^Bջ @ک6 ` ԱOU!u=j*g&avKסj,F*<|,]k/PT)*^'AUP X%G/(A}*A8mLuj}4cThR5`s 7f\pfuXF-zimKq'Un?Lm~ѾިjoNԿj~oe,mq$N6KwT/ NPOäUGԡj`-FLe|^EU<_*8_ئ>~W[lX#XKlp #[umN .GbEA9'J^"}cKL %B`:QpM$}.6yb`W\"X7kPTöA5N6h۶}l1P2R~g"]!ZA#%͏js( 8nCH(ލH=hR1.8$0s9t'azYAҗP` hFG^P[rGH4a,} ׺Fa )d@mqɹ-'%<֪_rDkF̔&ZJ9ךmdAݖ%q2VhT XS9RaVb`ePb6 &pV,M@@`YC[e*kxN'[F}yMB+ BM&7c޿) @0;󛂤nOj dXSt75ܥM! WS`FMaXppe ϯ_0ؒo ֆ$k]P*@awFx^>k[CM /,!LXC.ॶ_21~vP_Vf 53Jak(p}ڜ3]o 3Hkx4!lsv t5M`6 MD5 BŰv&~j>-_m{*=0# "}o0C#.QNJԩBxO%q^$KLW9Q%LV#۫""TᑏA'~JڑrFWUXA9A,VfEJKæO(n/~+W׾Ԋ)%ʭ3sʛb꾸8QT\l)Bٓ `(:$m3([D(/ hԨj.1[>Z #+ڙyMu/OݒŪב^OU>yC9~~v^XP*yм mfbԶp=@-V;tXh /,p~{g[;8/b&CBۃ/>!Rs,CLmr{X|Wk7[aHk!^iS`=B=L*> =-l~w [LJV2[0nr-tCwXC=wakCn't QWߤbQsT>RT/j75Bu#-R9I|UBaUJ.P˥NRB# TGHRJMHcͥqTAuPHu &.nBuTW* 2S^DNU+Փ2>ƚ|S3R2Qs4jn45> MWjf UCiP4>:ng)4!ҿ^@)e{u J)5$/BEEk"(ƞѼ m5ɷMI򈺜ܨF.R? KuB-5U-CYjH Y/NHՓ")C=OL5OzRU,],".MVX!EwTkG5jʦڨHI%S٪Jr,Au[`pb tW1\^" e= Pl\X #vF6vG@}޶F,|`IՉEMtMPKjfu~':~-Y}2S,pEBB#\ov}n$>pHZ"#! p<"aN?s+l\+\K Bu"Q+ȆE8WH }Xܿe/wo]aEs*W+Ns.C W^;`+ S~ػYNz@bI.PD3jq]4&X)Yc,OY f zLh΂"a3m`P# x[J\r}/Gc.Fr)b8 b`, v@ء/q}b3gĐ{f:@wke5bX;6bߓ11/Q&Egr\t`rvSDN>"^urZfYgJmHXmxLUL֏y9Js?T$'\#ٯǘ?Qklb5bkb̍LchG\ީ9}@1fqaM 8=4z7>ިEDMu/ۃǰuhC͏xjDkDKS7k+'jDފ^}T[w=OkԡvVnlFbnm}uzbJVa[ ( wjNG5!%d xF洀$1$\ H sIsHh\$ck) Gf$H`lw 9hP$XRF$l>aq-Ǎ02a`1C̯# w/dØcoC} 66q$# Z+#{7H_6zvC<; po;w@[C lIby:&#BSΰ&@<6O(=rJٛ _J;,!a,w AI$$rr Al Lsv:qp-o߈  Tq D K7}z\ocTcm c̯qJ;>HSҘWe1Xa$6&)c)8~E>yb:%Tem$JmlFqaaN`6SɁl VK F@Eƽ r{(paU |pLulŅwKH~ K$PY>FeWmd-{=eV)qE)-}%~PJ̔)ⷥLLɏ7݆ƿv$>>ZB?zd`-g>f4=/_lia\סiơww+ي Gqp{tXi%ԙ2{0cMת&rnj+nfx|̧2S["5w0v'L [L6}m}6V|^f6[j͡{bX}'\5''Yݤ\eOIŪ!jZldh+4nzA}h5q$*vKαu{̽s0Ht(Z?s}duO_ OklXVHlkwW}ԄFk=Xkʶ3,"ő>a1 cq<o$yq)8 &^cek|p`t\8!hC:J0bAWh#Å>4aDX07}gYff+A2̑â2mt`| ]⓯wFC4⸺'+~ ) j>K&Q:F.` oUyԺuz{Y i2)Z}'ymVbzj+L/]o1cٵ@_Ei>2qQQmAQQm9X4ő"<4UXB6k-aUeC(|/S w}|{ݨ?\iOx{jf*b]~M*?7pK'"\һAUߩhAIeܠ{ƅka̻   _%l'MM}vڴ;yϬii &Nh9>Op,?KlCH#xޏ<}\{DZksB}u9~"Mҿa**<3oy%b>%U1uDZϬE Wa3?p?M?a6. _<4:Wy.KӉ5Dh-\x~g3L ~/Vgw ωHv0?bd=9[1ԁA2I7 s HҁGvvdǡ99ܡ9ቤd^\~Lv#q0')iP9 c>a.A%}K2Iz:I:;&)Z:!iHu%qtZe;Tf oQ oteWyL䐓6u9@::F8";!I̻:َ[ɁQ3|DZTäE/'$dG=h"biNOúK*Ď+ 8sOgCLF50cG19:D8TS77ONwN3H+' C ȋNJ߽q˸Lo8}#4?i['_ҩu):ħ:N.jZ4Z4TBpZBq@wEq:Dv:I5esT HI+Սf0QÙx i~\J\NE3WSzs-Ղj̜E=sJU8rgSzP0~9uŲt8w3LRL i43*`v2;P"j33PAf=jys[֪F*?e}9il-*rn+:˜K`^&:oQu99:,ʝk6z1ڐ'I۱i8Vk4U(ʗN`Ng geI4լ(FVt=']Ʋa5PX8S*UInPYg,s~t*e2:L`X'! 8kT՝uRQ2}*(LUAc1KAk>پX,~^rf>,OPV+hV{XuE:,Jbec>#T8WGO`Lc0;~x}1L.ԻduQCZq17>sHe\<Ԗr1.G]VQ.. "O~n֨{ea ޟ?H9>6v}'zAz7iz=YTI*zC3Z1:&[ºC?넕‹Ba}p3g|$da/zPF7W? 7-|ݜ*D(I_~\x~Ix@xn%Cw BYzh]%*WW>C̑ŏw65f=G#-x}cȚ_(qgEEa"1F(d  Q<#K@b3(A> b3+j3"Q-FzJwCWQ+'cp\M_ <^!A/D(FA$((>'#ї^uh}*oFf*tqRnb$4>GHWt )퐜9i6(nLh ( ]zAN{,>#5cb1"_hHDݱ2z3h8X#X/d,1JqE4F>}\ؽ_ ƬM53\9]-a8A "4eA\DwQc-*e$Bm[ Uchn5vC~|kta?kV/7ohn3cy}/o[;|7~l~KB7`CUhx~*;Pɗ/\n+dl;~S͖[>{FElCLu~|)51[TU'O25}?W5E[+g!mv$|CDJ?;Q_ppa_͵j sI8VDNE|okh Mߡ"07?oy̝|~##y}D0spqya;{cξ.Q˃[>]Ak۹(P ӷ u 6PVD}uRTT Eo;F䅩)>>'jMqO مF@} >𹷨ԧ=}+Vs9VC}>"Y~A|F5>yhѢ> O<Hk,[}_ F!o vCɾF; F|ס|. h4LXq>Qv[8!Ƙcsvb͡Fc-S5t0 =>k7:b:kFVXmcZ_[ JXf{OsygVS<D՗l|#YsƩ) WOyd!/\ҖgOĝ'I$y$uy%"I=BI#Z G;*&NIy%=x%xG$q:W.1JW,i䙳<Iu3* rS{9N:Ӎ:I;Qg81T9;M5S-M([j}Nr od[^w]Asvܙd#n1SL sf9ȍ; ,!K8\qrg?Zblaۨ߫=h7eʺNבrKE(OIrZ˓t#u3tt{'t'tr'5|y\%Oѯ31*OgzzO\wUSGVR6G7U6M7PV& +\dudun%'X |LՄ9  e7Y.2l[zZJ?.N z̼o?_!+OzTz'YF桷Yu.TvU-Sneᲆٲv#z[db:}|~|~:N>_\^/C,QwMsى7tn;tvź]yQy[J._n3ʭu:/ys]9[wSV]ݘkk1ֻ躜Xf \Dq}d\C`+3镉?r]ο+u:A&_araD0X0H>s\J>)|EsyY&+R&x-_e3&ϴSʔ*&g)3 #{Ms'~U(, ?)*2z(d3+f\I\v^O$6DX]xqd CLc;}TcDsNqTcaoʼnO%1>ImxiR3'?)Vg*~6R)K x@kKq}w5yo5yƏ$F=e.2Uf|4"t"W5 RlRL>ؙNZ4(}449'U_?'>ókn_pl7@/6oje~yy=Y4YKcO1=K[0u%Lԛ^SRWxMK4U#u5g2дys&xOi+{;7dV=gQZgK i=ۥjz 5fdM^RzY5vHn&㝗]{gVi{uzm[읭3y/{yzoWnWu6#b,~t%j̗|P^Oq*WjT1zZ/j?O{N׿[ПQ-9<QY=a>WcccЗ!}inĨ [8)9>q&Âxѐ4Xn{"IDB!0 3ц27 2^e =CKxO~t7{epx+hc8I6# vDx!.gt!d1!#gh ]F614Fz_zj] ?5ieyZċϜpk%^r¹33GpUY?jUcΦ9XO>;Gz9[eߵvVڗ$q:>|;`:;䬺$d2ZCW=~L6Z- ea-ڰ >l*5̨J kV ;l6_y'trKhPshEh?坐!}B+V& 㡗 !H=[ y3Ŋ҃h6"b$bբxP JXDɥUBT襈 %( mJ*M ]vfeW/|X#BX-rB7(0" V@5z {qAKCXҬcMjC3]V`/m$ց+` k vv<|~/(MjJ ĥkWR/Iu uCyg`E :=G7Ǵ.lҼN_gwA /mF|~_m>{fm>Brbcfڬݥ7;Ǵ7פͥtasmϭ˞B?׿IUW =oWӪlt : l^Ʀlجӑ@mW(Dd V4"!>  # A"`";(yz+hY{kר(<@=(yz+hY{kר#OЁ.R'x]TS^TB^J'$!$@$ ]^{{AO(w߽e͞9g2e3sraXiX%fX#8,njDb9""a=pfbجo?&5u|{Oa^uc X (9RyuX4mAIbUm6-۞RdeY'ˤ>{ *D[^^yP==!sZ[%m-I+1m%} K:?/Wʄkb-4fޙ~)IOt*ErіO}IYlt*nSP7<\b| o- WCVزVoڭx ^d<4 Z =]>ۺ~Uh_.VpSp{tl]#'|pw;R;flA0Nq:^0k[z`y#<Ua鰿|dY YxYYY}ʩY9ӊɥj}NkƽRUWVv~UOATꠣZ59 tH: $G1ced399l.l䝌Zmg^i{0v2gK˘.R2%uFU;, 1||e7mS>ƴ6T,!o@(ɫOp%WʣJgP}k dɯd| k;U+6,*m{v?,.J|nySؓGNˇVؓn>V3rZzOWkb|8w8棭B{X-iWWl\7~Bm%TmeٛX}, Lgsޚ}]!g[[3^K{sG2smfj.Y%zriPd/V̜):bF,chƵED=ƋG 'sQRzWѵ6q6;E/q*9wZ♅go{uXS|XQ&%CEi4Y5DL { ozc$,ZKXŕ_Yl\UzW5w=:ZmQ/_L^s庿I"on2\_Ia]յ*勍;Jפ2Mq_/v[>jVuFʴY}uVʪXy+L8WD~!OVTa}')~%_rRuudtڮ}cˡR>)ŔnڳLg|BZԱb(R7N=;zl$XYNzO1w\>\*ĭO;C/;z]ym3*l_}˝zڼp$XMZ76DOin3k۱*tJo~U:cߏ/gVb=YY_u>>Lt?G)yfxW+Teӻi8SLp&>L2SW;9?Kb,͘躚aٙiXLxY?,A L+#u,u vJO|+e_xP׃# ?Đv.-*D߉?[ cs蒇e-a^c=ʯG@׀$Tπ=n9 ?wC‰n ōu&6Eo57dz^ C. nDji9hgȞ7܏tS\3D>[N:5#j{dIھcJKWmV#??Np;;RǓA)BRlm]J[Z_Bm 훡߱-Ƅ<7u8glɑV^K+3[#3&.c:NmqA4ף1#vR>UmmusTx Q: ly'?H3]+ɶl0N{V+&4m?LaԐr~Z>+ ŸU3;(mtusF%7)^7e4ZgZǘX{GuXq=OuK;?kNMn%?}p4k VGZ(9dZeJji`4KK[iZV~g7m}JWo&}[Qn R m?<7:K9Ne^ׯFCk8Go7(goP~P{̳ws %dt>uKUk_~}oh'k@O79ؑ<|CPٗGq )ODe2XXfQ,ܨ&`sXgs,[d\,آ\QI8(iLY(=l`U6tcp 6z>]Oȉ]4m CSz hеS>b ft`A}-2~OGON]HZ(l=ņ<#ytG>FlDg#Ψ>cI.#7ʮ2b3Fb>El tvɝtl"8Ga tqt'O.rꠧnJf2*5l$vхLú?t1/E}g:3tѵ i p{.t_s0Wr⢹xC=\p1y .L`E; oquTƟ~}Ԯ~IlJKsź,?HA_IR%,,6C}ĻĺLk&ctĽ 4LF-Zĸ3IRf0ӕ0̰WR~}Jm/B6sWlb 0L{&NP;4r\oY'0XH@a +lt6a &*La G0jƍ2!\$"Ѣ0f0QM|UXQ(* žB DCtY3nK3)8fS7xX֚&Xf 4f7iJ !#=3A763^y0WJ:aK){_5P_ CKR8L5Y/czL1dM$j$/q I`9C[R?.7J ^o.t&%Ծ_i\0>" PxEpz+W$)%uqyMҲdk>?}MSg7pݔoHOǬoCڏG.~?Dr )㠓[]Jq[CNxKq0[q6;ޓ3qx2#qp! Łxk2} _ C޹Wt!^)p<^̽WJ_XJ$ {) e)/CRYeR]2RNȬ26^}Ezgc~4:^/՟m)4OdSy5nhI0!!#9xCp4xUBȜW,鉥:<;"^Mm O(SWg'*ƟD͓C'jr1.~ãǗbK؎_G77Ak_"?q)g[_x7_2Y;%;".u yp^( jsixƢyMvvRɣ l_)k*2a1U05=/d=X98)pap؈bb>#Y% }\-"ЇiA k +U=!7;f.SQ'hr[D"IC^cEmk'jYqɾDYA_?cwґ7eoЮ;*_lt#̛Ec{$1iQ&xevtdX=2;#[#izFX,/" )!a=$L;#VCQ|' fh̻G{ WS*}XsXA8Ӯq"r \C051F'cQ3{EXq.A|23q=3]vG/$>3L3)OlVYv3fluZM3,&m n8Z;GqdT!D=S aƺJ62h ?ϵ٣VN=X*Գկ[䐟\࿊}NvN$=F-Y{dAC0LL3Fg t:#]faxK3c7B(LH닦XUpf i)浻Fq" {cUK/~f|&/Vʱ@D{kZK8D OBߒZ~[Zy?%_IeBWϗi ~[{;0vkb%].jnh].Yb.Yb':[QV}ױV<5nI8XzΥZcj=t`^z8Mqd5#٨{/X^%t%x5C>@ݬ񐫋5mqZdY[c:`J0kjBN<etc@tpjٓ8YW: t%,tp2 t` j?.4kVG tFl[#7xV-}k^9o’&4BՆ+S8^ ]9pk s,3 K?_,vO?sèNhU_*lFdK~PF['D>- {":vUt#H7|.Y\&3qU4FĆG1͘8 / /$B$lpX\arùV_4/ x,B8-pu9V1âOa]N8|;cwcD%ayKaD{– $ ,jMvaUϧV?XAqBMy?GvhQpg/OؙU=ڨ=\Mx*֣j6X?uhA(] koH_Glh&-- ֞^#Ů->DE"vѢVDq-QߙbfG?OSp]%54]!e}Pv2p-v*ch-F1t-Re[pC;Fء&6$@vΰc623{,vasX8P7D&E8y\=)oX6`,9xv3(k(P>8<أqÀ7{8rҳGJ' a- `[tĥбt 8HZ2@{PC `s>Q;uH6} 1e8}Nkz}=x\;㊳>ܓap3~/}V D:Bf0w[D?㢭n.<\inj.r/? .-p1%\mf[*`kҌk#S.٣'(A{Hr]`:8`t9  p6t7&rt=8@Bnh=v1'#؈8fapƬT0>fyvlϴvDnI[L ccﶰWb lz!qWɿg,56#4)K/|%z"HJX}:_r#.Q'}4B6R(]%ʑ&Hsizt(^:G$. E5" :QddQ'JJd+%*8%qS 񊈆R#7D&.8#q[l/y&8KKJ;%ŅFz@#]*˥U2Ј284Ԟp?JK֊IvWIKV%sč%#bI{qIOh^F0Ht67FW6]q-6ng"@4PhththhT.-m.$%Z)-eK1}DjF(XK3$# HD&Y2a$gY+)a#jnG7 G?ez]P-F`s[G{ѷS,f&NH5 `3G9NKa4d6Fr=w,)H%qtF~a 0n<0B.8nm]p1<\\o ?\/"cfn8]h Kw70Un(bܐ>3ܠ'2Dnzo{ +m3zl2e_7]i 3 d1nh0{sw nm=p>F-pǟ'1f2?裦 W70[WD W1ۥ FblW<7@l+&1@joW2]sW3G.@D.P(twśT]0f]q!⺯!uŒC8助5 m!nXgb5ilg/]d\qi 7bD#X`a1m \8&]0!l7Oϰe>կHHT6[ C=D8< zt8b\FVr#+;@d_֓8ڒm GֆԑɈ,@Dedb/D)q2b.MF;L݀l&K=Ɍhw2>>]DW'}'׃IEU>όd=\^BDo&/,(Fx--żV6џϤi;ˣ~k]Q@ Rhgbk9\_Ug7#,h]¦([n w3@t],Lq2qdS5īDS HbSQza)6{aI2ƅ&eLpk7,5ƚޘ7F+o>kѤu|!n]!Ɔky f|2j'5# pCl: P*9e!c!@C~L˻Bqz?쉡5 a Z/n2/4a7 #Я7Rao7x^c<2kBh nBa& 7@] mO 'DgM0k'n7 Okc/i˰:K vBLb}VYې!MsCB&P:,_A>;HEr EP27 +f⍢#+y8K.*d"h$P' 9+YH.O'"pb-_C^ȮK +Ä 91d7rS>X)P^[QDf*\TX(@?AH3$\x)ڄqܓw #2]'o"7 q녰'B6e .ڡ'm'!.#Vءmxgpp?E;,Y?ҟ7@Â-v a;4a; H;9 eփQږi`mZ|[- M[vB-Cj W tjb @0l@Nà@Li}H-J1”kc zy{;w{q+݊܃>$1s;.7гccX{Ҽ {qv2ïs"cI K=n_b~[9v(}|;,^vx:;;'lQ<ڢE olqWӶ68v(5|X#s:c=,E{̧ A.ZäHCI=Z'c-գMl;>v{|ld.HR.QJJJגl!o.o%Ɍ/iX"K&1$1,1,Nbo+mHE*i\|47~tldi3OhX9T)e~M&}/o%]ϗNw/t(oϔDLIB|$/>N2,dzJ2dw|?IAj򺤉D4&)M[-hX 5VՐ>HT7%a8ZOj/i D$<ՃCժ)'#V(F SHV`3#?U%E[-VB`L)NY8bgfq0Q7ǪC1s|}:t5&*sL*[j)T>s"7ώQZVE}o׭un넇6w4>xhb~gìV.pM17^<ӸB{]:=mܠO}W;qj.o>|4ds - 󂅸? } -W`7vŤ5|ꊉy| |vc>e41cv iuFJ Txy\Zb_D5W͈zuYY?z2%zr]%"P!k ŪbeTmeTJBf"^jZ/MGJУ2OX% >lO1o/Ncp,Bq'D @O#0^u'RRD6`&k <@ m'1X\쁚 K 聘?L (<0w:5X`;7ewx #x %hj(_ቡ^v zbAtn ^#62/ ! W V템BⅫB7BCg*מPFqq'$wp@lׯ0$XbI~_,AU(_n_b*LqWVQe(չފpuOE:K1DXn8R\Q*b"=&yzpDnpQpKXIn_.q,a#rL>v?OŖp3Y(fy6 ǽP',naXB0dB(rCqY)"X/ zWȗž}4 M3Dh+"8 E3"=Hh9LBяc|#M[u^*suؒشcbH:/&{?b'V:!T=ӔZt:**aa'{;$96#1`#Fb->v|&wЇژhtc0M$ED /"q:JCݣFMv1"a*@H,`HL/H`H6~]O6R2TRunЮRuRK G۫6vޚVUmNJ9꙲N!e*-e*+*'X3PZm^Ӿבk*׸egՎAdGF^S#>Ţ62CX6X\ӯb1'DX_,ѵmp,:<"Y , @AXaIty Ojpן qIkC/ t f x ]XH>R*wKe.a]6LaZ}9⡠<,&G`P`m0(93gw(>%81}c0~k0mX_"cZ`} lfpaHb Ky`X ̓Cn9AN<\M{Wچ+g3X+а59rLK9XyWMy'B9L8\Z|w#2G9Oc:u\eSTdFL|4Z}ə)}рǺDuנqK$.Q]G.N|RiɚC2ٕ3WsTrBJu+VDg\&{oKDh˃{yGtoqh " ܽHޏ.: K%KĹK*_"G"%D*]"{E$v.X"Y&䓹eޕTH]'fcSs3B4?quO eout62wm377gE3}n9{H5wUncYW'w/7wo~A&wu]WDw >҅X/iϿ]|oum[&77odoRoV[\^|zn]쓚;ç]PS-Λ?$j}n >q9N)NfMCII;H1+ 2so$Ȁ\~ܘ $ %,o MIdZ=B24K Kn4pI s<< ]'o&5ASlkzlNu:)T%;dd\#uP!H7ir\ANII/Ini(P$^ 6Powt, IlT8t4neppקc #3y[Mub#E$zuVz_%ŔiU y~՝wK6ϩ*?n\=7VE0 yj1y))3yqzQ /M;??wuqvsWwGn{;s-~ۛ[L ~sm6wߢy~!77or~ת\2cvU_yG'Yw4<f#(ܦ~dN1Ay yTLfИ[YK ;]B.e`­GI_&l#29i'M^9\Boċ%LW2aиL(+LdЂLthXL.ąHL|x,Į'L=!21F^*"g¤19}9 g?&Y21ifQ4 NWCk#R' ƳSzLlg#41y9ac90<[DZr1.M94).'>#[ݚg{bb1l;3+Ć̇b5-%Z q8qLw`\/V|SSJRɒ,!YPY&yLrg&ԉa&ɰf2(x0ghK$fWn 0l )y8+9˸*+Y̸)`%VU54t|G7]%6-Ĝa$0eP$K DɔX3`dR2^I\*!>\.>+(&.aڊ25q=Jȼ`Moܕ~+}cg4Ƒa4F{\onbz s*.62V-hv[o]_}+d iAבoX*̻_OI $ Qk_"aX7fC]}Ւ+d>5;F>㒠[4U?|c[Wm=\oLjýNddxߖv>`zuF{?GK|vyH.zn6u0 */h_,:KVf%/LAe ;B4e4xX+ "XA`p)"WWR3R8R! Ot-f࿇AR3&P|6ls | b0*/B* pR +QVfɰdx&)_Jcz73Vu%`@)pE%,"T"7uX#+sE +_)32~F=Bb hg4N *B;s Zݗ6R`..J.81.!TxV";*ul%w-&-# [C {Y=U%6@>6]6-fgλ#3z/XP[qme V~kmkiFOd(c"WyM7\ gwK 9 't?݆ftd@oEF~(nä~>)~_ h|9OR眲S#b!> C =Xl B4N':F s1p2^*NQZyfdkMY8אݏ!*:;Q$5e{$?u4\zsdhTTԺ灄yWi>s0 T?܎P`lV, /XНEVbw t ` <@t E `> ­ppš.T% * N*d v A;q:"_K#Bi6Ѡu!fv8I `#iK4p&4x;FOOc}[!A_U!B0. g)   I ^g`2C u p$x˄p=Ƃ$:d >?9HR$h`D}QAXfSJ\_)T`"H$??*l lK* ͐ Qc _ pmb,{T,$ΥBCa^! R[YDQd>8U|Qa7OtgExErwFwL[W&ZGś"KiOlhNW}}8Vc}oZ7mZB?.,R5m!|ST ЭS҉ }c qUݶPp[l!(.L¸m ׶;{\9.bQ`:Az[6iJ8;*} W%=~-SsّsJ]֏ېs)iҢi(zٳ]kY/'W Ml Ub%R!dXNN-el2Ldm0nުOw(>iɐVdϵn9L~4IXwyIj9JeKs\$ûIp98'69SMpow"ZD3,rx"`鉰V|N K=ؖpmI-pB-OYqcYBx8a[[-xwr ClM` xn|ex82w[=fPar̀G? f ڛ{A;Dp=DHH1\VMf`8|A  bࡎ98{%na;h/Ary\O^ P"w 8ak,`JYpyu[ej9b `ğHA $-DxYfѧDb)a@99&A1 & Vjc_4 2''3WümNN0#54aԒdk[Ls0 3Χl\:P>˲ɠu:nIm&pvV2a^K%Cxsv%z;ZAqYD1GJitO\ݭ9y}K-DZs[RJ.q%8$98I9'S3S2$-)r$N=@BpVK\gϒae${ك%\~6f;Kβ%zlBŹ*vlgpf'rFpWpū9]9*N+bNE ιQ}1顜t'NI4 {K/l-q8Z`(qgb{ؕ]ӷ@no)S$gl'xx []&iu5c:Zt8q+É8\js5l]Ld;HɎ g"T:z y=ʢh*xӇR!u> *K! >.Ӈ5E. oûQ`1|WJ[p/П w,Iߖp-]S!MSK"SᱥlԃnSAQ@G ӃR8Y/(=p @M|oS%!vhIPpwPCMj>jY;$[axY큅S{/IunK=KKddxgPzf5̸(-(!#6xM zƘ Ìs^K= %- ,tN7Hq饠A &opnFJmߤ'Z5Y!Z)LT4_j4Ej4J&(Q*T)AҶA*R7fɐ['x,vw'D*-xM8sEIu )kщOy"t.Fu)FSֳaƭbw6,.A"ذL aΥ(fc$"0hZF*R{F(j)> !Z1#O\>Q{1z:ѓ ѧB|e@(ĥfCld eTZ֗BHr%(3WCRnE0RmQW(,FSBabTZ +P0` 0+Abʆ#ŨVil{-HOגNԆԇXu|ly-Ii=c_Xֱ]* CC{ʥPP:VLW1ghb i b&C<6CS- U5^0hb*bFe>5н4㡗hC+hCҦդoE:}@J?!sVq :@Y8&ZRFbR4V'cKepp[!jZ3eCƆuhuY8Pp0\n9F@ּ2:&V v$(CSE2ʄ &!eE^QX.}{K0q:> S#ס".o†=HR$sVVvBʻp!v)A##@SM3bF8X(#`_TT ƄׅB9< Qbj8)xpu(@sAos>y&WZ(8p:IG@xiZw4oC @ߑ <]z>2O=GZZ1VFBduP8=V< 3Px~z؍‹Pʎv6<]44xЦ=<΅ .\,@|3.\&|4tIDGqC" F{cYtB7|Vq*-DS#B ~EGZ"Tq3Ũ ;VnU 6qa ʅOJD[!oK Z)  &H ~ ӽ%(^Dp&@~@~KNp!J7 ҝtp&MI"L{ BQ<-AW(Ȣy Ri( 4-BPA%(ndSo r\p'G%H[QM;-n iq'iB% ZuD8 amK#t vy 5hZ{'C7|g"m6AtBx |B)Tg; 𒋗th=Ed(G~06!v$?=/փ^۞+^[mL1}qW u3>a l@sFBT %"~^0)qR^ h}>t^ NR>X!aW؀ c7!w(a7ch|"۴Z>0_,e7LBߓ?~luZ؋Cc:LB hxF}/E(4ɁOu;@1QAl~u207&}3*cmAV[Q?چ7(߆tRavӷsk7mGO€mhC ZwVv~؂"@-(m7#`3i4ВHjw6pr'5֣ r!\I01 =o ʑ*Cb۬G bzεۀ619p6pFd~Г0ft$K7A} !| 2\j^{w m+d9[ѳFpVz?e?9}JhUGO6v0=xCNxyO;p y?kC^: 0䰃vhuTz POj9^8mݪǦ96%)p7&T!i96= Da\=o]a r4 >._6;†%hISXիM51HS;]By ¿{l+AKLSb pCcSnfNDZ+E,ӷom*l%} )wBwB+ UtP>>faVf`f[f_*T3V;XTޘCQrt'2!jG.?h\j\d" -VH,鐋-aU.\6zEgY½kH0Pvm*U茺 н KHm:tr e%U-"3^mj3s裀d, n!:.M.Dʎp u㴤]STvȞa @F󐦊%CW/Y@$=(<`ƿG[@llCZk`>n6,n-,ec}vnfSK`0+E xSc9~|ZDILᬢ~✣*^pi9R,ZC8&8w>% k9Nk8~G-Phk9mhٜi2(J0Bj$g:Տ3Jũ)gUzKO8 jK_|Pio9} [R. }3sG &,Yܴ~ ,? l֠47kAbe<{~ ׉?8]"h/S­9W);"P.FH(("њ/s>qj3ϜM5+ +ѣ4p29޵ȽgatX*<4* #e4H$14].h@u}z; WjM:M-7:*% #Th8`63`Q>Ry/x:CTK~6Յ?ڕN5緢MJuqNViwBy9F`r7{+#us^8@0 38=vv9@՜X 4gf@LJ8+ЙiN0aJf_\>:AUf'(] VNR' <נݝ xR(Gx9$Y:l}E6<3'>m:ky[K|М7ע͎tX[9A叨UQ(ۣR zΦ^*R#;JSD]t:HщJQ*,܋̣\\K9!$r%9[ :QXv_J>QTO[OŤ$Dq}S2(c^eF].1*.2jOT; v#J}Xobe}f2> ߺ/ńNG;6gu :]iYo{jsZ=C )xg[qMz|h*ܖ8-:[4.NC[\C!H4漞2A-s@q e!00 :AĄ>0s|Fy3V0/cБ{G[\2'B*5nnuMCDC}PrP,G(:وt͵zuH)X3dЁ:4E D6yֻql?=ԷMӴ&kIN%.ܮC\|ƺuTgu\wZg M1s]w:ea;5}9Ş!{pzco GP}W~Q"}g<[Pnj'@3*PIG4[ рpQkȿi*1ݧ"?pcL@\>_)lT^h\[t>oqxԪ}-/e؆ TOܞF22f2t|tY h6iև{5,MOxcA!EϣZ>NIpE,SƊm")Q'jC}CjwIRF½wQG&dAg*3WU(U5a4b oS1p5=cTG^i)r=S չ?ʠXedQo&Ƭ;c晬N5 d5t|evvSfbck~} r'>_KW̾f/rI *`j[Nk5 /0Wty|$EBFʠ4 "4aʖL8SQ_Q 2z?RnE!_JD޾ [W*0-G?)soiA>f}h52}Ӿ,mO>;z|0[x3cn,ܖp7,ĭXOnurzSO5({s#Bt} *[ &,]>T%(`.$gEW`&:qC@*`Hsݲ-,рEhD'd}uzCutNĴM(N wM\p^ῂ"xMOlU=֪ئGnetZpۥ?#qӥ^K¤_̦yێE)*hݶ ~ЃrQǝ`6pzd h0kԿKWpj.:֋HY ;Yg>@@/+x]ZjK.E Jak4m}E-)8}:! f,#(z%g7)MWRk^;~׹S٪k^feհ I-;O{dlng~xz֖;ƙgb63f&ý|G֖Kt9íU62)`cP-9]N0-ډM9ҝ K{1(>D;tHSx7J ~i«`ea?VE2=D s.T!񰌺>U/>O# )=s2:~سHo\?ߘ7 g>77o=p!m|5]ձ>N@jh8_GwㅦN[i2ZB~Kd  'hw&sѩ7`@y2ZѪW0q)4&;u sh$3w]oAu΅ȩ?V?]Oh]éԮE8j5(\7K!:V+.mXWPOWq .!]\.H̍D # P5-N-}KZMTNNAOސ<6s{Ao+XRcx6 668o `2`!)?A8o 뷄îFಟ-މ^ބC죡GW(]GI!E-ԧT4Q/ 3n>Aث#vRk:OSzPט&8 V̉Ÿ0ń8%Y3"gW ,7ZNgU!z$ozXdfS1_AU _\'J)|W5ݣG1q%{!˔T؞T־Z7[+<|~gEGu,Be,¬=!vR~?6`% 7ڙ%ROZVsYĢ=YDڍrϣ4vl]18ڿG$KjcEܗ88 X7okMADaDtKW?AHױ}OM^[c0KQƠ (V7Ǡ#L80X?yٲ j)6̠2]Ekγ-ɪ馨odO%,[uLkaY+kZm]jֺ@l>z n./r8tާ!.?$sO 9W>!4˳ ^iΩArW=H 0L57Zjs#L6W -Vol~FP.mMmosE?Hښ2&+r_OMYl>H҉pV՝hfF*2;BeuXbMsV ,,*_Fۮ} 8T"7ΪmKuR6IeYebUe/C2^e/u걗mjԮ^j$T֒Jr-gRկY#MS>dOt mdˁV.1]'rŖm6nS˪ɭmVtۢf#ޱFU۔վxb# ĚU9VUo9"}n*n[7lKɾm?d9oۚw3Rrޭ+t-5oFT;[ZmRR~=Z.=[7c! /R;rY]Ɲ{BlZ7>±d#-#*aZQ3Hu 4f%gq+;G#q 0H^;*ު7f.cҺeB*n~2 cc4X9cyXq6[6UCEW|4{q_ ReBv^I~Lvd!`ƿ !"\B8ӯ9R8"p41/X-cUi*)[Hs4]Α stȱ@D_/jKfuuZ}SRLTfؑXU]"~c<P)R'vH\1;fȽjJtZwk}'nڜͭd~-/lg,/| ,g6CX<,OoLW5sz{p={~,6ViuhSCINTdWiYNZӒ 3k1~^,*|? Q4Sez7-y[@}.Gr6j-cK19^ƂƂW8\eiuk'ȿzcc|=p]fhUb=8WZ݌+SQSB||vHU:KŌg+WsBfU#1m_ضj[a7~~ݬyj1 7eHƚ~ kzd )];@{>+y^]ofZm{gXrF]oUou߯7`8l >=={mװLryn -[\x93USx6y݆uݜm`[ "'<lNiC|o{kAEor^<_D2#Y{ߞ^䶚T9F:X( ߾#Dl|lmx~ieq"rJ/kx6>.;fXG7|ֿynu7B=rY>ƃWeB6XvMU4s߳l,Sr9w|Qama6R mv|»3zs볖d?I%Ycrlh~G-iyqd_;,4,Oy)^ܗq9 G\f79畸~hk+V Ǯ2mdGDy(b_r45'x_Kza92Z$e|)1No}}( }_C 4x.ϳ/KI,99$YSa,oYl}L< ˋAU_).g_Z?}:݊x Ss~~.\}K,翱|{'sÐ6NsN}+%iћErQ_Nd}\B妴߷xd̦ny !hYZŘM c??Ѩ#Μ*\ʲ{Nyš#bUd&Km߮7SrOJe>]mUuTE)Cޯ*W8:6rFKq4UqsΫν޸sGAD":P5ϟ<%⭤ SrQ}d;rAݑܞӽ?&`?JpXIr. GIS%o+T3t8_1M}idK)WN>}%H\]-l_exؤz9>6sbZ+C(uS݋tK0fAw94׆¢ RП P04.2Apob4t6?v`y|+mhlz]+=4i[ϒ|l_|n^1µ0OL> ^)Ai7Ç>:.9F?u}+%Y]_{p'mZFrښ%˿VN+pך+ƅD|4e"u<|9l])9Y p rl{\E s(\z[}sy$ѺB||?3;C7^n`xOU,:*KO0Q4nڀpf7wq;a=< NPM/srf`fgAuyW=*[;˕[fq-Ĺg0D!Xb N;{0w`Jh߫8B݉sWն 0H鰃3E!f@ BEV<cح"vkU=CJI4%ҤMZE}=eyԣU}S;^*-C:CtHSfv*w>7ciΠ@J{E ÿ"[,B߂?iX֗WH}jδ2} o8߉|!툘ޤk7X?ѷ݀#}k+RpE,(CPR&}s}OG1W?ؕ71m{MX2nQYgŽu;D){E;Os7ϵe޿%1ݽw gTwndj.Љ^)y|iP(UΘ!9dN*}dՎsEk%=#Kپ]+U]r]si ʝ-pzƳ$4VRI$y$N,ԷJ]5\i/}ߊ?Nz9q[3_ i~+|k `̝Wïժ_Y2iL L*}-0N\.-{yKzx/mt([L=|{XWyv*d_qG~1&"_ǻ> FcN UqWڎkLğ0G jbJuoơLLzX|^P ]X=}:RY_߿<ݿرU#YSԡ>j=` 7mf@JeR&wJv'iFO0jJдZq';we+.M2zn-wA}Mb]@񡘖j eP^C"2=;@Ѐr[NE=iڜjFPFX!V vMM*}F {7lNأLF}ۼH?nt/UIJ71MB4UֳLuھe냖ܶqorlO&>`~L$[y޷1TKwlѱ7Iߴ@QHYvwT |g>/+;SXY_2 [2UJ%QfMiN?j}ېwNҗ$9}$JfgL1?6ZxGvli܀df>t.%xO\zN,eXp)OձQWq%[=6"[af{W-[5/jxf{xn%Z}'k-}Zh%ZxJ 4^4$}Eղ/$.q oH/aG+Ex?Jͩ%ٺH}ةZܓ^ߕa8 Y( VHn-D|:jl'&\dc6v MN!d{4ߥX޸3UCNdZ18drj%y)rP1CfȲA]@L qsMc˛zu`^m{ .lOn Ø৤N Jb'Ie-Ud=I,dkBOykB;9gȞ_M7x^{NZh-q Z GN5MUX"ek?Q5`p|[A;%u =I([_^cdmVGh |9Th Z]~M ʩϽr6=4!Ă33G08I[^gVnag☸ e$ mk8ƹbs7]hX2\ ]Q45j{`2)Xzd!B7$s>;7*Sl5's6Bm i&>G-HH2Rhʠ;M;ަ/͜r4ofN=;*ovbiyK&'VӔ􁈪ekc]#B;'։:Vca2#*$[*q/ɖc/jPoل&ߕ6w t5=*_ŸhaOՁr7bke#yQo8 7B_k= \F!#`0][ ns)|񙖇v+HHȓd>#u(]TJV_3Yn2ª165dn;geLvWj2~Z<=\dk44 hJq =& %ns_a#l-\h%\l)\b.\jSYMUVvG]uZ|tܒ|%]X~.r?4HU>Pr+VpmˠUr#)6Lei7A?Z4mBqⵣYΛGέ)_sۯZ*UxRܤu,z/ѯΊ&XfA5z]OczVfߔi =._#1OuucVr=6G3;PLLwv#Y`IYrJɧu{*h Zy Ӂq|W?^siyR1r_8hUFOsPG̐sq`G"Z2.,,53F( jkdI/3s\<67ĭY\<4(.o6{.~/3ĥ4`cF?ƻ#c6 e` 6z>1ģkȟj hs+6oP_([{YJGrHAcC@Z(l9Ɇ"yx>FlHg#֬>}I,#2b7R'>4DL  rI] e8O!%(:.وf>C jb1#]n=8X@l_ aY~А œEF⍵ЍIYqaٝO.r jlpj^IGz9lp|A/@u/Hj\ mSJJ +$Ѿ\N}EJ|E"=S`_uC}|Ir,cЗ]iѪ$ )%u癀q{ER2d+1?yEQkŪ`פ'cրmǙEIKg.~=[r5.㠋qr'!=|wVc\LAoɇA&H"s_8}I,p3%%IDDp@JIH=Kc2#,<#SJʈ[KI##($3xy%ٟq||ޠVO`%G岪&Zfp33O݌:¤ 1#8K=?^R(y_ 1TKFRAPPSzK*=-h./K ~YE ;g: dcAor>*}-'Iͅ~RkAXG!6<{ID&,$Yª3^T_x͛ gJ NK1Y#8)&8$"&t̔t (PA$L((p_zvPɡ,_)}jr=_9~Uؘz[bdAlJHu\qar!ЈbRm2J8ߺ{"RJH&W9^61 n?>Qlŷk>㶐҅%k&HjC#jć7Nڝߑ? ^dcw|_[WՏR0wc2v%G\MFXҙmwɬD3lu`)b=$7a7E9mwILKncx 5W<}|i6˂$1^,KMp^s_{ s,~5+DZȜ ̒6 t~Ĕ AM޷2=XAU2<Ћ jSi3wIGH~vwo2,KWL,p- B}m B2*ɇb]!uU5lm ??kkOG8tPPZ׸|ܺ H#W'IV~v RVſVȫs=`&u 񷷀A糤L3 s~jf~%V*VH+xj{.s s>ą) gD2C1y6">c)aFKJBr$C&Jv,Y#QIҖ;T?؎c -)]zđa|:؎8Duqx=|ŎzFFfYBvMSݽ5]PQH7ĺu FSFbHO%JTzĎfMlZ~[+t=eKɥPvMXIl{ƺm FWfyOST)gW jz<]>+4B1;M7v`,{2±] H:GK賝np@l;`pnf#l:G̷7‡Qo[a6­X0~7E8q=)mXlv`9xz)P:X8q'::„zG8%s1rDR 8`9 `y{Qz=j9i~)5qgvظ[ g99vfLP!~&Ke.찬1!"ac17H1q-d]{hM!F&pnBo1vl1>d8"31Ɩ_5.9;ⲫ1\'D#kb A#1m=1vG1B<&s#rr\d=C!.=~3b2\ӕMXYR̸3K.88'َ #vs sqttؗpF0 4 +RA#NU3'h`##ubÓGV(3S~a:Q?^l$:9 ջ%'1%aá\=/cc8pBN]fYk46¾4-+K/JdFJ=:_v-A'4Kvr$U!ɒ'HɳPIDJ>["/$Ւ2j%rŒ.4d+$ul(B >ªK5 )Y,lt}<a[anIeO}f Yt이3_K[ʗH[ˇI1IxwƠ llltltlT%-m,)..5uAEX0S@j'{-i${)i'{/.3^rCNVT_ L,& &)WHvɛK6kIVKiL_^&^2ߘzXfl(0 Õ0a%~zSk~~G&sc=Gguˮ" cL!JtA?L3^6´,|kT;f1EYEJKO[i\@又Mb8BKK"I'bN`kdq]0ᘭ9N\ríprG| sLpGP9Z^wasB3# R=cz`@eS4]Ѧh=FS4w&GfܛtƸ+qE;^wd_d!җ,&#=oɠ:$+q(:F~lL'U4?#'Ȏ)|br;ryy|F"aex"E ;"#.;iZϲ}~Ź1 t_l# djLq`'B2`鉶!nꉲe==1}$=ѭ%N$y!%; 2&zc_%?z>Xhj M>'|o hZ9c9_#/ڞ1Ch  Їmh}!~EWsS||ꃉ3-঵ 2f7:5C1 Mp &&kv u"p~ Mqob#ZXo32Ao a >& WST+ASd|an~| {2|ьg'{Km-0/c-P0Y[hm]?i3ސ̡޸u+xxG{T ^8 + Xxa\s)ji9=5f0z_oVqM?au*eȡ> `b,r >^ঊ9qi:X^1+p;eb %/x|Hy3ZMA9EhV۶Z][ψm}7zm{#H3 C<[ڴv)3B #nm=vx֗_ۡz>^ͳCm>. ='@.;HM;, @0=7}tj="=j4"=$BjhBU]!Fr=!v@[N;> X8O34:`V`d4`Kna9 >JWr_=QG\h<5}0!cQH.2/V:,ҧ:¿+a9HG``qĭKAPnp/+p*3WE OV!=raq{? ‡-hQMxw<<\:h;aG>xtc#ん# u'V,ĮH$dF8bhH!6|t@Bӄ!dC#n{m|=l Ѥ)}o#2!:B$ء5aFTk;h{`1"5](\ <4AwlYc;=adwCb} !vVn,⵮\g(Y0@r4k1ftuA,1Ļ>O-\]p,Oq v"`u6b$Y 1-\&^j+vk%np^`oMw ;t{x厝:1ץFyx6ᘇX=D DhȻ厉r8m(Vc!%741bV meqER+5xY_oDX5UI5#^G\R׏ܦNܪ^yQ}+Hmej D ҴڨQG(pO`E3]/""-G֊34?v~]mCZM$iD[mzZf[4oI۽DS-&#v`Dvrֈ';.ȳ!۴"kEh_G6ӚFkkDhGmXEװ4O"Ki֚HƘ,ՌXVO^Qq}~ϒb#OaoD"\J"$O"_`~;X^aͨ~@~A=w}c>01[&3h1h_3H { Dy Ņnް/aWodZHl7Ih7$ yCtUI~>4荾FbzFl獤$ |ͽ1/w^xU]ۏD   Ps#a0` !;)=`8~J#lĺ&R\ |1[xc("ڮj{chG罱jo[ f 6A ^C6 Q>-c}&Y}8+b+WTFqq7dEBLߌibU)TTׯܫi< Qh5ijleCmoe2IMP.׶U(/kMEkbB]FEvwHQ-;u#.~CNEY EN\Uqኦqvq=,ZW6^qCNqQ+SֶR)j={UAQųt _:?_PS\{VL{OTF1_kU:+j=JOZJ+k{)SMe= ۘ)%|zߝźn 5aO1j:77b\{1ޭ,N^PdBFؿGpS"Ŋ׾8W}QZ`r`#x%Xl|z?u> :n䳊z?LY];*WV_t,2.(F3+RwPi_7&>$f^`r?Gcׯ]-(濍nTWL"A\F0g;CX ,zB _`RX0^qUQ:55X$I]0NH嵂߸`,^˂!tx$O`/beGuR$b'lĶr(.N([qqg㫊v=fBxׄ~ Ǐ[5K0ȄYqK3:I6nwaJ})gӔ`ʟwOЅVp h>ykgy(ZB ,CƷFAQvk#xfk R`^jshitA8n :hT[0 :lG&T#q6'qe9s;mo9>8Qh MdfOTUs[ĥ%VS%jiIq?>6o ~C98 Xݯ-ja1ŭIbXqŷPeȜ+IQ.ΝP2 Q_w~OXMOH:?SX]&=|WӢ Mqq T/[;sV[] H ǀ}Rl7"K Q>TƌvD[,aVMNQL<n/#/EX4헉6"2?vcJGq> {dã w=jIJ&5 k]"C%IFq$2ojl5O%鍦*ٜtF3iSMJMF-MVGɡ`Jl^ub- (;v4;0/ ?5umHWÐ"Òg"z1 b`tz$FhUg`7,ݜaێ{9 Oitןq Q@Cw. ԇn7/ LjxDRBteoDH-w~S+Ф׺)i, $c&kD >lWs2{9ѰGHp4#o4~Gh:GhU"Da7K?~tGc\hm/$@z%p%hđfUa[,@ F p7 0)VMc 8Y qQ Mb{Tj;R(x;GMb ] 3ѽ bp-Bqc]p w b' +$N? ;LtT&4U4uϔ#{5S^j^촗uAXt]nZh/&/K^&dWmdvFrvWF{'Y5iu ]v];Wgݢ{Ng_zm{*|}i"`)#U=cؐ 5l<4vj'y] +Y4VbquD?՗F y)g4StU{XQWj2\z[5.I'VJ6m:0՗Nb~9=NK9gUaA.Y,/Α:ĥ'0yWo|{:䓀:^ 'p`9F"yCNIl;]$]ΗH5k\"H觗ΌdL\k&ceR+_&ºB;s# /&]$b$X':#%d(-wntW w;/ d(]$BA2H\%#ErhQ2ZHOE2n2J.%pyOƲ6ɘ:̡ 擻!'f;aO&cXW.:iqկpbY}nز]ŷ-#oLvs3Z.r[׷#XCٷ[mVf7 !y~-qw7{_jwa}en!~ڰbo%:_7߇w{3~~vA~~³2ߴ̦}em-3LΞ޲CЖ$;ee=7i=[|=w4)H|u2p :MDzNE5! =\#EiP(ޡis:~Y&KCd_4sAۦA08 7mBR+=c [*V)hCs ;ᥠy!+UdK6 _0UH=avP!9vOi n:"w$: λCQYsH\u8[&CRB2PQ!7Ȉ~: S¹AQ(dŦdc HfŬHvLNv'#Ѽ+NL+ #txx*1@+ eb \- TA-Nn)AFHA7JR oXziRqi<:Wp_@R1˳lOŌ-NwHp5*+|ٔ)TWq9~OsU1M%wW1s.I Hɉ # (ͮ:ۇ&AЀ䀻WTem8:{@@Uq~{Cg{?.۲o&{UCvvů,VS/ebs7y/1ȱ HȱȥixMjs8s^)r29#t-ZA([(nݡ?wm3R%t-.$[d[Ȁ lt m_o6ic]ӰLɻr$=O%|i~=GESmutܪqFXBVG=4/6h|nAsω 4Y4EPJ wpN- pc28> 3f?&CҐ15M'[.MBiL4cSr%dwXŋɳNixQ[KHi{\(JÄw%[+͟bt=#:3ҤO:*!zۜJȻ0M-!yaҸ/LǮtgѩa1t&g<%q~,; +s[/L" =?MSDoKE#rR:zD2^##1My\<$d`҇lwg>$>fiCR^L c="v2:yw)<"Y(*"G]`zmVBlz[>!0qrCN4}JvO # Ťa2v1) yR'4L=,ݐ OIفL,xp3tr,uJ]aIȝ]D(3a▉3oz30wǾ tM@yz0eIHh5te z1X<1>u=!T~| @PLD}30~a1铁2A dz{ iwgD0=#Xpt  #ґ9&KGyNZísrH<'Ӑs@ng$1 'l%;~2CSQׯ?%2J=!/FQ i37+>&#"XHE"2ALTr.p\wN?σko ʛ_7~ C}|izWtҜxdu}9cx'rt9my/sjqe0RP%Auմ\׻W/>Cux7ψR-&=NuÔɺ,NFdEGb|? QdɼK"iw$bƢK?U}=:nWP*{T$ BEj⼨ N 03+vw&*]bkwwww?+쳿y̽=9iWuBSth=C:褡Aڰ9CC´C<moݿ+ NAhu<׽B;.{5@ͫAT > \ j4WK[8F  ~jnB @|. Fofdu08~do V&x&]<޹Pv<< LHA!߈LXOe4 a]e\#pv̀pW2,τ czg0 2dyN΄6x8;N_qUٰ\CjQ3uUnuan4utnU;3w&kVwt˩tөKuC#u jDMѨ:5煺Tn&CWN+.2hW9T}. z][jΈ{ t([M/O~iXbcXpEar/!Gxh0V8M`9 6; ALDhgBW&@J΄Mc&6=ٙ04 dnj&P@0˳]i[2 dW/n }ݖG~#L}kIK׽{'Y;V:ozΟ_DW6(: 9m clHj~k+x~V ɗBlYZ_7 `hl0j"Z60G/5Py%}`Ve&tL&l5.7E7Ꝕg NT{ս=.!ehE>FBJ6191$jF t^o}'11tc7eG'BJ*Bqop^B/))#}`@Y<4/D &'{ oʼ=˷35} uxfbT̻QQAYbQ)ꁒ *p0f'Q($LN&$H0d|"+&DBj8ڐ0h +A:hF-&ȽJ3"tTA~N. UTߊ [UBCaޘƐAϛ `TM_TNUFI` dEaMdu - 6`q2GP8S' 3RAsd}O SAwL gho0H AfRR`$%&So?%<@Z[%>L"x %`=y*\2+Dd^L2\PqnHބSI2%JKqe"\tlPT8(AcCD8DM #NDDHAYBgL߹h(6a߬de"}6ak@EG"Q/uHb5v9QcVd.rЬhΉl5bMgq Eqi\,M;q^<Sz2Kl%QلRM8T F)&hOjzxzxzx~&fkr EjaMXt~pC|Hm!>~+: 1uhzJ=_zhz(hTML)-Ymd,cy ;m7ׅ d8 <ፋ Zy]*>Px&)G,A$u$h% ЉhD2llݒ r'_URO8:] 4M#vD $DP ՚i36])ۚ}5oٞ4(JO8FrwؙN0 j%.@ݖ K.fb:QAˈtz ⃒!^;_&7RO!&G4{f;'O8ICknTCo<ЖO9 nwKgA r8d.%Fopel:̫rncAQ;+.49.(N].2`mg+W;Ó >L3 38e@_3{9C8v_w>.'XAM<2N0^:-c ӡ,':tHp=q'`uL>ȍa3؞,gpe3pں@w0< \ b؛ j KY"k T=#䇝a.8ĤQ:p{)0*,rW?AmK̽'c*,Z$A*N8Gۑ }z:B&is`jF;£~i3"SG8k!{o*]psRA4p :B, 6$z q 8CcB*t lS!0TcS>g­ ΐr(⊝oΐ.Hmmڼ4xRңi`uWi#q[t(#:ħNM1MtR1^pB3 &eeY'8?ʜ qc2`' $MAixgH=G݆ dǧd@!kE\Dyw]`tʪA =2ӡW+Lzr]4ts|Ͻ[4|F곽'AwKړ<=ʋK֮i&k'h3y+Ѽ-W%ʵyZow"wwv?Wjwqv/8I{k}%hysxs伥9)9#ysf,E,uYɳYk3w'{D@x^u6W+϶Udnݛ{>{Ikq9\E;0Ǎ;/Nj&'wKy9ܸnD3k3k<.A9Y;M6,kӋc$͋vv^ϩZj's}CLm7^ۏ;ӹڱJL*ܻ ܧxOwG;4o1/GkƗhZG~ka#N+~}:QMbju|wMyU&=T0b<ĝu=Jv)@c` X~j絇73a3^ky7Nk yN蒸S9Z;?G-,na_֞b< rAj0W:iϤ$GEۀtPV؁Ǒ H0 ěd;Ʉ {_]+55j~5/Ӡrj~~?^GFW~cNҎ ZS6݈{k>Cs-YsX 7_CڀIHYC|Rǁ`#E32Ȁm-{8T[-U3-&Lj Ӓ3%Y -!ygpDE45 Bn[Bچ,ve٫V0r4f +xf905Z5j5xѬa67[B話3Ԡ8fYjylj02m +׾-dr:.fA-xςФlSd l qUY0cj[gEm!%? ©r`80ԷU,f Y, LZ07iKdF:0䞍ۙ7_#7I̴˟|[ȼg^ѕ21Ov0101:- 73k'#?Dq~S|].sN\d.uay2u͙iL1t"u6LC6y_ۗ9𶈬Ƣ{3M]{7 eOÕ+Kߺ5u1С<{ =Rt:v(Cc0JZ3 譀  .$UHcVx̪@qපh RYw92[P)C0=TweJ):; &)F,5 .o.BbؐzÆSW O 6TQLyQai%H{cY,ERц Yehe,vl Uޝ2;7fr_!UNt.̩)E.8QRϷ-_Y?]K!6ۓ˩׉AakIOEN|F&'v&SN%p( єHR'P(WPv?%?F_B?<#^N9DK'( ʉ d}2q|V|,Nf$ %!$!G% OL0O0OxM&$"K\GE#U6r7hycć1ޜ 旣|gRXaub:ۖwT w_>Ve|ؓWJ"*T6}_Y `IEZ1[O y) %U詽FB(LUDOUf~Z(:!_06V AѼ5Kš_+J(HM-m#̗O/Gi`֤MpuVZr΍PV>8"l>Ez0BN~|pM)AiY|06(Aqb>}>X/B!%=5 "B&~E!/]k !P}z!jQ"@JrPX 9QnANbXT,c~'b4,7 +"Խ)Nczu(2TLf)~)EPNi 25A;A!]V Tb$v…Eh1v(B}ߤu F+FS<(Sqɉ%yg$qRtPO,+C;f ĵ°r/G"ؠ@mDvq$Y%b+;!PyUwYջPBN\4QK:MpqT#@ͫQx\sV>=pz5J7ãUUW.J$ǃIJ$-Wq')ߑ*ɓ@XLZ9|MuCeH饲hT](CUQQ* ej*e_uOVyl۩(ޯGp*i-Uz)oP'N\AY8R&R[S%ީWXb:Fn7' i5hFl+A=nzQi(M*C7ɽM GWO%P5:P .U(hA$p:VIƸcOqM=]%wJHI9t427wNr7+i;jwrO~>uCۤ2%L~w*>9/ŋԘ}Z}t_{h7x-mnנM`̺ =]Yf36t{2߄Nބ,`fQ6@Esd m7l xok7!W؈:P0kq!R Q됫5"K5aSg bQjkPnn)Qt9 >jU$`z- BvX"sZAHM^,4Sjћ60;y52]fFW赭 Y:߶֠5Ǭ5hfk8k`5=9]_:t5 n( p6 6c}Hh-oD[Qp&l|=فѹh/v/v`E߈aϷR/^2uסgObjodg?X~#~CG(OvO:{}̧{Ed1|Xln"o(#EqDiy˻Ud{0Hwt${hwE. 2uCYR,',K6,+"ݽ"ޣ#ޙ#yK#y#xFL2rB{},Y|(X5>Y|Vc]ӂ]Cabjc>].j,oaڬ^͵)&\vكQ2dPtEN^4wjt{g{ BLA脢MFh=Y\SKhaXֳuWУ(1 ]T;xr$n*Gv (}{m~0>צİד GC9)8Ro Ǹ}e)ح)[UlC|La)af$f`7.4ob J;F"T-h(s Tȫ3u(@VӢ\ 3oSRL\`krtwqvB \U* \ARݸاC\@SP\2\`R: VfhXg :AoMq%hcg835uiy1:-=]gor#ۅK 30^[n;CcV!=)DN4gX][:CBg\W9,=X^p^!禐K]"xJBI<:i/4#H41ke$11 */\B[CW#\Fq˅ll<N^#WWf&HyKII9(D7Dԁ7dțK- }x?17?0_0n11N:s=\[81 F__vȕhX||9]Yw󑦳;W+= }Z޹Ac> }ym 7Y1ߕtwEЁxZ%Z 6Ov̙Ʊe]oO%eROHRt&^^|M(o*ԥ '$S T(peo!u 6"2d*Bx2X*F`T]^ i1"ЧK B@_+FN{AzZ/V$l/he \7 Q/yz &7$c#"D-Dg<0ȻF٣Ю,"+R"]$BKb4= oP\&AyEē SH2,,Ddx[ަA&.@Ka몿0ߥֹ^Z[d C>6HM!! $$.&%$_qkrc1SԕP8D,D;I=_"zK+zC*=&]!Y\+HQNb>IܔToLJ0t*kF3P~@KP|T Z/A|Aݾw Zn8Kа ?86i :ZMqKQ|?rz)zS%}`r+t9jB|DnG+B d/<Bh(/D\f:+Z^Wq`=Y2M h*Y >~ꎕ\ր/vY=|aJ[?GV| m ^V b\QGy PF{V a(7!xoh{!~棦MG4>|v/T_}v9Zv.G8]^5\Xq?LZ4?i ݿ MKQ\/\|HRs/{-EM.dRtD -/{B6,hE wo{^{[#`#y!b%=I^%1^E~^$ӼJʼJy4"x%LBI 1G2,NHJ3%EqeS͒D}r=tZ3I+!%1&!=bb{nd#d5iT)FT!t*ADWE+j1#k >T?XOq^FocJ%MW 5S:Bxr4*"/G|f؟LY;b_n(qvLės]t=]?U̺)l o~^xxw]%W'ukkboUV6Z{w ~!'?Ik 0LAP?h:?OXρ7PMѹut,O?*Ώ ?(1N)ͩ pOFj-OsgD iShsi R}m-6%zк\hiϨO[שpI}Bu6] kO+AEK [Fvq+XIhah2i¢hw͌ڕ@S}iTZ%C;MMYЊh;֑΢ѹZ5;^ЭioTF+c5!0 =ðua,{wدN YQd$t5mQ>;7ZJYZxC%ĐnHoB ? Bnr"+ bP80b\qa Be 1V1,cL gG!ERώxqf0ڄ2B ƌ7tvC46=3T_?=~)1Ocq4T~= }!;CҳC !BFӅ!)tf iOO 1 yC 5١Qd19F j]n!Cc]%][G0c@ĠI upo%&Bw˶5\ b dP©`f܊tVA_csVP6Ǹ Pnd )q Wv;){ :Gpajc] ᛻_;[]0b9к(pMZ95ֵېQX.(d~elj%[w^mnBK|W768=iwl6iL<{ޭ U8QCWFxA_q=4|6z#b?SHghV9&cjhQL@ gк0 4"ՖyjK}z>5buyȈ}";'pLDׇ"SgEE4mhM;Lљ(O{E3dN2̘7hFL:)?ȦFO_QBQIOGccG+%`lE]>OΙ,0ҋя9g=d#{zУYohm";董hX :Vɯ +1N8ֿӆnBSZ:M>G>M[>A[U[}-5ǔαPz Gѳ8|mQwBC(2'֧>>\~s$Zϟ+* E51s7q~7X/0ǹfތoMan [a`8LevՂ? çCXF8?,. * _!jSt Q<[;Ht-EDLQ"J1QWQ(2CB*'a G#+a1z,8NAS: ׻>oB…(S8  aRumFEw\+䋤P! Eg!Od( ghD$0>|0!|P-.R]M c ,#ASpw8p M JܿQu{őѿVl[_:X|7|xj2C"qdb};v+~M\J|GǕ8{q׷&c?/^V5ۓeY)dXiaìٲ3=Y ̊@ցM3>l+y?| ^ *vKN,*{e9쑲 ~%8vLȶueH)R{Aikv%{{Ԓ&ubK>0)MJvs4m.=n)}Ŷs4]*DK5t4gt:@:W:sFp>ƾlO۔-GڃS" Ls~ְl͔esq;FΖFGJ%R9@ڗQ>+-bα}eo'Nɓys8ղN=Tޒ._`Gȷ y[*%ds |;D^Ⱥ-+Z%)#â}-6M׹׹;C1VLRe78r|^l0Hv5z(Φn09 &-ׯysx/dx'eNDY)2D) QJLpC.)(0()6(b1c`zJwM1S!t ?^›g n;-ZΗYtbOX[۠pQkUŊl ~HRp^n!7L7dE.|l~o 'ȍQ|/Z>/0~c%cbypm1}GEa\JEItX!*W^SE-E_T8*Eh(:0Q>P,^ST *6 9.$s[װ9nf5& 91~1v1BØL,"VxA!P݄{]; }pTD1T0o>LT|ҁC9GX,\ \8,\.\x)\0TX)E?)E) PA㼛89z'4{/1E :GW="[#P)EQ(cFIcǼcvLbmbc[ֳٝGml,'鏃"F3(FÏ=Ώ}m7 %./MK<$M,M)ON\/OO,L4Uԇ9C,_oq 4c}qƜ\ʔJ2{$&gӷJ~&d8U>)Z1')SN%S%+N*(ԪZ)j$u >6qrT>W&3W, PɒT I*RŔVuըeIh$)A4@6.iGX۵/^-\杴Xf4[f4IP5Vv\5^N5Ajlj,QU*㨶ʂU'd^2UcVn򕛫ɛxVRNV3TL RU UrUBaP$I@Ř$7/IfǸo%hk-uckuۉ6 S5p#Mߟߖ|H>3 PBKz(~_ (@p$@kF4 8HvWSu??+"kOU?Ep~h!C@: N5 @! Әk^kpi4k5U94#&s.T?)1QߛWuZWu[1տl?b4߉%v#1o֣?b1o3}#}_bGL?ȅ15_bG|:>+6=#s_b#ܗmߊefWϸZݟ!ӗGbċ?b|X-]g#_q*8_?b#|c|{c_Ǿ_bǞP|R+5nAx7m]=6eDFʁӈq:2E[M!\Zu T:uZ Azpz*(mF޿z-&8"5jfn/ `A0‹E\Y"#MؿF'`Шn|= E0"4gBlX<"\\ &P&/B%7Ѿ=Qk((b5B}ƈ CB q}Ӽ/pQ=Oe*sz%|n,m:{+LD襗68Hu:Jhfge{tJl*D$ 0/򚿹ysJ;m(/޵oS}NEu8sO CZ|A>pJr~3Q-EP6b6h /ODp:b4  %,0-6]By棠5Lnn[!8o\t7Xc i`whhz(zAp/zžlx 9OIJ8t 6?{_DeR ͞쎟A緇E;ѿZAq搕4e6.oy6\g #+~ށFj5nE-iu68-P^dK\BC{-La٦༖F_\ma: J_L@A'}iEL6y+(7zZNׯiȎ$ k<݇QU{WЖVZ8?>tȿq}M}_y}Ckcu| f]wM*#ߠFQJ)եn^, xe,O #{F /$ j ӐZRj^3v7PJhӡHh֪ [+gP0zlW췢ثo~.3"lC0q#4q!5uRၓ2 9fN=$P]w4G !1ީ7N.G.di7q:05B]!q6ۉdžǑ6s܈`rst&hFM X6 ֺ΃1 .PIfUt+?XEn3Wt)fTp/pxՏA!6sB moG'*)#[o }ԭ.Uۇ}zDK0X;;yKV~y oaM fE=#= jFό;vɅh1XaӰ&`*3!N`jc9VG8"Ai("nEAg /,1'-ִʾ!O})! eJH"Q ݭz>r{'}2a2EW)Y \bUWKzV3,`_-6&Nٳ[Aߝk 5TNlm+nun1t p^'(}<:Cǃv&:n |g\2]砀n U:l)z 6E-i_4/ ' 834p[?"5dg(*J|ígui]{Zuye!޺u8X؂;j=¹Ne- ?k+gÚ4W؄ Rm>hp-ca㉵k7h5SjP jU1 jϋ[&Cj@tvԞkז纆 ,o7Y~l=ӧuMs] _>Wvv=ljwiSi/-uwiV[8w AkÅk]ֆ4 0w<&|ܾb|pfMyNEz~wlbjD"߱YK͘|-_{MB%#6 Y><{%;m6̪r0YNyyA༠.fvҥ[%/xo܀d;Ns~7~_~; @؏;jtU4F0KtC6ur. .dOWM``.nvυfo"nw <@݃l"Ҧm:;@8_7qz[Wv PZ$[Ab @ }ONzu-7)`eFZ,2?ߗz'7q*"qwU=A^]!"V.k=AhvybN"AVu-{j#A#GPn+=rE{ x ?kL:\ȪW.AA#F'DQd\&:c 3LܙĨјϨ=2;u }{::ut4|//z;}GG £#Y?c3xd}W3 /47k^pgT\ Ǚ݇g=px6 qƉ )|?I½gOkv۩Oiw(N [yƎUօ$iژL k=?-Ͳm&LgDmkg{i)N AXM D9t#ɸQa[7"¾h,2S6ks2*{=*?*w]S$O D2Ϻ)ge'{jxZ;,Ң\ iZy=ky55;Ԣ G+g9|3٫Eol?֢9LGC4a)NW;Q/ʚz\ 2m_} D׬@2r]Z3/]شUyD&WMչ޼/C7|Gw6\K_FeIp7bKM#ݭEm ܠ/tn 9w}G)w  &e-{ϩ5Lڂ+l[ӧm J;ֶHmt{Mm۴\sI_2VF96a$X ڰ.vbϚ6ʚQg;ZI-bm.t-Sڗ7lP_Ζ3U_:X_K/EO$YǦ܀AA۳Fέpy1 FC`SC>MO\[CXcۂض)tv+mֶ]`6؈pCwj\y#~Q a`0*`Kf%0P4_ˢEl9GV$$A]JUqJޖ@ԥ` GIyҁ7r%'gq6)mڣR}^9c!w BA4zd9.oϝanۻT DX8EN+G rc'N۞SKӷXNOKㇸvˠc cN9,* V"h>ͶBMlClɸC }yX+~ BǂN`ܜoK a8͖m9ncLs]B-4=osO APTHѿhD)U/[)_۬)vScQxf迄I{Ѭ1l ,uI%x̫+a?K A =W<{JaO4;d~R/ڹN^Ĩe`?nc^Y2祈TAej;Oz\.{I񶃙 <\AfO9[AIyl0ixg?lGE[TL7*0=3??2́/w5}JάΪpYHJ緛0މ, &oռ mHU_\vqL3ר8t95vSCYњ,QżY @fdBȸ@Iѕwf /=m܀ DXƃZeIKb BB?<*;^(M͛-gx~Z 9/nRxujUqH-{AβS@W+a}z9> sw(ϑ:0 d1Ͼ9TRn6kêWϝt]j Iw<ɗƪ6HU7[[ӀpƷLJwj5" C߉%3or1״V\ }iCjo2al6{?> E {$33E۳b1(Xg 9<{f;R\z>깧ygO_3{W9.6vqoNk!i[3{Ϥ wj~Oy<őAa/>G vx|Υn9'$|ɡՐ]9ʩ} OKY[Wnm^zK3D>ϥ筠n~>KTRfŴ%3~,K/bҝK&kOSNmiOp;lAMܵOwAyD|'ՌMyjnJɱ69@jH”+L392+t-o0#l36W4J#3퀶V$ …p@Y&j+hgq)%"pxn/g?UmGBYnTXO ۞#d26rq)p pzVsу{Cܽ Au^ٝCoH <$hT+~ӱTzf8.\E1*؜YYu mI}1AQv^lammm sk}*VSA!/t9pErjOXC^װIZdEѦ8t#<797ψDao hj_hO繟6QV"w\=+@=<W0#|jaURĩprWyĦTzy}΀'EjIa&uM1 ZuǕl9Ys=w 3 ty@ Rῢ.K{W?:_(r1hc/:cL3&yd,S6o |k%F䫸ܣ;sgf}̇֒}Y=Ø癅+buOŴ _K:1~1$;Y8Ҿ$4'tZ mUx4bݠ$t=im"su'dy<?1A]0BH H%Ve־$wpdDx g乸}4Sh3[,y>bL=bF1V̏WC& WIR,78ϑ U~R26땚.^2߅$T8qWjTj떪tV?֖PP8x[ w! )ӗ'bϓ MT$$If!v h5>5h5h5h5h5h5h5h5 h#v>#v h:V l44n t06)v ,5 f4kd@c $$Ifl44n : rB!#&         t06$$$$44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdf $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdi $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdl $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdn $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdq $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdt $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdw $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdz $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd} $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd€ $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd| $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdr $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdh $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd^ $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdT $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kdJ $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd@ $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd6 $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd, $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd" $$Ifl4 : rB!#& t06((((44 laf4$$If!v h55M 5h5h5h5h5h5h5 h5 h#v#vM #v h:V l4 t065 f4#kd $$Ifl4 : rB!#& t06((((44 laf4$$If!vh5?5?#v?:V l4 t065 $$If!vh5<55B5#v<#v#vB#v:V l4 t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5$$If!vh5<55B5#v<#v#vB#v:V l t065&55)5DyK yK 8http://www.dlm-network.org/DyK yK 8http://www.dlm-network.org/DyK yK bhttp://ec.europa.eu/transparency/archival_policyDyK yK jhttp://www.interpares.org/ip2/ip2_terminology_db.cfm@`@ fNormalCJ_HaJmH sH tH Z@Z ^ Heading 1$<@&5CJ KH OJQJ\^JaJ \@\ ^ Heading 2$<@& 56CJOJQJ\]^JaJ@ ^!Heading 3,MoReq2 Metadata Element$<@&5CJOJQJ\^JaJJ@J D Heading 4$<@&5CJ\aJN@N D Heading 5 <@&56CJ\]aJH@H D Heading 6 <@&5CJ\aJ:@: D Heading 7 <@&@@@ D Heading 8 <@&6]N @N D Heading 9 <@&CJOJQJ^JaJDA`D fDefault Paragraph FontRi@R  Table Normal4 l4a (k`(fNo List ODSC Z Document TitleS^S`35B*CJ0OJPJQJ_HmHnHphsH tH u8@8 DHeader,h  !4 @4 DFooter  !ODSC Main Section HeadingS^S`35B*CJ0OJPJQJ_HmHnHphsH tH u^O2^ D SC Body Text $a$ CJOJQJ_HaJmH sH tH jCj D Table Grid7:V0lORl DSC Table Text (11pt) xx CJOJQJ_HaJmH sH tH hObh DSC Table Text (10pt) <<OJQJ_HaJmH sH tH |Or| DSC Body List Dot 1$ & Fa$)B*CJOJQJ_HaJmH phsH tH `O` [ppSC Body List Dot 2xCJOJQJ_HmH sH tH rOr DSC Body List Num  & F)B*CJOJQJ_HaJmH phsH tH .)@. D Page NumberO DSC Body CommentJh$d%d&d'dNOPQ0B*CJOJQJ\^J_HaJmH phsH tH `@`DTOC 1" # 7xx^7`;CJOJQJmHnHub@b OTOC 2% T# T<<^T`CJOJQJmHnHu>U@>  Hyperlink>*B*OJQJphO2D!SC UN-NUMBERED Heading 1 (No ToC)$&d P 65;B*CJOJQJ_HaJmHnHphsH tH uO2 DSC Title Text (Figure or Table) $xa$,5B*CJOJQJ_HaJmH phsH tH |O| DSC Table List Dot 1 (11pt)! & F<<CJOJQJ_HmH sH tH vO"v DSC Table List Dot1 (10pt)" & F<<OJQJ_HmH sH tH <m1<D1 / 1.1 / 1.1.1# F 0lA0D 1 / a / i$ F @nQ@DArticle / Section% F DT@bD D Block Text&x]^2B@r2 D Body Text'x<P@< D Body Text 2 (dx>Q@> D Body Text 3)xCJaJPM@qP DBody Text First Indent *`HC@H DBody Text Indent+x^TN@T DBody Text First Indent 2 ,`RR@R DBody Text Indent 2-dx^TS@T DBody Text Indent 3.x^CJaJ2?@2 DClosing /^$L@$ DDate0<[@< DE-mail Signature1.X@!. DEmphasis6]h$@2h DEnvelope Address!3@ &+D/^@ OJQJ^JN%@BN DEnvelope Return4CJOJQJ^JaJFV@QF DFollowedHyperlink >*B* ph0_@a0 D HTML Acronym:`@r: D HTML Address76]0a@0 D HTML Cite6]>b@> D HTML CodeCJOJ QJ ^J aJ<c@< DHTML Definition6]Fd@F D HTML KeyboardCJOJ QJ ^J aJRe@R DHTML Preformatted<CJOJ QJ ^J aJ:f@: D HTML Sample OJ QJ ^J Jg@J DHTML TypewriterCJOJ QJ ^J aJ8h@8 D HTML Variable6].(@. D Line Number4/@4 DListA^`82@"8 DList 2B6^6`83@28 DList 3CQ^Q`84@B8 DList 4Dl^l`85@R8 DList 5E^`:0@b: D List Bullet F & F>6@r> D List Bullet 2 G & F>7@> D List Bullet 3 H & F>8@> D List Bullet 4 I & F>9@> D List Bullet 5 J & FBD@B D List ContinueKx^FE@F DList Continue 2L6x^6FF@F DList Continue 3MQx^QFG@F DList Continue 4Nlx^lFH@F DList Continue 5Ox^:1@: D List Number P & F>:@> D List Number 2 Q & F>;@"> D List Number 3 R & F><@2> D List Number 4 S & F >=@B> D List Number 5 T & F I@R DMessage HeadergUn$d%d&d'd-DM NOPQ^n` OJQJ^J4^@b4 D Normal (Web)V>@r> D Normal Indent W^4O@4 D Note HeadingXDZ@D D Plain TextYCJOJ QJ ^J aJ0K@0 D SalutationZ6@@6 D Signature [^*W@* DStrong5\FJ@F DSubtitle]$<@&a$ OJQJ^J DTable 3D effects 1m:V^j#j#j#j#j.j.j.j. ^55\5B* \`J phB* `J ph66 DTable 3D effects 2:V_j.@j#j9jj 4_5\5\tt DTable 3D effects 3:V`j.@j j j#j9jj44`:B*`Jph B*`Jph5\5\brb DTable Classic 1:Va0  j#j#j#jj a9B*`Jph6]5\56\]s# DTable Classic 2#:Vb0  j% j#j0 jjj%  b:5\B*`JphB* `J ph5\Tt3T DTable Classic 3:Vc0    jj0  j0  cQB* ph5B*\`JphB* `J ph56B*\]`JphuC DTable Classic 4:Vd0  jj0 j0 jj dX5\B* `J ph56B*\]`JphB* `J ph5\RvSR DTable Colorful 1:Ve0    j% j% jj%  e<B*ph56\]56\]56\]TwcT DTable Colorful 2:Vf0 j% jj0  j f@56\]56B*\]`Jph56\]4xs4 DTable Colorful 3:Vg0j;$ j0 j%  g5B*\`Jphy DTable Columns 1 :Vh0    j j jjjj#jj4hl5\B*`Jph B*`Jph5\5\5\5\5\5\z DTable Columns 2:Vij j jjjj% jj4i5\B*`Jph B*`Jph5\5B*\`Jph5\B*`Jph5\5\{ DTable Columns 3:Vj0j j jjj#j% j4jh5\B*`Jph B*`Jph5\5\5\B*`Jph5\| DTable Columns 4:Vkj j jjj% 4kLB*`Jph B*`Jph5\5\B*`Jph`}` DTable Columns 5:Vl0    j jjj#j#4lVB*`Jph B*`Jph5\5\5\56\]00 DTable Contemporary:Vm0j%@ j% j% 4m<@B*`JphB*`Jph5B*\`Jph D Table Elegant_:Vn0j n;B*`Jph~ D Table Grid 1z:Vo0jj o6]6] D Table Grid 2:Vp0jjj#j p,5\5\5\5\ D Table Grid 3:Vq0  jjj0  q5\5\>#> D Table Grid 4:Vr0  jj0 j0  rB5B*\`Jph5B*\`JphB*`Jph3 D Table Grid 5:Vs0    jjj# j s5\5\$C$ D Table Grid 6:Vt0    jj#j#j t(5\B*`Jph5\JSJ D Table Grid 7:Vu0    jjj#j# j u25\5\5\5\5\ c  D Table Grid 8:Vv0jjj%  vH5B*\`Jph5B*\`Jph5B*\`Jphvsv D Table List 1:Vw0  j%@ jj#j0 j4wM@B*`JphB*`Jph56B* \]`J ph5\pp D Table List 2:Vx0 j%@ jj#j0 j4xG@B*`JphB*`Jph5B*\`Jph5\ D Table List 3:Vy0  j# j# j y05B* \`J ph6B* ]`J ph D Table List 4w:Vz0    j0   z5B*\`Jph D Table List 5:V{0jj#  {5\5\ D Table List 6:V|0j%@ j# j#  4|5\5\ D Table List 7:V}0  j%@ j% jjj# j0  4}>@B*`Jph5\5\5\5\ D Table List 8:V~0j%@ j% jjj#j0 4~D@B*`Jph5\5\5\56\] DTable Professionall:V0j%  5B*\`Jpho DTable Simple 1:V0  j#j# rpr DTable Simple 2:Vj#j# j#j# j#j#O5\5\5B*\`Jph5\5\5\q# DTable Simple 3l:V0    j%  5B*\`Jphp3p DTable Subtle 1 :Vj0@ j# j# j0  j. jj45\5\pCp DTable Subtle 2:V0j0  j0  j# j# jj5\5\lSl D Table Theme7:V0c D Table Web 1h:V03j B*`Jphs D Table Web 2h:V03j B*`Jph D Table Web 3h:V03j B*`JphV>@V DTitle$<@&a$5CJ KHOJQJ\^JaJ O ^ SC Heading 1%$ & Fx&d P +;B*CJKHOJQJ\^JaJphtH ~O!~^ SC Heading 2" & F-DM *6;B*CJOJQJmHnHphtH uVO1V ^ SC Heading 3 hB*CJOJQJphtH NO1N D SC Imagesr&`#$/ B*phxOxDSC Z-Address Block75B*CJOJQJ^J_HaJmHnHphsH tH uO2D!SC UN-NUMBERED Heading 2 (No ToC)@5;B*CJOJQJ\]^J_HaJmHnHphsH tH uO D SC Z-Footer#$ (#^`a$-B*CJOJQJ^J_HaJmH phsH tH T@ T D Balloon Text CJOJQJ^JaJmH sH tH D"@D DCaption5CJ\aJmH sH tH H@2 H D Comment TextCJaJmH sH tH @j@1 2 @ DComment Subject5\fY@R f D Document Map-D M CJOJQJ^JaJmH sH tH O1b DSC Highlighted CommentNh$d%d&d'dNOPQ5B*CJphO12DSC Un-numbered Heading$&d P "5;B*OJQJmHnHphufO12f DSC Figure or Table Title$a$5B*mH phsH lO lDSC Fax Heading35B*CJ,OJPJQJ_HmHnHphsH tH uH+@ H D Endnote TextCJaJmH sH tH |O |DSC Z Document Title Char35B*CJ0OJPJQJ_HmHnHphsH tH uO DSC Z Document Title 2$hdo&`#$/]^h75B*CJ(OJPJQJ_HaJ(mHnHphsH tH uHO HDSC Z Document SubtitleNO NDSC Z Document Subtitle CharTO TDSC Z Document Title 2 CharCJ(aJ(J@ J D Footnote TextCJaJmH sH tH F @F DIndex 1^` mH sH tH F @F DIndex 2^` mH sH tH F @F DIndex 3^` mH sH tH F @F DIndex 4^` mH sH tH F@F DIndex 5^` mH sH tH F@F DIndex 6^` mH sH tH F@F DIndex 7^` mH sH tH F@F DIndex 8^` mH sH tH F@F DIndex 9p^p` mH sH tH T!@ T D Index Heading5OJQJ\^JmH sH tH l-@ l D Macro Text"  ` @ OJ QJ ^J _HmH sH tH `,@` DTable of Authorities^` mH sH tH H#@H DTable of Figures mH sH tH T.@T D TOA Headingx5OJQJ\^JmH sH tH B@B DTOC 3 % ^ mH sH tH \@\TOC 4 $ ^&5CJOJQJaJmHnHsH tH uZ@ZTOC 5 $ ^#CJOJQJaJmHnHsH tH u:@: DTOC 6 ^ mH sH tH :@: DTOC 7 ^ mH sH tH :@: DTOC 8 ^ mH sH tH :@: DTOC 9 ^ mH sH tH B'@a B DComment ReferenceCJaJ\Oq \ D Char Char056CJOJQJ\]^J_HaJmH sH tH pO p DText for Tables d<<5$7$8$9DH$CJOJQJaJmH sH bO b DDefault 7$8$H$-B*CJOJ QJ ^J _HaJmH phsH tH TO T D Table Text$<<a$B*aJmH phsH nO n DTable text Bulleted" hh<<^h` aJmH sH tO t DIntro8 E#8d5$7$8$9DH$^8`CJOJQJaJmH sH :O : DLogoPC$ E#ha$\O \ D Main Heading $$ E#8h*$1$ 5:CJ4O 4 DPrompts E#8ZO Z DStandard<x^`B*aJmH phsH nO n D Dot 1 Red)$ & Fdx5$7$8$9DH$a$CJOJQJaJmH sH ^O" ^ D Annexe Text$v<x^va$B*aJmH phsH rO2 r DRequirement Bulleted$ & F<(a$B*aJhmH phsH POB P DText$<x^a$B*aJmH phsH DOR D DBullet & FOJQJaJmH sH TOA b T DIllustrative table^CJbOr b D Text Bulleted$ & F<xa$B*aJmH phsH lOa l DMoReq Annex subheading $xCJOJQJ\aJmH sH hO!B h DMoReq Heading 2$ x6CJ\]aJmH sH ^OA ^ DDot 1# & Fd5$7$8$9DH$B*CJOJQJph^OA ^ DDot 2# & Fd5$7$8$9DH$B*CJOJQJphnOA n D Text Indent 1$@d5$7$8$9DH$^@B*CJOJQJph>O > D Text Indent 2 8^86O 6 D Dot 1 Num & F6O 6 D Dot 2 Red & FxOA  x D Reference6d& #$+D./5$7$8$9DH$^B*CJOJQJph:O  : D Dot Table 1 & F>O " > D Dot Table Red & FO12 D!Style Heading 3 + 18 pt Underline%$dx*$1$5$7$8$9DH$>*CJ$OJQJaJmH sH O1B DMoreq2 Element Name($dx*$1$5$7$8$9D@&H$"CJOJQJ\aJmHnHsH uO!R DMoreq2 Metadata Group($dx*$1$5$7$8$9D@&H$6CJ\]aJmH sH XOb X Dmoreq2elementnamedd[$\$ mH sH tH POr P D textfortablesdd[$\$ mH sH tH VOV ^MR1$ & F!&d P ;B*CJOJQJphBO!B ^MR2 & F!6B*OJQJ]ph>O1 > ^MR3 & F!CJOJQJ\aJ6O1 6 D MR Comment6]HO H ^ MR Testable $a$ CJOJQJ\O \ DMR Requirement CJOJQJ_HaJmH sH tH HOQ H DSC Z-Letterheading *O1 * DMR textJOqJ DMR Text With Bullet & F TOT DMR Comment with Numbering6]@O1"@ DMR Text Heading5\jO2j ^MR Text With 2nd Bullet & FxCJOJQJaJtH HO BH DMR Annex Heading 1 & FRO!RR rMR Glossary Term$B*OJQJph`Ob` DMR Text in table with BulletxCJaJZOqZ DSC Body Text Char CJOJQJ_HaJmH sH tH 0Or0 D MR text CharhOh gMR Table Headingx'5CJOJQJ^J_HaJmH sH tH HO H DMR Annex Heading 2 & FHO H DMR Text in tablexCJaJnOn ^MR Annex Heading 3$<@&5B*CJOJQJ\^Jph:OA :DMR Element NameHOH 1 3MR Annex Heading 46aJTOr T |B MR2 Char Char!B*OJQJ^JmH phsH tH :O: D MR3 Char CharCJaJVOV JMR Annex Heading 3 CharB*\aJphBO!B DMR Text in table CharnO2n ^MR Bold Heading$<@&&56B*CJOJQJ\^JaJphFOrAF $HMR Text Heading Char5\TOBQT rMR Glossary Term CharB*OJQJphpOap SC Body List Dot 1 Char)B*CJOJQJ_HaJmH phsH tH HObqH #5MR Text With Bullet Char<Or< ;"MR Comment Char6]:Or : DMR2 CharB*OJQJph^O^ M MR Annex Heading 2 UNNUMBEREDCJaJ@&@@ m-Footnote ReferenceH*HO H H MR Figure Caption$a$6:O: | MR9 TOC 2 mH sH uPOP |MR Annex Heading 3 for 9-8JOJ g) MR Header5B*OJQJ\phXO X g) MR Footer 1'$ #h^`a$DO D g) MR Footer 2$ #a$NO "N Q MR Footnote0<^`0OJQJbO2b 7mqRequirement note$<(a$6B*aJmH phsH ROABR UMMR Annex Heading not in TOC6B8<^/BZd\Db  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~\     $; !"#<n%o&p'q(r)s*t+u,v-w.x/y0z1{2|3}4~56789:=m>l?k@jAiBhCgDfEeFdGcHbIaJ`K_L^M]N\O[PZQYRXSWTVUUVTWSXRYQZP[O\N]M^L_K`JaIbHcGdFeEfDgChBiAj@k?l>m=n<o;p:q9r8s7t6u5v4w3x2y1z0{/|.}-~,+*)('&%$#"!        !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~+\;yD_`abcxyz{|}~   Gbcdef{|qV`: c J  s E T 'Jae0cacJecC\r5Q h 6!!*"""8###I$$%q%%L&&,'''m(()))s**V++++,Y,8..0W23[6h6s6\8)9;Z<<<!==B>>L??@@ABCvEFHHHFL{NPQS TITzTT UUUVuVVeWWWXX=ZlZ\:^'c f!ghhlJl|lllm#mno]oop9pppppppqqqqHrkrrNsAt?upuuLwBxzzzzz{{{|}jȁ8]ʄB`'E8HZFs؎ŐΑ'sْlC͖%/$J-3T_oԞ۟;Ms / JУ٣^ͥzЦ*ʫ׫5KqѬ?HS\jw#2ĹwD߻06[+rSMyT $,4AcP #+jlw" "#(%>p?@AF+-./dfghLMNOSUVW{}~-/01X Z [ \     t v w |         P R S X      cdej>@BCD+,-.hw<=>? XZ[`$4678    !!!"!'!!!!!X"Z"["\"U#V#W#\#####%%%%%''*'/'0'5'((( ({(}(~(())))))))\*^*_*`*1+2+3+8+++++,,,,j,,-N-y---... ...../// /////t0v0w0x01o2p2q2v2)3+3,3-3334444/50515655555S6T6U6Z666667777q8s8t8u8(9)9*9/99999|:~:::;;;;;;;;>>9??p@@ AAB9CECrCCC)DWDDDDDDD}EEEESFUFVF[F'G)G*G+GVHmInIoIpII3JJJJJKKKKcLdLeLjLLM?MAMBMGMMMMMNNNNNNNNOOO OcOeOfOkOOOOOPPPPPPPPvQxQyQzQQQQQ*R,R-R2RRRRRSSSS^S`SaSfSTTTTxTyTzTTwUyUzU{U/W0W1W6WWWWWWWWX[[+[0[1[6[[[[[\\\\[]]]^]_]]H^d^e^f^k^^^^^%__1`````3a4a5a:aaaaa!c"c#c$cc`dadbdgdOeQeReSe)f*f+f,fffff[g]g^g_gggggi+jjjjjjkkkkllllmmmm nn5ooooo;p=p>p?pppppqqqq(r)r*r+rrrrrsssst t!t&ttttt'u)u*u+uuuuu_vavbvgvvvvvwwwwSwwwPxQxRxWxxxxx4y5y6y;yygzz{!{"{#{{{{{||||^}_}`}e}}}}}~~~~tvw|z|}~#$%*ȃʃ˃Ѓnpqrk؋'ݐtՕݖ—Ǘȗ͗npqrޛ(X՝ם؝ٝ>?@AZ\]^͟Οϟԟhjkl)+,-   hjkl-./4yz{+-.3ڦۦܦvxyz ¨{}~ߩSUVWVWX]BCDIҭԭխڭ֮خٮڮstuzɰ=ɱNPQR8:;HY޶ϸw{Op#ֽ>7aοvwxy345: %678=acdiXZ[`&()*ACDIJLMRACDE F{NPQV_`afGY[\]wyz{9.DFGHdefgpqrslmns4Ha(*+0{}~npqrHJKPVXY^       !&245:}b ')*+RRSTY    K ~               U W X Y ~    5789mnoppIuT8~nopqI_um&P8 9 : ;         _!a!b!c!"""" ############a$c$d$i$% % %%%$&(&&&&&''''K(M(N(S((((((((())))))))*** ***** +/+H+I+J+O+,,,,v,w,x,},----...."/$/%/*/////1333333k4m4n4s41535455555556666 7k777 8888}8~8888888Z9\9]9b99999.:/:0:5:*;z;;;;;;<<<3===>?j@]AAAAAAABBBB8C9C:C?CCCCCDDDDE?E@EEEEE,F`FFFGG?G@GGGGGRHTHUHVHII I%II\JJJJKrKLLLLL'MnMM7NNNNNOOOOhPiPjPoPPPPPcQeQfQkQQQQQRRRRRSSSSSSS0T1T2T3TTTTTUUUUUUUUsVVhWjWkWpWXXXXXXXXYYYYZZZ"Z+ZOZyZ{Z|Z}Z[[[[\\\\\]4];]H]v]]{^}^~^^ ____^_`_a_b_________```````bb]ddggh%hilkpk}kkkkkll.m0m1m2mmmmmoooo p$p4p;pFpGpHpIppppppqq+qRqqqqr6rfrrrrrrrrrrrsssstttt uuuuuvvv vBvuvvvwvxvwwwx yyyyyyzzzz||||J}L}M}R}'~)~*~+~~~~~u-łƂǂ̂ƒÃăɃ!"#ۄ܄݄ބ   ‡LJ,./4*,-.‹ËȋmopqPRSXՐKLMRK{!#$%)*+0]^_`ٖږۖܖABCHjlmr_abg#%&'֠ :dfglϣѣңӣƤǤȤͤ789>opqvACDEVWX]'.4<GHIN+-./sNdefg@h&^=?@AnUVW\ ʻ̻ͻλN]^_dɾ˾̾ѾKMNO,./0_pVXYZ BM/$&',  `PQRW:UWXY "*IiHIJKbdef.^JLMN&'(-MOPQ,-.3 yiklm[pDHUZ[`RTUZm;_ p *.;@AFLMNSMp "#$$&'(z|}~~)*+0 &'(- # }                H I J O         U W X ]     U|*LNY57BP_ v9avz"*1<EMXZ[`    1!V!}!!!!!!!M"O"P"U"""""# # # ####$$$$$$$$$$$%b&f&&&&&'''''((((A(B(C(H(()))))))))t*v*w*******%+<+D+K+V+_+h+++++++N,P,Q,R,3-4-5-:---------....////h0j0k0l000001111"2$2%2&22223M45V7889::::::;;;;;;B<<<<<<<<<V=W=X=]=====e>g>h>i>V?W?X?]?????@@@@$A&A'A(A#B$B%B*BBBBB%C&C'C,CCCCCDDD#DDDDDFEHEIEJEEEEEbFFFFFFGGGGHHH)H.HwHyHzHHHHHH|I~IIIIIIIQJSJTJYJJJJJJKKKKKKLLLLMMMMOOOOPPPP9Q;Q?@E!SUV[ACDI:;<Aٔ4mÕĕɕ9hjkp=_abg@\^_d   "#(ě˛ћݛtbdej"ҠӠԠ٠].245:>@AFRTUZ;=>g4٫ެp` Reghi̴ʹδӴٵ۵ܵݵtɸչ׹عٹNOPU̼μϼԼWYZ[   ھ۾ܾDoÿ}:kmno#rtuvuvw|#<>?D$&',eghm1`2Xs4B)9~|i'%15BGHMiklqacde%&',W}oqrw;=>C.012  *,-2VXYZ*?Pmu"&389> \]^c`]fopOL s qrsx    M N O T  ( X     i                j m      %xz{ rstuAsuv{BCDIVXYZ2lnotz|}Mtvwx       !!!!T"U"V"["""""-#/#0#5#####*$,$-$.$$$$$%%%%%%%%&&&&m&n&o&t&&&&'O''''''''':);)<)A)))))$*&*'*0*+S-v.. //// 000!0"0'00000?1A1B1G1426272<222222222.3/3035333334444F5H5I5N55555 6 6 6 66666777"77708S8U8V8[8888899;9<9A99999:::$:::::::::?;A;B;G;~;;;;;;;;<<<<<<<< =|==>>>>`>a>b>g>>>>>????s@u@v@{@@@@AAA AAAAATBUBVB[BBBB,CfChCiCnCCCCCjEkElEqEF F!F&FFFFFGG G%GHHH HxHzH{H|HHHHHtIvIwIxIJJJ JJJJJKKKKKKKKLLLLLLLLgMhMiMnMMMMM^N`NaNfNNNNNNNNNORRR SQSSSTTUVVVVVVWWWWXXXXYYYYx[z[{[[\\\\\\\\\_]_^_____Y``aaaaaaaaSbUbVbWbccccWdddJee fufwfxfyfffffggggg h\h^h_hdh i i iiiiiijjjj>k@kAkBkmmmm-n/n0n5nnnnnooo oooooppppqqqqVrXrYrZrssss?tAtBtGtttttFuuu`vvvvvxy3znzz{2{,|r}}}}}~Ѐ NăɃʃσ?̈́τЄՄ4R`bchQ]eo׊يڊۊ[]^c!"#ŽÎĎŎMNOTKLMR&'(-֔"Dj@=bСԡ¢#$%*9^Z[\açħŧ0127-oѩ#QSTUīūƫ˫OQRS%&'(efgl$ˮͮήϮ   !RTUZ߶$=[9;<A[]^xJ1PP5p0oCQUbghm _abcQRSXFHINrstuacdiGIJO@ABG'i(?IJKP ]-0238]_`e$^'+RAimz   467<$&',$ !crstu#$%*q$V;=>?m        < C K Z e g h i     x        " # $ )     5 7 8 L o\mJhjklqrsxdefgwvwx}*,-.BCDEFG1234&'(-]_`ar   b!d!e!f!!!!!""""####g$h$i$n$U%%%#&%&&&+&'f'''''')))) ****+ + ++B,,,-----........////////M000000,1-1.13111112222=3>3?3D34444555!5(6*6+606+7-7.7/77777;8=8>8C888889999-:.:/:4:::::r;s;t;y;9<;<<<=<<<<<== >7>[>>>>/?R?q@A CCCDDDEEE>FF?HKHIIIIIIaJcJdJeJ K K KKQKSKTKYKKKKK0L2L3L8LLLLLSMUMVMWMMMMM;N=N>N?NNNNNOOOOPPPPPPPPPPPP"Q$Q%Q&Q_Q`QaQfQPRRRSRTRRRRR S S SSCSESFSKS!T#T$T)TTTT U5UEUGUHUMUUUUU:VSVjVVVVVVVbWdWeWfWWWWWXXZX[X`XYYYYYYYYZZZZC[D[E[J[[[[[[[[[[[[[\\\$\/]1]2]3]^^^$^^^^^` `!`"` a aaaaaaabbbb_dadbdcdneoepeqe6f7f8f=fggggggggh h!h"hhhhhii i%iiiii5j6j7jw?w@wwwwwyyyyyzzzb{c{d{e{`|a|b|c|}}}}~~~~~~(C\^_`9:;@́߁-=lmns:<=Q- $9>?@STUVyz{||}~Z\]q!v>Nq-RTUZ   :<=BڔܔݔHŗҗחؗݗZ\]bNPQV >.B!_cpuv{SUVW.016wyzrtuzQRSX1349ΩDFGHíŭƭ˭RTU,bͱԲƷ0޸madz~\^_dμмѼҼnpqvDFGLhijosuvw()*+     !& 3FHINEGHIYZ[`pIJnp|pwI] F.016amMjxWYZ_+cnt+016fhijwBCDI)9DLoqrwklmr,./0<>?@",-.3QVXY^.xz{|ijkp'QhMNOT[]^_jlmr1238DFGLXzK I   ; n    H v 9 [I~2E3st)V*vo9c9)O\!   6!U!p!!!"###$&&''()g)))$*l***++C,,.-k--Q.u... /0r111z2222223 33I4j444"55 6n67878U999F:g:::;;;;^<<!=O=== >H>l>>#?O?`???hAAAA#BBBCCDEEEF9FF*GMGGG H9HRHHH7IJJ0KbKKKLLKM|MM3NOSPzPPPQQQSTATTTTUVVLWWXPYYYYDZiZZZ5[~[[,\@]^_`j```Laa$bybbb$c^ccef=ffffg3ghhibi*jBjcjj kJkvkkkkkSlllm`mmnnmooopp+qqpshtvvvwwwYy[yhyymzzz{|}}}}~~~~&QZ*U\lΆRY$#/%:EwMF1 5iǚ?՝2_jsʢȣϣݣ %),045JMQUYZäƤʤΤϤ!%)-12LORUXYpsw{ťɥͥΥCFJNRSehlptu¦ŦȦɦNQTX\]ӧקۧߧ 8;>BFGhknquvϨ9:>[vwx%&''()ج٬ڬX, VWXDEFpdefD¶նݷVXd7<2h}902>cdr auF'(@QRduv./<WXgxy#$4OPars(8 OPjklJ[^_{  !"6BCV_`x{|HIbq!0%ABVb}~/0@L#RSkw0<YZjv)5NO_k (FGWc 01@LMN[g@AVb78HT  (?@Tbtu  (BCR`lmz)7KL]k&':HZ[jx$:;M[op= xy   ()+45atu%&'.567FPQRahij|'().89:LVWXfpqry*126DKLMV]^_hrst{  #$%29:;IPQR[bcdmtuv(/01 67KZ[gz{"Ciju~ &')Fp234iwJDRyIJUklztu}cdm  rs}';<I"#/   h i o \ ] b    @ A T e    ) * /    kl{|  JKnoN<) "V##$$$&&(())**q+z+-#---..r.z..C0D0M0T0\0`0i0r0y00000111111 1!1"1#111P1R1T1U1V1W1X1Y1Z1[1i111111111111111111111111222426282:2<2=2>2?2H2222222222222222222333 3.3/31333537393:3;3<3G333333333333*4+4-4.4/40414243444>444444444444555555 5"5#5$5.555555555555666666 6!6"6#6-6`6b6d6e6f6g6h6i6j6k6u666666666666667777777 7797:7<7>7@7B7D7E7F7G7Q777777777777777777777778888888888(8888888888889999999999$9>9@9B9C9D9E9F9G9H9I9O999999999999999::::::: :+:-:/:1:3:5:7:8:9:::g::;<!=C======> >>>>> >!>1>2>5>B>D>Q>R>V>a>e>p>q>u>>>>>>>>>>>"?&?O?P?T???????????@$@G@H@L@q@v@@@@@@@@@@@AAA-A1AAABAFASAWAdAeAiAAAAAAAAAAABB>B?BCBUBYBkBlBpBxB|BBBBBBBBBCCCCC%C)C0C1C5CBCGCTCUCYCnCrCCCCCCCCCCCCCDDD.D/D1DHDJDdDeDiD}DDDDDDDDDDDDE E"E4E6EVEWE[EcEgEoEpEtEEEEEEEEEEEEEEEF FFFFF@FBFhFiFmFFFFFFFFFFFFGGGG-G1GEGFGHGaGcG|G}GGGGGGGGGGGGGH+H,H/HCHFHWHXH]HHHHHHHHIII)I.I]I^IcIlIqIzI{IIIIIIIIIIIIIIJJJ4J5JaJbJeJJJJJJJJJJJJJKK K K&K:K;K@KTKYKmKnKsKKKKKKKL1L2L7LjLoLLLLLLLLLLLLLL*M3M@MAMFMnMyMMMMMMMMM7NBNeNfNkNNNNNNNN O OO1OU`UiUUUUUVVWVW\?\@\A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z\[\\\]\^\_\`\a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z\{\|\}\~\\\\\\\\\\\\\\\\\\\0000000000D0D0D0D00c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c00G0G0G0G00f0f0f0f0f0f0f0f0f0f0f0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000+0+0+0+0+0+0+! 0! 0[6[60h60h60h60h6! 0[6[60Z<0Z<0Z< 0Z< 0Z< 0Z<0Z<0Z<! 0[6[60@0@0@0@0@0@! 0[6[60H0H0H0H0H0H0H! 0[6[60 T 0 T 0 T 0 T 0 T 0 T 0 T 0 T0 T 0 T 0 T0 T! 0[6[60X! 0[6[60=Z0=Z0=Z0=Z0=Z0=Z! 0[6[60h 0 h 0 h 0h 0h 0h! 0[6[60m0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m0m 0m 0m 0m0m! 0 [6[60Hr0Hr0Hr0Hr0Hr0Hr0Hr0Hr0Hr0Hr0Hr0Hr0Hr! 0 [6[60[60{ 0{ 0{ 0{0[600 0 0 00! 0 [6[608 08 080808 0 8 0!808! 0 [6[60`! 00'! 0''08080808080808080808 0"8 0#8 0$8 0%808 0&8 0'8 0(8 0)8 0*8 0+80808080808080808080808080808 0,8 0-80808 0.8 0/8 00808080808080808080808080808080808080808080808080808080808080808! 0''0ʫ 01ʫ 02ʫ 03ʫ 04ʫ 05ʫ 06ʫ 07ʫ 08ʫ0'0 09 0: 0; 0<000000'0 0= 0> 0? 0@0 0A 0B 0C 0D 0E 0F00'0606060606 0G6 0H6060'0r0r0r0r0r0r0'00000000'0M0M0'000'000000! 0''000 0I 0J 0K 0L 0M 0N000000000000! 00000 0O 0P 0Q 0R000000 0S 0T00! 00000! 00000 0 0 0! 00 0U 0V 0W000 0 0 0! 00000 0 0 0! 00000 0 0 0 0 0 0 0! 00000 0 0 0! 00000 0 0X 0Y 0 0! 00000 0 0 0! 00000 0 0 0! 0000! 0 0000 0 0 0! 0 000! 0 0000 0 0 0! 0 0000 0 0 0! 0 0000 0 0 0! 00 0Z 0[ 0\000 0 0 0 0 0 0 0 0 0 0 0! 00000 0 0] 0^ 0_ 0` 0 0 0 0 0 0! 0000! 0000! 0000! 0000! 00000 0 0 0! 0000! 0000! 0000! 00000 0 0 0! 00000 0 0 0! 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% 0a% 0b% 0c% 0d% 0e% 0f% 0g%0%0%! 0%%0%0%0%0% 0% 0% 0% 0% 0% 0% 0%! 0%%0%0%0%0% 0%0% 0% 0%! 0 %%0%0%0%0% 0%0%0% 0% 0% 0% 0% 0% 0%! 0 %%0%0%0%0% 0% 0% 0%! 0 %%0%0%0%! 0 %%0%0%0%! 0 %%0%0%0%0% 0% 0% 0%! 0%%0%0%0%! 0%%0%0%0%! 0%%0%0%0%0% 0% 0% 0%! 00;0; 0h; 0i;0;0; 0j; 0k;0;0;0; 0l; 0m; 0n; 0o; 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; 0q; 0r; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0;! 0;;0; 0s; 0t;0;0;! 0;;0;0;0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0;0;0;! 0;;0;0;0;! 0;;0;0;0;! 0 ;;0;0;0;0; 0; 0; 0;! 0 ;;0;0;0;0; 0; 0; 0;! 0 ;;0;0;0;! 0 ;;0;0;0;! 0 ;;0;0;0;! 0;;0;0;0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0;0;0;! 0;;0;0;0;! 00W0W0W0W0W! 0WW0W0W0W0W 0W 0W 0W! 0WW0W0W0W0W 0W 0uW 0vW 0W 0W! 0WW0W0W0W0W 0W 0wW 0xW 0yW 0W 0W 0W 0W 0W 0W! 0WW0W0W0W0W 0W 0W 0W 0W 0W0W 0W 0W! 0WW0W0W0W0W 0W 0W 0W 0W 0W 0W 0W! 0WW0W0W0W0W 0W 0W 0W! 0WW0W 0zW 0{W 0|W0W0W! 0WW0W0W0W! 0WW0W0W0W! 0 WW0W0W0W! 0 WW0W 0}W 0~W0W0W0W! 0 WW0W0W0W0W 0W 0W 0W! 0 WW0W0W0W0W 0W 0W 0W 0W 0W 0W 0W! 0 WW0W0W0W0W 0W 0W 0W! 0WW0W0W0W! 0WW0W0W0W0W 0W 0W 0W! 0WW0W0W0W! 0WW0W0W0W! 0WW0W0W0W0W 0W 0W0W 0W 0W 0W! 0WW0W0W0W0W 0W 0W 0W! 0WW0W 0W 0W 0W0W0W0W 0W 0W 0W! 0WW0W0W0W0W 0W 0W 0W! 0WW0W0W0W! 0WW0W0W0W0W 0W 0W 0W! 0WW0W0W0W0W 0W 0W 0W! 0WW0W0W0W! 0WW0W0W0W0W 0W 0W 0W! 0WW0W0W0W! 0WW0W0W0W0W 0W 0W 0W! 0000000! 000000000000000! 00000 0 0 0! 0000! 0000! 0000! 00 0 0 0 0 0 0000 0 0 0 0 0 0 0! 0000! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0! 0 0000 0 0 0! 0 0000 0 0 0! 0 0000 0 0 0! 0 0000 0 0 0! 0 000! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0! 0000! 00000 0 0 0! 00 0 0 0 0000 0 0 0 0 0 0 0! 0000! 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;;0;0;0;0; 0; 0; 0;! 0;;0;0;0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0;0;0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0;0;0;! 0;;0;0;0;! 0 ;;0;0;0;! 0 ;;0;0;0;0; 0; 0; 0;! 0 ;;0;0;0;! 0 ;;0;0;0;0; 0; 0; 0;! 0 ;;0;0;0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0;0;0;0; 0; 0; 0;! 00000000! 0000! 00 0 0 000! 0000! 00000 0 0 0! 0000! 00000000! 00000 0 0 0! 00 0 0000 0 0 0 0 0 0 00 0 0! 00000 0 0 0! 00 0 0000 0 0 0 0 0 0 0 0 0 0 0! 00000 0 0 0! 00000! 00a0a0a0a! 0aa0a0a0a! 0aa0a0a0a! 0aa0a0a0a0a 0a 0a 0a! 0aa0a0a0a! 0aa0a0a0a! 0aa0a0a0a! 0aa0a0a0a! 0aa0a0a0a0a 0a 0a 0a! 0aa0a0a0a! 0 aa0a0a0a0a 0a 0a 0a! 0 aa0a0a0a0a 0a 0a 0a! 0 aa0a0a0a! 0 aa0a0a0a! 0 aa0a0a0a0a 0a 0a 0a! 0aa0a0a0a0a 0a 0a 0a! 0aa0a0a0a0a 0a0a 0a 0a! 0aa0a0a0a0a 0a 0a 0a! 0aa0a0a0a0a 0a 0a 0a 0a 0a 0a! 0aa0a 0a0a 0a0a0a! 0aa0a 0a 0a0a0a! 0aa0a 0a 0a0a0a0a 0a 0a 0a! 0aa0a0a0a0a 0a 0a 0a! 0aa0a0a0a0a 0a 0a 0a 0a 0a 0a0a 0a0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a! 0aa0a 0a 0a 0a 0a 0a0a0a0a 0a 0a 0a! 0aa0a 0a 0a 0a 0a 0a 0a0a0a0a 0a 0a 0a 0a 0a 0a 0a! 0aa0a0a0a! 0aa0a0a0a0a 0a 0a 0a! 0aa0a0a0a! 0aa0a0a0a! 0aa0a0a0a! 0aa0a0a0a! 0aa0a0a0a! 0 aa0a 0a0a 0a0a0a0a 0a 0a 0a! 0!aa0a0a0a! 0"aa0a0a0a0a 0a 0a 0a! 0#aa0a0a0a0a 0a 0a 0a! 0$aa0a0a0a! 0%aa0a0a0a0a 0a 0a 0a 0a 0a! 0&aa0a0a0a0a 0a 0a 0a! 0'aa0a0a0a! 0(aa0a0a0a! 0)aa0a0a0a! 0*aa0a0a0a! 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/ 0/ 0/ 0/! 0//0/ 0/ 0/0/0/0/ 0/! 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;0; 0; 0; 0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0; 0; 0;0;0;! 0;;0; 0; 0;0;0;! 0;;0; 0; 0; 0; 0;0;0;! 0 ;;0;0;0;0; 0; 0; 0;! 0 ;;0;0;0;! 0 ;;0;0;0;! 0 ;;0;0;0;0; 0; 0; 0; 0; 0; 0; 0;! 0 ;;0;0;0;0; 0; 0; 0; 0; 0; 0; 0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0; 0; 0;0;0;! 0;;0;0;0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0; 0; 0; 0; 0; 0;0;0;0;0; 0; 0; 0; 0; 0; 0; 0;! 0;;0; 0; 0; 0; 0; 0; 0; 0;0;0;! 0;;0;0;0;! 0;;0;0;0;0; 0; 0; 0;! 0;;0;0;0;! 0;;0;0;0;0;! 00`0`0`0`0b0b0b0b0b! 0``0h0h0h0h0h0h! 0hh0h 0h 0h 0h0h0h0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h! 0hh0h0h0h0h 0h 0h 0h! 0hh0h0h0h! 0hh0h0h0h0h 0h 0h 0h 0h 0h 0h 0h 0h 0h! 0hh0h0h0h0h 0h 0h 0h 0h 0h 0h 0h 0h 0h! 0hh0h0h0h! 0hh0h0h0h0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0 h 0 h0h 0h 0h! 0hh0h0h0h0h 0h 0h 0h! 0hh0h0h0h0h 0h 0h 0h 0h 0h 0h 0h! 0 hh0h0h0h0h 0h 0h 0h! 0 hh0h0h0h! 0 hh0h0h0h0h 0h 0h 0h 0h 0h 0h 0h! 0 hh0h0h0h! 0 hh0h0h0h0h 0h 0h 0h 0h 0h 0h 0h! 0hh0h0h0h! 0hh0h0h0h! 0hh0h0h0h0h 0h 0 h 0 h0h 0h 0h! 0hh0h 0 h 0h 0h 0h 0h 0h0h0h0h0h 0h 0h 0h! 0hh0h0h0h0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h 0h! 0hh0h0h0h0h 0h 0h 0h! 0hh0h0h0h! 0hh0h0h0h! 0hh0h0h0h0h 0h 0h 0h! 0hh0h0h0h! 0hh0h0h0h! 0hh0h0h0h! 0hh0h0h0h! 0hh0h0h0h0h 0h 0h 0h! 0hh0h0h0h! 0hh0h0h0h0h 0h 0h 0h! 0hh0h0h0h0h 0h 0h 0h! 0hh0h 0h 0h 0h0h0h! 0 hh0h 0h 0h 0h 0h 0h0h0h! 0!hh0h0h0h0h 0h 0h 0h! 0"hh0h0h0h0h 0h 0h 0h! 0#hh0h0h0h0h 0h 0h 0h! 0$hh0h0h0h0h 0h 0h 0h 0h 0h 0h 0h! 0%hh0h0h0h! 0&hh0h0h0h0h 0h 0h 0h 0h 0h 0h 0h! 0'hh0h0h0h0h 0h 0h 0h! 0(hh0h 0h 0 h0h 0h 0h0h 0h 0h 0h 0h 0h 0h 0h! 0``0 0! 0" 0# 0$ 0%0000000! 00000 0 0 0! 00 0& 0' 0(000 0 0 0! 0000! 00000 0 0) 0* 0+ 0, 0 0! 0000! 00000 0 0 0! 00000 0 0- 0. 0/ 00 0 0! 00000 0 0 0! 0``0`0 0 0 0 0`0 010 020 0300 04 05 0600000! 0000! 00000 0 0 0 0 0 0 0! 00 07 08 09 0:000 0 0 0! 00 0; 0< 0= 0>000 0 0 0! 00 0? 0@ 0A 0B 0C 0D 0E0000 0 0 0 0 0 0 0! 00000 0 0 0! 00 0F 0G 0H000 0 0 0 0 0 0 0! 00000 0 0 0! 0000! 0 0000 0 0 0! 0 0000 0 0 0 0 0 0 0! 0 0000 0 0 0! 0 000! 0 0000 0 0 0! 00 0I0 0J000! 00 0K0 0L0000 0 0 0! 00000 0 0 0! 0000! 0``0 0M 0N 0O 0P00000! 0000! 0000! 0000! 0000! 0000! 0``00 0Q 0R00 0S 0T 0U0000 0V 0W 0X 0Y00000! 00000 0 0 0! 00000 0 0 0! 00 0Z 0[ 0\00! 00000 0 0 0! 0000! 00 0] 0^000 0 0 0! 00000 0 0 0! 00000 0 0 0 0 0 0 0! 0000! 0 0000 0 0 0! 0 0000 0 0 0! 0 0000 0 0 0 0 0 0 0! 0 000! 0 000! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0! 00 0_ 0` 0a 0b 0c 0d 0e 0f00! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0! 0000! 0000! 00 0  0g  0h 0  0i  0j  0k 0 0 0 0 0 0 0 0 0 0 0 0 0  0l  0m  0n  0o 0 0 0 ! 0  0a0a0a0a! 0aa0a 0pa 0qa 0ra 0sa 0ta 0ua0a0a! 0aa0a0a0a! 0aa0a0a0a! 0aa0a0a0a! 0aa0a 0va 0wa 0xa 0ya 0za0a0a! 0aa0a 0a 0a! 0aa0a 0{a 0|a 0}a 0~a0a0a0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a! 0aa0a 0a0a 0a0a0a0a 0a 0a 0a 0a 0a0a 0a 0a 0a 0a 0a 0a! 0aa0a 0a 0a0a0a0a 0a 0a 0a! 0 aa0a0a0a! 0  0w*0w*0w*0w*! 0w*w*0w* 0w* 0w* 0w* 0w* 0w* 0w* 0w* 0w* 0w*0w*0w*! 0w*w*0w*0w*0w*0w* 0w* 0w* 0w*! 0w*w*0w*0w*0w*! 0w*w*0w*0w*0w*0w* 0w* 0w* 0w* 0w* 0w* 0w* 0w*! 0w*w*0w*0w*0w*0w* 0w* 0w* 0w* 0w* 0w* 0w* 0w*! 0w*w*0w*0w*0w*0w* 0w* 0w* 0w*! 002020202! 022080808080808! 088080808! 08808 08 08080808! 08808080808 08 08 08! 088080808! 08808080808 08 08 08! 08808080808 08 08 08! 08808080808 08 08 08! 08808080808 08 08 08! 08808080808 08 08 08! 0 88080808! 0 8808080808 08 08 08! 0 8808 08 08080808 08 08 08! 0 8808 08 08 08 08080808! 0 88080808! 08808080808 08 08 08! 088080808! 08808 08 0808080808 08 08 08 08 08 08 08! 08808080808 08 08 08 08 08 08 08! 08808080808 08 08 08! 08808080808 08 08 08! 08808080808 08 08 08 08 08 08 08! 08808080808 08 08 08 08! 088080808! 08808080808 08 08 08! 0880808080808 08 08 08! 088080808! 088080808! 088080808! 08808 08 08 08 08 08 08 08 08 080808! 08808 08 08 08 080808! 088080808! 088080808! 0 8808080808 08 08 08! 0220`0`0`0`0`! 0``0`0`0`0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0`! 0``0`0`0`0` 0` 0` 0`! 0``0`0`0`0` 0` 0` 0`! 0220i0i0i0i0i0i0i! 0ii0i0i0i! 0ii0i0i0i! 0ii0i0i0i! 0ii0i0i0i! 0ii0i0i0i0i 0i 0i 0i! 0ii0i0i0i! 0ii0i0i0i! 0ii0i0i0i0i 0i 0i 0i! 0ii0i0i0i! 0 ii0i0i0i! 0 ii0i0i0i0i 0i 0i 0i! 0 ii0i0i0i! 0 ii0i0i0i0i 0i 0i 0i 0i 0i 0i 0i! 0 ii0i0i0i! 0ii0i0i0i0i 0i 0i 0i! 0ii0i0i0i! 0ii0i0i0i0i 0i 0i 0i! 0ii0i0i0i! 0ii0i 0i 0i0i0i0i 0i 0i 0i! 0220{0{0{0{0{! 0{{0{0{0{0{ 0{ 0{ 0{! 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` 0` 0` 0` 0`! 0``0`0`0`0` 0` 0` 0`! 0}}0S0S 0S 0S 0S 0S 0S0S0S0S0S0S0S! 0SS0S0S0S! 0SS0S0S0S0S 0S 0S 0S! 0SS0S0S0S0S 0S 0S 0S! 0SS0S0S0S! 0SS0S0S0S0S 0S 0S 0S! 0SS0S0S0S! 0SS0S0S0S0S 0S 0S 0S! 0SS0S0S0S! 0SS0S0S0S0S 0S 0S 0S! 0 SS0S 0S 0S 0S 0S 0S 0S0S0S! 0 SS0S 0S 0S 0S0S0S! 0 SS0S 0S 0S 0S0S0S! 0 SS0S 0S 0S 0S0S0S! 0 SS0S0S0S! 0SS0S0S0S0S 0S 0S 0S! 0SS0S0S0S! 0SS0S0S0S! 0SS0S 0S 0S 0S 0S 0S 0S 0S0S0S! 0SS0S 0S 0S 0S0S0S! 0SS0S0S0S! 0SS0S0S0S! 0SS0S0S0S! 0SS0S0S0S! 0SS0S0S0S0S 0S 0S 0S! 0SS0S0S0S! 0SS0S0S0S! 0SS0S 0S 0S 0S 0S 0S0S0S! 0SS0S0S0S! 0SS0S0S0S! 0SS0S0S0S! 0SS0S0S0S! 0SS0S0S0S! 0 SS0S0S0S! 0!SS0S0S0S! 0}}0>0>0>0> 0> 0>0>0>0>0>0>0>0>0>0>0>! 0>>0>0>0>0> 0> 0> 0>! 0>>0>0>0>0> 0> 0> 0>! 0>>0> 0> 0>0>0>0> 0> 0> 0>! 0>>0> 0> 0>0>0>! 0>>0>0>0>0> 0> 0> 0>! 0>>0>0>0>0> 0> 0> 0>! 0>>0> 0> 0> 0> 0> 0> 0>0>0>0> 0> 0> 0>! 0>>0>0>0>0> 0> 0> 0>! 0>>0>0>0>! 0 >>0>0>0>0> 0> 0> 0>! 0 >>0>0>0>0> 0> 0> 0> 0> 0> 0> 0>! 0 >>0>0>0>! 0 >>0>0>0>! 0 >>0> 0> 0> 0>0>0>! 0>>0>0>0>! 0>>0>0>0>! 0>>0>0>0>0> 0> 0> 0>! 0>>0>0>0>! 0>>0>0>0>! 0>>0>0>0>! 0 000 0 0 0 0 0 0 0 0 0 0 0 0 0000! 000 0 0000 0 00000000! 0000! 0000! 0000! 0000! 0000! 00000 0 0 0! 00 0 000! 0000! 0000! 0 000! 0 000! 0 000! 0 000! 0 000! 00000 0 0 0! 00000 0 0 0! 00 0 0 0 0 0 000! 0000! 0000! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0 0 0 0 0  0 0! 00 0  0 00! 00000 0 0 0! 00000! 0000! 00000 0 0 0! 0000! 00000 0 0 0! 00000000 0  0  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000 0 0 0! 00000 0 0 0! 00000 0 0 0! 00 0 0 000! 00 0 0 000! 00000 0 0 0! 00 00 000! 00000 0 0 0! 0000! 0000! 0 000! 0 0000 0 0 0 0 0 0 0! 0 0 0 0 0!000! 0 0000 0 0" 0# 0$ 0 0! 0 000! 0000! 0000! 00000 0 0 0! 00 0% 0& 0' 0(00! 0000! 0000! 00 0) 0*000 0 0 0! 00 0+ 0, 0-000 0 0 0! 00000 0 0 0! 0000! 0000! 0000! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0! 00 0. 0/ 00 01000! 00000 0 0 0! 0000! 0 000! 00'*0'*0'* 02'* 03'* 04'* 05'* 06'* 07'*0'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*0'* 0'* 0'* 0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0 '*'*0'*0'*0'*! 0 '*'*0'* 0'* 0'*! 0 '*'*0'*0'*0'*! 0 '*'*0'* 08'* 09'* 0:'*0'*0'*! 0 '*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*0'* 0'* 0'* 0'*! 0'*'*0'*0'*0'*0'* 0'* 0;'* 0<'* 0='* 0'* 0'* 0'* 0'* 0'* 0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*! 0'*'*0'* 0>'* 0?'* 0@'*0'*0'*! 0'*'*0'*0'*0'*0'* 0'* 0'* 0'*! 0'*'*0'* 0A'*0'* 0B'*0'*0'*0'*! 0'*'*0'*0'*0'*0'* 0'* 0'* 0'*! 0'*'*0'*0'*0'*! 0'*'*0'*0'*0'*0'* 0'* 0'* 0'*! 0 '*'*0'*0'*0'*! 0!'*'*0'*0'*0'*0'* 0'* 0'* 0'*! 0"'*'*0'*0'*0'*0'* 0'* 0'* 0'*! 0#'*'*0'*0'*0'*! 0$'*'*0'*0'*0'*! 0%'*'*0'*0'*0'*! 0&'*'*0'*0'*0'*! 0''*'*0'*0'*0'*0'* 0'* 0'* 0'*! 0('*'*0'*0'*0'*! 0)'*'*0'*0'*0'*! 0*'*'*0'*0'*0'*! 0+'*'*0'*0'*0'*! 00N0N0N 0CN 0DN 0EN 0FN 0GN 0HN 0IN0N0N0N0N0N0N! 0NN0N0N0N0N 0N 0N 0N! 0NN0N0N0N! 0NN0N0N0N! 0NN0N0N0N0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0JN 0KN 0LN 0MN 0N 0N! 0NN0N0N0N! 0NN0N0N0N0N 0N 0N 0N! 0NN0N 0NN 0ON 0PN 0QN 0RN 0SN0N0N0N 0N 0N 0N 0N 0N 0N 0N! 0NN0N 0TN 0UN0N0N! 0NN0N0N0N! 0 NN0N0N0N0N 0N 0N 0N! 0 NN0N0N0N0N 0N 0N 0N! 0 NN0N0N0N! 0 NN0N0N0N0N 0N 0N 0N! 0 NN0N0N0N0N 0N 0N 0N! 0NN0N0N0N! 0NN0N0N0N0N 0N 0N 0N! 0NN0N0N0N! 0NN0N0N0N! 0NN0N 0VN 0WN 0XN 0YN0N0N! 00v0v 0Zv 0[v 0\v 0]v 0^v0v0v0v0v0v0v 0_v 0`v 0av0v 0bv 0cv 0dv0v0v0v0v0v0v! 0vv0v 0ev0v 0fv0v0v! 0vv0v 0gv 0hv0v0v! 0vv0v0v0v0v 0v 0iv 0jv 0kv 0lv 0mv 0nv0v 0v 0v 0v 0v 0v 0v! 0vv0v0v0v! 0vv0v0v0v0v 0v 0v 0v! 0vv0v0v0v! 0vv0v0v0v0v 0v 0v 0v 0v 0v 0v 0v! 0vv0v0v0v! 0vv0v0v0v0v 0v 0v 0v! 0 vv0v0v0v0v 0v 0v 0v! 0 vv0v0v0v! 000 0o 0p 0q 0r0000000000! 00000 0 0 0! 00 0s 0t 0u000 0 0 0! 00000 0 0 0 0 0 0 0! 00000 0 0 0! 00 0v 0w 0x 0y 0z 0{000 0 0 0! 00000 0 0 0 0 0 0 0! 00 0| 0}00! 00000 0 0 0! 00000 0 0 0! 0 0000 0 0 0! 0000000! 0000! 0000! 00 0~ 0 0 0 000! 0000! 00000 0 0 0! 0000! 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^^0^0^0^! 0^^0^0^0^0^ 0^ 0^ 0^ 0^ 0^ 0^ 0^! 0^^0^0^0^! 0^^0^0^0^0^ 0^ 0^ 0^! 0 0000000! 0000! 0000! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0 0 0 0 0 0 0 0 0! 00000 0 0 0 0 0 0 0! 0000! 00000 0 0 0! 0000! 0 000! 0 0000 0 0 0! 0 000! 0 0000 0 0 0 0 0 0 0! 0 000! 00000 0 0 0! 0000! 0000! 0 00 0 0 0000000000! 00000 0 0 0! 0000! 0000! 0000! 00000 0 0 0! 0000! 00000 0 00 0 0 0! 00000 0 0 0 0 0 0 0! 0000! 0 000! 0 000! 0 000! 0 00000000! 0000! 00000 0 0 0! 0000! 0000! 00 0 0 0000 0 0 0! 00 0 0000 0 0 0! 00 0 0 0 0000 0 0 0! 00 0 0 0 0000 0 0 0! 0000! 0 000! 0 08 08 08 08 08 08 08 08 08 08 08 08 08 ! 08 8 08  08  08  08 08 08 08  08  08  08 ! 08 8 08 08 08 08  08  08  08 ! 08 8 08 08 08 08  08  08  08  08  08  08  08  08  08  08  08  08  08 ! 08 8 08 08 08 08  08  08  08  08  18  18  08  18  18  08  18  18  08  18  18  08  08  08  08  08  08  08  08  08  08  08  08 ! 08 8 08 08 08 08  08  08  08 ! 08 8 08 08 08 08  08  08  08 ! 08 8 08  08  08 08 08 08 08  08  08  08 ! 08 8 08 08 08 ! 08 8 08 08 08 08  08  08  08 ! 0 8 8 08  08  08  08 08 08 ! 0 8 8 08  08  08  08 08 08 ! 0 8 8 08 08 08 ! 0 8 8 08 08 08 ! 0 8 8 08 08 08 ! 08 8 08  08  08  08  08 08 08 ! 08 8 08 08 08 08  08  08  08 ! 08 8 08 08 08 08  08  08  08 ! 08 8 08  08  08 08 08 08  08  08  08 ! 08 8 08 08 08 ! 08 8 08 08 08 08  08  08  08 ! 08 8 08 08 08 ! 08 8 08 08 08 ! 08 8 08 08 08 ! 08 8 08 08 08 08  08  08  08 ! 08 8 08 08 08 ! 08 8 08 08 08 ! 08 8 08 08 08 08  08  08  08 ! 08 8 08 08 08 08  08  08  08 ! 08 8 08 08 08 08  08  08  08 ! 0 0<0< 0< 0< 0< 0< 0< 0< 0< 0<0<0<0<0<0<0<0<0<0<0<0<0<0<0<! 0<<0?H0?H0?H0?H0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H! 0?H?H0?H0?H0?H! 0?H?H0?H0?H0?H! 0?H?H0?H0?H0?H! 0?H?H0?H 0?H 0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0 ?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0 ?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0 ?H?H0?H0?H0?H! 0 ?H?H0?H0?H0?H! 0 ?H?H0?H0?H0?H! 0?H?H0?H 0?H 0?H 0?H 0?H 0?H0?H0?H! 0?H?H0?H0?H0?H! 0?H?H0?H 0?H 0?H 0?H 0?H 0?H0?H0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H 0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0?H?H0?H0?H0?H! 0?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0 ?H?H0?H0?H0?H! 0!?H?H0?H0?H0?H0?H 0?H 0?H 0?H! 0<<0Qk0Qk 0Qk 0Qk 0Qk 0Qk0Qk0Qk0Qk0Qk0Qk0Qk0Qk0Qk0Qk! 0QkQk0Qk 0Qk 0Qk 0Qk 0Qk0Qk0Qk! 0QkQk0Qk0Qk0Qk0Qk 0Qk 0Qk 0Qk! 0QkQk0Qk0Qk0Qk0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk! 0QkQk0Qk0Qk0Qk0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk! 0QkQk0Qk 0Qk 0Qk0Qk 0Qk 0Qk 0Qk! 0QkQk0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk0Qk 0Qk 0Qk 0Qk! 0QkQk0Qk 0Qk 0Qk0Qk 0Qk 0Qk 0Qk! 0QkQk0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk 0Qk0Qk0Qk0Qk0Qk 0Qk 0Qk 0Qk! 0QkQk0Qk0Qk0Qk! 0<<0=0=0=0=0=0=! 0==0= 0= 0=! 0==0= 0= 0=0= 0= 0= 0= 0= 0= 0= 0=! 0==0= 0= 0=0= 0= 0= 0=! 0==0= 0= 0=0= 0= 0= 0=! 0==0= 0= 0=! 0<<0]0] 0] 0] 0] 0] 0] 0] 0] 0]0]0]0]0]0]0]0]! 0]]0]0]0]! 0]]0]0]0]! 0]]0]0]0]0] 0] 0] 0]! 0]]0]0]0]! 0]]0]0]0]! 0]]0]0]0]! 0<<0ݔ0ݔ0ݔ0ݔ0ݔ0ݔ0ݔ0ݔ! 0ݔݔ0ݔ0ݔ0ݔ! 0ݔݔ0ݔ0ݔ0ݔ! 0ݔݔ0ݔ0ݔ0ݔ! 0ݔݔ0ݔ0ݔ0ݔ! 0<<0000 0 000000! 00000 0 0 0! 00000 0 0 0! 0000! 0000! 0000! 0000! 00000 0 0 0! 0000! 0000! 0 0 0 000! 0 000! 0 0000 0 0 0! 0 0000 0 0 0! 0 000! 0000! 0<<0<0 0 0 000<00 0 0 00<0Բ0<00 0 0 0 00 0 000<0d0d0d0d! 0Ud0d0d0d! 0Ud0d0d0d0d 0d 0d 0d! 0Ud0d0d0d! 0Ud0d0d0d! 0Ud0d0d0d! 0Ud0d0d0d! 0Ud0d0d0d0d 0d 0d 0d! 0Ud0d0d0d0d 0d 0d 0d! 0Ud0d0d0d0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d! 0 Ud0d0d0d! 0 Ud0d0d0d0d 0d 0d 0d! 0 Ud0d0d0d! 0 Ud0d 0d 0d0d0d! 0 Ud0d0d0d0d 0d 0d 0d! 0Ud0d0d0d0d 0d 0d 0d! 0Ud0d0d0d0d 0d 0d 0d! 0Ud0d0d0d! 0<<000 0 0 000000000! 0000! 0000! 00000 0 0 0 0 0 0 0 0 0! 0000! 00 0 0 0  0 00! 00000 0 0 0! 0000! 00 0  0  0 00! 00 0 0 0 0 0 0 0 0 0 000! 0 000! 0 0000 0 0 0! 0 00! 000n0n! 00000! 00000 0 0 0! 00000 0 0 0! 00000 0 0 0 0 0 0! 0000! 00 0 0 0 0 000! 00000 0 0 0! 0000! 00000 0 0 0! 0000! 0 0000 0 0 0! 0 0000 0 0 0! 0 000! 0 0 0  0! 0" 0# 0$00! 0 0 0% 0& 0'000 0 0 0! 0000! 00000 0 0 0! 00 0( 0) 0* 0+0000 0 0 0! 0000! 00000 0 0 0! 0000! 0000! 00000 0 0 0! 0000! 0000! 0 00 0, 0- 0. 0/! 0000000000000000000000000000000000000 00 01 02 030 04 05 06 07 08 0900000000000000000000000000 0: 0;00 0< 0= 0>0000000000000000000000000 0? 0@ 0A 0B 0C 0D 0E00000000000000000000000000000 0F 0G 0H 0I 0J0000000000000000000000000000000000000000000000000000000000000000000000000000 0K 0L00000000000000000000000000000000000000000000000! 00p0p0p0p0p0p0p0p0p0p0p0p0p! 00hy0hy00z00{ 0M{ 0N{ 0O{0{00~ 0P~ 0Q~ 0R~0~00Q 0SQ 0TQ0Q00U0U0U00Ά00R0R0R00#00! 00%0%0%0%0% 0U% 0V% 0W% 0X%0%0%0%0%0%0%0%0%0%0%0%0%0%0% 0Y% 0Z% 0[% 0\% 0]% 0^% 0_%0%0%0%0% 0%0% 0% 0% 0% 0% 0% 0% 0%0% 0%0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0000 0 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 00 0 00 0 0 00 0 0 00 0 0 0 0 0 0000f00000 0` 0a 0b 0c00000000000000000}0}0}0}0}0} 0d} 0e} 0} 0} 0f} 0} 0 } 0 }0}0}000 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 0000(0( 0( 0(0( 0( 0(0( 0( 0(0( 0( 0(0( 0( 0(0( 0( 0(0( 0( 0(0( 0( 0(000 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 0000 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00000 0g 0h0000 0 00 0 00 0 0 00 00 00 00 0 00 0 00 0 00 0 00 0 000000000000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 00000000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0i 0j 0k000000000000000000000000000000000000000000000000000000000000000000000000000000D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D0D00A 0A 0A 0A 0A 0A 0A 0A 0A 0A 0A 0A 0A 0A 0A 000000000000000000000000000o0o0o0o000000 0l 0m 0n 0o 0p0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0 0 0 0 0 000000 000 0 00 00000 0 0 00 0 0 0000000 0 0 0 0 0000000000000000 000 0 00 00000 000000 00000 0 0 00 0 0 0000000 00 0 0 00000 000000 00000 0 00 0 00 000000000000000000 0 0 0 0 00000 00 00 0 0 00000 00 00 0 0 00000000000000"0:: 0g: 0g: 0g: 0:: 0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!= 0!= 0!= 0!= 0!=0!=10U0U@1@1@1@1@1@1 00@0@0@0@0@0@0@0@0@0@0@0@0@0@1@1@0@0@0@0@0 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000D_`abcxyz{|}~   Gbcdef{|qV`: c J  s E T 'Jae0cacJecC\r5Q h 6!!*"""8###I$$%q%%L&&,'''m(()))s**V++++,Y,8..0W23[6h6s6\8)9;Z<<<!==B>>L??@@ABCvEFHHHFL{NPQS TITzTT UUUVuVVeWWWXX=ZlZ\:^'c f!ghhlJl|lllm#mno]oop9pppppppqqqqHrkrrNsAt?upuuLwBxzzzzz{{{|}jȁ8]ʄB`'E8HZFs؎ŐΑ'sْlC͖%/$J-3T_oԞ۟;Ms / JУ٣^ͥzЦ*ʫ׫5KqѬ?HS\jw#2ĹwD߻06[+rSMyT $,4AcP #+jlw" "#(%>p?@AF+-./dfghLMNOSUVW{}~-/01X Z [ \     t v w |         P R S X      cdej>@BCD+,-.hw<=>? XZ[`$4678    !!!"!'!!!!!X"Z"["\"U#V#W#\#####%%%%%''*'/'0'5'((( ({(}(~(())))))))\*^*_*`*1+2+3+8+++++,,,,j,,-N-y---... ...../// /////t0v0w0x01o2p2q2v2)3+3,3-3334444/50515655555S6T6U6Z666667777q8s8t8u8(9)9*9/99999|:~:::;;;;;;;;>>9??p@@ AAB9CECrCCC)DWDDDDDDD}EEEESFUFVF[F'G)G*G+GVHmInIoIpII3JJJJJKKKKcLdLeLjLLM?MAMBMGMMMMMNNNNNNNNOOO OcOeOfOkOOOOOPPPPPPPPvQxQyQzQQQQQ*R,R-R2RRRRRSSSS^S`SaSfSTTTTxTyTzTTwUyUzU{U/W0W1W6WWWWWWWWX[[+[0[1[6[[[[[\\\\[]]]^]_]]H^d^e^f^k^^^^^%__1`````3a4a5a:aaaaa!c"c#c$cc`dadbdgdOeQeReSe)f*f+f,fffff[g]g^g_gggggi+jjjjjjkkkkllllmmmm nn5ooooo;p=p>p?pppppqqqq(r)r*r+rrrrrsssst t!t&ttttt'u)u*u+uuuuu_vavbvgvvvvvwwwwSwwwPxQxRxWxxxxx4y5y6y;yygzz{!{"{#{{{{{||||^}_}`}e}}}}}~~~~tvw|z|}~#$%*ȃʃ˃Ѓnpqrk؋'ݐtՕݖ—Ǘȗ͗npqrޛ(X՝ם؝ٝ>?@AZ\]^͟Οϟԟhjkl)+,-   hjkl-./4yz{+-.3ڦۦܦvxyz ¨{}~ߩSUVWVWX]BCDIҭԭխڭ֮خٮڮstuzɰ=ɱNPQR8:;HY޶ϸw{Op#ֽ>7aοvwxy345: %678=acdiXZ[`&()*ACDIJLMRACDE F{NPQV_`afGY[\]wyz{9.DFGHdefgpqrslmns4Ha(*+0{}~npqrHJKPVXY^       !&245:}b ')*+RRSTY    K ~               U W X Y ~    5789mnoppIuT8~nopqI_um&P8 9 : ;         _!a!b!c!"""" ############a$c$d$i$% % %%%$&(&&&&&''''K(M(N(S((((((((())))))))*** ***** +/+H+I+J+O+,,,,v,w,x,},----...."/$/%/*/////1333333k4m4n4s41535455555556666 7k777 8888}8~8888888Z9\9]9b99999.:/:0:5:*;z;;;;;;<<<3===>?j@]AAAAAAABBBB8C9C:C?CCCCCDDDDE?E@EEEEE,F`FFFGG?G@GGGGGRHTHUHVHII I%II\JJJJKrKLLLLL'MnMM7NNNNNOOOOhPiPjPoPPPPPcQeQfQkQQQQQRRRRRSSSSSSS0T1T2T3TTTTTUUUUUUUUsVVhWjWkWpWXXXXXXXXYYYYZZZ"Z+ZOZyZ{Z|Z}Z[[[[\\\\\]4];]H]v]]{^}^~^^ ____^_`_a_b_________```````bb]ddggh%hilkpk}kkkkkll.m0m1m2mmmmmoooo p$p4p;pFpGpHpIppppppqq+qRqqqqr6rfrrrrrrrrrrrsssstttt uuuuuvvv vBvuvvvwvxvwwwx yyyyyyzzzz||||J}L}M}R}'~)~*~+~~~~~u-łƂǂ̂ƒÃăɃ!"#ۄ܄݄ބ   ‡LJ,./4*,-.‹ËȋmopqPRSXՐKLMRK{!#$%)*+0]^_`ٖږۖܖABCHjlmr_abg#%&'֠ :dfglϣѣңӣƤǤȤͤ789>opqvACDEVWX]'.4<GHIN+-./sNdefg@h&^=?@AnUVW\ ʻ̻ͻλN]^_dɾ˾̾ѾKMNO,./0_pVXYZ BM/$&',  `PQRW:UWXY "*IiHIJKbdef.^JLMN&'(-MOPQ,-.3 yiklm[pDHUZ[`RTUZm;_ p *.;@AFLMNSMp "#$$&'(z|}~~)*+0 &'(- # }                H I J O         U W X ]     U|*LNY57BP_ v9avz"*1<EMXZ[`    1!V!}!!!!!!!M"O"P"U"""""# # # ####$$$$$$$$$$$%b&f&&&&&'''''((((A(B(C(H(()))))))))t*v*w*******%+<+D+K+V+_+h+++++++N,P,Q,R,3-4-5-:---------....////h0j0k0l000001111"2$2%2&22223M45V7889::::::;;;;;;B<<<<<<<<<V=W=X=]=====e>g>h>i>V?W?X?]?????@@@@$A&A'A(A#B$B%B*BBBBB%C&C'C,CCCCCDDD#DDDDDFEHEIEJEEEEEbFFFFFFGGGGHHH)H.HwHyHzHHHHHH|I~IIIIIIIQJSJTJYJJJJJJKKKKKKLLLLMMMMOOOOPPPP9Q;Q?@E!SUV[ACDI:;<Aٔ4mÕĕɕ9hjkp=_abg@\^_d   "#(ě˛ћݛtbdej"ҠӠԠ٠].245:>@AFRTUZ;=>g4٫ެp` Reghi̴ʹδӴٵ۵ܵݵtɸչ׹عٹNOPU̼μϼԼWYZ[   ھ۾ܾDoÿ}:kmno#rtuvuvw|#<>?D$&',eghm1`2Xs4B)9~|i'%15BGHMiklqacde%&',W}oqrw;=>C.012  *,-2VXYZ*?Pmu"&389> \]^c`]fopOL s qrsx    M N O T  ( X     i                j m      %xz{ rstuAsuv{BCDIVXYZ2lnotz|}Mtvwx       !!!!T"U"V"["""""-#/#0#5#####*$,$-$.$$$$$%%%%%%%%&&&&m&n&o&t&&&&'O''''''''':);)<)A)))))$*&*'*0*+S-v.. //// 000!0"0'00000?1A1B1G1426272<222222222.3/3035333334444F5H5I5N55555 6 6 6 66666777"77708S8U8V8[8888899;9<9A99999:::$:::::::::?;A;B;G;~;;;;;;;;<<<<<<<< =|==>>>>`>a>b>g>>>>>????s@u@v@{@@@@AAA AAAAATBUBVB[BBBB,CfChCiCnCCCCCjEkElEqEF F!F&FFFFFGG G%GHHH HxHzH{H|HHHHHtIvIwIxIJJJ JJJJJKKKKKKKKLLLLLLLLgMhMiMnMMMMM^N`NaNfNNNNNNNNNORRR SQSSSTTUVVVVVVWWWWXXXXYYYYx[z[{[[\\\\\\\\\_]_^_____Y``aaaaaaaaSbUbVbWbccccWdddJee fufwfxfyfffffggggg h\h^h_hdh i i iiiiiijjjj>k@kAkBkmmmm-n/n0n5nnnnnooo oooooppppqqqqVrXrYrZrssss?tAtBtGtttttFuuu`vvvvvxy3znzz{2{,|r}}}}}~Ѐ NăɃʃσ?̈́τЄՄ4R`bchQ]eo׊يڊۊ[]^c!"#ŽÎĎŎMNOTKLMR&'(-֔"Dj@=bСԡ¢#$%*9^Z[\açħŧ0127-oѩ#QSTUīūƫ˫OQRS%&'(efgl$ˮͮήϮ   !RTUZ߶$=[9;<A[]^xJ1PP5p0oCQUbghm _abcQRSXFHINrstuacdiGIJO@ABG'i(?IJKP ]-0238]_`e$^'+RAimz   467<$&',$ !crstu#$%*q$V;=>?m        < C K Z e g h i     x        " # $ )     5 7 8 L o\mJhjklqrsxdefgwvwx}*,-.BCDEFG1234&'(-]_`ar   b!d!e!f!!!!!""""####g$h$i$n$U%%%#&%&&&+&'f'''''')))) ****+ + ++B,,,-----........////////M000000,1-1.13111112222=3>3?3D34444555!5(6*6+606+7-7.7/77777;8=8>8C888889999-:.:/:4:::::r;s;t;y;9<;<<<=<<<<<== >7>[>>>>/?R?q@A CCCDDDEEE>FF?HKHIIIIIIaJcJdJeJ K K KKQKSKTKYKKKKK0L2L3L8LLLLLSMUMVMWMMMMM;N=N>N?NNNNNOOOOPPPPPPPPPPPP"Q$Q%Q&Q_Q`QaQfQPRRRSRTRRRRR S S SSCSESFSKS!T#T$T)TTTT U5UEUGUHUMUUUUU:VSVjVVVVVVVbWdWeWfWWWWWXXZX[X`XYYYYYYYYZZZZC[D[E[J[[[[[[[[[[[[[\\\$\/]1]2]3]^^^$^^^^^` `!`"` a aaaaaaabbbb_dadbdcdneoepeqe6f7f8f=fggggggggh h!h"hhhhhii i%iiiii5j6j7jw?w@wwwwwyyyyyzzzb{c{d{e{`|a|b|c|}}}}~~~~~~(C\^_`9:;@́߁-=lmns:<=Q- $9>?@STUVyz{||}~Z\]q!v>Nq-RTUZ   :<=BڔܔݔHŗҗחؗݗZ\]bNPQV >.B!_cpuv{SUVW.016wyzrtuzQRSX1349ΩDFGHíŭƭ˭RTU,bͱԲƷ0޸madz~\^_dμмѼҼnpqvDFGLhijosuvw()*+     !& 3FHINEGHIYZ[`pIJnp|pwI] F.016amMjxWYZ_+cnt+016fhijwBCDI)9DLoqrwklmr,./0<>?@",-.3QVXY^.xz{|ijkp'QhMNOT[]^_jlmr1238DFGLXzK I   ; n    H v 9 [I~2E3st)V*vo9c9)O\!   6!U!p!!!"###$&&''()g)))$*l***++C,,.-k--Q.u... /0r111z2222223 33I4j444"55 6n67878U999F:g:::;;;;^<<!=O=== >H>l>>#?O?`???hAAAA#BBBCCDEEEF9FF*GMGGG H9HRHHH7IJJ0KbKKKLLKM|MM3NOSPzPPPQQQSTATTTTUVVLWWXPYYYYDZiZZZ5[~[[,\@]^_`j```Laa$bybbb$c^ccef=ffffg3ghhibi*jBjcjj kJkvkkkkkSlllm`mmnnmooopp+qqpshtvvvwwwYy[yhyymzzz{|}}}}~~~~&QZ*U\lΆRY$#/%:EwMF1 5iǚ?՝2_jsʢȣϣݣ %),045JMQUYZäƤʤΤϤ!%)-12LORUXYpsw{ťɥͥΥCFJNRSehlptu¦ŦȦɦNQTX\]ӧקۧߧ 8;>BFGhknquvϨ9:>[vwx%&''()ج٬ڬX, VWXDEFpdefD¶նݷVXd7<2h}902>cdr auF'(@QRduv./<WXgxy#$4OPars(8 OPjklJ[^_{  !"6BCV_`x{|HIbq!0%ABVb}~/0@L#RSkw0<YZjv)5NO_k (FGWc 01@LMN[g@AVb78HT  (?@Tbtu  (BCR`lmz)7KL]k&':HZ[jx$:;M[op= xy   ()+45atu%&'.567FPQRahij|'().89:LVWXfpqry*126DKLMV]^_hrst{  #$%29:;IPQR[bcdmtuv(/01 67KZ[gz{"Ciju~ &')Fp234iwJDRyIJUklztu}cdm  rs}';<I"#/   h i o \ ] b    @ A T e    ) * /    kl{|  JKnoN<) "V##$$$&&(())**q+z+-#---..r.z..C0D0M0T0\0`0i0r0y00000111111 1!1"1#111P1R1T1U1V1W1X1Y1Z1[1i111111111111111111111111222426282:2<2=2>2?2H2222222222222222222333 3.3/31333537393:3;3<3G333333333333*4+4-4.4/40414243444>444444444444555555 5"5#5$5.555555555555666666 6!6"6#6-6`6b6d6e6f6g6h6i6j6k6u666666666666667777777 7797:7<7>7@7B7D7E7F7G7Q777777777777777777777778888888888(8888888888889999999999$9>9@9B9C9D9E9F9G9H9I9O999999999999999::::::: :+:-:/:1:3:5:7:8:9:::g::;<!=C======> >>>>> >!>1>2>5>B>D>Q>R>V>a>e>p>q>u>>>>>>>>>>>"?&?O?P?T???????????@$@G@H@L@q@v@@@@@@@@@@@AAA-A1AAABAFASAWAdAeAiAAAAAAAAAAABB>B?BCBUBYBkBlBpBxB|BBBBBBBBBCCCCC%C)C0C1C5CBCGCTCUCYCnCrCCCCCCCCCCCCCDDD.D/D1DHDJDdDeDiD}DDDDDDDDDDDDE E"E4E6EVEWE[EcEgEoEpEtEEEEEEEEEEEEEEEF FFFFF@FBFhFiFmFFFFFFFFFFFFGGGG-G1GEGFGHGaGcG|G}GGGGGGGGGGGGGH+H,H/HCHFHWHXH]HHHHHHHHIII)I.I]I^IcIlIqIzI{IIIIIIIIIIIIIIJJJ4J5JaJbJeJJJJJJJJJJJJJKK K K&K:K;K@KTKYKmKnKsKKKKKKKL1L2L7LjLoLLLLLLLLLLLLLL*M3M@MAMFMnMyMMMMMMMMM7NBNeNfNkNNNNNNNN O OO1OU`UiUUUUUVVWVWE 0?E 0@E0E 0AE 0BE 0CE 0DE 0EE 0FE0E0P0_0_0_0_0_ 0G_ 0H_0_0P0000000P00000000P0v0v0P000P000000! 0PP000 0I 0J 0K 0L 0M 0N000000000000! 00000 0O 0P 0Q 0R000000 0S 0T00! 00 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0U 0V 0W 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0X 0Y 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0 0 0Z 0[ 0\ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0] 0^ 0_ 0` 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 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% 0a% 0b% 0c% 0d% 0e% 0f% 0g% 0% 0% ! 0%% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% ! 0%% 0% 0% 0% 0% 0%0% 0% 0% ! 0 %% 0% 0% 0% 0% 0%0%0% 0% 0% 0% 0% 0% 0% ! 0 %% 0% 0% 0% 0% 0% 0% 0% ! 0 %% 0% 0% 0% ! 0 %% 0% 0% 0% ! 0 %% 0% 0% 0% 0% 0% 0% 0% ! 0%% 0% 0% 0% ! 0%% 0% 0% 0% ! 0%% 0% 0% 0% 0% 0% 0% 0% ! 00;0; 0h; 0i;0;0; 0j; 0k;0;0;0; 0l; 0m; 0n; 0o; 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; 0q; 0r; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; ! 0;; 0; 0s; 0t; 0; 0; ! 0;; 0; 0; 0; ! 0;; 0; 0; 0; 0; 0; 0; 0; ! 0;; 0; 0; 0; ! 0;; 0; 0; 0; ! 0;; 0; 0; 0; ! 0 ;; 0; 0; 0; 0; 0; 0; 0; ! 0 ;; 0; 0; 0; 0; 0; 0; 0; ! 0 ;; 0; 0; 0; ! 0 ;; 0; 0; 0; ! 0 ;; 0; 0; 0; ! 0;; 0; 0; 0; ! 0;; 0; 0; 0; 0; 0; 0; 0; ! 0;; 0; 0; 0; 0; 0; 0; 0; ! 0;; 0; 0; 0; ! 0;; 0; 0; 0; ! 00X0X 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0uX 0vX 0X 0X ! 0XX 0X 0X 0X 0X 0X 0wX 0xX 0yX 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X 0X 0X0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0zX 0{X 0|X 0X 0X ! 0XX 0X 0X 0X ! 0XX 0X 0X 0X ! 0 XX 0X 0X 0X ! 0 XX 0X 0}X 0~X0X 0X 0X ! 0 XX 0X 0X 0X 0X 0X 0X 0X ! 0 XX 0X 0X 0X 0X 0X 0X 0X 0X 0X 0X 0X ! 0 XX 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X ! 0XX 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X0X 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X ! 0XX 0X 0X 0X ! 0XX 0X 0X 0X 0X 0X 0X 0X ! 00х0х0х0х0х0х! 0хх00000000000 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0хх0d0d0d0d0d0d0d0d 0d 0d 0d ! 0dd 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d ! 0dd 0d 0d 0d ! 0dd 0d 0d 0d 0d 0d 0d 0d ! 0dd 0d 0d 0d ! 0dd 0d 0d 0d 0d 0d 0d 0d ! 0dd 0d 0d 0d ! 0dd 0d 0d 0d 0d 0d 0d 0d ! 0dd 0d 0d 0d ! 0dd 0d 0d 0d ! 0 dd 0d 0d 0d ! 0 dd 0d 0d 0d 0d 0d 0d 0d ! 0 dd 0d 0d 0d ! 0 dd 0d 0d 0d 0d 0d 0d 0d ! 0 dd 0d 0d 0d ! 0dd 0d 0d 0d 0d 0d 0d 0d ! 0dd 0d 0d 0d 0d 0d 0d 0d ! 0хх0000 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0хх0)0)0)0) 0) 0) 0) ! 0)) 0) 0) 0) 0) 0) 0) 0) ! 0)) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0)0) 0) 0) ! 0)) 0) 0) 0) 0) 0) 0) 0) ! 0)) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) 0) ! 0)) 0) 0) 0) 0) 0) 0) 0) ! 00000! 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 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 ! 0  0 0 0 ! 0  0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 00 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 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 00 00 0 0 0 0 0 0 0 0 0 0 0 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 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0  0 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 0 0 0 ! 0' 0 0 0 ! 0( 0 0 0 ! 0) 0 0 0 ! 0* 0 0 0 ! 0000000 00 00 00 ! 000 00 00 00 ! 000 00 00 00 00 00 00 00 ! 000 00 00 00 ! 000 00 00 00 00 00 00 00 00 00 00 00 ! 000 00 00 00 ! 000 00 00 00 ! 000 00 00 00 00 00 00 00 ! 000 00 00 00 000000 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%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0 %<%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0 %<%< 0%< 0%< 0%< ! 0 %<%< 0%< 0%< 0%< ! 0 %<%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0 %<%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< 0%<0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< ! 0%<%< 0%< 0%< 0%< 0%<! 00`0`0`0`0b0b0b0b0b! 0``0Fh0Fh0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0 Fh 0 Fh0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0 FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0 FhFh 0Fh 0Fh 0Fh ! 0 FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0 FhFh 0Fh 0Fh 0Fh ! 0 FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0 Fh 0 Fh0Fh 0Fh 0Fh ! 0FhFh 0Fh 0 Fh 0Fh 0Fh 0Fh 0Fh 0Fh0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0 FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0!FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0"FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0#FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0$FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0%FhFh 0Fh 0Fh 0Fh ! 0&FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0'FhFh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0(FhFh 0Fh 0Fh 0 Fh0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh 0Fh ! 0``0 0! 0" 0# 0$ 0%0000 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0& 0' 0( 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0) 0* 0+ 0, 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0- 0. 0/ 00 0 0 ! 0 0 0 0 0 0 0 0 ! 0``0`030303030`0 010 020 0300 04 05 0600 0 0 0 ! 0! 0 0 0 ! 0! 0 0 0 0 0 0 0 0 0 0 0 ! 0! 0 07 08 09 0: 0 0 0 0 0 0 ! 0! 0 0; 0< 0= 0> 0 0 0 0 0 0 ! 0! 0 0? 0@ 0A 0B 0C 0D 0E0 0 0 0 0 0 0 0 0 0 0 ! 0! 0 0 0 0 0 0 0 ! 0! 0 0F 0G 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 0I0 0J0 0 0 ! 0! 0 0K0 0L0 0 0 0 0 0 0 ! 0! 0 0 0 0 0 0 0 ! 0! 0 0 0 ! 0``0 0M 0N 0O 0P00 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0``00 0Q 0R00 0S 0T 0U0000 0V 0W 0X 0Y00 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0Z 0[ 0\ 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0] 0^ 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 0 0 0 0 ! 0  0 0 0 ! 0  0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0_ 0` 0a 0b 0c 0d 0e 0f 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 00 0  0g  0h 0  0i  0j  0k 0 0 0 0 0 0 0 0 0 0 0 0 0  0l  0m  0n  0o 0 0 0 ! 0  0 0 0 0 ! 0 0 0p 0q 0r 0s 0t 0u 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0v 0w 0x 0y 0z 0 0 ! 0 0 0 0 ! 0 0 0{ 0| 0} 0~ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 00 0 0 0 0 0 0 0 0 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* ! 0** 0* 0* 0* ! 0** 0* 0* 0* 0* 0* 0* 0* 0* 0* 0* 0* ! 0** 0* 0* 0* 0* 0* 0* 0* 0* 0* 0* 0* ! 0** 0* 0* 0* 0* 0* 0* 0* ! 003030303! 033080808 08 08 08 ! 088 08 08 08 ! 088 08 08 0808 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 ! 0 88 08 08 08 ! 0 88 08 08 08 08 08 08 08 ! 0 88 08 08 08 08 08 08 08 08 08 ! 0 88 08 08 08 08 0808 08 08 ! 0 88 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 ! 088 08 08 08 0808 08 08 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 08 ! 088 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 0808 08 08 08 08 08 ! 088 08 08 08 ! 088 08 08 08 ! 088 08 08 08 ! 088 08 08 08 08 08 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 ! 088 08 08 08 ! 0 88 08 08 08 08 08 08 08 ! 0330`0` 0` 0` 0` ! 0`` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` 0` ! 0`` 0` 0` 0` 0` 0` 0` 0` ! 0`` 0` 0` 0` 0` 0` 0` 0` ! 0330$j0$j0$j0$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j ! 0 $j$j 0$j 0$j 0$j ! 0 $j$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j ! 0 $j$j 0$j 0$j 0$j ! 0 $j$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j ! 0 $j$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j ! 0$j$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j 0$j ! 0330|0| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| ! 00}0} 0} 0} 0}0} 0} 0}0}0}! 0}}000 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0}}0|0| 0| 0| 0| 0| 0|0|0|0| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| ! 0 || 0| 0| 0| 0| 0| 0| 0| 0| 0| ! 0 || 0| 0| 0| 0| 0| 0| ! 0 || 0| 0| 0| 0| 0| 0| ! 0 || 0| 0| 0| 0| 0| 0| ! 0 || 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| 0| 0| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| ! 0|| 0| 0| 0| ! 0 || 0| 0| 0| ! 0!|| 0| 0| 0| ! 0}}0g0g0g0g 0g 0g0g0g0g0g0g0g0g 0g 0g 0g ! 0gg 0g 0g 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g 0g 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g 0g 0g 0g 0g 0g 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g ! 0 gg 0g 0g 0g 0g 0g 0g 0g ! 0 gg 0g 0g 0g 0g 0g 0g 0g 0g 0g 0g 0g ! 0 gg 0g 0g 0g ! 0 gg 0g 0g 0g ! 0 gg 0g 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g ! 0gg 0g 0g 0g ! 0gg 0g 0g 0g 0g 0g 0g 0g ! 0gg 0g 0g 0g ! 0gg 0g 0g 0g ! 0gg 0g 0g 0g ! 0 000 0 0 0 0 0 0 0 0 0 0 0 0 0000! 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( 0( 0( 0( ! 0(( 0( 0( 0( ! 0(( 0( 0( 0( ! 0 (( 0( 0( 0( ! 0 (( 0( 0( 0( ! 0 (( 0( 0( 0( ! 0 (( 0( 0( 0( ! 0 (( 0( 0( 0( ! 0(( 0( 0( 0( 0( 0( 0( 0( ! 0(( 0( 0( 0( 0( 0( 0( 0( ! 0(( 0( 0( 0( 0( 0( 0( 0( 0( 0( ! 0(( 0( 0( 0( ! 0(( 0( 0( 0( ! 0(( 0( 0( 0( 0( 0( 0( 0( ! 0(( 0( 0( 0( 0( 0( 0( 0( ! 0(( 0( 0( 0( 0( 0( 0( 0( 0( 0( 0( 0 ( 0( 0( ! 0(( 0( 0 ( 0 ( 0( 0( ! 0(( 0( 0( 0( 0( 0( 0( 0( ! 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+ ! 000000 0 0 0  0  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 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 0 0 0 0" 0# 0$ 0 0 ! 0  0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0% 0& 0' 0( 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0) 0* 0 0 0 0 0 0 ! 0 0 0+ 0, 0- 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0. 0/ 00 010 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0  0 0 0 ! 00P*0P*0P* 02P* 03P* 04P* 05P* 06P* 07P*0P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* 0P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0 P*P* 0P* 0P* 0P* ! 0 P*P* 0P* 0P* 0P* ! 0 P*P* 0P* 0P* 0P* ! 0 P*P* 0P* 08P* 09P* 0:P* 0P* 0P* ! 0 P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* 0P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* 0P* 0P* 0;P* 0<P* 0=P* 0P* 0P* 0P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0>P* 0?P* 0@P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* 0P* 0P* 0P* 0P* ! 0P*P* 0P* 0AP*0P* 0BP*0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* 0P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* ! 0P*P* 0P* 0P* 0P* 0P* 0P* 0P* 0P* ! 0 P*P* 0P* 0P* 0P* ! 0!P*P* 0P* 0P* 0P* 0P* 0P* 0P* 0P* ! 0"P*P* 0P* 0P* 0P* 0P* 0P* 0P* 0P* ! 0#P*P* 0P* 0P* 0P* ! 0$P*P* 0P* 0P* 0P* ! 0%P*P* 0P* 0P* 0P* ! 0&P*P* 0P* 0P* 0P* ! 0'P*P* 0P* 0P* 0P* 0P* 0P* 0P* 0P* ! 0(P*P* 0P* 0P* 0P* ! 0)P*P* 0P* 0P* 0P* ! 0*P*P* 0P* 0P* 0P* ! 0+P*P* 0P* 0P* 0P* ! 00O0O0O 0CO 0DO 0EO 0FO 0GO 0HO 0IO0O0O0O 0O 0O 0O ! 0OO 0O 0O 0O 0O 0O 0O 0O ! 0OO 0O 0O 0O ! 0OO 0O 0O 0O ! 0OO 0O 0O 0O 0O 0O 0O 0O 0O 0O 0O 0O 0O 0O 0JO 0KO 0LO 0MO 0O 0O ! 0OO 0O 0O 0O ! 0OO 0O 0O 0O 0O 0O 0O 0O ! 0OO 0O 0NO 0OO 0PO 0QO 0RO 0SO 0O 0O 0O 0O 0O 0O 0O 0O 0O 0O ! 0OO 0O 0TO 0UO 0O 0O ! 0OO 0O 0O 0O ! 0 OO 0O 0O 0O 0O 0O 0O 0O ! 0 OO 0O 0O 0O 0O 0O 0O 0O ! 0 OO 0O 0O 0O ! 0 OO 0O 0O 0O 0O 0O 0O 0O ! 0 OO 0O 0O 0O 0O 0O 0O 0O ! 0OO 0O 0O 0O ! 0OO 0O 0O 0O 0O 0O 0O 0O ! 0OO 0O 0O 0O ! 0OO 0O 0O 0O ! 0OO 0O 0VO 0WO 0XO 0YO 0O 0O ! 00v0v 0Zv 0[v 0\v 0]v 0^v0v0v0v0v0v0v 0_v 0`v 0av0v 0bv 0cv 0dv0v0v0v 0v 0v 0v ! 0vv 0v 0ev0v 0fv 0v 0v ! 0vv 0v 0gv 0hv 0v 0v ! 0vv 0v 0v 0v 0v 0v 0iv 0jv 0kv 0lv 0mv 0nv0v 0v 0v 0v 0v 0v 0v ! 0vv 0v 0v 0v ! 0vv 0v 0v 0v 0v 0v 0v 0v ! 0vv 0v 0v 0v ! 0vv 0v 0v 0v 0v 0v 0v 0v 0v 0v 0v 0v ! 0vv 0v 0v 0v ! 0vv 0v 0v 0v 0v 0v 0v 0v ! 0 vv 0v 0v 0v 0v 0v 0v 0v ! 0 vv 0v 0v 0v ! 000 0o 0p 0q 0r0000000 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0s 0t 0u 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0v 0w 0x 0y 0z 0{ 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0| 0} 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0  0 0 0 0 0 0 0 ! 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? ! 0000 0 0 0 0 0000 0 0000 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0,0,0,0, 0, 0, 0, ! 0,, 0, 0, 0, ! 0,, 0, 0, 0, ! 0,, 0, 0, 0, 0, 0, 0, 0, ! 0,, 0, 0, 0, 0, 0, 0, 0, ! 0,, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, ! 0,, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, ! 0,, 0, 0, 0, ! 0,, 0, 0, 0, 0, 0, 0, 0, ! 0,, 0, 0, 0, ! 0 ,, 0, 0, 0, ! 0 ,, 0, 0, 0, 0, 0, 0, 0, ! 0 ,, 0, 0, 0, ! 0 ,, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, ! 0 ,, 0, 0, 0, ! 0,, 0, 0, 0, 0, 0, 0, 0, ! 0,, 0, 0, 0, ! 0,, 0, 0, 0, ! 0 00 0 0 0000000 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 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 00000 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0  0 0 0 ! 0 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  0a  1a  1a  0a  1a  1a  0a  1a  1a  0a  1a  1a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a 0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0 a a  0a  0a  0a  0a  0a  0a  ! 0 a a  0a  0a  0a  0a  0a  0a  ! 0 a a  0a  0a  0a  ! 0 a a  0a  0a  0a  ! 0 a a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  ! 0a a  0a  0a  0a  ! 0a a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  ! 0a a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0a a  0a  0a  0a  0a  0a  0a  0a  ! 0 0<0< 0< 0< 0< 0< 0< 0< 0< 0<0<0<0<0<0<0<0<0<0<0<0<0<0<0<! 0<<0hH0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0 hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0 hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0 hHhH 0hH 0hH 0hH ! 0 hHhH 0hH 0hH 0hH ! 0 hHhH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH ! 0hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0 hHhH 0hH 0hH 0hH ! 0!hHhH 0hH 0hH 0hH 0hH 0hH 0hH 0hH ! 0<<0zk0zk 0zk 0zk 0zk 0zk0zk0zk0zk0zk0zk0zk 0zk 0zk 0zk ! 0zkzk 0zk 0zk 0zk 0zk 0zk 0zk 0zk ! 0zkzk 0zk 0zk 0zk 0zk 0zk 0zk 0zk ! 0zkzk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk ! 0zkzk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk ! 0zkzk 0zk 0zk 0zk 0zk 0zk 0zk 0zk ! 0zkzk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk ! 0zkzk 0zk 0zk 0zk 0zk 0zk 0zk 0zk ! 0zkzk 0zk 0zk 0zk 0zk 0zk 0zk 0zk 0zk0zk 0zk 0zk 0zk 0zk 0zk 0zk ! 0zkzk 0zk 0zk 0zk ! 0<<0f0f0f 0f 0f 0f ! 0ff 0f 0f 0f ! 0ff 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f ! 0ff 0f 0f 0f 0f 0f 0f 0f ! 0ff 0f 0f 0f 0f 0f 0f 0f ! 0ff 0f 0f 0f ! 0<<00 0 0 0 0 0 0 0 00000 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0<<00000 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0 0 0 0 ! 0<<08080808 08 080808 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 ! 088 08 08 08 ! 088 08 08 08 ! 088 08 08 08 ! 088 08 08 08 08 08 08 08 ! 088 08 08 08 ! 088 08 08 08 ! 0 88 08 08 08 08 08 ! 0 88 08 08 08 ! 0 88 08 08 08 08 08 08 08 ! 0 88 08 08 08 08 08 08 08 ! 0 88 08 08 08 ! 088 08 08 08 ! 0<<0<0 0 0 000<00 0 0 00<00<00 0 0 0 00 0 000<0 0 0 0 ! 0~ 0 0 0 ! 0~ 0 0 0 0 0 0 0 ! 0~ 0 0 0 ! 0~ 0 0 0 ! 0~ 0 0 0 ! 0~ 0 0 0 ! 0~ 0 0 0 0 0 0 0 ! 0~ 0 0 0 0 0 0 0 ! 0~ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ! 0 ~ 0 0 0 ! 0 ~ 0 0 0 0 0 0 0 ! 0 ~ 0 0 0 ! 0 ~ 0 0 0 0 0 ! 0 ~ 0 0 0 0 0 0 0 ! 0~ 0 0 0 0 0 0 0 ! 0~ 0 0 0 0 0 0 0 ! 0~ 0 0 0 ! 0<<0 0 0  0  0  0 0 0 0 0 0  0  0  0  ! 0   0  0  0  ! 0   0  0  0  ! 0   0  0  0  0  0  0  0  0  0  0  0  0  0  ! 0   0  0  0  ! 0   0  0  0  0   0   0  0  ! 0   0  0  0  0  0  0  0  ! 0   0  0  0  ! 0   0  0   0   0   0  0  ! 0   0  0  0  0  0  0  0  0  0  0  0  0  0  ! 0   0  0  0  ! 0   0  0  0  0  0  0  0  ! 0 0>0>! 0>>0>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%% 0% 0% 0% 0% 0% 0% 0% ! 0%% 0% 0% 0% ! 0%% 0% 0% 0% 0% 0% 0% 0% ! 0%% 0% 0% 0% ! 0 %% 0% 0% 0% 0% 0% 0% 0% ! 0 %% 0% 0% 0% 0% 0% 0% 0% ! 0 %% 0% 0% 0% ! 0 %% 0% 0 % 0!% 0"% 0#% 0$% 0% 0% ! 0 %% 0% 0%% 0&% 0'% 0% 0% 0% 0% 0% 0% ! 0%% 0% 0% 0% ! 0%% 0% 0% 0% 0% 0% 0% 0% ! 0%% 0% 0(% 0)% 0*% 0+%0% 0% 0% 0% 0% 0% 0% ! 0%% 0% 0% 0% ! 0%% 0% 0% 0% 0% 0% 0% 0% ! 0%% 0% 0% 0% ! 0%% 0% 0% 0% ! 0%% 0% 0% 0% 0% 0% 0% 0% ! 0%% 0% 0% 0% ! 0%% 0% 0% 0% ! 0 00 0, 0- 0. 0/! 0080808080808080808080808080808080808080808080808080808080808080808080808 008 018 028 03808 048 058 068 078 088 0980808080808080808080808080808080808080808080808080808 0:8 0;80808 0<8 0=8 0>808080808080808080808080808080808080808080808080808 0?8 0@8 0A8 0B8 0C8 0D8 0E80808080808080808080808080808080808080808080808080808080808 0F8 0G8 0H8 0I8 0J808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808 0K8 0L80808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808! 00p0p0p0p0p0p0p0p0p0p0p0p0p! 00y0y00z00(| 0M(| 0N(| 0O(|0(|008~ 0P8~ 0Q8~ 0R8~08~00z 0Sz 0Tz0z00~0~0~0000{0{0{00L00! 00N0N0N0N0N 0UN 0VN 0WN 0XN0N0N0N0N0N0N0N0N0N0N0N0N0N0N 0YN 0ZN 0[N 0\N 0]N 0^N 0_N0N0N0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N0N 0N0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 0N 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Ԩ 0Ԩ0000000 0` 0a 0b 0c0000000000000000000000 0d 0e 0 0 0f 0 0  0 00000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000Q0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 0Q 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  000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0000: 0g: 0h:0:000 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000:0 0i 0j 0k00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 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 0000000000 0 00000000000000A0m0m0m0m0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0m 0A0j  0j  0j  0j  0j  0j  0j  0j  0j  0j  0j  0j  0j  0j  0j  0A000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0A0 0 0 0 0A00000 0l 0m 0n 0o 0p000000000000000000000000000000000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00c:0:0:0:0c:0J=0J=0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J=0J= 0J=0J= 0J= 0J= 0J= 0J=0J= 0J=0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J= 0J=10U0U@1@1@1@1@1@100@0h00@0h00@0h00@0h00@0@0@0@0@0@0@0@0@0@1@1@0@0@0@0@0h00  ###::iiilllloor~ q ^OB'  !"#$%&p'`(U)~*W+',2-(.K/l07123>]vԑ9:g^e zb8<IJUTm)~>v|Pf-G@FZJjwjZbr A6ZViwE <"JgsyrR 'ImLj?J\L;4sBWKe@ƳlgE@erqko0;wA'DSFH[DJQ]degilwx[>Qڧ0bjd;g@h "*27@\bv}%9Ng}7UfoKh0^} " D m ~ 7 D a m     l    1 7 = B I M Q \ cG q *4)ABFHX\]e_`ttvxxxyڄ8B8lJ3o*5Hw,F"   %  @ -fMf}H,Qc !!"#$|%\')*+,,-U..01F223{446B8Z89;;<W==>>>s??)@@CbD\FGHII@JJKLNNjOOrPzSU1XXYkZA[\Z^__Paa-bbcccQdd~eedffgggLhieiejlllDs(touuvvFwx3yy{|}~2mO6) 1&ؐ'ޕ2֘OX .vAO> `WL`ӺE^R 3W2KO@b7 jEm>=Kb=4u#$0GIgOv-D%ySLN  _ >AU$6^#$&'h,./06273z34 556+6679<=o>!??G@CD[EFGNIIbJ)K8LVN>PPIQQ RNTT3UU$VpWMX8Y[\]]^^5__%`d`aa,bc?ddhhiOjjkl'mmmwnnJoEpqqwwy1zz{| }&~~%xV˂4 È+1Y <<6Qj(>Ɯ ΝL]ū 8jxЮH7ѰҲ>/q2ҷGʻ{XϽٿxQ9][(|RY J&+q *T.$'t&PF)o,H9R8~pKJe   c   p WFHi4f   @!B#$y$$%%S&&'u((G))1**+,X--.3//'0s01253c4 5G56V6677\869k;;?@CAAQBBBqCCMDD8ECEsEEF;GG=HH*II""_##S$%D*w+,,W-.2/0{0v12T253*46556H77899V::;=CoEG`HHIrJHKKLLMNkOwPQRS+TT UUDVWWXYJYYZ[\I]\]]rapccd gqh@iiijkkllmmnp~pp.qLqrvsrt {T{{|} g?h~ b@QhƋ|! Ɣ.t 9Қ2@{U;x,lgB ?#'+ 9;9!:S:::::0;L;m;;;;<<<l<<<=B=g====>>>>?I??@@AJBBxCKDDEF[s[[[ \B\r\\\]R]]]] ^K^y^^^_=_j__8aBbOb\bsbbbbbbb]dddddde#e1eNe`eseweeeeeeef f2fBfRfqfffffffg"gDg[gugggggghh)h?hXhnhhhhvjjk&kBkYkk ll5lBlUl_lillllmpvkw xxyryyzXzz_{{||4}z}}}B~s~~.O_e[Ƀ|:>%<ZkB05O,lN@rZҹѿiV;wA 2'iFt6o;SpaNo@c hBu0]7#\@\\\]]X]]^E^^^^=___`R`r```8acgggghh:h@h     !#$%&'()+,-./01345689:;<=>?ABCDEFGHIJKLMNOPQRSTUVWXYZ[]^_`acdefghijklmnopqrstuwxyz{|~      !"#$&'()*+,-./012345678:;<=>?@ABCDEFGHIJKLMOPQRSTUVWXYZ[\]^_`abcdefhijklmnopqrstuvwxyz{|~      !"#$%&'()*+,-./012345689:;<=>?@ABCDEFGHIJKLMNOPQRSTVWXYZ[\]^_`abcdeghijklmnpqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJLMNOPQRSTUVWXYZ[\]^_`abcdefgijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]_`abcdefghijklmnopqrstuvwxyz{|~                          ! # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l n o p q r s t u v w x y z { | }                            ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 8 9 : ; < = > ? @ A B C E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` b c d e f g h i j k l n o p q r s t u v w x y z { | } ~                        i j k m n o p q r s t u v w x y z { | } ~                         ! " # $ % & ' ( ) * + , - . / 0 2 3 4 5 6 8 9 : ; < > ? @ A C D E F G H J K L N O P R S T U V W X Y Z [ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~  ?hTjk   /?[]^`578:Zp B ^ ` a c ) E G H J j     9 R n p q s $ @ B C E e 2 N Q R T t !$%'Gr (DGHJj 3?[^_a  0C_bce*-.0PsA]`ac(?[^_a 1A]`ac9c'CGHJj%B^bce6d@\`ac <@ACcr9UYZ\|  /Okopr.235Ul .JNOQq  + E a e f h !/!3!4!6!V!!!!!!!"#"'"("*"J"c"""""""""""##1#5#6#8#X#|###########$&$B$F$G$I$i$$$$$$$$ %%%%3%N%j%n%o%q%%%%%%%%)&E&I&J&L&l&&&&&&& '%')'*','L'y'''''''''''(J(f(j(k(m((((((((())))6)b)~)))))))))) *P*l*p*q*s*******+3+O+S+T+V+v++++++YZ9Zyyz k{ه9IQ݈"VfnAWt2:Xu}Gbgx D_d\4S\}9IP&1Iio &1    w   h'''(()@)P)X)))) *-*8*|***///8/S/X////000888888999M<m<y<<@_@m@'OCOIOhXXXXXX2ZRZYZ_ZZZZ[[eeeiiiiiij j'jrrrrrrSwtwwwwwx"y1y~~~7U]<_l؋?_kĜ;I@\b:C&2Ͳղ9IQȴдqڽZ}ɿD_dVfnXhp  #a q y          @PXD!T!\!$$%&&&&''(((6'626BBBEEE_OoOwO:QWQ`Q7TGTOTUTeTmTUUUUUUXXXYYZ\\\aaacddf VfmAQY+((()))h+++G>W>^>z@@@IIINL^LfLlL|LLooorrr"w2w:w&y6y>yzzz ė̗>NVhK[b´ɴ$+ϵֵ-=Dfv}ߺm}ӽ-5?Ii!y!!>,N,V,;;;7ZGZOZ[[[2wLwQw!19ˊӊ&-3CJɒْu!""#(#1#e*u*~*/)/2////2(22222222234 4^9n9w9[MkMsMvMMMMMMYYZu.u6u{vvv<LTWgou5IS_owzP`ioI q  ; ^ l    H h t [}!1t 9TZ(7OwDZ     6!O!S!p!!!(()g))))*"*+++,-,-k---u...r111I4c4h455677 8U9{99F:`:e:: ;;;;;!=A=M=#???F?`?{??hAAAAAABBBDEEEEEF2F7F*GEGKG H,H7HHHHJJJ0KRK`KKLLKMmMzMSPpPxPPPPT3T?TTTTVVVPYrYYDZ`ZgZZZZ~[[[j````'aJaybbb$cJc\cf(f;fffffg ghhhBj\jajJkiktkkkkkkklmmnnnmooo٪#׫֬X}ʮ TAp9avwDhMq6    * e  ) X |     < f   'f<s%[ <rYo?kFqH\XX X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%̕XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]dfr!!^D_YXXXXx(G./"$_ӑEx斷"^"$)voWk{:b$: 9 dlR$(an#HdQ^n?2$ġ{F5>;1"$yz+hY{kר(2$3"GpV2W4:R2$:TD\u"$ʖ}pzW NuR"$C?xAe䝐~ş"$wZ>skR`[X"$P߳^'-u"$Tk_7>^9=v"$(A\t:k"$uit. 7 D"$f#A%<+- l"$ì?OeV"$I2P}vld kr $$@$ -P(    6@@A? C"?t : x#  U# C"?n V c $X99?"`: x# NB W 3 @ TB X C >B x zTB Y C >@   2A ??s"*???rt J   o# C"?n p c $X99?"`J  NB q 3 = ? TB r C >J M TB s C >` b j  C .AMoreq2_RGBZ p l  C .AMoreq2_RGB"?B S  ?(     ;> @4 DRAFT - FOR EC REVIEW PURPOSESArialPowerPlusWaterMarkObject4c"$?   ;> @4 DRAFT - FOR EC REVIEW PURPOSESArialPowerPlusWaterMarkObject5c"$?F  ;T @4 DRAFT - STRICTLY FOR REVIEW PURPOSEs ONLYTimes New RomanPowerPlusWaterMarkObject1c"$?F  ;T @4 DRAFT - STRICTLY FOR REVIEW PURPOSEs ONLYTimes New RomanPowerPlusWaterMarkObject2c"$?  ;> @4 DRAFT - FOR EC REVIEW PURPOSESArialPowerPlusWaterMarkObject1c"$?  ;> @4 DRAFT - FOR EC REVIEW PURPOSESArialPowerPlusWaterMarkObject2c"$?x  S 4AMoreq2_RGB#" `?~\o 2}T j t\ ytUR T!t  #ilr 2t2it 2t2it%t  2t  2tk _Hlt178479200 _Hlt178479201 _Toc188881249 _Toc201478390 _Toc188881250 _Toc201478391 _Toc188881251 _Toc201478392 _Toc188881252 _Toc201478393 _Toc188881253 _Toc201478394 _Toc188881254 _Toc201478395 _Toc188881255 _Toc201478396 _Toc188881256 _Toc201478397 _Hlt190497527 _Hlt190497528 _Toc188881257 _Toc201478398 _Toc188881258 _Toc201478399 _Toc188881259 _Toc201478400 _Toc188881260 _Toc201478401 _Toc188881261 _Toc201478402 _Toc188881265 _Toc201478403 _Toc188881266 _Toc201478404 _Hlt188934317 _Hlt188934318 _Toc188881267 _Toc201478405 _Toc188881268 _Toc201478406 _Toc188881269 _Toc201478407 OLE_LINK5 _Toc188881270 _Toc201478408 OLE_LINK16 OLE_LINK17 _Toc188881271 _Toc201478409T_ClassificationSchemeT_FilesT_ClassT_Volume T_SubFileT_ERMST_ElectronicRecordT_Record T_CaptureT_Classification _Hlt192581702 _Hlt192581703 _Toc188881272 _Toc201478410Bk2089 _Toc188881273Bk2112 _Toc188881274T_UserBk3355 _Toc188881275T_AdministrativeRole _Hlt188876157 _Hlt188876158 T_Metadata _Hlt192582583T_Export _Hlt189016697 _Hlt189016698Bk2088 _Toc188881276Bk2715 _Toc188881277Bk2765 _Toc188881278 T_UserRoleT_Group T_CaseFileT_GAuthorisedUserT_AuthorisedUser _Hlt189016776Bk2081 _Toc188881279Bk2087 _Toc188881280T_ConfigurationTimeBk2082 _Toc188881281Bk2692 _Toc188881282Bk4921 _Toc188881283T_Import _Hlt192582579Bk2677 _Toc188881284Bk2693 _Toc188881285!T_RetentionandDispositionSchedule T_AuditTrailBk2771 _Toc188881286Bk2773 _Toc188881287Bk2775 _Toc188881288Bk2696 _Toc188881289Bk2697 _Toc188881290Bk2699 _Toc188881291Bk2777 _Toc188881292Bk3175 _Toc188881293Bk3176 _Toc188881294T_Format _Hlt189017073 _Hlt189017351Bk2718 _Toc188881295Bk2720 _Toc188881296Bk2086 _Toc188881297Bk2084 _Toc188881298 _Toc188881299 _Toc201478411Bk2100 _Toc188881300T_PresentationBk2664 _Toc188881301Bk2099 _Toc188881302T_ClassificationCodeBk2665 _Toc188881303 T_Electronic T_NonCaseFileBk2666 _Toc188881304Bk2700 _Toc188881305Bk3740 _Toc188881306Bk2789 _Toc188881307T_OpenT_ClosedBk2701 _Toc188881308Bk2096 _Toc188881309Bk2667 _Toc188881310Bk2668 _Toc188881311Bk2093 _Toc188881312Bk3635 _Toc188881313Bk2092 _Toc188881314Bk2681 _Toc188881315 T_RepetoryBk4218 _Toc188881316 _Toc188881317 _Toc201478412 T_PaperFileT_DocumentTypeBk4201 _Toc188881318Bk4199 _Toc188881319Bk4200 _Toc188881320Bk2104 _Toc188881321Bk2103 _Toc188881322Bk2107 _Toc188881323Bk3650 _Toc188881324Bk5004 _Toc188881325T_CloseBk2106 _Toc188881326Bk2105 _Toc188881327Bk3671 _Toc188881328Bk2115 _Toc188881329Bk2758 _Toc188881330Bk2670 _Toc188881331Bk3659 _Toc188881332Bk3660 _Toc188881333Bk2799 _Toc188881334Bk2801 _Toc188881335Bk3656 _Toc188881336 _Toc188881337 _Toc201478413Bk2123 _Toc188881338Bk4984 _Toc188881339Bk4985 _Toc188881340Bk2717 _Toc188881341Bk5045 _Toc188881342 T_Component _Hlt189018380Bk5034 _Toc188881343Bk5036 _Toc188881344Bk5037 _Toc188881345Bk5038 _Toc188881346Bk4992 _Toc188881347Bk4993 _Toc188881348Bk2674 _Toc188881349Bk4991 _Toc188881350Bk2119 _Toc188881351Bk2120 _Toc188881352Bk3664 _Toc188881353Bk2707 _Toc188881354Bk2708 _Toc188881355Bk2118 _Toc188881356 T_DestructionBk2117 _Toc188881357T_Administrator _Hlt188948972 _Hlt188948973Bk2116 _Toc188881358Bk2704 _Toc188881359Bk2113 _Toc188881360Bk2111 _Toc188881361 T_Document _Hlt188948987Bk2110 _Toc188881362Bk3670 _Toc188881363Bk2053 _Toc188881364Bk2819 _Toc188881365 T_Keyword _Hlt192582456 _Hlt192582535 _Hlt192582576Bk2825 _Toc188881366 _Toc188881367 _Toc201478414T_Authenticity T_VitalRecord _Toc188881368 _Toc201478415T_Role _Hlt188945237Bk4391 _Toc188881369Bk2136 _Toc188881370 T_UserGroup _Hlt188945362Bk4214 _Toc188881371Bk2135 _Toc188881372Bk3186 _Toc188881373T_SecurityClearanceBk3226 _Toc188881374Bk3202 _Toc188881375Bk3229 _Toc188881376Bk3227 _Toc188881377Bk2134 _Toc188881378Bk3239 _Toc188881379Bk2133 _Toc188881380Bk2132 _Toc188881381Bk3205 _Toc188881382Bk2166 _Toc188881383Bk2131 _Toc188881384 T_UserProfileBk2130 _Toc188881385OwnerUserProfileT_OwnerBk2129 _Toc188881386 T_ProfileBk3268 _Toc188881387Bk3272 _Toc188881388 T_CaseWorkerBk4977 _Toc188881389Bk2127 _Toc188881390Bk2128 _Toc188881391Bk4393 _Toc188881392 _Toc187464961 _Toc187464966 _Toc187464971 _Toc187464976 _Toc188881393 _Toc201478416Bk2149 _Toc188881394 T_Disposition _Hlt189017604T_DisposalHold T_TransferBk4664 _Toc188881395Bk4366 _Toc188881396 T_AggregationBk3237 _Toc188881397Bk4210 _Toc188881398Bk2148 _Toc188881399Bk2147 _Toc188881400Bk2146 _Toc188881401 OLE_LINK12BK4924 _Toc188881402Bk3223 _Toc188881403Bk2145 _Toc188881404Bk2142 _Toc188881405Bk3212 _Toc188881406Bk4363 _Toc188881407Bk2141 _Toc188881408Bk2140 _Toc188881409 _Toc188881410 _Toc201478417T_EDMSBk2157 _Toc188881411Bk2156 _Toc188881412Bk2155 _Toc188881413Bk4370 _Toc188881414Bk2154 _Toc188881415 _Toc188881416 _Toc201478418Bk2152 _Toc188881417Bk2151 _Toc188881418Bk4373 _Toc188881419Bk4375 _Toc188881420Bk3218 _Toc188881421 _Toc188881422 _Toc201478419 T_RecordType _Toc188881423 _Toc201478420Bk2199 _Toc188881424Bk2977 _Toc188881425Bk3685 _Toc188881426Bk2953 _Toc188881427Bk4446 _Toc188881428Bk2951 _Toc188881429Bk2960 _Toc188881430Bk3688 _Toc188881431Bk2952 _Toc188881432Bk2980 _Toc188881433Bk3692 _Toc188881434Bk4625 _Toc188881435Bk4626 _Toc188881436Bk2197 _Toc188881437Bk2969 _Toc188881438Bk2196 _Toc188881439Bk2195 _Toc188881440Bk2988 _Toc188881441 OLE_LINK7 OLE_LINK8Bk2194 _Toc188881442 _Ref193708610Bk4761 _Toc188881443Bk3699 _Toc188881444Bk2193 _Toc188881445Bk2192 _Toc188881446Bk2191 _Toc188881447Bk2190 _Toc188881448Bk3707 _Toc188881449Bk2189 _Toc188881450Bk2188 _Toc188881451Bk2957 _Toc188881452Bk4041 _Toc188881453Bk4042 _Toc188881454Bk2186 _Toc188881455Bk2183 _Toc188881456Bk2971 _Toc188881457Bk4452 _Toc188881458 _Ref193708770Bk2972 _Toc188881459Bk2973 _Toc188881460Bk3712 _Toc188881461 OLE_LINK3 OLE_LINK4Bk3714 _Toc188881462Bk3715 _Toc188881463Bk3716 _Toc188881464Bk3717 _Toc188881465Bk3718 _Toc188881466 _Toc188881467 _Toc201478421Bk2211 _Toc188881468Bk2209 _Toc188881469Bk4028 _Toc188881470 T_RenditionBk2207 _Toc188881471Bk2963 _Toc188881472Bk2206 _Toc188881473Bk2203 _Toc188881474Bk2208 _Toc188881475 _Toc188881476 _Toc201478422Bk4695 _Toc188881477Bk4988 _Toc188881478Bk2230 _Toc188881479Bk4953 _Toc188881480Bk2229 _Toc188881481Bk5042 _Toc188881482Bk2922 _Toc188881483Bk3003 _Toc188881484Bk2228 _Toc188881485Bk3357 _Toc188881486Bk2967 _Toc188881487Bk4627 _Toc188881488T_RenderBk2226 _Toc188881489Bk2224 _Toc188881490Bk4628 _Toc188881491T_StubBk2223 _Toc188881492Bk2221 _Toc188881493Bk2975 _Toc188881494Bk2217 _Toc188881495T_MetadataStubBk4852 _Toc188881496Bk2216 _Toc188881497Bk5058 _Toc188881498Bk2215 _Toc188881499Bk4696 _Toc188881500 _Toc188881501 _Toc201478423 T_BulkImport _Hlt188944199 T_DigitalT_Registration _Toc176141909 _Toc176142884 _Toc176143860 _Toc176172267 _Toc176344698 _Toc176486430 _Toc176578315 _Toc176619646 _Toc176626401 _Toc188881502 _Toc201478424T_ElectronicDocumentBk2247 _Toc188881503 T_FileFormatBk2254 _Toc188881504Bk2253 _Toc188881505Bk2235 _Toc188881506Bk4636 _Toc188881507T_PDFA _Hlt188949781Bk4638 _Toc188881508Bk2881 _Toc188881509 T_VersionBk2880 _Toc188881510Bk4790 _Toc188881511 OLE_LINK2 OLE_LINK1Bk2830 _Toc188881512Bk2832 _Toc188881513Bk2833 _Toc188881514T_PDFBk2245 _Toc188881515Bk4494 _Toc188881516Bk2244 _Toc188881517Bk2845 _Toc188881518Bk2234 _Toc188881519Bk2242 _Toc188881520Bk2241 _Toc188881521Bk2240 _Toc188881522Bk2836 _Toc188881523Bk2835 _Toc188881524Bk2807 _Toc188881525Bk4499 _Toc188881526Bk2809 _Toc188881527Bk4691 _Toc188881528Bk4914 _Toc188881529Bk4217 _Toc188881530Bk2239 _Toc188881531Bk2842 _Toc188881532Bk2838 _Toc188881533Bk2238 _Toc188881534Bk2237 _Toc188881535Bk2236 _Toc188881536Bk4394 _Toc188881537Bk4976 _Toc188881538Bk2889 _Toc188881539Bk4692 _Toc188881540Bk2233 _Toc188881541Bk2165 _Toc188881542BK2102 _Toc188881543 _Toc188881544 _Toc201478425Bk5006 _Toc188881545Bk2251 _Toc188881546Bk2846 _Toc188881547Bk2891 _Toc188881548Bk2849 _Toc188881549Bk2893 _Toc188881550Bk2250 _Toc188881551Bk2850 _Toc188881552 _Toc182368365 _Toc182368366 _Toc188881553 _Toc201478426Bk4518 _Toc188881554Bk2894 _Toc188881555Bk2262 _Toc188881556Bk2935 _Toc188881557Bk4515 _Toc188881558 OLE_LINK6 OLE_LINK18Bk4075 _Toc188881559Bk2739 _Toc188881560Bk2744 _Toc188881561Bk4706 _Toc188881562Bk2938 _Toc188881563Bk2740 _Toc188881564Bk2859 _Toc188881565Bk2742 _Toc188881566Bk4470 _Toc188881567Bk2746 _Toc188881568Bk4520 _Toc188881569Bk3704 _Toc188881570Bk2260 _Toc188881571 _Toc188881572 _Toc201478427Bk2709 _Toc188881573Bk2751 _Toc188881574Bk2710 _Toc188881575Bk2897 _Toc188881576Bk2712 _Toc188881577 _Toc188881578 _Toc201478428T_PhysicalFileT_PhysicalRecordBk4117 _Toc188881579Bk4719 _Toc188881580Bk4119 _Toc188881581Bk4120 _Toc188881582Bk4522 _Toc188881583Bk4131 _Toc188881584Bk4122 _Toc188881585Bk4138 _Toc188881586Bk4490 _Toc188881587Bk4124 _Toc188881588Bk4126 _Toc188881589Bk4132 _Toc188881590Bk4711 _Toc188881591Bk4712 _Toc188881592Bk4713 _Toc188881593Bk4715 _Toc188881594Bk4717 _Toc188881595Bk4127 _Toc188881596Bk4133 _Toc188881597Bk4128 _Toc188881598Bk4136 _Toc188881599Bk4524 _Toc188881600Bk4708 _Toc188881601 _Toc188881602 _Toc201478429 _Toc188881603 _Toc201478430Bk2270 _Toc188881604Bk3804 _Toc188881605Bk4919 _Toc188881606Bk2268 _Toc188881607Bk2267 _Toc188881608 _Toc188881609Bk3945 _Toc188881610Bk2266 _Toc188881611Bk2265 _Toc188881612Bk3956 _Toc188881613 _Toc188881614 _Toc201478431Bk3954 _Toc188881615 T_RedactionBk3953 _Toc188881616Bk3951 _Toc188881617Bk3950 _Toc188881618Bk3962 _Toc188881619Bk3959 _Toc188881620 _Toc188881621 _Toc201478432 _Toc188881622 _Toc201478433Bk2300 _Toc188881623Bk2289 _Toc188881624Bk2286 _Toc188881625Bk3896 _Toc188881626Bk2288 _Toc188881627Bk2285 _Toc188881628Bk4074 _Toc188881629Bk2284 _Toc188881630Bk2281 _Toc188881631Bk2273 _Toc188881632Bk2295 _Toc188881633Bk2283 _Toc188881634Bk3787 _Toc188881635Bk2812 _Toc188881636Bk2811 _Toc188881637Bk2280 _Toc188881638Bk3792 _Toc188881639Bk2817 _Toc188881640Bk3898 _Toc188881641Bk2815 _Toc188881642Bk2279 _Toc188881643Bk2278 _Toc188881644Bk2276 _Toc188881645Bk2275 _Toc188881646Bk3797 _Toc188881647Bk2296 _Toc188881648Bk3784 _Toc188881649Bk3764 _Toc188881650Bk2294 _Toc188881651Bk2292 _Toc188881652Bk2291 _Toc188881653Bk2301 _Toc188881654Bk3800 _Toc188881655 _Toc188881656 _Toc201478434Bk2272 _Toc188881657Bk2304 _Toc188881658Bk2303 _Toc188881659 _Toc188881660 _Toc201478435Bk2319 _Toc188881661Bk2318 _Toc188881662Bk2317 _Toc188881663Bk2316 _Toc188881664Bk2315 _Toc188881665T_SecurityCategoryBk4160 _Toc188881666Bk2314 _Toc188881667Bk2313 _Toc188881668Bk2312 _Toc188881669Bk2311 _Toc188881670Bk2824 _Toc188881671Bk4536 _Toc188881672Bk2822 _Toc188881673BK2682 _Toc188881674BK3641 _Toc188881675Bk2091 _Toc188881676Bk3639 _Toc188881677Bk2308 _Toc188881678Bk2307 _Toc188881679 _Toc188881680 _Toc201478436Bk2321 _Toc188881681 _Toc188881682 _Toc201478437 _Toc188881683 _Toc201478438Bk2330 _Toc188881684Bk3904 _Toc188881685Bk2327 _Toc188881686Bk2326 _Toc188881687Bk2324 _Toc188881688 _Toc188881689 _Toc201478439Bk2333 _Toc188881690Bk3917 _Toc188881691Bk4724 _Toc188881692Bk4014 _Toc188881693Bk2335 _Toc188881694Bk2334 _Toc188881695Bk4016 _Toc188881696Bk3919 _Toc188881697Bk3920 _Toc188881698Bk3911 _Toc188881699Bk3912 _Toc188881700Bk4933 _Toc188881701Bk4018 _Toc188881702Bk2138 _Toc188881703Bk4019 _Toc188881704Bk2336 _Toc188881705Bk3910 _Toc188881706Bk2338 _Toc188881707Bk2337 _Toc188881708Bk3915 _Toc188881709Bk3916 _Toc188881710Bk3924 _Toc188881711Bk2332 _Toc188881712Bk3923 _Toc188881713Bk2210 _Toc188881714Bk2962 _Toc188881715Bk2204 _Toc188881716Bk2212 _Toc188881717BK4726 _Toc188881718Bk2225 _Toc188881719Bk4978 _Toc188881720Bk4974 _Toc188881721Bk2220 _Toc188881722Bk2219 _Toc188881723 _Toc188881724 _Toc201478440T_RedactBk2354 _Toc188881725Bk2353 _Toc188881726Bk4595 _Toc188881727Bk3929 _Toc188881728Bk2348 _Toc188881729Bk4945 _Toc188881730Bk3930 _Toc188881731Bk2347 _Toc188881732Bk3968 _Toc188881733Bk2346 _Toc188881734Bk2345 _Toc188881735Bk2344 _Toc188881736Bk4920 _Toc188881737Bk2343 _Toc188881738Bk3972 _Toc188881739Bk3973 _Toc188881740Bk2342 _Toc188881741Bk3971 _Toc188881742Bk4024 _Toc188881743Bk2341 _Toc188881744 _Toc188881745 _Toc201478441 _Toc182368383 _Toc182368384 _Toc188881746 _Toc201478442Bk3569 _Toc188881747Bk4479 _Toc188881748Bk3570 _Toc188881749Bk2363 _Toc188881750Bk3326 _Toc188881751Bk3327 _Toc188881752Bk2361 _Toc188881753Bk2359 _Toc188881754Bk2360 _Toc188881755 T_CustodianBk4731 _Toc188881756Bk4732 _Toc188881757Bk4733 _Toc188881758Bk2357 _Toc188881759Bk2161 _Toc188881760Bk4480 _Toc188881761Bk4482 _Toc188881762Bk2160 _Toc188881763Bk3329 _Toc188881764Bk3330 _Toc188881765Bk2371 _Toc188881766Bk2356 _Toc188881767Bk3578 _Toc188881768Bk2297 _Toc188881769Bk4467 _Toc188881770 _Toc188881771 _Toc201478443 _Toc188881772Bk3964 _Toc188881773Bk2372 _Toc188881774Bk2369 _Toc188881775Bk2222 _Toc188756879 _Toc188762413 _Toc188881788 _Toc188888271 _Toc188888569 _Toc188933227 _Toc189015846 _Toc188756891 _Toc188762425 _Toc188881800 _Toc188888283 _Toc188888581 _Toc188933239 _Toc189015858 _Toc188881804 _Toc201478444Bk2382 _Toc188881805Bk3421 _Toc188881806Bk3424 _Toc188881807Bk3423 _Toc188881808Bk2388 _Toc188881809Bk2387 _Toc188881810Bk2377 _Toc188881811Bk3582 _Toc188881812Bk4549 _Toc188881813Bk3597 _Toc188881814Bk3584 _Toc188881815Bk3586 _Toc188881816Bk4630 _Toc188881817Bk4632 _Toc188881818Bk3657 _Toc188881819Bk2386 _Toc188881820Bk2385 _Toc188881821Bk3418 _Toc188881822Bk3594 _Toc188881823Bk3595 _Toc188881824Bk3596 _Toc188881825Bk3700 _Toc188881826Bk3702 _Toc188881827Bk3415 _Toc188881828Bk3416 _Toc188881829Bk5001 _Toc188881830Bk3419 _Toc188881831Bk2383 _Toc188881832Bk2380 _Toc188881833Bk2379 _Toc188881834Bk3422 _Toc188881835Bk4658 _Toc188881836Bk4659 _Toc188881837 _Toc188881838 _Toc201478445Bk2412 _Toc188881839Bk2397 _Toc188881840Bk2396 _Toc188881841Bk2408 _Toc188881842Bk3599 _Toc188881843Bk3601 _Toc188881844Bk2407 _Toc188881845Bk3602 _Toc188881846Bk2403 _Toc188881847Bk2405 _Toc188881848 _Toc188881849Bk3438 _Toc188881850Bk2202 _Toc188881851Bk3433 _Toc188881852Bk3430 _Toc188881853Bk2402 _Toc188881854Bk3603 _Toc188881855Bk2404 _Toc188881856Bk3598 _Toc188881857Bk2411 _Toc188881858Bk2395 _Toc188881859Bk2394 _Toc188881860 T_RendezvousBk3435 _Toc188881861Bk3437 _Toc188881862Bk2393 _Toc188881863Bk4353 _Toc188881864Bk4355 _Toc188881865Bk2406 _Toc188881866Bk2401 _Toc188881867Bk2400 _Toc188881868Bk2398 _Toc188881869Bk2410 _Toc188881870Bk3328 _Toc188881871Bk2409 _Toc188881872Bk4656 _Toc188881873Bk2392 _Toc188881874Bk2391 _Toc188881875Bk3439 _Toc188881876Bk3608 _Toc188881877Bk3431 _Toc188881878Bk3434 _Toc188881879Bk3441 _Toc188881880Bk3610 _Toc188881881Bk3750 _Toc188881882 _Toc188881883 _Toc201478446Bk3495 _Toc188881884Bk2094 _Toc188881885Bk4640 _Toc188881886Bk4737 _Toc188881887Bk3476 _Toc188881888Bk3497 _Toc188881889Bk2748 _Toc188881890Bk4568 _Toc188881891Bk4569 _Toc188881892Bk3887 _Toc188881893Bk3499 _Toc188881894Bk3491 _Toc188881895Bk3490 _Toc188881896Bk3890 _Toc188881897Bk3892 _Toc188881898Bk4163 _Toc188881899Bk3487 _Toc188881900Bk3486 _Toc188881901Bk3895 _Toc188881902 _Toc188881903 _Toc201478447T_CMSBk4294 _Toc188881904Bk5007 _Toc188881905Bk4265 _Toc188881906Bk4299 _Toc188881907Bk4273 _Toc188881908Bk4259 _Toc188881909Bk4253 _Toc188881910Bk4301 _Toc188881911Bk4297 _Toc188881912Bk4291 _Toc188881913Bk4305 _Toc188881914 _Toc187465013 _Toc187655578 _Toc187655691 _Toc187657416 _Toc188881915 _Toc201478448Bk2420 _Toc188881916Bk3305 _Toc188881917Bk2419 _Toc188881918Bk2418 _Toc188881919Bk2417 _Toc188881920Bk2415 _Toc188881921Bk2414 _Toc188881922Bk4759 _Toc188881923Bk3314 _Toc188881924Bk3315 _Toc188881925 _Toc188881926 _Toc201478449Bk2426 _Toc188881927Bk4095 _Toc188881928Bk2425 _Toc188881929Bk2424 _Toc188881930Bk2423 _Toc188881931Bk2422 _Toc188881932 _Toc188881933 _Toc201478450Bk2428 _Toc188881934Bk4359 _Toc188881935Bk3626 _Toc188881936Bk2299 _Toc188881937Bk3623 _Toc188881938Bk2429 _Toc188881939Bk2430 _Toc188881940Bk3316 _Toc188881941 _Toc182368394 _Toc182368395 _Toc188881942 _Toc201478451Bk4145 _Toc188881943Bk2083 _Toc188881944Bk3529 _Toc188881945Bk4318 _Toc188881946Bk4320 _Toc188881947Bk4323 _Toc188881948Bk4325 _Toc188881949Bk3531 _Toc188881950Bk3530 _Toc188881951Bk4148 _Toc188881952Bk3532 _Toc188881953BK3535 _Toc188881954BK3533 _Toc188881955Bk4143 _Toc188881956Bk4329 _Toc188881957Bk4331 _Toc188881958Bk4332 _Toc188881959 _Toc188881960 _Toc201478452Bk4307 _Toc188881961Bk3545 _Toc188881962Bk4223 _Toc188881963Bk3546 _Toc188881964Bk3547 _Toc188881965Bk4224 _Toc188881966Bk4107 _Toc188881967Bk4106 _Toc188881968Bk4312 _Toc188881969Bk4313 _Toc188881970Bk4314 _Toc188881971Bk4315 _Toc188881972 _Toc188881973 _Toc201478453Bk3536 _Toc188881974Bk3537 _Toc188881975Bk3541 _Toc188881976Bk3539 _Toc188881977Bk4096 _Toc188881978Bk4102 _Toc188881979Bk3542 _Toc188881980Bk4112 _Toc188881981Bk4104 _Toc188881982Bk3538 _Toc188881983 _Toc188881984 _Toc201478454 T_ClearanceBk2178 _Toc188881985Bk4333 _Toc188881986Bk2176 _Toc188881987Bk4336 _Toc188881988Bk2175 _Toc188881989Bk2174 _Toc188881990Bk4338 _Toc188881991Bk4155 _Toc188881992Bk2172 _Toc188881993Bk2171 _Toc188881994Bk4647 _Toc188881995Bk4360 _Toc188881996Bk4361 _Toc188881997Bk2170 _Toc188881998Bk4908 _Toc188881999Bk2169 _Toc188882000Bk3518 _Toc188882001Bk2168 _Toc188882002Bk3519 _Toc188882003Bk4341 _Toc188882004Bk4342 _Toc188882005Bk3522 _Toc188882006Bk3520 _Toc188882007Bk3521 _Toc188882008Bk4343 _Toc188882009Bk4344 _Toc188882010Bk2351 _Toc188882012Bk4177 _Toc188882013Bk2349 _Toc188882014 _Toc188882015 _Toc201478455 _Toc188882016 _Toc201478456Bk4202 _Toc188882017Bk2457 _Toc188882018Bk4752 _Toc188882019Bk2453 _Toc188882020Bk2456 _Toc188882021 _Toc188882022Bk2452 _Toc188882023Bk2448 _Toc188882024Bk3675 _Toc188882025Bk2447 _Toc188882026Bk2451 _Toc188882027Bk2450 _Toc188882028Bk4061 _Toc188882029Bk2446 _Toc188882030Bk2440 _Toc188882031Bk2445 _Toc188882032Bk2444 _Toc188882033Bk4000 _Toc188882034Bk2443 _Toc188882035Bk2442 _Toc188882036Bk2441 _Toc188882037Bk2745 _Toc188882038Bk2439 _Toc188882039Bk2438 _Toc188882040Bk2437 _Toc188882041Bk2290 _Toc188882042Bk4063 _Toc188882043Bk4065 _Toc188882044Bk4067 _Toc188882045Bk4070 _Toc188882046Bk4072 _Toc188882047Bk2820 _Toc188882048Bk4741 _Toc188882049Bk4742 _Toc188882050 _Toc188882051 _Toc201478457Bk2466 _Toc188882052Bk2465 _Toc188882053BK2464 _Toc188882054BK2463 _Toc188882055BK2462 _Toc188882056 _Toc188882057 _Toc188882058Bk2460 _Toc188882059Bk2459 _Toc188882060 _Toc188882061 _Toc201478458 _Toc188882062 _Toc188882063 _Toc188882064 _Toc188882065 _Toc188882066 _Toc188882067 _Toc201478459Bk2484 _Toc188882068Bk2483 _Toc188882069Bk2481 _Toc188882070Bk2478 _Toc188882071Bk2476 _Toc188882072Bk2474 _Toc188882073 _Toc188882074 _Toc201478460Bk2489 _Toc188882075Bk2488 _Toc188882076Bk2487 _Toc188882077Bk2486 _Toc188882078 _Toc188882079 _Toc201478461Bk2505 _Toc188882080Bk2504 _Toc188882081Bk2503 _Toc188882082Bk2502 _Toc188882083Bk4006 _Toc188882084Bk2501 _Toc188882085Bk2500 _Toc188882086Bk2499 _Toc188882087Bk2498 _Toc188882088Bk2497 _Toc188882089Bk2496 _Toc188882090Bk2495 _Toc188882091Bk2494 _Toc188882092Bk2493 _Toc188882093Bk2492 _Toc188882094 _Toc188177142 _Toc188882095 _Toc201478462 _Toc188882096Bk2513 _Toc188882097Bk4029 _Toc188882098Bk2512 _Toc188882099Bk2511 _Toc188882100Bk2510 _Toc188882101Bk4009 _Toc188882102Bk4586 _Toc188882103Bk4026 _Toc188882104 _Toc188882105Bk4681 _Toc188882106Bk4592 _Toc188882107Bk4593 _Toc188882108Bk4030 _Toc188882109Bk5002 _Toc188882110Bk2508 _Toc188882111Bk2514 _Toc188882112Bk4689 _Toc188882114 _Toc188888307 _Toc188888605 _Toc188933263 _Toc189015882 _Toc189021385 _Toc188882160 _Toc188888353 _Toc188888651 _Toc188933309 _Toc189015928 _Toc189021431 _Toc188882173 _Toc188888366 _Toc188888664 _Toc188933322 _Toc189015941 _Toc189021444 _Toc188882197 _Toc188888390 _Toc188888688 _Toc188933346 _Toc189015965 _Toc189021468 _Toc188882205 _Toc188888398 _Toc188888696 _Toc188933354 _Toc189015973 _Toc189021476 _Toc188882213 _Toc188888406 _Toc188888704 _Toc188933362 _Toc189015981 _Toc189021484 _Toc188882217 _Toc188888410 _Toc188888708 _Toc188933366 _Toc189015985 _Toc189021488 _Toc188882226 _Toc188888419 _Toc188888717 _Toc188933375 _Toc189015994 _Toc189021497 _Toc188882238 _Toc188888431 _Toc188888729 _Toc188933387 _Toc189016006 _Toc189021509 _Toc188882256 _Toc188888449 _Toc188888747 _Toc188933405 _Toc189016024 _Toc189021527 _Toc188882264 _Toc188888457 _Toc188888755 _Toc188933413 _Toc189016032 _Toc189021535 _Toc188882272 _Toc188888465 _Toc188888763 _Toc188933421 _Toc189016040 _Toc189021543 _Toc188882280 _Toc201478463Bk4082 _Toc188882281Bk4083 _Toc188882282Bk4084 _Toc188882283Bk4085 _Toc188882284Bk4086 _Toc188882285Bk4087 _Toc188882286Bk4089 _Toc188882287Bk4090 _Toc188882288Bk4092 _Toc188882289Bk4093 _Toc188882290Bk2813 _Toc188882291 _Toc188882292 _Toc201478464 _Toc188882293 _Toc201478465 _Toc188882294 _Toc201478466Bk2539 _Toc188882295Bk2538 _Toc188882296Bk2537 _Toc188882297Bk2536 _Toc188882298Bk2540 _Toc188882299Bk2535 _Toc188882300Bk2534 _Toc188882301Bk2533 _Toc188882302Bk2531 _Toc188882303Bk2530 _Toc188882304Bk2529 _Toc188882305Bk4599 _Toc188882306Bk2521 _Toc188882307Bk2528 _Toc188882308Bk2527 _Toc188882309Bk4989 _Toc188882310Bk2541 _Toc188882311Bk2526 _Toc188882312Bk2525 _Toc188882313Bk2524 _Toc188882314Bk2523 _Toc188882315Bk2522 _Toc188882316Bk2520 _Toc188882317Bk2519 _Toc188882318 _Toc188882319 _Toc201478467 _Toc188882320 _Toc201478468Gl_AdministrativeRoleGl_Administrator _Hlt188948979Gl_Aggregation Gl_AuditTrailGl_AuthenticityGl_AuthorisedUser _Hlt189016778Gl_BulkImporting _Hlt188944195 Gl_Capture Gl_CaseFile Gl_CaseWorkerGl_ClassGl_ClassificationGl_ClassificationCodeGl_ClassificationScheme Gl_ClearanceGl_Close Gl_ClosedGl_CMS _Hlt189021209 Gl_Component _Hlt189018382Gl_ConfigurationTime Gl_Custodian Gl_Destructon Gl_DigitalGl_DisposalHoldGl_Disposition _Hlt189017606 Gl_Document _Hlt188948993Gl_DocumentTypeGl_EDMS Gl_ElectronicGl_ElectronicDocumentGl_ElectronicRecordGl_ERMS Gl_Export _Hlt189016700Gl_File Gl_FileFormat Gl_Format _Hlt189017089 _Hlt189017354Gl_Group Gl_Import _Hlt192582577 Gl_Metadata Gl_keyword _Hlt192582574 _Hlt192582509 _Hlt192582581Gl_MetadataStubGl_NonCaseFileGl_OpenGl_Owner Gl_PaperFileGl_PDFGl_PDFAGl_PhysicalFileGl_PhysicalRecordGl_Presentation Gl_Profile Gl_Record Gl_RecordType Gl_Redact Gl_RedactionGl_Registration Gl_Render Gl_Rendezvous Gl_Rendition Gl_RepertoryGl_RetentionScheduleGl_RoleGl_SecurityCategoryGl_SecurityClearanceGl_Stub Gl_SubFile Gl_TransferGl_User Gl_UserGroupGl_UserProfile _Hlt188945357 Gl_UserRole _Hlt188950064 Gl_VersionGl_VitalRecord Gl_Volume _Toc188882321 _Toc201478469 _Toc188882322 _Toc188888480 _Toc188888778 _Toc188933436 _Toc189021558 _Toc188882323 _Toc201478470 _Toc188882324 _Toc201478471 _Ref477932464 _Ref477960617AnnexReferencePublications _Toc510410287 _Toc188882325 _Toc188884272 _Toc201478472 _Ref497495983PRO _Ref497495228 _Hlt508163292AnnexDevelopmentofthisSpec _Toc510410288 _Toc188882326 _Toc188884273 _Toc201478473 _Ref477932479AnnexUseofthisSpec _Toc510410289 _Toc188882327 _Toc188884274 _Toc201478474Annexacknowledgements _Toc510410290 _Toc188882328 _Toc188884275 _Toc201478475 _Ref506713536 _Ref506713550 _Toc510410291 _Toc188882329 _Toc188884276 _Toc188882330 _Toc188884277 _Toc188882331 _Toc188884278 _Toc188882332 _Toc188884279 _Toc510410293 RANGE!A1:E14 _Toc188882333 _Toc188884280 _Toc510410294 _Toc188882334 _Toc188884281 _Toc201478476 _Toc188882336 _Toc188884283 _Toc188882337 _Toc188884284AnnexDateProcessing _Toc510410297 _Toc188882338 _Toc188884285 _Toc201478477 _Toc188882339 _Toc188884286 _Toc201478478 _Toc188882340 _Toc188884287 _Toc201478479 _Hlt189022959 _Hlt189022960 _Toc188882341 _Toc188884288 _Toc201478480 _Hlk188254679 _Toc188882342 _Toc188884289 _Toc201478481 _Hlt189022619 _Hlt189022620 _Toc188882343 _Toc188884290 _Toc201478482 _Toc188882344 _Toc188884291 _Toc201478483 _Toc188882345 _Toc188884292 _Toc201478484 _Toc188882346 _Toc188884293 _Toc201478485 _Toc188882347 _Toc188884294 _Toc201478486 _Toc188882348 _Toc188884295 _Hlt189017973pp++[6[6h6h6Z<Z<@@HH T TXX0Z0Z=Z=ZhhmmHrHrzz88``''88ʫʫyPPtXGx''DEE\4W}I   { {     W W   ii  __##w     &!&!!![#[#%%4'4'h' ( (((()) *|*7+7+++,,..8////u2u25555Y6Y66677.9.9999::;;M<<@DDEEZFZFiLiLFMFMMMNN O O'OjOjOOOPPQQ1R1RRRSSeSeS~T~T5W5WWWWW5[5[\\j^j^9a9afdfdeeffggjjkkllmmoopprr%t%tttuufvfvvvSwVxVxx-y-y:y:y{{d}d}}}~~{{))7:YZσσ<؋̗̗?gĜӟӟ3322@@\\HH٭٭yy;;;;;;ڽZ99$$<<hh__HHQQDUUeerraa//OO]]%%99XX             ""######h$h$%%''R(R(((())**J+J+N+N+|,|,--..)/)///33r4r4556668888a9a94:4:;;AA>C>CCCDDEEGG$I$IKKLLNNnPnPPP:QjQjQSSTTUUUoWoWXXYYY\\^^______``aacfhhhhhhhhhhh%hkk lrrttuuxx{|||Q}Q}}˂˂ȃȃބބƇƇ33!NjNjWWQQ//GGqqff  kk̤̤==uu\\MM[[  ccоо++  VVJK,,22__YYEERR//,,    N N   \ \   aa__  !T"T"$$G(G())w*w***h+++9-9---//112288::;;<<\=\===\?\?@@)B)B+C+C"D"DDDEEGG~H~HHHIIXJXJLLPPQQSSJUJU3V3VVVxXxXYY+Z+ZZZ[[x\x\]]3^3^{_{_``^a^aeeggiill(m(mmm n nnnoppqqoqoqLrLrrr5s5stttt]v]vvv6x6xxxXzXzzz{{||}}``pphhSS  DD  ZZHH@@ȕȕooffcc''ii!!ؠؠ99EEYY>>hҴҴTTӼӼ""{{""CC++llLLpp++vvBB11==bbwwS S         $$zzHHss  Z"Z"""4#4###$$%%s&s&''@)@)))'*'*&0&000F1F1;2;22243433344M5M555 666!7!7Z8Z888@9@999#:#:::::F;F;;;;<<f>f>>>??z@z@ A AZBZBmCmCpEpE%F%F$G$G H HHH J JJJKKKKLLmMmMMMeNeNNNNNVVXXYY[[aaaaccggchchiijjmm4n4n o oppqqssFtFtttvv2w΃΃ԄԄggbbSSQQ,,))``66ʫʫkk##YY@@^^ll  WWMMhhNNFFOO77dd##;;++##))    ( (   8 8 uww||,,!!""m$m$*&*&''))**++--..//212111C3C344 5 5/6/677B8B8883:3:x;x;<<?H?HIIKKXKXKKK7L7LLMMNNPPPPeQeQRRSSJSJS(T(TLULUUUVVWW_X_XYYI[I[[[#\#\#^#^^^aabb?@ABCDEHF@G@JI@MK@L@NOPQRSTUVXYW@Z[\]^_`abcdfe@ghijklmnopqrstuvwxyz{|}~@@@     @@@ !"#@$@%@&'()*+,-/.@012354@6789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnoqp@rstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWYX@Z[\]^_`abcdefghijklmnopqrts@uvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~@@@@@@@@@@@@@@@@     @ !"#$%&'()*+,-./0123456879:B;<=>?@ACDEFGHIJKLMN@O@PQRSTUVW@X@YZ[\]^_`abcdefghij@qq++g6g6r6r6<<@@HHHTHTXX1Z1ZkZkZhh"m"mjrjr{{\\~~DDGG֫֫X;~h ''eEEX]2p2   { {     W W   ii  __##     &!&!!![#[#%%4'4'' ( ((()))9**7+7+++,,..Y////u2u25555Y6Y66677.9.9999::;;z<n@DDEEZFZFiLiLFMFMMMNN O OJOjOjOOOPPQQ1R1RRRSSeSeS~T~T5W5WWWXX5[5[\\j^j^9a9afdfdeeffggjjkkllmmoopprr%t%tttuufvfvvvwVxVx.y.y2y:y:y{{d}d}}}~~{{))7:Z[σσm ̗̗hlӟӟ3322JccD\\3HH٭٭yy;;;;GG ʿ99$$<<hh__HHQQeUUee  rr//OO]]%%99XX             ""######h$h$%%''R(R(((())**N+N+,,|,|,--..)/)///33r4r45536668888a9a94:4:<<AA>C>CCCDDEEGG$I$IKKLLNNnPnPPPaQjQjQSSTTUUUoWoWXXYYZ\\^^______``aadJfhhhhhhhhh$h$hdhkk9lrrttuuxx| |||Q}Q}}˂˂ȃȃƇƇ33@NjNjWWQQ//GGqqff  kk̤̤==uu\\MM[[  ccоо  ++  VV,,22__YY,,EERR//,,    N N   \ \   uu__  !T"T"$$G(G())****+++9-9---//113388::;;<<\=\===\?\?@@)B)B+C+C"D"DDDEEGG~H~HHHIIXJXJLLPPQQSSJUJU3V3VVVxXxXYY+Z+ZZZ[[x\x\]]3^3^{_{_``^a^aeeggjjll(m(mmm n nnnoppqqoqoqLrLrrr5s5stttt]v]vvv6x6xxxXzXzzz{{||}}vvpphh\\  DD  ZZHH@@ȕȕooffcc''ii!!ؠؠ99EEYYffҴҴTTӼӼ""{{""CC++ll88LLpp++JvvBB11!!==bbwwS S         $$zzHHss  Z"Z"""4#4###$$%%s&s&''@)@)))/*/*&0&000F1F1;2;22243433344M5M555 666!7!7Z8Z888@9@999#:#:::::F;F;;;;<<f>f>>>??z@z@ A AZBZBmCmCpEpE%F%F$G$G H HHH J JJJKKKKLLmMmMMMeNeNNNNNVVXXYY[[aaaaccggchchiijjmm4n4n o oppqqssFtFtttvvRw΃΃ԄԄggbbSSQQ,,ՔՔ))``66ʫʫkk##  YY@@wwll  WWMMhhNNFFOO77dd##;;++##))    ( (   K K ww||,,!!""m$m$*&*&''))**++--..//212111C3C344 5 5/6/677B8B8883:3:x;x;<<JHJHIIKKXKXKKK7L7LLMMNNPPPPeQeQRRSSJSJS(T(TLULUUUVVWW_X_XYYI[I[[[#\#\#^#^^^aabbvy\{!j"z<$T!$+ĸ$!!{l!}**Ty" q$\* ++\"x"TZ0ܝ*  T++*T+l*t*$*D~2**˜\V+Ø|/ Ę*ŘLt2Ƙt$+ǘ4$+Ș#+ɘ$+ʘo$˘t2̘$͘o Θ$ϘD$Иd*ј*ҘdM ӘM Ԙ{2՘{2֘$|2טؘT٘ژԱۘY+ܘZ+ݘDZ+ޘZ+ߘZ+N N O \O O l$ m$Lm$m$m$ n$Ln$   D     , l   , l   , l   , l   , D   D  DDDD4+ t+!+"+#4+$t+%+&+'4+(t+)+*++4+,t+-+.+/4 +0t +1 +2 +34!+4t!+5!+6!+74"+8t"+9"+:"+;4#+<t#+=#+>` ?T` @` A` Ba CTa Da Ea Fb GTb Hb Ib Jc KTc Lc Mc Nd OTd Pd Qd Re STe Te Ue Vf WTf Xf Yf Zg [Tg \g ]g ^h _Th `h ah bi cTi di ei fj g@ hT@ i@ j@ kA lTA mA nA oB pTB qB rB sC tTC uC vC wD xTD yD zD {E |TE }E ~E F TF F F G TG G G H TH H H I TI I I J TJ t_+_+_+4`+t`+`+ `+ 4a+ ta+,355>6XXyYdC׷sdxx||ssííZZ +[ ((Hjt__[[{{VVxx88?rr99zz%%vv::H<<HQ==Kyy33C**ss~::bb|##/88ll??``i  GGkk|HHRxx}``f77 T TWX ZQZ\      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqtrsuvwxyz{|}~     ,355D6XXYj%Cݷyd~~~~}̭̭``?f&ENNp{jj]]    ^^zz=GG  @@||..FQQGOXXIMMAEE//|??z+66  >>ss  AAgkkJJz~~%%PYY{enn==TT]XZWZ\  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqstruvwxyz{|}~     B*urn:schemas-microsoft-com:office:smarttagscountry-region9*urn:schemas-microsoft-com:office:smarttagsplace>*urn:schemas-microsoft-com:office:smarttags PersonName=*urn:schemas-microsoft-com:office:smarttags PlaceType9*urn:schemas-microsoft-com:office:smarttagsState=*urn:schemas-microsoft-com:office:smarttags PlaceName8*urn:schemas-microsoft-com:office:smarttagsCity je |}JKghJKQ)R)))//8888XXXXSZTZZZ[[iiii!j"jrrrrwwβϲJKɴʴghij  r s       QRU!V!$$&&''((BBEEpOqOHTITfTgTUUXX\\S|T|78ghRS(())X>Y>@@II_L`L}L~Lrr3w4w7y8yzz ŗƗOP\]ôĴ%&еѵ>?wx~./z!{!''O,P,HZIZ[[23̊͊'(DEڒے"")#*#v*w**/+///)2*2222244o9p9lMmMMMMMYY/u0uvvMNhiJKpqab  %)03>CO]douy\c'/<GJOPV !  '+1DIPUbmqz;BCGJStyT[*238HP >FGK* . ((?)C)**33V4a4g8l8: :SSSSWVt[t[v[v[w[w[y[z[|[}[[[[[\P??uVwVWW]ocoppppȁЁ ؎܎ŏȏloŖٖ$%./_go;EMr .05Уأ]ť)\h¹ξվkp ,6pw--9?=? AA3J7J8K>KM MVVH^K^1`4`ffjjEkKkClIl5o>owwzz!':E=D%ps{ ~    !IRuxTWQZ(&.&/+2+i-q-77z;;3=6=G G\JaJL#L7N:N"O/OQQVVZXdXOZTZ]]ll;p>pBvCvyy!ƌԌ֠ݠ$<L&- BH`bik y# ) Y_bMV!!##f&k&))++B<E<FF.H0HTT`\e\]]r{y{~~-3@Hkv9<=@@A.6 :B}u~ #X ^   m t AD25%%O'R'//0888==@@,C/CTT]]`` ff hh{jj`vcv{{l{p{RW<#&ɯFQ>F[^q{ik?G-0Z c     %%''--0033/?7?CCCCDDEEEE5UΩթͱѱ0=aj+.37IKxLS.8r    _ l n        % G i n v 8 ~",sor 8UZdft)7xESh  !     5!U!o!!!!!(()f)))))*"*$*k*++-'-.-j---....111133j44445678868|9999g:: ;;;;;;<<B=F=O==@?F?|????AAAABBBB$CCE EEE3F7F:F>F@FFFFF)GFGKGMGG-H2H9HQHSK[KbKK LLLLnMzM|MMqPxPPP4T:TTTTTVVVVsYYYYaZgZiZZZZZ4[[[^\y\6]:]``(a1abbKcScccdd)f1fbfufffg gg2ghhhi]jajcjjjjjknkkkkkkk+l5l mmmm"m_mnnoooo}}&)*-fw|Ȣp}ru y z s:{:SSMVUVWVt[t[v[v[w[w[y[z[|[}[[[[[\3333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333 ?^8pB a ) H  R q $ C 2 R %r(H?_Cc.sAa?_Aac'HBcd@a Ar9Z Op3l.O E f !4!!!"("c""""#6#|####&$G$$$$%N%o%%%)&J&&& '*'y''''J(k(((()b))))P*q***3+T+++kه9R55Vo%%9Q    $$@)Y)))//8888hXXXX2ZZZ_ZZZ[iiiij(jrrrrwwֲ9RѴqVoXq $EEa z       @YD!]!$%&&& '((BBEEEENN'O'O_OxO7TPTUTnTUUXX\\B|[| p&? VnAZ(())<<G>_>z@@rDrDDDwHwHIINLgLlLLrr"w;w&y?yzz͗>WKcʴ,׵-Ef~ߺmӽ6i!!'''>,W,BB7ZPZ[[!:Ԋ.3Kɒ   !"#2#(())e**/3///23222233 4^9x9;;[MtMvMMMMYZu7u{vv<UWpu5T_xzPjoFFG /?==00"hsAM OVVTVTVWVZVWt[t[v[v[w[w[y[z[|[}[[[[[[[[[[[[[\WVt[t[v[v[w[w[y[z[|[}[[[[[\$|$T}S~ZRfQJnbI sHzxvGfPFT3$# U Gx?QRT7@fbYq("(-B !A'(u҈hX*~)0!,p&.Tm?c~1[4b,;Lݪ(>4:I~юy!LS!]hb` k5[5q Xwt.o |v Rht(x~\n b| ^`.^`.^`.^`. ^`OJQJo( ^`OJQJo( ^`OJQJo( ^`OJQJo(hh^h`. hh^h`OJQJo( ^`hH Article . 8^`hH Section . P^`PhH() `p`^``phH() P^`PhH) P^`PhH) ^`hH) P^`PhH. 0p0^0`phH.e9^`789;<B*H*OJ QJ S*TXo(phhHoe^`OJ QJ ^J o(hHoepp^p`OJQJo(hHe@ @ ^@ `OJQJo(hHe^`OJ QJ ^J o(hHoe^`OJQJo(hHe^`OJQJo(hHe^`OJ QJ ^J o(hHoePP^P`OJQJo(hHhh^h`[]hee^e`B*OJQJo(phhHh^`OJ QJ ^J o(hHohpp^p`OJQJo(hHh@ @ ^@ `OJQJo(hHh^`OJ QJ ^J o(hHoh^`OJQJo(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohPP^P`OJQJo(hHh9TT^T`789;<B*H*OJQJS*TXo(phhHh^`OJ QJ ^J o(hHohpp^p`OJQJo(hHh@ @ ^@ `OJQJo(hHh^`OJ QJ ^J o(hHoh^`OJQJo(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohPP^P`OJQJo(hHh dd^d`OJQJo(h 4 4 ^4 `OJ QJ o(oh   ^ `OJQJo(h ^`OJQJo(h ^`OJ QJ o(oh tt^t`OJQJo(h DD^D`OJQJo(h ^`OJ QJ o(oh ^`OJQJo(Q^`QB* o(phVhH.(Q^`Q56B*CJOJQJo(phhH. Q^`Qo(hH.. Q^`Qo(hH. Q^`Qo(hH. `^``;o(hH APPENDIX : Q^`Qo(hH. Q^`Qo(hH..Q^`Q;o(hH.@88^8`B*CJ OJQJo(pho@ ^`OJ QJ o(o@ pp^p`OJQJo(@ @ @ ^@ `OJQJo(@ ^`OJ QJ o(o@ ^`OJQJo(@ ^`OJQJo(@ ^`OJ QJ o(o@ PP^P`OJQJo(jQ^`Q4*56789;<>*@B*CJEHH*KHCJEHOJQJS*TX[\]^Jo(phhH.YQ^`Q4*56789;<>*@EHH*KHEHOJQJS*TX[\]^Jo(hH.jcQc^c`Q4*56789;<>*@B*CJEHH*KHCJEHOJQJS*TX[\]^Jo(phhH..Q^`Q5\o(hH... Q^`Qo(hH. `^``;o(hH APPENDIX : Q^`Qo(hH. Q^`Qo(hH..Q^`Q;o(hH.@@^@`B*OJQJo(ph ^`OJ QJ o(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJQJo( ^`OJQJo( ^`OJ QJ o(o PP^P`OJQJo(h hh^h`OJQJo(h 88^8`OJ QJ o(oh ^`OJQJo(h   ^ `OJQJo(h   ^ `OJ QJ o(oh xx^x`OJQJo(h HH^H`OJQJo(h ^`OJ QJ o(oh ^`OJQJo( P^`POJQJo( ^`OJ QJ o(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJQJo( ^`OJQJo( ^`OJ QJ o(o PP^P`OJQJo(@@^@`o(.^`.pLp^p`L.@ @ ^@ `.^`.L^`L.^`.^`.PLP^P`L.Q^`QB* o(phVhH.Q^`QB*OJQJo(phhH. Q^`Qo(hH.. Q^`Qo(hH. Q^`Qo(hH. `^``;o(hH APPENDIX : Q^`Qo(hH. Q^`Qo(hH..Q^`Q;o(hH.e=^`789;<B*H*CJOJQJS*TXo(phhHe^`OJ QJ ^J o(hHoepp^p`OJQJo(hHe@ @ ^@ `OJQJo(hHe^`OJ QJ ^J o(hHoe^`OJQJo(hHe^`OJQJo(hHe^`OJ QJ ^J o(hHoePP^P`OJQJo(hHh hh^h`OJQJo(h 88^8`OJ QJ o(oh ^`OJQJo(h   ^ `OJQJo(h   ^ `OJ QJ o(oh xx^x`OJQJo(h HH^H`OJQJo(h ^`OJ QJ o(oh ^`OJQJo(@@^@`B*OJQJo(ph3n ^`OJ QJ o(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJQJo( ^`OJQJo( ^`OJ QJ o(o PP^P`OJQJo(ee^e`B*OJQJo(phhH^`OJ QJ o(hHopp^p`OJQJo(hH@ @ ^@ `OJQJo(hH^`OJ QJ o(hHo^`OJQJo(hH^`OJQJo(hH^`OJ QJ o(hHoPP^P`OJQJo(hHP^`PB*OJQJo(ph3n ^`OJ QJ o(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJQJo( ^`OJQJo( ^`OJ QJ o(o PP^P`OJQJo(hhh^h`B*o(phhH.h^`OJ QJ ^J o(hHohpp^p`OJQJo(hHh@ @ ^@ `OJQJo(hHh^`OJ QJ ^J o(hHoh^`OJQJo(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohPP^P`OJQJo(hHhee^e`B*OJQJo(phhHh^`OJ QJ ^J o(hHohpp^p`OJQJo(hHh@ @ ^@ `OJQJo(hHh^`OJ QJ ^J o(hHoh^`OJQJo(hHh^`OJQJo(hHh^`OJ QJ ^J o(hHohPP^P`OJQJo(hH hh^h`hH. P^`PhH.. ^`hH... x^`xhH....  ^`hH .....  X@ ^ `XhH ......  ^ `hH.......  8x^`8hH........  `H^``hH.........Q^`Q3*G+5\B* CJ OJQJsHtHphVaJ _H4*56789:;<>*@B*EHH*KHEHOJQJS*TX[\]^Jo(phhH.Q^`Q3*G5CJsHtHaJ_H.vQ^`Q3*GCJsHtHaJ_H4*56789:;<>*@EHH*KHEHOJQJS*TX[\]^Jo(hH..Q^`Q5\o(hH... Q^`Qo(hH. `^``;o(hH APPENDIX : Q^`Qo(hH. Q^`Qo(hH..Q^`Q;o(hH.e=^`789;<B*H*CJOJQJS*TXo(phhHe^`OJ QJ ^J o(hHoepp^p`OJQJo(hHe@ @ ^@ `OJQJo(hHe^`OJ QJ ^J o(hHoe^`OJQJo(hHe^`OJQJo(hHe^`OJ QJ ^J o(hHoePP^P`OJQJo(hH88^8`B*CJ OJQJo(ph3p ^`OJ QJ o(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJ QJ o(o ^`OJQJo( ^`OJQJo( ^`OJ QJ o(o PP^P`OJQJo( hh^h`hH) ^`hH) 88^8`hH) ^`hH() ^`hH() pp^p`hH()   ^ `hH. @ @ ^@ `hH.   ^ `hH.)~}|[5qn b|T3$0|v!]7c~1:IYq0(>QhX*(;(. !t(x0!,LS` k''U ''[4Xwt` k` k$$:"q                Z        Xb         K        zT        Tr                          S                 *E                $                 4$. Z}cdq-4\8kF{Q+W]jav?+XoG|b 0^2(ZJFaK3g}!N+@nyc) = R x     ; @ GD Z t w '7 l r c# (> M A% + U c l K~^ > B4K Dh {%d{r mW+WO^_,}#-]txy6{  <XUi"$/)@DXP0I$Z[:>9k_zo{5 D M l } !=!5#!#A!E!pU!9h!D&"Z3"(6"O<"#"#$#-#v#S$l$9y$%<%&&)<&I&M'P'Z't'TV(L )R)+)f[) * G*lX*qx* +Fi+,,*,dn,r,.- C-D-N-m-`r-I.`//////00!0_C0@F0$W0Vp0Eu0y00)15u121 33+3A34Q45#5$5T)5$i5~556M<6v'7wZ7v7K 8q48L8q89O9l9'J:y:#;0;s`;g;k;2)<s<<==7='_=i=c9>D> M>P>X>~> ?h ?@%@1@*<@_@A&AB6ABMjB6C"kDC{DQErEtE{E=FF0FFw$FwkFpF=GwGWH$H0/H%[H[H\H%IwIIJ\=JRK'K{9KEKRKvKLV`L.MMAMUMUMN4Nb@NLNo{N OAO#LPfP^Q8QnLRf_RkRwRyRSSSLBSwISTSUS T-T-T9THTRTg;U{VWW\W fWiWr$Xt+X+ZXpXYY(YH_YZ(Z*ZWZeZqZ[ [ [ZB[&t[\13\Q\Fh\cz\c\]^^-^%>^Z_&E`!\`aCaa1a0afZa=bgNbTbc8cf]cjcokcd1.d6dAd-MdodNeQewexefh f*fWOfRfXef2ghLLh`hX iMifJi*Wijikiyi/ juj(Sk$Ykl#lm-Cm6HmSmimYxmnHnT\nj{no'oHolo'p(p{7pKpcp[ppppm@qAqkXq7mq#rL&rM.r@2r:r~VrsistYvt uI uuouk4uv0 v_$v3v wwFwhwwxyg#yAyWQyNqyJzzV'zszxz!{W{_{-t{|6|j^|Pg|m|{|s}}*}X7~S~n~)p~?H'JEVO!*1EJYh;?BSm%*u}&8P&S. BR|x{~U!QSnz-Hl MT2v2Vh J]'=kxm:2>jRu::9kdUeg{uQRWq5$t,l9U=V qCs Yh^a1PRYI l]gq\Cx6zV$M Vf70QiF;bsc0NZjCP5.hLf6&w aa# a=rH t- h{ ~(b(#5Jnz!`Uj]$$^.xCFTuVBWtlG(nNR[)U)8?OL8'12JMgW _q2%l7}N!# );H 45CvsLw-@F' +PVQxn 9uZ  $'0|v|'t#)(GnWZ[N8h;H_%>mbd{v0O@{-@nOtf57fAXXc,g~D^H!N3|BD>apr}G?ov4#4_bC8dYev%Fo %4<,CpZ~"*?vyF8B9D?uF}@GwR`rT#CzsV$$,Lnprx0AHCRX9@vy{4uQ-@S[* 7B'fw:~&f,$7\v V@+1ea/+LakhMMU=`;"hFQ]bzz#')1HJi[U\\\h)/u!G|hj %KL[jp>MQt[nMqfinpRp!tQzB57:D[#O4FCYA4;ft0 8H^zhGNvp2|Zz^c +5$h~hmH'g)N]idg os"%=Q]Xi_\_jq '0W]"<#_y{}~ "#(?@AF+-./dfghLMNOSUVW{}~-/01X Z [ \     t v w |         P R S X      cdej@BCD+,-.<=>? XZ[`$4678    !!!"!'!!!!!X"Z"["\"U#V#W#\#####%%%%''*'/'0'5'((( ({(}(~(())))))))\*^*_*`*1+2+3+8+++++,,,,... ...../// /////t0v0w0x0o2p2q2v2)3+3,3-34444/50515655555S6T6U6Z666667777q8s8t8u8(9)9*9/99999|:~:::;;;;;;;WDDDDDDD}EEEESFUFVF[F'G)G*G+GmInIoIpIJJJJKKKKcLdLeLjL?MAMBMGMMMMMNNNNNNNNOOO OcOeOfOkOOOOOPPPPPPPPvQxQyQzQQQQQ*R,R-R2RRRRRSSSS^S`SaSfSTTTTxTyTzTTwUyUzU{U/W0W1W6WWWWWWWWX[[+[0[1[6[[[[[\\\\[]]]^]_]d^e^f^k^^^^^````3a4a5a:aaaaa!c"c#c$c`dadbdgdOeQeReSe)f*f+f,fffff[g]g^g_gggggjjjjkkkkllllmmmmoooo;p=p>p?pppppqqqq(r)r*r+rrrrrsssst t!t&ttttt'u)u*u+uuuuu_vavbvgvvvvvwwwwPxQxRxWxxxxx4y5y6y;y{!{"{#{{{{{||||^}_}`}e}}}}}~~~~tvw|z|}~#$%*ȃʃ˃Ѓnpqrݖ—Ǘȗ͗npqrޛ՝ם؝ٝ>?@AZ\]^͟Οϟԟhjkl)+,-   hjkl-./4yz{+-.3ڦۦܦvxyz ¨{}~ߩSUVWVWX]BCDIҭԭխڭ֮خٮڮstuzNPQR8:;w{vwxy345: %678=acdiXZ[`&()*ACDIJLMRACDENPQV_`afGY[\]wyz{DFGHdefgpqrslmnsa(*+0{}~npqrHJKPVXY^       !&245:} ')*+RSTY                U W X Y ~    5789mnopnopq8 9 : ;         _!a!b!c!"""" ############a$c$d$i$% % %%&&&&''''K(M(N(S((((((((())))))))*** *****H+I+J+O+,,,,v,w,x,},----...."/$/%/*////1333333k4m4n4s41535455555556666 8888}8~8888888Z9\9]9b99999.:/:0:5:;;;]AAAAAAABBBB8C9C:C?CCCCCDDDDE?E@EEEEEG?G@GGGGGRHTHUHVHII I%IJJJKLLLLNNNNOOOOhPiPjPoPPPPPcQeQfQkQQQQQRRRRRSSSSSSS0T1T2T3TTTTTUUUUUUUUhWjWkWpWXXXXXXXXYYYYyZ{Z|Z}Z[[[[\\\\{^}^~^^ ____^_`_a_b_________```ilkpk}kkkk.m0m1m2mmmmmFpGpHpIppppprrrrrrrrsssstttt uuuuuvvvuvvvwvxvwwwx yyyyzzzz||||J}L}M}R}'~)~*~+~~~~~łƂǂ̂ƒÃăɃ!"#ۄ܄݄ބ   ‡LJ,./4*,-.‹ËȋmopqPRSXKLMR!#$%)*+0]^_`ٖږۖܖABCHjlmr_abg#%&' dfglϣѣңӣƤǤȤͤ789>opqvACDEVWX]GHIN+-./defg=?@AUVW\ ʻ̻ͻλ]^_dɾ˾̾ѾKMNO,./0VXYZ$&', PQRWUWXYHIJKbdefJLMN&'(-MOPQ,-.3 iklmDHUZ[`RTUZ *.;@AFLMNS "#$$&'(z|}~~)*+0 &'(-}                H I J O         U W X ]    avzXZ[`    !!!!M"O"P"U"# # # #$$$$$$$$&&&&''''((((A(B(C(H())))))))t*v*w*******++++N,P,Q,R,3-4-5-:---------....////h0j0k0l000001111"2$2%2&22229::::::;;;;<<<<<<<<V=W=X=]=====e>g>h>i>V?W?X?]?????@@@@$A&A'A(A#B$B%B*BBBBB%C&C'C,CCCCCDDD#DDDDDFEHEIEJEEEEEFFFFGGGGwHyHzHHHHHH|I~IIIIIIIQJSJTJYJJJKKKKKKLLLLMMMMOOOOPPPP9Q;Q?@E!SUV[ACDI:;<AÕĕɕhjkp_abg\^_d   "#(bdej"ҠӠԠ٠245:>@AFRTUZ;=>Reghi̴ʹδӴٵ۵ܵݵչ׹عٹNOPU̼μϼԼWYZ[   ھ۾ܾkmno#rtuvuvw|#<>?D$&',eghm15BGHMiklqacde%&',oqrw;=>C.012 *,-2VXYZ"&389> \]^c]fopOL s qrsx    M N O T                      %xz{ rstusuv{BCDIVXYZlnotz|}tvwx       !!!!T"U"V"["""""-#/#0#5#####*$,$-$.$$$$$%%%%%%%%&&&&m&n&o&t&'''''''':);)<)A)))))$*&*'*/ 000!0"0'00000?1A1B1G1426272<222222222.3/3035333334444F5H5I5N55555 6 6 6 66666777"7S8U8V8[8888899;9<9A99999:::$:::::::::?;A;B;G;~;;;;;;;;<<<<<<<<>>>>`>a>b>g>>>>>????s@u@v@{@AAA AAAAATBUBVB[BfChCiCnCCCCCjEkElEqEF F!F&FFFFFGG G%GHHH HxHzH{H|HHHHHtIvIwIxIJJJ JJJJJKKKKKKKKLLLLLLLLgMhMiMnMMMMM^N`NaNfNNNNNNNNUVVVVVVWWWWXXXXYYYYx[z[{[[\\\\\\\\\_]_^___aaaaaaaaSbUbVbWbccccufwfxfyfffffgggg\h^h_hdh i i iiiiiijjjj>k@kAkBkmmmm-n/n0n5nnnnnooo oooooppppqqqqVrXrYrZrssss?tAtBtGtttttvvvăɃʃσ̈́τЄՄ`bch׊يڊۊ[]^c!"#ŽÎĎŎMNOTKLMR&'(-bСԡ¢#$%*Z[\açħŧ0127QSTUīūƫ˫OQRS%&'(efgl$ˮͮήϮ   RTUZ9;<A[]^CQUbghm _abcQRSXFHINrstuacdiGIJO@ABGIJKP0238]_`e$Aimz   467<$&',$ !rstu#$%*$;=>?        e g h i         " # $ )     5 7 8 hjklqrsxdefgvwx}*,-.BCDEFG1234&'(-]_`ab!d!e!f!!!!!""""####g$h$i$n$#&%&&&+&'''')))) ****+ + ++----........////////0000,1-1.13111112222=3>3?3D34444555!5(6*6+606+7-7.7/77777;8=8>8C888889999-:.:/:4:::::r;s;t;y;9<;<<<=<<<<KHIIIIIIaJcJdJeJ K K KKQKSKTKYKKKKK0L2L3L8LLLLLSMUMVMWMMMMM;N=N>N?NNNNNOOOOPPPPPPPPPPPP"Q$Q%Q&Q_Q`QaQfQPRRRSRTRRRRR S S SSCSESFSKS!T#T$T)TEUGUHUMUUUUUVVVVbWdWeWfWWWWWXXZX[X`XYYYYYYYYZZZZC[D[E[J[[[[[[[[[[[[[\\\$\/]1]2]3]^^^$^^^^^` `!`"` a aaaaaaabbbb_dadbdcdneoepeqe6f7f8f=fggggggggh h!h"hhhhhii i%iiiii5j6j7jw?w@wwwwwyyyyyzzzb{c{d{e{`|a|b|c|}}}}~~~~\^_`9:;@lmns:<=- $9>?@STUVyz{||}~Z\]-RTUZ   :<=BڔܔݔHŗҗחؗݗZ\]bNPQV !_cpuv{SUVW.016wyzrtuzQRSX1349DFGHíŭƭ˭RTUdz~\^_dμмѼҼnpqvDFGLhijosuvw()*+     !&FHINEGHIYZ[`| .016WYZ_+016fhijBCDIoqrwklmr,./0<>?@",-.3VXY^xz{|ijkpMNOT[]^_jlmr1238DFGLȣݣ %),045JMQUYZäƤʤΤϤ!%)-12LORUXYpsw{ťɥͥΥCFJNRSehlptu¦ŦȦɦNQTX\]ӧקۧߧ 8;>BFGhknquv9:>[vwx%&''()ج٬ڬX,VWXDEFpde'(@QRduv./<WXgxy#$4OPars8 OPjklJ[^_{  !"6BCV_`x{|HIbq!0%ABVb}~/0@L#RSkw0<YZjv)5NO_k (FGWc 01@LMN[g@AVb78HT  (?@Tbtu  (BCR`lmz)7KL]k&':HZ[jx$:;M[opxy   ()+45tu%&'.567FPQRahij|'().89:LVWXfpqry*126DKLMV]^_hrst{  #$%29:;IPQR[bcdmtuv(/067KZ[gz{"iju~ &')23IJUklztu}cdm  rs}';<I"#/   h i o \ ] b    @ A T e    ) * /    kl{|  JKnoC0D0M0T0\0`0i0r0y00000111111 1!1"1#111P1R1T1U1V1W1X1Y1Z1[1i111111111111111111111111222426282:2<2=2>2?2H2222222222222222222333 3.3/31333537393:3;3<3G333333333333*4+4-4.4/40414243444>444444444444555555 5"5#5$5.555555555555666666 6!6"6#6-6`6b6d6e6f6g6h6i6j6k6u666666666666667777777 7797:7<7>7@7B7D7E7F7G7Q777777777777777777777778888888888(8888888888889999999999$9>9@9B9C9D9E9F9G9H9I9O999999999999999::::::: :+:-:/:1:3:5:7:8:9:::=====> >>>>> >!>1>2>5>B>D>Q>R>V>a>e>p>q>u>>>>>>>>>>>"?&?O?P?T???????????@$@G@H@L@q@v@@@@@@@@@@@AAA-A1AAABAFASAWAdAeAiAAAAAAAAAAABB>B?BCBUBYBkBlBpBxB|BBBBBBBBBCCCCC%C)C0C1C5CBCGCTCUCYCnCrCCCCCCCCCCCCCDDD.D/D1DHDJDdDeDiD}DDDDDDDDDDDDE E"E4E6EVEWE[EcEgEoEpEtEEEEEEEEEEEEEEEF FFFFF@FBFhFiFmFFFFFFFFFFFFGGGG-G1GEGFGHGaGcG|G}GGGGGGGGGGGGGH+H,H/HCHFHWHXH]HHHHHHHHIII)I.I]I^IcIlIqIzI{IIIIIIIIIIIIIIJJJ4J5JaJbJeJJJJJJJJJJJJJKK K K&K:K;K@KTKYKmKnKsKKKKKKKL1L2L7LjLoLLLLLLLLLLLLLL*M3M@MAMFMnMyMMMMMMMMM7NBNeNfNkNNNNNNNN O OO1OU`UiUUUVV\33333333333333333333333333333333333333 3333333333333333333333@(o=@{ JJJ ()/089XYZ[ijrswxgggiii    QQQ!Q"Q$Q%&'(BCEFNOSTUVXY[\bc{|туggRR'()=>@AIJ_L_Mrs3w3x7y7z7{  \\\\\\\www..z!z"O,O-OYOZ[\2222222 "#$*+/0234o9o:oLoMoNYZtuvJJaaaa``````/`0`1`2`3`4`5`7`8`9`:QP\P@PPPP(@PP@PP@PPP,@P0Pd@P:Px@PBP@PLP@PnPpPrP@PP@PP@PP(@PPPP@PP@PP@PP@PPP<@P P"PH@P&PP@P.P`@P4Pl@P8P:Px@PHP@PLP@PRP@PVP@PZP\P@PxP@P|P@PP@PP@PP$@PP,@PP4@PPD@PPx@PP@PPP@PPP@PP@PP@PP@P\P@PrPtP@PP@PP @PP4@PP<@PP@PP@PPP@PP@PPP@PPPPPPP4@PPP@@P"PH@P0Pd@P4Pl@PxP@P|P@PP @PP @PP8 @PP @PP @PPP @PPPP @P(PT @P^P @PbP @PPP4 @PP< @PPPH @PPX @PPd @PPPp @PP @PPP @PP @PPP @P4Pl @PVP @PfP @PtP @PPP @PP @PP @PP( @PP` @P,@PJP,@PXP,@PPPPPPPPPPPx-@P2@UnknownAuthor Gz Times New Roman5Symbol3& z ArialS PalatinoBook Antiqua5& zaTahomaI Arial BoldArial;Wingdings;J PFS Sophie3z Times?5 z Courier NewABook Antiqua"1Ȉh_FKF+ Y=Q Y=Q !nn4dRRuG 2qZ 0RK!MoReq2 Specification;Model Requirements for the Management of Electronic Records$         %                  # ! " #$Oh+'0$ 0< \ h t MoReq2 Specification<Model Requirements for the Management of Electronic RecordsNormal7Microsoft Office Word@d@ ,@Z @TnY=՜.+,D՜.+,x4  Q R MoReq2 Specification Titled P>dJdndddd _PID_HLINKSTemplate_Version SC_Title1SC_DateSC_Produced_By SC_Version SC_ReferenceALckKIhttp://www.nationalarchives.gov.uk/documents/functional_requirements.pdf2sHhttp://www.nla.gov.au/padi/"3Ehttp://www.interpares.org/u7B,http://www.rnib.org.uk/softwareaccesscentre]?rhttp://www.equalityhumanrights.com/en/publicationsandresources/Disability/Pages/Websiteaccessibilityguidance.aspx[<Fhttp://www.verva.se/english/international-network/the-accent-project/(v9'http://www-03.ibm.com/able/guidelines/u76,http://www.rnib.org.uk/softwareaccesscentree=3'http://www.rnib.org.uk/webaccesscentreua0http://www.w3.org/WAI/d'-(http://dlmforum.typepad.com/gdlines.pdfkk*0http://europa.eu/scadplus/leg/en/lvb/124118.htm'1http://www.wfmc.org/standards/referencemodel.htmX$http://www.w3.org/TR/REC-xml/(g!http://www.w3.org/TR/xkms/ht/http://www.itu.int/rec/T-REC-X.509-200003-I/enau;http://partners.adobe.com/public/developer/tiff/index.html2q;http://www.itu.int/ITU-T/studygroups/com17/oid/X.667-E.pdf%<$http://www.ietf.org/rfc/rfc2822.txt&<$http://www.ietf.org/rfc/rfc2821.txtjh$http://www.icacds.org.uk/icacds.htmZ !http://www.ica.org/en/node/30230&3 0http://csrc.nist.gov/publications/PubsFIPS.htmld'(http://dlmforum.typepad.com/gdlines.pdf5http://www.interpares.org/ip2/ip2_terminology_db.cfmkIhttp://www.nationalarchives.gov.uk/documents/functional_requirements.pdfJIhttp://www.arkivverket.no/arkivverket/lover/elarkiv/noark-4/english.htmlU?>http://www.naa.gov.au/Images/ERMSspecifications_tcm2-1007.pdf !http://jitc.fhu.disa.mil/recmgt/"3http://www.interpares.org/b'http://www.bsi-global.com/@KJhttp://www.nationalarchives.gov.uk/electronicrecords/reqs2002/default.htm &http://dublincore.org/documents/dces/  T_Volume4T_VitalRecord& T_VersionzT T_UserRole&T_UserProfilelY T_UserGroupd^T_UserwW T_Transfer  T_SubFilerIT_StubxPT_SecurityClearance`MT_SecurityCategoryjUT_Role#"T_RetentionandDispositionSchedulepI T_RepetoryhE T_Rendition8 T_Rendezvous , T_Render{AT_Registrationh@ T_Redaction/ T_Redact- T_RecordType1 T_Record' T_ProfilekVT_Presentation%T_PhysicalRecordGT_PhysicalFilebZT_PDFA;T_PDFoQ T_PaperFileuMT_Owner~AT_Open*T_NonCaseFile{MT_MetadataStub}[ T_Metadata ? T_Keyword)| T_Import|XyT_Group)v T_Format %s T_FileFormat~SpT_Files<m T_Export|^jT_ERMSeAgT_ElectronicRecord$dT_ElectronicDocument/a T_Electronic|H^T_EDMStH[T_DocumentTypepTX T_Document .UT_DispositioniRRT_DisposalHold>O T_Digital LT_Destructionb[I T_CustodianjAFT_ConfigurationTimep@C T_Component2@T_CMS$= T_Closedx@:T_ClosenP7 T_ClearancemE4T_ClassificationScheme,1T_ClassificationCode&.T_Classificationv@+T_Class-( T_CaseWorkernW% T_CaseFile8" T_Capture7 T_BulkImport&T_AuthorisedUsergUT_Authenticity: T_AuditTrail6T_AggregationcAT_Administrator ( T_AdministrativeRole7 Gl_ClearanceU|Gl_CMS,wGl_Rendezvous<b Gl_Custodian<, Gl_RedactSxGl_SecurityCategory' Gl_Redaction&Gl_PhysicalRecord\zGl_PDFAo Gl_Version\zGl_PDFA6Gl_FileFormat7Gl_ElectronicDocumentHcGl_RegistrationYw Gl_Digital>Gl_BulkImportingHcGl_MetadataStubLjGl_Stub9 Gl_Render" Gl_Rendition/ ]Gl_RecordType\dWGl_EDMSQiQGl_AggregationBoN Gl_TransferQqKGl_DisposalHoldIzHGl_Disposition89Gl_CaseWorker@6 Gl_Profile*3 Gl_OwnerAo0Gl_UserProfile7-Gl_SecurityClearance>* Gl_UserGroupWr'Gl_RoleSl$Gl_VitalRecordK!Gl_AuthenticityXu Gl_keywordGh Gl_Document& Gl_Administrator(Gl_Destructon' Gl_Component' Gl_CloseJlGl_DocumentType6 Gl_PaperFile>  Gl_RepertoryEgGl_PhysicalFile' Gl_ClosedHfGl_OpenMdGl_NonCaseFile+Gl_Electronic.Gl_ClassificationCode_sGl_Presentation: Gl_Format1Gl_AuditTrail0Gl_RetentionSchedule: Gl_Import&Gl_ConfigurationTime3 Gl_AuthorisedUserUv Gl_CaseFile> Gl_UserGroupVb Gl_UserRole/  Gl_Export]e Gl_Metadata*Gl_AdministrativeRoleK|Gl_User/Gl_Classification_o Gl_Capture2 Gl_Record7|Gl_ElectronicDocumentJdyGl_ERMSGqv Gl_SubFile"s Gl_Volume'p Gl_ClassQfmGl_FileGujGl_ClassificationScheme-4dhttp://www.dlm-network.org/-4Rhttp://www.dlm-network.org/-4Ohttp://www.dlm-network.org/0H_Toc2014784860B_Toc2014784850<_Toc20147848406_Toc20147848300_Toc2014784820*_Toc2014784810$_Toc2014784800_Toc2014784790_Toc2014784780_Toc2014784770 _Toc2014784760_Toc2014784750_Toc2014784740_Toc2014784730_Toc2014784720_Toc2014784710_Toc2014784700_Toc2014784690_Toc2014784680_Toc2014784670_Toc2014784660_Toc2014784650_Toc2014784640_Toc2014784630_Toc2014784620_Toc2014784610_Toc2014784600_Toc2014784590_Toc2014784580_Toc2014784570_Toc2014784560_Toc2014784550_Toc2014784540_Toc2014784530|_Toc2014784520v_Toc2014784510p_Toc2014784500j_Toc2014784490d_Toc2014784480^_Toc2014784470X_Toc2014784460R_Toc2014784450L_Toc2014784440F_Toc2014784430@_Toc2014784420:_Toc20147844104_Toc2014784400._Toc2014784390(_Toc2014784380"_Toc2014784370_Toc2014784360_Toc2014784350_Toc2014784340 _Toc2014784330_Toc2014784320_Toc2014784310_Toc2014784300_Toc2014784290_Toc2014784280_Toc2014784270_Toc2014784260_Toc2014784250_Toc2014784240_Toc2014784230_Toc2014784220_Toc2014784210_Toc2014784200_Toc2014784190_Toc2014784180_Toc2014784170_Toc2014784160_Toc2014784150_Toc2014784140_Toc2014784130_Toc2014784120_Toc2014784110_Toc2014784100z_Toc2014784090t_Toc2014784080n_Toc2014784070h_Toc2014784060b_Toc2014784050\_Toc2014784040V_Toc2014784030P_Toc2014784020J_Toc2014784010D_Toc2014784007>_Toc20147839978_Toc20147839872_Toc2014783977,_Toc2014783967&_Toc2014783957 _Toc2014783947_Toc2014783937_Toc2014783927_Toc2014783917_Toc201478390r1http://ec.europa.eu/transparency/archival_policyQZhttp://dlm-network.org/moreq2 5http://www.interpares.org/ip2/ip2_terminology_db.cfmr1http://ec.europa.eu/transparency/archival_policy-4http://www.dlm-network.org/-4http://www.dlm-network.org/1.5MoReq2 Specification v4.2January 2008    !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~                           ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~                            ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~                            ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~                            ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~                            ! " # % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~        !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Root Entry FuknData $ e 1Table%_ WordDocumentGSummaryInformation(DocumentSummaryInformation8@fCompObjq  FMicrosoft Office Word Document MSWordDocWord.Document.89q