Issue 17791: How can an attributive role be declared? (sbvr-rtf) Source: NIST (Mr. Edward J. Barkmeyer, edbark(at)nist.gov) Nature: Uncategorized Issue Severity: Summary: SBVR v1.1 Clause 8 says: Note: in the glossary entries below, the words “Concept Type: role” indicate that a general concept being defined is a role. Because it is a general concept, it is necessarily a situational role and is not a verb concept role. How does one declare an attributive role that is not a general concept? SBVR v1.1 appears to use such declarations to also declare roles that are attributive roles of a given noun concept and thus also in the attributive namespace of the noun concept. For example, clause 8.6 declares 'cardinality', which is an attributive role of integers with respect to 'sets', in a glossary entry with Concept type: role. But 'cardinality' is not a general concept; nothing is a 'cardinality', full stop. An integer can only be a 'cardinality' OF something. it is a purely attributive term. As a term for a general concept, 'cardinality' is thus a term in the Meaning and Representation namespace; it has no 'context'. The problem arises in defining attributive roles of general noun concepts, such as 'occurrence has time span' and 'schedule has time span', where the definitions of the two roles are importantly different because they are attributes of different general concepts that are only similar in nature. Neither is a situational role. That is, neither is a general concept. No time interval is a 'time span', full stop. A time interval must be a time span OF something. One 'time span' is in the attributive namespace of 'schedule', and a different 'time span' designation is in the attributive namespace of 'occurrence'. Neither is in the DTV.Situations vocabulary namespace per se. How can this be declared using SBVR conventions? Declaring them both in glossary entries with Concept Type: role apparently makes them conflicting designations for 'situational roles' in the DTV.Situations vocabulary. Does simply declaring the verb concept 'occurrence has time span' declare the attributive role? If so, how is the range of the role declared? And where does the definition of the attributive role go? Resolution: Revised Text: Actions taken: September 26, 2012: received issue Discussion: End of Annotations:===== m: "Barkmeyer, Edward J" To: "issues@omg.org" CC: "Barkmeyer, Edward J" Date: Wed, 26 Sep 2012 01:21:52 -0400 Subject: How can an attributive role be declared? Thread-Topic: How can an attributive role be declared? Thread-Index: AQHNm6bVElURoVuRoEiLmc+3eB0Z3A== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id q8Q5Ni5p006815 Specification: SBVR Version: 1.1 Title: How can an attributive role be declared? Source: Ed Barkmeyer, NIST, edbark@nist.gov' Summary: SBVR v1.1 Clause 8 says: Note: in the glossary entries below, the words .Concept Type: role. indicate that a general concept being defined is a role. Because it is a general concept, it is necessarily a situational role and is not a verb concept role. How does one declare an attributive role that is not a general concept? SBVR v1.1 appears to use such declarations to also declare roles that are attributive roles of a given noun concept and thus also in the attributive namespace of the noun concept. For example, clause 8.6 declares 'cardinality', which is an attributive role of integers with respect to 'sets', in a glossary entry with Concept type: role. But 'cardinality' is not a general concept; nothing is a 'cardinality', full stop. An integer can only be a 'cardinality' OF something. it is a purely attributive term. As a term for a general concept, 'cardinality' is thus a term in the Meaning and Representation namespace; it has no 'context'. The problem arises in defining attributive roles of general noun concepts, such as 'occurrence has time span' and 'schedule has time span', where the definitions of the two roles are importantly different because they are attributes of different general concepts that are only similar in nature. Neither is a situational role. That is, neither is a general concept. No time interval is a 'time span', full stop. A time interval must be a time span OF something. One 'time span' is in the attributive namespace of 'schedule', and a different 'time span' designation is in the attributive namespace of 'occurrence'. Neither is in the DTV.Situations vocabulary namespace per se. How can this be declared using SBVR conventions? Declaring them both in glossary entries with Concept Type: role apparently makes them conflicting designations for 'situational roles' in the DTV.Situations vocabulary. Does simply declaring the verb concept 'occurrence has time span' declare the attributive role? If so, how is the range of the role declared? And where does the definition of the attributive role go? -- Edward J. Barkmeyer Email: edbark@nist.gov National Institute of Standards & Technology Engineering Laboratory -- Systems Integration Division 100 Bureau Drive, Stop 8263 Office: +1 301-975-3528 Gaithersburg, MD 20899-8263 Mobile: +1 240-672-5800