Skip to content

FeforProcessors

Jump to bottom
AnnCopestake edited this page May 28, 2006 · 34 revisions

Current topics

See also FeforRmrs

Warning: this page is in a highly unstable state: best not to edit unless you're one of the organisers! Thanks, Ann.

Lexicon building

There will be at least two talks about this in the plenary session.

  • Lexical acquisition, esp. for immature grammars (EmilyBender)

  • large lexica and LexDB (NTNU)

  • large lexicons (FrancisBond)

Interfaces, preprocessors and standoff annotation

  • Standoff Annotation Interface - use in integrating: shallow and deep linguistic processors, speech input (BenWaldron)

  • fspp (simple preprocessor) module, usage in specific grammars

  • Preprocessors (FrancisBond)

  • coordination/discussion on SMAF (UlrichSchaefer)

  • preprocessor implementation and integration (UlrichSchaefer)

  • PET API (proposal, discussion) (UlrichSchaefer)

  • grammar interfaces: clear interface for robustness-related grammar elements

    • (paths/types/pos-tags/expected tokenization/punctuation etc.)
      • e.g. specified in the inline documentation in such a way that it could be processed/extracted automatically from grammar sources.

(UlrichSchaefer)

Tools

If somebody is interested in, I could show how to define SDL cascades in HoG (20-30 min.), e.g. taking the recently integrated RMRS-merging stylesheets (developed by Anette) as an example. But maybe that's too special; an alternative would be a general HoG intro or 'installation party'. (UlrichSchaefer: then let's do a HoG tutorial)

  • Tutorial on web server requested by FrancisBond, with a view to other grammars being put online

  • PET tutorial requested by LarsAhrenberg

  • [incr tsdb()] requested by LarsAhrenberg

    PavelMihaylov (Processing Tools Session)] Trollet: tool for multilingual

grammar engineering - a wrapper around the LKB

  • LKB/PET compatibility issues (NTNU), shared configuration, reducing and documenting the globals (FrancisBond)

  • multilingual grammar engineering issues (NTNU)

  • NL1 project by Martin Magnusson, integrated LKB with the theorem

    • prover SNARK and Temporal Action Logic. Lars Ahrenberg

  • Automated testing (FrancisBond, UlrichSchaefer, cf. also TestingWithAnt)

Working groups

The aim of a working group is to get something working! Working groups are intended for topics that involve a small group that needs to sort out something specific/technical. For instance: there's some tool that the leader developed, the participants have an active interest in and have used at a novice level, but they want it to get it to work on a new grammar etc. We will try to identify possible group leaders, who will sort out the topic and group composition before Fefor. Scheduling is done by the group on an ad-hoc basis.

Installation parties

Suggested by UlrichSchaefer. Leaders have expertise in some resource. The objective is to get particular resource running on participants' computers AND to document on the Wiki on an ongoing basis. i.e, rather than take notes on pieces of paper, the installers write notes on the Wiki. In an ideal world, later installers have a go at installation from the Wiki instructions alone while still at Fefor so we get successive stages of refinement. Leaders need to circulate info about hardware/software requirements in advance. We will schedule some time for these events and identify potential leaders.

* HoG: UlrichSchaefer

Tours of resources

Short descriptions of particular resources.

Home | Forum | Discussions | Events

Clone this wiki locally