3 ms·

One true semantic context is of course a pipe dream, theres 2 reasons I would like to be able to define whatever tag I want. 1. My markup is cleaner, <contextm

One true semantic context is of course a pipe dream, theres 2 reasons I would like to be able to define whatever tag I want. 1. My markup is cleaner, <contextmenu> vs <div id="contextmenu">, this has implications on my javascript and css (both in terms of speed and cleanliness) 2. API and "microformats" are trivialised, this is of course also dependant on producing parseable (x)html (another decision I really dont understand) but why on earth is http://api.flickr.com/services/rest/?method=flickr.people.getPublicPhotos&api_key=d6c998c73b6ba60e7b31b83618909afe&user_id=69845378%40N00 http://api.flickr.com/services/rest/?method=flickr.people.ge... different from http://www.flickr.com/photos/daleharvey http://www.flickr.com/photos/daleharvey they really dont need to be

jerf 17y ago
Yes, as a direct consequence of the fact that I don't believe in One True Context, I think the proper solution to HTML 5 is to say "Look, tags can be anything, here's enough CSS to style your arbitrary tags" (which we pretty much have, CSS 3 removed the last browser-only magic by letting you futz with tables), and everything else should be a separate standard. That said, I think this approach even sort of mostly works already, albeit with some pain and some JS hackery required. I just want it in the standard. And if we were doing that, I would ask for some events around tags, so I could in the <head> register a "tag creation" listener for, say, <calendar>, and so when that tag is encountered, use JS to populate it with stuff the browser understands. Alas, I am not the standard maker.
blasdel 17y ago
The Flickr people thought naked RPC via URL query strings was somehow RESTful just because you can use GET. They didn't have a fucking chance of noticing the existence of the Accept header. Microformats are bullshit when you have <link> and HTTP!

jerf 17y ago

Yes, as a direct consequence of the fact that I don't believe in One True Context, I think the proper solution to HTML 5 is to say "Look, tags can be anything, here's enough CSS to style your arbitrary tags" (which we pretty much have, CSS 3 removed the last browser-only magic by letting you futz with tables), and everything else should be a separate standard. That said, I think this approach even sort of mostly works already, albeit with some pain and some JS hackery required. I just want it in the standard. And if we were doing that, I would ask for some events around tags, so I could in the <head> register a "tag creation" listener for, say, <calendar>, and so when that tag is encountered, use JS to populate it with stuff the browser understands. Alas, I am not the standard maker.

blasdel 17y ago

The Flickr people thought naked RPC via URL query strings was somehow RESTful just because you can use GET. They didn't have a fucking chance of noticing the existence of the Accept header. Microformats are bullshit when you have <link> and HTTP!