SBVR 1.4 RTF Avatar
  1. OMG Issue

SBVR14 — no glossary entry for intensional roles

  • Key: SBVR14-75
  • Legacy Issue Number: 19542
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Edward J. Barkmeyer)
  • Summary:

    SBVR Clause A.2.6 provides syntax for a concept called ‘intensional role’, but there is no such terminological entry and no clear definition.

    In one of the business usage examples for DTV, we have encountered a usage of ‘time period’ in two intensional roles: ‘fixed period’ and ‘variable period’, but we can’t declare them: Concept type: intensional role.

    As A.2.6 says, intensional roles arise when a concept designation is used with verbs of specification and change, and possibly others. The reference is to an unspecified thing of that will satisfy the concept. When one ‘specifies the rental period for X’, the rental period does not denote any time period. The whole idea is that one associates the concept ‘rental period for X’ with an extension that will only exist when the specifying action completes. Similarly, one cannot ‘change the rental period’, one can only change which time period “the rental period for X” denotes. With these verbs, the “intensional role” is equivalent to an ‘answer’ (at least in structure): one specifies “what time period the rental period is”.

    The same idea seems to apply to a verb like ‘prevents’. If someone “prevents a forest fire”, there is no forest fire that is prevented; rather the concept ‘forest fire’ is not instantiated. But unlike the above, one does not prevent “what forest fire it is.” And if one ‘orders 1000 widgets’, they may or may not already exist so that they can be ordered. What one orders is a characterization of objects that are to be instantiated.

    So, the intensional role seems to be a valuable concept for verb concept wordings, because it has real business use

  • Reported: SBVR 1.1 — Thu, 24 Jul 2014 04:00 GMT
  • Disposition: Deferred — SBVR 1.4b2
  • Disposition Summary:

    Deferred to SBVR v1.5 Revision Task Force because the SBVR v1.4 RTF was requested to close before it was finished so the SBVR RTF could be convert to JIRA.

  • Updated: Thu, 6 Apr 2017 13:51 GMT