If you have a moment, this question could only be answered by you. It looks
like the tagging is done within the AtD code. I was wondering why you chose
to do this, rather than use an available 3rd party PoS tagger? Was it for
performance reasons? (I know your design document mentioned that
performance was considered critical for the service). For my needs,
accuracy is going to trump performance and I'm considering swapping out the
tagger with a more accurate one. As I develop rules, I'm finding that I
need to get very creative in order to work around improperly tagged
sentences. I end up having to considerably narrow the scope of my rules, or
abandon the rule completely due to so many false positives. If you have a
minute, I'd be interested in hearing your thoughts on the PoS tagging and
the idea of swapping that portion out. Any pitfalls? Suggestions?
Also, if anyone else has modified, or attempted to modify, the AtD PoS
tagging, I would love to hear your experiences.