Translation Schedule and Guidelines Sample Clauses

Translation Schedule and Guidelines. Rights Holder will provide the Lead Translator with an Electronic copy of the Book that is editable and not protected by any Digital Rights Management protocol. Lead Translator will deliver the first 10 pages of the Translated Book to Rights Holder for Rights Holder’s approval by the number of days in Appendix A from receipt of the material to be translated. Lead Translator will deliver the completed Translated Book by the number of days in Appendix A from receipt of the material to be translated, as extended pursuant to Section 5(c) (ii) below, if applicable ("Completion Date"). Lead Translator will deliver the Translated Book in the same Electronic format as the original Book, in an editable file with no protection by any Digital Rights Management protocol. Rights Holder and Lead Translator will deliver the Book and the Translated Book through the mechanisms provided by Babelcube within its platform. The name of Lead Translator will be prominently displayed inside the Translated Book as the translator. The name of Editor and Proofreader will be prominently displayed inside the Translated Book as the editor.
Sample 1
AutoNDA by SimpleDocs

Related to Translation Schedule and Guidelines

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Annexes and Protocols The Annexes and the Protocols to this Agreement are an integral part of it. The Joint Committee may decide to amend the Annexes and Protocols.

  • Construction Schedule The progress schedule of construction of the Project as provided by Developer and approved by District.

  • Evaluation Schedule CLIENT REFERENCES The Tenderer shall provide details of his performance on each of the previous projects listed in the “Relevant Experience” returnable schedule. “Client Reference Scorecards” will be completed by each of the respective Clients for the projects listed in the “Relevant Experience” returnable schedule. The following are to be completed by the Client and Principal Agent and is to be supported in each case by a letter of award and the works completion certificate. Both Client and Principal Agent must sign and stamp the documents, failure to obtain both signatures and stamps will result in no allocation of points. PROJECT NAME and SCOPE OF WORK: Principal agent: ................................................................................................................................. Client: .. ..............................................................................................................................................

  • Construction Schedules 10.1 Within seven (7) days of the University’s issuance of a purchase order, the Contractor shall submit to the Project Coordinator three (3) copies of a Construction Schedule for this Project. The Schedule shall be in bar chart form and shall include all aspects of the work, the interrelationship of the various trades and the critical path of the job. The schedule shall include a timeline for the submission, review and approval of shop drawings for critical path items and delivery and installation dates for those same critical path, or long lead time items, (such as electrical transformers and elevator). The Schedule shall coincide with the Contractor’s approved Schedule of Values. The Schedule shall indicate a completion date in advance of the date established for Substantial Completion. The Schedule shall be acceptable to the Architect/Engineer and the Project Coordinator. It shall be revised and reissued at the beginning of every month for the duration of the project. This monthly update progress Schedule shall include a summary comparison of the original schedule and the latest updated schedule (previous month) showing all activity description and dates. These comparison schedules shall be in the form of a summary bar chart, an activity listing report and actual to target comparisons. The reports may include critical activities, float time, duration of each activity, dates of each activity and the network logic (including successors and predecessors of each activity). Included with the written report and electronic copy of the schedule submission noting the above referenced requirements. Failure to provide the Architect/Engineer, or the Project Coordinator with an acceptable, revised Schedule, within seven (7) days of the receipt of a written request, may result in the withholding of the Contractor’s monthly progress payments until such a Schedule is received.

  • Design Guidelines The Owner’s “Design Guidelines” are as published on the Owner’s website (xxxx://xxxxx.xxxxx.xxx/for-vendors/design-guidelines/). In addition to providing a guide to be used in the preparation of design documents for the Owner’s construction projects, the Design Guidelines also contain regulatory code compliance and other Owner requirements. The “Effective Date” (as noted in Section 2.7 of the Design Guidelines), determining which edition will be used for a given project, is set at the beginning of Design Development and will govern the preparation of construction documents for the project unless noted otherwise. Compliance with the Design Guidelines does not relieve the Design Professional from any of its responsibility.

  • Annexes, Appendices and Footnotes The annexes, appendices and footnotes to this Agreement constitute an integral part of this Agreement.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Effect of Addenda, Bulletins, and Change Orders No special implication, interpretation, construction, connotation, denotation, import, or meaning shall be assigned to any provision of the Contract Documents because of changes created by the issuance of any (1) Addendum, (2) Bulletin, or (3) Change Order other than the precise meaning that the Contract Documents would have had if the provision thus created had read originally as it reads subsequent to the (1) Addendum, (2) Bulletin, or (3) Change Order by which it was created.

  • Change Order Formats Formats for Lump Sum Change Orders and for Change Orders based upon either a force account or upon unit pricing with an indeterminate number of units are in Section 7, Forms.

Time is Money Join Law Insider Premium to draft better contracts faster.