Product Speciffic Terms Sample Clauses

Open Split View

Download

Share

Cite

Product Speciffic Terms. 33.1. The Customer agrees to the following terms for usage of the ‘Tribepad Importer’ Google Chrome browser extension;

Sample 1

Save

Copy

Related to Product Speciffic Terms

• Product Specific Terms these terms apply to specific Products referenced in this section.

• Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

• Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.

• Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

• 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.

• Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

• ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

• EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

• NON-COMPLYING PRODUCT WATER & SEDIMENT CONTENT – PRICE DEDUCTION When the delivered fuel oil’s water and sediment content is found to be greater than three hundredths (0.03%) of a percent for Xxxxxxxx, Xx. 0 and No. 2, a deduction from the contracted price shall be taken at the rate of one (1%) percent for every two hundredths (0.02%) of a percent above the specified limit. (i.e., 0.02% above limit equals a 1% deduction, 0.04% above limit equals a 2% deduction, 0.06% above equals a 3% deduction) No. 4 fuel oil shall have an excess water and sediment content adjustment at the rate of one-tenth percent (0.1%) of invoice for every one-tenth (0.1%) in excess of five-tenths (0.5%) up to and including one percent (1.0%) and at the rate of two-tenths percent (0.2%) of invoice for every one-tenth percent (0.1%) in excess of one percent (1.0%).

• Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).