[CWB] Does CQPweb support dynamic attributes now?

(Ray) WU Liangping liangpingwu at 126.com
Tue Oct 6 06:31:07 CEST 2015


Thanks Andrew.


Sorry for my confusion about CQP and CQPweb ...


Well, for illustration of "not really executed",  let's take the query [pos="N.*" & f(word)>100] on the Brown corpus for example, which returns 90,211 matches. In comparison, resetting 100 to 1000 in the previous query returns 7,205 matches (all experimented with BFSU CQPweb). This fact shows that the f() function does work. However,  further "Frequency breakdown"  reveals that even words with a single occurrence are in the final result set, an evidence that the f() function is not really respected (at least in some operations within CQPweb). 


I find the dynamic attribute an attractive idea as it would enable CQPweb administrators to  extend the CQP query language to suit their particular needs, for instance, using WordNet for some semantic restrictions. There must be some good reasons for removing it from the source but is it possible to have it back?


Best,
Liangping 

At 2015-10-06 06:35:25, "Hardie, Andrew" <a.hardie at lancaster.ac.uk> wrote:


This is a CQP issue rather than a  CQPweb issue, I think. Anyway…

 

When you say, “doesn’t seem to work” , “not really executed”, what do you mean? That the results were not as desired? Can you give an example of a case where there was a difference between what you expected and what you got?

 

To explain the background:

 

True dynamic attributes, i.e. user-created functions that evaluate by passing their arguments to an external program, no longer exist.

 

However, CQP’s builtin functions (which is the current terminology for what Christ 1994 calls “predefined dynamic attributes”) are implemented using the parameter-passing system for dynamic attributes (but they are not real dynamic attributes because they do not use an external program).   So a lot of the code for dynamic attributes survives to support these functions, even though you can’t have REAL dynamic attributes.

 

These builtin functions are defined in cqp/builtins.c lines 50 to 70, and implemented on lines 229 to 518 . f() is one of them.

 

Finally: Christ (1994) is of historical interest only.  All the builtin functions except f() are documented in the current CQP tutorial, however, which means they are still part of the query language (not sure why f() doesn’t get mentioned, Stefan may be able to shed light)

 

best

 

Andrew.

 

From:cwb-bounces at sslmit.unibo.it [mailto:cwb-bounces at sslmit.unibo.it] On Behalf Of (Ray) WU Liangping
Sent: 05 October 2015 19:17
To:cwb at sslmit.unibo.it
Subject: [CWB] Does CQPweb support dynamic attributes now?

 

hi all,

 

I tried the query [pos="N.*" & f(word)>100] on some corpora but the frequency limitation doesn't seem to work. 

According to Christ (1994: 6) , f is a predefined dynamic attribute. However, the query was happily accepted by CQPweb but not really executed.

I noticed in cwb-decode.c that a comment reads like this "case ATT_DYN: /* dynamical attributes aren't implemented */".

So that is where the answer lies?

 

Thanks for any tips.

Wu Liangping

 

Reference

Christ, Oliver (1994). A modular and flexible architecture for an integrated corpus query system. In Papers in Computational Lexicography (COMPLEX '94), pages 22–32, Budapest, Hungary.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://devel.sslmit.unibo.it/pipermail/cwb/attachments/20151006/1143a9c1/attachment.html>


More information about the CWB mailing list