Lately, there have been two semantic web widgets for Opera:
- Widgnaut, a widget version of FOAFNAUT (FOAF visualiser)
- Tabulator, a widget version of TBL’s tabulator(generic RDF browser)
Both of these seem to work much better than their webpage equivalents.
So there is a use for these widget things after all?
Dietrich Kappe has done another of those social network studies of book consumption using Amazon’s
Other Customer’s also Bought...
(The original (at least, the first one I heard about) being Valdis Krebb’s Study of polarised political book buying).
The graph isn’t so pretty as Krebb’s, but it is more interesting in that it shows a more complex picture than the rather-to-be-expected left/right political divide of American politics.
If you’ve written or read similar studies, I’d appreciate it if you’d link to ’em in the comments.
I came across a post about semantic markup and accessibility citing a remark I had made about how, for all the talk about semantic markup in the web-dev community, HTML isn’t a very semantic markup language.
The post goes so far as to say:
[…] when you mark up a page in HTML you shouldn’t get too hung up on the semantic meaning of the elements.[…] What you should be concerned about […] is describing your page elements in such a way as to make them easier to use by screen readers, keyboard-based browsers etc. For example, don’t ask ‘is this set of elements really an unordered list?’ but do ask ‘if I mark up this set of elements as an unordered list, does that make my page more accessible and easier to use?’
However, I feel this has got things backwards – accessibility should, and will be, a consequence of good semantic markup.
Ideally, accessibility is a game for two: you provide the document in as semantic a form as you can, the user agent interprets that document as intelligently as it can. And if the user agent isn’t smart enough to handle all the semantics of your document today, then it will be tomorrow. Admittedly, in practice, a lot of things have to be dumbed down for Internet Explorer – though these tend to be of the bells and whistles rather than semantic variety, but it is usually better to aim at solid principles than the moving target of particular user agents.
In theory, there’s lots of ways we can markup user interfaces – XUL, XBL, XForms, ZAML
But the div doesn’t have to be bland anymore.
The Role Attribute
Yes, the role attribute is going to save the day.
You can read more about how wonderful the role attribute is at Mark Birbeck’s blog.
openacademia is an initiative to collect, share, publish and manage bibliographical information, the Semantic Web-way.
Information about scientific publications is often maintained by individual researchers. Reference management software such as EndNote and Bibtex help researchers to maintain a personal collection of bibliographic references. (These are typically references to one’s own publications and also those that have been read and cited by the researcher in his own work.)
The Amazon Historical Pricing web service gives developers programmatic access to over three years of actual sales data for books, music, videos, and DVDs (as sold by third-party sellers on Amazon.com). Sellers can use Amazon Historical Pricing to make informed decisions on pricing and purchasing.
Unfortunately it seems to be limited to getting 10 items at a time:
* Returns pricing information for up to ten items per request
Which will limit the potential for this to be used by book historians as a kind of barometer for cultural or economic change.
Simile at MIT have recently come up with a timeline widget api – google maps for timelines. It lets you plot events and time ranges (taken from either XML or JSON) onto timelines, and it’s all pretty darn good.
It should facilitate all kinds of interesting visualisations. There are a few really interesting examples up already – my favourite is the timeline of the shooting of JFK.