W3C

- DRAFT -

Ubiquitous Web Applications Working Group Teleconference
06 Aug 2009

Agenda

See also: IRC log

Attendees

Present
Regrets
Chair
Matt
Scribe
matt

Contents


 

 

<trackbot> Date: 06 August 2009

<jcantera> i'm calling

Extending DCO deadline

Matt: Already extended deadline for WAI...

jcantera: Sensor network incubator group would also like extension.
... The extension we gave to WAI would fit for them.

[[Comments on this Last Call Working Draft are accepted until 7 July 2009 ...]]

jcantera: Can we extend until the end of the month?

Matt: Any objections?

RESOLUTION: DCO comment period will remain open until end of August

<scribe> ACTION: jcantera to respond to sensor network IG to tell them of extended deadline [recorded in http://www.w3.org/2009/08/06-uwawg-minutes.html#action01]

<trackbot> Created ACTION-144 - Respond to sensor network IG to tell them of extended deadline [on Jose Manuel Cantera Fonseca - due 2009-08-13].

UWA Extension length

Matt: We are out of charter and need an extension

Rotan: a month would be nice, but realistically two

Matt: I'll put in the request for 2 months...

RESOLUTION: 2 Month charter extension request

Geolocation LC comments

-> http://lists.w3.org/Archives/Member/member-uwa/2009Jul/0038.html Geolocation LC

Matt: Everyone should read and comment on his comments by the 10th. We'll send them as is on the 10th.

jcantera: I'm happy with his comments.

RESOLUTION: Group resolves that they are happy with Rotan's LC comments

<scribe> ACTION: dsr to send on Rotan's geolocation comments to the WG [recorded in http://www.w3.org/2009/08/06-uwawg-minutes.html#action02]

<trackbot> Created ACTION-145 - Send on Rotan's geolocation comments to the WG [on Dave Raggett - due 2009-08-13].

New Group Charter

Matt: Added more text, please fill in where the @@ symbols are.

Rotan: There are dependencies that aren't reflected in the charter.
... Rather than dates put things like "Publish with CR"

Matt: putting in relative dates sounds good.
... Let's figure out the dependencies and their dates on the mailing list and reflect that in the charter.

<Rotan> Maybe I could draw a graphic showing the dependencies?

<scribe> ACTION: Rotan to draw graphic showing the dependencies of the various documents on each other [recorded in http://www.w3.org/2009/08/06-uwawg-minutes.html#action03]

<trackbot> Created ACTION-146 - Draw graphic showing the dependencies of the various documents on each other [on Rotan Hanrahan - due 2009-08-13].

DCCI plans

sailesh: I was wondering what FT's position is on the DCCI stuff.
... Do we want to create a new completely different spec or update the existing spec?
... Do we do "DCCI Lite", or do we @@?

KRosenbl: We'd like to see it go forward, and we'd like to see the current version go forward. I don't know what the best way to move is.
... If it can move along modifying the current doc that would be the way to go I think, if possible.

sailesh: We had some solid comments from Jose and Rich.
... If we could remove the DOM dependency... I think that will be a lot of work...
... I'm not sure about how to proceed.
... If we should keep the current DCCI spec, or come up with something called @@ which is a reduced subset.
... but we should be able to extend it with @@ releases.

<jcantera> I'm also interested in standadizing bindings between properties and the functions that provide property values. That could be the link between concrete APIs and generic APIs

sailesh: If we go for a DCCI lite version then as a first step we should collect requirements.
... We can take the requirements and mark the features as must and shoulds.

<jcantera> I cannot understand Sailesh :( following him only on IRC

sailesh: My opinion: it's sort of like a research spec. Usually... ?? and then propose it.
... We'll probably be doing some joint development together.

Rotan: What did you mean by DCCI as a research spec?

sailesh: What we do in this standardization stuff is we develop something in house, and then we put it out for standardization. Then other folks comment and we make edits, and that's the usual process. What we have to date is the DCCI spec, which we developed jointly and then implemented.
... It was all done within W3C.

Rotan: The same thing was done with DD...

sailesh: DCCI is not a unique case, I'm just generally talking about the Nokia process. This was just some feedback from the Nokia internal standards guys.
... If we go for something other than DOM then we have to redesign from scratch. No problem there though.

richardschwerdtfe: When you said you implemented it, what did you implement? What are you accessing?

sailesh: A local store, we had a server running on our device. It was accessing GPS coordinates from the device. It was a wrapper around our local API.

richardschwerdtfe: You didn't make use of the local data storage stuff that's in HTML5 and implemented in WebKit.

sailesh: We have the local store already implemented in our current runtime on the mobile. I've got an older fork of WebKit that I've been using.
... The current runtime that's out on the public Nokia devices doesn't have that now, so we didn't use the local store.
... As far as DCCI is concerned we look at cases where we are directly sourcing information from property providers, so I don't see how the local store comes into play here.

richardschwerdtfe: So you're saying you couldn't have an extension to your user agent to store this?

sailesh: via an extension to the browser, yes.

richardschwerdtfe: Looking around, it seems like WebKit is the pervasive browser out there, so I'm thinking from a strategy perspective if this was laid over WebKit and you could use the local store and store properties on your machine...

sailesh: This is a model for getting at dynamic info.
... So, you need up to date information and such.
... From a spec point of view, I don't see how it comes into play.

-> http://www.doodle.com/ercgqgv9ifhrd948 Don't forget to fill in the summer time poll!

<Rotan> Rotan: ensure that people remember that DCCI is about *dynamic* info. Don't artificially bind it to other notions.

<sailesh> ACTION: Matt to open a wiki to record DCCI requirements [recorded in http://www.w3.org/2009/08/06-uwawg-minutes.html#action04]

<trackbot> Created ACTION-147 - Open a wiki to record DCCI requirements [on Matt Womer - due 2009-08-13].

<sailesh> we could have bi-weekly meeting calls to proceed

Summary of Action Items

[NEW] ACTION: dsr to send on Rotan's geolocation comments to the WG [recorded in http://www.w3.org/2009/08/06-uwawg-minutes.html#action02]
[NEW] ACTION: jcantera to respond to sensor network IG to tell them of extended deadline [recorded in http://www.w3.org/2009/08/06-uwawg-minutes.html#action01]
[NEW] ACTION: Matt to open a wiki to record DCCI requirements [recorded in http://www.w3.org/2009/08/06-uwawg-minutes.html#action04]
[NEW] ACTION: Rotan to draw graphic showing the dependencies of the various documents on each other [recorded in http://www.w3.org/2009/08/06-uwawg-minutes.html#action03]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009/08/06 13:56:34 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: matt
Inferring Scribes: matt

WARNING: No "Present: ... " found!
Possibly Present: Andy Bryan KRosenbl Matt Rich Rotan Sailesh aaaa aabb aacc aadd aaee inserted jcantera joined richardschwerdtfe trackbot uwawg
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Agenda: http://lists.w3.org/Archives/Member/member-uwa/2009Aug/0005
Found Date: 06 Aug 2009
Guessing minutes URL: http://www.w3.org/2009/08/06-uwawg-minutes.html
People with action items: dsr jcantera matt rotan

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]