<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>Advogato blog for adubey</title>
    <link>http://www.advogato.org/person/adubey/</link>
    <description>Advogato blog for adubey</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Thu, 23 May 2013 11:06:37 GMT</pubDate>
    <item>
      <pubDate>Thu, 24 Aug 2000 18:05:59 GMT</pubDate>
      <title>24 Aug 2000</title>
      <link>http://www.advogato.org/person/adubey/diary.html?start=1</link>
      <guid>http://www.advogato.org/person/adubey/diary.html?start=1</guid>
      <description>&lt;P&gt;Random thoughts... does anyone else find advogato's
interface a bit lacking?

&lt;p&gt; &lt;P&gt;Often, I find I have to click through 2-3 pages to do
common things like post a diary entry.  In general, I feel
like it's harder than it should be to do the things I want
to do, or that I do often.  While this feeling might go away
after I get used to it, perhaps it isn't as welcoming to new
users.

&lt;p&gt; &lt;P&gt;Other random thoughts...  sometimes people post diary
entries that have interesting ideas that are worth
discussing.  While email is a suitable route for that,
wouldn't it be cool if you could reply to those?

&lt;p&gt; &lt;P&gt;Even more random...  first there were linear news
readers, then there were "threaded" news readers.  These are
essentially trees, where each node has one parent.  Now, the
web does threaded discussions one up: we have directed
graphs instead of trees.  But short of a &lt;A
HREF="http://www.kehei.com/kehei/doc/WikiWikiWeb.html"&gt;WikiWikiWeb&lt;/a&gt;-type
CGI program, the web is geared to "read this" rather than
"comment on this".  Mightn't it be cool if you had some kind
of "threaded" system where posts may have more than one
parent?  Someplace where you could bring separate
discussions that are mutually relevant together instead of
forever splitting them.  For example, a discussion hanging
off an article with one hanging off a diary entry.  Ah... if
I only I had the time...  anyways, I'm getting far too
random for my own good.

&lt;p&gt; &lt;P&gt;Anyways, my prob parser is stuck right now; the training
data is in an ass-backwards format in which words aren't
necessarily given a part-of-speech.  In other words, rules
are in the form Nonterminal-&amp;gt;(Terminal|Nonterminal)* rather
than Nonterminal-&amp;gt;Terminal* | Nonterminal-&amp;gt;Nonterminal*.  Of
course, I could split things up myself (by putting the
grammar in CNF), but then there I will loose some
generalizations (ie in AP-&amp;gt; NP and NP | AP-&amp;gt; VP and VP NP,
each "and" will get a different non-terminal, but I want
only one.  Sometimes the POS will be different, so I can't
say "always make 'and' an adjunct".)  Grr... I could use a
part-of-speech tagger, but then I have to 1) link the 'C'
POS tagger to ML or 2) play around with the training data's
nonterminals to be compatible with the tagger's tags. 
Alternatively, I could shell out $2500 for a good training
set...</description>
    </item>
    <item>
      <pubDate>Wed, 23 Aug 2000 19:56:38 GMT</pubDate>
      <title>23 Aug 2000</title>
      <link>http://www.advogato.org/person/adubey/diary.html?start=0</link>
      <guid>http://www.advogato.org/person/adubey/diary.html?start=0</guid>
      <description>&lt;P&gt;This is my first diary entry.  I've just added three
"projects" although I'm only actively working on two of
them.

&lt;p&gt; &lt;P&gt;They are &lt;A
HREF="http://www.advogato.org/proj/Simulus/"&gt;Simulus&lt;/a&gt; (a
game), a really bad first &lt;A
HREF="http://www.advogato.org/proj/Speech%20for%20Gnumeric/"&gt;attempt&lt;/a&gt;
at making a speech interface to a software application - in
this case gnumeric (this is the one that I've abandonded for
now) and finally, my &lt;A
HREF="http://www.advogato.org/proj/Probabilisitc%20Parser/"&gt;probabilistic
parser&lt;/a&gt;.

&lt;p&gt; &lt;P&gt;My short-term goal is getting the parser to a workable
state.  When that's done I'll probably post another diary
entry.  I don't intent to touch the game until
september.</description>
    </item>
  </channel>
</rss>
