Policy Language Sample Clauses

Policy Language. All policies of insurance required to be maintained pursuant to this Section 9.2 shall be issued in English, with a clause in such policies stating that the English language version will prevail over any other version should any dispute arise regarding policy language.
AutoNDA by SimpleDocs
Policy Language. The Company grants MGA authority to utilize only insurance contract wordings, endorsement wordings and rates that are approved by the Company and are properly filed and approved, to the extent necessary, by the appropriate regulatory authorities of the State of Florida or of such other states in which the Company is licensed and authorized to transact insurance. 2.8.
Policy Language. Purpose and Scope This Delegation of Authority Policy (“Delegation of Authority”), which shall be effective as of the Effective Date, defines authorities delegated by the Members to the Delegate. Business matters involving the Company (which, for all purposes of this Delegation of Authority, shall include any Subsidiaries of the Company) outside of, or greater than, the scope of authorities expressly delegated to the Delegate by (i) the Second Amended and Restated Limited Liability Company Agreement of DCP Sand Hills Pipeline, LLC dated as of September 3, 2013 (the “Agreement”) or (ii) this Delegation of Authority require approval by the Management Committee or, in certain circumstances, the Members. This Delegation of Authority only pertains to the delegation of authority from the Members to the Delegate, and all delegations to other Persons acting on behalf of the Delegate are covered by other documentation maintained by or on behalf of the Delegate. Unless the context requires otherwise, capitalized terms used herein have the meanings stated in the Agreement.
Policy Language. Policies are specified in the GlueQoS policy language. The language provides a set of built in operators to specify ac- ceptable aspect configurations, as well as the ability to ex- tend the system with functions to measure operating con- ditions (such as load, available energy, and bandwidth). A configuration includes which aspects should be used as well as what their operating parameters should be. Each client to server session is associated with a set of adaptlets [19]. An adaptlet conceptually encapsulates a pair of client and server aspects. This includes the provided and required interfaces of client and server aspects. This scop- ing of aspects can be viewed in analogy to the “aspect per” scoping of AspectJ but based on a client/server negotiated session. The adaptlet abstraction serves to properly type the “connection” between cooperating aspect instances. Our work is focused on automating the process of configuring these instances using a client-server handshake. During the handshake the two parties agree on a set of adaptlets to use, as well as the values of any parameters they expose. In this section we detail the constructs in GlueQoS used to automate this handshake including support for boolean constraints, linear constraints, and run-time monitoring.
Policy Language. The language in the policy of Victims of Trafficking and Violence Protection Act of 2000 is obscure and unclear in places, leading to a variety of interpretations of the policy (Potocky, 2010). The Victims of Trafficking and Violence Protection Act of 2000 defines human trafficking as “a form of modern-day slavery”, yet no other forms of trafficking are identified (Potocky, 2010). While the term “trafficking” is not synonymous with “movement”, it is commonly used in this manner and often misunderstood to be a requirement in qualifying as “trafficking” (Potocky, 2010). Additionally, the term “abolition” has been commonly designated to refer to prostitution, rather than slavery, confusing the issue further and placing less emphasis on the crime of slavery and more on the criminalization of prostitution (Potocky, 2010). Without clear legislation using commonly defined terminology, confusion and misinterpretations around the issue of sex trafficking will continue to exist, resulting in the failure of the protection of the victims and the legal methods of justice for the perpetrators of sex trafficking (Potocky, 2010). This will only further impede progressive and effective policy needed through the collaboration of the public sector, the private sector, and the government agencies (Potocky, 2010). The multitude of variations in definitions of trafficking, including the differences found among the state, federal, and international arena only further confuses an already complex issue (Potocky, 2010). Advocating for the use of plain language of the issue, such as using the term “slavery” in place of “human trafficking”, will allow for less confusion and unproductive discourse on the issue and more action on solving the problem (Potocky, 2010). This type of confusion and uncertainty results in a misinformed or misunderstood legal system; thereby resulting in the inability to effectively prosecute the perpetrator and provide proper rehabilitation services for the victims (Potocky, 2010).

Related to Policy Language

  • Official Language The official text of this Agreement and any appendices, exhibits and schedules hereto, or any notice given or accounts or statements required by this Agreement shall be in English. In the event of any dispute concerning the construction or meaning of this Agreement, reference shall be made only to this Agreement as written in English and not to any other translation into any other language.

  • Use of English Language This Agreement has been executed and delivered in the English language. Any translation of this Agreement into another language shall have no interpretive effect. All documents or notices to be delivered pursuant to or in connection with this Agreement shall be in the English language or, if any such document or notice is not in the English language, accompanied by an English translation thereof, and the English language version of any such document or notice shall control for purposes thereof.

  • English Language (a) Any notice given under or in connection with any Finance Document must be in English.

  • Governing Language This Agreement has been negotiated and executed by the parties in English. In the event any translation of this Agreement is prepared for convenience or any other purpose, the provisions of the English version shall prevail.

  • Controlling Language This Agreement is in English only, which language shall be controlling in all respects. All documents exchanged under this Agreement shall be in English.

  • Construction of Language Whenever appropriate in the Agreement, words used in the singular may be read in the plural, words used in the plural may be read in the singular, and words importing the masculine gender may be read as referring equally to the feminine or the neuter. Any reference to a section shall be a reference to a section of this Agreement, unless the context clearly indicates otherwise. Capitalized terms not specifically defined herein shall have the meanings assigned to them under the Plan.

  • Languages 20.1 The Proclamation of Sale, these conditions of sale and the Memorandum may have been translated and published in different forms and languages. In the event of any discrepancy, misstatement, omission or error appearing in the various forms or languages, this English version shall prevail.

  • Language If the Participant has received this Agreement or any other document related to the Plan translated into a language other than English and if the meaning of the translated version is different than the English version, the English version will control.

  • Choice of Language It is the express wish of the parties that this Agreement and any related documents be drawn up and if execution is required, to be executed in English. Les parties conviennent que la présente convention et tous les documents s’y rattachant soient rédigés et signés en anglais.

Time is Money Join Law Insider Premium to draft better contracts faster.