From 3affa123cd41df0ab70b9a3e48773e1ee1c7ff41 Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Mon, 21 Oct 2013 17:17:51 +0200 Subject: [PATCH 01/10] adding support for read status in MmsDeliveryInfo --- index.html | 46 +++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 41 insertions(+), 5 deletions(-) diff --git a/index.html b/index.html index eb329f2..4d042c5 100644 --- a/index.html +++ b/index.html @@ -1596,19 +1596,30 @@

MmsAttachment Dictionary

MmsDeliveryInfo Dictionary

-
DeliveryStatus deliveryStatus
-
- The delivery status of the MMS message to a specific recipient. -
DOMString recipient
The recipient of the MMS to which the delivery status is related.
+
DeliveryStatus deliveryStatus
+
+ The delivery status of the MMS message to a specific recipient. +
Date deliveryTimestamp
The time the message was delivered to the recipient, i.e. the 'Date' field in the M-Delivery.ind Protocol Data Unit [[!MMS13]]. It is not provided if there is no positive knowledge about the delivery of the - message.
+ message. + +
ReadStatus readStatus
+
+ The read status of the MMS message to a specific recipient. +
+
Date readTimestamp
+
The time the message was read by the recipient, i.e. the 'Date' + field in the M-Read-Orig.ind Protocol Data Unit [[!MMS13]]. It is not + provided if there is no positive knowledge about the delivery of the + message. +
@@ -2031,6 +2042,31 @@

Enumerations

+

The attibute readStatus can have the following values: +

+
success
+
+ The message has been read by the recipient. +
+ +
pending
+
+ There is no positive knowledge that the message has been read by + the recipient. +
+ +
error
+
+ The delivery of the message has failed. +
+ +
not-applicable
+
+ The read status is not applicable either because a read report has + not been requested or because the message is an inbound message +
+
+

The MMS fetch mode can have the following values:

automatic
From 423157e105a1da9287390808eb1354636110d1b1 Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Mon, 21 Oct 2013 17:27:02 +0200 Subject: [PATCH 02/10] adding Interface ReadReport --- index.html | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/index.html b/index.html index 4d042c5..7b93a7c 100644 --- a/index.html +++ b/index.html @@ -1776,6 +1776,42 @@

DeliveryReport Interface

+ +
+

ReadReport Interface

+

The ReadReport interface represents a system message related to + a read report of a sent MMS message. This event is originated from the system + and will start the application if it is not currently running. + +

The application that consumes this API MAY set a message handler for the + ReadReport system message to listen for when a system + message related to a received read report is fired. + +

+
readonly attribute DOMString serviceID
+
MUST return the identifier of the service used to send the message to + which this read report is related.
+
readonly attribute DOMString messageID
+
MUST return the identifier of the message to which this read + report is related.
+
readonly attribute DOMString[] recipients
+
MUST return an array contining the addresses of the subset of the + original recipients of the message to which this read report is + related. As read reports related to just part of the recipients of the + MMS message are possible, this array may not contain the full list of + recipients to which the MMS message was sent. +
+
readonly attribute Date[]? readTimestamps
+
MUST return an array containing the read dates by each of the + recipients to which this read report event relates. Each element in the + array refers to the recipient in the same position of the + recipients array. +
+
+
+ +

MessagingEvent Interface

From 326d1a0faeeeaf119cc7633f4f4a8bb95f29738b Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Mon, 21 Oct 2013 17:29:58 +0200 Subject: [PATCH 03/10] adding Interface ReadReportEvent --- index.html | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/index.html b/index.html index 7b93a7c..e0b3d68 100644 --- a/index.html +++ b/index.html @@ -1859,6 +1859,36 @@

DeliveryReportEvent Interface

+ +
+

ReadReportEvent Interface

+

The ReadReportEvent interface represents events related + to a read report of a sent message. +

+
readonly attribute DOMString serviceID
+
MUST return the identifier of the service used to send the message to + which this read report event is related.
+
readonly attribute DOMString messageID
+
MUST return the identifier of the message to which this read + report event is related.
+
readonly attribute DOMString[] recipients
+
MUST return an array contining the addresses of the subset of the + original recipients of the message to which this read report event is + related. As read reports related to just part of the recipients of the + MMS message are possible, this array may not contain the full list of + recipients to which the MMS message was sent. +
+
readonly attribute Date[]? readTimestamps
+
MUST return an array containing the read dates for each of the + recipients to which this read report event relates. Each element in the + array refers to the recipient in the same position of the + recipients array. +
+
+
+ +

ServiceChangeEvent Interface

From c4344ad42e06e2336d7cf184aaaee5d807e228aa Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Mon, 21 Oct 2013 17:50:02 +0200 Subject: [PATCH 04/10] MMS read report procedures --- index.html | 119 +++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 101 insertions(+), 18 deletions(-) diff --git a/index.html b/index.html index e0b3d68..e23c493 100644 --- a/index.html +++ b/index.html @@ -557,9 +557,9 @@

SmsManager Interface

report is received on this messaging service manager.
- attribute EventHandler ondeliveryfailure + attribute EventHandler ondeliveryerror
-
Handles the deliveryfailure event of type +
Handles the deliveryerror event of type DeliveryReportEvent, fired when a new failure delivery report is received on this messaging service manager.
@@ -722,7 +722,7 @@

Steps

DT) parameter included in the SMS-STATUS-REPORT Protocol Data Unit [[!GSM-SMS]].
  • Queue a task to fire an event named - deliverysuccess or deliveryfailure respectively if the + deliverysuccess or deliveryerror respectively if the delivery was successfull or not, with
    1. the messageID attribute set to the @@ -736,7 +736,7 @@

      Steps

  • Queue a task to fire a system message of type DeliveryReportnamed deliverysuccess or - deliveryfailure respectively if the delivery was successfull or + deliveryerror respectively if the delivery was successfull or not, with
    1. the messageID attribute set to the @@ -809,8 +809,8 @@

      Event handlers

      handles successful delivery reports - ondeliveryfailure - deliveryfailure + ondeliveryerror + deliveryerror DeliveryReportEvent handles failure delivery reports @@ -976,12 +976,26 @@

      MmsManager Interface

      report is received on this messaging service manager.
      - attribute EventHandler ondeliveryfailure + attribute EventHandler ondeliveryerror
      -
      Handles the deliveryfailure event of type +
      Handles the deliveryerror event of type DeliveryReportEvent, fired when a new failure delivery report is received on this messaging service manager.
      +
      + attribute EventHandler onreadsuccess +
      +
      Handles the readsuccess event of type + ReadReportEvent, fired when a new succesful read report is + received on this messaging service manager.
      + +
      + attribute EventHandler onreaderror +
      +
      Handles the readerror event of type + ReadReportEvent, fired when a new failure read report is received + on this messaging service manager.
      +
      attribute EventHandler onserviceadded
      @@ -1268,7 +1282,7 @@

      Steps

      value of the X-Mms-Status element in the M-Delivery.ind Protocol Data Unit [[!MMS13]] is 'Retrieved', or
    2. to 'error', in case of failed delivery, i.e. if the value of - the X-Mms-Status element in the the M-Delivery.ind Protocol Data + the X-Mms-Status element in the M-Delivery.ind Protocol Data Unit [[!MMS13]] is 'Expired', 'Rejected' or 'Unreachable'.
  • set its deliveryTimestamp attribute to the delivery @@ -1276,7 +1290,7 @@

    Steps

    [[!MMS13]], in case of successful delivery.
  • Queue a task to fire an event named - deliverysuccess or deliveryfailure respectively if the + deliverysuccess or deliveryerror respectively if the delivery was successfull or not, with
    1. the messageID attribute set to the @@ -1292,8 +1306,8 @@

      Steps

      same position of the recipients array.
  • Queue a task to fire a system message of type - DeliveryReportnamed deliverysuccess or - deliveryfailure respectively if the delivery was successfull or + DeliveryReport named deliverysuccess or + deliveryerror respectively if the delivery was successfull or not, with
    1. the messageID attribute set to the @@ -1310,6 +1324,63 @@

      Steps

    +

    Upon a read report of a previously sent MMS message being received, the + user agent MUST +

      +
    1. Let mmsMessage be the instance of MmsMessage + to which this read report is related. +
    2. For each of the items in the deliveryInfo array + attribute of mmsMessage whose recipient + attribute matches one of the recipients of the MMS to which the read + report is related, +
        +
      1. set its readStatus attribute: +
          +
        1. to 'success', in case the message has been read, i.e. if the + value of the X-Mms-Read-Status element in the M-Read-Orig.ind + Protocol Data Unit [[!MMS13]] is 'Read', or +
        2. to 'error', in case the message has been deleted without being + read, i.e. if the value of the X-Mms-Status element in the + M-Read-Orig.ind Protocol Data Unit [[!MMS13]] is 'Deleted without + being read'. +
        +
      2. set its readTimestamp attribute to the read + time, i.e. the 'Date' field in the M-Read-Orig.ind Protocol Data Unit + [[!MMS13]], in case the message has been read. +
      +
    3. Queue a task to fire an event named readsuccess + or readerror respectively if the message has been read or not, with +
        +
      1. the messageID attribute set to the + messageID attribute of mmsMessage, +
      2. the serviceID attribute set to the + serviceID attribute of mmsMessage, +
      3. the recipients attribute set to the subset of the + original recipients of mmsMessageto which this read + report is related, and +
      4. in case the message has been read, with each of the items in the + readTimestamps attribute set to the read time of + the MMS message by the corresponding recipient, i.e. that in the + same position of the recipients array. +
      +
    4. Queue a task to fire a system message of type + ReadReport named readsuccess or + readerror respectively if the message has been read or not, with +
        +
      1. the messageID attribute set to the + messageID attribute of mmsMessage, +
      2. the serviceID attribute set to the + serviceID attribute of mmsMessage, +
      3. the recipients attribute set to the subset of the + original recipients of mmsMessageto which this read + report is related, and +
      4. in case the message has been read, with each of the items in the + readTimestamps attribute set to the read time of + the MMS message by the corresponding recipient, i.e. that in the + same position of the recipients array. +
      +
    +

    The clear method when invoked MUST run the following steps:

      @@ -1369,11 +1440,23 @@

      Event handlers

      handles successful delivery reports - ondeliveryfailure - deliveryfailure + ondeliveryerror + deliveryerror DeliveryReportEvent handles failure delivery reports + + onreadsuccess + readsuccess + ReadReportEvent + handles successful read reports + + + onreaderror + readerror + ReadReportEvent + handles failure read reports + onserviceadded serviceadded @@ -1757,7 +1840,7 @@

      DeliveryReport Interface

      MUST return the identifier of the message to which this delivery report is related.
      readonly attribute DOMString[] recipients
      -
      MUST return an array contining the addresses of the subset of the +
      MUST return an array containing the addresses of the subset of the original recipients of the message to which this delivery report is related. As delivery reports related to just part of the recipients of the MMS message are possible, this array may not contain the full list of @@ -1796,7 +1879,7 @@

      ReadReport Interface

      MUST return the identifier of the message to which this read report is related.
      readonly attribute DOMString[] recipients
      -
      MUST return an array contining the addresses of the subset of the +
      MUST return an array containing the addresses of the subset of the original recipients of the message to which this read report is related. As read reports related to just part of the recipients of the MMS message are possible, this array may not contain the full list of @@ -1840,7 +1923,7 @@

      DeliveryReportEvent Interface

      MUST return the identifier of the message to which this delivery report event is related.
      readonly attribute DOMString[] recipients
      -
      MUST return an array contining the addresses of the subset of the +
      MUST return an array containing the addresses of the subset of the original recipients of the message to which this delivery report event is related. As delivery reports related to just part of the recipients of the MMS message are possible, this array may not contain the full list of @@ -1873,7 +1956,7 @@

      ReadReportEvent Interface

      MUST return the identifier of the message to which this read report event is related.
      readonly attribute DOMString[] recipients
      -
      MUST return an array contining the addresses of the subset of the +
      MUST return an array containing the addresses of the subset of the original recipients of the message to which this read report event is related. As read reports related to just part of the recipients of the MMS message are possible, this array may not contain the full list of From 25639acacf3bbd0eeef615fefd741a1b9f8be270 Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Mon, 21 Oct 2013 17:59:59 +0200 Subject: [PATCH 05/10] adding MmsSendParameters --- index.html | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index e23c493..8f58be7 100644 --- a/index.html +++ b/index.html @@ -921,10 +921,10 @@

      MmsManager Interface

      Content and recipients of the MMS message to be sent.
      -
      optional DOMString serviceID
      +
      optional MmsSendParameters sendParameters
      - Identifier of the service through which the message is requested to - be sent. + Set of parameters related to the submission of the message (e.g. + request of delivery/read report or not).
    • @@ -1477,6 +1477,22 @@

    Event handlers

    + +
    +

    MmsSendParameters Dictionary

    +
    +
    optional DOMString serviceID
    +
    Identifier of the service through which the message is requested to be + sent.
    + +
    boolean requestDeliveryReport
    +
    Flag to indicate whether a delivery report is requested.
    + +
    boolean requestReadReport
    +
    Flag to indicate whether a read report is requested.
    + +
    +
    From d803a4e097d0c6921581e84c705d2ba82d9185d0 Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Tue, 22 Oct 2013 07:25:10 +0200 Subject: [PATCH 06/10] MmsManager.send procedures with MmsSendParameters --- index.html | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/index.html b/index.html index 8f58be7..18215f3 100644 --- a/index.html +++ b/index.html @@ -1037,9 +1037,9 @@

    Steps

  • Set the type of mmsMessage to 'mms'.
  • Set the serviceID of mmsMessage to the identifier of the service used to send the message, i.e. the one passed in - the serviceID parameter, if provided, or otherwise to the - first item in the serviceIDs attribute of the - MmsManager. + the serviceID parameter in MmsSendParameters, if + provided, or otherwise to the first item in the serviceIDs + attribute of the MmsManager.
  • Set the from of mmsMessage to the number of the mobile subscription used to send this MMS message.
  • Set the read of mmsMessage to 'true'. @@ -1062,13 +1062,14 @@

    Steps

    to, cc and bcc parameters (i.e. a single item if the same address has multiple ocurrences across these parameters), with the recipient attribute set to this - recipient's address and the deliveryStatus attribute set to + recipient's address, with the deliveryStatus attribute set to 'pending', if a delivery report has been requested, or 'not-applicable' - otherwise. + otherwise and with the readStatus attribute set to 'pending', + if a read report has been requested, or 'not-applicable' otherwise.
  • Make a request to the system to send an MMS message with the content passed in the content parameter to the number(s) of indicated in the to parameter, using the proper service as described - above. + above and asking for delivery and/or read report if requested.
  • Queue a task to monitor MMS sending progress.
  • If an error occurs run these substeps and terminate these From faf2110c69473b75863b1f47c15d991fb26aca36 Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Tue, 22 Oct 2013 15:25:55 +0200 Subject: [PATCH 07/10] addressing ReSpec warnings --- index.html | 102 +++++++++++++++++++++++++++++------------------------ 1 file changed, 56 insertions(+), 46 deletions(-) diff --git a/index.html b/index.html index 18215f3..632a8ee 100644 --- a/index.html +++ b/index.html @@ -26,7 +26,6 @@ inlineCSS: true, noIDLIn: true, noIDLSorting: true, - extraCSS: ["../ReSpec.js/css/respec.css"], wg: "System Applications Working Group", wgURI: "http://www.w3.org/2012/sysapps/", wgPublicList: "public-sysapps", @@ -582,8 +581,7 @@

    SmsManager Interface

    Steps

    -

    The send method when invoked MUST run the - following steps: +

    The send method when invoked MUST run the following steps:

    1. Let promise be a new Promise object and resolver its associated resolver @@ -637,8 +635,9 @@

      Steps

    2. Invoke resolver's fulfill algorithm with smsMessage as the value argument. -
    3. Queue a task to fire an event named sent - with the message attribute set to smsMessage. +
    4. Queue a task to fire an event named sent with + the message attribute set to smsMessage.
    @@ -701,9 +700,9 @@

    Steps

    'received'.
  • Set the deliveryStatus of smsMessage to 'not-applicable'. -
  • Queue a task to fire an event named - received with the message attribute set - to smsMessage. +
  • Queue a task to fire an event named received + with the message attribute set to smsMessage.
  • Queue a task to fire a system message named received of type ReceivedMessage with the message attribute set to smsMessage. @@ -721,9 +720,11 @@

    Steps

    to the delivery time of the SMS message, i.e. the TP-Discharge-Time (TP DT) parameter included in the SMS-STATUS-REPORT Protocol Data Unit [[!GSM-SMS]]. -
  • Queue a task to fire an event named - deliverysuccess or deliveryerror respectively if the - delivery was successfull or not, with +
  • Queue a task to fire an event named deliverysuccess or deliveryerror + respectively if the delivery was successfull or not, with
    1. the messageID attribute set to the messageID attribute of smsMessage, @@ -735,7 +736,7 @@

      Steps

      to delivery time of such message.
  • Queue a task to fire a system message of type - DeliveryReportnamed deliverysuccess or + DeliveryReportnamed deliverysuccess or deliveryerror respectively if the delivery was successfull or not, with
      @@ -750,8 +751,7 @@

      Steps

    -

    The clear method when invoked MUST run the - following steps: +

    The clear method when invoked MUST run the following steps:

    1. Let promise be a new Promise object and resolver its associated resolver @@ -792,38 +792,42 @@

      Event handlers

      onreceived - received + received MessagingEvent handles received messages onsent - sent + sent MessagingEvent handles sent messages ondeliverysuccess - deliverysuccess + deliverysuccess DeliveryReportEvent handles successful delivery reports ondeliveryerror - deliveryerror + deliveryerror DeliveryReportEvent handles failure delivery reports onserviceadded - serviceadded + serviceadded ServiceChangeEvent handle new messaging services onserviceremoved - serviceremoved + serviceremoved ServiceChangeEvent handle disabled messaging services @@ -1020,8 +1024,7 @@

      MmsManager Interface

      Steps

      -

      The send method when invoked MUST run the - following steps: +

      The send method when invoked MUST run the following steps:

      1. Let promise be a new Promise object and resolver its associated resolver @@ -1092,9 +1095,9 @@

        Steps

      2. Invoke resolver's fulfill algorithm with mmsMessage as the value argument. -
      3. Queue a task to fire an event named - sent with the message attribute set to - mmsMessage. +
      4. Queue a task to fire an event named sent with + the message attribute set to mmsMessage.
    @@ -1205,7 +1208,7 @@

    Steps

    the deliveryStatus attribute set to 'not-applicable'.
  • Queue a task to fire an event named - received with the message attribute set + received with the message attribute set to mmsMessage.
  • Queue a task to fire a system message named received of type ReceivedMessage with the @@ -1290,9 +1293,11 @@

    Steps

    time, i.e. the 'Date' field in the M-Delivery.ind Protocol Data Unit [[!MMS13]], in case of successful delivery. -
  • Queue a task to fire an event named - deliverysuccess or deliveryerror respectively if the - delivery was successfull or not, with +
  • Queue a task to fire an event named deliverysuccess or deliveryerror + respectively if the delivery was successfull or not, with
    1. the messageID attribute set to the messageID attribute of mmsMessage, @@ -1307,8 +1312,8 @@

      Steps

      same position of the recipients array.
  • Queue a task to fire a system message of type - DeliveryReport named deliverysuccess or - deliveryerror respectively if the delivery was successfull or + DeliveryReport named deliverysuccess or + deliveryerror respectively if the delivery was successfull or not, with
    1. the messageID attribute set to the @@ -1349,8 +1354,10 @@

      Steps

      time, i.e. the 'Date' field in the M-Read-Orig.ind Protocol Data Unit [[!MMS13]], in case the message has been read.
    -
  • Queue a task to fire an event named readsuccess - or readerror respectively if the message has been read or not, with +
  • Queue a task to fire an event named readsuccess or + readerror + respectively if the message has been read or not, with
    1. the messageID attribute set to the messageID attribute of mmsMessage, @@ -1365,8 +1372,8 @@

      Steps

      same position of the recipients array.
  • Queue a task to fire a system message of type - ReadReport named readsuccess or - readerror respectively if the message has been read or not, with + ReadReport named readsuccess or + readerror respectively if the message has been read or not, with
    1. the messageID attribute set to the messageID attribute of mmsMessage, @@ -1382,8 +1389,7 @@

      Steps

    -

    The clear method when invoked MUST run the - following steps: +

    The clear method when invoked MUST run the following steps:

    1. Make a request to the system to delete all the messages associated to the messaging service with identifier equal to the serviceID @@ -1424,50 +1430,54 @@

      Event handlers

      onreceived - received + received MessagingEvent handles received messages onsent - sent + sent MessagingEvent handles sent messages ondeliverysuccess - deliverysuccess + deliverysuccess DeliveryReportEvent handles successful delivery reports ondeliveryerror - deliveryerror + deliveryerror DeliveryReportEvent handles failure delivery reports onreadsuccess - readsuccess + readsuccess ReadReportEvent handles successful read reports onreaderror - readerror + readerror ReadReportEvent - handles failure read reports + handles failure read reports onserviceadded - serviceadded + serviceadded ServiceChangeEvent handle new messaging services onserviceremoved - serviceremoved + serviceremoved ServiceChangeEvent handle disabled messaging services From 6f991414d0e8f13b112006913b09d6720076363c Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Tue, 22 Oct 2013 15:48:43 +0200 Subject: [PATCH 08/10] adding readReportRequested attribute in MmsMessage --- index.html | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/index.html b/index.html index 632a8ee..1990b14 100644 --- a/index.html +++ b/index.html @@ -1197,6 +1197,10 @@

      Steps

      Content-Location used to reference this attachment from the SMIL object in the incoming MMS message [[!MMS13]], if present.
    +
  • Set the readReportRequested attribute to 'true' + if the 'X-Mms-Read-Report' field is present in the incoming MMS + message [[!MMS13]] and has the value 'Yes', and to 'false' + otherwise.
  • Set the state of mmsMessage to 'received'. @@ -1636,6 +1640,10 @@

    MmsMessage Interface

    status and, if applicable, the delivery time to each of the recipients of the message. +
    readonly attribute boolean? readReportRequested
    +
    MUST return true in case the originator of a received message requested + a read report and false otherwise. MUST return null for sent messages.
    +
    • From eb1f9bae1e82809652beb23214623cd12ca44c7e Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Wed, 23 Oct 2013 15:03:41 +0200 Subject: [PATCH 09/10] adding sendReadReport in markMessageRead and markConversationRead --- index.html | 28 +++++++++++++++++++++------- 1 file changed, 21 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index 1990b14..0c6677e 100644 --- a/index.html +++ b/index.html @@ -266,10 +266,15 @@

    MessagingManager Interface

    Identifier of the message that is requested to be marked as read or unread -
    optional boolean value = true
    +
    boolean value
    - Indicates whether the message is to be marked as read ('true', - which is the default) or unread ('false') + Indicates whether the message is to be marked as read ('true') or + unread ('false') +
    +
    optional boolean sendReadReport value = false
    +
    + Indicates that, in case a Read Report was requested, it is to be sent + ('true') or not ('false', which is the default)
    @@ -284,10 +289,16 @@

    MessagingManager Interface

    Identifier of the conversation whose messages are requested to be marked as read or unread -
    optional boolean value = true
    +
    boolean value
    Indicates whether the messages in the conversation are to be marked as - read ('true', which is the default) or unread ('false') + read ('true') or unread ('false') +
    +
    optional boolean sendReadReport value = false
    +
    + Indicates that, in case a Read Report was requested for any MMS + message in the conversation, a Read Report is to be sent ('true') or + not ('false', which is the default)
    @@ -419,7 +430,8 @@

    Steps

  • Make a request to the system to mark as read/unread (depending on the value parameter being respectively 'true' or 'false') the message with identifier equal to the messageID parameter - passed in the request. + passed in the request, and to send a Read Report if + sendReadReport is set to 'true'.
  • If an error occurs invoke resolver's reject algorithm with error as the value argument. @@ -442,7 +454,9 @@

    Steps

  • Make a request to the system to mark as read/unread (depending on the value parameter being respectively 'true' or 'false') the messages in the conversation with identifier equal to the - conversationID parameter passed in the request. + conversationID parameter passed in the request, and in case + sendReadReport is set to 'true', to send a Read Report for + each of the MMS messages for which it was requested.
  • If an error occurs invoke resolver's reject algorithm with error as the value argument. From 1147b3bc14e58e29daddf9b595dcbc59beae9487 Mon Sep 17 00:00:00 2001 From: Eduardo Fullea Date: Wed, 23 Oct 2013 15:11:29 +0200 Subject: [PATCH 10/10] fix --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 0c6677e..10851a8 100644 --- a/index.html +++ b/index.html @@ -271,7 +271,7 @@

    MessagingManager Interface

    Indicates whether the message is to be marked as read ('true') or unread ('false') -
    optional boolean sendReadReport value = false
    +
    optional boolean sendReadReport = false
    Indicates that, in case a Read Report was requested, it is to be sent ('true') or not ('false', which is the default) @@ -294,7 +294,7 @@

    MessagingManager Interface

    Indicates whether the messages in the conversation are to be marked as read ('true') or unread ('false')
    -
    optional boolean sendReadReport value = false
    +
    optional boolean sendReadReport = false
    Indicates that, in case a Read Report was requested for any MMS message in the conversation, a Read Report is to be sent ('true') or