representing_message

Template:— representing_message (rep_msg)

Date: 2010/02/26 01:54:41
Revision: 1.32

Cover Contents Description Model diags.Input params.Ref. params.Instantiation path Instance diags.Characterizations Issues

Issue raised against: representing_message

GENERAL issues

Issue: SBH-2 by Brad Harris (2007-07-27) minor_technical issue
Resolution: Accept. Status: closed

Subsequent to the addition of the content_item_select entity type and the associated message_content_item select type, the assigning_reference_data characterization of content_item (#14 Content item type) looks as though it ought to be removed.

Comment: (Mike Ward 2008-01-14)
Content item type removed.

Issue: SBH-1 by Brad Harris (2007-07-26) minor_technical issue
Resolution: Accept. Status: closed

Subsequent to the addition of the assigning_security_classification characterization (#11 Security classification), the assigning_reference_data characterization (#13 Message security classification) looks as though it ought to be removed.

Comment: (Mike Ward 2008-01-14)
Message security classification removed.

Issue: RBN-1 by Rob Bodington (2007-01-31) minor_technical issue
Resolution: Accept. Status: closed

SEDS #1135 proposes to create sub type content_item_selected

Comment: (Rob Bodington 2007-10-15)
Updated path

Issue: RBN-2 by Rob Bodington (2007-01-31) minor_technical issue
Resolution: Accept. Status: closed

The characterization should include assigning_security_classification.

Comment: (Mike Ward 2008-01-14)
assigning_security_classification added.

Comment: (Rob Bodington 2007-03-21)
assigning_security_classification has been added

Issue: RBN-3 by Rob Bodington (2007-01-31) minor_technical issue
Resolution: Accept. Status: closed

The template shows the use of assigning_supported_justification - not sure that this is necessary

Comment: (Rob Bodington 2007-01-31)
Removed from model diagram

Issue: RBN-4 by Rob Bodington (2007-01-31) minor_technical issue
Resolution: Accept. Status: closed

The path and parameters for assigigning person and organization are missing

Comment: (Trisha Rollo 2007-06-13)
path and parameters not added, although amendment done to indicate that either assigning_person_in_organization or assigning_organization is required in the template.

Issue: RBN-5 by Rob Bodington (2007-01-31) minor_technical issue
Resolution: Accept. Status: closed

The characterizations in the model diagram are missing from the template

Comment: (Trisha Rollo 2007-06-14)
characterizations added

Issue: RBN-6 by Rob Bodington (2007-01-31) minor_technical issue
Resolution: Accept. Status: closed

There is no instance diagram for the template

Comment: (Trisha Rollo 2007-06-14)
instance diagram added

Issue: RBN-7 by Rob Bodington (2007-03-21) minor_technical issue
Resolution: Accept. Status: closed

The EXPRESS-g diagram and the content parameter shows the select Message_content_select. It should be message_content_item

Comment: (Rob Bodington 2007-03-21)
Corrected parameter and EXPRESS-G diagram Note - the EXPRESS is: dexlib/docs/ap239/ap239_arm_lf.exp

Issue: PBM-1 by Peter Bergström (2007-01-31) minor_technical issue
Resolution: Accept. Status: closed

In order to process OWL correctly, the reference data library that is the most specialized rdl must be identified as the context ontology. The context ontology must include all other rdl's in an exchange file. This should be achieved by classifying the most specialized External_data_library as the "Context_ontology".

Figure 1 — Possible solution

This template should describe how to achieve this, both in text and using an instance example. An OWL class "Context_ontology" has to be created. Possibly, a specific template has to be developed for this.

Comment: (Leif Gyllstrom 2007-04-23)
This issue has been moved from the template 'assigning_reference_data', since the context ontology should only be refered to once within a message.

Comment: (Mike Ward 2008-01-14)
This issue requires further discussion.

Comment: (Rob Bodington 08-03-06)
This issue has been deferred

Issue: TRO-1 by Trisha Rollo (2007-16-14) minor_technical issue
Resolution: Accept. Status: closed

add "Date_message_sent" as valid type to urn:plcs:rdl:std

Comment: (Mike Ward 2007-12-19)
"Date_message_sent" added to plcs-proposed.owl

Issue: RBN-8 by Rob Bodington (2007-10-04) minor_technical issue
Resolution: Accept. Status: closed

The path shows: Message.contains -> Content_item_select it should be: Message.contains -> Content_item_selected

Comment: (Rob Bodington 2007-10-04)
Implemented

Issue: RBN-9 by Rob Bodington (2007-11-07) minor_technical issue
Resolution: Accept. Status: closed

The path does not show Content_item_selected.contents -> @content

Comment: (Rob Bodington 2007-11-07)
Corrected

Issue: RBN-10 by Rob Bodington (2007-11-07) major_technical issue
Resolution: Accept. Status: closed

"Figure 3 Entities instantiated by representing_message template" Shows a content_item - it should be a Content_item_selected The example should also show the contents of the message. For example - assign Content_item_selected.contents to Representing_work_done to show a message reporting on work done

Comment: (Mike Ward 2007-12-19)
Content_item replaced by Content_item_selected in diagram.

Issue: DNV-53 by Tore Hartvigsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\TORHAR_template_issues_temp.xls Template: representing_message Check list clause: 10 Error message displayed : Ref. to unrecognized CLASS

Comment: (Mike Ward 2007-12-19)
"Date_message_sent" added to plcs-proposed.owl

Issue: DNV-54 by Tore Hartvigsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Comment: (Mike Ward 2008-01-14)
Cover page now has no errors.

Issue: DNV-55 by Tore Hartvigsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Comment: (Mike Ward 2008-01-14)
Cover page now has no errors.

Issue: DNV-56 by Tore Hartvigsen, DNV (2007-11-15) editorial issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\TORHAR_template_issues_temp.xls Template: representing_message Check list clause: 20 status not 'end modelling'

Comment: (Mike Ward 2007-12-19)
Status has been corrected.

Issue: DNV-57 by Tore Hartvigsen, DNV (2007-11-15) major_technical issue
Resolution: Accept. Status: closed

Comment: (Mike Ward 2007-12-19)
Content_item_selected and message_content_item are defined in the extended dexlib version of the AP239 EXPRESS schema.

Issue: DNV-58 by Tore Hartvigsen, DNV (2007-11-15) major_technical issue
Resolution: Accept. Status: closed

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\checklists_12_07\TORHAR_template_issues_temp.xls Template: representing_message Check list clause: 22 message_content_item not a PLCS SELECT. See item #22

Comment: (Mike Ward 2007-12-19)
Content_item_selected and message_content_item are defined in the extended dexlib version of the AP239 EXPRESS schema.

Issue: RBN-11 by Rob Bodington (2007-11-18) minor_technical issue
Resolution: Accept. Status: closed

The message currently only allows there to be ONE content item. Content_item_selected.contents should be an aggregate.

Comment: (Rob Bodington 2007-11-19)
The Message.contains attribute is an aggregate. This means that if there are multiple items in the messages, there should be multiple instantiations of the entity Content_item_selected. The Content_item_selected.contents should not be an aggregate otherwise we would have two ways in which a message could have multiple items. Either by multiple Content_item_selected or by a single Content_item_selected with the Content_item_selected.contents populated with instances. The Express-g should be modified to show that the Content_item should not be used, instead use Content_item_selected. In effect make Content_item an abstract supertype. This should also be documented a restriction in the text. The text and diagram should explain that if the message contains multiple items, then there are multiple instances of Content_item_selected.

Comment: (Mike Ward 2007-12-19)
Diagrams and text revised.

Issue: RBN-12 by Rob Bodington (2007-11-19) minor_technical issue
Resolution: Accept. Status: closed

Content_item_selected is a subtype of Content_item - the Express-g shows the opposite.

Comment: (Mike Ward 2007-12-19)
Diagram modified.

Issue: RBN-13 by Rob Bodington (08-01-03) minor_technical issue
Resolution: Accept. Status: closed

The description of ap239_id_class_name does not make sense. "The name of the class being used to classify the message (Message) of the message. This identifies the version of AP239 to which the data in the message conforms."

Comment: (Rob Bodington 08-01-03)
Improved definition

Issue: RBN-14 by Rob Bodington (08-01-03) minor_technical issue
Resolution: Accept. Status: closed

The definitions of the times/date parameters do not make sense.

Comment: (Rob Bodington 08-01-03)
Improved defnitions

Issue: RBN-15 by Rob Bodington (08-01-10) minor_technical issue
Resolution: Accept. Status: closed

The path should include: Content_item_selected.item_identifier = '/IGNORE' Content_item_selected.item_type = '/IGNORE' Content_item_selected.access_comment = '/IGNORE'

Comment: (Rob Bodington 08-01-10)
added

Issue: RBN-16 by Rob Bodington (08-02-15) major_technical issue
Resolution: Accept. Status: closed

When you package up a message, it may not be sent straight away. Hence it is not possible to know what the sent time is. Hence the sent time of the message should be an optional characterization The extract time however, should be mandatory as it indicates when the message was created and the data extract from the sending system

Comment: (Rob Bodington 08-02-15)
Corrected