PUBLIC MARKS with search proposal

Data Walk: Bringing Demographics to the People is a project proposal that seeks to unfurl one of the most used data sets into the real world by mapping Census data directly onto the NYC landscape.

Recently the JSR for standardizing injection annotations was announced. I think the proposal is going in the wrong direction, and would like to outline why in this post.

The following is a proposal for the use of machine tags for content related to Bucketworks. I’d love feedback from people familiar with machine tags, and people involved with Bucketworks.

Then, at the back, I wanted to include a section of stuff that I'm working on. (I'm supposed to be writing a book proposal so I've bound all my notes in here hoping it will spur me on.)

Karl Dubost, who has recently left the W3C, has a proposal for Data Independence And Survival Best Practices that he is looking for feedback on. If you are interested in this topic, please take a moment to consider his proposal and provide feedback to him (not me.)

This visualization is a concept for the LizardFeeder and it’s built with jQuery and SVG plugin. Code is a mess, so I’ll post only some (retouched) screenshots.

This is at present a braindump of an idea I had to extend RDFa to use as a templating language for building web pages. It is not by any means finished or implemented, but it is a starting point for further discussion as to how such a thing should work.

Proposal and distribution of the SVG Map profile specification.

ECMA Script 4 instead chose to focus on obscure problems like let-versus-var scoping rules. The result was an overly bloated and complex proposal that was destined to be scrapped, and more importantly, would have not pushed the next generation of web applications even had it succeeded. [...] And that’s why Objective-J is different.

Comment annoncer que son objectif c'est de faire de la daube.

Atom Info Proposal Improving the human readability and understanding of Atom feeds

This proposal does sound appealing, but I agree with the others that it's too draconian.

What strikes me most plainly about this design is how the effect of a big, lumbering organisation can impact on a redesign. A good few months ago, or maybe years, when this proposal was first taking shape, it was probably the time when curved gradients, reflections and like were at the forefront of the ‘web 2.0 aesthetic’. Thing is, it takes any large organisation ages to get their shit together. Which is why designing to visual trends such as this is so risky. If your organisation can’t react quickly enough to keep up, then go the classic design route every time. If you don’t, your design will look dated within months. Or, in this case, even before it’s launched.

proposal to establish a reasonable privacy balance in social networking environment.

the question of whether there is a 'default' XML processing model, and if so what it looks like.