W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2009

RE: ISSUE-14: Gathering requirements [System Info & Events]

From: JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>
Date: Mon, 05 Oct 2009 12:55:29 +0200
To: Robin Berjon <robin@robineko.com>
Cc: "Tran, Dzung D" <dzung.d.tran@intel.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-id: <93AA9E47B82F684A868C217766F4890538E6719F76@EXCLU2K7.hi.inet>
I was referring to other kind of extensibility :) not to the fact that Javascript is extensible by definition. 

I would rewrite the requirement as "universality", i.e. the API should allow to access system information without requiring to define new interfaces or operations or modifying existing ones ...

Best Regards

-----Mensaje original-----
De: Robin Berjon [mailto:robin@robineko.com] 
Enviado el: lunes, 05 de octubre de 2009 11:20
Para: JOSE MANUEL CANTERA FONSECA
CC: Tran, Dzung D; public-device-apis@w3.org
Asunto: Re: ISSUE-14: Gathering requirements [System Info & Events]

On Oct 5, 2009, at 09:50 , JOSE MANUEL CANTERA FONSECA wrote:
> here goes a very important non-functional requirement:
>
> The System Info and Events API should be extensible and not  
> constrained to the properties the DAP group defines but any property  
> that now or in the future might appear.

That one is fairly simple to address, in Javascript all interfaces are  
extensible, whatever we do doesn't jail us the way Java interfaces did.

--
Robin Berjon
   robineko — setting new standards
   http://robineko.com/




Received on Monday, 5 October 2009 10:56:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:39 UTC