W3C home > Mailing lists > Public > www-smil@w3.org > October to December 1998


From: Henning Timcke <henning.timcke@werft22.com>
Date: Fri, 23 Oct 1998 20:48:56 +0200
Message-ID: <01BDFEC6.8E72A660@marketing.aart.ch>
To: "'Patrick Schmitz'" <pschmitz@microsoft.com>, "'Jacco van Ossenbruggen'" <Jacco.van.Ossenbruggen@cwi.nl>
Cc: "www-smil@w3.org" <www-smil@w3.org>
Please allow me some questions:

Is there a way to describe the +TIME part of HTML+TIME separated from HTML+TIME and HTML ?
Could the  +TIME part of HTML+TIME be used with SMIL ?
Could HTML+TIME documents be upgraded to XML conformance in the same way as HTML can be upgraded to XML conformance ?
What is the diffrence between HTML+TIME and BHTML:
from the HTML+TIME point of view ?
What is the diffrence between HTML+TIME and BHTML:
from the BHTML point of view ?
What makes an author choose HTML+TIME or BHTML or SMIL ?
Can the needs of authors today be separted from the future ?
Maybe we should look for a way to understand a subset of any language currently in use as SMIL (Synchronisation Markup Integration Language) instead of the *traditional* SMIL.

From my point of view

> >   - Timing markup
>> 	.. synchronization markup

can not be mixed with other aspects of any multimedia content contexted by any Markup Language.

Imagine you were the conducter of a philharmonic orchestra, what you are doing is: being in charge of timing and synchronsation. This job has to  be done, without playing any of the many many instrument that have to be played (well conducted) in a philharmonic orchestra.

Timeing and synchronization should be similar to CSS.

Looking forward to your answers -


-----Ursprüngliche Nachricht-----
Von:	Patrick Schmitz [SMTP:pschmitz@microsoft.com]
Gesendet am:	Freitag, 23. Oktober 1998 18:24
An:	Henning Timcke; 'Jacco van Ossenbruggen'
Cc:	www-smil@w3.org
Betreff:	RE: SMIL and HTML+TIME

Actually, there is little in the HTML+TIME proposal that precludes
application to XML (see also the W3C comments on the submission).  We
specifically included support for more abstract control of XML "sprinkled"
elements.  Nevertheless, much of the web content is HTML based, and many
authors have a large investment in HTML at this point.  It is a good thing
to look forward, but we must also aknowledge the needs of authors today.

Thanks for your comments -


> -----Original Message-----
> From:	Henning Timcke [SMTP:henning.timcke@werft22.com]
> Sent:	Thursday, October 22, 1998 10:45 AM
> To:	'Jacco van Ossenbruggen'; Patrick Schmitz
> Cc:	www-smil@w3.org
> Subject:	AW: SMIL and HTML+TIME
> IMHO you should rethinkig HTML + TIME on a XML Basis to keep SMIL smiling
> Henning Timcke
> Ideen Werft22 GmbH
> -----Ursprüngliche Nachricht-----
> Von:	Jacco van Ossenbruggen [SMTP:Jacco.van.Ossenbruggen@cwi.nl]
> Gesendet am:	Donnerstag, 22. Oktober 1998 09:43
> An:	Patrick Schmitz
> Cc:	www-smil@w3.org
> Betreff:	Re: SMIL and HTML+TIME
> Patrick Schmitz wrote:
> ..
> > > XML+Anything
> > >
> > > The superimposing of TIME constructs on HTML could be applied to
> > > superimposing other construct sets on documents of other XML DTDs as
> > > well.  Defining this type of superimposing is a problem on a higher
> > > level that applies to many formats.  Solving this problem is 
> > > currently
> > > the domain of several W3C activities.  If/when the problem is 
> > > solved,
> > > SMIL would be a more appropriate DTD for putting through the
> > > superimposing mechanism than TIME.
> > >
> > [Patrick]  I am not clear on what you are saying.  If SMIL is aligned
> with
> > the activities you allude to, then HTML+TIME should be as well.  If not,
> > then there is a more basic problem at hand.  Perhaps you could explain a
> bit
> > further what you mean?
> [Jacco] What I tried to say is that HTML+TIME uses elements from SMIL in 
> HTML, and that this can be seen as just a special case of the problem of
> mixing elements from multiple DTDs in general. Solving this problem is 
> probably behind the scope of the HTML and SYMM groups, since it involves 
> issues (partly) addressed by XML namespaces and XML architectures 
> (a la XLink),  mixing HTML/XML etc.  
> ..
> Patrick Schmitz wrote:
> > 
> > The modularization that I proposed divides the functionality into 4
> areas:
> > 
> >   - Timing markup
> > 
> >   - Media elements and synchronization markup
> > 
> >   - Conditional delivery controls (switch and test attributes)
> > 
> >   - Layout
> [Jacco] Can you explain the difference betweeen timing and
> synchronization markup?
> Jacco
Received on Friday, 23 October 1998 14:51:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:22 UTC