Re: Draft roadmap for new work items

Hi Jose,

I left out DIAL v2 since we need to get v1 further along the 
Recommendation track first. Of course, we could just do v2 and get 
on with including SVG, SMIL and XBL if that is what the working 
group desires, but with the current plan, we should move v1 to Last 
Call later this year, and enter Candidate Recommendation early next 
year. Let's see what people think. If necessary I could always set 
up an online questionnaire -- we can discuss this in next week's 
call.

Thanks for offering to help with the policy work. I think the first 
step will be a document covering use cases and requirements. With 
regards to the delivery context ontology, I am keen for us to 
publish a first working draft as soon as practical. We can then 
update it as necessary as we head towards a last call. Let's use 
next week's call to see see where we are on this.

Best regards,

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

On Fri, 27 Jul 2007, José Manuel Cantera Fonseca wrote:

>
> Hi Dave,
>
> I can do the proposed call next Thursday ...
>
> Regarding the new work items for the group these are my comments:
>
> +I'm missing a work item on DIAL v2. Regarding this I think we 
> should define a roadmap for DIAL and a plan for DIAL v2 which is 
> IMHO something totally separated from the Policy based Layout 
> spec. I'm willing to work on this "DIAL roadmap".
>
> + For policy based layout or Device Independent Layout, as I 
> pointed out recently I would like to participate and edit 
> documents of this task force. We can contribute with some ideas 
> coming from the MyMobileWeb project and I will be more than happy 
> to analyse or adopt good proposals coming from existing solutions 
> of group members. I will be on vacation from August 20th to 
> September 10th. After vacation I can start working on that
>
> + Delivery Context Ontology. I have been providing feedback to 
> Rhys since the beginning of this work item in the context of the 
> DD Group. In the context of the MyMobileWeb project, in which we 
> plan also to create an ontology for semantic content adaptation, 
> we have been analysing the current version of the DC ontology and 
> we will submit to the group some comments during the next couple 
> of weeks.
>
> Have a nice weekend
>
> Best Regards
>
> Dave Raggett escribió:
>> 
>> Since the UWA WG started we have made good progress with work 
>> items carried over from the Device Independence WG:
>>
>>   DIAL v1 - updated Working Draft
>>   DISelect/XAF - both the Candidate Recommendation
>>   DCCI - re-entered Last Call with revised spec
>>   CC/PP 2.0 - Last Call
>> 
>> At the Dublin face to face we agreed to initiate new work items 
>> as envisaged in the Charter, but so far there has been little 
>> progress. To get us started, I would like to devote telecon time 
>> to a detailed consideration of particular work items and would 
>> like to get a feeling for whether when to start this, given the 
>> fact that many of us will be taking time off during August.
>> 
>> Here is a summary of the proposed work items:
>>
>>  * Remote Events for XML (REX) version 2:
>> 
>> The Web API WG has concluded its work on REX v1 and we are 
>> chartered to pick this up and move it forward. The basic idea is 
>> to enable remote user interfaces via a means to exchange events 
>> between an XML-based UI and the application it controls. This is 
>> valuable for devices with a limited native UI, or for situations 
>> where remote control is needed.
>> 
>> The intention for REX v2 is to define an extensible framework for 
>> serializing events and to provide a serialization for DOM3 
>> events. My suggestion is to do this as two Working Drafts. The 
>> first would define the rex and event elements and the semantics 
>> for their attributes. The second would define the XML 
>> serialization for DOM3 events. I propose to draft initial 
>> versions of these for review in early September. If you would 
>> like to help with the preparation of these please let me know.
>>
>>  * Resource binding interface
>> 
>> This is intended to provide a means for web application clients 
>> to bind to local or remote resources and expose them as part of 
>> the DCCI. Examples include the camera built into a phone, the 
>> geographic location, or real world sensors and effectors such as 
>> lighting and heating controls. The specification would cover the 
>> interface for the binding request, and events that signal success 
>> or failure.
>> 
>> You can see some of the some of the implications for work on 
>> access control in my post to the public UWA list:
>>
>>  http://lists.w3.org/Archives/Public/public-uwa/2007Jun/0003.html
>> 
>> The intention is to decouple the specification of the binding 
>> interface from work on access control mechanisms. If you follow 
>> the above link you will see that I believe that there is 
>> considerable potential for exploiting the power of the Semantic 
>> Web as a means to represent both resource descriptions and access 
>> control policies, along with associated trust, identity, privacy 
>> and security considerations. There are likely to be synergies 
>> with the recently formed POWDER working group as well as the Web 
>> Security Context working group.
>> 
>> The next step is to write up a first cut at a working draft that 
>> covers the use cases, requirements and context, as well as the 
>> interface itself. If you would like to help with this, please let 
>> me know.
>>
>>  * Fleshing out the DCCI
>> 
>> The Last Call review period for the DCCI ends soon and we should 
>> then be able to move it swiftly to Candidate Recommendation 
>> status. The next step will be to flesh out the DCCI with work on 
>> specific properties and their associated interfaces. Rhys has 
>> been focusing on an ontology for properties of specific 
>> importance to content adaptation and I am hoping we can publish 
>> the initial draft for that in the near future.
>> 
>> I would also like to see work on defining interfaces for access 
>> to a range of device capabilities such as an integrated camera, 
>> and the means to get and set levels for audio input and output. 
>> At the face to face we also discussed the possibility of work on 
>> a simple interface for exposing device location to web 
>> applications. We also talked about the possibility of work on 
>> remote capabilities such as a means to expose a networked printer 
>> within a web application, and the opportunities for collaborating 
>> with external groups such as the PUCC.
>> 
>> This work directly complements to work on resource binding. The 
>> next step will be to write up some kind of discussion paper on 
>> which to base plans for further work.  If you would like to help 
>> with this, please let me know.
>>
>>  * Policy based layout and behavior
>> 
>> DIAL essentially focuses on device independent markup for web 
>> pages, leaving a gap for work on standards that cover how to 
>> adapt the markup, style sheets, scripts and other resources to 
>> suit particular delivery contexts. The Charter optimistically 
>> called for a first public working draft in September 2007. Who 
>> would like to volunteer to make a stab at use cases and 
>> requirements? What about Member contributions based upon existing 
>> proprietary solutions?
>>
>>  * Intent based events
>> 
>> This is awaiting further coordination with WAI-PF and the XHTML2 
>> working groups, and looks like a good topic for discussion at the 
>> Technical Plenary.
>> 
>> I propose to discuss the roadmap and particular milestones in 
>> next week's telecon and will send out an agenda either tomorrow 
>> or early next week.
>>
>>  Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett