A.7 XHTML Mobile Profile
26.2463GPP3GPP SMIL language profileRelease 17Transparent end-to-end Packet-switched Streaming Service (PSS)TS
When rendering texts in a SMIL presentation, authors are able to use XHTML Mobile Profile [47] that contains thirteen modules. However, some of the modules include non-text information. When referring to an XHTML Mobile Profile document from a SMIL document, authors should use only the required XHTML Host Language modules : Structure Module, Text Module, Hypertext Module and List Module. The use of the Image Module, in particular, should not be used. Images and other non-text contents should be included in the SMIL document.
NOTE: An XHTML file including a module which is not part of the XHTML Host Language modules may not be shown as intended. Also, an XHTML file which uses elements or attributes from the required XHTML Host Language modules and which uses elements or attributes that are not included in XHTML Basic Profile [28], may not render correctly on legacy handsets which implement only XHTML Basic. These are:
– The start attribute on the ‘ol’ element in the List module
– The value attribute on the ‘li’ element in the List module
– The ‘b’ element in the Presentation module
– The ‘big’ element in the Presentation module
– The ‘hr’ element in the Presentation module
– The ‘i’ element in the Presentation module
– The ‘small’ element in the Presentation module
Annex B (normative):
Additional specification on the
systemComponent Test Attribute
B.1 General
This annex includes additional normative specification on the encoding of the SMIL 2.0 BasicContentControl Module systemComponent test attribute value. The purpose is to allow a SMIL presentation to test if a 3GPP SMIL player supports a media type.
B.2 Definition of Attribute Encoding
To test support for a certain media type the value of the systemComponent attribute must be encoded as a URI as follows:
systemComponentAttrValue –> "ContentType:" mimeMediaTypeName "/" mimeSubTypeName options?
options –> "?" parameters
where
– "ContentType:" is a static pre-fix that must always be encoded,
– ‘mimeMediaTypeName‘ and ‘mimeSubtypeName‘ are a MIME type and subtype. These two must be encoded and must be separated by a dash ( "/" ), and
– encoding ‘options’ is optional.
– ‘parameters‘ stands for any parameter to the MIME type that can optionally be encoded. When encoded, parameters must be separated from the MIME type and sub-type names by a question mark ( "?" ).
For all content formats mandated by [3] the ‘mime-media-type-name‘ and ‘mime-subtype-name‘ must be encoded as defined in section 5.4 of [3]. For all other content types established MIME types must be used.
NOTE: This specification intentionally does not define a format for parameters.
B.3 Behaviour of a 3GPP SMIL Player
For any systemComponent test attribute value that is prefixed with the string ‘ContentType:’ a 3GPP SMIL player is required to evaluate the systemComponent test attribute based on ‘mimeMediaTypeName‘ and ‘mimeSubtypeName‘ as follows.
– evaluation of the test attribute returns true whenever the 3GPP SMIL player supports rendering media content of this MIME type,
– in all other cases the evaluation returns false.
A 3GPP SMIL player must be able to ignore any encoded parameters for performing this evaluation. A 3GPP SMIL player is allowed but not required to also include parameters into the evaluation.
NOTE: The specification on parameters makes a 3GPP SMIL player forward compatible with any future version of the specification that will possibly define how to encode MIME type parameters and how to evaluate the systemComponent test attribute when parameters are included into its value.
NOTE: This specification intentionally leaves it open how those systemComponent test attribute values evaluate that are not prefixed with the string "ContentType:". Again, this makes a 3GPP SMIL player forward compatible with any future version of the specification that will possible define other URI schemes for the systemComponent attribute value.
Annex C (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2004-06 |
24 |
SP-040345 |
Approved at 3GPP TSG SA#24 |
2.0.0 |
6.0.0 |
||
|
2004-09 |
33 |
SP-060596 |
0001 |
2 |
Fix to the SMIL timing modules and to the references |
6.0.0 |
6.1.0 |
|
2007-06 |
36 |
Version for Release 7 |
6.1.0 |
7.0.0 |
|||
|
2008-12 |
42 |
Version for Release 8 |
7.0.0 |
8.0.0 |
|||
|
2009-12 |
46 |
Version for Release 9 |
8.0.0 |
9.0.0 |
|||
|
2011-03 |
51 |
Version for Release 10 |
9.0.0 |
10.0.0 |
|||
|
2012-09 |
57 |
Version for Release 11 |
10.0.0 |
11.0.0 |
|||
|
2014-09 |
65 |
Version for Release 12 |
11.0.0 |
12.0.0 |
|||
|
2015-12 |
70 |
Version for Release 13 |
12.0.0 |
13.0.0 |
|||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
75 |
Version for Release 14 |
14.0.0 |
||||
|
2018-06 |
80 |
Version for Release 15 |
15.0.0 |
||||
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2022-04 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |