Closed Bug 840063 (mms-oma-compliance) Opened 10 years ago Closed 9 years ago

[MMS][User Story] OMA MMS v1.2 compliance

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:-)

RESOLVED FIXED
blocking-b2g -

People

(Reporter: pdol, Assigned: vicamo)

References

Details

(Keywords: feature, Whiteboard: [LOE:L])

UCID: Messages-049

User Story:
As an operator, I can successfuly test the MMS capabilities of the device against the Open Mobile Alliance's Multimedia Messaging Service V1.2 to ensure that the MMS capabilities of the device meet my minimum operating standards (http://www.openmobilealliance.org/Technical/release_program/mms_v1_2.aspx)
Vicamo, can you take this first? thanks
Assignee: nobody → vyang
Whiteboard: [LOE:L]
http://technical.openmobilealliance.org/Technical/release_program/docs/MMS/V1_2-20050429-A/OMA-MMS-CONF-V1_2-20050301-A.pdf

Regarding 7. MM Content Classes. An MMS Client conforming to this document SHALL support MM Content Class Text and at least one other MM Content Class. 

Currently planning to support the minimum Text and Image Basic only.


An MM specified in [MMSCONF] belongs to either MM Content Class Text or MM Content Class Image Basic. In [MMSCONF], support of the speech codecs described in Table 1, SMIL and PIM objects are conditional (respectively under condition of support of audio, presentation part of the multimedia message and PIM). On the other hand, an MMS Client supporting MM Content Class Image Basic has to support presentation of speech codec attachments described in Table 1, SMIL as well as PIM objects in the limits as defined in this section. 

Regarding, SMIL / PIM support, is it needed? Vicamo or Cassie?
Flags: needinfo?(vyang)
Flags: needinfo?(cassie)
(In reply to Joe Cheng [:jcheng] from comment #2)
> http://technical.openmobilealliance.org/Technical/release_program/docs/MMS/
> V1_2-20050429-A/OMA-MMS-CONF-V1_2-20050301-A.pdf
> 
> Regarding, SMIL / PIM support, is it needed? Vicamo or Cassie?

You've already excerpted the answer:

> an MMS Client supporting MM Content Class Image Basic has to support presentation of speech
> codec attachments described in Table 1, SMIL as well as PIM objects in the limits as
> defined in this section. 

So both are mandatory to Image Basic cc.
Flags: needinfo?(vyang)
Blocks: mms-p1
Per partner and release-driver discussions, marking blocking- until all MMS functionality in bug 849867 is complete, allowing it all to be uplifted at once to avoid SMS bustage.
blocking-b2g: leo+ → -
Flags: in-moztrap?
leo+ as this is a part of MMS and part of v1.1 to be included in leo+ queries. No_UPLIFT for now before the whole MMS is completed
blocking-b2g: - → leo+
Whiteboard: [LOE:L] → [LOE:L] [NO_UPLIFT]
Alias: mms-oma-compliance
Whiteboard: [LOE:L] [NO_UPLIFT] → [LOE:L]
Whiteboard: [LOE:L] → [LOE:L][NO_UPLIFT]
Vicamo, this bug is leo+ P1 for MMS, but it's unclear what actual work is required, since all three dependent bugs are blocking-.

Can you help sort out what's actually required to be done for 1.1?
Removing vcard/vcal deps since they're blocking-.
No longer depends on: 849729, 849733
The b2g mms conformance bug 792319 has no blocking+ dependencies, and neither does this, so flipping the flag to blocking-.
blocking-b2g: leo+ → -
Flags: needinfo?(cassie)
Whiteboard: [LOE:L][NO_UPLIFT] → [LOE:L]
Bug 792319 depends on all mandatory items listed on OMA-TS-MMS-CONF-V1_3-20110913-A, which contains features that we're not going to implement in v1.1.  So, instead of depending on a super set, we depend on v1.1 features only here.
Now we can close it.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Flags: in-moztrap?
You need to log in before you can comment on or make changes to this bug.