[Index] [Process] [All issues] [CCB issues] [Open NoRes issues]
Export date: 2012-11-19 06:32:58
Row | Id | Category | Summary | Details | Priority | Status | Resolution | Release | Submitter | Assignee | Closer | Date Raised | Date Closed |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | 3566989![]() |
owl classes included in templates made ready for review | owl classes included in templates made ready for review | 5 | Open | Accepted | mikeward | mikeward | nobody | 2012-09-12 11:25:51 | 1970-01-01 12:00:00 | ||
2 | 3568406![]() |
RD: Multiple language definition | It should be possible to manage multiple languages. As an example create Swedish reference data for the PLCS PSM and RDL | 5 | Open | Accepted | robbod | robbod | nobody | 2012-09-17 12:35:37 | 1970-01-01 12:00:00 | ||
3 | 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 | Accepted | mikeward | mikeward | nobody | 2012-09-28 11:09:10 | 1970-01-01 12:00:00 | ||
4 | 3576600![]() |
corrrect and complete owl classes under ExternalUnit | we should create the following class tree: Non_si_unit Context_dependent_unit Us_imperial_unit Si_unit Derived_si_unit_or_multiple Named_derived_si_unit_or_multiple Unamed_derived_si_unit__or_multiple Si_base_unit_or_multiple (though we might use different names) We should then create instances under these classes as follows: Non_si_unit Context_dependent_unit: A small set of examples (eg Flying_hours) according to the needs of the Templates Us_imperial_unit: One or two examples (eg Pound Foot) Si_unit Derived_si_unit_or_multiple Named_derived_si_unit_or_multiple: The complete set of named derived SI units (eg newton pascal) and a small set of multiples (eg kilonewton micropascal) Unamed_derived_si_unit_or_multiple: A small set of examples (eg square_metre square_kilometre) Si_base_unit_or_multiple The complete set of base SI units (eg metre ampere kilogram) and a small set of multiples (eg kilometre microampere gram) The assumption being that these sets of units would be extended as the need arises | 5 | Open | Accepted | mikeward | mikeward | nobody | 2012-10-12 07:38:37 | 1970-01-01 12:00:00 | ||
5 | 3578060![]() |
create owl classes under ProjectAssignment | ie ProjectAsg_planned and ProjectAsg_actual | 5 | Open | Accepted | mikeward | mikeward | nobody | 2012-10-18 11:08:36 | 1970-01-01 12:00:00 | ||
6 | 3576007![]() |
quality of content | corrrect and complete owl classes under StateDefinition | The hierarchy of owl classes under StateDefinition needs to be completed for the set of blocks to which a StateDefinition can be assigned: Activity, File< Project etc and the annotations for those classes need correcting or (in most cases) creating | 5 | Open | Accepted | mikeward | mikeward | nobody | 2012-10-10 11:00:48 | 1970-01-01 12:00:00 | |
7 | 3577682![]() |
quality of content | corrrect and complete owl classes under LocationAssignment | follow the pattern established under DateTimeAssignment: | 5 | Open | Accepted | mikeward | mikeward | nobody | 2012-10-16 05:21:21 | 1970-01-01 12:00:00 | |
8 | 3577693![]() |
quality of content | corrrect and complete owl classes under DocumentAssignment | Delete all existing sub-classes save for those relating to contractual and reference documents and construct the following class tree (renaming and re-defining as required: DocumentAssignment Contractual_document_assignment Reference_document_assignment PartialDocumentAssignment Partial_contractual_document_assignment Partial_reference_document_assignment | 5 | Open | Accepted | mikeward | mikeward | nobody | 2012-10-16 06:08:13 | 1970-01-01 12:00:00 | |
9 | 3577919![]() |
quality of content | corrrect and complete owl classes under PersOrgAsg | delete exiting classes under OrganizationOrPersonInOrganizationAssignment and replace with actual, Planned, and required PersOrgAsg in roles assertor through to user | 5 | Open | Accepted | mikeward | mikeward | nobody | 2012-10-17 10:21:11 | 1970-01-01 12:00:00 | |
10 | 3578062![]() |
quality of content | corrrect and complete owl classes under ContractAssignment | add ContractAsg_actual ContractAsg_planned & delete prefomed_under_contract | 5 | Open | Accepted | mikeward | mikeward | nobody | 2012-10-18 11:16:55 | 1970-01-01 12:00:00 |