W3C home > Mailing lists > Public > public-websignage@w3.org > November 2012

Re[4]: Gap analysis: SMIL

From: Futomi Hatano <futomi.hatano@newphoria.co.jp>
Date: Wed, 28 Nov 2012 18:47:54 +0900
To: Kai Hendry <hendry@webconverger.com>
Cc: public-websignage@w3.org
Message-Id: <20121128184754.1E17.17D6BAFB@newphoria.co.jp>
On Tue, 6 Nov 2012 11:12:56 +0800
Kai Hendry <hendry@webconverger.com> wrote:

> Hello there from Malaysia, :)
> Some quick comments on
> http://www.w3.org/community/websignage/wiki/Web-based_Signage_Use_cases_and_Requirements#R1._Making_contents_using_a_declarative_approach

Dear Kai,
I'm sorry for my delay.
Thanks for your comments.

> HTML as we know offers several ways to do animations:
> * declaratively http://dev.w3.org/csswg/css3-animations/
> * video
> * canvas
> * WebGL
> You can see these technologies already supported in browsers today,
> for example point your browser to http://renewsolution.com/ for a
> demo.
> I don't see the point of defining yet another way to do animations
> with "we can use data-* attributes specified in HTML5 specification.".
> Could you please provide an example?

Consider how to achieve SMIL approach using HTML.
SMIL allows this:

<img src="pic.png" dur="16s" left="0" top="0" width="2560">
  <animate from="0" to="-1280" begin="0s" dur="16s" />

This approach is very simple for creating contents.
Besides, the animation will happen in SMIL browsers.

HTML doesn't allow the snippet  above because HTML doesn't
define <animate>, @dur, @from, @to, @begin, etc.
If we adopt this approach using HTML, we can use @data-*.

This HTML snippet is valid:

<img src="pic.png"
  data-dur="16s" data-left="0" data-top="0" width="2560"
  data-animate="{from:0, to:-1280, begin:'0s', dur:'16s'}">

As you know, no animation will happen in HTML browsers
preparing only this HTML snippet.
If javascript and css libraries handling above annotations are
developed, we can achieve simple transitions of ads using
a declarative approach like SMIL.

> I'm not sure I can agree to "A declarative approach make creating
> contents cost-effective." This reminds me of xforms and xhtml2.

I don't think so.
If so, why is SMIL used widely in signage industry?

> Admittedly authoring Web content is always a little tricky, but that
> doesn't mean it's not possible. There are good CMSes available today
> using a range of HTML compatible technology such as Google docs
> Presenter that meet your requirements for the "Basic advertisement"

A declarative approach make developing CMSs easier.
If we can use CMSs for signage contents, creating content will
be cost-effective.
I can't imagine using Google docs for creating signage contents.
How do you control playlists? How do you control transition effects?
How do you control durations for each ads?
Existing HTML CMSs such as Google docs don't meet even the
requirement for the "Basic advertisement". 

> Then there is the sentence "Furthermore, this could achieve
> interoperability among terminals using ordinary web browser." which
> doesn't fit into the SMIL proposal.

If SMIL were implemented in ordinary web browsers,
the sentence would be correct.
We listed all possibilities in the "Gap analysis".
Of course, I know it's unlikely actually.
But no one can bet that for now.

> The big advantage of Web signage compared to other signage mediums is
> that one can discover Web content displayed upon "Web signage". That a
> member of the public can load the same Web content on their mobile
> browser or when they get home with their desktop browser. 

Could be.
But I think it isn't big advantage.
I've never heard such scenario.
If I were an advertiser, I would prepare dedicated contents
for PCs or smartphones.

Best regards,

Newphoria Corporation
Chief Technology Officer
Futomi Hatano
Received on Wednesday, 28 November 2012 09:47:35 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 2 November 2017 07:33:14 UTC