Object characterisation Sample Clauses

Object characterisation. The JHOVE 37 technical characterisation result (XML format) is embedded as a descendant of the ob- jectCharacteristicsExtension element. An example is shown in Listing 13. <objectCharacteristicsExtension> <mdSec ID="ID426087e8-0f79-11e3-847a-34e6d700c47b"> <mdWrap MDTYPE="OTHER" OTHERMDTYPE="JHOVE"> <xmlData> <jhove>
AutoNDA by SimpleDocs

Related to Object characterisation

  • Client Categorisation 4.1. The client understands and accepts that each category of Clients has its individual level of regulative protection acknowledging that Retail Clients have the highest level of protection whereas Professional Clients and Eligible Counterparties are considered to be more experienced, informed, skilled and able to estimate their risk, therefore are provided with a lower level of protection. 4.2. The Company will treat the Client as a Retail Client, Professional Client or Eligible Counterparty, depending on how the Client completes the Application Form and according to the method of categorisation as this method is explained under the title “Client Categorisation” (Appendix II), and by accepting this Agreement the Client accepts application of such method. 4.3. The Client accepts that when categorising the Client and dealing with him, the Company will rely on the accuracy, completeness and correctness of the information provided by the Client in his Application Form and the Client has the responsibility to immediately notify the Company in writing if such information changes. 4.4. The Company has the right to review the Client’s Categorisation and change his Categorisation if this is deemed necessary (subject to Applicable Laws).

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Meter Testing Company shall provide at least twenty-four (24) hours' notice to Seller prior to any test it may perform on the revenue meters or metering equipment. Seller shall have the right to have a representative present during each such test. Seller may request, and Company shall perform, if requested, tests in addition to the every fifth-year test and Seller shall pay the cost of such tests. Company may, in its sole discretion, perform tests in addition to the fifth year test and Company shall pay the cost of such tests. If any of the revenue meters or metering equipment is found to be inaccurate at any time, as determined by testing in accordance with this Section 10.2 (Meter Testing), Company shall promptly cause such equipment to be made accurate, and the period of inaccuracy, as well as an estimate for correct meter readings, shall be determined in accordance with Section 10.3 (Corrections).

  • Drug Testing (A) The state and the PBA agree to drug testing of employees in accordance with section 112.0455, F.S., the Drug-Free Workplace Act. (B) All classes covered by this Agreement are designated special risk classes for drug testing purposes. Special risk means employees who are required as a condition of employment to be certified under Chapter 633 or Chapter 943, F.S. (C) An employee shall have the right to grieve any disciplinary action taken under section 112.0455, the Drug-Free Workplace Act, subject to the limitations on the grievability of disciplinary actions in Article 10. If an employee is not disciplined but is denied a demotion, reassignment, or promotion as a result of a positive confirmed drug test, the employee shall have the right to grieve such action in accordance with Article 6.

  • Two-­‐character labels All two-­‐character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Such labels may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator, provided that such two-­‐character label strings may be released to the extent that Registry Operator reaches agreement with the related government and country-­‐code manager of the string as specified in the ISO 3166-­‐1 alpha-­‐2 standard. The Registry Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such labels that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.

  • ODUF Testing 6.6.1 Upon request from TWTC, AT&T shall send ODUF test files to TWTC. The Parties agree to review and discuss the ODUF file content and/or format. For testing of usage results, AT&T shall request that TWTC set up a production (live) file. The live test may consist of TWTC’s employees making test calls for the types of services TWTC requests on ODUF. These test calls are logged by TWTC, and the logs are provided to AT&T. These logs will be used to verify the files. Testing will be completed within thirty (30) days from the date on which the initial test file was sent.

  • Agreement Exceptions/Deviations Explanation If the proposing Vendor desires to deviate form the Vendor Agreement language, all such deviations must be listed on this attribute, with complete and detailed conditions and information included. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any proposal based upon any deviations indicated below. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Vendor Agreement.

  • Inspection/Testing In order to assess Supplier’s work quality and/or compliance with this Order, upon reasonable notice by Buyer: (a) all goods, materials and services related to the items purchased hereunder, including, raw materials, components, assemblies, work in process, tools and end products shall be subject to inspection and testing by Buyer, its customer, representative or regulatory authorities at all places, including sites where the goods are made or located or the services are performed, whether at Supplier’s premises or elsewhere; and (b) all of Supplier’s facilities, books and records relating to this Order shall be subject to inspection by Buyer or its designee. If specific Buyer and/or Buyer’s customer tests, inspection and/or witness points are included in this Order, the goods shall not be shipped without an inspector’s release or a written waiver of test/inspection/witness with respect to each such point; however, Buyer shall not be permitted to unreasonably delay shipment; and Supplier shall notify Buyer in writing at least twenty (20) days prior to each of Supplier’s scheduled final and, if applicable, intermediate test/inspection/witness points. Supplier agrees to cooperate with such/audit inspection including, completing and returning questionnaires and making available its knowledgeable representatives. Buyer’s failure to inspect or test goods, materials or services or Buyer’s failure to reject or detect defects by inspection or testing shall not relieve Supplier from its warranty obligations or any of its other obligations or responsibilities under this Order. Supplier agrees to provide small business as well as minority and/or women owned business utilization and demographic data upon request.

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