File Naming Conventions. Files will be named according to the following convention: {gTLD}_{YYYY-‐MM-‐DD}_{type}_S{#}_R{rev}.{ext} where:
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”.
File Naming Conventions. Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where: 5.1. 5.3. {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:
File Naming Conventions. Files shall be named according to the following convention: <gTLD>_<YYYY-MM-DD>_<FILE>_<type>_<comp>_<encrypt>_S<#>_R<rev>.<ext> where:
File Naming Conventions. Each Produced PDF Paginated Document file will be named with the beginning Xxxxx Number. Each Produced TIFF image and corresponding text file shall be named with the unique Xxxxx Number of the page of document. In the event the Xxxxx Number contains a symbol and/or character that cannot be included in a file name, the symbol and/or character will be omitted from the file name.
File Naming Conventions. Each document shall be uniquely identifiable together with its version. See the table below for the way to name files. Other document types should also follow this logic. File naming conventions: Document Type ID Convention File Name example Deliverables D D[WP#].[D#]_[Short Title]_[version#]. [extension] D1.1_ProjectHandbookv1.0.doc Meeting Minutes MM MM_[type of meeting, e.g. EB or WPL#]_[YYYYMMDD ].[extension] MM_WPL_20191001.doc Presentation P P[WP#]_[Conference Title]_[version#].[ext ension] P3-XYconference- v1.ppt Periodic Report PR PR[period#]- [version#]. [extension] PR1-v0.0.doc
File Naming Conventions. Files uploaded to the FTPS server should conform to the following naming convention: *** *** Portions of this agreement marked by *** have been omitted pursuant to a request for confidential treatment. Omitted material for which confidential treatment has been requested has been filed separately with the Securities and Exchange Commission. *** PROPRIETARY AND CONFIDENTIAL
File Naming Conventions. The tarball file will be named according to the following convention: {Provider ICANN ID}{_Registrar ID}_{YYYY‐MM‐ DD}_{type}_S{#}_R{rev}.{ext} where:
File Naming Conventions. Throughout this contract the Bailiff is referred to as the Service Provider. The file naming conventions for the Specification are as follows:- Bailiff = Service Provider Council = CSP
File Naming Conventions. Valid extensions for files using their associated applications are listed below in Table G-1 (File Extensions): Table G-1 File Extensions Type of Application/Files Valid Extensions Portable Document Files .pdf Microsoft Word documents .docx Microsoft Excel documents .xlsx Microsoft Power Point .pptx Microsoft Project .mpp The Offeror shall follow the basic structure of the file naming convention in Table G-2 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where "#" represents the sequential numbering of files. Offeror’s shall keep the file name as short as possible (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names may become corrupt or inaccessible. The Offeror should provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. Please submit each volume, or annex as one file if possible. Offerors should not provide each section/paragraph as separate files. The Offeror shall ensure that the electronically submitted files are directly traceable to paper copy submittals. Table G-2 - CMMARS Offeror Electronic File Naming Convention Volume Title File naming convention Number 1 Technical Vol 1 Tech#.docx Table T-1 Offeror Summary Vol 1 T Tables.xlsx and Vol 1 T Tables.pdf Table T-2 Contract Summary Table T-3 Contracts for Aircraft Maintenance Experience Vol 1 T-3 CAME.xlsx and Vol 1 T-3 CAME.pdf Table T-3a DO/TO Sub-references 2 Contract Administration Vol 2 CA#.docx and Vol 2 CA#.pdf Annexes Annex A Supporting Documentation for Aircraft Maintenance Experience XxxX SDfAME#.pdf and XxxX SDfAME#.docx Please note: The Offeror should provide both a .pdf and .docx version if they are available. Annex B Small Business (i.e. Small Business Subcontracting Plan and Small Business Utilization Plan) AnnB SB SP.docx and AnnB SB SP. pdf AnnB SB UP.docx and AnnB SB UP.pdf
