RE: ISSUE-22: Should we have an umbrella requirements document?

Hi Frederick,

> On Sep 23, 2009, at 17:45 PM, Frederick Hirsch
> wrote:
> How will such general requirements that span multiple APIs be 
> captured and communicated outside the work group and beyond 
> the life of the work group, apart from the implicit impact on 
> the specifications?

Truth be told: I can live with published or not published general

However, not publishing our general guidelines means not imposing
restrictions on future Device API development. Future API developers
will do what works at that time and would not be bound by our general
guidelines. If our API patterns and designs work (which are the
manifests of our general guidelines) then they will be imitated in the
future (such as we see with the W3C Geolocation specs to a degree, which
does not publish it's design guidelines).

It would be analagous to disposing of the scaffolding and allowing new
scaffolding to be created depending on the work required in the future.

Either way works for me.



Received on Wednesday, 23 September 2009 17:38:07 UTC