- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Tue, 7 Jul 2009 08:39:41 -0400
- To: w3c-updates@celestialwake.com
- Cc: Marcos Caceres <marcosc@opera.com>, www-archive@w3.org
Jeff - please respond to Marcos' email to you by July 9th at the latest and please public-webapps@w3.org. -Regards, Art Barstow Begin forwarded message: > From: ext Marcos Caceres <marcosc@opera.com> > Date: July 1, 2009 11:11:23 AM EDT > To: Jeff Decker <w3c-updates@celestialwake.com> > Cc: "public-webapps@w3.org" <public-webapps@w3.org> > Subject: Re: Widgets 1.0: Packaging and Configuration questions > Reply-To: "marcosc@opera.com" <marcosc@opera.com> > Archived-At: <http://www.w3.org/mid/ > b21a10670907010811t381782d4s72fa767bc454b624@mail.gmail.com> > > On Wed, Jun 17, 2009 at 5:12 PM, Jeff > Decker<w3c-updates@celestialwake.com> wrote: >> Hi Everyone, >> >> I was going over the P&C spec and had a couple questions: >> >> 1. Under section 7.12 "The feature Element" it does not note how a >> widget >> user agent should handle an unknown feature name. Is this intended? > > Yes, this is intentional. Processing is actually defined in Step 7: > > "x. If feature-name is not supported by the user agent, and > required-feature is true, then treat this widget as an invalid widget > package. > > x. If feature-name is not supported by the user agent, and > required-feature is false, then this element, its attributes, and its > children are in error and must be ignored. Stop processing this > element and proceed to the next element in the elements list. > " > > I've added a note at the start of the "Configuration Document" section > referring the reader to Step 7 for details about processing of > elements. Hopefully that will alert the reader to where processing of > elements is described. The note simply reads: > > "Please see Step 7 for details of how the elements of the > configuration document are processed by a user agent." > > Is that clear enough? > >> 2. Under section 6.5 "Start Files" it says "It is optional for >> user agents >> to support the media types listed in the default start files >> table." Does >> this mean a user agent can support any combination of Default >> Start Files >> from the table or are the files grouped under the media types? So >> If I were >> to support text/html, then I would need to search for both .htm >> and .html >> files? > > That is correct. Is that not clear enough? If no, can you suggest some > text that would make that more clear? > > -- > Marcos Caceres > http://datadriven.com.au >
Received on Tuesday, 7 July 2009 12:41:03 UTC