reSpec.js experience?
Posted on:If someone has experience with reSpec.js (such as using reSpec to build the current WebRTC 1.0 API spec), I’d be interested in your recommendations on how we might best leverage it in this community group.
Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
name |
---|
Object RTC (ORTC) API for WebRTC |
Object RTC (ORTC) API for WebRTC |
Chairs, when logged in, may publish draft and final reports. Please see report requirements.
If someone has experience with reSpec.js (such as using reSpec to build the current WebRTC 1.0 API spec), I’d be interested in your recommendations on how we might best leverage it in this community group.
Two points…
I would like to propose that discussions regarding the API happen via the ORCA Community Group, the public-orca@w3c.org mail list seems to make sense. If you have not subscribed to that list yet and wish to receive messages sent to the list please do so here.
As part of this proposal, I suggest we abide by the W3C consensus policy (http://www.w3.org/2005/10/Process-20051014/policies.html#Consensus)
Starting with these 2 points should provide for a healthy community, more transparency and hopefully more input on decisions being made.
You can agree to this proposal by simply replying to the mail thread created in correlation with this post, with +1 Or reply with your objection and reasoning why we should not do this.
Thanks,
/Erik
—-
Just a head’s up, Robin is sick with the flu.
WebRTC Object API (alpha):
https://github.com/openpeer/ortc/blob/master/draft-w3c-ortc-api-00.md
Early example code, written in Node.js:
https://github.com/openpeer/ortc
It is the current authors intent to provide an alternative to the existing WebRTC API, to allow more control to web developers looking to leverage WebRTC.
Rationale for this alternate approach can be found in the informational draft submitted to the IETF RTCWEB working group several weeks ago.
Those interested in assisting in the completion of this API reference are asked to join this community group and take part in the discussions by:
On behalf of the current authors, thank you for your support and consideration.