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