1. You use these classes in the annotator code in the next step.

2. Note that the Relationship Annotator can detect relationships without looking at the actual document text, but by analyzing preexisting concepts and grammar annotations in the CAS.

3. With the annotator aspect approach, the participation occurs only at the level of a shared understanding of annotation type.

4. For example, if you are running multiple annotators in a row, one annotator can access the annotations that were created by previously running annotators.

5. A custom-developed annotator would replace or be deployed together with the provided regular-expression annotator.

6. Use inside the table annotator to select an entire column.

7. Each annotator stores its results in typed feature structures, which are simply data structures that have a type and a set of (attribute, value) pairs.

8. With both the annotator and the mapping file linked to the collection, documents can be crawled, parsed, and indexed.

9. CVD runs the annotator on sample texts that can be copied into the CVD interface.

10. During development of the annotator,() you might want to test it out on some sample text.

11. You could, for example, implement one annotator aspect per package.

12. Used inside the field annotator to specify a selectable option.

13. The most important methods of the Annotator interface are initialize and process.

14. The regular expression annotator is configured by means of an XML file.

15. Many text analysis tasks can be addressed by extending the rules of the regular expression annotator.

16. This file contains a set of rules that define on what type of character or number sequences the annotator should act and how it should act.

17. To simplify the extraction of document text,[http://] the OmniFind/ICM integration can be run in "training mode" (not included in the sample annotator).

18. The rule and type system changes discussed in the previous section must be applied to the XML rule and type system files in the installed version of the regular expression annotator PEAR.

19. Now the collection is ready to process documents with the customized annotator and store the results in its search index.

20. The PEAR format contains all necessary information to run the wrapped annotator component.

21. For more complex text analysis tasks, the development of a custom annotator may be of interest.

22. A PEAR file is actually a ZIP archive file that contains the annotator code and configuration in a well-defined directory structure.