Hi Krzysztof,
I've made most of the changes you recommended but I was not able to
resolve everything. Please see below. I would really appreciate if you
could take the time to help me resolve outstanding issues. However, if
you are happy with leaving things as they are, please let me know so I
Hi Stuart, All,
This email is a continuation of the discussion about the Widget URI
scheme we've had in the past [1]. WebApps is trying to draft the final
text for the Widget Requirements document regarding a URI scheme for
widgets and we would again appreciate some input from the TAG. WebApps
WG
Hi Thomas,
Mark Priestley of Vodafone will respond to you on OMTP's behalf in relation to
the comments below. Speak to you all on the call later on today.
Thanks,
David.
-Original Message-
From: Thomas Roessler [mailto:[EMAIL PROTECTED]
Sent: 07 August 2008 01:30
To: David Rogers
Hi Thomas,
On Thu, Aug 7, 2008 at 10:43 AM, Thomas Roessler [EMAIL PROTECTED] wrote:
While I'm on it... I believe that we should add the following
points to the automatic update requirement:
- Conforming specifications should ensure that updates are
authenticated.
- Conforming
On Wed, 30 Jul 2008 18:19:20 +0200, Jonas Sicking [EMAIL PROTECTED] wrote:
Please note that
Access-Control-Allow-Origin: url
is also allowed syntax. Where the url must contain only scheme, [host,
and port].
So the following syntax is allowed:
Access-Control-Allow-Origin:
ISSUE-45 (Extensible metadata): Do we need an extensible metadata hook?
[Widgets]
http://www.w3.org/2008/webapps/track/issues/45
Raised by: Marcos Caceres
On product: Widgets
Krzysztof Maczyński recommended that we need some kind of generic extensible
metadata hook. If there a use case for
Hi Bryan,
I'm wondering if you could help me understand R21. Resource
Declarations, which was proposed in your feedback [1]:
R21. Resource Declarations
A conforming specification must specify a means for declaring that the
instantiated widget will have an impact on sensitive device or
