SAMPLE TYPES OF BOXES Sample Clauses

Open Split View

Download

Share

Cite

SAMPLE TYPES OF BOXES. CRATES — GENERAL SPECIFICATION

Sample 1

Save

Copy

Related to SAMPLE TYPES OF BOXES

• Certain Types of Accounts (a) You may instruct FIIOC to register purchased shares in your name and account as nominee for your customers. If you hold Portfolio shares as nominee for your customers, all Prospectuses, proxy statements, periodic reports, and other printed material will be sent to you, and all confirmations and other communications to shareholders will be transmitted to you. You will be responsible for forwarding such printed material, confirmations, and communications, or the information contained therein, to all customers for whose account you hold any Portfolio shares as nominee. However, we or FIIOC on behalf of itself or the Portfolios will be responsible for the costs associated with your forwarding such printed material, confirmations, and communications. You will be responsible for complying with all reporting and tax withholding requirements with respect to the customers for whose account you hold any Portfolio shares as nominee. (b) With respect to accounts other than those accounts referred to in paragraph 4(a) above, you agree to provide us with all information (including certification of taxpayer identification numbers and back-up withholding instructions) necessary or appropriate for us to comply with legal and regulatory reporting requirements. (c) Accounts opened or maintained pursuant to the NETWORKING system of the National Securities Clearing Corporation ("NSCC") will be governed by applicable NSCC rules and procedures and any agreement or other arrangement with us relating to NETWORKING. (d) If you hold Portfolio shares in an omnibus account for two or more customers, you will be responsible for determining, in accordance with the Prospectus, whether, and the extent to which, a CDSC is applicable to a purchase of Portfolio shares from such a customer, and you agree to transmit immediately to us any CDSC to which such purchase was subject. You hereby represent that if you hold Portfolio shares subject to a CDSC, you have the capability to track and account for such charge, and we reserve the right, at our discretion, to verify that capability by inspecting your tracking and accounting system or otherwise.

• Account Types The Financial Institution agrees that each Collateral Account is, and will be maintained as, either a “securities account” (as defined in Section 8-501 of the UCC) or a “deposit account” (as defined in Section 9-102(a)(29) of the UCC).

• Types of Cash Accounts Cash accounts opened on the books of the Custodian (Principal Accounts) shall be opened in the name of the Fund. Such accounts collectively shall be a deposit obligation of the Custodian and shall be subject to the terms of this Section 7 and the general liability provisions contained in Section 9. Cash accounts opened on the books of a Subcustodian may be opened in the name of the Fund or the Custodian or in the name of the Custodian for its customers generally (Agency Accounts). Such deposits shall be obligations of the Subcustodian and shall be treated as an Investment of the Fund. Accordingly, the Custodian shall be responsible for exercising reasonable care in the administration of such accounts but shall not be liable for their repayment in the event such Subcustodian, by reason of its bankruptcy, insolvency or otherwise, fails to make repayment.

• Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,

• Particular Methods of Procurement of Goods Works and Services (other than Consultants’ Services)

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

• Types of Grievances (A) An Individual Grievance is a grievance initiated by the Union on behalf of an individual employee. (B) A Group Grievance is a grievance initiated by the Union on behalf of a group of employees similarly affected by the Employer’s actions. (C) A Policy Grievance is a grievance by the Union which may involve a matter of general policy or general application of the Collective Agreement. (D) A Union Grievance is a grievance which directly affects the Union. (E) An Employer Grievance is a grievance initiated by the Employer.

• Other Types of Traffic 8.1 Notwithstanding any other provision of this Agreement or any Tariff: (a) the Parties’ rights and obligations with respect to any intercarrier compensation that may be due in connection with their exchange of Internet Traffic shall be governed by the terms of the FCC Internet Order and other applicable FCC orders and FCC Regulations; and, (b) a Party shall not be obligated to pay any intercarrier compensation for Internet Traffic that is in excess of the intercarrier compensation for Internet Traffic that such Party is required to pay under the FCC Internet Order and other applicable FCC orders and FCC Regulations. 8.2 Subject to Section 8.1 of this Attachment, interstate and intrastate Exchange Access, Information Access, exchange services for Exchange Access or Information Access, and Toll Traffic, shall be governed by the applicable provisions of this Agreement and applicable Tariffs. 8.3 For any traffic originating with a third party carrier and delivered by CBB to Verizon, CBB shall pay Verizon the same amount that such third party carrier would have been obligated to pay Verizon for termination of that traffic at the location the traffic is delivered to Verizon by CBB. 8.4 Any traffic not specifically addressed in this Agreement shall be treated as required by the applicable Tariff of the Party transporting and/or terminating the traffic. 8.5 The Parties may also exchange Internet Traffic at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA established hereunder for the exchange of Reciprocal Compensation Traffic. Any intercarrier compensation that may be due in connection with the Parties’ exchange of Internet Traffic shall be applied at such technically feasible Point of Interconnection on Verizon’s network in a LATA in accordance with the FCC Internet Order.

• Categories of Data Subject 2.1. When using this Service, the groups of individual’s data by category • Your end users using the service that you deliver • The personal data about your employees and contractors that bookinglab collects as a Customer of ours to complete account administration and set up

• Categories of Data Subjects Any individual accessing and/or using the Services through the Customer's account ("Users"); and any individual: (i) whose email address is included in the Customer's Distribution List; (ii) whose information is stored on or collected via the Services, or (iii) to whom Users send emails or otherwise engage or communicate with via the Services (collectively, "Subscribers").