WHO WILL REVIEW THE INFORMATION DISCLOSED ON THE RELATIONSHIP DISCLOSURE FORM AND ANY UPDATES? The information disclosed on this form and any updates will be a public record as defined by Chapter 119, Florida Statutes, and may therefore be inspected by any interested person. Also, the information will be made available to the Mayor and the BCC members. This form and any updates will accompany the information for the applicant’s project or item. However, for development-related items, if an applicant discloses the existence of one or more of the relationships described above and the matter would normally receive final consideration by the Concurrency Review Committee or the Development Review Committee, the matter will be directed to the BCC for final consideration and action following committee review.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
WHO WILL BE MADE AWARE OF THE INFORMATION DISCLOSED ON THE SPR AND ANY UPDATES? The information disclosed on the SPR and any updates will be a public record as defined by Chapter 119, Florida Statutes, and therefore may be inspected by any interested person. Also, the information will be made available to the Mayor and the BCC members. This information will accompany the other information for the principal’s project or item.
Return of material containing or pertaining to the Confidential Information 7.1 The Disclosing Party may, at any time, and in its sole discretion request the Receiving Party to return any material and/or data in whatever form containing, pertaining to or relating to Confidential Information disclosed pursuant to the terms of this Agreement and may, in addition request the Receiving Party to furnish a written statement to the effect that, upon such return, the Receiving Party has not retained in its possession, or under its control, either directly or indirectly, any such material and/or data.
Voice Grade Unbundled Copper Sub-Loop Unbundled Sub-Loop Distribution – Intrabuilding Network Cable (aka riser cable)
Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.
Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:
Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.
Unbundled Voice Loop – SL2 (UVL-SL2 Loops may be 2-wire or 4-wire circuits, shall have remote access test points, and will be designed with a DLR provided to NewPhone. SL2 circuits can be provisioned with loop start, ground start or reverse battery signaling. OC is provided as a standard feature on XX0 Xxxxx. The OC feature will allow NewPhone to coordinate the installation of the Loop with the disconnect of an existing customer’s service and/or number portability service. In these cases, BellSouth will perform the order conversion with standard order coordination at its discretion during normal work hours.
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.
