W3C home > Mailing lists > Public > public-mwts@w3.org > August 2009

Re: [widgets] Test Suite for Packaging and Configuration

From: Marcos Caceres <marcosc@opera.com>
Date: Thu, 13 Aug 2009 13:24:43 +0200
Message-ID: <b21a10670908130424t1a5b8951we0f1b10eac455d99@mail.gmail.com>
To: Scott Wilson <scott.bradley.wilson@gmail.com>
Cc: public-webapps <public-webapps@w3.org>, public-mwts@w3.org
On Mon, Aug 10, 2009 at 1:36 PM, Scott
Wilson<scott.bradley.wilson@gmail.com> wrote:
>
> On 10 Aug 2009, at 10:00, Marcos Caceres wrote:
>>
>> Secondly, although some elements are not exposed as part of A&E (e.g.,
>> icon and license), there are still conformance requirements as to how
>> the user agent is supposed to expose the content of those elements to
>> the end-user. For example, for the license element, the spec says:
>>
>> "When the href  attribute [of the license element] is used, the user
>> agent should provide users the ability to view or otherwise link to
>> the referenced license."
>>
>> Although not mandatory behavior, nor exposed via A&E, it is still
>> manually testable ("test: does the widget provide some means to show
>> the license?"). Having said that, we could have made this more clear
>> in the spec by saying: "Upon request by an end-user, a user agent
>> should expose a license in an accessible manner (e.g., visually or
>> aurally)."
>
> Thanks Marcos, this is quite a good one to work through.
>
> For "license" is the conformance requirement that the widget instance
> exposes the license to the current *viewer*?

No.

> Or that the UA makes the
> license available to the UA *owner*? (Or both or neither...)

Yes:
  1. The UA  MUST processes the license (Step 7)
  2. The UA SHOULD make the license available by some means to the end
user, if possible.

Note, that 2, means that the UA does not have to.

> For example, Wookie could show the license either in the gallery metadata
> (for the "end UA" to display to the user in some fashion) and also within
> the admin interface for the UA owner/admin.

IMO, the above would be preferable to what is below.

> Or, the widget itself has some
> sort of display mechanism for the license to the viewer (but then wouldn't
> that mechanism be within scope of A&E?)

Correct. But no one has asked for this kind of functionality from the
A&E. One way of getting to the license is to XHR the config doc, in
this case.


-- 
Marcos Caceres
http://datadriven.com.au
Received on Thursday, 13 August 2009 11:25:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 August 2009 11:25:47 GMT