File Naming Clause Samples

File Naming. The XML file will follow the following naming convention: YYYYMMDD_SCHEMANAME_SCHEMAVERSION_ACERCODE_SEQID.EXTENSION where:  YYYYMMDD - submission date where: o YYYY: date year; o MM: date month; o DD: date day.  SCHEMANAME: The name of the ACER scheme for the file submitted, i.e. "REMITTable1"  SCHEMAVERSION: The version of the ACER xsd schema for the file submitted (e.g. "V1"or “V2”, etc.)  ACERCODE: LAGIE ACER code, i.e. ▇▇▇▇▇▇▇▇▇.▇▇  SEQID: a unique file sequence identifier (integer number) assigned by LAGIE for a specific file upload.  EXTENSION: the file extension. LAGIE will provide Market Participants the XML files signed and encrypted in order to preserve data quality and integrity.
View SourceView Similar (2)
File Naming. The contractor shall, for all deliverables, establish and enforce a file naming convention that requires a standard format for naming the basic submitted file, and all subsequent serial revisions/versions separately, by basic filename, serial revision/version number and date. The file naming convention shall be defined/established as agreed to by the IPPT at the PAC.
View SourceView Similar (2)
File Naming. Appliction / e-book fonts are supplied in the following kebab-cased format — ▇▇▇▇▇▇▇▇-▇▇▇▇▇▇▇▇▇▇.▇▇▇ The licensee agrees NOT to change this file naming structure. It is kebab-cased. Only Camel Casing can be added if required. E.G. apercu-regular-italic.otf or Apercu-Regular-Italic.otf
View Source
File Naming. 9.1 Files shall be named in accordance with the UK National Annex to ISO19650-2. Adoption of the National Annex methodology (i.e. the unique ID plus metadata) means that information descriptions, if needed, can be kept to a bare minimum. This aids efficiency and consistency for information identity (which is essential when a CDE contains a large volume of information containers) but importantly, supports a security-minded approach to information management. 9.2 The UK’s National Annex describes the naming standard for information containers within a common data environment (CDE) and is based on the same convention set out in superseded BS 1192:2007. 9.3 In the National Annex, the term ‘information container’ is used to describe the unique identification of a file. For a construction project, an information container could be a cost plan, a programme, a drawing, a geometric model etc. 9.4 The National Annex Clause NA3.6 lists common types of information containers and how these can be named. It is not a definitive list and there is an option to specify project-specific codes if required. 9.5 Each information container should be identified through a unique ID and National Annex Clause NA2.2 provides the structure for this ID. 9.6 The National Annex also requires the project’s CDE(s) to enable attributes (metadata) against each information container to record its status, revision and classification. Metadata requirements are covered in National Annex Clause 4. 9.7 The CDE should prompt the addition of metadata according to the National Annex plus the update of metadata when an information container is revised. The CDE may also enable configuration so that additional metadata can be added if required.
View Source
File Naming. Desktop fonts are supplied in the following kebab-cased format — DATE 06 May 2020 DOCUMENT Desktop License COMPANY AS & EH Partnership Ltd COMPANY NUMBER 8402407 VAT NUMBER ▇▇▇-▇▇▇▇-▇▇
View Source

Related to File Naming

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

  • Authorization to File Financing Statements Borrower hereby authorizes Bank to file financing statements, without notice to Borrower, with all appropriate jurisdictions to perfect or protect Bank’s interest or rights hereunder, including a notice that any disposition of the Collateral, by either Borrower or any other Person, shall be deemed to violate the rights of Bank under the Code. Such financing statements may indicate the Collateral as “all assets of the Debtor” or words of similar effect, or as being of an equal or lesser scope, or with greater detail, all in Bank’s discretion.

  • Voter Registration: When designated by the Secretary of State Party agrees to become a voter registration agency as defined by 17 V.S.A. §2103 (41), and to comply with the requirements of state and federal law pertaining to such agencies.

  • Preparation and Filing of Tax Returns (i) The Company, if possible, or otherwise the Stockholders shall file or cause to be filed all income Tax Returns (federal, state, local or otherwise) of any Acquired Party for all taxable periods that end on or before the Funding and Consummation Date, and shall permit TCI to review all such Tax Returns prior to such filings. Unless the Company is a C corporation, the Stockholders shall pay or cause to be paid all Tax liabilities (in excess of all amounts already paid with respect thereto or properly accrued or reserved with respect thereto on the Company Financial Statements) shown by such Returns to be due. (ii) TCI shall file or cause to be filed all separate Returns of, or that include, any Acquired Party for all taxable periods ending after the Funding and Consummation Date, and shall permit the Stockholders a reasonable opportunity to review all such Returns for periods including the Funding and Consummation Date prior to the filing thereof. (iii) Each party hereto shall, and shall cause its Subsidiaries and Affiliates to, provide to each of the other parties hereto such cooperation and information as any of them reasonably may request in filing any Return, amended Return or claim for refund, determining a liability for Taxes or a right to refund of Taxes or in conducting any audit or other proceeding in respect of Taxes. Such cooperation and information shall include providing copies of all relevant portions of relevant Returns, together with relevant accompanying schedules and relevant work papers, relevant documents relating to rulings or other determinations by Taxing authorities and relevant records concerning the ownership and Tax basis of property, which such party may possess. Each party shall make its employees and independent certified public accountants reasonably available on a mutually convenient basis at its cost to provide explanation of any documents or information so provided. Subject to the preceding sentence, each party required to file Returns pursuant to this Agreement shall bear all costs of filing such Returns. (iv) Each of the Company, Newco, TCI and each Stockholder shall comply with the Tax reporting requirements of Section 1.351-3 of the Treasury Regulations promulgated under the Code, and treat the transaction as a tax-free contribution under Section 351(a) of the Code subject to gain, if any, recognized on the receipt of cash or other property under Section 351(b) of the Code.