File Size Clause Samples

The File Size clause sets limits or requirements regarding the maximum allowable size of files that can be uploaded, transferred, or stored under an agreement. In practice, this clause may specify a precise file size limit (such as 10MB per file) or outline procedures for handling files that exceed the permitted size, such as requiring compression or alternative transfer methods. Its core function is to manage technical constraints, prevent system overloads, and ensure efficient use of resources by controlling the volume of data handled within the contractual relationship.
File Size. The maximum size of each XML file will not exceed 10MB, otherwise it will be rejected by the RS-RRM Platform and the Market Participant will be notified accordingly.
View SourceView Similar (2)
File Size. 2.4.1 Each party shall use reasonable efforts to ensure that Data Communications transmitted in any single file are no greater than 5Mb (five million one hundred twenty thousand bytes) in total size. 2.4.2 If the Data Communications file exceeds 5Mb in size the receiving party may, without liability to the sending party, reject the entire file from processing and notify the sending party of such rejection and the sending party shall attempt to correct the error and retransmit the Data Communications in smaller multiple files. 2.4.3 A Data Communications file rejected pursuant to Section 2.4.2 will not be considered as a properly receipted file pursuant to Section 2.1 of this Agreement.
View SourceView Similar (2)
File Size. The maximum size of each XML file will not exceed 10MB.
View SourceView Similar (2)
File Size. For each file that needs to be uploaded, the maximum file size should be kept to 30 megabytes (MB). If you have a large file, please save large color images (e.g., figures, site photos, maps) and supplemental information (appendices) into separate PDF files.
View Source

Related to File Size

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

  • Workstation/Laptop encryption All workstations and laptops that process and/or store County 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 County Information Security Office.

  • Signs; Exterior Appearance Tenant shall not, without the prior written consent of Landlord, which may be granted or withheld in Landlord’s sole discretion: (i) attach any awnings, exterior lights, decorations, balloons, flags, pennants, banners, painting or other projection to any outside wall of the Project, (ii) use any curtains, blinds, shades or screens other than Landlord’s standard window coverings, (iii) coat or otherwise sunscreen the interior or exterior of any windows, (iv) place any bottles, parcels, or other articles on the window ▇▇▇▇▇, (v) place any equipment, furniture or other items of personal property on any exterior balcony, or (vi) paint, affix or exhibit on any part of the Premises or the Project any signs, notices, window or door lettering, placards, decorations, or advertising media of any type which can be viewed from the exterior of the Premises. Interior signs on doors and the directory tablet shall be inscribed, painted or affixed for Tenant by Landlord at the sole cost and expense of Tenant, and shall be of a size, color and type acceptable to Landlord. Nothing may be placed on the exterior of corridor walls or corridor doors other than Landlord’s standard lettering. The directory tablet shall be provided exclusively for the display of the name and location of tenants.

  • Painting All exterior surfaces and materials requiring paint shall be prime coated plus 2 coats of ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ Pro-Mar alkyd flat exterior finish, or ▇▇▇▇▇▇▇-▇▇▇▇▇▇▇▇ SWP exterior gloss paint. 10.1 Wall Corner Guards: Provide clear plastic guards up to 60” AFF on all outside corners to protect vinyl wall covering.