Directive feature_mapper Sample Clauses

Directive feature_mapper. This directive defines which features of the syntactic arguments must be checked. It plays two distinct roles: the first is to list such features; the second is to map the same features between the two lexicons. The format is value_lexicon_A (tab) value_lexicon_B and it is coherent with the two input lexicons, A and B: # format lexA (tab) lexB Lexicon A Lexicon B Function function syntacticConsti tuent realization Introducer introducer Table 1: mapping among features This directives maps the features of the SAs in lexicon A on those of lexicon B. The software uses this directive to: • count the features in SAs structure • substitute the values in B with A's The directive is used to establish equivalence among syntactic arguments such the following: Lexicon A Lexicon B Equivalent <Syn > <feat att="function" val="subj"/> <feat att="syntacticCostituent" val="np"/> <feat att="introducer" val="to"/> </Syn. > <Syn > <feat att="function" val="subj"/> <feat att="realization " val="np"/> <feat att="introducer" val="to"/> </Syn. > YES. Both arguments have three features with the same attributes and values. Please note the bold which reflects the mapping. <Syn > <feat att="function" val="subj"/> <feat att="syntacticCostituent" val="np"/> <feat att="introducer" val="to"/> </Syn. > <Syn > <feat att="function" val="subj"/> <feat att="realization " val="np"/> </Syn. > NO. Different number of SAs <Syn > <feat att="function" val="subj"/> <feat att="syntacticCostituent" val="np"/> <feat att="introducer" val="to"/> </Syn. > <Syn > <feat att="function" val="subj"/> <feat att="realization " val="pp"/> <feat att="introducer" val="to"/> </Syn. > NO. Both arguments have three features with the same attributes but different values. Please note the bold which reflects the mapping but also the bold italic which shows different values. Table 2: Equivalence between two syntactic arguments according to features_mapper directive
Sample 1
AutoNDA by SimpleDocs

Related to Directive feature_mapper

  • Construction Change Directives 7.3.1 A Construction Change Directive is written order prepared by the Architect and signed by the Owner and Architect, directing a change in the Work and stating a proposed basis for adjustment, if any, in the Contract Sum, or Contract Time, or both. The Owner may by Construction Change Directive, without invalidating the Contract, order changes in the Work within the general scope of the Contract consisting of additions, deletions or other revisions, the Contract Sum and Contract Time being adjusting accordingly.

  • Construction Change Directive A written order prepared and issued by the District, the Construction Manager, and/or the Architect and signed by the District and the Architect, directing a change in the Work.

  • CHANGE DIRECTIVE A Change Directive means a written instruction, which shall be deemed incorporated into and forming part of the Agreement, prepared by the Contract Administrator and signed by the Owner directing the Contractor to proceed with a change in the Work prior to or in the absence of the Owner and the Contractor agreeing upon adjustments in the Contract Price and the Contract Time.

  • CONTRACT DIRECTION (a) Only the LOCKHEED XXXXXX Procurement Representative has authority on behalf of LOCKHEED XXXXXX to make changes to this Contract. All amendments must be identified as such in writing and executed by the parties.

  • Change Management Process If Customer or Oracle requests a change in any of the specifications, requirements, Deliverables, or scope (including drawings and designs) of the Professional Services described in any Statement of Work, the party seeking the change shall propose the applicable changes by written notice. Within forty-eight (48) hours of receipt of the written notice, each party’s project leads shall meet, either in person or via telephone conference, to discuss and agree upon the proposed changes. Oracle will prepare a change order describing the proposed changes to the Statement of Work and the applicable change in fees and expenses, if any (each, a “Change Order”). Change Orders are not binding unless and until they are executed by both parties. Executed Change Orders shall be deemed part of, and subject to, this Addendum. If the parties disagree about the proposed changes, the parties shall promptly escalate the change request to their respective senior management for resolution.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • Change Orders Any alteration or deviation from the Services mentioned or any other contractual specifications that result in a revision of this Agreement shall be executed and attached to this Agreement as a change order (“Change Order”).

  • Change Order Conditions All Change Orders are issued under the following conditions and shall contain the following language as appropriate:

  • Client Classification 7.1. We shall not have an obligation to treat our clients in different classes depending on their knowledge and expertise.

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

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