kern/t0
t0_citlist_showlistid
t0_citlist_showlisttoken
t0_cit
t0_freq_abs
{ "meta": [ "t0_citlist_showlistid", "t0_citlist_showlisttoken", "t0_cit", "t0_freq_abs" ], "data": [] }
Use HTTP_ACCEPT: application/json to get JSON only.
HTTP_ACCEPT: application/json
142 columns in table /kern/t0
/kern/t0
typ_len
t0_freq_nor
t0_freq_abslog
t0_freq_norlog
t0_freq_rank
t0_freq_rank123
t0_fam_abs
t0_fam_nor
t0_fam_abslog
t0_fam_norlog
t0_fam_rank
t0_fam_rank123
t0_inf_abs
t0_inf_nor
t0_inf_abslog
t0_inf_norlog
t0_inf_rank
t0_inf_rank123
t0_div_con_abs
t0_div_con_nor
t0_div_con_abslog
t0_div_con_norlog
t0_div_con_rank
t0_div_con_rank123
t0_div_sen_abs
t0_div_sen_nor
t0_div_sen_abslog
t0_div_sen_norlog
t0_div_sen_rank
t0_div_sen_rank123
t0_c0s_cumfreq_token_abs
t0_c0s_cumfreq_token_nor
t0_c0s_cumfreq_token_abslog
t0_c0s_cumfreq_token_norlog
t0_c0s_cumfreq_token_rank
t0_c0s_cumfreq_token_rank123
t0_c0s_cumfreq_type_abs
t0_c0s_cumfreq_type_nor
t0_c0s_cumfreq_type_abslog
t0_c0s_cumfreq_type_norlog
t0_c0s_cumfreq_type_rank
t0_c0s_cumfreq_type_rank123
t0_cc0s_cumfreq_token_abs
t0_cc0s_cumfreq_token_nor
t0_cc0s_cumfreq_token_abslog
t0_cc0s_cumfreq_token_norlog
t0_cc0s_cumfreq_token_rank
t0_cc0s_cumfreq_token_rank123
t0_cc0s_cumfreq_type_abs
t0_cc0s_cumfreq_type_nor
t0_cc0s_cumfreq_type_abslog
t0_cc0s_cumfreq_type_norlog
t0_cc0s_cumfreq_type_rank
t0_cc0s_cumfreq_type_rank123
t0_ccc0s_cumfreq_token_abs
t0_ccc0s_cumfreq_token_nor
t0_ccc0s_cumfreq_token_abslog
t0_ccc0s_cumfreq_token_norlog
t0_ccc0s_cumfreq_token_rank
t0_ccc0s_cumfreq_token_rank123
t0_ccc0s_cumfreq_type_abs
t0_ccc0s_cumfreq_type_nor
t0_ccc0s_cumfreq_type_abslog
t0_ccc0s_cumfreq_type_norlog
t0_ccc0s_cumfreq_type_rank
t0_ccc0s_cumfreq_type_rank123
t0_init_unigr_abs
t0_init_unigr_nor
t0_init_unigr_abslog
t0_init_unigr_norlog
t0_init_unigr_rank
t0_init_unigr_rank123
t0_init_bigr_abs
t0_init_bigr_nor
t0_init_bigr_abslog
t0_init_bigr_norlog
t0_init_bigr_rank
t0_init_bigr_rank123
t0_init_trigr_abs
t0_init_trigr_nor
t0_init_trigr_abslog
t0_init_trigr_norlog
t0_init_trigr_rank
t0_init_trigr_rank123
t0_uniq_orth_strict_pos
t0_uniq_orth_strict_neg
t0_uniq_lemma_strict_pos
t0_uniq_lemma_strict_neg
t0_pia_avgcondprob_bigr
t0_pia_avginfcont_bigr
t0_pia_avgcondprob_trigr
t0_pia_avginfcont_trigr
t0_nei_col_hf_cumfreq_abs
t0_nei_col_hf_cumfreq_nor
t0_nei_col_hf_cumfreq_abslog
t0_nei_col_hf_cumfreq_norlog
t0_nei_col_hf_cumfreq_rank
t0_nei_col_hf_cumfreq_rank123
t0_nei_col_hf_cnt_abs
t0_nei_col_hf_cnt_nor
t0_nei_col_hf_cnt_abslog
t0_nei_col_hf_cnt_norlog
t0_nei_col_hf_cnt_rank
t0_nei_col_hf_cnt_rank123
t0_nei_col_all_cumfreq_abs
t0_nei_col_all_cumfreq_nor
t0_nei_col_all_cumfreq_abslog
t0_nei_col_all_cumfreq_norlog
t0_nei_col_all_cumfreq_rank
t0_nei_col_all_cumfreq_rank123
t0_nei_col_all_cnt_abs
t0_nei_col_all_cnt_nor
t0_nei_col_all_cnt_abslog
t0_nei_col_all_cnt_norlog
t0_nei_col_all_cnt_rank
t0_nei_col_all_cnt_rank123
t0_nei_lev_hf_cumfreq_abs
t0_nei_lev_hf_cumfreq_nor
t0_nei_lev_hf_cumfreq_abslog
t0_nei_lev_hf_cumfreq_norlog
t0_nei_lev_hf_cumfreq_rank
t0_nei_lev_hf_cumfreq_rank123
t0_nei_lev_hf_cnt_abs
t0_nei_lev_hf_cnt_nor
t0_nei_lev_hf_cnt_abslog
t0_nei_lev_hf_cnt_norlog
t0_nei_lev_hf_cnt_rank
t0_nei_lev_hf_cnt_rank123
t0_nei_lev_all_cumfreq_abs
t0_nei_lev_all_cumfreq_nor
t0_nei_lev_all_cumfreq_abslog
t0_nei_lev_all_cumfreq_norlog
t0_nei_lev_all_cumfreq_rank
t0_nei_lev_all_cumfreq_rank123
t0_nei_lev_all_cnt_abs
t0_nei_lev_all_cnt_nor
t0_nei_lev_all_cnt_abslog
t0_nei_lev_all_cnt_norlog
t0_nei_lev_all_cnt_rank
t0_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/t0/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/t0/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
typ_cit
To select more columns, use the select parameter:
select
http://sr/dlexdb/kern/t0/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/t0/list/?orderby=[-]COL
The default sort order is subject to change. Don't rely on it in your application!
http://sr/dlexdb/kern/t0/list/?top=N&skip=M