Steve Bennett | 1 May 2003 18:04
Picon
Picon

Time Limited Links in HTML+TIME


Hi

Can anyone tell me how to do time limited links in HTML+TIME.  For
instance the equivalent of the SMIL

<area href="http://whatever.com" cords="10,10,100,100" dur="15s" />

Also, I read that the SMIL linking module is not implemented in
HTML+TIME since it just uses the trad HTML version.  How then can you
make a time limited hyperlink?

Also, how might internal hyperlinking be supported in HTML+TIME - e.g
the equivalent of

 <area href="#clip3" cords="10,10,100,100" dur="15s" />

Thanks

Steve Bennett

Patrick Schmitz | 1 May 2003 18:59

RE: Time Limited Links in HTML+TIME


Basically, you do the same thing as in SMIL language. I just tested it in
IE6 with a sequence of area elements synced to a sequence of text (so I knew
when the areas *should* be active). Works fine. If you have trouble, let me
know and I will post the example to the ludicrum demos site.

Seeking on hyperlinks does not work in IE. You can still do the internal
hyperlinking, but all you get is the spatial seek (scrolls the page). You
can make it work by adding a behavior that does the seeking (e.g. in an htc
or in script onclick handlers for the links). Unfortunately, for non-trivial
cases where you are seeking to elements deep within time containers that are
not active, the logic may be hard to get right. The spec describes it
clearly, but it is work. If you  have simpler cases, then you can use the
time2 DOM to do the seek as you need.

Patrick

> -----Original Message-----
> From: www-smil-request <at> w3.org [mailto:www-smil-request <at> w3.org]On Behalf
> Of Steve Bennett
> Sent: Thursday, May 01, 2003 9:04 AM
> To: www-smil <at> w3.org
> Subject: Time Limited Links in HTML+TIME
>
>
>
> Hi
>
> Can anyone tell me how to do time limited links in HTML+TIME.  For
> instance the equivalent of the SMIL
(Continue reading)

Sigurd Lerstad | 4 May 2003 17:58
Picon

spline animation


From spec:

*********
keySplines:
The values must all be in the range 0 to 1

********

I'm puzzled by this, if I understand correctly, This limits the possibility
to create smooth curves from one value to the next.

I agree that x1 and x2 should be limited to 0..1, but y1, y2 shouldn't have
that limitation.

Am I misunderstanding something?

thanks,

--
Sigurd Lerstad

Steve Bennett | 6 May 2003 17:08
Picon
Picon

Access Key & Unicode


Hi all,

I am attempting to implement a system for slide presentation over the web.  I have a main region containing a
sequence of graphics and audio within <PAR> tags, and below that, a region containing a list of buttons
allowing the user to navigate to the various slides within the presentation.

Now supposing the number of slides was greater than 10, how could one implement access keys for those
buttons?  Now on windows platforms if you press on the alt key and then do a sequence of numbers you can
produce characters to appear on screen. I'm wondering if that would work for me (e.g you could press ALT+17
and that would take you to slide 17).

Below is what alt + 1 to 10 looks like

☺☻♥♦♣♠•◘○◙

(I'm not sure if the mail relay will reproduce what I see before me but it is essentially)

a smiley with the fill white and the line black
a smiley with the fill black and the line white
a heart symbol
a diamonds symbol
a clubs symbol
a spade symbol
a dot
a white dot inside a black square
a circle with fill white and line black
a white circle enclosed within a black square

Anyway, my question is, does anyone know how to implement access Keys for non standard ascii characters?
(Continue reading)

Patrick Schmitz | 7 May 2003 22:26

RE: Access Key & Unicode


Hi Steve - 

I do not know what the SMIL Language players do, but accessKey support is not in IE (XHTML+SMIL includes it,
but IE does not support it).

I would think that an easier UI would include a TOC panel with a list of slides (e.g. by title), and then
hyperlinks or event-based timing that shows the associated slide.  You can even have that whole TOC hide
and show on a small button if you are concerned about real-estate. I have done this in IE for my own slides (I
use a simple XML schema for slides and then have different XSLT stylesheets to create the presentations).

Good luck - Patrick

> -----Original Message-----
> From: www-smil-request <at> w3.org [mailto:www-smil-request <at> w3.org]On Behalf
> Of Steve Bennett
> Sent: Tuesday, May 06, 2003 8:09 AM
> To: www-smil <at> w3.org
> Subject: Access Key & Unicode
> 
> 
> 
> Hi all,
> 
> I am attempting to implement a system for slide presentation over 
> the web.  I have a main region containing a sequence of graphics 
> and audio within <PAR> tags, and below that, a region containing 
> a list of buttons allowing the user to navigate to the various 
> slides within the presentation.
> 
(Continue reading)

Annie Chang | 10 May 2003 01:38
Picon
Favicon

events vs syncbases, what gets cleared during reset

Hello,
 
I have a question about what gets cleared during a reset. Under "resetting element state", #1 says that times associated with event-values, repeat-values, accesskey-values or added via DOM method call are cleared. Am I correct in thinking that event values are times that cannot be previously computed, such as media ends and user clicks? If so, does this mean that all resolved syncbase instances stay in the instance times lists for the lifetime of the program, even when the element gets reset? If so, how does the element computing its next interval figure out which ones not to use?
 
What is the desired behavior in the following example:
<par>
 <par id="p" begin="5s" dur="100s" >
 <img id="b" begin="a.begin+1s" end="9s"/>
 </par>
 <img id="a" repeatCount="5" begin="0s" end="3s"/>
</par>
What will happen at time 5s?
Will b begin at 1s into the media at time 5s since the computed time of a.begin+1s first happened at 4s? Or will it wait until time = 7s in to begin?
 
How about this one:
<par>
 <par id="p" begin="0s" dur="2s" repeatCount = "5">
 <img id="b" begin="a.begin+1s"/>
 </par>
 <img id="a" begin="0s" dur="3s" repeatCount="5"/>
</par>
 
What times does b start?
At 1s, it should start because it depends on a. What about at 2s, when it gets reset? If only events are cleared out of instance timelists and not syncbases, won't b always begin immediately when its parent container begins, since it is dependent on a, which will have begun long ago? This does not seem like it would be the desired behavior.
 
Thanks,
Annie
Colin Law | 12 May 2003 12:03
Picon
Picon

RE: Grouping Media Items


> > > Also, is there a way to group related items? For instance, 
> > > the animation
> > > and the associated text objects are related, however there is 
> > > nothing to
> > > relate these items specifically when all items (and there 
> > > many be many)
> > > are placed within the <par> elements as above.
> > [seema]
> > <par > is the only grouping agent here.
> 
> Do you think that a generic grouping element would be of use within
> SMIL? Although not a functional, or time based element, I think players
> and authoring tools could make use of some such meta element.
> 
> Thoughts?

Hi,

Following up on my previous question, would it be correct to nest <par>
tags used simply as a grouping mechanism?

For example,
<par>
	<audio ....>

	<!-- pseudo grouping 1 -->
	<par>
		<image begin="0" dur="3"...>
			<transitionFilter.../>
		</image>
		<animation begin="0" dur="3"...>
			<transitionFilter.../>
		</animation>
		<text begin="0" dur="3"...>
			<transitionFilter.../>
		</text>
	</par>

	<!-- pseudo grouping 2 -->
	<par>
		<image begin="2" dur="3"...>
			<transitionFilter.../>
		</image>
		<animation begin="2" dur="3"...>
			<transitionFilter.../>
		</animation>
		<text begin="2" dur="3"...>
			<transitionFilter.../>
		</text>
	</par>

	...etc

</par>

So we have an audio stream playing in parallel with 'groups' of other
media items which are roughly in sequence, but written in parallel (by
the top level par tag) to facilitate transition effects between the
'groups'

I am evaluating the potential of SMIL as a data format for a project I
am working on and so I am interested in what the language allows. I
think some kind of generic 'group' item, or meta data group tag, would
be useful in situations like this, however, as there does not appear to
be one within SMIL, is the above the correct approach?

Thanks
~Colin.

Yoshihisa Gonno | 17 May 2003 14:31
Picon
Picon

Proposal on SMIL 2.0 Extension


Dear All,

I'm pleased to inform you that our Submission request on SMIL 2.0
Extension[1] has been acknowledged and published by W3C[2].

[1] http://www.w3.org/Submission/2003/04/
[2] http://www.w3.org/TR/SMIL2-AuthExt/

------------------------------------------------------------------------
Abstract:

This submission is a proposal for resuming SYMM Working Group to improve
SMIL 2.0 Specification.

Originally SMIL was designed for describing interactive multimedia on
the Web. However, this proposal intends to seek out the possibility of
SMIL for professional multimedia authoring. Introducing SMIL-based
content authoring into professional multimedia production is also
expected to enhance the possibility of SMIL-based contents on the Web.

Depicting a number of requirements for professional multimedia authoring,
possible solutions are proposed by improving existing function modules
and appending additional function modules. Lightweight profiles are also
important to keep conformance between wide variety of authoring
functionality.
------------------------------------------------------------------------

I believe some of you on this ML already familiar with this because
originally I made a presentation of this idea at SMIL Europe 2003 in
February.  Now I would like to call your attention on this ML to our
proposal.  

We are still making continuing efforts to introduce SMIL-based XML
language to multimedia authoring systems.  That is expected not only to
change professional content production and content delivery, but also
expand the market of SMIL application.

I would like to encourage those who are interested in developing the
future possibility of SMIL to be involved in the discussion and future
working of SMIL.

I will be so glad to have your comments, suggestions and any interests.

Best regards,
Yoshihisa Gonno
  Platform Technology Center, Sony Corporation
  tel:+81-3-5448-4590 fax:+81-3-5448-4066 email:ygonno <at> sm.sony.co.jp

Yoshihisa Gonno | 17 May 2003 14:32
Picon
Picon

Re: Proposal on SMIL 2.0 Extension

Dear All,

> I believe some of you on this ML already familiar with this because
> originally I made a presentation of this idea at SMIL Europe 2003 in
> February.  Now I would like to call your attention on this ML to our
> proposal.

For those who were not there, I attach the slides of my talk to help you
to understand the overview of our proposal.

Best regards,
Yoshihisa Gonno
  Platform Technology Center, Sony Corporation
  tel:+81-3-5448-4590 fax:+81-3-5448-4066 email:ygonno <at> sm.sony.co.jp

SMIL 2.0 Extension for Professional Multimedia Authoring - Preliminary Investigation

Yoshihisa Gonno

ygonno <at> sm.sony.co.jp

Sony Corporation

2003.2.14

Outline

  • Background and Motivation: Why SMIL ?
    • to enlarge potential SMIL market
    • to innovate content production workflow
  • Requirements for Professional Multimedia Authoring
    • Material Identification
    • Content Description
    • Profiles, Conformance
  • Improvement of SMIL 2.0
    • Extension
    • Addtion
    • Re-definition, Clarification
    • Re-consideration

SMIL: Current Status

  • designed for multimedia content description on the Web
    • 1998.6: SMIL 1.0 W3C Recommendation
    • 2001.8: SMIL 2.0 W3C Recommendation
    • technically in good shape
    • precious resource on the Web
  • on the market ..
    • shortage (almost lack) of commercial SMIL contents
    • multi-codec (mpeg-1/2/4,qt,real,win,..) capability is required, rather than multimedia integration capability
    • standard DRM still not ready
    • DVD already on the market
      • Sony also seems one of suspects:|
  • for now ..
    • still under development on the commercial market

SMIL: Key to Success in Business

  • success in the CE market is indispensable
  • potential SMIL markets:
    • Low-end: Mobile
      • SMIL 2.0 Basic Profile ?
    • Midrange: PC, Web
      • SMIL 2.0 ? XHTML+SMIL Profile ?
    • High-end: TV, DVD, Digital Cinema, ..
      • why not ? making the best use of SMIL for professional content business
      • challenge: let SMIL go beyond the Web
      • SMIL Professional Profile ???
  • contents flow:
    • Production-site -> Consumer-site
    • in terms of professional content business:
      • Consumer Needs < SMIL Capability < Production Needs

Innovation: Media Authoring Process

  • Destructive Authoring - Conventional Approach

  • Non-Destructive Authoring - Prospective Approach

    • authoring descriptions usability, distributed authoring capability

Requirements for Professional Media Authoring Description Language

  • Material Identification
    • Unique Material Identifier (UMID)
    • Media Track Identification
    • Media Time Identification
    • Temporal Duration Media Clipping
    • Spatial Region Media Clipping
    • Intermediate Media Identification
  • Content Description
    • Metadata Description
    • Metadata Synchronization
    • Media Transition
    • Media Composition and Transformation
    • Animated Subtitles
  • Profiles, Conformance
    • variety of products must work properly together
  • in general: fidelity rather than interactivity or adaptivity

SMIL 2.0

  • 10 Groups of Modules
    • Structure Module
    • Media Objects Modules
    • Timing and Synchronization Modules
    • Layout Modules
    • Content Control Modules
    • Linking Modules
    • Animation Modules
    • Metainformation Module
    • Transition Effects Modules
    • Time Manipulations Module

Professional Media Clipping

Requirement: Temporal Duration Media Clipping
  • media clipping capability by referring embedded SMPTE Time Codes (TCs)
Limitation:
  • MediaClipping Module says:

    The clipBegin attribute specifies the beginning of a sub-clip of a continuous media object as offset from the start of the media object. This offset is measured in normal media playback time from the beginning of the media.

Proposal:
  • If the media have embedded time codes, the offset should be measured with the embedded time codes.
See next slide Affect: Media Objects Modules (Re-definition/Clarification)

Professional Media Clipping

CASE1: <ref src="media1" clipBegin="smpte=01:02:00:00" clipEnd="smpte=01:06:00:00"/> media1 |---------+++++++++++++++++++++---------| 8-minute-long 01:00:.. 01:02:00:00 01:06:.. 01:08:00:00 embedded TCs in media1 ref |+++++++++++++++++++| 4-minute-long 00:00:00:00 00:04:00:00 CASE2: <ref src="media2" clipBegin="smpte=00:02:00:00" clipEnd="smpte=00:06:00:00"/> media2 empty // |-------------------| 8-minute-long 00:02:.. 00:06:.. // 01:00:00:00 01:08:00:00 embedded TCs in media2 ref |---------| // 4-minute-long 00:00:.. 00:04:.. //

Media Type Casting

Requirement: Media Track Identification
  • extracting and handling individual types of media, e.g. video, audio, out of complex media
Limitation:
  • BasicMedia Module says:

    All of these media elements are semantically identical. When playing back a media object, the player must not derive the exact type of the media object from the name of the media object element.

  • How can we get media1 video with media2 audio ?
Proposal:
  • video element should represent video, audio element should represent audio, exclusively.
<par> <video src="media1"/> <audio src="media2"/> </par> Affect: Media Objects Modules (Re-definition/Clarification)

Media Track Identification and Destination

Requirement: Media Track Identification
  • manipulating individual tracks within a media material
    • a media material may consist of multiple tracks
Proposal: by XPointer-like URI fragment: <audio src="media1#track('A1')" cast="left"/> by attribute: <audio src="media1" track="A1" cast="left"/> Affect: Media Objects Modules (Extension)

Visual Area Clipping

Requirement: Spatial Region Media Clipping
  • media clipping capability by specifying coodinates
Proposal:
  • apply coords attribute to media object elements and time container elements
<video src="media2" coords="0%,0%,50%,100%"/> <seq coords="50%,0%,100%,100%"> <video src="media1"/> <video src="media2"/> </seq> Affect: Media Objects Modules, Timing and Synchronization Modules (Extension)

Media Transparency Modification

Requirement: Visual Media Transparency (Alpha-Blending) Proposal:
  • apply alpha attribute to media object elements and time container elements
<par alpha="0.5"> <video src="media1" alpha="0.8"/> <video src="media2" alpha="0.2"/> </par> Affect: Media Objects Modules, Timing and Synchronization Modules (Extension)

Media Time Addressing

Requirement: Media Time Identification
  • embedding Time Codes (TCs) into resulting media
Proposal:
  • apply SMPTE TCs to begin|end attributes
See next slide Affect: Timing and Synchronization Modules (Extension)

Media Time Addressing

<ref src="media1" begin="smpte=01:00:00:00" end="smpte=01:05:00:00"/> media1 |+++++++++++++++++++| 03:00:00:00 03:04:00:00 embedded TCs in media1 01:00:00:00 01:04:00:00 applied TCs to ref element <seq begin="smpte=01:00:00:00"> <ref src="media1"/> <ref src="media2"/> </seq> media1 |+++++++++++++++++++| 03:00:00:00 03:04:00:00 embedded TCs in media1 media2 |+++++++++++++++++++| 02:00:00:00 02:04:00:00 embedded TCs in media2 seq |+++++++++++++++++++++++++++++++++++++++| 01:00:00:00 01:04:00:00 01:08:00:00 applied TCs to seq element

Time Container Clipping

Requirement: Intermediate Media Identification
  • improvement of Time Container (par|seq) usability as Media Object
Proposal:
  • apply clipBegin|clipEnd attributes to time container elements
See next slide Affect: Timing and Synchronization Modules (Extension)

Time Container Clipping

<ref src="media0" clipBegin="smpte=01:02:00:00" clipEnd="smpte=01:06:00:00"/> Given media0 as a par element below: <par> <ref src="media1" begin="smpte=01:00:00:00"/> <ref src="media2" begin="smpte=01:03:00:00"/> </par> to be equivalent to a par element below: <par clipBegin="smpte=01:02:00:00" clipEnd="smpte=01:06:00:00"> <ref src="media1" begin="smpte=01:00:00:00"/> <ref src="media2" begin="smpte=01:03:00:00"/> </par>

Metadata Description

Requirement: Metadata Description
  • inclusion of non-RDF XML descriptions
    • e.g. MPEG-7 Descriptions
    • may be introduced with rdf:parseType="Literal", but this makes descriptions unnecessarily redundant
Proposal: <head> <metadata type="text/xml"> <mp7:mpeg7 xmlns:mp7="urn:mpeg:mpeg7:..."> .... </mp7:mpeg7> </metadata> <metadata type="application/rdf+xml"> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> .... </rdf:RDF> </metadata> </head> Affect: Metainformation Module (Extension)

Metadata Synchronization

Requirement: Metadata Synchronization
  • metadata synchronization with audio/video streams
    • e.g. MPEG-7 Binary Stream
Proposal:
  • using ref element is possible but ambiguous
  • should define another Media Object element ?
    • audio|video|img|animation|text|textstream
  • why not for metadata
    • meta|metadata elements are already in use for other purpose
    • metastream ?
Affect: Media Objects Modules (Extension)

Media Transition

Requirement: Transition Effects on Time Container Elements
  • improvement of Time Container (par|seq) usability as Media Object
Proposal:
  • allow transIn|transOut attributes to be applied to Time Container elements
Why not ? <par transOut="crossfade"> <ref src="media1"/> <ref src="media2"/> </par> rather than <par> <ref src="media1" transOut="crossfade"/> <ref src="media2" transOut="crossfade"/> </par> Affect: Transition Effects Modules (Extension)

Audio Transition

Requirement: Audio Transition
  • only visual behavior is defined, what about audio and other data ?
  • should be clearly defined
Proposal:
  • increase/decrease soundLevel along with transition progress
  • needs more consideration
Affect: Transition Effects Modules (Re-definition/Clarification)

Transformation Effects Modules

Requirement: Media Composition and Transformation Proposal:
  • follow the syntax of Transition Effects Modules BasicTransformations Module declare transformation element in head element, refer with transform attribute of media object element InlineTransformations Module apply transformationFilter element directly to Media Object Element
  • transformation effect types
    • visualDeform -- mosaic, frosting and crystal effects
    • colorEffect -- monotone, sepia and negative
    • chromaKey -- blue-screen
    • soundEffect -- hall, theater and stadium
Affect: SMIL 2.0 Modules (Addition)

Timed Text

Requirement: Animated Subtitles
  • single standard
    • Title, Subtitles, Captions, Baloons
Proposal:
  • W3C Timed Text Working Group will work on this !

Profiles, Conformance

Requirement: lightweight profile and conformance Proposal:
  • slim-down of minimum profile
    • SMIL 2.0 Basic Profile requires 11(10) modules
      • Structure Module
      • Media Object Modules -- BasicMedia
      • Layout Modules -- BasicLayout
      • Timing and Synchronization Modules -- BasicInlineTiming, MinMaxTiming, BasicTimeContainers, RepeatTiming, (SyncbaseTiming)
      • Content Control Modules -- BasicContentControl, SkipContentControl
      • Linking Modules -- BasicLinking
    • all is not necessary and too many from the professional content authoring viewpoint
    • Tiny Profile ? Core Profile ?
    • needs more consideration

Summary

  • Background and Motivation
    • to enlarge potential SMIL market
    • to innovate content production workflow
  • Requirements
    • Media Identification
    • Content Description
    • Profiles, Conformance
  • Improving SMIL 2.0
    • Extensions, Clarifications and Additions
    • lightweight profile and conformance to be investigated
  • Comments and suggestions are welcome
  • Let's resume W3C SMIL(SYMM) Working Group !

Thank you ! 

Attachment (projection.css): application/octet-stream, 4308 bytes
Jose Ramirez | 19 May 2003 17:25

Re: Proposal on SMIL 2.0 Extension


Yoshihisa Gonno wrote:

> Dear All,
> 
> I'm pleased to inform you that our Submission request on SMIL 2.0
> Extension[1] has been acknowledged and published by W3C[2].
> 
> [1] http://www.w3.org/Submission/2003/04/
> [2] http://www.w3.org/TR/SMIL2-AuthExt/
> 
> ------------------------------------------------------------------------
> Abstract:
> 
> This submission is a proposal for resuming SYMM Working Group to improve
> SMIL 2.0 Specification.
> 
> Originally SMIL was designed for describing interactive multimedia on
> the Web. However, this proposal intends to seek out the possibility of
> SMIL for professional multimedia authoring. Introducing SMIL-based
> content authoring into professional multimedia production is also
> expected to enhance the possibility of SMIL-based contents on the Web.
> 
> Depicting a number of requirements for professional multimedia authoring,
> possible solutions are proposed by improving existing function modules
> and appending additional function modules. Lightweight profiles are also
> important to keep conformance between wide variety of authoring
> functionality.
> ------------------------------------------------------------------------
> 
> I believe some of you on this ML already familiar with this because
> originally I made a presentation of this idea at SMIL Europe 2003 in
> February.  Now I would like to call your attention on this ML to our
> proposal.  
> 
> We are still making continuing efforts to introduce SMIL-based XML
> language to multimedia authoring systems.  That is expected not only to
> change professional content production and content delivery, but also
> expand the market of SMIL application.
> 
> I would like to encourage those who are interested in developing the
> future possibility of SMIL to be involved in the discussion and future
> working of SMIL.
> 
> I will be so glad to have your comments, suggestions and any interests.
> 
> Best regards,
> Yoshihisa Gonno
>   Platform Technology Center, Sony Corporation
>   tel:+81-3-5448-4590 fax:+81-3-5448-4066 email:ygonno <at> sm.sony.co.jp
> 
> 

It would be great to see those with the resources to take advantage
of what SMIL does to Multimedia. SMIL can take separate media files
and present it as one, but it also can allow the viewer to choose
and customize the audio/visual experience. An analogy would be
a restaurant customer choosing the foods that pleased their senses of
smell and taste, a Multimedia viewer watching a SMIL movie could now 
choose the audio and visual selections that would please those senses.

Choice is Good :)

Jose Ramirez


Gmane