Drew Wilson wrote on 06/03/09 23:39:
...
- Worker UI:
From the worker standpoint, the main difference between a
PersistentWorker and other types of workers is that the normal way of
interacting with the user (via an open browser window) is not
available, since there may be no windows open to
At 3:22 +0100 10/03/09, Charles McCathieNevile wrote:
That format has some serious limitations for heavy metadata users.
In particular for those who are producing information about
historical objects, from British Parliamentary records to histories
of pre-communist Russia or China to museum
Filed a bug on URL encoding,
https://bugzilla.mozilla.org/show_bug.cgi?id=482388
On Mon, Mar 9, 2009 at 5:02 PM, Jonas Sicking jo...@sicking.cc wrote:
On Fri, Mar 6, 2009 at 4:51 PM, Dmitry Titov dim...@chromium.org wrote:
Hi,
I have a couple of questions about Web Workers and text encoding
Hi David,
On 10 Mar 2009, at 17:03, David Singer wrote:
The trouble is, that opens a large can of worms. Once we step out
of the Gregorian calendar, we'll get questions about various other
calendar systems (e.g. Roman ab urbe condita http://
en.wikipedia.org/wiki/Ab_urbe_condita,
Thanks for the info - I wasn't aware of the new Ubuntu notification
infrastructure. Notes below:
On Mon, Mar 9, 2009 at 10:42 PM, Matthew Paul Thomas m...@myrealbox.comwrote:
Speaking for Ubuntu, we are making active efforts to reduce the number
of elements in the notification area (aka
In message cc3986d1-6ddc-4007-8bba-42a5d4e39...@eatyourgreens.org.uk,
Jim O'Donnell j...@eatyourgreens.org.uk writes
This is already a solved problem in the Text Encoding Intiative (TEI).
The value of a date/time is encoded in the Gregorian calendar, using
ISO8601. The calendar attribute is
In message 20090309215532.ga3...@stripey.com, Smylers
smyl...@stripey.com writes
Tom Duhamel writes:
My opinion is that all the following dates are precise:
2009
2009-03
2009-03-09
The later is more precise, but the three are all precise in my
opinion.
Being precise means having a small
This seems to provide a good use case for a couple of RDFa attributes:
time xmlns:d=http://dbpedia.org/resource/;
datatype=d:Mesoamerican_Long_Count_calendar
content=12.19.16.2.18
13 Etz'nab' 1 Kumk'u/time
Adopting RDFa in HTML5 not only gives us a technique for embedding
On Tue, Mar 10, 2009 at 3:48 PM, Andy Mabbett a...@pigsonthewing.org.uk wrote:
How widely - compared to Julian dates - are those published, in the wild?
You might be tending towards 'Reductio ad absurdum'.
There are definitely many non-Julian/Gregorian calendar systems used
in the wild.
In message hb0sf5+2xbwff...@pigsonthewing.org.uk, in February 2007, I
wrote:
In message 8434a459-7c78-42f8-bef6-98e6f0a5d...@w3.org, Karl Dubost
k...@w3.org writes
I think there is a possible win-win here. The Mozilla UI widget could
be activated only when the right URI (profile attribute) is
In message zxed4ttdzyojf...@pigsonthewing.org.uk, I wrote:
Another abuse of ABBR in microformats for coordinates:
abbr class=geo title=52.548;-1.932Great Barr/abbr
Bruce and I agree that this could be resolved, and HTML5 usefully
extended, by a “location element:
location
On Tue, 10 Mar 2009 18:03:37 +0100, David Singer sin...@apple.com wrote:
At 3:22 +0100 10/03/09, Charles McCathieNevile wrote:
That format has some serious limitations for heavy metadata users. In
particular for those who are producing information about historical
objects, from British
Posted first at public-html-comments, but that list seems silent. I
have received suggestions to repost here.
Message 1 of 2, from
http://lists.w3.org/Archives/Public/public-html-comments/2009Mar/0001.html:
Currently, HTML5's postMessage may transfer some amount of data in the
message, and up to
Message 2 of 2, from
http://lists.w3.org/Archives/Public/public-html-comments/2009Mar/0002.html:
To be concrete about it, I am a member of the Caja team, which is building
an object-capability subset of JavaScript by translation to JavaScript.
Currently, Caja brings object-capabilities only to
14 matches
Mail list logo
