Capability (C014):— messaging Date: 2007/06/22 12:22:09
Revision: 1.23
CoverContentsIntro.Overview Info. modelTemplatesCapabilitiesRef. dataIssues

Issue raised against: messaging

GENERAL issues

Open issue Issue: SMB-2 by Sean Barker (06-02-14) minor_technical issue
Resolution: Accept. Status: open

SEDS for use of select on Content item will require update to the capability.
Comment: (Rob Bodington 07-01-31)
This has been raised as SEDS #1135 roblem Description: The use of message always requires the use of the escape mechanism to reference items, whereas, in some cases an AP may wish to restrict the usage to particular entities. Suggest: The entity Content_item should be subtyped (oneof) to Content_item_selected and Content_item_reference Content_item would become an abstract type, and the current attributes migrated to Onservation_item_reference Content_item_selected would have a single attribute pointing to an extensible select. Additional Notes: An AP could chose to define the set of things an observation is restricted to by a rule allowing only the Content_item_select subtype and extending the associated select.
Comment: (Rob Bodington 07-01-31)
The model diagram in the template has been modified to show Content_item_selected. The EXPRESS needs to be modified and the SEDS addressed.

GENERAL issues

Closed issue Issue: RBN-1 by Rob Bodington (04-01-16) minor_technical issue
Resolution: Accept. Status: closed

The capability should describes how the message supports the exchange of DEX data. The "Other DEX level commitments" should be defined within the DEX
Comment: (Sean Barker 2004-03-08)
Revised Messaging now satisfies the requirement.

Closed issue Issue: PS-1 by Phil Spiby (04-03-26) minor_technical issue
Resolution: Accept. Status: closed

The acknowledgement attribute of envelope should follow the concepts specified in "Delivery Status Notification" for SMTP and X.400. We should not be creating new concepts here but using those developed over a number of years in the e-mail standards community.
Comment: (Sean Barker 2004-6-10)
Additional section added on semantics of Acknowledge.

Closed issue Issue: PS-2 by Phil Spiby (04-03-26) minor_technical issue
Resolution: Accept. Status: closed

The acknowledgement attribute of envelope should either be an enumeration or be specified by reference data.
Comment: (Sean Barker 2004-4-26)
Should be raised as issue against Envelope module, where categories should be an enumeration.

Closed issue Issue: PS-3 by Phil Spiby (04-03-26) minor_technical issue
Resolution: Accept. Status: closed

The mapping of the acknowledgement attribute of envelope should include the "contents corrupt" value also.
Comment: (Sean Barker 2004-4-26)
Issue raised against Envelope Module

Closed issue Issue: PS-4 by Phil Spiby (04-03-26) minor_technical issue
Resolution: Accept. Status: closed

In Figure 2 and the associated instance data the value for the Acknowledge attribute of instance #1 should be "Ask message arrival" not "Ack message arrival".
Comment: (Sean Barker 2004-4-26)
Corrected

Closed issue Issue: PS-5 by Phil Spiby (04-03-26) minor_technical issue
Resolution: Accept. Status: closed

In figure 3 and the associated instance data the recipient of envelope #2 should be the sender of envelope #1, i.e. #8 not #14. As the instance set currently stands the recipient of the first envelope sends a message to himself saying that he recevied the first message!
Comment: (Sean Barker 2004-4-26)
Corrected

Closed issue Issue: SMB-1 by Sean Barker (04-07-08) minor_technical issue
Resolution: Accept. Status: closed

Message should also classify against scheme and version.
Comment: (Sean Barker 2006-2-24)
Done