Template:— representing_geographical_location (rep_geo_locn)
Capability:representing_location		 Date: 2005/08/15 08:20:35 :
Revision: 1.15
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssuesin situ

Issue raised against: representing_geographical_location

GENERAL issues

Open issue Issue: RBN-1 by Rob Bodington (07-08-07) minor_technical issue
Resolution: Accept. Status: open

The XML for the template is not valid

Open issue Issue: TJT-1 by Tim Turner, LSC (04/09/2007) minor_technical issue
Resolution: Accept. Status: open

Parse error by Graphical Instance vn 1.0.5.20; Element content is invalid according to the DTD/Schema. Expecting: valid element at line 309: See figure id="representing_geo_char_location_inst.png"

Open issue Issue: DNV-3 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: General#7 The checklist requires files to be in the dvlp directory. This seems systematically not to be the case. Is the checklist wrong?

Open issue Issue: DNV-40 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: General#5 The naming of the files is not as required.

Open issue Issue: DNV-41 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: XML#9 upto should probably be split in two. metre should probably be meter. Several places the template seems to be called "Representing Global Location Representation".

Open issue Issue: DNV-42 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: XML#14 The "Type" of the parameters could be hyperlinked.

Open issue Issue: DNV-43 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: Cover#19 Names of reviewers are only given as company names.

Open issue Issue: DNV-44 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: Cover#20 Current status is "in_model_review"

Open issue Issue: DNV-45 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: Cover#22 Location_assignment should e.g. be mentioned in this template * if just in an example.

Open issue Issue: DNV-46 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: Description#24 It is rather brief and would gain a lot by examples. The matter of assigning the location should be covered. Also, the optional characterizations should be mentioned here already.

Open issue Issue: DNV-47 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: Description#24 The 3 numerical items that are instantiated by this template should be named and explained.

Open issue Issue: DNV-48 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: Model diagram#31 It may be benefitial to add names to the 3 Value_with_unit instances. OR Figure 1 should be removed; figure 2 seems to be sufficient.

Open issue Issue: DNV-49 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Check list clause: Model diagram#34 Altitude is supposed to be optional, but not dashed.

Open issue Issue: DNV-50 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Model diagram#36 That the required class-names are not included in the boxes seems right, as subclasses are allowed. Here, however, the superclass names are added elsewhere on the diagram. Is that right?

Open issue Issue: DNV-51 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Model diagram#38 Not all blue arrows have attribute names assigned (in figure 1).

Open issue Issue: DNV-52 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Model diagram#39 Not done for the Unit entities.

Open issue Issue: DNV-53 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Model diagram#41 Global_location_representation inherits from Location_representation, but no attributes. This is not shown here * right or not right?

Open issue Issue: DNV-54 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Model diagram#48 Not done for the abbreviated template.

Open issue Issue: DNV-55 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Model diagram#49 The name of the class library should be an input parameter; currently it is a constant in the template

Open issue Issue: DNV-56 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Input parameters#51 Several of the descriptions are not specific to the parameter; just copy/paste without adaption. Descriptions like "The class name of the corresponding to the altitude units " do not make sense.

Open issue Issue: DNV-57 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Input parameters#54 The referenced concepts are TYPEs, not ENTITYs.

Open issue Issue: DNV-58 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Reference parameters#57 Shouldn't the definition of the type be consistent with how it is defined in the input parameter section. I would have expected the following: organization(Type='ENTITY(Global_location_representation)')).

Open issue Issue: DNV-59 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Instantiation path#62 RDL path should be a string, should it not? Same with class names.

Open issue Issue: DNV-60 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Instantiation path#63 The statement representing_value_with_unit.item does not seem to match the specification of the representing_value_with_unit template; there is no reference parameter of name item!

Open issue Issue: DNV-61 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Instance diagrams#67 There is an XML error T7 below the textual representation.

Open issue Issue: DNV-62 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Instance diagrams#70 No such examples used here ... but it would be useful to see how this template can be referenced.

Open issue Issue: DNV-63 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Instance diagrams#73 urn:plcs:rdl:std is used instead.

Open issue Issue: DNV-64 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Instance diagrams#75 No bold here.

Open issue Issue: DNV-65 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Instance diagrams#76 No dashed border lines around the altitude template.

Open issue Issue: DNV-66 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Instance diagrams#80 The reference parameter ^item is used in connection with representing_value_with_unit ... whereas the definition of this template only specifies ^value as reference parameter.

Open issue Issue: DNV-67 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Instance diagrams#84 No bold here.

Open issue Issue: DNV-68 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Characterization#90 No bold in there. Aggregates start with [0], not [1]. Items included as examples only are not greyed out.

Open issue Issue: DNV-69 by , (2007-8-17) minor_technical issue
Resolution: Accept. Status: open

Template: representing_geographical_location Check list clause: Characterization#91 The XML shows an error T7 ... .