Re: Requirements: one doc or two?

All we need is a way to assign a callback. It doesn’t need to be an ‘event’ listener. For example mediaQueryList.addListener() isn’t an ‘event’ listener in the strict sense. 


> On Dec 17, 2013, at 3:38 PM, Jason White <jason@jasonjgw.net> wrote:
> 
> James Craig <jcraig@apple.com> wrote:
>> I don’t have a strong opinion for one or two *requirements* documents, as long as the specifications can remain two separate documents.
> 
> Indeed they can, but there's an interesting point of intersection. It has been
> suggested in discussions of User Context requirements that Web applications
> should be notified whenever the user's needs/preferences change, for example
> when a mobile device detects a relevant alteration of the environment and
> updates them accordingly.
> 
> An event that signals a needs/preferences profile change is the obvious way to
> satisfy this requirement. This being the case, I think it's so integral to
> User Contexts that it belongs in that spec, preferably without introducing a
> dependency on the Events spec.
> 
>

Received on Wednesday, 18 December 2013 04:01:12 UTC