Existing path Sample Clauses

Existing path creation tools One of the core elements of PATHS system will be functionality to support the development of paths, as a means of exploring, signposting and engaging with cultural heritage collections. This functionality is not entirely novel, and a review of the state of the art (see PATHS Deliverable D1.2), reveals several systems that offer facilities to support this type of activity to a greater or lesser degree and there are others emerging on a regular basis as we progress through the project. Selected examples of these types of systems are presented in Table 5, and some of which have been used in the early experiments relating to PATHS user requirements, the results of which are presented in Section 7. Table 5 Examples of existing path-creation tools Path-creation tool Web site Type Site specific Audience Walden‟s Paths xxxx://xxxxxx.xxxx.xxxx.xxx/xxxxxx/p ublisher/ Paths N Teachers Trailmeme xxxxx://xxxxxxxxx.xxx/home Paths N Teachers & general First World War Poetry Digital Archive xxxx://xxx.xxxx.xx.xx.xx/ww1lit/educ ation/pathways Paths Timeline Mind map Y Teachers Storify xxxx://xxxxxxx.xxx/ Content curation N Bloggers & social media users Pearltrees xxxx://xxx.xxxxxxxxxx.xxx/ Mind map Tree N Bloggers & general Flickr Galleries xxxx://xxx.xxxxxx.xxx/galleries/ Content curation Y Flickr users Dipity xxxx://xxx.xxxxxx.xxx/ Timeline N Bloggers, teachers, general It will be especially important to monitor developments of this type of software in support of digital cultural heritage collections, of which there are few to date, but the Trailmeme and First World War Poetry project show that this may change, especially in contexts where there is a need or a desire to create learning resources that are then to be shared freely amongst other peer groups and professional networks, or simply to support students‟ informal learning opportunities with regard to key topics within a collection.
Sample 1
AutoNDA by SimpleDocs

Related to Existing path

  • Existing Products 1. Hardware - Title and ownership of Existing Hardware Product shall pass to Authorized User upon Acceptance.

  • License Agreement The Trust shall have the non-exclusive right to use the name "Invesco" to designate any current or future series of shares only so long as Invesco Advisers, Inc. serves as investment manager or adviser to the Trust with respect to such series of shares.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.

  • Vendor Agreement (Part 1)

  • Agreement to Lease Landlord agrees to lease to Tenant and Tenant agrees to lease from Landlord, according to the terms and conditions set forth herein, the Premises.

  • Vendor Agreement 230105 Vendor Agreement pdf The Vendor Agreement must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, Vendor Name placed in the line provided at the top, and uploaded to this location. If Vendor has proposed deviations to the Vendor Agreement, Vendor may assert so in the Attribute Questions and those shall be addressed during evaluation.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Agreement Scope The scope of this Agreement is as prescribed in section 46 of the Act, setting out: • the health services to be provided to the State by the HSP, • the TTR in support of the health services to be provided, • the funding to be provided to the HSP for the provision of the health services, including the way in which the funding is to be provided, • the performance measures and operational targets for the provision of the health services by the HSP, • how the evaluation and review of results in relation to the performance measures and operational targets is to be carried out, • the performance data and other data to be provided by the HSP to the Department CEO, including how, and how often, the data is to be provided, and • any other matter the Department CEO considers relevant to the provision of the health services by the HSP. Where appropriate, reference will be made in this Agreement to Policy Frameworks issued by the Department CEO pursuant to Part 3, Division 2 of the Act.

  • License Transfer You may not transfer the software to a third party without Microsoft’s prior written consent. If permitted, there may be additional charges for transferring the software to a third party.

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