File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
File Search Reports File search reports have been obtained from each Uniform Commercial Code filing office identified with respect to such Grantor in Section 2 hereof, and such search reports reflect no liens against any of the Collateral other than those permitted under the Credit Agreement.
Layout a. Estimate and quantity sheet
(1) List of all bid items
(2) Bid item quantities
(3) Specification item number
(4) Paid item description and unit of measure
b. Basis of estimate sheet (list of materials)
c. General notes and specification data.
d. Condition diagram
(1) Highway and intersection design features
(2) Roadside development
(3) Traffic control including illumination
e. Plan sheet(s)
(1) Existing traffic control that will remain (signs and markings)
(2) Existing utilities
(3) Proposed highway improvements
(4) Proposed installation
(5) Proposed additional traffic controls
(6) Proposed illumination attached to signal poles.
(7) Proposed power pole source
f. Notes for plan layout
g. Phase sequence diagram(s)
(1) Signal locations
(2) Signal indications
(3) Phase diagram
(4) Signal sequence table
(5) Flashing operation (normal and emergency)
(6) Preemption operation (when applicable)
(7) Contact responsible Agency to obtain interval timing, cycle length and offset
h. Construction detail sheets(s)
(1) Poles (State standard sheets)
(2) Detectors
(3) Pull Box and conduit layout
(4) Controller Foundation standard sheet
(5) Electrical chart i. Marking details (when applicable)
Library Borrowing privileges available without charge. Upon retirement an employee shall be issued a permanent individual library card.
Artwork Licensee must use the Java Logo(s) only in the exact form of approved camera-ready artwork or electronic artwork received from Oracle or Oracle's designee.
Directory Publication Nothing in this Agreement shall require Verizon to publish a directory where it would not otherwise do so.
Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.
Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria
