File Naming Conventions Files will be named according to the following convention: {gTLD}_{YYYY-‐MM-‐DD}_{type}_S{#}_R{rev}.{ext} where:
Public Access to Meetings and Records If the Contractor receives a cumulative total per year of at least $250,000 in City funds or City-administered funds and is a non-profit organization as defined in Chapter 12L of the San Francisco Administrative Code, Contractor shall comply with and be bound by all the applicable provisions of that Chapter. By executing this Agreement, the Contractor agrees to open its meetings and records to the public in the manner set forth in §§12L.4 and 12L.5 of the Administrative Code. Contractor further agrees to make-good faith efforts to promote community membership on its Board of Directors in the manner set xxxxx xx §00X.0 of the Administrative Code. The Contractor acknowledges that its material failure to comply with any of the provisions of this paragraph shall constitute a material breach of this Agreement. The Contractor further acknowledges that such material breach of the Agreement shall be grounds for the City to terminate and/or not renew the Agreement, partially or in its entirety.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Reservations for Registry Operations 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
PUBLIC RECORDS COMPLIANCE (APPLICABLE FOR SERVICE CONTRACTS Orange County is a public agency subject to Chapter 119, Florida Statutes. The Contractor agrees to comply with Florida’s Public Records Law. Specifically, the Contractor shall:
