On Mon, 18 Jul 2011, David Karger wrote:
[...] the Exhibit data visualization framework
(http://simile-widgets.org/exhibit) [...]
The goal of Exhibit is to make it easy for non-programmers to embed
interactive data visualizations in their web pages.
HTML has a number of features intended
On 01/20/2012 02:24 PM, Ian Hickson wrote:
Thanks for taking the time to look at this.
On Mon, 18 Jul 2011, David Karger wrote:
[...] the Exhibit data visualization framework
(http://simile-widgets.org/exhibit) [...]
The goal of Exhibit is to make it easy for non-programmers to embed
On Fri, 20 Jan 2012, David Karger wrote:
However, in our use case, it is in a sense coincidence that our tags
are being examined by a script. The _purpose_ of our tags is to provide
the same kind of semantic structuring as img or author or navbar
tags: specifying that certain elements,
OK, per Ian's suggestion I'm starting a new thread on a problem that I'd
hoped html5 would solve for us. As far as I know the problem still
exists so I'm going to raise it here. I'm coming late to the discussion
so will surely retread old territory (for example,
On Mon, 18 Jul 2011 16:22:42 +0200, David Karger kar...@mit.edu wrote:
Another approach would be to use the catchall html5 data- prefix for
attributes. We could certainly prefix all of our specialized attributes
with the data- prefix, which would turn those attributes valid for
html. This
Yes, we could, but it doesn't address the two objections I raised to
data- prefix:
1. it isn't actually a data attribute, so prefixing with data seems
odd (appearance; minor)
2. there's no way to guarantee someone else won't use the same
data-exhibit prefix, causing incompatibilities
On Mon, 18 Jul 2011 16:33:47 +0200, David Karger kar...@mit.edu wrote:
Yes, we could, but it doesn't address the two objections I raised to
data- prefix:
1. it isn't actually a data attribute, so prefixing with data seems odd
(appearance; minor)
It is custom data implemented by a
On Mon, Jul 18, 2011 at 7:33 AM, David Karger kar...@mit.edu wrote:
Yes, we could, but it doesn't address the two objections I raised to data-
prefix:
1. it isn't actually a data attribute, so prefixing with data seems odd
(appearance; minor)
You seem to have mentally associated the data-*
The html5 spec states that
Custom data attributes
http://dev.w3.org/html5/spec/elements.html#custom-data-attribute are
intended to store custom data private to the page or application, for
which there are no more appropriate attributes or elements.
These attributes are not intended for use
On Mon, Jul 18, 2011 at 10:33 AM, David Karger kar...@mit.edu wrote:
Yes, we could, but it doesn't address the two objections I raised to data-
prefix:
1. it isn't actually a data attribute, so prefixing with data seems odd
(appearance; minor)
It's data in the sense that it's being used to
On Mon, Jul 18, 2011 at 11:23 AM, David Karger kar...@mit.edu wrote:
The exhibit attributes are not associated with any server, and are not
associated with any particular data items being delivered by any server.
Rather, they are part of generic software not associated with the server
(see
Dear whatwg,
I wish to submit a comment regarding the (non) use of namespaces in
html5. But I hope you might help me track down the relevant issue off
which to hang that comment. Some time ago I found a lengthy discussion
of whether html5 should use namespaces, with an over-simplified
On Mon, 18 Jul 2011, David Karger wrote:
I wish to submit a comment regarding the (non) use of namespaces in
html5. But I hope you might help me track down the relevant issue off
which to hang that comment. Some time ago I found a lengthy discussion
of whether html5 should use
13 matches
Mail list logo
