[Index] [Process] [All issues] [In work issues]
Export date: 2012-10-08 12:18:02
Row | Id | Category | Summary | Details | Priority | Status | Resolution | Release | Submitter | Assignee | Closer |
---|---|---|---|---|---|---|---|---|---|---|---|
1 | 3572716![]() |
owl classes for id codes should be consistently named | Every SysML block that can be assigned an identifier should have a corresponding owl class that is a sub-class of "Identifier" and that can be used to classify the relevant Identifier and the name of that class should be derived directly from the name of the original block. For example GlobalLocationRepresentation has an attribute called "id" (inherited from LocationRepresentation) which allows for the assignment of one or many Identifiers. Each Identifier can in turn be assigned a Classification that may be an Owl class (or some other type of class). If an Owl class is to be used, it should be called "Global_location_representation_identification_code" (or similar - the "identification_code" suffix is something that requires a separate discussion). It is currently called "Geographic_location_identification_code" - something that cannot be reliably inferred from the relevant block. | 5 | Open | Remind | mikeward | nobody | nobody | ||
2 | 3572722![]() |
owl classes for id codes should be consistently structured | Every SysML block that can be assigned an identifier should have a corresponding owl class that is a sub-class of "Identifier" and that owl class should appear in a hierarchy that is structured just like the main class tree. For example the owl class "ActivityMethod" has (inter alia) a sub-class called "TaskElement" and "TaskElement" has (inter alia) sub-classes called "EndTask" and "ExitLoop": Activity_method Task_element End_task Exit_loop All the corresponding SysML blcoks can be assigned identifiers which can in turn be assigned a Classification that may be an Owl class (or some other type of class). The relevant Owl classes should be as follows: Identifier Activity_method_identification_code Task_element_identification_code End_task_identification_code Exit_loop_identification_code This hierarchy reflects that the set of exit loop ids is a subset of the set of task element ids which is (in turn) a subset of the set of activity method ids and also provides a reliable way to infer the route to a particular owl id class in the tree. (The "identification_code" suffix is something that requires a separate discussion) It can be argued that other groupings are required - eg the set of owl id classes that include the word "version" (not all of which will occur under "Product_version_identification code") but if this is felt necessary, an additional class called "Version_identification_classes" (or similar) should be created and all the relevant owl classes should be included in that class IN ADDITION to their inclusion in the "correct parent class in the owl tree. Such additional groupings would provide an additional navigation mechanism, but at the expense of additional complexity. | 5 | Open | Remind | mikeward | nobody | nobody |