On Mon, May 18, 2009 at 5:45 AM, Brett Zamir bret...@yahoo.com wrote:
Has any thought been given to standardizing on at least a part of DOM Level
3 Load and Save in HTML5?
The Load and Save APIs in DOM 3 are much too complicated IMHO so I'd
like to see something simpler standardized.
We've had
On May 20, 2009, at 04:36, Ian Hickson wrote:
REQUIREMENTS:
* There should be a definitive location for vocabularies.
If this means that vocabulary schemas should live in a predestined URI
subspace, I'm inclined to disagree with this requirement, because
1) for non-predefined
On 20 May 2009, at 05:23, Tab Atkins Jr. wrote:
Specifically, people can use a search engine to find information about
foaf. I know that typing foaf into my browser's address bar and
clicking on the first likely link is *way* faster than digging into a
document with a foaf namespace declared,
On May 19, 2009, at 11:49 PM, Jonas Sicking wrote:
On Mon, May 18, 2009 at 5:45 AM, Brett Zamir bret...@yahoo.com
wrote:
Has any thought been given to standardizing on at least a part of
DOM Level
3 Load and Save in HTML5?
The Load and Save APIs in DOM 3 are much too complicated IMHO so
On Wed, May 20, 2009 at 12:49 AM, Maciej Stachowiak m...@apple.com wrote:
On May 19, 2009, at 11:49 PM, Jonas Sicking wrote:
On Mon, May 18, 2009 at 5:45 AM, Brett Zamir bret...@yahoo.com wrote:
Has any thought been given to standardizing on at least a part of DOM
Level
3 Load and Save in
Jonas Sicking wrote:
On Wed, May 20, 2009 at 12:49 AM, Maciej Stachowiakm...@apple.com wrote:
On May 19, 2009, at 11:49 PM, Jonas Sicking wrote:
On Mon, May 18, 2009 at 5:45 AM, Brett Zamirbret...@yahoo.com wrote:
Has any thought been given to standardizing on at least a
Brett Zamir wrote:
Jonas Sicking wrote:
On Wed, May 20, 2009 at 12:49 AM, Maciej Stachowiakm...@apple.com wrote:
On May 19, 2009, at 11:49 PM, Jonas Sicking wrote:
On Mon, May 18, 2009 at 5:45 AM, Brett Zamirbret...@yahoo.com wrote:
Has any thought been given to
Brett Zamir wrote:
Brett Zamir wrote:
Jonas Sicking wrote:
On Wed, May 20, 2009 at 12:49 AM, Maciej Stachowiakm...@apple.com wrote:
On May 19, 2009, at 11:49 PM, Jonas Sicking wrote:
On Mon, May 18, 2009 at 5:45 AM, Brett Zamirbret...@yahoo.com wrote:
Has any thought
Hi,
On Tuesday, May 19, 2009, Drew Wilson atwil...@google.com wrote:
One alternate approach to providing this support would be via shared,
cross-domain workers (yes, workers are my hammer and now everything looks
like a nail :) - this seems like one of the canonical uses of cross-domain
Ian --
There's an authoring and reasoning tool that you may like to evaluate for
your purposes.
A possible advantage of the tool for your tasks is that it explains its
answers, step by step, in hypertexted English.
The vocabulary for writing rules in executable English is open, but the tool
can
Kristof Zelechovski wrote:
Following the URL to discover the semantic of properties is not only useful
but can also be necessary for CURIE, e.g. when the author uses a paradoxical
prefix just for the fun of it. A language without CURIE would not expose
the users to this necessity.
If you have
Note: I wrote this yesterday. My internet connection wasn't working as
desirable, but GMail told me it had been sent and I believed it. Now I
have just noticed that it hadn't; and at least one person has been
confused by the changes in the document. Sorry for this issue, and
hope this time GMail
Re: the recent microdata work and the subsequent effort to include
BibTeX in the spec, I summarized my argument against this on my blog:
http://community.muohio.edu/blogs/darcusb/archives/2009/05/20/on-the-inclusion-of-bibtex-in-html5
I think it's fair to say that the Zotero project [1] agrees
On Wed, May 20, 2009 at 2:35 AM, Toby A Inkster m...@tobyinkster.co.uk wrote:
On 20 May 2009, at 05:23, Tab Atkins Jr. wrote:
Specifically, people can use a search engine to find information about
foaf. I know that typing foaf into my browser's address bar and
clicking on the first likely
On 20/5/09 22:54, Tab Atkins Jr. wrote:
On Wed, May 20, 2009 at 2:35 AM, Toby A Inksterm...@tobyinkster.co.uk wrote:
And yet, given an example use of the vocabulary, I'm quite certain I
can easily find the page I want describing the vocab, even when there
are overlaps in prefixes such as
Document.load would be the simplified
load/save method that it would make sense to standardize IMO, since
Firefox
has it and it is needed for Web compatibility. I am concerned though that
Document.load() allows for synchronous network loads.
I'm certainly no fan of Document.load() and wish
Although it seems most browsers have adopted these APIs, HTML5 offers basically
identical APIs in the form of
document.innerHTML
or is there something that DOMParser / XMLSerializer can do that
document.innerHTML cannot?
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, May 20, 2009 at 11:56 AM, Toby Inkster m...@tobyinkster.co.uk wrote:
Given that one of the objections people cite with RDFa is complexity,
I'm not sure how this resolves things. It seems twice as complicated to
me. It creates fewer new attributes, true, but number of attributes
On Wed, May 20, 2009 at 4:02 PM, Dan Brickley dan...@danbri.org wrote:
On 20/5/09 22:54, Tab Atkins Jr. wrote:
On Wed, May 20, 2009 at 2:35 AM, Toby A Inksterm...@tobyinkster.co.uk
wrote:
And yet, given an example use of the vocabulary, I'm quite certain I
can easily find the page I want
On Wed, 20 May 2009 23:20:34 +0200, Anne van Kesteren ann...@opera.com wrote:
Although it seems most browsers have adopted these APIs, HTML5 offers basically
identical APIs in the form of
document.innerHTML
or is there something that DOMParser / XMLSerializer can do that
On 20 May 2009, at 23:10, Tab Atkins Jr. wrote:
Stuffing multiple discrete pieces of information makes things
harder for
parsing, harder for authoring tools and harder for authors. In RDFa,
each attribute performs a simple role - e.g. @rel specifies the
relationship between two resources;
On Wed, May 20, 2009 at 2:20 PM, Anne van Kesteren ann...@opera.com wrote:
Although it seems most browsers have adopted these APIs, HTML5 offers
basically identical APIs in the form of
document.innerHTML
or is there something that DOMParser / XMLSerializer can do that
document.innerHTML
Anne van Kesteren wrote:
or is there something that DOMParser / XMLSerializer can do that
document.innerHTML cannot?
Ignoring the non-web-facing functionality (like parsing from and
serializing to streams), and speaking only of Gecko's implementations,
basically the following:
1)
I dont see a way to do frame advance feature for a paused VIDEO.
Is there a way to achieve that ?
As well as frame backward also.
Thanks
Biju
24 matches
Mail list logo
