Review of WebRTC 1.0 from Web Applications Working Group

[Stefan Håkansson LK]

Dear Web Applications Working Group,

The WebRTC Working Group is working toward publishing the WebRTC 1.0 
specification to Candidate Recommendation and is thus seeking review 
from a variety of groups on the document:

http://w3c.github.io/webrtc-pc/

We are particularly interested on feedback on the following aspects from 
the Web Apps WG:
- proper usage of WebIDL; in particular, the WebRTC API has now a 
dependency on the maplike<> construct which is not part of the 
/TR/webidl-1/ spec at the moment,
- the DataChannel API which is heavily inspired from the WebSockets API,
- the overall approach to error handling,
- the instantiation of a worker to interact with a third party system, 
as defined in the Identity section

We of course also welcome feedback on any other aspect of the specification.

Any such feedback received the week before TPAC would make it possible 
for us to look at it during our F2F there and so would be appreciated. 
We hope to transition request to Candidate Recommendation by the end of 
this year.

If you have any comments, we prefer you submit them as Github issues:
https://github.com/w3c/webrtc-pc/issues
Alternatively, you can send your comments by email to public-web...@w3.org.

Thanks,

For the WebRTC co-chairs,
Stefan

Re: App-to-App interaction APIs - one more time, with feeling

[Arthur Barstow]

On 10/14/15 12:33 PM, Daniel Buchner wrote:


Hey WebAppers,

Just ran into this dragon for the 1,326^th time, so thought I would do 
a write-up to rekindle discussion on this important area of developer 
need the platform currently fails to address: 
http://www.backalleycoder.com/2015/10/13/app-to-app-interaction-apis/. 
We have existing APIs/specs that get relatively close, and my first 
instinct would be to leverage those and extend their capabilities to 
cover the broader family of use-cases highlighted in the post.


I welcome your ideas, feedback, and commentary,



Hi Daniel,

In case you haven't done so already, perhaps the Web Platform Incubation 
Group's Discourse service would be a "better" place to discuss your 
proposal ?


--
AB

RfC: WebRTC 1.0; deadline Oct 23

[Arthur Barstow]

[ Stefan's e-mail hasn't been delivered to p-webapps so Dom asked me to 
forward it ]


 Forwarded Message 
Subject:Review of WebRTC 1.0 from Web Applications Working Group
Date:   Thu, 15 Oct 2015 09:05:57 +
From:   Stefan Håkansson LK 
To: 	art.bars...@gmail.com , 
cha...@yandex-team.ru , Web Applications Working 
Group WG (public-webapps@w3.org) 

CC: webrtc-cha...@w3.org 



Dear Web Applications Working Group,

The WebRTC Working Group is working toward publishing the WebRTC 1.0
specification to Candidate Recommendation and is thus seeking review
from a variety of groups on the document:

http://w3c.github.io/webrtc-pc/

We are particularly interested on feedback on the following aspects from
the Web Apps WG:
- proper usage of WebIDL; in particular, the WebRTC API has now a
dependency on the maplike<> construct which is not part of the
/TR/webidl-1/ spec at the moment,
- the DataChannel API which is heavily inspired from the WebSockets API,
- the overall approach to error handling,
- the instantiation of a worker to interact with a third party system,
as defined in the Identity section

We of course also welcome feedback on any other aspect of the specification.

Any such feedback received the week before TPAC would make it possible
for us to look at it during our F2F there and so would be appreciated.
We hope to transition request to Candidate Recommendation by the end of
this year.

If you have any comments, we prefer you submit them as Github issues:
https://github.com/w3c/webrtc-pc/issues
Alternatively, you can send your comments by email to public-web...@w3.org.

Thanks,

For the WebRTC co-chairs,
Stefan

TPAC Topic: Using ES2015 Modules in HTML

[Ryosuke Niwa]

Hi all,

Can we discuss how we can integrate ES2015 modules into HTML on Tuesday, 
October 27th at TPAC?

Both Gecko and WebKit are basically done implementing ES6 module supports in 
their respective JavaScript engines but blocked on 
http://whatwg.github.io/loader/  to support in 
web contents.

Since my colleague who is interested in this topic cannot attend TPAC in 
person, it would be great if we could have it in Tuesday Morning (Monday 
evening in California).

- R. Niwa

RE: App-to-App interaction APIs - one more time, with feeling

[Daniel Buchner]

After publishing the post, Google has reached out and we’ve been discussing 
options for solving this – would you like those discussions to be on the ML, or 
back-channeled?

- Daniel

From: Samsung account [mailto:bnw6...@gmail.com]
Sent: Thursday, October 15, 2015 9:26 AM
To: Arthur Barstow 
Cc: Daniel Buchner ; public-webapps@w3.org
Subject: Re: App-to-App interaction APIs - one more time, with feeling


2015/10/15 下午11:58於 "Arthur Barstow" 
>寫道：
>
> On 10/14/15 12:33 PM, Daniel Buchner wrote:
>>
>>
>> Hey WebAppers,
>>
>> Just ran into this dragon for the 1,326^th time, so thought I would do a 
>> write-up to rekindle discussion on this important area of developer need the 
>> platform currently fails to address: 
>> http://www.backalleycoder.com/2015/10/13/app-to-app-interaction-apis/.
>>  We have existing APIs/specs that get relatively close, and my first 
>> instinct would be to leverage those and extend their capabilities to cover 
>> the broader family of use-cases highlighted in the post.
>>
>> I welcome your ideas, feedback, and commentary,
>>
>
> Hi Daniel,
>
> In case you haven't done so already, perhaps the Web Platform Incubation 
> Group's Discourse service would be a "better" place to discuss your proposal 
> >?
>
> --
> AB
>
>

Call for Consensus (CfC) to close the Web Intents Task Force - Deadline October 29, 2015

[Frederick Hirsch]

This is a Call for Consensus (CfC) to close the Web Intents Task Force [1].

This Task Force has been inactive for some time.  There are no relevant 
deliverables in the draft revision of the DAP WG charter [2], or the Web 
Platform WG charter [3].

The purpose of this CfC is obtain consensus to explicitly close the Task Force. 
If you agree with closing the Task Force a response with a +1 would be useful;  
if you have concerns please note them. Silence will be assumed to be agreement.

I believe the TF mail archive will remain despite the TF being closed.

Please respond by October 29, 2015 (2 weeks) to this CfC.

Thanks

regards, Frederick

Frederick Hirsch
Chair, W3C Device APIs WG (DAP)

www.fjhirsch.com
@fjhirsch

[1] http://www.w3.org/2009/dap/#webintents

[2] http://w3c.github.io/dap-charter/DeviceAPICharter.html

[3] http://www.w3.org/2015/10/webplatform-charter.html

[manifest] Manifest "splash_screens" with animated "any" size SVG

[Binyamin]

בע"ה


Hi,


Google recently has published icon support centered in splash screen in
Chrome 47 requiring icon minimum size 196px,
https://developers.google.com/web/updates/2015/10/splashscreen.

I propose instead "splash_screens" with animated SVG that could display
loading process similarly to almost any this days Android/iOS-native apps
like Skype, etc. Link to spec
https://w3c.github.io/manifest/#splash_screens-member

{
"src": "splashscreen.svg",
"sizes": "any"
}



Binyamin

[manifest] Manifest "background_color" with gradient?

[Binyamin]

בע"ה


How about gradients in "background_color" (linear-gradient,
radial-gradient, repeating-linear-gradient, repeating-radial-gradient)?
Anything delays such spec/implementation?



Binyamin