- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Jan 2015 19:39:22 +0000
- To: public-media-capture-logs@w3.org
I just wanted to bring up - in case it's been overlooked - that there was some support on the list for making "capabilities" the primary focus of our gUM narrative, not "constraints" [1]. To re-summarize: When we talk about "width", "height", "frameRate" etc. we historically think of them as of type "constraint" for some reason. This is bad, because a constraint is a property of a caller, which only makes sense in the narrow context of organizing demands. This is too narrow of a context to cover all the areas we need to talk about "width", "height", "frameRate" etc. in. By refocusing on capabilities, we'll avoid silly mind-benders like "is volume a constraint?", when the right question is "is volume an available capability?" - The fact that all supported capabilities can be constrained on, becomes a detail. [1] https://lists.w3.org/Archives/Public/public-media-capture/2014Nov/0004.html -- GitHub Notif of comment by jan-ivar See https://github.com/w3c/mediacapture-main/issues/116#issuecomment-70147634
Received on Thursday, 15 January 2015 19:39:30 UTC