| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:pojmy:ud [2023/04/04 10:22] – [Corpus Search] alexandrrosen | en:pojmy:ud [2023/04/04 12:08] (current) – [Other categories] alexandrrosen |
|---|
| * In an advanced query using the CQL query language each category can be specified separately: the Czech form //moře// 'sea' is one of the answers to the query ''%%[upos="NOUN" & feats="Number=Sing"]%%''. The Russian form is found following the query ''[upos=%%"NOUN"%% & feats=%%"Gender=Fem"%% & feats=%%"Case=Gen"%%]''. The order of categories in the query is irrelevant. | * In an advanced query using the CQL query language each category can be specified separately: the Czech form //moře// 'sea' is one of the answers to the query ''%%[upos="NOUN" & feats="Number=Sing"]%%''. The Russian form is found following the query ''[upos=%%"NOUN"%% & feats=%%"Gender=Fem"%% & feats=%%"Case=Gen"%%]''. The order of categories in the query is irrelevant. |
| * The value of ''feats'' can also be treated as a string of characters using regular expressions, e.g. ''[upos=%%"NOUN"%% & feats=%%".*Case=Gen.*Gender=Fem.*"%%]''. Here the order of categories in the query should correspond to their order in the corpus. The result is the same in both cases. | * The value of ''feats'' can also be treated as a string of characters using regular expressions, e.g. ''[upos=%%"NOUN"%% & feats=%%".*Case=Gen.*Gender=Fem.*"%%]''. Here the order of categories in the query should correspond to their order in the corpus. The result is the same in both cases. |
| * Some of the categories in ''feats'' are listed also outside the list as **categorial attributes** at the same level as ''upos''. As a result, a query for a singular noun can be simply as follows: ''%%[upos="NOUN" & number="Sing"]%%''. Similarly, the query for the Russian form ''[upos=%%"NOUN"%% & %%gender="Fem"%% & %%case="Gen"%%]'' gives the same result as the two queries above. Categorial attributes can be also used to generate frequency lists.((Note that for technical reasons the names of the categorial attributes are all in lower case, including names such as ''VerbForm'' (in ''feats''), rendered as ''verb_form'', or ''NumType'', rendered as ''num_type''. The attribute values, such as ''Fem'', retain the initial upper case character, but are enclosed in double quotes, like other non-embedded attributes.)) Such attributes appear on the <fc #f4a460>light brown</fc> background in {{cnk:intercorp:ud_ic_atributy.pdf|Attribute list by language}} or in KonText in the lower part of the table shown in ''View'' / ''Corpus-specific settings...'' . | * Some of the categories in ''feats'' are listed also outside the list as **categorial attributes** at the same level as ''upos''. As a result, a query for a singular noun can be simply as follows: ''%%[upos="NOUN" & number="Sing"]%%''. Similarly, the query for the Russian form ''[upos=%%"NOUN"%% & %%gender="Fem"%% & %%case="Gen"%%]'' gives the same result as the two queries above. Categorial attributes can be also used to generate frequency lists.((Note that for technical reasons the names of the categorial attributes are all in lower case, including names such as ''VerbForm'' (in ''feats''), rendered as ''verb_form'', or ''NumType'', rendered as ''num_type''. The attribute values, such as ''Fem'', retain the initial upper case character, but are enclosed in double quotes, like other attribute values outside ''feats''.)) Such attributes appear on the <fc #f4a460>light brown</fc> background in {{cnk:intercorp:ud_ic_attributes.pdf|Attribute list by language}} or in KonText in the lower part of the table shown in ''View'' / ''Corpus-specific settings...'' . |
| |
| ^ category ^ gloss ^ example values ^ | ^ category ^ gloss ^ example values ^ |
