Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.
Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.
Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Month, Assuming Institution shall provide Receiver:
Packet Switching Capability 4.5.1 The packet switching capability network element is defined as the function of routing or forwarding packets, frames, cells or other data units based on address or other routing information contained in the packets, frames, cells or other data units.
DOES THE SPR NEED TO BE UPDATED IF INFORMATION CHANGES Yes. It remains a continuing obligation of the principal or his/her authorized agent to update the SPR whenever any of the information provided on the initial form changes. WHERE DO THE SPR AND ANY UPDATES NEED TO BE FILED? The SPR needs to be filed with the County Department or County Division processing the application or matter. If and when an additional expenditure is incurred subsequent to the initial filing of the SPR, an amended SPR needs to be filed with the County Department or County Division where the original application, including the initial SPR, was filed. WHEN DO THE SPR AND ANY UPDATES NEED TO BE FILED? In most cases, the initial SPR needs to be filed with the other application forms. The SPR and any update must be filed with the appropriate County Department or County Division not less than seven (7) days prior to the BCC hearing date so that they may be incorporated into the BCC agenda packet. (See Section 2-354(b), Orange County Code.) When the matter is a discussion agenda item or is the subject of a public hearing, and any additional expenditure occurs less than 7 days prior to BCC meeting date or updated information is not included in the BCC agenda packet, the principal or his/her authorized agent is obligated to verbally present the updated information to the BCC when the agenda item is heard or the public hearing is held. When the matter is a consent agenda item and an update has not been made at least 7 days prior to the BCC meeting or the update is not included in the BCC agenda packet, the item will be pulled from the consent agenda to be considered at a future meeting.