Comments on: Microformats, dark data and CSS - part 1 http://hexmen.com/blog/2008/07/microformats-dark-data-and-css-part-1/ On programming, and other things... Thu, 20 Nov 2008 12:45:03 +0000 http://wordpress.org/?v=2.6.2 By: Ash Searle’s Blog » Blog Archive » Microformats, dark data and CSS - part 2 http://hexmen.com/blog/2008/07/microformats-dark-data-and-css-part-1/#comment-31026 Ash Searle’s Blog » Blog Archive » Microformats, dark data and CSS - part 2 Mon, 21 Jul 2008 14:52:06 +0000 http://hexmen.com/blog/?p=52#comment-31026 [...] Ash Searle’s Blog On programming, and other things… « Microformats, dark data and CSS - part 1 [...] [...] Ash Searle’s Blog On programming, and other things… « Microformats, dark data and CSS - part 1 [...]

]]> By: Erigami http://hexmen.com/blog/2008/07/microformats-dark-data-and-css-part-1/#comment-31021 Erigami Fri, 18 Jul 2008 21:01:10 +0000 http://hexmen.com/blog/?p=52#comment-31021 You hit the nail on the head. Using the title attribute is a terrible, terrible idea, as it exposes machine readable information to the user. I completely agree that using the class attribute is a good way to go. While you're talking about repurposing the class attribute, it's worth thinking about the extra text that the hformat producer is forced to put into human readable HTML. For hReviews, the <i>rating</i> has to go into plain text. This is an absolute pain in the ass. It means any site displaying the hreview has to play silly CSS tricks to hide the "best" and "worst" attributes (and even the score itself, if they want to display a graphic instead). Including machine-readable information in human-readable HTML also falls into the "terrible, terrible idea" category. I'm not sure what you're going to suggest in your part two, but it would be nice to see a general mechanism for storing all uformat attributes in a single class attribute. You hit the nail on the head. Using the title attribute is a terrible, terrible idea, as it exposes machine readable information to the user. I completely agree that using the class attribute is a good way to go.

While you’re talking about repurposing the class attribute, it’s worth thinking about the extra text that the hformat producer is forced to put into human readable HTML. For hReviews, the rating has to go into plain text. This is an absolute pain in the ass. It means any site displaying the hreview has to play silly CSS tricks to hide the “best” and “worst” attributes (and even the score itself, if they want to display a graphic instead). Including machine-readable information in human-readable HTML also falls into the “terrible, terrible idea” category.

I’m not sure what you’re going to suggest in your part two, but it would be nice to see a general mechanism for storing all uformat attributes in a single class attribute.

]]> By: microformatique - a blog about microformats and “data at the edges” : A Discussion on “microformats and dark data” http://hexmen.com/blog/2008/07/microformats-dark-data-and-css-part-1/#comment-31020 microformatique - a blog about microformats and “data at the edges” : A Discussion on “microformats and dark data” Tue, 15 Jul 2008 21:52:32 +0000 http://hexmen.com/blog/?p=52#comment-31020 [...] Ash Searle has a thoughtful, though a little inflammatory, discussion of the issue of embedding data.... Worth a read, though the occasionally overly provocative term is best ignored to get to the substance of the article. Posted by john on Tuesday, July 15, 2008, at 5:52 pm, and filed under Uncategorized. Follow any responses to this post with its comments RSS feed. You can post a comment or trackback from your blog. [...] [...] Ash Searle has a thoughtful, though a little inflammatory, discussion of the issue of embedding data…. Worth a read, though the occasionally overly provocative term is best ignored to get to the substance of the article. Posted by john on Tuesday, July 15, 2008, at 5:52 pm, and filed under Uncategorized. Follow any responses to this post with its comments RSS feed. You can post a comment or trackback from your blog. [...]

]]> By: Jake Archibald http://hexmen.com/blog/2008/07/microformats-dark-data-and-css-part-1/#comment-31019 Jake Archibald Tue, 15 Jul 2008 15:21:31 +0000 http://hexmen.com/blog/?p=52#comment-31019 Just to clear one thing up... we (the BBC) haven't back-tracked on our class -data proposal, we're still happy with it. In true BBC fashion I tried to keep the article unbiased and point out the pros and cons of each proposal including our own, which is by no means perfect. However, that's not to say we've made our mind up and we won't accept anything but our proposal. We're certainly open to ideas. Looking forward to your follow-up post. Just to clear one thing up… we (the BBC) haven’t back-tracked on our class -data proposal, we’re still happy with it. In true BBC fashion I tried to keep the article unbiased and point out the pros and cons of each proposal including our own, which is by no means perfect.

However, that’s not to say we’ve made our mind up and we won’t accept anything but our proposal. We’re certainly open to ideas. Looking forward to your follow-up post.

]]>