Skip to content

FeforProcessors

Jump to bottom
UlrichSchaefer edited this page May 29, 2006 · 34 revisions

Processing session

To take place on the 13th and the morning of the 14th, with small group activities (see below) proceeding throughout the week at Fefor. FeforRmrs will take place on the afternoon of the 14th and morning of the 15th. The emphasis in the processing sessions is intended to be on practical activities that are best done face-to-face and where we can achieve concrete results while at Fefor. In particular, getting existing resources working more widely and improving the wiki documentation. We also hope to make progress on ongoing collaborative activities, especially those that require negotiations of interface standards and so on.

Participants should feel free to add additional information to sessions (obviously large scale additions are best done with new pages), but should email AnnCopestake with suggestions of changes to schedule and topics. Names below are of presenters and also of proposers of discussion topics: leaders of discussions and scribes will be added when we can work out load. Please email AnnCopestake to volunteer.

Preliminary timetable
Morning of the 13th Plenary meeting to discuss organisation, working groups etc.
Initial working group meetings over coffee
Session on testing for developers
Afternoon of the 13th Interfaces, preprocessors and standoff annotation
Small group activities
Morning of the 14th Tools
Lexicon building

Testing (technology and practice for developers)

Interfaces, preprocessors and standoff annotation

  • Standoff Annotation Interface / SMAF (BenWaldron and UlrichSchaefer)

  • Preprocessors (FrancisBond)

  • 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

  • Presentation/Demonstration: Trollet: tool for multilingual grammar engineering - a wrapper around the LKB (PavelMihaylov)

  • Presentation/Demonstration: NL1 project by Martin Magnusson, integrated LKB with the theorem prover SNARK and Temporal Action Logic. LarsAhrenberg

  • Discussion: LKB/PET compatibility issues: shared configuration, reducing and documenting the globals (NTNU, FrancisBond). [ AAC - would this be better as a Working Group? ]

  • Multilingual grammar engineering issues (NTNU) [ not currently sure what this means, have asked - AAC ]

Discussion on lexicon building

  • Requested by FrancisBond and NTNU: details to be decided. (Note that there will be at least two talks about this in the plenary session and that some issues need to be discussed with the grammarians, so this session would be for processing issues and technology development.)

Small group activities

Much of what we might accomplish at Fefor will be best done in small groups. The distinctions made below are not meant to be hard and fast, but are intended to help to achieve concrete results. In all cases, leaders are named (if leaders have been specified inappropriately, please let AnnCopestake know as soon as possible). Other people who may wish to volunteer to lead an activity are asked to add themselves and to email AnnCopestake as soon as possible.

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. Group leaders will sort out the topics and group composition before Fefor (as far as possible). Scheduling is done by the group on an ad-hoc basis. Leaders are asked to add a page to the wiki for their groups. Groups will report back to the plenary session.

Installation parties

Suggested by UlrichSchaefer. (I suggested this as an alternative pharmaceutical form for or addendum to tutorials, BTW HoG installation is already documented in this way, and I am not the author of the following extended definition of installation party. -Uli) Leaders have expertise in some resource. The objective is to get particular resource running on participants' computers AND to document the instructions on the Wiki on an ongoing basis. That is, rather than take notes on pieces of paper, the installers write detailed notes on the Wiki. We would like later installers to try installation from the Wiki instructions alone while still at Fefor so that if things go wrong they can get help easily and then refine the wiki instructions. This is intended for situations less complex than those to be addressed by working groups: the leaders should believe they can get the software working relatively straightforwardly.

Leaders are asked to circulate info about hardware/software requirements in advance (this may just take the form of an appropriate link). Participants may wish to sign up with leaders in advance of Fefor.

Tours of resources

Short descriptions of particular resources for small groups. Possibly including:

  • DanFlickinger: Semantic test suite (for people who haven't seen it, in advance of discussion in FeforRmrs)

  • AnnCopestake: Algebra checking tool (for people who haven't seen it, preferably in advance of discussion of algebra in FeforRmrs)

  • UlrichSchaefer: Defining SDL cascades in HoG e.g. taking the recently integrated RMRS-merging stylesheets (developed by AnetteFrank) (could be part of HoG tutorial or installation party)

Also, if time permits, tours could be given of the resources listed above under working groups or installation parties, for people who just want a introduction.

Home | Forum | Discussions | Events

Clone this wiki locally