Workshop on SVG microDOM, DCCI and trust management services?

Andrew Sledd and Torkel Hambraeus gave a presentation to SVG Open 
2007 entitled: SVG Tiny 1.2 brings AJAX to the world of mobile SVG", 
see: http://www.svgopen.org/2007/papers/ajax/index.html

The SVG microDOM defines a subset of the DOM that is independent of 
the usual browser specific interfaces. It includes for example, 
support for Ajax and DOM3 events for interoperable scripted text 
input, and has been designed for efficient implementation on mobile 
devices.

Sledd and Hambraeus not that demand is expected to quickly emerge 
for extensions to enable even more advanced applications. They 
call out the need for interfaces that would allow scripts to 
interact with the device:

"The SVG uDOM contains support for modifying the data model and 
handling the communication with the server. This is the backbone 
functionality in web applications and allows creation of many useful 
applications. However the demand for increased functionality arises 
quite fast and a few more functions are desirable to be able to 
create even more advanced applications. Allowing scripts to interact 
with the device is a desirable feature. This would allow the 
application to launch other device applications such as the 
calendar, messaging tools etc. The ability to store information in 
between consecutive runs of and is also a desirable feature. This 
would allow the storage of user preferences and thereby make the 
start up of the application more user friendly. Not the least, a 
method to exit the application gracefully is needed. Currently there 
are no standardized APIs for these functions in the scripting API 
and applications that make use of these functions must rely on 
proprietary solutions. To maintain the highly desirable 
interoperability requirements it is desirable that these extensions 
are standardized in some open standard and do not evolve into a 
number of proprietary standards."

"Extensions along these lines does however raise questions about how 
to handle security issues. Allowing scripting and access to device 
functionality in the same application opens up a new set of security 
concerns. In the near future the framework will have to rely on 
security mechanism already present on the device. It is expected to 
in the future see a number of mobile AJAX solutions based on SVG."

This sounds like a good match to the UWA working group's goals for 
defining richer access to device capabilities as part of work on the 
DCCI:

    * Rich descriptions of devices and services and the means
      to expose this to web applications and enable them to
      dynamically adapt to changes in user preferences, device
      capabilities and environmental conditions

    * An approach to resource binding that leverages the
      Semantic Web for managing trust, identity, privacy
      and security through rich descriptions of capabilities
      and policies, and which layer on top of complementary
      work on device coordination

The former is being catered for via the DCCI and we are starting 
work on defining rich meta-data for device capabilities including 
devices like mobile handsets, printers, cameras and media players.

I posted some ideas for resource binding and access control back in 
June, see:

  http://lists.w3.org/Archives/Public/public-uwa/2007Jun/0003.html

Perhaps it is time to consider organizing a W3C workshop to bring 
together people interested in combining the microDOM with access to 
device capabilities and a solid story on usable security, including 
the means for network operators to provide trust management 
services?

  Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett

Received on Thursday, 13 September 2007 15:23:01 UTC