Meeting minutes
Previous minutes
<dape> -> August-22
<kaz> dp: we had a short meeting last time
Daniel: we talked about quick updates
… the minutes looks good
… we can remove empty sections
… any objections?
… ok minutes approved
Quick updates
Daniel: it is pre-tpac week
… it seems that every call will take place as usual
… only main and testing calls are canceled
… today I would like to discuss not the technical aspect but the agenda
… I will ask mccool for a scripting slot
… just notice that the next two meetings are cancelled
TPAC Agenda
Daniel: I created three different slots
Working mode for Scripting API
Daniel: one is the working mode for the next charter
… different options:
… stay in the Working Group and write an Informative Note
… stay in WG but create a Formal Note (note track) . In this case we can have a conformance section
… WG, REC track
… and finally Community Group but there we don't have any W3C team support
… in my understanding kaz can provide one or two slides with pro and cons about these four options
… what do you think about this agenda point?
Cristiano: I agree that we must discuss this with high priority. About the options my personal take would be to go with the 2nd option. is not that I don't like the others but I think they are harder to achive
Daniel: I agree
Kaz: the options here are not really correct ( the terminology can be improved)
Daniel: Ok fixed
Kaz: the problem is that people are not familiar with the latest status of the "process" document
… I'd like to describe the essence of the document to everybody
Daniel: I totally agree
Kaz: also the community groud produce a community group reoport and it is not endorsed by the W3C
… notice that this information is reported by the status section in each document type
… originally this presentation about the latest status of the process document was planned during the recharting presentation
Daniel: ok then we can try to schedule scripting discussion after it
Kaz: we need to think also about potential push backs for the new charter
… there is not just pro/cons but a rather complex mix of view points
… anything else to add here?
… should we collect pro/cons that we see?
mizushima: I would not add CG among the options
… the direction of the group is not clear
… there is no deliverables defined
Daniel: I agree I would not go to the CG
… the point was raised by Zoltan to reach for a wider contributor pool
mizushima: CG is the last option
Cristiano: I agree
Kaz: if we talk about these options we should also include people's preference, why they would like to go for which option
Breaking changes
Daniel: we can discuss about Exposing process
… also about discovery API
… do you have something that you want to present to the group
… also actions support
Cristiano: I think we can discuss also additionalResponses and error codes
Daniel: I agree
Next charter
Daniel: mccool asked to report next charter topics
… I collected some options
… Discovery Alignment, TD profile support
… also management API
… finally, we can try to bring our API to project fugu
Cristiano: about the last one we have a blocker: we need to define discovery api correctly
Daniel: any other topics to discuss?
Kaz: during the Architecture call and the Testing call, we discussed how to test architecture specification
… it seems that there are some assertions in the Architecture that are relevant to scripting implementations
… it seems that we can have an implementation report also for scripting api
… then how should we test a scripting API implementation?
… also we should clarify the relationship between Architecture and Scripting.
Daniel: anything else to discuss?
… feel free to ping me if you want to add more topics
… aob?
[adjourned]