The terminology server will accept CTU expressions when the stated attribute(s) refines the meaning of the focus concept, without adding new attributes or groups.
In this case, the terminology server will accept attributes-value pairs with the following characteristics:
- The attribute is already present in the NNF of the focus concept
- The attribute value stated in the expression is a subtype of the attribute value of the focus concept
Important Notes
- If no groups are stated in the CTU expression (i.e. attributes are declared as loose attributes), the terminology server will accept attribute-value pairs correctly belonging to role groups of the focus concept as follows:
- The terminology server will accept attribute-value pairs that refine one or more of the attribute-value pairs of the focus concept, i.e.
- The attribute type should be the same as, or a subtype of, an attribute that already exists in the NNF of the focus concept, for which
- The attribute value may be the same as, or a subtype of, the existing attribute value
- The attribute type should be the same as, or a subtype of, an attribute that already exists in the NNF of the focus concept, for which
- The terminology server will reject attribute-values, if this is a supertype of the attribute value used in the definition of the focus concept
- The terminology server will accept attribute-value pairs that refine one or more of the attribute-value pairs of the focus concept, i.e.
- If groups are stated in the CTU expression
- The terminology server will accept groups that refine an existing role group of the concept, i.e. the group stated in the CTU should represent a subtype of the role group of the focus concept
Table 5.3.2.1-1: Examples of CTU expressions candidate to this pattern, and their evaluation at level 1.
Feedback
Overview
Content Tools
Apps