Issues agianst the templates and ballots

The following issues have been raised against the templates
and DEXs out for public review

 

Template: assigning_concession

Issue: MWD-01 by MIke Ward (2008-04-29) minor_technical
issue 

Resolution: Accept. Status: open

Reference data has been assigned to the Approval entity. The reference data
should have been assigned to the Assigning_approval entity - as a replacement
for the Assigning_approval.role attribute. 

Comment: ( )

Template: assigning_reference_data

Issue: RBN-5 by Rob Bodington (08-06-18) major_technical issue

Resolution: Accept. Status: open

Assigning reference data template is used to both: 1) indicate that a PLCS
entity is an external class defined by reference data 2) indicate that a PLCS
entity is an individual defined by reference data The semantics of
classification assignment do not support this. The assigning reference data
template should make it clear that the assignment if either to an individual or
a class, or another mechanism should be provided for assigning individuals as
reference data. A number of templates that use assigning_reference data are
using it to assign classes that should in fact be individuals. The associated
reference data (OWL files) should be corrected so that individuals are created
rather than classes. There is also a conflict in DEXlib (in some areas) as to
which EXPRESS attributes should be populated with individuals. Specifically,
most templates assume that identification codes will populate
Identification_assignment.identifier and that the classifiers of those codes will
populate External_class.name. The way that some OWL files have been populated
and the (particularly) assigning_code template assumes that the codes
themselves will populate External_class.name. This is not just incorrect from a
semantic point of view, it is inconsistent. A rigorous and consistent approach
to the use of reference data classes and instances in DEXlib is clearly
required. 

Template: assigning_security_classification

Issue: PBM-1 by Peter Bergstrom (08-04-16) minor_technical
issue 

Resolution: Accept. Status: open

The template assigning_security_classification has an error in figure 3, where
it uses the template assigning_requirements instead of
assigning_reference_data. 

Template: assigning_work_output

Issue: EPM-98 by Erik Balaton, EPMT (2007-8-9)
minor_technical issue 

Resolution: Accept. Status: open

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\\EPM
reviews\template_issues_EPMT_JH.xls Template: assigning_work_output Check list
clause: 28 Optional templates are shown, but do not appear in the
characterization section. 

Template: independent_property_limit

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

INDEPENDENT_PROPERTY_LIMIT: path referring to a reference parameter which is
not declared (^representation). It should be. 

Template: independent_property_numeric

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

path referring to a reference parameter which is not declared
(^representation). It should be. 

Template: independent_property_range

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

path referring to a reference parameter which is not declared
(^representation). It should be. 

Template: independent_property_range

Issue: PHX-2 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

INDEPENDENT_PROPERTY_RANGE: Wrong type for input params: upper_limit and
lower_limit, should be ANY_NUMBER_VALUE instead of MEASURE_VALUE to be
consistent with inner template REPRESENTING_VALUE_RANGE 

Template: independent_property_text

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

path referring to a reference parameter which is not declared (^representation)

Template: independent_property_w_tolerances

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

path referring to a reference parameter which is not declared (^representation)

Template: representing_physical_element

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

REPRESENTING_PHYSICAL_ELEMENT has no uniqueness constraints ... I think it
should have 

Template: representing_planned_activity

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

REPRESENTING_PLANNED_ACTIVITY: Wrong types for input param: year, month, day,
hour, minute, second ... they should be of the corresponding DefinedType in the
schema not IntegerValue 

Template: representing_planned_activity

Issue: PHX-2 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

REPRESENTING_PLANNED_ACTIVITY: Usage constraint should also include the
following template parameters: id_owner id_owner_class_name id_owner_ecl_id 

Template: representing_planned_activity

Issue: PHX-3 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

Figure 1 EXPRESS-G - the assigning_identification template has a parameter
org_id_class_name defaulted to "owner_of" - it should have no default
here 

Template: representing_probability_numeric

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

REPRESENTING_PROBABILITY_NUMERIC: missing usage constraint on instance of
REPRESENTATION_CONTEXT 

Template: representing_resource_item

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

REPRESENTING_RESOURCE_ITEM: Usage constraint should also include the following
template parameters: res_item_id_owner res_item_id_owner_class_name
res_item_id_owner_ecl_id 

Template: representing_task_simple

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

REPRESENTING_TASK_SIMPLE has no uniqueness constraints 

Template: representing_task_simple

Issue: PHX-2 by Patrick Houbaux (08-04-16) minor_technical
issue 

Resolution: Accept. Status: open

REPRESENTING_TASK_SIMPLE path doesn't set the attribute of_task_method on the
instance of TASK_METHOD_VERSION 

Template: representing_task_simple

Issue: PHX-3 by Patrick Houbaux (08-04-16) minor_technical
issue 

Resolution: Accept. Status: open

REPRESENTING_TASK_SIMPLE path doesn't set the content attribute of the
TASK_METHOD_VERSION to the instance of TASK_STEP 

Template: representing_task_step

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

REPRESENTING_TASK_STEP has no uniqueness constraints 

Template: representing_value_range

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

REPRESENTING_VALUE_RANGE: path refererring to 2 reference parameters which are
not declared (^upper_item, ^lower_item) 

Template: representing_zone_breakdown

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

Uniqueness constraint on Zone_breakdown_version in REPRESENTING_ZONE_BREAKDOWN
is wrong. It should also include id and id_owner of the Zone_breakdown 

Template: representing_zone_element

Issue: RBN-1 by Patrick Houbaux (08-04-16) minor_technical
issue 

Resolution: Accept. Status: open

The template REPRESENTING_ZONE_ELEMENT has no uniqueness constraints ... I
think it should have 

Template: representing_zone_structure

Issue: PHX-1 by
Patrick Houbaux (08-04-16) minor_technical issue 

Resolution: Accept. Status: open

The path doesn't set the attribute name of the ZONE_ELEMENT_USAGE to /IGNORE. 

Template: resource_property_limit

Issue: PHX-1 by Patrick Houbaux (08-04-16) major_technical
issue 

Resolution: Accept. Status: open

Wrong type of input parameter "property". It should be
RESOURCE_PROPERTY instead of ASSIGNED_PROPERTY 

DEX: aviation_maintenance

Issue: RBN-7 by Rob Bodington (08-03-20) minor_technical
issue 

Resolution: Accept. Status: open

The NSN code should be broken down into it constituent parts. E.g. NIN code.
Consider using the Item of supply 

DEX: aviation_maintenance

Issue: RBN-8 by Rob Bodington (08-03-20) minor_technical
issue 

Resolution: Accept. Status: open

The section on a reportable item "10303-239 representation Representing a
reportable item", should show how to represent the GUID 

DEX: aviation_maintenance

Issue: RBN-9 by Rob Bodington (08-03-20) minor_technical
issue 

Resolution: Accept. Status: open

When representing a state. There should be a representation of "how"
something was determined to be in a given state. E.g. by measurement of a
particular piece of test equipment. The relationship between a fault state and
a symptom should also be made explicit. E.g. the cause effect relationship. The
"Observation/symptom" is that the car vibrates = the cause is the
flat tyre state of the wheel. 

DEX: aviation_maintenance

Issue: RBN-10 by Rob Bodington (08-03-20) minor_technical
issue 

Resolution: Accept. Status: open

Figure 23 "UML class diagram representing the state of an asset" The
deferred fault should go straight to a closed work order 

DEX: aviation_maintenance

Issue: RBN-11 by Rob Bodington (08-06-18) minor_technical
issue 

Resolution: Accept. Status: open

"Figure 39 EXPRESS-G diagram for representing a usage activity" The
justification shoudl be optional as you may not know what caused the chnage in
propoerty.

 

Regards

Rob

--------------------------------------------------------------------------------

Rob Bodington

Eurostep Limited

Web Page: http://www.eurostep.com http://www.share-a-space.com

Email: 

Phone: +44 (0)1452 810 960

Mobile: +44 (0)7796 176 401

Skype: rbodington

Eurostep
Limited. Registered in England and Wales No.03049099

Registered
Office: Cwttir Lane, St. Asaph, Denbighshire LL17 0LQ.