MNM characterisation Sample Clauses

MNM characterisation. The key question in the first step of the flow chart is: Is it a MNM? (This is the first question in the flow chart, however, this is not a risk potential) If this question is answered with no: no nanospecific potential for health risk is expected and risk assessment can be performed in the conventional way. If this question is answered with yes: nanospecific data/testing is required (see testing strategy)

Related to MNM 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).

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

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

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.