IEC PAS 62292:2001

IEC/PAS 62292
Edition 1.0
2001-12
Draft SMPTE Engineering Guideline
SMPTE XXX –
Declarative Data Essence
PUBLICLY AVAILABLE SPECIFICATION
INTERNATIONAL Reference number
ELECTROTECHNICAL
IEC/PAS 62292
COMMISSION
IEC/PAS 62292
Edition 1.0
2001-12
Draft SMPTE Engineering Guideline
SMPTE XXX –
Declarative Data Essence
PUBLICLY AVAILABLE SPECIFICATION
INTERNATIONAL Reference number
ELECTROTECHNICAL
IEC/PAS 62292
COMMISSION
INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________
DRAFT SMPTE ENGINEERING GUIDELINE SMPTE XXXX –

DECLARATIVE DATA ESSENCE
FOREWORD
A PAS is a technical specification not fulfilling the requirements for a standard, but made available to the

public and established in an organization operating under given procedures.
IEC-PAS 62292 was submitted by the SMPTE (Society of Motion Picture and Television Engineers) and
has been processed by IEC technical committee 100: Audio, video and multimedia systems and
equipment.
The text of this PAS is based on the This PAS was approved for
following document: publication by the P-members of the
committee concerned as indicated in
the following document:
Draft PAS Report on voting
100/398/PAS 100/426/RVD
Following publication of this PAS, the technical committee concerned will investigate the
possibility of transforming the PAS into an International Standard.
1) The IEC (International Electrotechnical Commission) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of the IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, the IEC publishes International Standards. Their preparation is
entrusted to technical committees; any IEC National Committee interested in the subject dealt with may
participate in this preparatory work. International, governmental and non-governmental organizations liaising with
the IEC also participate in this preparation. The IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of the IEC on technical matters express, as nearly as possible, an
international consensus of opinion on the relevant subjects since each technical committee has representation
from all interested National Committees.
3) The documents produced have the form of recommendations for international use and are published in the form
of standards, technical specifications, technical reports or guides and they are accepted by the National
Committees in that sense.
4) In order to promote international unification, IEC National Committees undertake to apply IEC International
Standards transparently to the maximum extent possible in their national and regional standards. Any divergence
between the IEC Standard and the corresponding national or regional standard shall be clearly indicated in the
latter.
5) The IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with one of its standards.
6) Attention is drawn to the possibility that some of the elements of this PAS may be the subject of patent rights.
The IEC shall not be held responsible for identifying any or all such patent rights.
Page i
Draft SMPTE Engineering Guideline D27.111-2425B

17-October- 2001
Declarative Data Essence
1 Scope
This document provides an overview of the Declarative Data Essence Standards, describes how

the various documents and technical components are related, and provides informative material

useful to the users of these standards.
2 Organization
2.1 Table of contents
1SCOPE.1
2 ORGANIZATION .1
2.1 TABLE OF CONTENTS .1
3 INTRODUCTION .2
4 AUTHORING GUIDELINES .4
4.1 HTML4.4
4.2 STYLE SHEETS AND FONTS.4
4.3 ECMASCRIPT .5
4.4 DOM-0 .5
4.5 URI SCHEMES .5
4.6 UUID .5
5 RECEIVER BEHAVIOR .6
5.1 RECEIVER MODEL .6
5.2 ENHANCEMENT CHARACTERIZATION .6
5.3 STATE MODEL.7

5.3.1 New Enhancement Triggers.8
5.3.2 Triggers for the Current Enhancement.8
5.4 CACHE MANAGEMENT .9
5.4.1 Size.9
5.4.2 Behavior.10
5.5 COOKIES.10
5.6 CSS-1 AND FONTS.11
6 DISTRIBUTION ISSUES .11
7 AD INSERTION SCENARIO DETAILS.11
8 EXAMPLES.13
Declarative Data Essence – Engineering Guideline Page 1 of 20

!"#$%&'()*+*,--./*012345*,--./*64!

EQFNBK+>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA4M
YA4 H
YA7 FNBK+>+9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA4I
YAM >OH0D+*!EGRK+H9*FNBK+>+9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA4V

? 9-96-$*)+%4@''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''!?

E* 6:)%">=@)&":
9:"*(-('(%$*/&51<*56*,'%-2%&2,*="&"*2")"$5<"2*(-*>K39+*@%,"2*5-*':"*B2)%-#"2*9"$")(,(5-
+-:%-#";"-'* F5&1;* ZB9T+F[* ,<"#(6(#%'(5-* \B9T+F]A* * 9:","* %&"* #5$$"#'()"$^* _-5=-* %,
!"#$%&%'()"* !%'%* +,,"-#"* Z!!+[* 2"&()"2* 6&5;* ':"* '"&;(-5$5/^* 2")"$5<"2* (-* ':"* `5(-'
>K39+a+CR*=5&_*651-2*(-*\>K39+Q+CR]A**9:(,*=%,*61&':"&*$%@"$"2*%,*#5-'"-'*$")"$*4*%6'"&
':"*B9T+F*,<"#(6(#%'(5-*65&*b4A8c?*%-2*(-*%-'(#(<%'(5-*56*@5':*$5="&*%-2*:(/:"&*#5-'"-'*$")"$,A
J"-#"?*':"*,:5&':%-2?*b!!+Q4cA
9:"*B9T+F*,<"#(6(#%'(5-*=%,*@&5_"-*(-'5*S*,"<%&%'"*>K39+*25#1;"-',*':%'*#5)"&*':"*5&(/(-%$
B9T+F*,<"#(6(#%'(5-A**9:","*,<"#(6(#%'(5-,*%&"d
!1 \!!+Q4]* >K39+* 3&5<5,"2* >'%-2%&2* MSMK?* b!"#$%&%'()"* !%'%* +,,"-#"?* G5-'"-'
D")"$*4cA
!1 \!EKQ8]*>K39+*3&5<5,"2*>'%-2%&2*MSSK?*b!5#1;"-'*E@`"#'*K52"$*D")"$*8*Z!EKQ8[
%-2*N"$%'"2*E@`"#'*+-)(&5-;"-'cA
!1 \DO!]*>K39+*3&5<5,"2*>'%-2%&2*MIMK?*b9:"*D5#%$*O2"-'(6("&*Z$(2d[*RNO*>#:";"cA
!1 \O3K]* >K39+* 3&5<5,"2* >'%-2%&2* MPVK?* b!"#$%&%'()"* !%'%* +,,"-#"?* O3* K1$'(#%,'
+-#%<,1$%'(5-cA
!1 \RJ993]*>K39+*>'%-2%&2*MSIK?*b!"#$%&%'()"*!%'%*+,,"-#"*Q*R-(2(&"#'(5-%$*J^<"&'"e'
9&%-,<5&'*3&5'5#5$cA
!1 \H9>G]*>K39+*3&5<5,"2*>'%-2%&2*MS4K?*bH9>G*O3*%-2*9&(//"&*C(-2(-/*'5*TCOcA
O-*%22('(5-?*':"&"*(,*%*-"=*3BDa>+GBK*@(-2(-/d

!1 \3BD]*>K39+*!&%6'*>'%-2%&2*eeee?*b3BDa>+GBK*O3*%-2*9&(//"&*C(-2(-/*'5*TCO
ZS7P*D(-"*9"$")(,(5-*>^,'";,[cA
9:"*&"$%'(5-,:(<*56*%$$*V*56*':","*25#1;"-',*#%-*@"*651-2*(-*F(/1&"*MQ4*@"$5=A
!"#$%&%'()"*!%'%*+,,"-#"*.*+-/(-""&(-/*01(2"$(-" 3%/"*7*56*78

And, finally it is worth noting that there is ongoing work (not covered in this document) on

wrappers for this content for carriage in SMPTE KLV. And, there is very early work on a

content level 2.
DDE-1
lid: DOM-0
Wrappers & KLV
UHTTP
Encapsulation*
IPM
SMPTE KLV on MPEG
PAL
MPEG
NTSC Bindings MPEG Bindings
SECAM
Figure 3-1. Relationship of the DDE-1 Standards.
The collection of DDE-1 documents is fully ATVEF compliant, and is collectively known as
“Content Level 1”, or DDE-1. No extensions were designed, and no new functionality was
added. However, a considerable amount of new material was added to more fully specify the
work for the purpose of providing interoperability. Specifically, there was significant additional
work put into the following technology:
• DOM-0
• Triggers (defined in [DDE-1])

• Lid:
The DDE-1 document set is an authoring content standard. As such, it avoided as much as
possible specific receiver behavior. However, expectations of receiver behavior are implied, and
often overtly stated. Some more information on the expected behavior is covered in this
document.
Declarative Data Essence – Engineering Guideline Page 3 of 20

4 Authoring Guidelines
4.1 HTML4
Some operations taken for granted in computer-based browsers that decode HTML

should often be avoided when using DDE-1. In general, anything that would require

extensive use of an input device, such as pull-downs and similar input objects. In addition,

the expectation of scrolling down or to the right to view a page may often result in parts of
the display being unviewable due to limited (or unwilling) user input. It is a good idea to
create pages that are a single screen, and avoid any assumption of input devices, certainly
anything more than can be done on a standard remote control.
Absolute positioning and sizes should be avoided to permit consistent rendering on
displays of varying resolutions. Using pixel coordinates will result in significant undesirable
variations.
DDE-1 does not provide good means to ensure accurate positioning of the HTML
elements with respect to the video. Since the video format can be altered during distribution
from its original format when the DDE-1 was created, this poses interesting registration
challenges at the decoder. For example, it can be as gross a change as a conversion from
16x9 to 4x3 letterbox. Authors are cautioned about making any assumptions about the
registration between the video and the DDE-1 content at the decoder when the distribution is
not well known. Authors should try to stay within the safe area and safe titling areas as
defined in SMPTE RP26.3 [SAFE].
Authors are referred to the general interoperability warnings found within the HTML
specification [HTML].
4.2 Style Sheets and Fonts
There is no default style sheet in DDE-1. And, there is no requirement that a receiver
choose any particular set of styles. Thus, without authoring and sending a style sheet along
with the HTML content, the variation in rendering across manufacturers will be significant
and perhaps undesirable. Authors are encouraged to make explicit use of CSS style sheets

in order to control the display of their content.
As in HTML for positioning, percent sizes should be used wherever possible to provide
display independence.
DDE-1 does not support downloadable fonts, however, there are two default fonts with
specific sizes required to be supported. Authors are encouraged to make use of these fonts
for better display control. The fonts sizes are specified in pixels, so there will be some
amount of display variation if specific sizes are chosen.
Declarative Data Essence – Engineering Guideline Page 4 of 20

4.3 ECMAScript
Authors should avoid using eval() that results in dynamically generated HTML.  Doing

this makes transcoding of the content computationally impossible, and thus may affect the

quality in future generation enhancement systems.

4.4 DOM-0
Authors should avoid using document.write() with arguments other than constants.
Doing this makes transcoding of the content computationally impossible, and thu
...