Semantic Web form for the relation of synonymy Sample Clauses

Semantic Web form for the relation of synonymy. On the Semantic Web, a small number of available data vocabularies is capable of expressing synonymy as found in thesauri. Searches in LOV for ‘synonym’ and ‘synonymy’ located a number of candidate data vocabularies for this purpose. The majority of them contains terminology to capture synonymy between elements other than lexical senses.58 However, as discussed in Chapter 1, the relation of synonymy as found in thesauri is one between senses.59 Only three vocabularies define their synonymy relations as lexical relations or sense relations: LEMON, GOLD,60 and LexInfo. The last two vocabularies are positioned as supplementing classifications to LEMON, useful for describing linguistic objects more thoroughly.61 In order to satisfy the criterion of cohesion, a closer look at LEMON is therefore warranted, since this data vocabulary has already been selected for representing historical language thesauri (i.e., for expressing lexical senses, see section 3.5.1). If LEMON suffices in expressing synonymy for thesauri, its use is therefore preferred over that of GOLD and LexInfo. In LEMON, the relation of synonymy is asserted not directly between senses but indirectly by grouping them under a lexical concept. Lexical senses that are associated with the same lexical concept through the isLexicalizedSenseOf relation are considered to be synonymous. The LEMON specification indicates how its terminology for synonymy corresponds to those used in lexical nets, such as University of Princeton’s WordNet, which captures sets of synonyms (referred 55McCrae et al., ‘Integrating WordNet and Wiktionary with lemon’. 56Nielsen, ‘Lexemes in Wikidata’. 57Eckle-Xxxxxx et al., ‘lemonUby’. 58LOV, s.v. ‘ru’, ‘xxxx’, ‘dbpedia-owl’, ‘uniprot’. 59Indeed, near-synonymy, which is a form of synonymy between lexical senses, has been called “the staple of thesauruses” (Xxxxxx, ‘Meaning Relations in Dictionaries’, p. 448). 60In full, GOLD stands for General Ontology for Linguistic Description. 61‘Lexicon Model for Ontologies’. to as synsets).62 The specification thereby demonstrates that synonymy can be captured using solely this data vocabulary, which is shown suitable for capturing this important relation in historical language thesauri on the Semantic Web. With the relation of synonymy covered, this chapter will proceed to discuss which data vocabularies best capture sense attributes.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Semantic Web form for the relation of synonymy

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Your Liability for Unauthorized Transfers Immediately following your discovery of an unauthorized Payment Instruction, you shall communicate with customer care for the Service in the manner set forth in Section 6 of the General Terms above. You acknowledge and agree that time is of the essence in such situations. If you tell us within two (2) Business Days after you discover your password or other means to access your account through which you access the Service has been lost or stolen, your liability is no more than $50.00 should someone access your account without your permission. If you do not tell us within two (2) Business Days after you learn of such loss or theft, and we can prove that we could have prevented the unauthorized use of your password or other means to access your account if you had told us, you could be liable for as much as $500.00. If your monthly financial institution statement contains payments that you did not authorize, you must tell us at once. If you do not tell us within sixty (60) days after the statement was sent to you, you may lose any amount transferred without your authorization after the sixty (60) days if we can prove that we could have stopped someone from taking the money had you told us in time. If a good reason (such as a long trip or a hospital stay) prevented you from telling us, we will extend the time periods specified above to a reasonable period.

  • Transition of Registry upon Termination of Agreement Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, Registry Operator shall provide ICANN or any successor registry operator that may be designated by ICANN for the TLD in accordance with this Section 4.5 with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process; provided, however, that (i) ICANN will take into consideration any intellectual property rights of Registry Operator (as communicated to ICANN by Registry Operator) in determining whether to transition operation of the TLD to a successor registry operator and (ii) if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (A) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator or its Affiliates for their exclusive use, (B) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (C) transitioning operation of the TLD is not necessary to protect the public interest, then ICANN may not transition operation of the TLD to a successor registry operator upon the expiration or termination of this Agreement without the consent of Registry Operator (which shall not be unreasonably withheld, conditioned or delayed). For the avoidance of doubt, the foregoing sentence shall not prohibit ICANN from delegating the TLD pursuant to a future application process for the delegation of top-­‐level domains, subject to any processes and objection procedures instituted by ICANN in connection with such application process intended to protect the rights of third parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument for the maintenance and operation of the TLD, regardless of the reason for termination or expiration of this Agreement.

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