Team Registration

Registration
==========================================================
Registration is required before downloading task training/test
datasets.

When registering, teams need to carefully choose how they wish to be
identified.  Note that both your team name and the name(s) of your
system(s) will be used on the website, in the proceedings, in the
result tables, and also in your system paper title. For this reason
participants must to follow the guidelines below.

(Additional information can be found here: "General rules about
team-system definition and paper authorship")

- Each team should be identified by a descriptive 2-5 letter
  abbreviation, preferably taken from the affiliation (e.g. UBC for
  the University of the Basque Country)

- We allow sites to register more than one team, where each of the
  teams signs in for a number of tasks. Team members don't need to be
  disjoint, but two teams with exactly the same members may not register
  as two teams.  These teams should use abbreviation-label as
  identification. Teams should choose the label with care. Some options
  include to choose the first letters of the members (e.g. UBC-ALMB,
  UBC-AC) or just a number (e.g. UBC1, UBC2)

- In order to ease browsing the proceedings and finding citations,
  teams will have to put their team name in the title of their system
  paper (e.g "UBC-ALMB: WSD using ..."). Please take into account the
  "General rules about team-system definition and paper authorship"
  in these guidelines, and try to match team identifications and papers.

Please try to follow these guidelines. If you have trouble with them
please contact the Semeval coordinators.

General rules about team-system definition and paper authorship
================================================================
The organizers would like to avoid multiple submissions of very
similar systems from the same teams, as well as multiple papers from
the same team describing one basic system applied to similar tasks. We
would also like to make the proceedings easier to browse, making the
mapping from system identification to paper title easier.
            
We therefore would like to set general rules regarding these issues:
            
1. On registration, participant teams will need to provide a unique
team ID and a list of its members.

2. The team will then specify the tasks it is participating on, adding
a short description of the systems (e.g. "supervised system based on
SVMs and kernels"). The webpage will then return unique "team-task"
keywords (e.g. UBC-ALMB-11 for task 11). 
            
3. Each team can only submit a single system for each task. The system
will be identified by the "team-task" keyword. If multiple results are
uploaded all but the last will be automatically discarded.
            
4. Each team will get one paper in the proceedings.

Exceptions to 3 are allowed when one team prepares two
substantially different systems for the same (or the same family of)
tasks. Participants should contact task organizers and Semeval
organizers, which might then grant the authorization. In any case, all
systems will have to be described in a single (possibly longer) paper.

Exceptions to 4 are allowed when one team participates in two
different kind of tasks. Participants should contact task organizers
and Semeval organizers, which might then grant the authorization.