Re: Reviving Semantic Relationships in Beagle

2007-10-27 Thread Roberto Marino
I'm very interested on this topic. I guess that organize metadata in a
RDF document is a good idea. But, in my opinion, the best improvement
would be to arrange beagle metadata in a OWL ontology.
In this way, metadata could populate a Knowledge Base of system.
Clearly, this involve a preexisting OWL rules.
The challenge, for me, is to build a GUI that easily allow Description
Logic search.

Regards.
Roberto

-- 
Roberto (aka formica) Marino
Computer Engineering Student
Free Software User - Me|Lug Member
--> [EMAIL PROTECTED] <--
http://www.messinalug.org
Mobile: 349-5740870

keyID = 641AE37D on pgp.mit.edu

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Exclude patterns and subdirectories

2007-10-27 Thread Debajyoti Bera
(This is more relevant to distributions and sysadmins)
Earlier beagle had a hardcoded list of file and directory name patterns 
(Makefile.in, .*, *.o etc) and directories (~/tmp) to ignore. There was a way 
to add more patterns and directories to the ignore list but nothing to enable 
indexing of a file with any of the default excluded patterns, e.g. Also, 
build-index was not using the full ignore list as that used by the file 
system backend.

With the new configuration system, the list is now configurable. The global 
default is in the config file 
$SYSCONFDIR/beagle/config-files/FilesQueryable.xml Add or remove values at 
will. Note that for subdirectories to exclude, environment variables can be 
used (e.g. the default excluded subdirectories included in the 
FilesQueryable.xml are $HOME/tmp and $BEAGLE_HOME/tmp). BuildIndex now shares 
the same exclude pattern list as well.

Users can further override the behaviour to their liking by using the 
beagle-settings GUI or beagle-config. If you can test the system and help us 
iron out any remaining bugs in the new config system, that will be 
appreciated.
Thanks.

- dBera

-- 
-
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


webinterface enable: howto

2007-10-27 Thread Debajyoti Bera
Hi,
There has been several more changes to the web-interface included in 
the 
trunk. Namely, the static html page is removed and all html is generated from 
an xml file and xml data (+xslt + css). The UI looks much better. It also 
provides a way to view information about the beagled process and shutdown 
beagled. The hits are now categorized and the categories can be shows/hidden 
by checkboxes. And most importantly it has a new (based on beagle-project 
logo) logo :-).

Enough advertising. The webinterface is now available in trunk (with 
the 
files served by the server is in the location pointed to by 
BEAGLE_WEBSERVER_DIR) but disabled by default. There are two config options 
related to this:
1) config:Networking - option:ServiceEnabled = turns on/off network search. 
WebInterface is turned on at the first available port after 4000. This has to 
be set before beagled is started. Local beagled (thus the webinterface too) 
can be queried from anywhere in the network 
(http://:4000).
  $ beagle-config Networking ServiceEnabled
2) config:Networking - option:WebInterface = turns on/off webinterface, only 
if ServiceEnabled is false. This can be set/unset even when beagled is 
running and the webinterface will be accordingly started or stopped. The 
webinterface is only accessible from localhost (http://localhost:4000).
  $ beagle-config Networking WebInterface

Due to a couple of mono bugs (fixed and to be available in mono-1.2.6), even 
when the web interface is apparently stopped (and trying to access 
http://localhost:4000 results in a failure), beagled keeps on listening on 
port 4000. This is harmless since nothing can be accessed via that port (but 
still an open port, so you should know this fact).
And mono HttpListener listens on all interfaces - but again this is harmless, 
because illegal access is denied (e.g. only setting WebInterface to true 
causes beagled to listen on port 4000 on all interfaces, but only queries 
from localhost are allowed).

The hits displayed in the webinterface are clickable links. On firefox 1.5, 
clicking the links to open in a new tab causes the file to open; on firefox 
2.0 and above, opening of local files is completely disallowed due to 
security reasons. There are user configurable options to override this and 
allow the user to click on hits and open results - we will describe them in 
detail sometime soon.

- dBera

-- 
-
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers