FEDERAL SEAL(S), LOGOS, AND FLAGS Sample Clauses

FEDERAL SEAL(S), LOGOS, AND FLAGS. The Contractor shall not use the seal(s), logos, crests, or reproductions of flags or likenesses of Federal agency officials without specific pre-approval.
Sample 1Sample 2Sample 3See All (34)
AutoNDA by SimpleDocs
FEDERAL SEAL(S), LOGOS, AND FLAGS. The Supplier cannot use the seal(s), logos, crests,
Sample 1Sample 2Sample 3See All (15)
FEDERAL SEAL(S), LOGOS, AND FLAGS. In addition to the prohibitions of the North Carolina General Contract Terms & Conditions section above entitled “ADVERTISING,” the Vendor shall not use the seal(s), logos, crests, or reproductions of flags of a federal agency providing funding herein, or likenesses of federal agency officials without specific pre-approval of the relevant federal agency.
Sample 1Sample 2Sample 3See All (4)
FEDERAL SEAL(S), LOGOS, AND FLAGS. In addition to the prohibitions of the BUYER Master Agreement Terms and Conditions above, SUPPLIER shall not use the seal(s), logos, crests, or reproductions of flags of a federal agency providing funding herein, or likenesses of federal agency officials without specific pre-approval of the relevant federal agency.
Sample 1

Related to FEDERAL SEAL(S), LOGOS, AND FLAGS

  • LOGOS, AND FLAGS The Supplier cannot use the seal(s), logos, crests, or reproductions of flags or likenesses of Federal agency officials without specific pre-approval.

  • DHS Seal, Logo, and Flags The Contractor shall not use the Department of Homeland Security (DHS) seal(s), logos, crests, or reproductions of flags or likeness of DHS agency officials without specific FEMA pre-approval.

  • File Naming Conventions Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where: {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used; {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”; {type} is replaced by: “full”, if the data represents a Full Deposit; “diff”, if the data represents a Differential Deposit; “thin”, if the data represents a Bulk Registration Data Access file, as specified in Section 3 of Specification 4; {#} is replaced by the position of the file in a series of files, beginning with “1”; in case of a lone file, this must be replaced by “1”. {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: {ext} is replaced by “sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!