{"component": "clause", "props": {"groups": [{"snippet_links": [{"key": "the-contractor-shall", "type": "clause", "offset": [0, 20]}, {"key": "the-installation", "type": "clause", "offset": [28, 44]}, {"key": "requirements-for", "type": "clause", "offset": [94, 110]}, {"key": "separate-file", "type": "clause", "offset": [186, 199]}, {"key": "web-interface", "type": "clause", "offset": [248, 261]}, {"key": "training-materials", "type": "definition", "offset": [300, 318]}, {"key": "the-delivery", "type": "clause", "offset": [502, 514]}, {"key": "technical-proposal", "type": "clause", "offset": [531, 549]}], "size": 5, "snippet": "The contractor shall update the installation/access instructions and system, user, capability requirements for each SRP application and include the installation/access instructions as a separate file with each application\u2019s installation package or web interface. The contractor shall update tutorial training materials for each SRP application. The contractor shall update the screen cast video tutorial, with audio, demonstrating and teaching each application\u2019s features. The contractor shall propose the delivery medium in their technical proposal (e.g.", "samples": [{"hash": "krZcdhmnPYG", "uri": "/contracts/krZcdhmnPYG#pdf-format", "label": "Contract", "score": 23.0013689254, "published": true}, {"hash": "dqBzUbOok5d", "uri": "/contracts/dqBzUbOok5d#pdf-format", "label": "Contract", "score": 23.0013689254, "published": true}, {"hash": "9KorggWVSBP", "uri": "/contracts/9KorggWVSBP#pdf-format", "label": "Contract", "score": 23.0013689254, "published": true}], "hash": "b403dac2942decc2b7a2abf4a02638f9", "id": 1}, {"snippet_links": [{"key": "if-available", "type": "definition", "offset": [47, 59]}, {"key": "our-website", "type": "definition", "offset": [138, 149]}], "size": 4, "snippet": "Provide both a vertical and horizontal format, if available. Both are needed as vertical works best for ads and horizontal works best for our website.", "samples": [{"hash": "iZSXtz0u9i1", "uri": "/contracts/iZSXtz0u9i1#pdf-format", "label": "Sponsorship Agreement", "score": 26.1819916971, "published": true}, {"hash": "6XQwUcqADVy", "uri": "/contracts/6XQwUcqADVy#pdf-format", "label": "Sponsorship Agreement", "score": 25.1916495551, "published": true}, {"hash": "duOUEqhagor", "uri": "/contracts/duOUEqhagor#pdf-format", "label": "Sponsorship Agreement", "score": 21.8021902806, "published": true}], "hash": "fc26583605d3e8593feac2af8c07cff6", "id": 2}, {"snippet_links": [{"key": "the-contractor-shall", "type": "clause", "offset": [77, 97]}, {"key": "available-for-use", "type": "definition", "offset": [135, 152]}, {"key": "by-the-government", "type": "clause", "offset": [153, 170]}], "size": 2, "snippet": "Resolution of 300 dpi with no image compression. All fonts must be embedded. The Contractor shall only use fonts that are licensed and available for use by the Government.", "samples": [{"hash": "ixULWSLgyfC", "uri": "/contracts/ixULWSLgyfC#pdf-format", "label": "Cooperative Agreement", "score": 26.5924419662, "published": true}, {"hash": "bAkaJpJcejZ", "uri": "/contracts/bAkaJpJcejZ#pdf-format", "label": "Cooperative Agreement", "score": 21.9628474228, "published": true}], "hash": "226d48eaa740e9e10fe375abd10c7ea7", "id": 3}, {"snippet_links": [{"key": "lessee-shall", "type": "clause", "offset": [4, 16]}, {"key": "changes-and-modifications", "type": "clause", "offset": [92, 117]}, {"key": "to-the-lessor", "type": "clause", "offset": [157, 170]}, {"key": "certificates-of-occupancy", "type": "clause", "offset": [181, 206]}, {"key": "issued-to", "type": "definition", "offset": [234, 243]}, {"key": "completion-of-construction", "type": "clause", "offset": [252, 278]}, {"key": "compliance-with-applicable-requirements", "type": "clause", "offset": [282, 321]}], "size": 2, "snippet": "The Lessee shall thereafter furnish the Lessor with copies of any updated plans showing all changes and modifications thereto. The Lessee shall also furnish to the Lessor copies of certificates of occupancy or other similar documents issued to certify completion of construction in compliance with applicable requirements.", "samples": [{"hash": "98iNcjQk3CV", "uri": "/contracts/98iNcjQk3CV#pdf-format", "label": "Lease Agreement", "score": 25.3737166324, "published": true}], "hash": "74de013a84cbd8f075e397954db5773a", "id": 4}, {"snippet_links": [{"key": "the-documents", "type": "clause", "offset": [15, 28]}, {"key": "its-original", "type": "clause", "offset": [51, 63]}, {"key": "electronic-format", "type": "definition", "offset": [64, 81]}, {"key": "by-the-department", "type": "clause", "offset": [126, 143]}], "size": 1, "snippet": "Any element of the documents shall be delivered in its original electronic format (i.e. MSWord, Excel, AutoCAD\u2026) if requested by the Department", "samples": [{"hash": "b1zF0cy9Jhu", "uri": "/contracts/b1zF0cy9Jhu#pdf-format", "label": "Grant Agreement", "score": 26.9417049427, "published": true}], "hash": "c76343a69763fff03c0e60060cbc1de1", "id": 5}, {"snippet_links": [{"key": "design-submittal", "type": "clause", "offset": [29, 45]}, {"key": "commuter-rail", "type": "definition", "offset": [91, 104]}, {"key": "april-2009", "type": "clause", "offset": [121, 131]}, {"key": "addendum-1", "type": "definition", "offset": [134, 144]}, {"key": "light-rail", "type": "clause", "offset": [514, 524]}, {"key": "bus-terminal", "type": "definition", "offset": [1054, 1066]}, {"key": "track-changes", "type": "clause", "offset": [1455, 1468]}, {"key": "maintenance-facility", "type": "definition", "offset": [1504, 1524]}], "size": 1, "snippet": "Denver Union Station Systems Design Submittal o Eagle Scope \u00a7 Denver Union Station Systems Commuter Rail, 15% Submittal, April 2009 \u00a7 Addendum 1, DUS Systems Commuter Rail, 15% Submittal \u2013 Revisions dated September 11, 2009 o Denver Union Station 30% Systems Commuter Rail Design (by DUS Infrastructure Contractor) \u00a7 Addendum 1, DUS Systems Commuter Rail, 30% Submittal-Drawings, April 3, 2009 \u00a7 Addendum 1, DUS Systems Commuter Rail, 30% Submittal-Specifications, April 3, 2009 o Denver Union Station 30% Systems Light Rail Design (by DUS Infrastructure Contractor) \u00a7 Denver Union Station Light Rail Submittal \u2022 Denver Union Station Light Rail 30% Submittal, Oct. 2008 \u2022 Denver Union Station Light Rail 30% Submittal, Systems Specifications, Oct. 2008 \u00a7 Denver Union Station Light Rail Submittal Update \u2022 Denver Union Station Light Rail 30% Submittal Update, April 2009 \u2022 Denver Union Station Light Rail 30% Submittal Systems Specifications, April 2009 o Denver Union Station 30% Systems Design Submittal, Oct. 2008 (by DUS Infrastructure Contractor) \u00a7 Bus Terminal \u2022 East Corridor 15% Systems Design Submittal, April 2009 o East Corridor, 15% Systems Design Submittal, Revisions for Relay House Updates o East Corridor - 15% Systems Design Submittal - Revisions - Update to Switch Configuration, December 18, 2009 \u2022 Gold Line 15% Systems Design Submittal \u2022 Denver Union Station - P3 - Systems 15% Design Submittal - Revisions - Switch Configuration and Track Changes, December 18, 2009 \u2022 Commuter Rail Maintenance Facility 15% Systems Design, May 2009 \u2022 Northwest Corridor - 15% Systems Design Submittal \u2013 Drawings", "samples": [{"hash": "gK5aBvI3MhX", "uri": "/contracts/gK5aBvI3MhX#pdf-format", "label": "Reference Data List", "score": 19.257357974, "published": true}], "hash": "6a7b7ac7341bb97f7586af2c7045db98", "id": 6}, {"snippet_links": [{"key": "grading-and-drainage", "type": "definition", "offset": [11, 31]}, {"key": "traffic-signal-plans", "type": "clause", "offset": [34, 54]}, {"key": "commuter-rail", "type": "definition", "offset": [106, 119]}, {"key": "design-revisions", "type": "clause", "offset": [124, 140]}, {"key": "system-revisions", "type": "clause", "offset": [215, 231]}, {"key": "electrical-drawings", "type": "clause", "offset": [382, 401]}, {"key": "drainage-plan", "type": "definition", "offset": [408, 421]}, {"key": "grade-separation", "type": "definition", "offset": [476, 492]}, {"key": "february-2010", "type": "clause", "offset": [494, 507]}, {"key": "drainage-structures", "type": "definition", "offset": [510, 529]}, {"key": "box-culverts", "type": "clause", "offset": [557, 569]}, {"key": "construction-drawings", "type": "clause", "offset": [756, 777]}, {"key": "utility-plan", "type": "definition", "offset": [816, 828]}, {"key": "november-2009", "type": "clause", "offset": [832, 845]}, {"key": "plan-iii", "type": "definition", "offset": [959, 967]}, {"key": "general-layout", "type": "clause", "offset": [1019, 1033]}, {"key": "rail-corridor", "type": "definition", "offset": [1114, 1127]}, {"key": "march-2010", "type": "clause", "offset": [1189, 1199]}], "size": 1, "snippet": "At Grades, Grading and Drainage - Traffic Signal Plans \u2022 South Westminster Station \u2022 Track and Drainage \u2022 Commuter Rail 30% Design Revisions, January 2010 o Track Alignment & Train Hall revisions o Overhead Contact System revisions o Systemwide Electrical revisions \u2022 Commuter Rail 15% Design Revisions, January 2010 o Overhead Contact System Drawings o Signal Systems o Systemwide Electrical Drawings \u2022 30% Drainage Plan and Profiles Revisions \u2022 64th Avenue BNSF RR Overpass Grade Separation, February 2010 o Drainage Structures under proposed 64th Avenue Box Culverts As-builts \u2022 15% Track Design, Track Chart Revised, February 2010 \u2022 15% Track Design Revised, January 2010 \u2022 50% Grade Crossings and Traffic, January 2010 \u2022 South Westminster Station 50% Construction Drawings, o South Westminster 50% Engineering, Utility Plan I, November 2009 o South Westminster 50% Engineering, Utility Plan II, November 2009 o South Westminster 50% Engineering, Utility Plan III, November 2009 \u2022 South Westminster Station o Walls General layout, February 2010 o Pedestrian Underpass General Layout, February 2010 \u2022 Northwest Rail Corridor Track Alignment at Station 250+00 to avoid Little Dry Creek, March 2010", "samples": [{"hash": "gK5aBvI3MhX", "uri": "/contracts/gK5aBvI3MhX#pdf-format", "label": "Reference Data List", "score": 19.257357974, "published": true}], "hash": "44573b198a61b5350d4c1546f3881633", "id": 7}, {"snippet_links": [{"key": "amendment-and", "type": "clause", "offset": [5, 18]}, {"key": "agreement-or", "type": "definition", "offset": [30, 42]}, {"key": "entered-into", "type": "clause", "offset": [54, 66]}, {"key": "in-connection-with", "type": "clause", "offset": [67, 85]}, {"key": "to-the-extent", "type": "clause", "offset": [140, 153]}, {"key": "signed-and-delivered-by", "type": "clause", "offset": [154, 177]}, {"key": "facsimile-machine", "type": "definition", "offset": [189, 206]}, {"key": "original-agreement", "type": "definition", "offset": [276, 294]}, {"key": "legal-effect", "type": "definition", "offset": [358, 370]}, {"key": "original-signed", "type": "definition", "offset": [389, 404]}, {"key": "in-person", "type": "clause", "offset": [431, 440]}, {"key": "the-request", "type": "clause", "offset": [445, 456]}, {"key": "party-hereto", "type": "definition", "offset": [464, 476]}, {"key": "other-party", "type": "definition", "offset": [522, 533]}, {"key": "other-parties", "type": "clause", "offset": [616, 629]}, {"key": "no-party", "type": "clause", "offset": [631, 639]}, {"key": "delivery-of", "type": "clause", "offset": [702, 713]}, {"key": "an-agreement", "type": "clause", "offset": [714, 726]}, {"key": "signature-by-facsimile", "type": "clause", "offset": [730, 752]}, {"key": "formation-of-a-contract", "type": "clause", "offset": [799, 822]}, {"key": "such-party", "type": "clause", "offset": [832, 842]}], "size": 1, "snippet": "This Amendment and any signed agreement or instrument entered into in connection with this Amendment, and any amendments hereto or thereto, to the extent signed and delivered by means of a facsimile machine or in .pdf format, shall be treated in all manner and respects as an original agreement or instrument and shall be considered to have the same binding legal effect as if it were the original signed version thereof delivered in person. At the request of any Party hereto or to any such agreement or instrument, each other Party hereto or thereto shall re-execute original forms thereof and deliver them to all other Parties. No Party hereto or to any such agreement or instrument shall raise the delivery of an agreement or signature by facsimile machine or in .pdf format as a defense to the formation of a contract and each such Party forever waives any such defense.", "samples": [{"hash": "9qxkeJhUmDS", "uri": "/contracts/9qxkeJhUmDS#pdf-format", "label": "Agreement and Plan of Reorganization", "score": 29.340862423, "published": true}], "hash": "1a57f515a1c5d72ee8209b7c9ef00512", "id": 8}, {"snippet_links": [{"key": "first-amendment", "type": "clause", "offset": [5, 20]}, {"key": "executed-by", "type": "clause", "offset": [28, 39]}, {"key": "facsimile-copies", "type": "clause", "offset": [40, 56]}], "size": 1, "snippet": "This First Amendment may be executed by facsimile copies or copies in PDF format, each of which facsimile copies or copies in PDF format will be deemed an original hereof.", "samples": [{"hash": "aKv3Y7w5wXc", "uri": "/contracts/aKv3Y7w5wXc#pdf-format", "label": "Sublease (Sunesis Pharmaceuticals Inc)", "score": 22.1950718686, "published": true}], "hash": "44da9e8ba8c525f5320e5936f9266aa0", "id": 9}, {"snippet_links": [{"key": "this-agreement", "type": "clause", "offset": [0, 14]}, {"key": "more-than-one-counterpart", "type": "clause", "offset": [34, 59]}, {"key": "when-taken", "type": "clause", "offset": [76, 86]}, {"key": "by-facsimile-transmission", "type": "clause", "offset": [170, 195]}, {"key": "by-email", "type": "clause", "offset": [199, 207]}, {"key": "each-case", "type": "definition", "offset": [228, 237]}, {"key": "force-and-effect", "type": "clause", "offset": [253, 269]}], "size": 1, "snippet": "This Agreement may be executed in more than one counterpart, each of which, when taken together, shall be deemed to be one (1) instrument. This Agreement may be executed by facsimile transmission or by email via .pdf format, in each case, with the same force and effect as originals.", "samples": [{"hash": "1wN3OvJxEL4", "uri": "/contracts/1wN3OvJxEL4#pdf-format", "label": "Sale Purchase Agreement (Bluerock Residential Growth REIT, Inc.)", "score": 27.8528405202, "published": true}], "hash": "398df0d5567c09607307e80d458e3c99", "id": 10}], "next_curs": "ClMSTWoVc35sYXdpbnNpZGVyY29udHJhY3Rzci8LEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhNwZGYtZm9ybWF0IzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"size": 20, "title": "PDF Format", "children": [], "parents": [["maps-drawings-and-sketches", "Maps, Drawings, and Sketches"], ["map-products-and-support-files", "Map Products and Support Files"]], "id": "pdf-format", "related": [["certificate-of-formation", "Certificate of Formation", "Certificate of Formation"], ["filing-of-form-8-k", "FILING OF FORM 8-K", "FILING OF FORM 8-K"], ["file-format-standard", "File Format Standard", "File Format Standard"], ["of-form-s-3", "of Form S-3", "of Form S-3"], ["purpose-of-form", "Purpose of Form", "Purpose of Form"]], "related_snippets": [], "updated": "2025-07-07T12:37:48+00:00", "also_ask": ["What minimum technical specifications should the PDF format clause require to ensure document integrity?", "How can parties negotiate protections against unauthorized alterations of PDF documents?", "What are the legal risks if a contract only specifies 'PDF format' without further detail?", "How do courts treat disputes over authenticity or admissibility of PDF documents versus originals?", "Are there industry standards or best practices for PDF usage in legal agreements that should be referenced?"], "drafting_tip": "Specify acceptable PDF versions and security settings to ensure compatibility; require text-searchable files to facilitate document review; prohibit password protection unless agreed to prevent access issues.", "explanation": "The PDF Format clause specifies that documents, communications, or deliverables must be provided in Portable Document Format (PDF). This means that any files exchanged between parties, such as reports, invoices, or official correspondence, should be submitted as PDFs to ensure consistent formatting and compatibility across different devices and software. By standardizing the file format, this clause helps prevent issues related to document readability, editing, or version discrepancies, thereby ensuring clarity and uniformity in document handling."}, "json": true, "cursor": ""}}