Next: , Previous: , Up: Annotation schema   [Contents]


7.3.1 Strict or loose handling of an annotation schema

You can configure, how strict standoff mode enforces an annotation schema. You can configure, to not restrict markup types, relation predicates etc. at all. Then, the annotator is free to use what ever type or predicate comes to his mind. But even then, a list of types, predicates etc. he used before is presented to him on the UI; but he can ignore it and type in a new type, predicate etc. Let’s call this process of implicitly generating an open annotation schema a posteriori.

The other alternative is to restrict the user input regarding markup types, relation predicates etc. to an annotation schema given a priori.

User Option: standoff-markup-type-require-match
User Option: standoff-predicate-require-match
User Option: standoff-literal-key-require-match

These user options define how restrictive the markup schema is handled. If set to t then the entered type must be amongst the members of the list of markup types, relation predicates of attribute name defined in the schema or so far used in the source document. If set to nil, the user may exit his input with any type. If set to 'confirm (quoted symbol), the user may exit with any type, but is asked to confirm his input. All these user options default to 'confirm.

User Option: standoff-markup-types-allowed
User Option: standoff-relations-allowed
User Option: standoff-literal-keys-allowed

These user options each take a list of allowed types, predicates of attribute names. Default is the empty list '().