- From: Francesco Mambrini <f.mambrini@gmail.com>
- Date: Tue, 11 Apr 2023 19:42:36 +0200
- To: public-ontolex@w3.org
- Cc: Flavia Sciolette <flavia.sciolette@ilc.cnr.it>
- Message-Id: <20185938-402D-4CFD-848C-978439CD0866@gmail.com>
Dear Flavia, Another option might be to explicitly model the derivation process between lexical entries, using morphemes and derivation rules. You may be interested to see how we did this in LiLa, using the new Morph Ontolex module: https://aclanthology.org/2022.ldl-1.10.pdf https://publires.unicatt.it/it/publications/the-two-approaches-to-word-formation-in-the-lila-knowledge-base-o Best, Francesco > Il giorno 11 apr 2023, alle ore 19:05, Alik Kirillovich <alik.kirillovich@gmail.com> ha scritto: > > Dear Flavia, > > You can also create your resource-specific features, but define them as instances of the popular OLiA [1] or GOLD [2] ontologies. (OLiA is more suitable to model corpus annotation schemas, but can be used in lexical resources too). In this case, your resource retains interoperability with other OLiA/GOLD-based resources and applications. > > For example, define the pejorative feature: > >> @prefix : <http://example.org/myfeatures#> . >> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . >> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . >> @prefix owl: <http://www.w3.org/2002/07/owl#> . >> @prefix olia <http://purl.org/olia/olia.owl#> . >> >> :pejorative >> a olia:PejorativeEvaluative; >> rdfs:label >> "pejorative"@en, >> "peggiorativo"@en. > > And then link it to the personacce lexical entry: > >> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . >> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . >> @prefix ontolex: <http://www.w3.org/ns/lemon/ontolex#> . >> @prefix lexinfo: <http://www.lexinfo.net/ontology/3.0/lexinfo#> . >> @prefix olia <http://purl.org/olia/olia.owl#> . >> @prefix myfeatures: <http://example.org/myfeatures#> . >> >> <http://example.org/mylexicon/politicastro> >> a ontolex:Word; >> rdfs:label "politicastro"@it; >> lexinfo:partOfSpeech lexinfo:noun; >> olia:hasEvaluativeFeature myfeatures:pejorative. > > If you use OLiA, the easiest way to link features to lexical entries/forms is to reuse subproperties of the olia_system:hasFeature object property (e.g. olia:hasEvaluativeFeature as in the example below). However, defining your own object properties (as subproperties of lexinfo:morphosyntacticProperty) may be a more preferable way. First, the domain of olia_system:hasFeature is the olia_system:LinguisticAnnotation class, and so, strictly speaking, this property is a property of annotations (i.e. token-level entities), not lexical entries or forms. And, second, such subproperties are not defined for all feature classes. Also, you can link all the features just by the single top-level lexinfo:morphosyntacticProperty property. > > Best, > Alexander Kirillovich > > [1] https://acoli-repo.github.io/olia/ > > [2] http://web.archive.org/web/20131118135345/http://linguistics-ontology.org/gold-2010.owl > > вт, 11 апр. 2023 г. в 19:09, Fahad Khan <fahad.khan@ilc.cnr.it <mailto:fahad.khan@ilc.cnr.it>>: >> Dear Flavia, >> DiminuitiveNoun exists as a class in lexinfo. The others don't, but you can open a new issue <https://github.com/ontolex/lexinfo/issues> on the lexinfo github suggesting them as additions to the ontology. >> Cheers >> Fahad >> >> Il giorno mar 11 apr 2023 alle ore 16:58 Flavia Sciolette <flavia.sciolette@ilc.cnr.it <mailto:flavia.sciolette@ilc.cnr.it>> ha scritto: >>> Dear all, >>> >>> I write this email to ask for your advice. I am working on a >>> conversion of a lexical resource for Italian in an ontolex-compliant >>> format. This starting resource describes lemmas and associated forms, >>> some of which are derived with suffixes (e.g. for the diminutive or >>> the pejorative). This kind of form is described with a feature and >>> associated values: “dim” for diminutive, “end” for endearment, “pej” >>> for pejorative, and “aug” for augmentative. I am having some trouble >>> with the conversion of these values to define forms. I set out to use >>> Lexinfo, but, to the best of my knowledge, I have not found exact >>> equivalents. I thought about using a sub-property of morphosyntactic >>> properties but first wanted to figure out if there was a way to use a >>> popular vocabulary like Lexinfo, rather than maintaining >>> resource-specific values. I apologize for this possibly naive concern. >>> >>> Thank you in advance. >>> >>> Flavia Sciolette >>> >>> >>> >>> >>>
Received on Tuesday, 11 April 2023 17:43:42 UTC