kern/typ
typ_cit
typ_freq_abs
Hans
11790
None
Maria
6516
{ "meta": [ "typ_cit", "typ_freq_abs" ], "data": [ [ "Hans", 11790 ], [ null, null ], [ "Maria", 6516 ] ] }
Use HTTP_ACCEPT: application/json to get JSON only.
HTTP_ACCEPT: application/json
156 columns in table /kern/typ
/kern/typ
typ_len
typ_syls_cit
typ_syls_cnt
typ_freq_nor
typ_freq_abslog
typ_freq_norlog
typ_freq_rank
typ_freq_rank123
typ_fam_abs
typ_fam_nor
typ_fam_abslog
typ_fam_norlog
typ_fam_rank
typ_fam_rank123
typ_inf_abs
typ_inf_nor
typ_inf_abslog
typ_inf_norlog
typ_inf_rank
typ_inf_rank123
typ_div_con_abs
typ_div_con_nor
typ_div_con_abslog
typ_div_con_norlog
typ_div_con_rank
typ_div_con_rank123
typ_div_sen_abs
typ_div_sen_nor
typ_div_sen_abslog
typ_div_sen_norlog
typ_div_sen_rank
typ_div_sen_rank123
typ_syls_cumfreq_token_abs
typ_syls_cumfreq_token_nor
typ_syls_cumfreq_token_abslog
typ_syls_cumfreq_token_norlog
typ_syls_cumfreq_token_rank
typ_syls_cumfreq_token_rank123
typ_syls_cumfreq_type_abs
typ_syls_cumfreq_type_nor
typ_syls_cumfreq_type_abslog
typ_syls_cumfreq_type_norlog
typ_syls_cumfreq_type_rank
typ_syls_cumfreq_type_rank123
typ_cus_cumfreq_token_abs
typ_cus_cumfreq_token_nor
typ_cus_cumfreq_token_abslog
typ_cus_cumfreq_token_norlog
typ_cus_cumfreq_token_rank
typ_cus_cumfreq_token_rank123
typ_cus_cumfreq_type_abs
typ_cus_cumfreq_type_nor
typ_cus_cumfreq_type_abslog
typ_cus_cumfreq_type_norlog
typ_cus_cumfreq_type_rank
typ_cus_cumfreq_type_rank123
typ_cbs_cumfreq_token_abs
typ_cbs_cumfreq_token_nor
typ_cbs_cumfreq_token_abslog
typ_cbs_cumfreq_token_norlog
typ_cbs_cumfreq_token_rank
typ_cbs_cumfreq_token_rank123
typ_cbs_cumfreq_type_abs
typ_cbs_cumfreq_type_nor
typ_cbs_cumfreq_type_abslog
typ_cbs_cumfreq_type_norlog
typ_cbs_cumfreq_type_rank
typ_cbs_cumfreq_type_rank123
typ_cts_cumfreq_token_abs
typ_cts_cumfreq_token_nor
typ_cts_cumfreq_token_abslog
typ_cts_cumfreq_token_norlog
typ_cts_cumfreq_token_rank
typ_cts_cumfreq_token_rank123
typ_cts_cumfreq_type_abs
typ_cts_cumfreq_type_nor
typ_cts_cumfreq_type_abslog
typ_cts_cumfreq_type_norlog
typ_cts_cumfreq_type_rank
typ_cts_cumfreq_type_rank123
typ_init_unigr_abs
typ_init_unigr_nor
typ_init_unigr_abslog
typ_init_unigr_norlog
typ_init_unigr_rank
typ_init_unigr_rank123
typ_init_bigr_abs
typ_init_bigr_nor
typ_init_bigr_abslog
typ_init_bigr_norlog
typ_init_bigr_rank
typ_init_bigr_rank123
typ_init_trigr_abs
typ_init_trigr_nor
typ_init_trigr_abslog
typ_init_trigr_norlog
typ_init_trigr_rank
typ_init_trigr_rank123
typ_uniq_orth_strict_pos
typ_uniq_orth_strict_neg
typ_uniq_lemma_strict_pos
typ_uniq_lemma_strict_neg
typ_pia_avgcondprob_bigr
typ_pia_avginfcont_bigr
typ_pia_avgcondprob_trigr
typ_pia_avginfcont_trigr
typ_nei_col_hf_cumfreq_abs
typ_nei_col_hf_cumfreq_nor
typ_nei_col_hf_cumfreq_abslog
typ_nei_col_hf_cumfreq_norlog
typ_nei_col_hf_cumfreq_rank
typ_nei_col_hf_cumfreq_rank123
typ_nei_col_hf_cnt_abs
typ_nei_col_hf_cnt_nor
typ_nei_col_hf_cnt_abslog
typ_nei_col_hf_cnt_norlog
typ_nei_col_hf_cnt_rank
typ_nei_col_hf_cnt_rank123
typ_nei_col_all_cumfreq_abs
typ_nei_col_all_cumfreq_nor
typ_nei_col_all_cumfreq_abslog
typ_nei_col_all_cumfreq_norlog
typ_nei_col_all_cumfreq_rank
typ_nei_col_all_cumfreq_rank123
typ_nei_col_all_cnt_abs
typ_nei_col_all_cnt_nor
typ_nei_col_all_cnt_abslog
typ_nei_col_all_cnt_norlog
typ_nei_col_all_cnt_rank
typ_nei_col_all_cnt_rank123
typ_nei_lev_hf_cumfreq_abs
typ_nei_lev_hf_cumfreq_nor
typ_nei_lev_hf_cumfreq_abslog
typ_nei_lev_hf_cumfreq_norlog
typ_nei_lev_hf_cumfreq_rank
typ_nei_lev_hf_cumfreq_rank123
typ_nei_lev_hf_cnt_abs
typ_nei_lev_hf_cnt_nor
typ_nei_lev_hf_cnt_abslog
typ_nei_lev_hf_cnt_norlog
typ_nei_lev_hf_cnt_rank
typ_nei_lev_hf_cnt_rank123
typ_nei_lev_all_cumfreq_abs
typ_nei_lev_all_cumfreq_nor
typ_nei_lev_all_cumfreq_abslog
typ_nei_lev_all_cumfreq_norlog
typ_nei_lev_all_cumfreq_rank
typ_nei_lev_all_cumfreq_rank123
typ_nei_lev_all_cnt_abs
typ_nei_lev_all_cnt_nor
typ_nei_lev_all_cnt_abslog
typ_nei_lev_all_cnt_norlog
typ_nei_lev_all_cnt_rank
typ_nei_lev_all_cnt_rank123
The list query interface is for fetching properties from dlexDB for a given list of lexical items, as far as they have matches in the dlexDB table that you are querying.
Add the list_eq URL parameter one or multiple times to define a list like so:
list_eq
http://sr/dlexdb/kern/typ/list/?list_eq=VAL1[&list_eq=VAL2...]
If you want the matching against dlexDB entries to be case-insensitive, use the list_eqi parameter instead:
list_eqi
http://sr/dlexdb/kern/typ/list/?list_eqi=VAL1[&list_eqi=VAL2...]
The result set will always contain all of your input items, whether they have a match in dlexDB or not. For items without match, the properties will be NULL. The result set may be longer than your input list if
The list query interface does not offer any filtering options. In order to retrieve lexical items from dlexDB by filtering, use the filter query interface.
In list query mode, the result set contains three or more columns by default:
*_citlist_showlistid
*_citlist_showlisttoken
To select more columns, use the select parameter:
select
http://sr/dlexdb/kern/typ/list/?select=COL1[,COL2...]
If using select, the default columns are discarded unless you include them manually.
The default column selection is subject to change. Don't rely on it in your application!
http://sr/dlexdb/kern/typ/list/?orderby=[-]COL
The default sort order is subject to change. Don't rely on it in your application!
http://sr/dlexdb/kern/typ/list/?top=N&skip=M