City-wide storytelling requirements Sample Clauses

City-wide storytelling requirements. The city-wide storytelling scenario includes the following components that rely on FLAME: Î Story Computations – A story engine is required for users to experience an interactive narrative. DRZ had previously developed a system for computer-assisted narrative animation synthesis, called “CANVAS: Computer-Assisted Narrative Animation Synthesis” [3]. The system uses a formal representation of a story world to enable computer assisted generation of 3D animated stories. In the context of FLAME, DRZ has been developing an interactive version of the system, called “iCANVAS”, which enables the computer-assisted telling of interactive stories. With iCANVAS, the user may be represented as a character in the story, has agency to interact with the story world and influence narrative progression. Interactive stories are pre-authored and then consumed based on user participation. Virtual characters may guide the user to experience an author intended narrative. In the context of city-wide storytelling, elements of the story (e.g. characters, props and places) are associated with physical locations of a city, which are in proximity to FLAME- enabled infrastructure.
AutoNDA by SimpleDocs

Related to City-wide storytelling requirements

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Screening Requirements Practitioner shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements. a. Practitioner shall screen all prospective Covered Persons against the Exclusion List prior to engaging their services and, as part of the hiring or contracting process, shall require such Covered Persons to disclose whether they are Ineligible Persons.‌ b. Practitioner shall screen all current Covered Persons against the Exclusion List within 30 days after the Effective Date and on a monthly basis thereafter.‌ c. Practitioner shall require all Covered Persons to disclose immediately if they become an Ineligible Person.‌ Practitioner shall maintain documentation in order to demonstrate that Practitioner: (1) has checked the Exclusion List (i.e., a print screen of the search results) and determined that its Covered Persons are not Ineligible Persons; and (2) has required its Covered Persons to disclose if they are an Ineligible Person. Nothing in this Section III.D affects Practitioner’s responsibility to refrain from (and liability for) billing Federal health care programs for items or services furnished, ordered, or prescribed by an excluded person. Practitioner understands that items or services furnished by excluded persons are not payable by Federal health care programs and that Practitioner may be liable for overpayments and/or criminal, civil, and administrative sanctions for employing or contracting with an excluded person regardless of whether Practitioner meets the requirements of Section III.D.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.

  • Licensing Requirements (a) Employer and Employee hereby covenant and agree that this Agreement and/or Employee’s employment may be subject to the approval of one or more gaming regulatory authorities (the “Authorities”) pursuant to the provisions of the relevant gaming regulatory statutes (the “Gaming Acts”) and the regulations promulgated thereunder (the “Gaming Regulations”). Employer and Employee hereby covenant and agree to use their best efforts to obtain any and all approvals required by the Gaming Acts and/or Gaming Regulations. In the event that (i) an approval of this Agreement or Employee’s employment by the Authorities is required for Employee to carry out Employee’s duties and responsibilities set forth in Section 3 of this Agreement, (ii) Employer and Employee have used their best efforts to obtain such approval, and (iii) this Agreement or Employee’s employment is not so approved by the Authorities, then this Agreement shall immediately terminate and shall be null and void, thus extinguishing any and all obligations of either party, subject to any surviving obligations of Employee under Sections 9, 10 and 21. (b) If applicable, Employer and Employee hereby covenant and agree that, in order for Employee to discharge the duties required under this Agreement, Employee must apply for or hold a license, registration, permit or other approval (the “License”) as issued by the Authorities pursuant to the terms of the relevant Gaming Act and as otherwise required by this Agreement. In the event Employee fails to apply for and secure, or the Authorities refuse to issue or renew Employee’s License, Employee, at Employer’s sole cost and expense, shall promptly defend such action and shall take such reasonable steps as may be required to either remove the objections or secure or reinstate the Authorities’ approval, respectively. The foregoing notwithstanding, if the source of the objections or the Authorities’ refusal to renew or maintain Employee’s License arise as a result of any of the acts, omissions or events described in Section 1(c) of this Agreement, then Employer’s obligations under this Section 8 also shall not be operative and Employee shall promptly reimburse Employer upon demand for any expenses incurred by Employer pursuant to this Section 8. (c) Employer and Employee hereby covenant and agree that the provisions of this Section 8 shall apply in the event Employee’s duties require that Employee also be licensed by governmental agencies other than the Authorities.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • ORDERING REQUIREMENTS Eligible Purchasers shall order Goods and/or Services from this Contract, consistent with the terms hereof and by using any ordering mechanism agreeable both to Contractor and Purchaser but including, at a minimum, a purchase order. When practicable, Contractor and Purchaser also shall use telephone orders, email orders, web- based orders, and similar procurement methods (collectively “Purchaser Order”). All Purchase Orders must reference the Contract number. The terms of this Contract shall apply to any Purchase Order and, in the event of any conflict, the terms of this Contract shall prevail. Notwithstanding any provision to the contrary, in no event shall any ‘click-agreement,’ software or web-based application terms and conditions, or any other agreement modify the terms and conditions of this Contract.

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