Here are a couple of suggestions for the <access> element (http://dev.w3.org/2006/waf/widgets/#the-access-element):

Attributes

(add two new attributes)

required: Optional.

A boolean attribute that indicates whether or not this resource is essential to the operation of the widget, and thus must be accessible to the widget at runtime. In other words, the required attribute denotes that a resource is absolutely needed by the widget to function correctly, and without the availability of this resource the widget serves no useful purpose or won't execute properly. The default value when this attribute is absent is true, meaning that the resource must be made available to the widget by the widget at runtime.

duration: Optional.

One of "one-shot", "session", "blanket", indicating the duration of the access essential to the operation of the widget, and thus must be allowed to the widget at runtime. In other words, the duration attribute denotes the minimum period over which the widget requires access to the resource, without further user action authorizing continued access. Without this minimum duration the widget serves no useful purpose or won't execute properly.

        -       "one-shot" means that the widget requires no extended access authorization, and the runtime can prompt the user for every access attempt, if required.

        -       "session" means that each time the widget is executed, the widget must have free access to the resource after at most one user prompt for access confirmation.

        -       "blanket" means that once the widget is installed, it requires free access to the resource without any user prompts for access confirmation.

        The default value when this attribute is absent is "session".

Best regards,

Bryan Sullivan | AT&T