NON-RESTRICTIVE SPECIFICATION Sample Clauses

POPULAR SAMPLE Copied 1 times
NON-RESTRICTIVE SPECIFICATION. Consultant shall not produce a design or specification that would be restrictive or written in a manner as to contain proprietary requirements other than those based on performance, unless such requirements are necessary to demonstrate a specific outcome or to provide for necessary interchangeability of parts and equipment. Consultant shall justify, in writing, the use of any sole source. Where brand names are identified, they shall be followed by the salient product performance characteristics and the words “or approved equal” so that comparable quality or utility may be determined.
View SourceView Similar (2)

Related to NON-RESTRICTIVE SPECIFICATION

  • PROPRIETARY/RESTRICTIVE SPECIFICATIONS If a prospective bidder considers the specification contained herein to be proprietary or restrictive in nature, thus potentially resulting in reduced competition, they are urged to contact the Procurement Division prior to bid opening. Specifications which are unrelated to performance will be considered for deletion via addendum to this Invitation for Bids.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • ACCEPTABLE USE RESTRICTIONS You must: • not use the App or any Service in any unlawful manner, for any unlawful purpose, or in any manner inconsistent with these terms, or act fraudulently or maliciously, for example, by hacking into or inserting malicious code, such as viruses, or harmful data, into the App, any Service or any operating system; • not infringe our intellectual property rights or those of any third party in relation to your use of the App or any Service, including by the submission of any material (to the extent that such use is not licensed by these terms); • not transmit any material that is defamatory, offensive or otherwise objectionable in relation to your use of the App or any Service; • not use the App or any Service in a way that could damage, disable, overburden, impair or compromise our systems or security or interfere with other users; and • not collect or harvest any information or data from any Service or our systems or attempt to decipher any transmissions to or from the servers running any Service.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-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.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.