Filtered LMF example Sample Clauses

Filtered LMF example. <Lexicon> <LexicalEntry id=“le_1”> <feat att=“partOfSpeech” val=“noun”/> <!--Lemma is obligatory in LMF and should be used to encode the morphosyntactic information applicable to the whole lemma --> <Lemma> <feat att=“writtenForm” val=“boy”/> </Lemma> <!--use feat “partOfSpeech” to set the PoS of the entry --> <feat att=“partOfSpeech” val=“noun”/> <Sense> <!-- add one feat for each class and its assigned score --> <!-- “boy” belongs to the class human but not to location or eventive --> <feat att=“event” val=“no”/> <feat att=“hum” val=“yes”/> <feat att=“loc” val=“no”/> <!-- “domain” is a label used to identify the corpus from where the lexicon has been extracted, in case it has been automatically acquiered --> <feat att=“domain” val=“labour”/> </Sense> </LexicalEntry> <LexicalEntry id=“le_2”> <feat att=“partOfSpeech” val=“noun”/> <Lemma> <feat att=“writtenForm” val=“car”/> </Lemma> <Sense> <feat att=“domain” val=“labour”/> <!-- “car” does not belong to the class human nor eventive, but the classifier is not sure about class location --> <feat att=“event” val=“no”/> <feat att=“hum” val=“no”/> <feat att=“loc” val=“unknown”/> </Sense> </LexicalEntry> <LexicalEntry id=“le_3”> <feat att=“partOfSpeech” val=“noun”/> <Lemma> <feat att=“writtenForm” val=“storm”/> </Lemma> <Sense> <feat att=“domain” val=“labour”/> <!-- “storm” belongs to the class eventive but not to location or human --> <feat att=“event” val=“yes”/> <feat att=“hum” val=“no”/> <feat att=“loc” val=“no”/> </Sense> </LexicalEntry> </Lexicon>
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Filtered LMF example

  • Local Switching Interfaces 4.2.13.1 Newcomm shall order ports and associated interfaces compatible with the services it wishes to provide as listed in Exhibit A. BellSouth shall provide the following local switching interfaces:

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Required Coverages For Generation Resources Of 20 Megawatts Or Less Each Constructing Entity shall maintain the types of insurance as described in section 11.1 paragraphs (a) through (e) above in an amount sufficient to insure against all reasonably foreseeable direct liabilities given the size and nature of the generating equipment being interconnected, the interconnection itself, and the characteristics of the system to which the interconnection is made. Additional insurance may be required by the Interconnection Customer, as a function of owning and operating a Generating Facility. All insurance shall be procured from insurance companies rated “A-,” VII or better by AM Best and authorized to do business in a state or states in which the Interconnection Facilities are located. Failure to maintain required insurance shall be a Breach of the Interconnection Construction Service Agreement.

  • Packet Switching Capability 4.5.1 The packet switching capability network element is defined as the function of routing or forwarding packets, frames, cells or other data units based on address or other routing information contained in the packets, frames, cells or other data units.

  • Shift Rotation Routine shift rotation is not an approach to staffing endorsed by the Employer. Except for emergency situations where it may be necessary to provide safe patient care, shift rotation will not be utilized without mutual consent. If such an occasion should ever occur, volunteers will be sought first. If no one volunteers, the Employer will rotate shifts on an inverse seniority basis until the staff vacancies are filled.

  • Manual Disconnect Switch 5.1 U.L.1741 Listed, inverter-based Tier 1 customer-owned renewable generation systems do not require a customer-installed manual disconnect switch.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.

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