Mechanics of interfacing WebRTC API and JSEP


As part of discussing at the 
WebRTC F2F last week, we came to the conclusion that we needed a better 
mechanism to link from the WebRTC API to the JSEP draft, and I 
volunteered to work with EKR on finding the right mechanism for that.

Having looked quickly in the tools used to build the JSEP draft, I can 
imagine the following options:
* we link directly to the "latest" version of JSEP posted at — this one has semantic anchors (e.g. so it's easy to do 
and requires little or no machinery to work; but it's not the official URL

* we extract "live" the matching of semantic anchors to section numbers 
from that same document, and use these to build full links to 
URLs; the extraction can be done live since the doc is CORS'd; fairly 
easy to do, but requires some understanding and commitment of the 
alignment between and ; also, it will make 
the WebRTC spec slower to load

* we set up a (automated?) process whereby each time the JSEP draft is 
updated, we run a tool that extract the mapping between semantic anchors 
and section numbers; I'm not sure how we integrate with the updates to 
JSEP draft (is there an IETF webhook for that?)

Any reaction or preference?


Received on Monday, 2 November 2015 11:35:53 UTC