W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Re: ISSUE-80: Runtime localization model for widgets [Widgets]

From: Marcos Caceres <marcosc@opera.com>
Date: Mon, 23 Feb 2009 22:04:11 +0000
Message-ID: <b21a10670902231404o2349c530hbbc83ad204b5828@mail.gmail.com>
To: "Priestley, Mark, VF-Group" <Mark.Priestley@vodafone.com>
Cc: Jon Ferraiolo <jferrai@us.ibm.com>, Web Applications Working Group WG <public-webapps@w3.org>
2009/2/6 Priestley, Mark, VF-Group <Mark.Priestley@vodafone.com>:
> Having discussed this internally and gone through some examples we agree with the issue identified by Josh. In addition, concerns were raised that even without the prospect of authors forking html to create localised content - which we agree is highly undesirable, debugging localised widgets could become more cumbersome, i.e. a case of checking all relative paths to see if they started with a "/" or not.  A simple override behaviour is easier to understand, and, in our opinion, debug.

Agreed. It will make life easier for everyone.

> We therefore support specifying the kind of behaviour outlined by Josh, i.e. first check the base folder for the file, if no match is found and if the base folder isn't the root, checking there using the same filename. My follow up question is that if this behaviour is specified then can't we also get rid of the behaviour relating to the leading "/" for relative paths in widgets? Maybe this is already implicit in Josh's proposal? This would also seem to partly address Jon's concerns below.

Again, I'm strongly against fiddling with URI semantics or devising
our own path scheme. Paths should stay as they are: a forward slash
means an absolute path; no slash means a relative path. Whatever
solution we settle on must work within those constraints.

Kind regards,
Marcos Caceres
Received on Monday, 23 February 2009 22:04:56 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:14 UTC