- From: Futomi Hatano <futomi.hatano@newphoria.co.jp>
- Date: Wed, 16 Jan 2013 18:48:02 +0900
- To: ashimura@w3.org
- Cc: public-websignage@w3.org
On Fri, 11 Jan 2013 16:52:53 +0900 Kazuyuki Ashimura <ashimura@w3.org> wrote: > # Sorry but forgot to CC the list, so resending. > > On 01/11/2013 10:15 AM, Futomi Hatano wrote: > > On Thu, 10 Jan 2013 20:02:12 +0900 > > Kazuyuki Ashimura <ashimura@w3.org> wrote: > > > >> On 01/10/2013 06:37 PM, Sangwhan Moon wrote: > >>> Hello all, > >>> > >>> On 1/10/13 5:01 AM, Kazuyuki Ashimura wrote: > >>>> On 01/09/2013 08:55 PM, Futomi Hatano wrote: > >>>> I think using SCXML for a play list (or history of all the play lists) > >>>> would be a great idea. Also I 100% agree with you SCXML would fit the > >>>> use for control layer. > >>>> > >>>> FYI, as you might know, SCXML is expected to be used as the > >>>> Interaction Manager (=controller layer) for MMI Architecture [1]. > >>>> For example, one possible example of MMI-based multimodal Web > >>>> applications is a voice-ready game application which has GUI as well. > >>>> And it could consist of the following three parts: > >>>> > >>>> - SCXML-based Controller: Interaction Manager of MMI Architecture > >>>> which controls the flow of the game application > >>>> > >>>> - VoiceXML-based speech interface: Voice Modality Component of MMI > >>>> Architecture which handles speech input/output > >>>> > >>>> - HTML5-based graphical interface: GUI Modality Component of MMI > >>>> Architecture which handles keyboard/touch panel input and display > >>>> output > >>>> > >>>> Please see also the MMI Interoperability test report at: > >>>> http://www.w3.org/TR/mmi-interop/ > >>>> for the details of the example. > >>>> > >>>> > We can handle SCXML using JavaScript. > >>>> > 1. Get a SCXML file specified in JS or HTML from the originated web > >>>> server using XHR. > >>>> > 2. Parse the SCXML file using DOM3Core. > >>>> > 3. Show each content (e.g. an ad) marked up in HTML based on the > >>>> scenario defined in the SCXML. > >>>> > >>>> I agree handling SCXML as a data format to describe play lists using > >>>> JavaScript would be also a good idea. > >>> > >>> If it's a linear or simple branching playlist, using a state machine > >>> for this is overkill. And it would be good to keep in mind that XML is > >>> also less memory/processor cycle efficient than say, JSON when it > >>> comes to parsing and storing, due to the structural overhead. > >> > >> Probably we should concentrate on use cases and gap analysis first. > >> > >> And I personally think one of possible use cases is that advanced > >> vending machines (e.g., [1] and [2]) have kind of complicated > >> process flow and they even could store whole purchase history of > >> each specific user identified by his/her credit card or stored fair > >> card in the near future. > > > > SCXML could be used for such advanced vending machines. > > But I don't think it's best for the use cases. > > If I were to develop it using web technologies, I would use > > only JavaScript like web apps (or web games). > > > > Anyway, though I proposed a way to use SCXML as a play list, > > this doesn't mean that I support SCXML. > > I just show one of the possibilities for R1. > > If I set your expectations, I'm sorry in advance. > > > > To be honest, I believe that XML-based solutions such as SCXML > > won't be accepted by developers (including me) in practice > > at this time. > > > > Of course, I don't deny potential of SCXML for eternity. > > I think that our "Use cases and Requirements" shouldn't deny > > possibilities regardless whether it's the best solution or not, > > because no one can bet which solution is the best at this time. > > > > How about adding this phrase in the gap analysis for R1. > > > > [[ > > SCXML > > When contents are separated to a presentation layer and a control layer, > > it's possible to use HTML/CSS for a presentation layer and SCXML for a control layer. > > ]] > > That's fine by me. done. http://www.w3.org/community/websignage/wiki/Web-based_Signage_Use_cases_and_Requirements#SCXML Cheers, Futomi -- Newphoria Corporation Chief Technology Officer Futomi Hatano -- futomi.hatano@newphoria.co.jp http://www.newphoria.co.jp/
Received on Wednesday, 16 January 2013 09:48:15 UTC