This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The terminology section should only define terms; it feels like bad practice that it sets conformance requirements (e.g. "Some sources have an identifier which must be unique to the application"). The conformance requirements should be moved to the relevant section of the spec (e.g. for the previous example, as part of the description of sourceId in SourceInfo).
The terminology section talks a lot about sources, state, constraints and so on, so let's fix this when the new Constrainable interface [1] is in place. [1] http://lists.w3.org/Archives/Public/public-media-capture/2013Oct/0027.html
This paragraph: Some sources have an identifier which must be unique to the application (un-guessable by another application) and persistent between application sessions (e.g., the identifier for a given source device/application must stay the same, but not be guessable by another application). Sources that must have an identifier are camera and microphone sources; local file sources are not required to have an identifier. Source identifiers let the application save, identify the availability of, and directly request specific sources. needs to be moved to section 9, "Enumerating Local Media Devices", where the deviceId is a main topic of concern. A pointer should be left under terminology. (s/"Some sources"/"Devices"/) This paragraph: A conforming user-agent must support all the setting names defined in this spec. needs to move to section 14.1, where the track property registrations are done. This paragraph: After successful application of constraints on a track (and its associated source), if at any later time the track becomes overconstrained, the user agent must change the track to the muted state. can be deleted, it's already described in section 4.3.2 "tracks and constraints".
In reply to Harald's comments, 1. Is a local file source to be considered a device and thus required to have an identifier? 2. Setting conformance statements don't belong in 15.1 (the new 14.1), but they might belong in a new tiny subsection 15.2.
1. I believe the text "Sources that must have an identifier are camera and microphone sources; local file sources are not required to have an identifier." still applies. 2. This makes sense to me. It can even go first.
Proposed fix: https://github.com/w3c/mediacapture-main/pull/7 Re (2), I've opted to put the conformance requirements under 11.4 Settings, where it seemed a good fit.