Next: Looking for feedback
Up: Structurecontents and status
Previous: Structurecontents and status
Even though we are formally at the end of a phase of EAGLES activity, it
must be clear that:
- The results stemming from this initiative are not
at the same level of completion since some Working Groups
began work in 1993 and their results have therefore undergone a wide
process of testing, application, feedback and revision, whereas others
began work only in 1995 and are therefore in a phase of first
proposals; and
- Not all the Working Groups, and the Subgroups within
them, had the objective of reaching a normalisation proposal, some of
them having considered as possible - within the timeframe and
person months effort available - only preparatory work in view of future
normalisation activity proper.
We attach therefore to each document (or sometimes to
parts of a document) a label describing its current status.
The labels used are given in table 1.
Label | Description |
R | Recommendations |
P | Preliminary recommendations or first proposals |
F | Formal specifications and explicit guidelines |
V | Validation document |
B | Background document |
D | Data produced according to EAGLES recommendations |
L | Links to related project documents |
| |
Table 1: Status labels of EAGLES documents
No labels are attached to summaries, introductions, conclusions,
syntheses, etc. The definitions of these labels are, in more detail:
- R: Recommendations
- -- Applies to those parts where work has reached a stage allowing the formulation of
recommendations concerning common specifications, definitions, terminology, etc.
Usually these recommendations have already been widely publicised in the community,
have been tested, applied, evaluated and accordingly revised.
- P: Preliminary recommendations
- -- Applies to those parts where preliminary recommendations -- sometimes rather general --
could be formulated, but these are being made available outside EAGLES only now and
therefore did not have the chance of being commented on, evaluated, tested, etc. We
expect to have major feedback on these from now onwards and thus envisage
revisions to them.
- F: Formal specifications and explicit guidelines
- -- Applies to those parts which provide formal, explicit guidelines and specifications for
implementing the above recommendations. This typically involves taking broad
recommendations and formalising them to the point of demonstrating how to instantiate
them for specific languages.
- V: Validation document
- -- Applies to documents produced in testing EAGLES recommendations within EAGLES internal validation tasks, especially in relation to application-specific areas.
- B: Background document
- -- Applies to those parts which are at an earlier stage of development and where only survey
or other preparatory work has been done, or where, in certain cases, individual views
have been put forward as a trigger to consensus building.
- D: Data produced according to EAGLES recommendations
- -- Applies to linguistic data which have been produced, analysed or encoded according to
EAGLES recommendations, outside EAGLES itself, by affiliated projects or other bodies
collaborating with EAGLES.
- L: Links to related project documents
- -- Applies i) to links to Web or ftp sites of related projects, having contributed to EAGLES
either with input or in the testing, application, validation phases, and ii) to particular
documents of such projects of particular relevance to EAGLES.
Next: Looking for feedback
Up: Structurecontents and status
Previous: Structurecontents and status