12-14 September
Hissar, Bulgaria
ranlp2011@lml.bas.bg
This year RANLP joined the LRE Map Initiative. The map is intended to monitor the use and creation of language resources (datasets, tools, etc.). Submitting RANLP papers via the SoftConf system, the authors are expected to fill in a form describing the resources used in their research. Information on both existing and newly-created resources is collected. Some conferences have already taken part in the initiative and the collected data are now available at http://www.resourcebook.eu.
The resource entry form is simple, to make the RANLP submission process as easy and quick as possible. If the RANLP authors have no resources to describe (e.g. in articles dealing with General issues, Infrastructures, etc.), they should tick the box No resources to report with this submission and complete the submission.
If the RANLP authors have more than one resource to describe, they should fill in one form per each resource. Please note that the RANLP reviewers will also see the information about the presented resources in the form(s).The metadata required per resource (dataset, tool, etc.) consists of:
It is possible that some important information is overlooked. The suggested lists are deliberately kept short, containing only the most frequent/common values. DO NOT feel compelled to use the suggested values, if you feel they do not describe fully your case. In every field you can always choose “Other” and specify the most appropriate label for your resource/tool.
Since the LRE Map initiative is interested in collecting information about the existing resources and resources that the authors create, it may well be that the papers deal with more than one resource. In this case one form for each resource should be filled in while submitting the article. For instance, if a paper discusses the creation of a bilingual lexicon from a parallel annotated corpus using a specific parser, then the author will have to fill in 3 forms: one for the newly created lexicon, one for the annotated corpus and one for the parser).
The SoftConf system provides entering forms about up to 15 resources and/or tools. If you need to fill in more than 10 forms, please contact us.Resource Type: The general type of the resource (e.g. Lexicon, Corpus, Guidelines and Standards, Evaluation resources and methodologies, etc.)
Resource Name: Full name is preferred for newly created resources, followed by the acronym if any. For existing resources, please use the most commonly used term.
Resource Production Status: A tag specifying whether the resource already exists or is newly created. A newly created resource is ‘Completed’ or its development is still ‘in progress’. In the case of an existing resource, the form allows to specify whether it has been simply used (‘Existing-used’) or the authors have updated or modified it (‘Existing-updated’).
Languages: Please use full names and not codes or abbreviations. If you need to list more than one language please separate them with commas (e.g. French, Italian, Chinese).
Modality: Choose one of the suggested options or indicate a more appropriate label.
Use of the Resource: The ‘actual use’ is presented here. For an existing resource, the authors describe the actual application/task using the resource. For any newly created resource please indicate the actual/intended use for which it has been built. Otherwise, select: ‘Not applicable’. NB: In case the resource has more than one use, please select here the most relevant/main application and indicate the others in the “Resource Description” free text box at the end of the template.
Resource Availability:
Resource URL (if available): The authors should indicate the URL of the resource/tool/guidelines described, including the URL of the resource documentation if it is available
Resource Description: It is important to fill in this section especially for newly created resources. This is also the place where the authors can contribute any further detail that were not specified above, e.g. additional uses of the resources, more detailed info about the availability of the resource, etc.
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Documentation: Is there documentation? In which language? Is the documentation publicly available?