UWA WG Dublin Face to Face

Thanks to MobileAware and the CityWest Campus

• Review of charter and UWA mission
  • Dave's XTech slides
• What was learned from the workshop
• New work items and assigning editors
• Status of existing work items
• Publication policy as a "public" working group
• Patent policy and transfer of work items from DIWG
• Next face to face?
• Logistics for the November Tech Plenary
• Planning for the next few months

Chartered deliverables

Where next for DIAL?

• Status of current specification, Kevin
• Why it makes sense to plan on adding XBL and SVG, Dave
• Support for rich web interaction and relationship to Ajax
• Relationship to SCXML?
• Positioning of DIAL within the XML family of languages
• Giving declarative authoring a much bigger visibility

DISelect and XAF

Preparing for CR transition call, Dave+Stephane+Rhys

• How to organize a Recommendation Track Transition?
• Aiming for mid-July on account of travel/vacation constraints

CC/PP 2

Next steps, Cedric

Policy based layout

• Describing presentation and behaviour
  • Application defined events and component libraries
  • Adapting XBL bindings according to the delivery context?
• New CSS proposals
  • Microsoft's grid positioning proposal
  • The older CSS3 advanced layout draft
  • Bert writes: I'm currently on holiday and it's not easy to look for things on the Web. You can may ask the CSS WG or the authors for more info.
• Collecting use cases and requirements
• What kind of specification do we envisage?
• Who is interested in being an editor?

Ontologies for device capabilities/services

• What is our value proposition for work on such ontologies?
• Rhys - Draft Delivery Context Ontology
• Which groups are working on ontologies and what are they doing?
• What are our priorities in terms of devices and services?
• Gile's report on PUCC
• Next steps?

DCCI

• Finalizing new WD, Keith+Rhys+Sailesh
• Editing DCCI (XMLSpec or XHTML?)
• Planning for Last Call and re-entering CR, Keith
• Relationship to work on binding (next slide)

Device Coordination and Binding

• Framework for binding to local and remote capabilities and services
• Name or describe service and attempt to bind to it
  • Via markup or via scripting interface
• If successful, binding event provides object as part of DCCI
  • bound object acts as proxy for capability/service
  • set event listeners, target events or call service specific methods on proxy object
• If binding fails (e.g. access denied) get error event
• Binding takes place within an application session
• See XTech presentation for more details
• Working Draft covering use cases, requirements and relationship to existing resource binding mechanisms in XHTML, DOM
  • Who would like to be an editor for this work?

Geolocation

• Good starting point for application of binding framework
• Simple interface for exposing location to browser and independent of location technology
  • Cell id/triangulation, GPS, WiFi, etc. and associated strengths and weaknesses
  • Latitude, longitude and error as baseline
• Access control decision based on domain name e.g. www.trustme.com
  • Usability considerations when asking for a decision
  • Can network operator play a role in mediating trust decisions?
• Role of websites in dealing with trust decisions for providing location to others, e.g. your buddies
• Working Draft covering use cases, requirements and other considerations
  • Ryan Sarver as a potential Invited Expert to help with this

Remote eventing and REX v2

• Extensible XML grammar for DOM events
• Support for remote UI via coupling master and slave DOM's
  • Reflect mutations on master DOM to slave DOM
  • Reflect UI events on slave DOM to master DOM
  • See XTech slides for diagram
• Propose two working drafts
  • One that only deals with <rex> container element and <event> element, and their associated attributes
  • Another that defines XML serialization for DOM3 events
• How could SCXML be used with REX v2?
• Ongoing PAG for REX v1 in WebAPI WG

Web agents and asynchronous events

• How to deliver incoming events through NAT or Firewall?
• Role of public proxies
• Techniques for punching holes
• What protocols?
  • Stretching HTTP
  • SIP and leveraging work on IMS (IP Multimedia Subsystem)
  • XMPP and leveraging increasing popularity of Jabber
• What if anything should we do next?

Role of SCXML in ubiquitous web applications

• Do we want to look at combining SCXML with DCCI and device coordination?
• How could SCXML be used with REX v2?
• What is the relationship between DIAL and SCXML?