[Bug 25353] [DataCue] change DOMString? text to any? value

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25353

--- Comment #19 from Brendan Long <self@brendanlong.com> ---
This makes sense to me, except for this:

> Incidentally, defining the @type values doesn't need us to also define the
> format of the JSON blob that's in @metadata, seeing as we're leaving the
> interpretation of that blob to the JS dev. They can do whatever data
> analysis/filtering they need.

If the metadata attribute has no defined content, then we force devs back into
the dark ages of web development: Try everything we can think of and hope we
didn't miss something. Or more likely, use the format that [your favorite
browser] uses and ignore all of the others.

I think it would be worthwhile to standardize the content for each type, and
expose everything that isn't standardized as an unparsed DataCue, since at
least that way everything would be consistent. Having undefined JSON is worse
than undefined binary, because the binary should be the original data, while
the JSON is "someone's interpretation of what would be useful in that data".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 19 May 2014 15:06:59 UTC