Search Paths by topic Sample Clauses

Search Paths by topic. The user requirement states that registered users can search for objects via related Paths. For the first prototype we interpret this to say that all users (registered or not) should be able to search for Paths about a given topic. Source: p133/B1 Tags: Search, Paths
AutoNDA by SimpleDocs

Related to Search Paths by topic

  • APPLICABILITY TO SUBCONTRACTORS Respondent agrees that all contracts it awards pursuant to the contract awarded as a result of this Agreement will be bound by the foregoing terms and conditions.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

  • Removal of Improvements Grantor shall not demolish or remove any Improvements from the Real Property without Lender's prior written consent. As a condition to the removal of any Improvements, Lender may require Grantor to make arrangements satisfactory to Lender to replace such Improvements with Improvements of at least equal value.

  • Patent Maintenance All annuity and maintenance fees that are necessary in order to keep the Patents in force as of the Effective Date have been paid by Seller, and no payment of annuities or fees, or papers to be filed in patent offices, are required to be made within the three-month period after the Effective Date.

  • Scope of Collaboration As part of the collaboration, the Controllers will act as Joint Controller. The roles of the Controller and the associated tasks are specified in more detail in Appendix 1. If one party is solely responsible for a data processing operation, this party will implement all relevant data protection provisions on its own responsibility. However, such data processing procedures are not subject to this Agreement. Joint data processing and the type of Personal Data collected and processed within the framework of collaboration are specified in Appendix 1.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • Use of Attachment Facilities by Third Parties Purpose of Attachment Facilities.‌‌ Except as may be required by Applicable Laws and Regulations, or as otherwise agreed to among the Parties, the Attachment Facilities shall be constructed for the sole purpose of interconnecting the Large Generating Facility to the New York State Transmission System and shall be used for no other purpose.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract. a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract. b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.

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