Requirements and Recommendations Sample Clauses

Requirements and Recommendations. From the use cases described in the previous sections, a set of high-level requirements and recommendations can be derived. These provide a framework for the technical and governance analysis in subsequent sections.
AutoNDA by SimpleDocs
Requirements and Recommendations. Requirement 28 The Blockchain should implement the data elements described in Sections 8.3.1, 8.3.2, 8.3.3, and 8.3.4, and the data model as described in Section 8.3.5. Requirement 29 The Blockchain should provide the APIs as described in Section 8.4

Related to Requirements and Recommendations

  • Conclusion and Recommendations D. Evaluations for Offenders without a sex offense conviction shall answer the following additional referral questions in the evaluations:

  • Conclusions and Recommendations The demonstration and evaluation process provided an opportunity to test community specific tools with a range of end users from the memory institution domain and to gain greater insight into both the current and future evolution of the SHAMAN prototypes for preservation, access and re-use. Xxxx et al. (2000) in their user evaluation study of the Alexandria Digital Library which incorporated the evaluation of a Web prototype by earth scientists, information specialists and educators raised four key questions in relation to their findings that SHAMAN may be well advised to consider, they are paraphrased here with our conclusions from the investigations. What have we learned about our target organizations and potential users?  Memory institutions are most definitely not a homogenised group; their needs and requirements differ greatly across the domain.  Representatives of the archives community are agreed on the benefits of SHAMAN‟s authenticity validation function.  The representatives of government information services remained unconvinced as to the need or benefit of grid technologies or distributed ingest while librarians saw the value of grid access as an asset of the framework. What have we learned about the evaluation approach for digital preservation?  Within the limits of the exercise, in terms of time-frame and resources, the approach adopted has generated useful information for the further development of demonstrators and for the development of the SHAMAN framework overall. What have we learned about the SHAMAN ISP1 demonstrator?  Respondents to the evaluation questionnaires and the focus groups indicate that, overall, the presentation of the demonstrator worked effectively and that, in general, participants in the demonstration and evaluation events were able to understand the intentions of the demonstration and to apply the ideas presented to their own context. What have we learned about the applicability of the SHAMAN framework to memory institutions?  Respondents to the questionnaires and participants in the focus groups readily identified the value of the SHAMAN framework to their own operations. The majority had not yet established a long-term digital preservation policy, but recognized the need. Generally, the concepts of distributed ingest and grid operations found favour.  Virtually all practitioners in the focus groups, however, drew attention to need of a lower level demonstration that would be closer to their everyday preservation troubles, especially for digital preservation to be applied to non-textual materials, such as film, photographs and sound archives. In addition to the criteria suggested by Xxxx et al., we can add a further project-related question: What have we learned that has implications for the training and dissemination phase of the Project?  It was not part of the remit of the demonstration and evaluation specifically to discover information of relevance to the training and dissemination function. However, a number of factors will affect the efficacy of any training programme in particular. o First, no common understanding of digital preservation can be assumed of the potential target audiences for training. Consequently, it is likely that self-paced learning materials will be most effective in presenting the SHAMAN framework. o Secondly, the aims of SHAMAN as a project must be conveyed clearly: specifically, that it is a kind of „proof-of-concept‟ project and is not intended to deliver a package of programs capable of being implemented by institutions. o Thirdly, it needs to be emphasised that the SHAMAN framework is not limited to text documents; it can be applied to materials of all kinds. However, the demonstrations relate to bodies of material that were actually available for use. o Fourthly, the existing presentation materials are capable of being adapted for use in training activities. o Finally, the target audiences will appreciate the possibility of online access to the demonstrator, which will need to have very great ease of access in order that people with diverse backgrounds are able to use it with equal facility. We believe that, overall, WP14 has met its aims and objectives in this demonstration and evaluation of ISP1. Valuable lessons have been learnt by all parties involved, which will be transferred to the evaluation of ISP2 in the coming months.

  • Representations and Recommendations Unless otherwise stated in writing, neither Xxxxxxxx Realty Inc, nor its brokers or licensees have made, on their own behalf, any representations or warranties, express or implied, with respect to any element of the Property including but not limited to, the legal sufficiency, legal effect, or tax consequences of this transaction. Any information furnished by either party should be independently verified before that party relies on such information. Xxxxxxxx Realty Inc. recommends that Buyer consult its attorneys and accountants before signing this Agreement regarding the terms and conditions herein and that Seller satisfy itself as to the financial ability of Buyer to perform.

  • Manufacturer's Recommendations All work or materials shall be installed in accordance with the manufacturer's recommendations and requirements. The Contractor shall obtain the manufacturer’s recommendations and requirements, for its use at the Site in executing the Work, copies of bulletins, circulars, catalogues, or other publications bearing the manufacturer’s titles, numbers, editions, dates, etc. If the manufacturer’s recommendations and requirements are not available, the Contractor shall request installation instructions from the Design Professional.

  • Regulatory Requirements and Governing Law 43 14.1 Regulatory Requirements. 43 14.2 Governing Law 44 ARTICLE 15. NOTICES 44 15.1 General. 44 15.2 Xxxxxxxx and Payments. 44 15.3 Alternative Forms of Notice 44 15.4 Operations and Maintenance Notice 44 ARTICLE 16. FORCE MAJEURE 45 16.1 Force Majeure 45 ARTICLE 17. DEFAULT 45 17.1 Default. 45 ARTICLE 18. INDEMNITY, CONSEQUENTIAL DAMAGES AND INSURANCE 46 18.1 Indemnity. 46 18.2 No Consequential Damages. 47 18.3 Insurance 47 ARTICLE 19. ASSIGNMENT 49 19.1 Assignment. 49 ARTICLE 20. SEVERABILITY 49 20.1 Severability. 49 ARTICLE 21. COMPARABILITY 50 21.1 Comparability. 50 ARTICLE 22. CONFIDENTIALITY 50 22.1 Confidentiality. 50 ARTICLE 23. ENVIRONMENTAL RELEASES 53 23.1 Developer and Connecting Transmission Owner Notice 53 ARTICLE 24. INFORMATION REQUIREMENT 53 24.1 Information Acquisition. 53 24.2 Information Submission by Connecting Transmission Owner 54 24.3 Updated Information Submission by Developer 54 24.4 Information Supplementation 54 ARTICLE 25. INFORMATION ACCESS AND AUDIT RIGHTS 55 25.1 Information Access. 55 25.2 Reporting of Non-Force Majeure Events. 55 25.3 Audit Rights. 56 25.4 Audit Rights Periods. 56 25.5 Audit Results. 56 ARTICLE 26. SUBCONTRACTORS 56 26.1 General. 56 26.2 Responsibility of Principal. 57 26.3 No Limitation by Insurance 57 ARTICLE 27. DISPUTES 57 27.1 Submission 57 27.2 External Arbitration Procedures. 57 27.3 Arbitration Decisions. 58 27.4 Costs. 58 27.5 Termination 58 ARTICLE 28. REPRESENTATIONS, WARRANTIES AND COVENANTS 58 28.1 General. 58 ARTICLE 29. MISCELLANEOUS 59 29.1 Binding Effect. 59 29.2 Conflicts. 59 29.3 Rules of Interpretation 59 29.4 Compliance 60 29.5 Joint and Several Obligations. 60 29.6 Entire Agreement. 60 29.7 No Third Party Beneficiaries. 60 29.8 Waiver 60 29.9 Headings. 61 29.10 Multiple Counterparts. 61 29.11 Amendment. 61 29.12 Modification by the Parties. 61 29.13 Reservation of Rights. 61 29.14 No Partnership 62 29.15 Other Transmission Rights. 62 Appendices STANDARD LARGE GENERATOR INTERCONNECTION AGREEMENT THIS STANDARD LARGE GENERATOR INTERCONNECTION AGREEMENT (“Agreement”) is made and entered into this 17th day of April 2013, by and among Erie Boulevard Hydropower, LP (a limited partnership subsidiary of Brookfield Renewable Power), a company organized and existing under the laws of the State of New York (“Developer” with a Large Generating Facility), the New York Independent System Operator, Inc., a not-for-profit corporation organized and existing under the laws of the State of New York (“NYISO”), and Niagara Mohawk Power Corporation d/b/a National Grid, a corporation organized and existing under the laws of the State of New York (“Connecting Transmission Owner”). Developer, the NYISO, or Connecting Transmission Owner each may be referred to as a “Party” or collectively referred to as the “Parties.”

  • Organizational Matters 16 Section 2.1. Organization.....................................................16 Section 2.2. Name ............................................................16 Section 2.3. Resident Agent; Principal Office.................................16 Section 2.4.

  • Disclosure Requirements (a) The Estate Agent or Salesperson *has / does not have(1) (11) a conflict or potential conflict of interest in acting for the Tenant. If the Estate Agent or Salesperson has a conflict or potential conflict of interest, the details are as follows:

  • Safeguarding requirements and procedures (1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls:

  • COMPLIANCE WITH LEGAL OBLIGATIONS Contractor shall procure and maintain for the duration of this Contract any state, county, city or federal license, authorization, waiver, permit, qualification or certification required by statute, ordinance, law, or regulation to be held by Contractor to provide the goods or services required by this Contract. Contractor will be responsible to pay all taxes, assessments, fees, premiums, permits, and licenses required by law. Real property and personal property taxes are the responsibility of Contractor in accordance with NRS 361.157 and 361.159. Contractor agrees to be responsible for payment of any such government obligations not paid by its subcontractors during performance of this Contract.

  • Compliance with Laws and Rules You agree to comply with all state and federal laws, rules, and regulations applicable to you and to your use of the Services (the “Laws”), including the operating rules of all systems used to provide Services to you (the “Rules”), and to provide evidence reasonably satisfactory to us of the same if requested by us. You agree not to use the Service for any illegal purpose, including but not limited to illegal Internet gambling. Without limitation, you agree and acknowledge that the Services may not be used by you in violation of the laws of the United States, including sanction laws administered by the Office of Foreign Asset Controls. You acknowledge and agree that the software you use to access Services may be subject to restrictions and controls imposed by the Export Administration Act and the Export Administration Regulations. You agree and certify that neither the software nor any direct product thereof is being or will be used by you for any purpose prohibited by these Acts. Additionally, each Account and the Services will be subject to and governed by the following: • The terms or instructions appearing on a screen when using a Service; • Our Deposit Agreement, and our rules, procedures, and policies; • Applicable provisions of the rules of the National Automated Clearing House Association (NACHA) for bill payments facilitated through the ACH; • Applicable state and federal laws, rules, and regulations; and • The rules of other funds transfer systems when used in connection with a Service. Nothing in this Agreement relieves you of any obligation you may have under the Laws or the Rules, and this Agreement is deemed modified to the extent necessary to allow or require you to comply with the same. You will implement and maintain procedures, including retention of legal or compliance services, to ensure that you are able to comply with all current and future Laws and Rules, including any changes to them. We are not obligated to provide information, updates or notice of or regarding the Laws or the Rules, even if we are aware of the same and of the potential for material impact on you and your use of the Services, and your indemnification and other obligations to us are not relieved or reduced by our not providing the same to you. If we do provide information, updates or notices of or regarding the Laws or the Rules to you, we are not responsible for the accuracy of the same and may discontinue doing so at any time.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!