Fwd: Call for information before teleconference

As suggested.

Thanks,
Bryan Sullivan

Begin forwarded message:

> From: Arthur Barstow <art.barstow@nokia.com>
> Date: September 20, 2011 9:14:02 AM PDT
> To: ext Bryan Sullivan <blsaws@gmail.com>
> Cc: Rigo Wenning <rigo@w3.org>, member-widgets-pag <member-widgets-pag@w3.org>
> Subject: Re: Call for information before teleconference
> 

> Hi Bryan - I think it would be useful if you would please send your data to public-widgets-pag@w3.org archived at:
> 
> http://lists.w3.org/Archives/Public/public-widgets-pag/
> 
> -Thanks, Art
> 
> On 9/20/11 11:49 AM, ext Bryan Sullivan wrote:
>> Rigo,
>> 
>> Here is some input we had intended to send, but failed to before your deadline. Hopefully this will still be useful:
>> 
>> In regard to prior art for US-20070101433 (issued Patent #7,743,336), managed access to resources for applications (including device/application functions and content) is covered by a variety of standards and products going back to the 1990’s, including in the specific scope of the WARP spec (managed access to Web resources/content). From the detailed description, there may be overlap between US-20070101433 and US-20070101146 (application), and specifications for application security and deployed products such as the following:
>> • Dec 6, 1998: Website “Netscape Object Signing Establishing Trust for Downloaded Software”,http://web.archive.org/web/19981206013607/http://developer.netscape.com/docs/manuals/signedobj/trust/index.htm 
>> • Nov 5, 2002: JSR-000118 Mobile Information Device Profile Specification 2.0 Final Release (Release: November 5, 2002): http://download.oracle.com/otn-pub/jcp/7121-midp-2.0-fr-spec-oth-JSpec/midp-2_0-fr-spec.pdf. See in particular Chapter 3 “Security for MIDP Applications” and Chapter 4 “Trusted MIDlet Suites using X.509 PKI”
>> • March 1996: Release of Netscape Navigator 2.0, which included the “same-origin” policy for network access by Javascript applications:https://developer.mozilla.org/en/Bypassing_Security_Restrictions_and_Signing_Code. Netscape also supported the ability to bypass the same-origin policy (http://www.w3.org/Security/wiki/Same_Origin_Policy) using a Javascript API: netscape.security.PrivilegeManager.enablePrivilege(“UniversalBrowserRead”). The WARP spec defines a similar ability to bypass the same-origin restriction by declaring Web domains to be accessed by the application, in the widget manifest file.
>> • Oct 18, 2004 (or before): “XML Security: Control information access with XACML”:http://www.ibm.com/developerworks/xml/library/x-xacml/
>> 
>> Thanks,
>> Bryan Sullivan
>> 
>> On Sep 19, 2011, at 10:44 AM, Rigo Wenning <rigo@w3.org <mailto:rigo@w3.org>> wrote:
>> 
>>> Dear all,
>>> 
>>> the call for prior art is over now. We have received some feedback:
>>> http://www.w3.org/2009/11/widgets-pag/prior-art.html
>>> please compare to the call for prior art in
>>> http://www.w3.org/2009/11/widgets-pag/cfpa.html
>>> 
>>> Please look at the page and the information contained therein. I would
>>> especially call out those companies that have implemented the WARP
>>> Specification as documented in:
>>> http://dev.w3.org/2006/waf/widgets-access/imp-report/
>>> I wont those to compare their implementation experience with the
>>> descriptions in the patents and also with the description in the Symbian
>>> security features.
>>> 
>>> I remind everyone that the WARP Specification will not pass Proposed
>>> Recommendation without closing this PAG. We have received good
>>> directions from outside. So please consider the information.
>>> 
>>> I will be on the road this week, but we will have a call on this next
>>> week. Please fill out the following doodle by the end of this week so I
>>> can arrange the phone conference:
>>> http://www.doodle.com/cnszfh8c5uk7vbq7
>>> 
>>> 
>>> Best,
>>> 
>>> Rigo Wenning
>>> WARP PAG Chair
>>> 
>>>