Re: Overview of W3C technologies for mobile Web applications

2011-05-31 Thread Dominique Hazael-Massieux
Le vendredi 13 mai 2011 à 12:19 -0400, Arthur Barstow a écrit :
 Thanks for creating this Dom (FYI, I made some edits and updates yesterday).

Thanks! As you may have seen, I've just released a new version of that
document which includes your updates
http://www.w3.org/2011/05/mobile-web-app-state.html

 Re the overall positioning and scope of the document, it seems like the 
 document would be more useful if it was positioned more generally as a 
 survey of Standards for Web Applications. The definition of mobile, in 
 the context of devices, changes rapidly and it wasn't so long ago that 
 mobile devices meant monochrome phones running a WAP stack. If any of 
 the specs used for Web applications have particularly relevant mobile 
 characteristics/constraints, that could be documented in a new 
 Mobile/Mobility column.

Given that the time I can spend on this is funded for its mobile
orientation angle, I would rather its focus as is; now, if there is a
way to extract a mobile oriented from a more generic document, I would
be more than happy to contribute to the generic document.

If someone creates such a generic document with enough hooks for me to
extract the mobile-focused document, I'm also fine with producing the
tool that does the extraction.

But I probably wouldn't have the cycles to migrate the current
mobile-focused document into a more generic one with the proper hooks.

HTH,

Dom





Re: Overview of W3C technologies for mobile Web applications

2011-05-13 Thread Arthur Barstow

Hi Dom,

On May/12/2011 4:41 AM, ext Dominique Hazael-Massieux wrote:

Le jeudi 24 février 2011 à 16:03 +0100, Dominique Hazael-Massieux a
écrit :

As part of a European research project I'm involved in [1], I've
compiled a report on the existing technologies in development (or in
discussion) at W3C for building Web applications and that are
particularly relevant on mobile devices:
http://www.w3.org/2011/02/mobile-web-app-state.html
[...]
I can also look into moving it in a place where a larger community could
edit it (dvcs.w3.org, or www.w3.org/wiki/ for instance) if anyone is
interested in contributing.

Since I've received at least one offer to help keeping the page up to
date if moved to a wiki, I've moved a copy of the document above to the
wiki page at
http://www.w3.org/wiki/Standards_for_Web_Applications_on_Mobile

In the upcoming two weeks, I'll bring a number of updates to the
document for a new stable release at this of the month. Any help in
bringing the document up to date will be very welcomed!


Thanks for creating this Dom (FYI, I made some edits and updates yesterday).

Re the overall positioning and scope of the document, it seems like the 
document would be more useful if it was positioned more generally as a 
survey of Standards for Web Applications. The definition of mobile, in 
the context of devices, changes rapidly and it wasn't so long ago that 
mobile devices meant monochrome phones running a WAP stack. If any of 
the specs used for Web applications have particularly relevant mobile 
characteristics/constraints, that could be documented in a new 
Mobile/Mobility column.


-ArtB





Re: Overview of W3C technologies for mobile Web applications

2011-05-13 Thread Marcos Caceres

On 5/13/11 6:19 PM, Arthur Barstow wrote:

Hi Dom,

On May/12/2011 4:41 AM, ext Dominique Hazael-Massieux wrote:

Le jeudi 24 février 2011 à 16:03 +0100, Dominique Hazael-Massieux a
écrit :

As part of a European research project I'm involved in [1], I've
compiled a report on the existing technologies in development (or in
discussion) at W3C for building Web applications and that are
particularly relevant on mobile devices:
http://www.w3.org/2011/02/mobile-web-app-state.html
[...]
I can also look into moving it in a place where a larger community could
edit it (dvcs.w3.org, or www.w3.org/wiki/ for instance) if anyone is
interested in contributing.

Since I've received at least one offer to help keeping the page up to
date if moved to a wiki, I've moved a copy of the document above to the
wiki page at
http://www.w3.org/wiki/Standards_for_Web_Applications_on_Mobile

In the upcoming two weeks, I'll bring a number of updates to the
document for a new stable release at this of the month. Any help in
bringing the document up to date will be very welcomed!


Thanks for creating this Dom (FYI, I made some edits and updates
yesterday).

Re the overall positioning and scope of the document, it seems like the
document would be more useful if it was positioned more generally as a
survey of Standards for Web Applications. The definition of mobile, in
the context of devices, changes rapidly and it wasn't so long ago that
mobile devices meant monochrome phones running a WAP stack. If any of
the specs used for Web applications have particularly relevant mobile
characteristics/constraints, that could be documented in a new
Mobile/Mobility column.


I agree with Art.

Also, the packaging section is a little misleading. I would not say that 
AppCache is some kind of packaging format: it's a way of doing cache 
control (but does not package anything).


I have updated some widget-related bits...



Re: Overview of W3C technologies for mobile Web applications

2011-05-12 Thread Dominique Hazael-Massieux
Le jeudi 24 février 2011 à 16:03 +0100, Dominique Hazael-Massieux a
écrit :
 As part of a European research project I'm involved in [1], I've
 compiled a report on the existing technologies in development (or in
 discussion) at W3C for building Web applications and that are
 particularly relevant on mobile devices:
 http://www.w3.org/2011/02/mobile-web-app-state.html
 [...]
 I can also look into moving it in a place where a larger community could
 edit it (dvcs.w3.org, or www.w3.org/wiki/ for instance) if anyone is
 interested in contributing.

Since I've received at least one offer to help keeping the page up to
date if moved to a wiki, I've moved a copy of the document above to the
wiki page at
http://www.w3.org/wiki/Standards_for_Web_Applications_on_Mobile

In the upcoming two weeks, I'll bring a number of updates to the
document for a new stable release at this of the month. Any help in
bringing the document up to date will be very welcomed!

Dom





Re: Overview of W3C technologies for mobile Web applications

2011-05-12 Thread Michael[tm] Smith
Dominique Hazael-Massieux d...@w3.org, 2011-05-12 10:41 +0200:

 Since I've received at least one offer to help keeping the page up to
 date if moved to a wiki, I've moved a copy of the document above to the
 wiki page at
 http://www.w3.org/wiki/Standards_for_Web_Applications_on_Mobile
 
 In the upcoming two weeks, I'll bring a number of updates to the
 document for a new stable release at this of the month. Any help in
 bringing the document up to date will be very welcomed!

I have some things I think probably need adding, and realize the point is
that it's a wiki and I can add to it myself, but I probably can't make the
time to add anything this week. So for now at least, I just want to note
the following other wiki page:

  http://www.w3.org/wiki/BrowserTechnologies

...and I want to say it if you or anybody else has time to add relevant
specs from there, I think there probably are some that aren't included in
your page yet but probably should be.

  --Mike

-- 
Michael[tm] Smith
http://people.w3.org/mike



Re: Overview of W3C technologies for mobile Web applications

2011-03-09 Thread Dominique Hazael-Massieux
Hi Charles,

Le mardi 08 mars 2011 à 21:14 -0800, Charles Pritchard a écrit :
 InkML is a development relevant to mobile Web.
 Tablets and other input-rich devices are gaining in acceptance (and
 becoming easier to purchase).
 
 InkML is one of the few specs to put forward both a stream-based and
 archive-oriented format.

I see that there is ongoing discussions around the relationship between
InkML and DOM touch events:
http://lists.w3.org/Archives/Public/www-multimodal/2011Feb/0004.html

This may indeed make InkML a promising lead for capturing user input;
I'll see if I find a way to integrate it in the mobile web apps
standards document
http://www.w3.org/2011/02/mobile-web-app-state.html

If anyone has more input on how developers would actually use InkML as
part of their Web applications on mobile devices, that would be most
useful.

Thanks,

Dom





Re: Overview of W3C technologies for mobile Web applications

2011-03-08 Thread Richard Ishida


On 08/03/2011 15:08, Somnath Chandra wrote:

We have already started working on Mobile Rendering Engine and Fonts
development which would enable seamless display across platforms and
devices.


That's interesting.  Did you know about work currently under way 
involving Harfbuz to provide a small, universal rendering engine that 
can be used on mobile devices and other kinds of OS to do opentype 
rendering? [1]   Are you working on the same thing?  I'd hate to think 
that you are reinventing the wheel such that different systems are 
needed for different fonts...


RI


[1] http://behdad.org/text/

--
Richard Ishida
Internationalization Activity Lead
W3C (World Wide Web Consortium)

http://www.w3.org/International/
http://rishida.net/



Re: Overview of W3C technologies for mobile Web applications

2011-03-08 Thread Somnath Chandra
Hi Richards,
Thanks for the input. Yes we are aware of the work and investigating Indian 
Language /Scripts Complexities on that platform also. Certainly our idea is not 
to redo the same work and  to address specific issues of each Indic languages. 

Best Regards,
Somnath


On 03/08/11, Richard Ishida ish...@w3.org wrote:
 
 
 On 08/03/2011 15:08, Somnath Chandra wrote:
 We have already started working on Mobile Rendering Engine and Fonts
 development which would enable seamless display across platforms and
 devices.
 
 That's interesting.  Did you know about work currently under way involving 
 Harfbuz to provide a small, universal rendering engine that can be used on 
 mobile devices and other kinds of OS to do opentype rendering? [1]   Are you 
 working on the same thing?  I'd hate to think that you are reinventing the 
 wheel such that different systems are needed for different fonts...
 
 RI
 
 
 [1] http://behdad.org/text/
 
 -- 
 Richard Ishida
 Internationalization Activity Lead
 W3C (World Wide Web Consortium)
 
 http://www.w3.org/International/
 http://rishida.net/
 


-- 

Dr. Somnath Chandra
Scientist-D
Dept. of Information Technology
Govt. of India
Tel:+91-11-24364744,24301811
Fax: +91-11-24363099
e-mail :schan...@mit.gov.in


Re: Overview of W3C technologies for mobile Web applications

2011-03-08 Thread Charles Pritchard

InkML is a development relevant to mobile Web.
Tablets and other input-rich devices are gaining in acceptance (and 
becoming easier to purchase).


InkML is one of the few specs to put forward both a stream-based and 
archive-oriented format.


We'll be using it to serialize input between devices, recording time, 
and pressure data when available.


In relation to font rendering: though standard dialects and scripts are 
widely supported,
non-standard usage, personal usage, experimental / artistic expression 
are not part of the package.


That's an area where InkML will intersect with mobile rendering of 
linguistic data.

InkML and VoiceXML provide a standard means to transcribe language.
That's great for researchers and anthropologists.

The programmable canvas tag and audio tags, associated with the img tag 
and audio/video sources,
provide scientists with a standard structure to render transcribed 
vocalizations and movements.

InkML and VoiceXML enable their transcription.

The mobile web refers to sensor-rich, portable devices; two things which 
computers
generally aren't. Laptops are a kludge to carry, and sensor-rich devices 
are generally

used in scientific labs, not consumer desktops.

Pressure sensitive computing tablets have been available for years, but 
they did not gain wide acceptance
nor support. It was recent touch-based mobile devices which introduced 
the web to sensory-rich computing.


-Charles


On 3/8/2011 8:41 PM, Somnath Chandra wrote:

Hi Richards,
Thanks for the input. Yes we are aware of the work and investigating 
Indian Language /Scripts Complexities on that platform also. Certainly 
our idea is not to redo the same work and  to address specific issues 
of each Indic languages.


Best Regards,
Somnath

On 03/08/11, *Richard Ishida *ish...@w3.org wrote:


On 08/03/2011 15:08, Somnath Chandra wrote:
We have already started working on Mobile Rendering Engine and Fonts
development which would enable seamless display across platforms and
devices.

That's interesting.  Did you know about work currently under way 
involving Harfbuz to provide a small, universal rendering engine that 
can be used on mobile devices and other kinds of OS to do opentype 
rendering? [1]   Are you working on the same thing?  I'd hate to 
think that you are reinventing the wheel such that different systems 
are needed for different fonts...


RI


[1] http://behdad.org/text/

--
Richard Ishida
Internationalization Activity Lead
W3C (World Wide Web Consortium)

http://www.w3.org/International/
http://rishida.net/


--
Dr. Somnath Chandra
Scientist-D
Dept. of Information Technology
Govt. of India
Tel:+91-11-24364744,24301811
Fax: +91-11-24363099
e-mail :schan...@mit.gov.in




Re: Overview of W3C technologies for mobile Web applications

2011-03-07 Thread Dominique Hazael-Massieux
Hi Ben,

Le vendredi 25 février 2011 à 14:04 +, Ben Laurie a écrit :
  As part of a European research project I'm involved in [1], I've
  compiled a report on the existing technologies in development (or in
  discussion) at W3C for building Web applications and that are
  particularly relevant on mobile devices:
  http://www.w3.org/2011/02/mobile-web-app-state.html
 
 Nothing on security?

It does mention the work on CORS and the work around widgets security,
but there is no dedicated section on security — I'm not sure what would
appear there that would be particularly relevant on mobile devices, any
suggestion?

Thanks,

Dom





RE: Overview of W3C technologies for mobile Web applications

2011-03-07 Thread Dominique Hazael-Massieux
(trimming CC)

Hi Somnath,

Le samedi 26 février 2011 à 12:45 +0530, Somnath Chandra a écrit :
 This document is an excellent document. It gives present state-of-the
 art and roadmap ahead for development of Mobile Web. 
 Implementation of Mobile Web with South Asian complex scripts is a
 challenging task. In India we have 22 constitutionally recognized
 languages and 12 scripts. Therefore , as a lead in W3C Mobile Web ,
 Internationalization requirements and associcated complexities for
 Mobile Web implementation may also be a part of your document.

 If you desire , Swaran Lata , Director  W3C India Country Manager and
 myself  Dr. Somnath Chandra , Dy. country manager , W3C India would be
 happy to contribute.

It would be indeed very useful to get your perspectives on what
standards could help in getting mobile Web applications deployed across
many more languages and scripts.

I know Richard Ishida already provided some input on the bricks needed
to display non-Latin 1 pages in a blog post:
http://rishida.net/blog/?p=445

I wonder if this could be a starting point for something more formal
that could help in this space?

(I expect I'll get to hear some of your thoughts on this at the Mobile
Web Apps camp in WWW2011 http://www.w3.org/2011/03/w3c-track.html)

Thanks,

Dom





Re: Overview of W3C technologies for mobile Web applications

2011-03-07 Thread Dominique Hazael-Massieux
Hi Paul,

Le vendredi 25 février 2011 à 16:53 +0100, Paul Libbrecht a écrit :
 I definitely agree this is a useful deliverable; I wish more EU
 projects be as careful in their survey as that!

Thanks!

 I was looking to see if MathML was mentioned (I think it should as a
 future technology but it has almost zero coverage on the mobile world
 yet). But I realize that HTML is also not decomposed there. It seems
 to be assumed and mentioned in many places.
 
 Am I right?

The approach I've taken is to highlight the most relevant features in
specs across the large number of W3C groups for developing applications
on mobile devices.

While there are certainly use cases for display maths as part of mobile
app (e.g. for education), it hasn't struck me as a particularly
mobile-relevant feature, which is why I haven't included it. The fact
that it has very little implementation on mobile browsers doesn't help
either.

But I'd be happy to reconsider that position if you have further input
on this :)

 I would think a feature-by-feature analysis of what's in HTML4/5/XHTML
 and works on mobiles would be rather useful.

I would certainly love that as well, but I think it is also beyond what
I can possibly manage :)

That said, part of the MobiWebApp project is also to help on the
development of test suites for the relevant technologies, so maybe we'll
get some of that picture when this makes more progress.

Thanks for the feedback,

Dom





Re: Overview of W3C technologies for mobile Web applications

2011-03-07 Thread John Kemp
Hi Dom,

On Mar 7, 2011, at 11:57 AM, Dominique Hazael-Massieux wrote:

 Hi Ben,
 
 Le vendredi 25 février 2011 à 14:04 +, Ben Laurie a écrit :
 As part of a European research project I'm involved in [1], I've
 compiled a report on the existing technologies in development (or in
 discussion) at W3C for building Web applications and that are
 particularly relevant on mobile devices:
 http://www.w3.org/2011/02/mobile-web-app-state.html
 
 Nothing on security?
 
 It does mention the work on CORS and the work around widgets security,
 but there is no dedicated section on security — I'm not sure what would
 appear there that would be particularly relevant on mobile devices, any
 suggestion?

For example, mobile devices are usually correlated with a single individual, or 
at most a small group of people. The data contained on them is often personal. 
As such, identifiers related to mobile devices (phone number, IMEI) constitute 
sensitive information. 

In addition, they carry an increasing array of sensors again closely related to 
a single individual (e.g. GPS). 

By providing Javascript APIs to device functionality, we are opening up a 
mechanism which allows unidentified (or, identified mostly only by unreliable 
technologies) access to personal and/or sensitive information. There are some 
security benefits to doing so with Javascript APIs accessible only to the 
recipient of an HTTP request initiated by the user, but also some potential 
pitfalls. 

Of course, I can't tell if that's what Ben was alluding to with his question ;)

Regards,

- John





Re: Overview of W3C technologies for mobile Web applications

2011-02-25 Thread Ben Laurie
Nothing on security?

On 24 February 2011 15:03, Dominique Hazael-Massieux d...@w3.org wrote:
 (bcc to public-html and public-device-apis; please follow-up on
 public-webapps)

 Hi,

 As part of a European research project I'm involved in [1], I've
 compiled a report on the existing technologies in development (or in
 discussion) at W3C for building Web applications and that are
 particularly relevant on mobile devices:
 http://www.w3.org/2011/02/mobile-web-app-state.html

 It is meant as a picture of the current state as of today, based on my
 own (necessarily limited) knowledge of the specifications and their
 current implementations.

 I'm very much looking for feedback on the document, the mistakes it most
 probably contains, its overall organization, its usefulness.

 I can also look into moving it in a place where a larger community could
 edit it (dvcs.w3.org, or www.w3.org/wiki/ for instance) if anyone is
 interested in contributing.

 I'll likely publish regular updates to the document (e.g. every 3
 months?), esp. if it helps sufficiently many people to understand our
 current ongoing activities in this space.

 Thanks,

 Dom

 1. http://mobiwebapp.eu/







RE: Overview of W3C technologies for mobile Web applications

2011-02-25 Thread Somnath Chandra
Hello Dom,

This document is an excellent document. It gives present state-of-the art and 
roadmap ahead for development of Mobile Web. 
Implementation of Mobile Web with South Asian complex scripts is a challenging 
task. In India we have 22 constitutionally recognized languages and 12 scripts. 
Therefore , as a lead in W3C Mobile Web , Internationalization requirements and 
associcated complexities for Mobile Web implementation may also be a part of 
your document.

If you desire , Swaran Lata , Director  W3C India Country Manager and myself  
Dr. Somnath Chandra , Dy. country manager , W3C India would be happy to 
contribute.

With best regards,
Somnath Chandra , W3C India

On 02/25/11, Deborah Dahl d...@conversational-technologies.com wrote:
 
 Hi Dom,
 This looks like a very useful document. 
 On the voice/multimodal side, in addition to the HTML-Speech XG, you will 
 definitely want to add some of the Voice Browser Working Group and Multimodal 
 Interaction Working Group specs, specifically:
 1. Multimodal Architecture and Interfaces, for integrating multiple 
 modalities into an application
 http://www.w3.org/TR/mmi-arch/
 2. InkML for representing traces from pointing devices (stylus, finger, mouse)
 http://www.w3.org/TR/InkML/
 Also see an interesting prototype for displaying and capturing traces in a 
 web browser at
 http://lists.w3.org/Archives/Public/www-multimodal/2011Feb/0004.html
 3. EMMA for representing user inputs from different modalities (for example, 
 speech, ink, haptics, biometrics)
 http://www.w3.org/TR/emma/
 4. VoiceXML (especially VoiceXML 3.0) for speech interaction
 http://www.w3.org/TR/voicexml30/
 
 Regards,
 Debbie Dahl
 
  -Original Message-
  From: public-html-requ...@w3.org [mailto:public-html-requ...@w3.org] 
  public-html-requ...@w3.org] On
  Behalf Of Dominique Hazael-Massieux
  Sent: Thursday, February 24, 2011 10:04 AM
  To: public-webapps
  Subject: Overview of W3C technologies for mobile Web applications
  
  (bcc to public-html and public-device-apis; please follow-up on
  public-webapps)
  
  Hi,
  
  As part of a European research project I'm involved in [1], I've
  compiled a report on the existing technologies in development (or in
  discussion) at W3C for building Web applications and that are
  particularly relevant on mobile devices:
  http://www.w3.org/2011/02/mobile-web-app-state.html
  
  It is meant as a picture of the current state as of today, based on my
  own (necessarily limited) knowledge of the specifications and their
  current implementations.
  
  I'm very much looking for feedback on the document, the mistakes it most
  probably contains, its overall organization, its usefulness.
  
  I can also look into moving it in a place where a larger community could
  edit it (dvcs.w3.org, or www.w3.org/wiki/ for instance) if anyone is
  interested in contributing.
  
  I'll likely publish regular updates to the document (e.g. every 3
  months?), esp. if it helps sufficiently many people to understand our
  current ongoing activities in this space.
  
  Thanks,
  
  Dom
  
  1. http://mobiwebapp.eu/
  
  
 
 
 
 


-- 

Dr. Somnath Chandra
Scientist-D
Dept. of Information Technology
Govt. of India
Tel:+91-11-24364744,24301811
Fax: +91-11-24363099
e-mail :schan...@mit.gov.in


RE: Overview of W3C technologies for mobile Web applications

2011-02-24 Thread Dailey, David P.
Hi Dom,

It looks quite nice as a way to organize a large lot of information. I'm sure I 
will be making use of this often as I seem often to get confused by the number 
of W3C projects on going and the proper jurisdiction as specific concerns may 
arise. A couple of quick reactions:

I'm not sure I see a place for time-series data such as covered in InkML. InkML 
is very interesting for data visualization efforts, particularly with regard to 
animation and geolocation. I also don't see MathML anywhere, or has no one yet 
attempted it in the mobile environment?

Just a couple of quibbles from the SVG perspective: There are a few places in 
the table where specific functionalities have been broken out and assigned to 
some technology, where, depending on one's purposes another technology might be 
preferred. 

For example: rounded corners, complex background images and box shadow effects 
are just as well the purview of SVG as of CSS, at least in my mind, though 
admittedly the applicability from CSS (to either HTML or SVG or MathML. Is 
someone likely to look at this table to get advice on where to turn to 
accomplish a given effect? If so, then pointing them in more than one direction 
might be useful.

Under animations in your table, it seems like both SVG/animation and SMIL 
should be listed in addition to CSS. The SVG/SMIL animate module is probably 
more mature, widely implemented, and powerful than the CSS business. 

In discussion of fonts, SVG fonts has a more powerful model than WOFF, allowing 
broader extensibility as well as interactive fonts (defined dynamically in the 
browser). While they are downloadable (as in bundle-able in one's document) 
they need not be, and are hence of greater potential utility to the mobile 
community.

Under Image  Video analysis and modification, you mention SVG filters in the 
discussion at top, but in the table, only HTML Canvas/2D Context is mentioned. 
What if someone only looks in the table to find the row that they are 
interested in, and concludes aha! this must be the way to filter video?

It looks as though your table attempts to provide a one-to-one mapping from 
functionality to Working Groups, but the proper relationship may be one-to-many 
owing to the zeal of some of the working groups.

One other comment: much of what you've listed here is just as relevant to the 
browser community as to the mobile community. Would a minor expansion of scope 
and effort suffice to make a roadmap that is relevant to both?

Regards
David

-Original Message-
From: public-html-requ...@w3.org [mailto:public-html-requ...@w3.org] On Behalf 
Of Dominique Hazael-Massieux
Sent: Thursday, February 24, 2011 10:04 AM
To: public-webapps
Subject: Overview of W3C technologies for mobile Web applications

(bcc to public-html and public-device-apis; please follow-up on
public-webapps)

Hi,

As part of a European research project I'm involved in [1], I've
compiled a report on the existing technologies in development (or in
discussion) at W3C for building Web applications and that are
particularly relevant on mobile devices:
http://www.w3.org/2011/02/mobile-web-app-state.html

It is meant as a picture of the current state as of today, based on my
own (necessarily limited) knowledge of the specifications and their
current implementations.

I'm very much looking for feedback on the document, the mistakes it most
probably contains, its overall organization, its usefulness.

I can also look into moving it in a place where a larger community could
edit it (dvcs.w3.org, or www.w3.org/wiki/ for instance) if anyone is
interested in contributing.

I'll likely publish regular updates to the document (e.g. every 3
months?), esp. if it helps sufficiently many people to understand our
current ongoing activities in this space.

Thanks,

Dom

1. http://mobiwebapp.eu/





Re: Overview of W3C technologies for mobile Web applications

2011-02-24 Thread Scott Wilson
Hi Dom,

This is really helpful - thanks for making this! 

(I'm also working on some EU research projects, and I keep mentioning W3C specs 
which no-one else has heard of, so this is a good resource to point researchers 
and developers at.)

I think a 3-monthly update would also be worth doing given the pace of new spec 
work going on.

S

On 24 Feb 2011, at 15:03, Dominique Hazael-Massieux wrote:

 (bcc to public-html and public-device-apis; please follow-up on
 public-webapps)
 
 Hi,
 
 As part of a European research project I'm involved in [1], I've
 compiled a report on the existing technologies in development (or in
 discussion) at W3C for building Web applications and that are
 particularly relevant on mobile devices:
 http://www.w3.org/2011/02/mobile-web-app-state.html
 
 It is meant as a picture of the current state as of today, based on my
 own (necessarily limited) knowledge of the specifications and their
 current implementations.
 
 I'm very much looking for feedback on the document, the mistakes it most
 probably contains, its overall organization, its usefulness.
 
 I can also look into moving it in a place where a larger community could
 edit it (dvcs.w3.org, or www.w3.org/wiki/ for instance) if anyone is
 interested in contributing.
 
 I'll likely publish regular updates to the document (e.g. every 3
 months?), esp. if it helps sufficiently many people to understand our
 current ongoing activities in this space.
 
 Thanks,
 
 Dom
 
 1. http://mobiwebapp.eu/
 
 
 




RE: Overview of W3C technologies for mobile Web applications

2011-02-24 Thread Deborah Dahl
Hi Dom,
This looks like a very useful document. 
On the voice/multimodal side, in addition to the HTML-Speech XG, you will 
definitely want to add some of the Voice Browser Working Group and Multimodal 
Interaction Working Group specs, specifically:
1. Multimodal Architecture and Interfaces, for integrating multiple modalities 
into an application
http://www.w3.org/TR/mmi-arch/
2. InkML for representing traces from pointing devices (stylus, finger, mouse)
http://www.w3.org/TR/InkML/
Also see an interesting prototype for displaying and capturing traces in a web 
browser at
http://lists.w3.org/Archives/Public/www-multimodal/2011Feb/0004.html
3. EMMA for representing user inputs from different modalities (for example, 
speech, ink, haptics, biometrics)
http://www.w3.org/TR/emma/
4. VoiceXML (especially VoiceXML 3.0) for speech interaction
http://www.w3.org/TR/voicexml30/

Regards,
Debbie Dahl

 -Original Message-
 From: public-html-requ...@w3.org [mailto:public-html-requ...@w3.org] On
 Behalf Of Dominique Hazael-Massieux
 Sent: Thursday, February 24, 2011 10:04 AM
 To: public-webapps
 Subject: Overview of W3C technologies for mobile Web applications
 
 (bcc to public-html and public-device-apis; please follow-up on
 public-webapps)
 
 Hi,
 
 As part of a European research project I'm involved in [1], I've
 compiled a report on the existing technologies in development (or in
 discussion) at W3C for building Web applications and that are
 particularly relevant on mobile devices:
 http://www.w3.org/2011/02/mobile-web-app-state.html
 
 It is meant as a picture of the current state as of today, based on my
 own (necessarily limited) knowledge of the specifications and their
 current implementations.
 
 I'm very much looking for feedback on the document, the mistakes it most
 probably contains, its overall organization, its usefulness.
 
 I can also look into moving it in a place where a larger community could
 edit it (dvcs.w3.org, or www.w3.org/wiki/ for instance) if anyone is
 interested in contributing.
 
 I'll likely publish regular updates to the document (e.g. every 3
 months?), esp. if it helps sufficiently many people to understand our
 current ongoing activities in this space.
 
 Thanks,
 
 Dom
 
 1. http://mobiwebapp.eu/