Agreement Hierarchy Sample Clauses

Agreement Hierarchy. The Agreement Hierarchy is a hierarchy of agreement positions postulated on the basis of data collected from a variety of languages that allow alternative agreements (ibid.). AH facilitates predictions about the likelihood of occurrence of syntactic or semantic agreements in a given target position: attributive > predicate > relative pronoun > personal pronoun The four positions indicate the domain where the agreement occurs: within the noun phrase, within the clause, within the sentence, and beyond the sentence. The AH imposes the following constraint on possible agreement patterns: For any controller that permits alternative agreements, as we move rightwards along the Agreement Hierarchy, the likelihood of agreement with greater semantic justification will increase monotonically (that is, with no intervening decrease). (Xxxxxxx 2006:207) 2.2.1. The hybrid controller величество ‘majesty’ permits alternative agreements: we find syntactic agreement in the attributive position [2b] and semantic agreement in the predicative position [3b]. Let us further observe the AH effect by looking at examples of agreement in the target positions further to the right of the hierarchy: [14] Relative pronoun 3SG.POSS.F majesty(N) xxx-X.XX never NEG обнаруживала удаления от справедливого и xxxxxxxx-XXX-X.XX withdrawal from fair CONJ разумного мира с королём прусским не зна-ет reasonable peace CONJ king prussian NEG know-3SG до until сего this дня day самого the.most главного important … ‘Her majesty, who has never considered withdrawing from peace with the Prussian king, to this day does not know the most crucial thing…’ (Soloviev Istorija Rossii s Drevnejschich Vremen 2017) Here we can see semantic feminine agreement expressed on the relative pronoun которая via the inflectional suffix -ая. As the hybrid controller величество ‘majesty’ has already been shown to permit semantic agreement in the predicative position [3b], the occurrence of semantic agreement in the relative pronoun position is no surprise and is in accord with the AH. [15] Personal pronoun9 Ее 3SG.POSS.F Величество majesty(N) плохо перенос-ит poorly tolerate-3SG путешествияпо travelling by воде water | И она очень сетова-л-а по поводу того, что в CONJ 3SG.F very xxxxxxxx-XXX-X.XX for reason such that in England autumnalways bad weather (Xxxxxx Lady on the Coin 1995 (Russian Translation by Xxxxxxx)) While it is impossible to say whether the predicate verb переносит ‘tolerates’ agrees with the controller syntac...
Sample 1
AutoNDA by SimpleDocs
Agreement Hierarchy. The claim that these subject markers indicate agreement between the subject noun and the verb is also supported by typological evidence. Following Xxxxxx (1997), agreement marking in languages oper- ates according to an implicational hierarchy of grammatical relations, given in (35). (35) Agreement Hierarchy (Xxxxxx 1997:154)13 subject > direct object > indirect object > other According to this hierarchy, if there is agreement with one of the nominals in the hierarchy, there will also be agreement with those nominals to the left of it. For example, the hierarchy predicts that if verb agreement is used to indicate the grammatical relation of just one nominal, it will be with the subject. If it marks agreement with only two nominals, it will be with both the subject and the direct object, and so on. Furthermore, the frequency with which one finds agreement decreases as one moves rightward along the hierarchy. In other words, subject agreement is very common, direct ob- ject agreement less so, indirect object agreement fairly uncommon, and agreement with other nomi- nals extremely rare. The Lamnso data appear to be in accord with the predictions of this hierarchy. Consider the sentence in (36). The subject noun vitam ‘elephants’ agrees with the verb by means of the enclitic -vi. The di- rect object noun, on the other hand, has no enclitic and, hence, is not marked for agreement with the verb. This pattern is fully consistent with the pattern predicted by the hierarchy: (36) vi-tam-vi kfar vi-kwi 8-elephant-XX xxxx 8-grass ‘The elephants are eating the grass.’ Only one nominal is marked for agreement with the verb – the subject noun. While we argue that ob- ject nouns are not marked for agreement, it is not the case that all object nouns are unmarked. We take up the issue of marking on object nouns in the following sections. Xxxxx and Xxxxxxxxx (cited in Croft 1990: 130) have noted that agreement may be with a pri- xxxx object rather than with a direct object. Hence, agreement would occur with the goal of ditransi- tive verbs rather than with the theme. This would also mean that the patient of transitive verbs should license agreement. However, as the example in (36) illustrates, this is not the case in Lamnso (even in cases where the object is human or animate, properties conducive to agreement marking).
Sample 1

Related to Agreement Hierarchy

  • PERFORMANCE MANAGEMENT SYSTEM 6.1 The Performance Plan (Annexure A) to this Agreement sets out – 6.1.1 The standards and procedures for evaluating the Employee’s performance; and 6.1.2 The intervals for the evaluation of the Employee’s performance. 6.2 Despite the establishment of agreed intervals for evaluation, the Employer may in addition review the Employee’s performance at any stage while the contract of employment remains in force; 6.3 Personal growth and development needs identified during any performance review discussion must be documented in a Personal Development Plan as well as the actions agreed to and implementation must take place within set time frames; 6.4 The Employee’s performance will be measured in terms of contributions to the goals and strategies set out in the Employer’s Integrated Development Plan (IDP) as described in 6.6 – 6.12 below; 6.5 The Employee will submit quarterly performance reports (SDBIP) and a comprehensive annual performance report at least one week prior to the performance assessment meetings to the Evaluation Panel Chairperson for distribution to the panel members for preparation purposes; 6.6 Assessment of the achievement of results as outlined in the performance plan: 6.6.1 Each KPI or group of KPIs shall be assessed according to the extent to which the specified standards or performance targets have been met and with due regard to ad-hoc tasks that had to be performed under the KPI, and the score of the employer will be given to and explained to the Employee during the assessment interview. 6.6.2 A rating on the five-point scale shall be provided for each KPI or group of KPIs which will then be multiplied by the weighting to calculate the final score; 6.6.3 The Employee will submit his self-evaluation to the Employer prior to the formal assessment; 6.6.4 In the instance where the employee could not perform due to reasons outside the control of the employer and employee, the KPI will not be considered during the evaluation. The employee should provide sufficient evidence in such instances; and 6.6.5 An overall score will be calculated based on the total of the individual scores calculated above.

  • AGREEMENT MANAGEMENT Pinellas Community Foundation designates the following person(s) as the liaison for the Xxxxxx Xxxxxx, CEO Pinellas Community Foundation

  • FRAMEWORK AGREEMENT MANAGEMENT The Parties shall manage this Framework Agreement in accordance with Schedule 14 (Framework Management).

  • Local Health Integration Networks and Restructuring In the event of a health service integration with another service provider the Employer and the Union agree to meet. (a) The Employer shall notify affected employees and the Union as soon as a formal decision to integrate is taken. (b) The Employer and the Union shall begin discussions concerning the specifics of the integration forthwith after a decision to integrate is taken. (c) As soon as possible in the course of developing a plan for the implementation of the integration the Employer shall notify affected employees and the Union of the projected staffing needs, and their location.

  • Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.

  • Service Agreement Refers to the Contract, Purchase Order or Terms of Service or Terms of Use. Student Data: Student Data includes any data, whether gathered by Provider or provided by LEA or its users, students, or students’ parents/guardians, that is descriptive of the student including, but not limited to,

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA): (a) we are liable for any remedy or rebate specified by the SLA; and (b) subject to clauses 40 to 42, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.

  • Data Processing Agreement The Data Processing Agreement, including the Approved Data Transfer Mechanisms (as defined in the Data Processing Agreement) that apply to your use of the Services and transfer of Personal Data, is incorporated into this Agreement by this reference. Each party will comply with the terms of the Data Processing Agreement and will train its employees on DP Law.

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