feature if it recognizes and is capable of transforming the ttp:markerMode
attribute.
A TTML presentation processor supports the #markerMode
feature
if it implements presentation semantic support for the ttp:markerMode
attribute.
A TTML transformation processor supports the
#markerMode-continuous
feature if it recognizes and is capable of
transforming the continuous
value of the ttp:markerMode
attribute.
A TTML presentation processor supports the
#markerMode-continuous
feature if it implements presentation
semantic support for the continuous
value of the ttp:markerMode
attribute.
A TTML transformation processor supports the
#markerMode-discontinuous
feature if it recognizes and is capable
of transforming the discontinuous
value of the ttp:markerMode
attribute.
A TTML presentation processor supports the
#markerMode-discontinuous
feature if it implements presentation
semantic support for the discontinuous
value of the ttp:markerMode
attribute.
A TTML transformation processor supports the #metadata
feature
if it recognizes and is capable of transforming the following vocabulary
defined by 12 Metadata:
A TTML presentation processor supports the #metadata
feature if
it recognizes and is capable of presenting the information expressed by the
same vocabulary enumerated above.
Note:
This specification does not define a standardized form for the presentation of metadata information. The presentation or ability to present metadata information is considered to be implementation dependent.
A TTML transformation processor supports the #nested-div
feature if it recognizes and is capable of transforming nested div
elements.
A TTML presentation processor supports the #nested-div
feature
if it implements presentation semantic support for nested div
elements.
A TTML transformation processor supports the #nested-span
feature if it recognizes and is capable of transforming nested span
elements.
A TTML presentation processor supports the #nested-span
feature
if it implements presentation semantic support for nested span
elements.
A TTML transformation processor supports the #opacity
feature
if it recognizes and is capable of transforming the tts:opacity
attribute.
A TTML presentation processor supports the #opacity
feature if
it (1) implements presentation semantic support for the tts:opacity
attribute and (2) is
capable of displaying or generating an output display signal that distinguishes
between at least eight (8) values of opacity.
A TTML transformation processor supports the #origin
feature if
it recognizes and is capable of transforming the tts:origin
attribute.
A TTML presentation processor supports the #origin
feature if
it implements presentation semantic support for the tts:origin
attribute.
A TTML transformation processor supports the #overflow
feature
if it recognizes and is capable of transforming all defined values of the
tts:overflow
attribute.
A TTML presentation processor supports the #overflow
feature if
it implements presentation semantic support for all defined values of the
tts:overflow
attribute.
A TTML transformation processor supports the #overflow-visible
feature if it recognizes and is capable of transforming the
visible
value of the tts:overflow
attribute.
A TTML presentation processor supports the #overflow-visible
feature if it implements presentation semantic support for the
visible
value of the tts:overflow
attribute.
A TTML transformation processor supports the #padding
feature
if it recognizes and is capable of transforming the tts:padding
attribute.
A TTML presentation processor supports the #padding
feature if
it implements presentation semantic support for the tts:padding
attribute.
A TTML transformation processor supports the #padding-1
feature
if it recognizes and is capable of transforming values of the tts:padding
attribute that consist
of one <length> specification.
A TTML presentation processor supports the #padding-1
feature
if it implements presentation semantic support for values of the tts:padding
attribute that consist
of one <length> specification.
A TTML transformation processor supports the #padding-2
feature
if it recognizes and is capable of transforming values of the tts:padding
attribute that consist
of two <length> specification.
A TTML presentation processor supports the #padding-2
feature
if it implements presentation semantic support for values of the tts:padding
attribute that consist
of two <length> specification.
A TTML transformation processor supports the #padding-3
feature
if it recognizes and is capable of transforming values of the tts:padding
attribute that consist
of three <length> specification.
A TTML presentation processor supports the #padding-3
feature
if it implements presentation semantic support for values of the tts:padding
attribute that consist
of three <length> specification.
A TTML transformation processor supports the #padding-4
feature
if it recognizes and is capable of transforming values of the tts:padding
attribute that consist
of four <length> specification.
A TTML presentation processor supports the #padding-4
feature
if it implements presentation semantic support for values of the tts:padding
attribute that consist
of four <length> specification.
A TTML transformation processor supports the #pixelAspectRatio
feature if it recognizes and is capable of transforming the ttp:pixelAspectRatio
attribute.
A TTML presentation processor supports the #pixelAspectRatio
feature if it implements presentation semantic support for the ttp:pixelAspectRatio
attribute.
A TTML processor supports the #presentation
feature if it (1)
satisfies the generic processor criteria defined by 3.2.1 Generic Processor
Conformance, (2) implements support for the region and line layout
semantics defined by 9.3 Region Layout
and Presentation and 9.4 Line
Layout, respectively, and (3) implements presentation semantics for the
following features:
In addition, a TTML processor that supports the #presentation
feature should satisfy the user agent accessibility guidelines specified by
[UAAG].
A TTML transformation processor supports the #profile
feature
if it recognizes and is capable of transforming the ttp:profile
attribute on the
tt
element and
transforming the following vocabulary defined by 6.1 Parameter Element
Vocabulary:
A TTML presentation processor supports the #profile
feature if
it implements presentation semantic support for the same vocabulary specified
above.
A TTML transformation processor supports the #showBackground
feature if it recognizes and is capable of transforming all defined values of
the tts:showBackground
attribute.
A TTML presentation processor supports the #showBackground
feature if it implements presentation semantic support for all defined values
of the tts:showBackground
attribute.
A TTML transformation processor supports the #structure
feature
if it recognizes and is capable of transforming the following vocabulary
defined by 7 Content:
A TTML presentation processor supports the #structure
feature
if it implements presentation semantic support for the same vocabulary
enumerated above.
A TTML transformation processor supports the #styling
feature
if it recognizes and is capable of transforming the following vocabulary
defined by 8 Styling:
A TTML presentation processor supports the #styling
feature if
it implements presentation semantic support for the same vocabulary enumerated
above.
A TTML transformation processor supports the #styling-chained
feature if it recognizes and is capable of transforming chained style
association as defined by <IP_ADDRESS> Chained
Referential Styling.
A TTML presentation processor supports the #styling-chained
feature if it implements presentation semantic support for chained style
association as defined by <IP_ADDRESS> Chained
Referential Styling.
A TTML transformation processor supports the
#styling-inheritance
feature if it recognizes and is capable of
transforming content style inheritance as defined by <IP_ADDRESS> Content Style
Inheritance.
A TTML presentation processor supports the
#styling-inheritance-content
feature if it implements presentation
semantic support for content style inheritance as defined by <IP_ADDRESS> Content Style
Inheritance.
A TTML transformation processor supports the
#styling-inheritance
feature if it recognizes and is capable of
transforming region style inheritance as defined by <IP_ADDRESS> Region Style
Inheritance.
A TTML presentation processor supports the
#styling-inheritance-region
feature if it implements presentation
semantic support for region style inheritance as defined by <IP_ADDRESS> Region Style
Inheritance.
A TTML transformation processor supports the #styling-inline
feature if it recognizes and is capable of transforming inline style
association as defined by <IP_ADDRESS> Inline Styling.
A TTML presentation processor supports the #styling-inline
feature if it implements presentation semantic support for inline style
association as defined by <IP_ADDRESS> Inline Styling.
A TTML transformation processor supports the #styling-nested
feature if it recognizes and is capable of transforming nested style
association as defined by <IP_ADDRESS> Nested Styling.
A TTML presentation processor supports the #styling-nested
feature if it implements presentation semantic support for nested style
association as defined by <IP_ADDRESS> Nested Styling.
A TTML transformation processor supports the
#styling-referential
feature if it recognizes and is capable of
transforming referential style association as defined by <IP_ADDRESS> Referential
Styling.
A TTML presentation processor supports the #styling-referential
feature if it implements presentation semantic support for referential style
association as defined by <IP_ADDRESS> Referential
Styling.
A TTML transformation processor supports the #subFrameRate
feature if it recognizes and is capable of transforming the ttp:subFrameRate
attribute.
A TTML presentation processor supports the #subFrameRate
feature if it implements presentation semantic support for the ttp:subFrameRate
attribute.
A TTML transformation processor supports the #textAlign
feature
if it recognizes and is capable of transforming all defined values of the
tts:textAlign
attribute.
A TTML presentation processor supports the #textAlign
feature
if it implements presentation semantic support for all defined values of the
tts:textAlign
attribute.
A TTML transformation processor supports the
#textAlign-absolute
feature if it recognizes and is capable of
transforming the left
, center
, and right
values of the tts:textAlign
attribute.
A TTML presentation processor supports the #textAlign-absolute
feature if it implements presentation semantic support for the
left
, center
, and right
values of the
tts:textAlign
attribute.
A TTML transformation processor supports the
#textAlign-relative
feature if it recognizes and is capable of
transforming the start
, center
, and end
values of the tts:textAlign
attribute.
A TTML presentation processor supports the #textAlign-relative
feature if it implements presentation semantic support for the
start
, center
, and end
values of the
tts:textAlign
attribute.
A TTML transformation processor supports the #textDecoration
feature if it recognizes and is capable of transforming all defined values of
the tts:textDecoration
attribute.
A TTML presentation processor supports the #textDecoration
feature if it implements presentation semantic support for all defined values
of the tts:textDecoration
attribute.
A TTML transformation processor supports the
#textDecoration-over
feature if it recognizes and is capable of
transforming the overline
and noOverline
values of
the tts:textDecoration
attribute.
A TTML presentation processor supports the #textDecoration-over
feature if it implements presentation semantic support for the
overline
and noOverline
values of the tts:textDecoration
attribute.
A TTML transformation processor supports the
#textDecoration-through
feature if it recognizes and is capable of
transforming the lineThrough
and noLineThrough
values
of the tts:textDecoration
attribute.
A TTML presentation processor supports the
#textDecoration-through
feature if it implements presentation
semantic support for the lineThrough
and
noLineThrough
values of the tts:textDecoration
attribute.
A TTML transformation processor supports the
#textDecoration-under
feature if it recognizes and is capable of
transforming the underline
and noUnderline
values of
the tts:textDecoration
attribute.
A TTML presentation processor supports the
#textDecoration-under
feature if it implements presentation
semantic support for the underline
and noUnderline
values of the tts:textDecoration
attribute.
A TTML transformation processor supports the #textOutline
feature if it recognizes and is capable of transforming the tts:textOutline
attribute.
A TTML presentation processor supports the #textOutline
feature
if it implements presentation semantic support for the tts:textOutline
attribute.
A TTML transformation processor supports the
#textOutline-blurred
feature if it recognizes and is capable of
transforming values of the tts:textOutline
attribute that
includes a blur radius specification.
A TTML presentation processor supports the #textOutline-blurred
feature if it implements presentation semantic support for values of the
tts:textOutline
attribute that includes a blur radius specification.
A TTML transformation processor supports the
#textOutline-unblurred
feature if it recognizes and is capable of
transforming values of the tts:textOutline
attribute that
does not include a blur radius specification.
A TTML presentation processor supports the
#textOutline-unblurred
feature if it implements presentation
semantic support for values of the tts:textOutline
attribute that
does not include a blur radius specification.
A TTML transformation processor supports the #tickRate
feature
if it recognizes and is capable of transforming the ttp:tickRate
attribute.
A TTML presentation processor supports the #tickRate
feature if
it implements presentation semantic support for the ttp:tickRate
attribute.
A TTML transformation processor supports the #timeBase-clock
feature if it recognizes and is capable of transforming the clock
value of the ttp:timeBase
attribute and if
it supports the #clockMode
feature.
A TTML presentation processor supports the #timeBase-clock
feature if it implements presentation semantic support for the
clock
value of the ttp:timeBase
attribute and if
it supports the #clockMode
feature.
A TTML transformation processor supports the #timeBase-media
feature if it recognizes and is capable of transforming the media
value of the ttp:timeBase
attribute.
A TTML presentation processor supports the #timeBase-media
feature if it implements presentation semantic support for the
media
value of the ttp:timeBase
attribute.
A TTML transformation processor supports the #timeBase-smpte
feature if it recognizes and is capable of transforming the smpte
value of the ttp:timeBase
attribute and if
it supports the #dropMode
feature.
A TTML presentation processor supports the #timeBase-smpte
feature if it implements presentation semantic support for the
smpte
value of the ttp:timeBase
attribute and if
it supports the #dropMode
feature.
A TTML transformation processor supports the #timeContainer
feature if it recognizes and is capable of transforming the timeContainer
attribute.
A TTML presentation processor supports the #timeContainer
feature if it implements presentation semantic support for the timeContainer
attribute.
A TTML transformation processor supports the #time-clock
feature if it recognizes and is capable of transforming all values of the
<timeExpression> that satisfy
the following subset of time expression syntax:
<timeExpression> : hours ":" minutes ":" seconds ( fraction )?
A TTML presentation processor supports the #time-clock
feature
if it implements presentation semantic support for the same syntax specified
above.
A TTML transformation processor supports the
#time-clock-with-frames
feature if it supports the #frameRate
, #frameRateMultiplier
, and
#subFrameRate
features and if
it recognizes and is capable of transforming all values of the <timeExpression> that satisfy the
following subset of time expression syntax:
<timeExpression> : hours ":" minutes ":" seconds ( fraction | ":" frames ( "." sub-frames )? )?
A TTML presentation processor supports the
#time-clock-with-frames
feature if it implements presentation
semantic support for the same features and syntax specified above.
A TTML transformation processor supports the #time-offset
feature if it recognizes and is capable of transforming all values of the
<timeExpression> that satisfy
the following subset of time expression syntax:
<timeExpression> : time-count fraction? ( "h" | "m" | "s" | "ms" )
A TTML presentation processor supports the #time-offset
feature
if it implements presentation semantic support for the same syntax specified
above.
A TTML transformation processor supports the
#time-offset-with-frames
feature if it supports the #frameRate
, #frameRateMultiplier
, and
#subFrameRate
features and if
it recognizes and is capable of transforming all values of the <timeExpression> that satisfy the
following subset of time expression syntax:
<timeExpression> : time-count fraction? "f"
A TTML presentation processor supports the
#time-offset-with-frames
feature if it implements presentation
semantic support for the same features and syntax specified above.
A TTML transformation processor supports the
#time-offset-with-ticks
feature if it supports the #tickRate
feature and if it recognizes and
is capable of transforming all values of the <timeExpression> that satisfy the
following subset of time expression syntax:
<timeExpression> : time-count fraction? "t"
A TTML presentation processor supports the
#time-offset-with-ticks
feature if it implements presentation
semantic support for the same features and syntax specified above.
A TTML transformation processor supports the #timing
feature if
it recognizes and is capable of transforming the following vocabulary defined
by 10 Timing:
A TTML presentation processor supports the #timing
feature if
it implements presentation semantic support for the same vocabulary enumerated
above.
A TTML processor supports the #transformation
feature if it (1)
satisfies the generic processor criteria defined by 3.2.1 Generic Processor Conformance
and (2) implements the transformation semantics of the following features:
A TTML transformation processor supports the #unicodeBidi
feature if it recognizes and is capable of transforming all defined values of
the tts:unicodeBidi
attribute.
A TTML presentation processor supports the #unicodeBidi
feature
if it implements presentation semantic support for all defined values of the
tts:unicodeBidi
attribute.
A TTML transformation processor supports the #visibility
feature if it recognizes and is capable of transforming all defined values of
the tts:visibility
attribute.
A TTML presentation processor supports the #visibility
feature
if it implements presentation semantic support for all defined values of the
tts:visibility
attribute.
A TTML transformation processor supports the #visibility-block
feature if it recognizes and is capable of transforming all defined values of
the tts:visibility
attribute when applied to a content element that would generate a block area
during presentation processing.
A TTML presentation processor supports the #visibility-block
feature if it implements presentation semantic support for all defined values
of the tts:visibility
attribute when applied to a content element that generates a block area.
A TTML transformation processor supports the #visibility-inline
feature if it recognizes and is capable of transforming all defined values of
the tts:visibility
attribute when applied to a content element that would generate an inline area
during presentation processing.
A TTML presentation processor supports the #visibility-inline
feature if it implements presentation semantic support for all defined values
of the tts:visibility
attribute when applied to a content element that generates an inline area.
A TTML transformation processor supports the #visibility-region
feature if it recognizes and is capable of transforming all defined values of
the tts:visibility
attribute when applied to a region
element.
A TTML presentation processor supports the #visibility-region
feature if it implements presentation semantic support for all defined values
of the tts:visibility
attribute when applied to a region
element.
A TTML transformation processor supports the #wrapOption
feature if it recognizes and is capable of transforming all defined values of
the tts:wrapOption
attribute.
A TTML presentation processor supports the #wrapOption
feature
if it implements presentation semantic support for all defined values of the
tts:wrapOption
attribute.
A TTML transformation processor supports the #writingMode
feature if it recognizes and is capable of transforming all defined values of
the tts:writingMode
attribute.
A TTML presentation processor supports the #writingMode
feature
if it implements presentation semantic support for all defined values of the
tts:writingMode
attribute.
A TTML transformation processor supports the
#writingMode-vertical
feature if it recognizes and is capable of
transforming the tbrl
, tblr
, and tb
values of the tts:writingMode
attribute.
A TTML presentation processor supports the
#writingMode-vertical
feature if it implements presentation
semantic support for the tbrl
, tblr
, and
tb
values of the tts:writingMode
attribute.
A TTML transformation processor supports the
#writingMode-horizontal
feature if it recognizes and is capable of
transforming the lrtb
, rltb
, lr
and
rl
values of the tts:writingMode
attribute.
A TTML presentation processor supports the
#writingMode-horizontal
feature if it implements presentation
semantic support for the lrtb
, rltb
, lr
and rl
values of the tts:writingMode
attribute.
A TTML transformation processor supports the
#writingMode-horizontal
feature if it recognizes and is capable of
transforming the lrtb
and lr
values of the tts:writingMode
attribute.
A TTML presentation processor supports the
#writingMode-horizontal-lr
feature if it implements presentation
semantic support for the lrtb
and lr
values of the
tts:writingMode
attribute.
A TTML transformation processor supports the
#writingMode-horizontal
feature if it recognizes and is capable of
transforming the rltb
and rl
values of the tts:writingMode
attribute.
A TTML presentation processor supports the
#writingMode-horizontal-rl
feature if it implements presentation
semantic support for the rltb
and rl
values of the
tts:writingMode
attribute.
A TTML transformation processor supports the #zIndex
feature if
it recognizes and is capable of transforming the tts:zIndex
attribute.
A TTML presentation processor supports the #zIndex
feature if
it implements presentation semantic support for the tts:zIndex
attribute.
The following table, Table D-1 – Feature Support, enumerates every defined feature designation (expressed without the TT Feature Namespace), and, for each designated feature, specifies whether the feature must be implemented, i.e., is mandatory (M), or may be implemented, i.e., is optional (O), for transformation and presentation processors.
For the sake of convenience, the following table, Table D-2 – Mandatory Features - Transformation, enumerates all mandatory features for a TTML Transformation Processor, providing additional comments to summarize the context of usage or the nature of the feature. The Profile Definition Document that defines the corresponding DFXP Transformation Profile is specified in F.1 DFXP Transformation Profile.
| Feature | Comments |
#content |
body ,
div , p , span , br |
#core |
@xml:id , @xml:lang , @xml:space |
#profile |
|
#structure |
tt ,
head |
#time-offset |
|
#timing |
@begin , @dur , @end |
#transformation |
For the sake of convenience, the following table, Table D-3 – Mandatory Features - Presentation, enumerates all mandatory features for a TTML Presentation Processor, providing additional comments to summarize the context of usage or the nature of the feature. The Profile Definition Document that defines the corresponding DFXP Presentation Profile is specified in F.2 DFXP Presentation Profile.
| Feature | Comments |
#content |
body ,
div , p , span , br |
#core |
@xml:id , @xml:lang , @xml:space |
#profile |
|
#presentation |
|
#structure |
tt ,
head |
#time-offset |
|
#timing |
@begin , @dur , @end |
This appendix is normative.
This appendix specifies the syntactic form of extension designations, which are used to express authorial intent regarding the support for extension mechanisms in a TTML processor.
An extension designation is expressed as a string that adheres to the following form:
extension-designation : extension-namespace designation extension-namespace : TT Extension Namespace // http://www.w3.org/ns/ttml/extension/ | Other Extension Namespace // expressed as an absolute URI designation : "#" token-char+ token-char : { XML NameChar } // XML 1.1 Production [4a]
If the extension namespace of an extension designation is the TT Extension
Namespace, then all values of the following designation
token are
reserved for future standardization.
If the extension namespace of an extension designation is not the TT Extension
Namespace, i.e., is an Other Extension Namespace, then the extension
namespace must be expressed as an absolute URI capable of serving as a base URI
used in combination with a designation
token that takes the form of
a fragment identifier.
This appendix is normative.
This appendix specifies the following standard TTML profiles:
The SDP US profile is defined in TTML Simple Delivery Profile for Closed Captions (US).
Each TTML profile is defined in terms of a Profile Definition Document, which is expressed as an XML document wherein the root element adheres to 6.1.1 ttp:profile.
The DFXP Transformation Profile is intended to be used to express minimum compliance for transformation processing.
<?xml version="1.0" encoding="utf-8"?> <!-- this file defines the "dfxp-transformation" profile of ttml --> <profile xmlns="http://www.w3.org/ns/ttml#parameter"> <features xml:base="http://www.w3.org/ns/ttml/feature/"> <!-- required (mandatory) feature support --> <feature value="required">#content</feature> <feature value="required">#core</feature> <feature value="required">#profile</feature> <feature value="required">#structure</feature> <feature value="required">#time-offset</feature> <feature value="required">#timing</feature> <feature value="required">#transformation</feature> <!-- optional (voluntary) feature support --> <feature value="optional">#animation</feature> <feature value="optional">#backgroundColor-block</feature> <feature value="optional">#backgroundColor-inline</feature> <feature value="optional">#backgroundColor-region</feature> <feature value="optional">#backgroundColor</feature> <feature value="optional">#bidi</feature> <feature value="optional">#cellResolution</feature> <feature value="optional">#clockMode-gps</feature> <feature value="optional">#clockMode-local</feature> <feature value="optional">#clockMode-utc</feature> <feature value="optional">#clockMode</feature> <feature value="optional">#color</feature> <feature value="optional">#direction</feature> <feature value="optional">#display-block</feature> <feature value="optional">#display-inline</feature> <feature value="optional">#display-region</feature> <feature value="optional">#display</feature> <feature value="optional">#displayAlign</feature> <feature value="optional">#dropMode-dropNTSC</feature> <feature value="optional">#dropMode-dropPAL</feature> <feature value="optional">#dropMode-nonDrop</feature> <feature value="optional">#dropMode</feature> <feature value="optional">#extent-region</feature> <feature value="optional">#extent-root</feature> <feature value="optional">#extent</feature> <feature value="optional">#fontFamily-generic</feature> <feature value="optional">#fontFamily-non-generic</feature> <feature value="optional">#fontFamily</feature> <feature value="optional">#fontSize-anamorphic</feature> <feature value="optional">#fontSize-isomorphic</feature> <feature value="optional">#fontSize</feature> <feature value="optional">#fontStyle-italic</feature> <feature value="optional">#fontStyle-oblique</feature> <feature value="optional">#fontStyle</feature> <feature value="optional">#fontWeight-bold</feature> <feature value="optional">#fontWeight</feature> <feature value="optional">#frameRate</feature> <feature value="optional">#frameRateMultiplier</feature> <feature value="optional">#layout</feature> <feature value="optional">#length-cell</feature> <feature value="optional">#length-em</feature> <feature value="optional">#length-integer</feature> <feature value="optional">#length-negative</feature> <feature value="optional">#length-percentage</feature> <feature value="optional">#length-pixel</feature> <feature value="optional">#length-positive</feature> <feature value="optional">#length-real</feature> <feature value="optional">#length</feature> <feature value="optional">#lineBreak-uax14</feature> <feature value="optional">#lineHeight</feature> <feature value="optional">#markerMode-continuous</feature> <feature value="optional">#markerMode-discontinuous</feature> <feature value="optional">#markerMode</feature> <feature value="optional">#metadata</feature> <feature value="optional">#nested-div</feature> <feature value="optional">#nested-span</feature> <feature value="optional">#opacity</feature> <feature value="optional">#origin</feature> <feature value="optional">#overflow-visible</feature> <feature value="optional">#overflow</feature> <feature value="optional">#padding-1</feature> <feature value="optional">#padding-2</feature> <feature value="optional">#padding-3</feature> <feature value="optional">#padding-4</feature> <feature value="optional">#padding</feature> <feature value="optional">#pixelAspectRatio</feature> <feature value="optional">#presentation</feature> <feature value="optional">#showBackground</feature> <feature value="optional">#styling-chained</feature> <feature value="optional">#styling-inheritance-content</feature> <feature value="optional">#styling-inheritance-region</feature> <feature value="optional">#styling-inline</feature> <feature value="optional">#styling-nested</feature> <feature value="optional">#styling-referential</feature> <feature value="optional">#styling</feature> <feature value="optional">#subFrameRate</feature> <feature value="optional">#textAlign-absolute</feature> <feature value="optional">#textAlign-relative</feature> <feature value="optional">#textAlign</feature> <feature value="optional">#textDecoration-over</feature> <feature value="optional">#textDecoration-through</feature> <feature value="optional">#textDecoration-under</feature> <feature value="optional">#textDecoration</feature> <feature value="optional">#textOutline-blurred</feature> <feature value="optional">#textOutline-unblurred</feature> <feature value="optional">#textOutline</feature> <feature value="optional">#tickRate</feature> <feature value="optional">#time-clock-with-frames</feature> <feature value="optional">#time-clock</feature> <feature value="optional">#time-offset-with-frames</feature> <feature value="optional">#time-offset-with-ticks</feature> <feature value="optional">#timeBase-clock</feature> <feature value="optional">#timeBase-media</feature> <feature value="optional">#timeBase-smpte</feature> <feature value="optional">#timeContainer</feature> <feature value="optional">#unicodeBidi</feature> <feature value="optional">#visibility-block</feature> <feature value="optional">#visibility-inline</feature> <feature value="optional">#visibility-region</feature> <feature value="optional">#visibility</feature> <feature value="optional">#wrapOption</feature> <feature value="optional">#writingMode-horizontal-lr</feature> <feature value="optional">#writingMode-horizontal-rl</feature> <feature value="optional">#writingMode-horizontal</feature> <feature value="optional">#writingMode-vertical</feature> <feature value="optional">#writingMode</feature> <feature value="optional">#zIndex</feature> </features> <extensions xml:base="http://www.w3.org/ns/ttml/extension/"> <!-- required (mandatory) extension support --> <!-- optional (voluntary) extension support --> </extensions> </profile>
The DFXP Presentation Profile is intended to be used to express minimum compliance for presentation processing.
<?xml version="1.0" encoding="utf-8"?> <!-- this file defines the "dfxp-presentation" profile of ttml --> <profile xmlns="http://www.w3.org/ns/ttml#parameter"> <features xml:base="http://www.w3.org/ns/ttml/feature/"> <!-- required (mandatory) feature support --> <feature value="required">#content</feature> <feature value="required">#core</feature> <feature value="required">#presentation</feature> <feature value="required">#profile</feature> <feature value="required">#structure</feature> <feature value="required">#time-offset</feature> <feature value="required">#timing</feature> <!-- optional (voluntary) feature support --> <feature value="optional">#animation</feature> <feature value="optional">#backgroundColor-block</feature> <feature value="optional">#backgroundColor-inline</feature> <feature value="optional">#backgroundColor-region</feature> <feature value="optional">#backgroundColor</feature> <feature value="optional">#bidi</feature> <feature value="optional">#cellResolution</feature> <feature value="optional">#clockMode-gps</feature> <feature value="optional">#clockMode-local</feature> <feature value="optional">#clockMode-utc</feature> <feature value="optional">#clockMode</feature> <feature value="optional">#color</feature> <feature value="optional">#direction</feature> <feature value="optional">#display-block</feature> <feature value="optional">#display-inline</feature> <feature value="optional">#display-region</feature> <feature value="optional">#display</feature> <feature value="optional">#displayAlign</feature> <feature value="optional">#dropMode-dropNTSC</feature> <feature value="optional">#dropMode-dropPAL</feature> <feature value="optional">#dropMode-nonDrop</feature> <feature value="optional">#dropMode</feature> <feature value="optional">#extent-region</feature> <feature value="optional">#extent-root</feature> <feature value="optional">#extent</feature> <feature value="optional">#fontFamily-generic</feature> <feature value="optional">#fontFamily-non-generic</feature> <feature value="optional">#fontFamily</feature> <feature value="optional">#fontSize-anamorphic</feature> <feature value="optional">#fontSize-isomorphic</feature> <feature value="optional">#fontSize</feature> <feature value="optional">#fontStyle-italic</feature> <feature value="optional">#fontStyle-oblique</feature> <feature value="optional">#fontStyle</feature> <feature value="optional">#fontWeight-bold</feature> <feature value="optional">#fontWeight</feature> <feature value="optional">#frameRate</feature> <feature value="optional">#frameRateMultiplier</feature> <feature value="optional">#layout</feature> <feature value="optional">#length-cell</feature> <feature value="optional">#length-em</feature> <feature value="optional">#length-integer</feature> <feature value="optional">#length-negative</feature> <feature value="optional">#length-percentage</feature> <feature value="optional">#length-pixel</feature> <feature value="optional">#length-positive</feature> <feature value="optional">#length-real</feature> <feature value="optional">#length</feature> <feature value="optional">#lineBreak-uax14</feature> <feature value="optional">#lineHeight</feature> <feature value="optional">#markerMode-continuous</feature> <feature value="optional">#markerMode-discontinuous</feature> <feature value="optional">#markerMode</feature> <feature value="optional">#metadata</feature> <feature value="optional">#nested-div</feature> <feature value="optional">#nested-span</feature> <feature value="optional">#opacity</feature> <feature value="optional">#origin</feature> <feature value="optional">#overflow-visible</feature> <feature value="optional">#overflow</feature> <feature value="optional">#padding-1</feature> <feature value="optional">#padding-2</feature> <feature value="optional">#padding-3</feature> <feature value="optional">#padding-4</feature> <feature value="optional">#padding</feature> <feature value="optional">#pixelAspectRatio</feature> <feature value="optional">#showBackground</feature> <feature value="optional">#styling-chained</feature> <feature value="optional">#styling-inheritance-content</feature> <feature value="optional">#styling-inheritance-region</feature> <feature value="optional">#styling-inline</feature> <feature value="optional">#styling-nested</feature> <feature value="optional">#styling-referential</feature> <feature value="optional">#styling</feature> <feature value="optional">#subFrameRate</feature> <feature value="optional">#textAlign-absolute</feature> <feature value="optional">#textAlign-relative</feature> <feature value="optional">#textAlign</feature> <feature value="optional">#textDecoration-over</feature> <feature value="optional">#textDecoration-through</feature> <feature value="optional">#textDecoration-under</feature> <feature value="optional">#textDecoration</feature> <feature value="optional">#textOutline-blurred</feature> <feature value="optional">#textOutline-unblurred</feature> <feature value="optional">#textOutline</feature> <feature value="optional">#tickRate</feature> <feature value="optional">#time-clock-with-frames</feature> <feature value="optional">#time-clock</feature> <feature value="optional">#time-offset-with-frames</feature> <feature value="optional">#time-offset-with-ticks</feature> <feature value="optional">#timeBase-clock</feature> <feature value="optional">#timeBase-media</feature> <feature value="optional">#timeBase-smpte</feature> <feature value="optional">#timeContainer</feature> <feature value="optional">#transformation</feature> <feature value="optional">#unicodeBidi</feature> <feature value="optional">#visibility-block</feature> <feature value="optional">#visibility-inline</feature> <feature value="optional">#visibility-region</feature> <feature value="optional">#visibility</feature> <feature value="optional">#wrapOption</feature> <feature value="optional">#writingMode-horizontal-lr</feature> <feature value="optional">#writingMode-horizontal-rl</feature> <feature value="optional">#writingMode-horizontal</feature> <feature value="optional">#writingMode-vertical</feature> <feature value="optional">#writingMode</feature> <feature value="optional">#zIndex</feature> </features> <extensions xml:base="http://www.w3.org/ns/ttml/extension/"> <!-- required (mandatory) extension support --> <!-- optional (voluntary) extension support --> </extensions> </profile>
The DFXP Full Profile is intended to be used to express maximum compliance for both transformation and presentation processing.
<?xml version="1.0" encoding="utf-8"?> <!-- this file defines the "dfxp-full" profile of ttml --> <profile xmlns="http://www.w3.org/ns/ttml#parameter"> <features xml:base="http://www.w3.org/ns/ttml/feature/"> <!-- required (mandatory) feature support --> <feature value="required">#animation</feature> <feature value="required">#backgroundColor-block</feature> <feature value="required">#backgroundColor-inline</feature> <feature value="required">#backgroundColor-region</feature> <feature value="required">#backgroundColor</feature> <feature value="required">#bidi</feature> <feature value="required">#cellResolution</feature> <feature value="required">#clockMode-gps</feature> <feature value="required">#clockMode-local</feature> <feature value="required">#clockMode-utc</feature> <feature value="required">#clockMode</feature> <feature value="required">#color</feature> <feature value="required">#content</feature> <feature value="required">#core</feature> <feature value="required">#direction</feature> <feature value="required">#display-block</feature> <feature value="required">#display-inline</feature> <feature value="required">#display-region</feature> <feature value="required">#display</feature> <feature value="required">#displayAlign</feature> <feature value="required">#dropMode-dropNTSC</feature> <feature value="required">#dropMode-dropPAL</feature> <feature value="required">#dropMode-nonDrop</feature> <feature value="required">#dropMode</feature> <feature value="required">#extent-region</feature> <feature value="required">#extent-root</feature> <feature value="required">#extent</feature> <feature value="required">#fontFamily-generic</feature> <feature value="required">#fontFamily-non-generic</feature> <feature value="required">#fontFamily</feature> <feature value="required">#fontSize-anamorphic</feature> <feature value="required">#fontSize-isomorphic</feature> <feature value="required">#fontSize</feature> <feature value="required">#fontStyle-italic</feature> <feature value="required">#fontStyle-oblique</feature> <feature value="required">#fontStyle</feature> <feature value="required">#fontWeight-bold</feature> <feature value="required">#fontWeight</feature> <feature value="required">#frameRate</feature> <feature value="required">#frameRateMultiplier</feature> <feature value="required">#layout</feature> <feature value="required">#length-cell</feature> <feature value="required">#length-em</feature> <feature value="required">#length-integer</feature> <feature value="required">#length-negative</feature> <feature value="required">#length-percentage</feature> <feature value="required">#length-pixel</feature> <feature value="required">#length-positive</feature> <feature value="required">#length-real</feature> <feature value="required">#length</feature> <feature value="required">#lineBreak-uax14</feature> <feature value="required">#lineHeight</feature> <feature value="required">#markerMode-continuous</feature> <feature value="required">#markerMode-discontinuous</feature> <feature value="required">#markerMode</feature> <feature value="required">#metadata</feature> <feature value="required">#nested-div</feature> <feature value="required">#nested-span</feature> <feature value="required">#opacity</feature> <feature value="required">#origin</feature> <feature value="required">#overflow-visible</feature> <feature value="required">#overflow</feature> <feature value="required">#padding-1</feature> <feature value="required">#padding-2</feature> <feature value="required">#padding-3</feature> <feature value="required">#padding-4</feature> <feature value="required">#padding</feature> <feature value="required">#pixelAspectRatio</feature> <feature value="required">#presentation</feature> <feature value="required">#profile</feature> <feature value="required">#showBackground</feature> <feature value="required">#structure</feature> <feature value="required">#styling-chained</feature> <feature value="required">#styling-inheritance-content</feature> <feature value="required">#styling-inheritance-region</feature> <feature value="required">#styling-inline</feature> <feature value="required">#styling-nested</feature> <feature value="required">#styling-referential</feature> <feature value="required">#styling</feature> <feature value="required">#subFrameRate</feature> <feature value="required">#textAlign-absolute</feature> <feature value="required">#textAlign-relative</feature> <feature value="required">#textAlign</feature> <feature value="required">#textDecoration-over</feature> <feature value="required">#textDecoration-through</feature> <feature value="required">#textDecoration-under</feature> <feature value="required">#textDecoration</feature> <feature value="required">#textOutline-blurred</feature> <feature value="required">#textOutline-unblurred</feature> <feature value="required">#textOutline</feature> <feature value="required">#tickRate</feature> <feature value="required">#time-clock-with-frames</feature> <feature value="required">#time-clock</feature> <feature value="required">#time-offset-with-frames</feature> <feature value="required">#time-offset-with-ticks</feature> <feature value="required">#time-offset</feature> <feature value="required">#timeBase-clock</feature> <feature value="required">#timeBase-media</feature> <feature value="required">#timeBase-smpte</feature> <feature value="required">#timeContainer</feature> <feature value="required">#timing</feature> <feature value="required">#transformation</feature> <feature value="required">#unicodeBidi</feature> <feature value="required">#visibility-block</feature> <feature value="required">#visibility-inline</feature> <feature value="required">#visibility-region</feature> <feature value="required">#visibility</feature> <feature value="required">#wrapOption</feature> <feature value="required">#writingMode-horizontal-lr</feature> <feature value="required">#writingMode-horizontal-rl</feature> <feature value="required">#writingMode-horizontal</feature> <feature value="required">#writingMode-vertical</feature> <feature value="required">#writingMode</feature> <feature value="required">#zIndex</feature> <!-- optional (voluntary) feature support --> </features> <extensions xml:base="http://www.w3.org/ns/ttml/extension/"> <!-- required (mandatory) extension support --> <!-- optional (voluntary) extension support --> </extensions> </profile>
This appendix is normative.
The Timed Text Markup Language (TTML), also known as the Distribution Format Exchange Profile (DFXP) of the Timed Text Authoring Format (TTAF), satisfies a subset of the requirements established by [TTAF1-REQ]. The following table enumerates these requirements and indicates the extent to which they are satisfied by this specification, where S denotes a requirement is satisfied, P denotes a requirement is partially satisfied, and N denotes a requirement is not satisfied.
| ID | Name | Status | Comments |
|---|---|---|---|
| R100 | Specification Format | S | |
| R101 | Specification Modularity | S | |
| R102 | Specification Organization | S | |
| R103 | Core and Periphery | S | TT extension namespaces |
| R104 | Evolution of Core | S | TT extension namespaces |
| R105 | Ownership of Core | S | TT namespaces |
| R106 | Surjection of Core | S | |
| R107 | Evolution of Periphery | S | TT extension namespaces |
| R108 | Ownership of Periphery | S | Non-TT namespaces |
| R109 | Transformation | S | Supports 3GPP, QText, RealText, SAMI |
| R110 | Streamable Transformation | S | Progressive decoding |
| R111 | Accessibility – Content | S | Alternative document instances |
| R112 | Accessibility – Authoring System | S | |
| R200 | Authorability | S | |
| R201 | Multiple Natural Languages | S | Alternative document instances |
| R202 | Natural Language Coverage | S | Unicode 4.0 |
| R203 | Natural Language Association Granularity | S | See xml:lang |
| R204 | Minimum Character Representability | S | Unicode 4.0 |
| R205 | Intrinsic and Extrinsic Text Content | P | Intrinsic only |
| R206 | Markup Association | P | Intrinsic only |
| R207 | Conditional Content | N | |
| R208 | Flowed Text | S | |
| R209 | Logical Flowed Text Vocabulary | S | |
| R210 | Presentational Flowed Text Vocabulary | S | Implied mapping from logical flowed text. |
| R211 | Flowed Text Vocabulary Relationship | S | |
| R212 | Flowed Text Vocabulary Separation | N | |
| R213 | Non-Flowed Text | N | |
| R214 | Non-Flowed Text Vocabulary | N | |
| R215 | Hybrid Flowed and Non-Flowed Text | N | |
| R216 | Hyperlinking | N | Can support via XLink |
| R217 | Embedded Graphics | N | |
| R218 | Non-Embedded Graphics | N | |
| R219 | Embedded Fonts | N | |
| R220 | Non-Embedded Fonts | N | |
| R221 | Descriptive Vocabulary | S | See ttm:agent , ttm:role |
| R222 | Embedded Audio | N | |
| R223 | Non-Embedded Audio | N | |
| R290 | Markup Format | S | |
| R291 | Markup Format and Unicode Interaction | S | |
| R292 | Extrinsic Resource References | N | No extrinsic references |
| R293 | Schema Validity Specification | S | |
| R300 | Inline Styling | S | |
| R301 | Inline Styling Form | P | Inline and referential styling |
| R301 | Out-of-Line Styling | N | |
| R301 | Out-of-Line Styling Form | N | |
| R304 | Styling Prioritization | S | |
| R305 | Style Parameters – Aural | N | |
| R306 | Style Parameters – Visual | P | Supports absolute position, background color, color, display none, display alignment, font family, font size, font style, font weight, height, line height, origin, opacity, overflow, padding (before, after, start, end), text alignment, text shadow (as outline), visibility, width, writing mode, z-index |
| R390 | Style Parameter Symmetry | S | |
| R391 | Style Parameter Definitions | S | |
| R392 | Style Parameter Shorthands | S | |
| R401 | Inline Timing | S | |
| R402 | Out-of-Line Timing | N | |
| R403 | Synchronization Parameters | P | Supports begin, end, dur |
| R404 | Synchronization Parameter Value Spaces | P | Supports offset values, media marker values (SMPTE 12M), wall-clock values |
| R405 | Time Containment Semantics | P | Supports sequential, parallel |
| R500 | Animation Modes | P | Supports discrete |
| R502 | Highlight Animation | S | <set tts:backgroundColor="..."/> |
| R503 | Fade Transition Animation | S | <set tts:opacity="..."/> |
| R504 | Animated Style Parameters – Aural | N | |
| R505 | Animated Style Parameters – Visual | P | Supports animating background color, color, display, opacity, origin, visibility |
| N506 | Animated Content | S | |
| R600 | Metadata Item Association | S | See metadata , Metadata.class |
| R601 | Metadata Item Constituents | P | Supports name, value |
| R602 | Metadata Item Value Representation | P | See metadata |
| R603 | Metadata Item Extensibility | S | See metadata |
| R604 | Metadata Item Validation | S | See metadata |
| R690 | Dublin Core Preference | N | Uses ttm:copyright , ttm:desc ,
ttm:title |
This appendix provides information about the derivation of TTML vocabulary, separately describing derivation of elements and attributes.
The first column of Table J-1 – Elements specifies a TTML element vocabulary item; the second column specifies the syntactic and/or semantic model on which the vocabulary item is based; the third column specifies the reference that defines the model (if a model is indicated); the fourth column specifies details about the derivation; the last column refers to additional notes describing the nature of the derivation.
In the fourth column, which describes details of derivation, a notation is use
to indicate the addition or removal of an attribute. For example, in the
derivation of the tt:div
element, the details column includes
"-@class", which denotes that the class
attribute that is specified
for use with the xhtml:div
model element is not specified for use
with the corresponding TTML element; in contrast, the details column includes
"+@begin", which denotes that a begin
attribute is added that is not
specified for use with the xhtml:div
model element.
| Element | Model | Reference | Details | Notes |
tt:body |
xhtml:body |
[XHTML 1.0] | -@class, -@dir, -@lang, -@on*, -@title; +@begin, +@dur, +@end, +@region, +@timeContainer, +@ttm:*, +@tts:*; content model subsetted to zero or more division (div) children, and supersetted by optional metadata and animation children | 1,2 |
tt:br |
xhtml:br |
[XHTML 1.0] | -@class, -@title; +@ttm:*, +@tts:*, +@xml:lang, +@xml:space; content model supersetted by optional metadata and animation children for congruity with other content vocabulary | 1,2 |
tt:div |
xhtml:div |
[XHTML 1.0] | -@class, -@dir, -@lang, -@on*, -@title; +@begin, +@dur, +@end, +@region, +@timeContainer, +@ttm:*, +@tts:*, +@xml:space; content model subsetted to zero or more paragraph (p) children, and supersetted by optional metadata and animation children | 1,2,3 |
tt:head |
xhtml:head |
[XHTML 1.0] | -@dir, -@lang, -@profile; +@id, +@xml:space; content model changed to optional metadata children, followed by optional styling child, followed by optional layout child | 1,3 |
tt:layout |
fo:simple-page-master |
[XSL 1.1] | conceptual derivation | 4 |
tt:metadata |
svg:metadata |
[SVG 1.1] | -@xml:base; +@ttm:*, +@xml:lang, +@xml:space; content model subsetted to foreign namespace element content only (no #PCDATA) | 3,5 |
tt:p |
xhtml:p |
[XHTML 1.0] | -@class, -@dir, -@lang, -@on*, -@title; +@begin, +@dur, +@end, +@region, +@timeContainer, +@ttm:*, +@tts:*, +@xml:space; content model subsetted to zero or more span children, and supersetted by optional metadata and animation children | 1,2,3 |
tt:region |
fo:region-* |
[XSL 1.1] | conceptual derivation | 4 |
tt:set |
svg:set |
[SVG 1.1] | -@* except begin, dur, end; +@tts:*, +@xml:lang, +@xml:space | 3,6 |
tt:span |
xhtml:span |
[XHTML 1.0] | -@class, -@dir, -@lang, -@on*, -@title; +@begin, +@dur, +@end, +@region, +@timeContainer, +@ttm:*, +@tts:*, +@xml:space; content model subsetted to zero or more #PCDATA or break (br) children, and supersetted by optional metadata and animation children | 1,2,3 |
tt:style |
style specification | [CSS2] | XML representation of identified set of pairs of style property name and value, with optional inclusion of other styles by reference to other style elements | 7 |
tt:styling |
xhtml:style |
[XHTML 1.0] | XML representation of a set of style specifications sets, each represented by a style child element | 1,7 |
tt:tt |
xhtml:html |
[XHTML 1.0] | -@dir, -@lang; +@id, +@ttp:*, +@xml:space; content model subsetted by permitting body and/or head to be optional | 1,8 |
ttm:actor |
mpeg7:Creator |
[MPEG7-5] | conceptual derivation | 4 |
ttm:agent |
mpeg7:Agent |
[MPEG7-5] | conceptual derivation | 4 |
ttm:copyright |
mpeg7:CopyrightString |
[MPEG7-5] | conceptual derivation | 4 |
ttm:desc |
svg:desc |
[SVG 1.1] | -@class, -@style, -@xml:base | 2,5,9 |
ttm:name |
mpeg7:Name |
[MPEG7-5] | conceptual derivation | 4 |
ttm:title |
svg:title |
[SVG 1.1] | -@class, -@style, -@xml:base | 2,5,9 |
ttp:extension |
@requiredExtensions |
[SVG 1.1] | conceptual derivation | 10 |
ttp:extensions |
@requiredExtensions |
[SVG 1.1] | conceptual derivation | 10 |
ttp:feature |
@requiredFeatures |
[SVG 1.1] | conceptual derivation | 10 |
ttp:features |
@requiredFeatures |
[SVG 1.1] | conceptual derivation | 10 |
ttp:profile |
@baseProfile |
[SVG 1.1] | conceptual derivation | 11 |
Note:
Derivation is indicated with respect to the strict DTD defined by [XHTML 1.0], §A.1.
The class
attribute is effectively replaced by the
style
attribute, which, instead of specifying an inline style,
refers indirectly to one or more style
elements that define a
set of style specification sets.
The xml:lang
and xml:space
attributes are
defined for all element types in order to support their inheritance
semantics to operate in the context of foreign namespace elements.
Derivation is conceptual (notional) only.
The xml:base
attribute is not used since there are no
external references from core vocabulary.
The attributeName
and to
attributes of
svg:set
are replaced by the direct expression of the target
attribute name and value by use of a tts:*
attribute.
CSS style specification syntax is mapped to XML by use of attributes defined in the TT Style Namespace.
The xml:id
attribute is defined for use on all element
types.
The style
attribute is supported only on Content elements.
Derived from the use of @requiredExtensions
and
@requiredFeatures
on the svg:svg
element, but
extended to support distinct specification of optionality.
Derived from the use of @baseProfile
and
@version
on the svg:svg
element.
The first column of Table J-2 – Attributes specifies a TTML attribute vocabulary item; the second column specifies the syntactic and/or semantic model on which the vocabulary item is based; the third column specifies the reference that defines the model (if a model is indicated); the fourth column specifies details about the derivation; the last column refers to additional notes describing the nature of the derivation.
In the fourth column, which describes details of derivation, a notation is use
to indicate the addition or removal of an attribute value. For example, in the
derivation of the timeContainer
attribute, the details column
includes "-excl", which denotes that the excl
value that is
specified for use with the timeContainer
model attribute is not
specified for use with the corresponding TTML attribute; similarly, an
"+value" in the details column indicates that the attribute's values
have been extended to include value.
Only those attributes that are specified for use on more than one TTML element type are listed below. Those per-element namespace attributes that are uniquely defined for a specific TTML element type are not listed below, but are considered to be part of the specific element type's derivation described in Table J-1 – Elements above.
| Attribute | Model | Reference | Details | Notes |
begin |
begin |
[SMIL 2.1] | see notes | 2,3,4 |
dur |
dur |
[SMIL 2.1] | see notes | 2,3,4 |
end |
end |
[SMIL 2.1] | see notes | 2,3,4 |
region |
master-reference |
[XSL 1.1] | conceptual derivation | |
style |
class |
[CSS2] | dereferences style specification(s) directly | |
timeContainer |
timeContainer |
[SMIL 2.1] | -excl, -none; no default attribute value | 5 |
ttm:agent |
none | used to attribute agent of content | ||
ttm:role |
none | used to attribute role of content | ||
ttp:cellResolution |
none | expresses uniform grid resolution for cell based coordinates | ||
ttp:clockMode |
none | determines how to interpret time expressions | ||
ttp:frameRate |
none | expresses integral frame rate | ||
ttp:frameRateMultiplier |
none | used to express non-integral, rational frame rates | ||
ttp:markerMode |
none | expresses marker continuity semantics | ||
ttp:pixelAspectRatio |
none | expresses pixel aspect ratio of related media | ||
ttp:profile |
none | expresses profile of TTML used by a Document Instance | ||
ttp:dropMode |
none | expresses frame counting (drop) modes | ||
ttp:subFrameRate |
none | expresses sub-frame rate | ||
ttp:tickRate |
none | used to interpret tick based time expressions | ||
ttp:timeBase |
none | used to interpret semantics of time expressions | ||
tts:backgroundColor |
background-color |
[XSL 1.1] | -inherit |
1,6 |
tts:color |
color |
[XSL 1.1] | -inherit |
6 |
tts:direction |
direction |
[XSL 1.1] | -inherit |
|
tts:display |
display |
[CSS2] | only auto , none |
|
tts:displayAlign |
display-align |
[XSL 1.1] | -inherit |
1 |
tts:extent |
width , height |
[XSL 1.1] | shorthand property | |
tts:fontFamily |
font-family |
[XSL 1.1] | -inherit , extends generic family names |
1 |
tts:fontSize |
font-size |
[XSL 1.1] | -inherit |
1,7 |
tts:fontStyle |
font-style |
[XSL 1.1] | -inherit , -backslant |
1 |
tts:fontWeight |
font-weight |
[XSL 1.1] | -inherit , -bolder , -lighter ,
-<number> |
1 |
tts:lineHeight |
line-height |
[XSL 1.1] | -inherit , -<number> ,
-<space> |
1 |
tts:opacity |
opacity |
[CSS3 Color] | -inherit |
|
tts:origin |
top , left |
[XSL 1.1] | shorthand property | |
tts:overflow |
overflow |
[XSL 1.1] | -inherit , -auto ,
-error-if-overflow |
|
tts:padding |
padding |
[XSL 1.1] | -inherit |
8 |
tts:showBackground |
showBackground |
[SMIL 2.1] | -inherit |
|
tts:textAlign |
text-align |
[XSL 1.1] | -inherit |
1 |
tts:textDecoration |
text-decoration |
[XSL 1.1] | -inherit |
1,9,12 |
tts:textOutline |
text-shadow |
[XSL 1.1] | -inherit |
10,12 |
tts:unicodeBidi |
unicode-bidi |
[XSL 1.1] | -inherit |
1 |
tts:visibility |
visibility |
[XSL 1.1] | -inherit , -collapse |
|
tts:wrapOption |
wrap-option |
[XSL 1.1] | -inherit |
1 |
tts:writingMode |
writing-mode |
[XSL 1.1] | -inherit , +tblr |
1 |
tts:zIndex |
z-index |
[XSL 1.1] | -inherit |
1 |
xml:id |
xml:id |
[XML ID] | complies with model | |
xml:lang |
xml:lang |
[XML 1.0] | complies with model | |
xml:space |
xml:space |
[XML 1.0] | see notes | 11 |
Note:
Attribute name and/or value(s) are normalized to use lowerCamelCase naming convention.
Restricted to expressing a clock value that denotes one of the following
in accordance to whether the parameter expressed by the
ttp:timeBase
attribute is media
,
smpte
, or clock
, respectively: (1) an offset from
an implicit syncbase that is linked to a media time line, (2) an event time
that represents the occurrence of an implicit media marker, or (3) a
wall-clock time.
Syntactically subsets and supersets the [SMIL
2.1] Clock-value
syntax as follows: (1) requires
non-negative Full-clock-value
or Timecount-value
;
(2) if Full-clock-value
then hours must be two or
more digits; (3) if Timecount-value
, then metric must
be specified; (4) uses m
as alias for min
metric
to denote minutes; (5) adds f
and t
metrics
denoting frames and ticks, respectively; (6) adds alternative expression of
optional Fraction
in Full-clock-value
by
specifying frame count or frame count with subframe count.
Interpretation of time expression is further constrained by parameters
expressed by ttp:clockMode
, ttp:dropMode
,
ttp:frameRate
, ttp:frameRateMultiplier
,
ttp:markerMode
, ttp:subFrameRate
,
ttp:tickRate
, and ttp:timeBase
attributes.
Uses subset of named colors from model to which two aliases are added as
follows: magenta
as fuchsia
, and
cyan
as aqua
.
If not specified, then parallel (par) container semantics apply to the element types specified by 10.2.4 timeContainer.
Restricts size to length specification which can be a percentage; adds optional second length (or percentage) for specifying separate horizontal and vertical scaling of glyph's EM square.
Expressed in terms of writing mode relative padding properties rather than absolute padding properties.
Excludes blink
and no-blink
values.
Uses only one length specification instead of two, where one length defines distance of outline effect from nominal edge of glyph contour outline perpendicular to point of glyph contour. Percentage lengths are also added to express outline effect in relative to font size. Outline effects are intended to be drawn both outside of outer closed contours and inside of inner closed contours.
On root element, default attribute value specified as
default
, which is defined in terms of whitespace
normalization. Semantics of preservation and default normalization are
defined in terms of presentation semantics by 7.2.3 xml:space.
Defined to be inheritable.
This appendix specifies the compliance of this specification with the requirements and guidelines defined by QA Framework Specifications Guidelines [QAF SG].
Note:
No feature is deprecated by this version of this specification.
Note:
When making normative references to external specifications, specific clauses or sections are cited.
See also J Vocabulary Derivation.
Test assertions and test suites will be provided prior to entering Proposed Recommendation (PR) phase.
See criterion #3 in 3.2 Processor Conformance and definition of TTML Abstract Document Instance.
No feature is deprecated or obsoleted by this version of this specification.
TTML Content is designed to support streamability by implementing the following properties:
can be progressively encoded (i.e., does not require computing subsequent data prior to sending current data);
can be progressively decoded (i.e., does not require forward references, but uses only reverse references when necessary);
does not require dereferencing (and subsequent loading) of any resources other than TTML Content (i.e., no embedded URIs);
does not support alternative content forms (e.g., different language, graphics formats, time bases) in a single document;
has timing structure compiled into inline format that makes possible a temporal ordering of content that follows temporal presentation order;
constrains content models to prevent arbitrary nested content structures;
One possible means by which TTML Content may be streamed is to partition a Document Instance's information set into non-overlapping fragments, where one particular fragment, call it the root fragment, represents the front matter (head) of the Document Instance as well as its top level structural elements, and other fragments represent content whose time intervals are expected to be active in parallel.
In applications that require arbitrary (random) entry into a stream, i.e., the property of being able to start reading data at an arbitrary data access unit, the root fragment will be repetitively transmitted (inserted) into the stream in order to permit a decoder to resynchronize and acquire sufficient structural information in the information set in order to interpret subsequent content fragments.
An example of such a fragmentation of a Document Instance is shown in Figure 3 – Fragment Streaming.
Note:
This specification does not define a transport buffer model or a decoder capabilities model.
In the absence of other requirements, it is recommended that a Document Instance be concretely encoded as a well-formed XML 1.0 [XML 1.0] document using the UTF-8 character encoding.
Note:
When using XML 1.0 [XML 1.0] as the concrete encoding of
TTML, only the following named character entities are defined:
&
, <
, and >
.
This appendix describes the intended semantics for interpreting time expressions in Document Instances.
Note:
It is expected that the information in this appendix will be elevated to normative status in a future revision of this specification.
Note:
The phrase local real time as used below is intended to model a virtual real time clock in the document processing context, where local means in the immediate proximity of the implementation of this processing context. The intent of defining relationships with this virtual clock is to establish a locally valid physical realization of time for didactic purposes.
Note:
The phrase play rate as used below is intended to model a (possibly variable) parameter in the document processing context wherein the rate of playback (or interpretation) of time may artificially dilated or narrowed, for example, when slowing down or speeding up the rate of playback of a Related Media Object. Without loss of generality, the following discussion assumes a fixed play(back) rate. In the case of variable play rates, appropriate adjustments may need to be made to the resulting computations.
When operating with the clock
time base, the following semantics
should be applied for interpreting time expressions, as defined by <timeExpression>, and their relationship
to media time and local real time.
The clock time base C
is related to
local real time R
expressed in an
arbitrary (implementation defined) epoch E
as follows:
|
Time value expressions, as denoted by a <timeExpression>, are related to clock
time C
as follows:
|
Note:
The frames and sub-frames terms and the frames
(f
) metric of time expressions do not apply when using the
clock
time base.
The clock time base C
is independent
of media time M
:
|
Note:
That is to say, timing is disconnected from (not necessarily proportional
to) media time when the clock
time base is used. For example, if
the media play rate is zero (0), media playback is suspended; however, timing
coordinates will continue to advance according to the natural progression of
clock time in direct proportion to the reference clock base. Furthermore, if
the media play rate changes during playback, presentation timing is not
affected.
When operating with the media
time base, the following semantics
should be applied for interpreting time expressions, as defined by <timeExpression>, and their relationship
to media time and local real time.
The media time base M
is related to
local real time R
expressed in an
arbitrary (implementation defined) epoch E
as follows:
|
Time value expressions, as denoted by a <timeExpression>, are related to media
time M
in accordance to the
ttp:frameRate
, ttp:subFrameRate
, and
ttp:frameRateMultipler
parameters as follows:
|
Note:
If the computed frameRateMultipler
ratio is not integral, then
effectiveFrameRate
will be a non-integral rational.
Note:
The above formalisms assumes that the Root Temporal Extent
corresponds with the beginning of a related media object. If this assumption
doesn't hold, then an additional offset that accounts for the difference may be
introduced when computing media time M
.
When operating with the smpte
time base, the following semantics
should be applied for interpreting time expressions, as defined by <timeExpression>, and their relationship
to media time and local real time.
If the computed value of the ttp:markerMode
parameter is
discontinuous
, then there is no direct relationship between time
expressions and media time M
or local
real time R
. In this case, time
expressions refer to synchronization events (markers) emitted by the Document
Processing Context when SMPTE Time Codes are encountered in the
Related Media Object.
Otherwise, if the computed value of the ttp:markerMode
parameter
is continuous
, then the relationships between time expressions and
local real time and media time are as described below in terms of a Synthetic
SMPTE Document Syncbase, here referred to as the SMPTE time base
S
.
|
The SMPTE time base S
is related to
the media time base M
as
follows:
|
Given the derived media time base as described above, then media time base
M
is related to the local real time
R
as described in N.2 Media Time Base above.
This section provides examples of the following common caption styles using TTML Content to obtain the desired behavior:
Pop-On Captions
Roll-Up Captions
Paint-On Captions
An example of paint-on captions. In this example, two regions are targeted with alternating, paint-on content, where content is timed using explicit sequential time containment rules. Each paragraph is non-overlapping in time and appears in the same single row of its targeted region.
<tt ttp:cellResolution="60 20" xml:lang="en" xmlns="http://www.w3.org/ns/ttml" xmlns:tts="http://www.w3.org/ns/ttml#parameter" xmlns:tts="http://www.w3.org/ns/ttml#styling"> <head> <layout> <region xml:id="r1" tts:color="white" tts:origin="10c 4c" tts:extent="40c 1c"/> <region xml:id="r2" tts:color="yellow" tts:origin="10c 8c" tts:extent="40c 1c"/> </layout> </head> <body> <div timeContainer="seq"> <p region="r1" dur="4s">Lorem ipsum dolor sit</p <p region="r2" dur="4s">Amet consectetur adipiscing elit</p> <p region="r1" dur="6s">Sed do eiusmod tempor incididunt labore</p> <p region="r2" dur="4s">et dolore magna aliqua</p> <p region="r1" dur="7s">Ut enim ad minim veniam quis, nostrud</p> </div> </body> </tt> |
An example of roll-up captions. Roll-up effects are achieved by using overlapped time intervals, where zero, one, or two paragraphs appear in the region at a given time. Each paragraph consumes a single row (line) of the region since no wrapping occurs. Depending on whether a presentation processor supports smooth scrolling between adjacent synchronic intermediate document instances, the transitions, i.e., moving an old paragraph (line) out and a new paragraph (line) in, will be either smooth or discrete.
<tt ttp:cellResolution="60 20" xml:lang="en" xmlns="http://www.w3.org/ns/ttml" xmlns:tts="http://www.w3.org/ns/ttml#parameter" xmlns:tts="http://www.w3.org/ns/ttml#styling"> <head> <layout> <region xml:id="r1" tts:color="white" tts:origin="10c 4c" tts:extent="40c 2c"/> </layout> </head> <body> <div region="r1"> <p begin="0s" end="8s">Lorem ipsum dolor sit</p <p begin="4s" end="12s">Amet consectetur adipiscing elit</p> <p begin="8s" end="18s">Sed do eiusmod tempor incididunt labore</p> <p begin="14s" end="25s">et dolore magna aliqua</p> <p begin="18s" end="29s">Ut enim ad minim veniam quis, nostrud</p> </div> </body> </tt> |
An example of paint-on captions. Paint-on effects are achieved by using timed
span
elements in order to expose (paint) inline text units, e.g.,
words, over some time interval. Here, five paragraphs have their individual words
sequentially timed in order to paint one new word every second. The end of the
active duration of each inline element coincides with the end of the
div
element's parallel time container, so that once a word is
painted, it remains in the region (on its rendered line) until the
div
element's active time interval lapses.
<tt ttp:cellResolution="60 20" xml:lang="en" xmlns="http://www.w3.org/ns/ttml" xmlns:tts="http://www.w3.org/ns/ttml#parameter" xmlns:tts="http://www.w3.org/ns/ttml#styling"> <head> <layout> <region xml:id="r1" tts:color="white" tts:origin="10c 4c" tts:extent="40c 5c"/> </layout> </head> <body> <div begin="0s" end="25s"> <p> <span begin="0s">Lorem</span> <span begin="1s">ipsum</span> <span begin="2s">dolor</span> <span begin="3s">sit</span> </p> <p> <span begin="4s">Amet</span> <span begin="5s">consectetur</span> <span begin="6s">adipiscing</span> <span begin="7s">elit</span> </p> <p> <span begin="8s">Sed</span> <span begin="9s">do</span> <span begin="10s">eiusmod</span> <span begin="11s">tempor</span> <span begin="12s">incididunt </span> <span begin="13s">labore</span> </p> <p> <span begin="14s">et</span> <span begin="15s">dolore</span> <span begin="16s">magna</span> <span begin="17s">aliqua</span> </p> <p> <span begin="18s">Ut</span> <span begin="19s">enim</span> <span begin="20s">ad</span> <span begin="21s">minim</span> <span begin="22s">veniam</span> <span begin="23s">quis,</span> <span begin="24s">nostrud</span> </p> </div> </body> </tt> |
The editor acknowledges the current and former members of the Timed Text Working Group, the members of other W3C Working Groups, and industry experts in other forums who have contributed directly or indirectly to the process or content of this document as follows:
Glenn Adams, Thomas Bause-Mason, John Birch, Kees Blom, Bert Bos, Brad Botkin, Dick Bulterman, Frans de Jong, Mike Dolan, Martin Dürst, Donald Evans, Geoff Freed, Al Gilman, Giles Godart-Brown, Markus Gylling, Markku Hakkinen, Sean Hayes, Erik Hodge, Philipp Hoschka, Suzi Hyun, Michael Jordan, Masahiko Kaneko, Courtney Kennedy, George Kerscher, David Kirby, Andrew Kirkpatrick, Philippe Le Hégaret, Pierre-Anthony Lemieux, Chris Lilley, Jason Livingston, Monica Martin, Matthew May, Nigel Megitt, Thierry Michel, Frank Olivier, Soohong Daniel Park, Silvia Pfeiffer, Brian Raymor, David Ronca, Patrick Schmitz, David Singer, Craig Smithpeters, Andreas Tai, and Mohamed Zergaoui.
The editor wishes to especially acknowledge the following contributions by members: Micheal Dolan (SMPTE time codes, streaming; SMPTE liaison), David Kirby (introductory example document; SMPTE time codes, descriptive metadata; EBU/AAF liaison), Geoff Freed (styling and example images of style properties), Sean Hayes (advanced profile concepts, including applicative timing), Eric Hodge (timing), Thierry Michel (metadata), and Dave Singer (animation, scrolling).
The Working Group dedicates this specification to our colleague David Kirby.


(You can search any
file or page on this web site by following the steps found by clicking on
Search.)
Descendants of John Tschappat
[ Click on the red
arrow for a shortcut to the list of family trees on this site
s Click on the blue question mark for
assistance navigating among family trees
1 John Tschappat b. 4 July 1828 d. 13 Nov. 1912 (John Tschappat or Shappat or Shabbat served with the
116th OVI during the Civil War) Photo, Photo, Photo
... + Margaret Ferguson b. 15
Jan. 1837 d. 1928 m. 6 June 1854 Photo, Photo, Photo, Marriage Cert, Home Place, 1924
.. 2 William Tschappat b. 22 May 1857 d. 30 June 1858
.. 2 Amanda (Manda) Tschappat b. 8 Jan. 1856
.. 2 Oliver Tschappat b. 22 Feb. 1859 d. 5 April 1909
.. 2 David (Dave) Tschappat b. 22 Dec. 1860
.. 2 Louisa (Louise) Tschappat b. 26 May 1862
.. 2 Mary Ann Tschappat
b. 17 Jan. 1867 d. 26 June 1968 1878,
1924,
Photo,
Obit
..... + William Henry Mozena b. December 19, 1850 d. October 10, 1944 obit
....... 3 Olive Mozena b. 18 Jan. 1892 d. 23 Dec. 1986 buried the
....... 3 Eva Mozena b. 25 June
1896 in
.......... + Ralph Everett Rose b.
31 March 1898 d. 2 April 1962 in
............ 4 Arlene Rose b.
10 Nov. 1922 d. 5 Nov. 1997 1924
............ 4 Dwain Ralph Rose
b. 22 Aug. 1929 d. 26 Dec. 2007 buried in Rose Hill Cemetery
in Rifle, Colorado
............... + Kathleen Phyllis Houchin b.21 March 1930 d. 24 Jan. 2006 buried in
Rose Hill Cemetery in Rifle, Colorado (dau. of Harley Houchin b. 11 Jan. 1903 d. 22 Sept. 1958 and Marie
M.Kees b. 19 Sept. 1901 d. 9 Aug. 1970)
................. 5 Larry Dwain Rose b. 9 Feb. 1948 in
................. 5 Gail Kathleen Rose
b. 17 Aug. 1952 in
.................... + Schoeppner
................. 5
Brenda Jean Rose b. 28 Sept. 1955
in
.................... + Marc Roland
Moen b. 1 Sept. 1950 in
...................... 6 Moriah Jean Moen born and died on 5 Dec. 1981
...................... 6 Michalee Rose Moen
b. 30 March 1983 in Whitefish,
...................... 6 Drew Roland Moen b. 4 Feb. 1988 in Whitefish,
....... 3
.. 2 Alice
Tschappat b. 7 May 1868 1878
.. 2 Harriet (Hattie) Tschappat b. 13 April 1874 d.
1965 Photo, Photo
.. 2 Emily (Emma)Tschappat
b. 3 July 1875 d. 14 Sept. 1910 1892,
Photo, Photo, Photo,
death cert
..... + Fred Duff Photo
.. 2 Charles
(Charley) Tschappat b. 12 April 1877 d. 1926 (fell off of an oil derrick in
Provided by: Brenda Moen
Click here for the Short-Cut Table of Contents


Generation of Random RGB Bitmap Image using Random.org API | Welcome
Click Here to Keep Generating Random RGB BitMap Images Below
Your browser does not support the HTML5 canvas tag.


New York Times Search
Complete Access to All Available Articles
Search Term
Number of Records to Retrieve
Start Year (Optional)
End Year (Optional)
Search
Clear Results


3 December 2003
Disease Outbreak Reported
As of 2 December 2003, the Ministry of Health of the Republic of the Congo has reported a total of 47 cases, including 28 deaths, of Ebola haemorrhagic fever (EHF) in Mbomo District, Cuvette Ouest Department (See previous report). Ninety-seven contacts are being followed-up.
A team of experts from WHO Geneva, and the Global Outbreak Alert and Response Network have joined the team already in the field, and will contribute to epidemiological surveillance, social mobilization and public health education, and support for diagnostics.


Workspace limits¶
This document provides a list of limits of the WSS.
Limits¶
| Parameter | Limit |
|---|---|
| Maximum RPC call size | 1.005GB |
| Maximum object size | 1GB |
| Maximum total size of returned objects | 1GB |
| Maximum provenance size | 1MB |
| Maximum user metadata size | 16000B |
| Maximum total size of user metadata key / value pair | 900B |
| Maximum total size of autometadata key / value pair | 900B |
| Maximum memory use for sorting objects | 200MB |
| Maximum object_infos returned by list_objects | 10000 |
| Maximum workspace references per save | 100000 |
Notes on sorting¶
The workspace service sorts the contents of all objects before MD5 calculations, serialization, and storage.
When sorting objects, object mapping and structure keys in a single path from the object root to a single object leaf are stored in memory at one time. The memory limit applies to these keys plus the memory required for the object itself.
Objects > 100MB in size are dumped to disk, so the maximum memory allowed for keys is 200MB. Objects < 100MB are kept in memory, so the maximum memory allowed is 200MB - object size.
Thus, objects may violate this limit if 1) they have very large maps, 2) have many very large keys in the same map, or 3) have very deeply nested maps (which probably still need to be fairly large).
As a point of reference, sorting a 550MB Network object required only ~10MB of memory for keys.
Notes on workspace references¶
The workspace service supports a maximum of 100,000 object references (e.g. a reference specified by @id ws in a typespec) per saveObjects() call. The references may be in a single object, or spread across many objects.
References that are duplicated in a single object only count once towards this limit.


Administrator
Administrator
GIG
Dashboard
Job Categories
View all categories
Create new category
Job Applications
Refund Requests
Log out
Create new category
Home
Job Category
Create
Create new category
Category Name
Cancel
Create


Home
Register
Log In
login
Username
Password
remember
forgot your password?
click here
new user?
create new account


|
BL3 SDK
0.0.1
Borderlands 3 Class Documentation
|
#include <BL3_GbxAI_structs.hpp>
Public Attributes | |
| class UClass * | Action |
| struct FGbxBlackboardKeySelector | Target |
| struct FVector | LocalOffset |
| struct FVector | TargetOffset |
| struct FName | TargetSocket |
| float | Speed |
| float | AnglePercent |
| float | MaxPrediction |
| bool | bDoNavigationTest |
| bool | bDoCollisionTest |
| bool | bAddTargetRadius |
| unsigned char | UnknownData00 [0x1] |
| float | UseExactLocationDistance |
| float | TestPeriod |
| bool | bCanStartWhileFalling |
| unsigned char | UnknownData01 [0x7] |
| class UClass* Action |
| float AnglePercent |
| bool bAddTargetRadius |
| bool bCanStartWhileFalling |
| bool bDoCollisionTest |
| bool bDoNavigationTest |
| struct FVector LocalOffset |
| float MaxPrediction |
| float Speed |
| struct FGbxBlackboardKeySelector Target |
| struct FVector TargetOffset |
| struct FName TargetSocket |
| float TestPeriod |
| unsigned char UnknownData00[0x1] |
| unsigned char UnknownData01[0x7] |
| float UseExactLocationDistance |


1 They are religious beyond measure, more than any other people; and the following are among their customs. They drink from cups of bronze, which they clean out daily; this is done not by some but by all.
2 They are especially careful always to wear newly-washed linen. They practise circumcision for cleanliness' sake; for they would rather be clean than more becoming. Their priests shave the whole body every other day, so that no lice or anything else foul may infest them as they attend upon the gods.
3 The priests wear a single linen garment and sandals of papyrus: they may have no other kind of clothing or footwear. Twice a day and twice every night they wash in cold water. Their religious observances are, one may say, innumerable.
4 But also they receive many benefits: they do not consume or spend anything of their own; sacred food is cooked for them, beef and goose are brought in great abundance to each man every day, and wine of grapes is given to them, too. They may not eat fish.
5 The Egyptians sow no beans in their country; if any grow, they will not eat them either raw or cooked; the priests cannot endure even to see them, considering beans an unclean kind of legume. Many (not only one) are dedicated to the service of each god. One of these is the high priest; and when a high priest dies, his son succeeds to his office.


Senate sessions suspended until Dec. 9 to give way to bicam on GAB, SEAG
by Vanne Elaine TerrazolaSessions in the Senate will be suspended until December 9 in anticipation of an upcoming holiday and road closures in Pasay City for the 30th Southeast Asian Games (SEAG), as well as the bicameral conference committee meetings on the proposed 2020 national budget.
Senate Majority Leader Juan Miguel Zubiri said the Upper Chamber decided to hold off its afternoon sessions next week due to the special non-working holiday in Pasay City Monday, December 2, for the celebration of the city’s foundation day.
Several roads going to the Senate will also be closed in the next few days for SEAG events in the World Trade Center, Philippine International Convention Center, and SM Mall of Asia.
Majority of the senators will also be attending the bicameral conference committee meeting to thresh out with their counterparts in the House of Representatives the differing provisions of their versions of the P4.1-trillion General Appropriations Bill.
“The bicam members from the Senate [panel] are 15, so if they would attend the bicam, we won’t have quorum,” Zubiri told reporters.
“That is why leadership decided that we just adjourn till the 9th,” he said.
The 15-man Senate panel to the bicameral conference committee is led by Senator Juan Edgardo M. Angara, chairman of the Senate Committee on Finance. Members of the Senate panel are Senate President Pro Tempore Ralph Recto, Senate Minority Leader Franklin Drilon, Senators Panfilo Lacson, Cynthia Villar, Pia Cayetano, Christopher Lawrence Go, Richard Gordon, Imee Marcos, Joel Villanueva, Risa Hontiveros, Nancy Binay, Grace Poe, and Francis Pangilinan.
They will sit down with the 23-member delegation of the House of Representatives to the bicam starting Friday, November 29.


| < Day Day Up > |
15.1 OverviewAssuming that you already have an origin server in place, you need to move it to a different IP address or TCP port. For example, you can (1) install Squid on a separate machine, (2) give the origin server a new IP address, and (3) give Squid the origin server's old IP address. In the interest of security, you can use non-globally routable addresses (i.e., from RFC 1918) on the link between Squid and the backend server. See Figure 15-1. Figure 15-1. How to replace your origin server with SquidAnother option is to configure Squid for HTTP interception, as described in Chapter 9. For example, you can configure the origin server's nearest router or switch to intercept HTTP requests and divert them to Squid. If you don't have the resources to put Squid on a dedicated system, you can run it alongside the HTTP server. However, both applications can't share the same IP address and port number. You need to make the backend server bind to a different address (e.g., <IP_ADDRESS>) or move it to another port number. It might seem easiest to change the port number, but I recommend changing the IP address instead. Changing the port number can be problematic. For example, when the backend server generates an error message, it may expose the "wrong" port. Even worse, if the server generates an HTTP redirect, it typically appends the nonstandard port number to the Location URI: HTTP/1.1 301 Moved Permanently Date: Mon, 29 Sep 2003 03:36:13 GMT Server: Apache/1.3.26 (Unix) Location: http://www.squid-cache.org:81/Doc/ If a client receives this response, it makes a connection to the nonstandard port (81), thus bypassing the server accelerator. If you must run Squid on the same host as your backend server, it is better to tell the backend server to listen on the loopback address (<IP_ADDRESS>). With Apache, you'd do it like this: BindAddress <IP_ADDRESS> ServerName www.squid-cache.org Once you've decided how to relocate your origin server, the next step is to configure Squid. |
| < Day Day Up > |


Reports non-boolean methods whose names start with a question
word. Non-boolean methods that override library methods are ignored by this inspection.
Use the list below to specify question words which should only be used for boolean methods.
Powered by InspectionGadgets


>>Download the programme as a pdf (your browser needs to accept pop-up windows)
|
10:00
|
Registration opens
|
|
||
|
12:00
|
Lunch
|
|
||
|
|
Session 1: Amyloid structure. Chair: Per Hammarström
|
|
||
|
13:30-14:10
|
Amyloid fibril polymorphism in vitro and in vivo. Marcus Fändrich
|
Keynote
|
||
|
14:15-14:30
|
Does low pH generate the TTR C-terminal fragments seen in ATTR amyloidosis? Elisabeth Ihse
|
Selected abstract
|
||
|
14:30-14:50
|
Assembly of protein nanofibrils into macroscopic fibers . Ayaka Kamada
|
Selected abstract
|
||
|
14:50-15:10
|
NANO-SCALE INFRARED IMAGING OF β-SHEET STRUCTURES IN PRIMARY
NEURONS FROM TRANSGENIC MOUSE MODELS OF ALZHEIMER´S DISEASE. Oxana Klementieva |
Selected abstract
|
||
|
15:10-15:30
|
Lipid membranes catalyse fibril formation of the amyloid-β(1-42) peptide through lipid-fibril interactions that reinforce secondary pathways. David Lindberg
|
Selected abstract
|
||
|
15:30
|
Coffee
|
|
||
|
|
Session 2: Amyloid structure. Chair: Gunilla Westermark
|
|
||
|
16:00-16:20
|
Enhanced clearance of amyloid deposits by pharmacological stimulation of phagocytosis: a study in a transgenic mouse model of ATTRV30M amyloid neuropathy. Eleni Fella
|
Selected abstract
|
||
|
16:20-16:40
|
Transthyretin Promotes Conversion of Amyloid β into Non-Amyloid Assemblies by Interfering with the Process of Nucleation. Anders Olofsson
|
Selected abstract
|
||
|
16:40-17:00
|
Monomer-dependent secondary nucleation in amyloid formation. Sara Linse
|
Selected abstract
|
||
|
17:00
|
Poster session
|
|
||
|
19:00
|
Dinner
|
|
||
|
|
|
|
|
07:00
|
Breakfast
|
|
||
|
|
Session 3: Biophysics and biochemistry of oligomers. Chair: Astrid Gräslund
|
|
||
|
09:00-09.40
|
Fibril structures by solid-state NMR: how does this work, where are the pitfalls, and applications to Aβ amyloid fibrils. Anja Böckmann
|
Keynote
|
||
|
09:45-10:05
|
SAXS and NMR studies of fibrillating α-synuclein and its interaction with phospholipid bilayers as model for Parkinson’s disease pathogenesis. Ersoy Cholak
|
Selected abstract
|
||
|
10:05-10:25
|
High throughput sorting of amyloid β multiprotein aggregates. Himansu Chaudhary
|
Selected abstract
|
||
|
10:25-10:45
|
Structural model of the oligomeric human molecular chaperone DNAJB6 comprised of dimers and a site for interaction with aggregation-prone peptides at the dimer interface. Cecilia Emanuelsson
|
Selected abstract
|
||
|
10:45
|
Coffee
|
|
||
|
11:15
|
Session 4: CWD, prions & neurodegeneration. Chair: Ann-Christine Brorsson
|
|
||
|
11:15-11:55
|
Chronic Wasting Disease, prion disease in cervids. Sylvie Benestad
|
Keynote
|
||
|
12:00-12:20
|
Seeding barrier between hamster and human prion protein amyloid-like fibrils. Vytautas Smirvovas
|
Selected abstract
|
||
|
12:20-12:40
|
Bar-coding Neurodegeneration: Identifying Sub-cellular Effects of Human Neurodegenerative Disease Proteins using Drosophila Leg Neurons. Josefin Fernius
|
Selected abstract
|
||
|
12:40-13:00
|
Amyloid Aβ1-42 is selectively toxic for neurons, whereas glial cells produce mature fibrils with low toxicity in Drosophila. Maria Jonson
|
Selected abstract
|
||
|
13:00
|
Lunch
|
|
||
|
14:30
|
Poster session and coffee
|
|
||
|
16:30
|
Session 5: Molecular diagnostics. Chair: Lars Nilsson
|
|
||
|
16:30-17:10
|
Keynote lecture. Harry LeVine III
|
Keynote
|
||
|
17:15-17:35
|
Development of ligands selective for tau aggregates. Therese Klingstedt
|
Selected abstract
|
||
|
17:35-17:55
|
Amyloid Formation in the presence of CSF. Chris Dunning
|
Selected abstract
|
||
|
17:55-18:15
|
Correlating CSF and blood molecular biomarkers in early diagnostics of Alzheimer’s and Parkinson’s diseases. Ludmilla Morozova-Roche
|
Selected abstract
|
||
|
19:00
|
Dinner
|
|
||
|
|
|
|
|
07:00
|
Breakfast
|
|
||
|
|
Session 6: Functional Amyloid. Chair: Peter Nilsson
|
|
||
|
09:00-09:40
|
Keynote lecture. Joost Schmykowitz
|
Keynote
|
||
|
09:45-10:30
|
Coffee and checkout
|
|
||
|
10:30-10:50
|
Self-organizing amyloid in bacteria. Daniel Otzen
|
Selected abstract
|
||
|
10:50-11:10
|
Curli amyloid structures in Salmonella biofilms. Ferdinand X Choong
|
Selected abstract
|
||
|
11:10-11:30
|
Improved overexpression of Amyloid-β peptide by solubility enhancer NT* from spider silk Improved overexpression of Amyloid-β peptide by solubility enhancer NT* from spider silk. Henrik Biverstål
|
Selected abstract
|
||
|
11:30-11:45
|
The future of amyloidosis research. Per Hammarström
|
Concluding remarks
|
||
|
12:00
|
Lunch and departure
|
|
||
|
|
|
|


Held in conjunction with KDD 2014, the Data Ethics workshop addressed a broad spectrum of ethical issues in data collection, storage, analysis, and sharing.
The workshop was a forum to explore data science's potential ethical implications -- both positive and negative -- for data analytics practitioners and researchers in academia and industry. Perspectives from those in the humanities and social sciences were also welcome.
Topics
Relevant areas of interest include but are not limited to:
- Balancing transparency/openness vs. privacy/security
- Intentional and unintentional impact
- Balancing reward vs. risk of data usage
- Data use and re-use
- Theory vs. practice in data ethics
- Case studies of ethical issues that have arisen in data science
- "Hippocratic Oath for Data Scientists"
- Data ethics and the law
- Commercial / economic dimensions of data ethics
- Safe and effective structures for "data philanthropy"
- Data ownership vs. data as a public good
- What data can/should be collected in public
- Surveillance technologies: pros and cons
- Data anonymization/scrubbing, and data de-anonymization
- Cross-cultural differences in data ethics
- Human data processing and the ethics of microtasking/crowdsourcing
- Development of ethical norms and/or suggested checklists for data practitioners
Program
(Download printable PDF version of program.)
| 2:00-2:10 | Welcome |
|---|---|
| [Slides] | Kayla Jacobs (Technion: Israel Institute of Technology) |
| 2:10-3:00 | Data of Vulnerable Populations |
|
Data and Human Trafficking Mark Latonero (University of Southern California) |
|
|
[Paper] [Slides] |
Mining Data Related to Children: Ethical Challenges Daya Wimalasuriya (University of Moratuwa) Dejing Dou (University of Oregon) Dilini Wimalasuriya (Northshore College of Business and Technology) |
| 3:00-3:10 | Poster Pitches |
|
[Paper] [Slides] [Poster] |
Finding the Most Appropriate Auxiliary Data for Social Graph Deanonymization Priya Govindan (Rutgers University) Sucheta Soundarajan (Rutgers University) Tina Eliassi-Rad (Rutgers University) |
|
[Paper] [Slides] [Poster] |
Decision Tree Classification on Outsourced Data Koray Mancuhan (Purdue University) Chris Clifton (Purdue University) |
| 3:10-4:00 | Privacy |
|
[Paper] [Full Guidelines] [Slides] |
Ethical Privacy Guidelines for Mobile Connectivity Measurements Bendert Zevenbergen (Oxford Internet Institute) |
| [Paper] |
Considering Privacy in Predictive Modeling Applications Troy Raeder (Dstillery) Brian Dalessandro (Dstillery) Claudia Perlich (Dstillery) |
| 4:00-4:30 | Coffee Break |
| 4:30-5:20 | Philosophical Themes in Data Ethics |
|
[Paper] [Slides] |
Big Data, Ethics, and the Social Implications of Knowledge Production Ralph Schroeder (Oxford Internet Institute) Josh Cowls (Oxford Internet Institute) |
| [Paper] |
Data Mining and the Discourse on Discrimination Solon Barocas (Princeton University) |
| 5:20-6:00 | Summary Panel |
Participants
(View more participant photos from the workshop.)
- Solon Barocas (Princeton)
- Daizhou Chen (Dstillery Inc.)
- Chris Clifton (Purdue University)
- Josh Cowls (Oxford Internet Institute)
- Andrea Costa (Consultant Data Visualization)
- Brian Dalessandro (Distillery Inc.)
- Priya Govindan (Rutgers University)
- Francisco Grajales (University of British Columbia)
- Yulig Grinberg (Columbia University)
- Melissa Han (Dstillery Inc.)
- Derrick Harris (Gigaom)
- Dominique Haughton (Bentley University, Paris I University, Toulouse I University)
- T. Ryan Hoens (Microsoft)
- Avrom Jacobs (NormaTec)
- Kayla Jacobs (Technion: Israel Institute of Technology)
- Tim Kucejko (Freelance)
- Mark Latonero (Data & Society Research Institute)
- Koray Mancuhan (Purdue University)
- Carlos Mazariegos (Carnegie Mellon University)
- Catherine McGeoch (Amherst College, D-Wave, ACM)
- Troy Raeder (Distillery Inc.)
- Bernard Rous (ACM)
- Daya Wimalasuriya (University of Moratuwa)
- Ran Wolff (Yahoo Labs)
- Bendert Zevenbergen (Oxford Internet Institute)
Organizers & Contact
- Kayla Jacobs (Technion: Israel Institute of Technology)
- Robert Munro (Idibon)
For questions or comments, e-mail the organizers at
<EMAIL_ADDRESS>KDD 2014
The workshop was run in conjunction with the 20th ACM SIGKDD International Conference on Knowledge Discovery and Data Mining (KDD'14), whose special theme for 2014 was "Data Mining for Social Good."


You are welcome, so happy to visit my website,I'am Ehab Al-shrida , Telecommunication enginner have experience in multi domains including comercial and technical side, i have shift my career path to move to full stack web developer , which the domain i like, and i will use all Knowledge which i collect to enhance set of services to make life more easer, i always looking to shape life by code, which is our attractive technology will lead future for industry in the word .
languages:
- html
- css
- java script
- python
- SQL
- Git
- GitHub
- VS Code
- Docker
- Linux
- Messi
- Neymar
- Swariz
- Ineista
- Chabi
- Ibra
- leva
- POyul
- Alvis
- canti
- Abdul Aziz Al Ghurair School of Advanced Computing (ASAC) - Amman, Jordan Course work completed in Dec / 2021- Advanced Software Development in Full-Stack JavaScript.
- Albalqa’a applied university - Amman, jordan Bachelor of Telecommunication and software engineering
- Revton, Amman, jordan , Merchandising specialist, Mar 2018 – Mar 2020
- Cayan For Consulting, Irbid, Jordan, Consultant and Pre sale Engineer, Sep 2017– Dec 2017.
- Estarta, Amman, Jordan, Customer Support Engineer , Jan 2019 – Jun 2019.
- Hi Electronic technology, Amman, Jordan, maintenance Engineer, Aug 2016 – Dec 2016
- Orange , Amman, Jordan, Bss and Field Trainee, Jun 2015– Jun 2016.
Tools:
Top Ten Fav Football Players


Help Rabbit escape from escape from the mine shaft by jumping from rock to rock! Space = jump left-arrow = left right-arrow = right


Blog Archive
2012 |
Own domain |
|
Setting up Octopress |
||
Update |
||
Welcomeposted in Octopress |
2012 |
Own domain |
|
Setting up Octopress |
||
Update |
||
Welcomeposted in Octopress |


Product Main Container
Our Beer Title
OUR BEERS
First Product Container
Product Description
HURRY UP
GETLE CLEAN WETWIPES
ALC / VOL 5.2%
"Brewed according to the high quality standards of the company"
ENJOY !!
Product Image
Second Product Container
Product Image
Product Description
SENSITIVE WETWIPES
ALC / VOL 6.2%
"Our expensive kleenex aging produces a taste, smothness and a drinkability that you will never find in other beer at any price. "
Third Product Container
Product Description
FLAVOUR EXPLOSION WETWIPES
ALC / VOL 4.2%
"It is a blend of real fruit taste and beer. Small batch brewed in
traditional style. Crisp and uber refreshing. It is a perfect choice for all flavours."
Explosion Of 6 Pack
Product Image
Fourth Product Container
Product Image
Product Description
GERM REMOVAL WETWIPES
ALC / VOL 6%
"At kleenx vintage, we make flavours of the old fanshioned way, traditional beer with the hint of orange for a refreshing home style fruit taste without carbonation"