Attachment File Format Sample Clauses

Attachment File Format. The following file formats can be exchanged via E-Mail interface: Format Name PEPPOL Document Type Identifier PEPPOL BIS Billing V3 urn:oasis:names:specification:ubl:schema:xsd:Invoice- 2::Invoice##urn:xxx.xx:en16931:2017#compliant#urn:fdc:xxxxxx.xx:2017:poacc:bill ing:3.0::2.1 PEPPOL BIS Billing V3 urn:oasis:names:specification:ubl:schema:xsd:CreditNote- 2::CreditNote##urn:xxx.xx:en16931:2017#compliant#urn:fdc:xxxxxx.xx:2017:poacc :billing:3.0::2.1 PEPPOL BIS Billing V3 urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100::CrossIndustryInvoic e##urn:xxx.xx:en16931:2017#compliant#urn:fdc:xxxxxx.xx:2017:poacc:billing:3.0:: D16B
AutoNDA by SimpleDocs

Related to Attachment File Format

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows:

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • System Description The DLCS is a network consisting of devices which are remotely controlled over RF transmission equipment by the PowerCAMPTM Software or equivalent. CL&P shall have access to the PowerCAMP™ LMS (as defined below) via the web interface. The PowerCAMPTM LMS shall include the software and hardware necessary to manage the Control Devices installed at the End-use Equipment at Participating Facilities. The PowerCAMPTM LMS includes AER’s PowerCAMPTM Server and PowerCAMPTM Suite, networking equipment, and third party software. PowerCAMPTM LMS Hardware

  • ATTACHMENT C STANDARD STATE PROVISIONS FOR CONTRACTS AND GRANTS

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • CONTRACTOR TO PACKAGE DELIVERABLES The Contractor will package deliverables in accordance with good commercial practice and shall include a packing list showing the description of each item, the quantity and unit price unless otherwise provided in the Specifications or Supplemental Terms and Conditions, each shipping container shall be clearly and permanently marked as follows: (a) The Contractor's name and address, (b) the City’s name, address and purchase order or purchase release number and the price agreement number if applicable, (c) Container number and total number of containers, e.g. box 1 of 4 boxes, and (d) the number of the container bearing the packing list. The Contractor shall bear cost of packaging. Deliverables shall be suitably packed to secure lowest transportation costs and to conform to all the requirements of common carriers and any applicable specification. The City's count or weight shall be final and conclusive on shipments not accompanied by packing lists.

  • Program Description The employer agrees to provide a vision benefit to eligible employees and dependents. The vision benefit provided by the State shall have an employee co-payment of $10 for the comprehensive annual eye examination and $25 for materials.

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