Skip to content
This repository was archived by the owner on Oct 2, 2019. It is now read-only.

Commit ec3ff54

Browse files
author
Eduardo Fullea
committed
fixing timestamp descriptions
1 parent a01acde commit ec3ff54

File tree

1 file changed

+24
-12
lines changed

1 file changed

+24
-12
lines changed

index.html

Lines changed: 24 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -142,7 +142,9 @@ <h2><a>Navigator</a> Interface</h2>
142142

143143
<!------------------------ Interface MessagingManager ------------------------------->
144144
<section>
145-
<h2><a>MessagingManager</a> Interface</h2> <p>The <a>MessagingManager</a> interface
145+
<h2><a>MessagingManager</a> Interface</h2>
146+
147+
<p>The <a>MessagingManager</a> interface
146148
represents the initial entry point for getting access to the mobile messaging
147149
services, i.e. SMS and MMS.
148150

@@ -466,10 +468,11 @@ <h2><a>SmsManager</a> Interface</h2>
466468
(e.g. 'sms_sim1').</dd>
467469

468470
<dt> SmsSegmentInfo getSegmentInfoForText ()</dt>
469-
<dd>This method returns an SmsSegmentInfo object including information on
470-
the number of concatenated SMS segments needed to send the text in the
471-
<code>text</code> parameter, the number of characters available per segment
472-
and the maximum number of available characters in the last segment.
471+
<dd>This method returns an <code>SmsSegmentInfo</code> object including
472+
information on the number of concatenated SMS segments needed to send the
473+
text in the <code>text</code> parameter, the number of characters available
474+
per segment and the maximum number of available characters in the last
475+
segment.
473476
<dl class='parameters'>
474477
<dt>DOMString text</dt>
475478
<dd>
@@ -619,7 +622,9 @@ <h3>Steps</h3>
619622
<ol>
620623
<li>Set the <code>state</code> of the <code>SmsMessage</code> to 'sent'.
621624
<li>Set the <code>timestamp</code> of the <code>SmsMessage</code> to the
622-
timestamp when the SMS message was actually sent.
625+
timestamp when the SMS message reached the Short Message Center, i.e. the
626+
value of the TP-Service-Centre-Time-Stamp (TP-SCTS) parameter returned in
627+
the SMS-SUBMIT-REPORT Protocol Data Unit.
623628
<li>Set the <code>readyState</code> of the <code>MessagingRequest</code>
624629
object to 'done'.
625630
<li>Set the <code>result</code> of the <code>MessagingRequest</code>
@@ -675,8 +680,9 @@ <h3>Steps</h3>
675680
sender of the SMS message, i.e. the value of the TP Originating Address
676681
(TP-OA) field of the SMS message.
677682
<li>Set the <code>timestamp</code> of the <code>SmsMessage</code> to the
678-
timestamp of the SMS message, i.e. the value if the TP Service Centre
679-
Time Stamp (TP-SCTS) field of the SMS message.
683+
timestamp of the SMS message, i.e. the value of the
684+
TP-Service-Centre-Time-Stamp (TP-SCTS) parameter received in the SMS
685+
DELIVER Protocol Data Unit.
680686
<li>Set the <code>read</code> of the <code>SmsMessage</code> to 'false'.
681687
<li>Set the <code>to</code> of the <code>SmsMessage</code> to the
682688
recipient of the SMS message, i.e. the value of the TP Destination
@@ -1039,7 +1045,8 @@ <h3>Steps</h3>
10391045
<ol>
10401046
<li>Set the <code>state</code> of the <code>MmsMessage</code> to 'sent'.
10411047
<li>Set the <code>timestamp</code> of the <code>MmsMessage</code> to the
1042-
timestamp when the MMS message was actually sent.
1048+
timestamp when the MMS message was sent, i.e. the date when the M-Send.req
1049+
Protocol Data Unit was send from the MMS Client to the MMS Server.
10431050
<li>Set the <code>readyState</code> of the <code>MessagingRequest</code>
10441051
object to 'done'.
10451052
<li>Set the <code>result</code> of the <code>MessagingRequest</code>
@@ -1078,6 +1085,10 @@ <h3>Steps</h3>
10781085
<ol>
10791086
<li>Set the <code>from</code> of the <code>MmsMessage</code> to the
10801087
value of the 'From' field of the MMS notification, if present.
1088+
<li>Set the <code>timestamp</code> of the <code>MmsMessage</code> to
1089+
the timestamp of the binary SMS message used to transport the MMS
1090+
notification, i.e. the value of the TP-Service-Centre-Time-Stamp
1091+
(TP-SCTS) parameter received in the SMS-DELIVER Protocol Data Unit.
10811092
<li>Add a new element in the <code>to</code> array of the
10821093
<code>MmsMessage</code> for each of recipients in the 'To' field of the
10831094
MMS notification, if present.
@@ -1099,7 +1110,7 @@ <h3>Steps</h3>
10991110
Once the MMS has been fetched continue with following steps.
11001111
<li>Run the <dfn id="dfn-fill-mms-message">steps for filling the
11011112
<code>MmsMessage</code> object with the data contained in the MMS
1102-
message</dfn>.
1113+
message enclosed in the M-Retrieve.conf Protocol Data Unit</dfn>.
11031114
<ol>
11041115
<li>Set the <code>from</code> of the <code>MmsMessage</code> to the
11051116
value of the 'From' field of the MMS message.
@@ -1415,8 +1426,9 @@ <h2><a>SmsMessage</a> Interface</h2>
14151426
(TP-OA) of the SMS message.</dd>
14161427

14171428
<dt>readonly attribute Date timestamp</dt>
1418-
<dd>MUST return the time the message was sent at, i.e. the TP Service Centre
1419-
Time Stamp (TP-SCTS) of the SMS message.</dd>
1429+
<dd>MUST return the time the message reached the Short Message Center,
1430+
indicated in the TP-Service-Centre-Time-Stamp (TP-SCTS) parameter of the SMS
1431+
message.</dd>
14201432

14211433
<dt>readonly attribute boolean read</dt>
14221434
<dd>MUST return 'true' if the message has been marked as read, or 'false'

0 commit comments

Comments
 (0)