Hello OpenWeb.org, Goodbye open web

Posted on July 24th, 2008

Chris Saad, co-founder of the Data Portability movement - probably well known for having the least imaginative graphic designers . Has started up another venture, it seems mainly to capture a the current vernacular of the day - "data portability" is passe, viva le "open web."

The reasons for muddying already murky waters are ostensibly to broaden the mandate. Data portability is about the concept of openness and evangelism but the open web is about implementation issues. This is, at best, a pedantic separation of concerns that bears little fruit for benefitting anybody, but hey a launch gets more press coverage than a rebrand or a mandate change.

Further, the names seem to be misapplied - Data portability connotes FAR more technical concerns than "open web," which is supposedly a highly inclusive term - so crappy title for a useless institution.

Nomenclature aside, creating an organization to handle implementation concerns divorced from a normative architecture is profoundly unwise - a lesson taught to us by the history of international and trans-governmental organizations. The presumption of a harmonized normative ideal is naive at best, pathetically short-sighted at worst.

The web ALREADY has a standards organization . And, compared to many other industries, a very consumer focused one. Data Portability was and is a promising institution for consumer advocacy - to act as a mouthpiece for the disparate cloud of users crying out for a decentralized identity and escape from walled gardens like Facebook. The Open Web is so patently and obviously a cash-in on a buzzword it’s hard not to raise one’s hackles.

It’s also obvious that to get the support of companies like Facebook and Plaxo (read: Comcast) major surgery had to be applied to the mandate of Data Portability’s mandate - so much so, that in order to avoid alienating DP.org’s supporters Saad instead started a new thing - in effect abandoning Data Portability.

I’m disheartened by the consumption of a perfectly good domain name for something so useless or just as likely, damaging. This is a corporate consortium that can now express its will obfuscated in code and technical specifications rather than policies and protocols - we already have the IEEE, ISO and yes, even the W3C for that. They’ve taken ownership of the term and as a result fundamentally altered its meaning. From now on one will have to clarify "open web.org or open web?"

Also, what about the Apple Store? The iPhone is a impenetrable device unless you build for it - Jobs has spouted various specious technical justifications for what is a business decision of forcing developers to the phone over and above other platforms.

Citizen Journalism just got a new weapon

Posted on July 22nd, 2008

Qik, a web application that allows users to submit footage to their YouTube-like streaming video library directly from their cell-phone live as they film it has come out of closed beta.

The implications this has for citizen journalism cannot be overstated. Despite predating the invention of cellphones hand-held video cameras haven’t really hit a critical penetration sufficient for anything but the highest profile events (e.g. Boeing 747s slamming into huge tourist attraction). Cell-phones, however, have huge adoption rates; even in the developing world. The proportion of those with built-in cameras is quite high.

Qik Logo

Qik would allow individuals to take footage and make it immediately make it publicly available. Obviously this means that the time between an event and distribution of media is shortened to nearly seconds. It also means that the omnipresence of the general public can easily trump the mobility and response capabilities of professional media.

There are negative consequences which I’m sure will rear their heads before the positive potential for this platform is realized (isn’t that always the way?). Amateur paparazzi can now stalk and stream using cheap, comparatively covert means - Paris Hilton could literally be lifestreamed by cloud ofpathetic losers voyeurs.

The real potential exists in the coverage of typically conjecture-saturated incidents like police violence and other crimes, protests (I can think of a university that could’ve made use of this), accidents etc. No longer can we be content watching aftermath coverage with witness testimony distorting and falsifying information (rationally speaking, testimony from witnesses is almost always tremendously worse than no information at all). Further, we’re not reliant on the resourcefulness of the one or two people nearby with camcorders to have them at the ready.

Collaborative Ontologies

Posted on July 21st, 2008

Some you may know that I’m the lead (read: only) developer for a semantic-web knowledge management platform called JengaNote. The central purpose of which is to enable students to manage all the information they consume day-to-day so that they can learn faster, better and with a deeper understanding.

One of the central problems of the system is presenting models and interfaces for note organization. There’s essentially competing priorities of information normalization and flexibility. We’ve selected RDF as the method of information exchange because we believe it to be a compromise between these two.

There are several people who make a case against the very notion of an ontology within collaborative systems - David Weinberger perhaps most articulate amongst them. They state that it’s simply impossible to construct an ontology that will satisfy all conditions under which data would be used - moreover the work-effort to construct, maintain and enforce this ontology would be a function of the total content but isolated to a small group of maintainers rather than being part and parcel with content commitment.

They suggest that the (now typical) method of folksonomy is likely the only sustainable method of sustainable information meta-data, and that any other scheme (unless intuitively obvious to all users - as in FOAF or vCard) for ontological construction would simply fall apart or be so under enforced as to be irrelevant.

Folksonomies, for the uninitiated, are the collection of keywords associated with content. Most people view it, however, inversely - the keywords associated with a given piece of content aka “tags”. As far as I know, Del.icio.us was the first to use a folksonomy as the backbone of information organization - Flickr followed suit soon after. Now most information systems offer some sort of tag-cloud like interface - including Wordpress (the software powering this blog).

The idea being that any determination of a content item categorical membership is a probabilistic inference of the aggregate keywords for that piece of content. Usually, any user can add a tag that doesn’t exist. In some systems users can “bump” the relevance rating for a keyword - allowing for variance of applicability amongst the keyword associations.

This system is particularly useful if keywords are the method of information retrieval - as in search systems, and the content itself isn’t easily parsed for keywords (as in photos or video) or in domains where the vocabulary is naturally constrained (blogs).

Ontologies, however, aren’t merely for single-item content retrieval (like search), ontologies are useful for content association - items that share the same classification are similar by definition - this isn’t necessarily true of a folksonomy. Usually this is handled by using multiple tags to distinguish items like “steve jobs” and “drawing” to get drawings of Steve Jobs rather than photographs.

With tagging there is no implied semantic relationship between the tag and the object being tag. Moreover, tags are constrained (usually) to simple literal text phrases. These two things severely retard a vast array of information retrieval tasks that extend beyond search - which is a crutch the internet needs to cast aside as soon as possible.

Firstly, it’s language specific - English tags only apply to English speakers. One could translate the individual keywords but often the lack of context and other tasks render this impossible to automate - requiring humans to translate the text or simply to recreate the tag cloud in each language; neither is a desirable outcome. Ontologies have no such limitation since they sort things semantically - that is, based on meaning rather than expression.

Secondly, tags have an unary relationship with the content. Either a piece of content has a tag or it does not - that is all that can be said confidently about the relationship between a tag. Relevance is determined by the improbability of that tag for any random article of content and, for systems that implement, the quantity of people who “voted” that tag as relevant. Thus the meaning of the tag word is meaningless, as is the nature of its association with the content. There’s no difference between, say a photo OF Steve Jobs and a photo BY Steve Jobs if they’re tagged with “Steve Jobs”. Or, for example, to know that a picture marked “JPEG” is the file-format of the photo or a photo taken at some sort of conference for Joint Picture Experts Group.

This second point is perhaps the most salient in light of the potential of Web 3.0. How can a machine meaningfully interpret these kinds of information?

This is not to say that the problems folksonomies seek to remedy aren’t very real - given the complexity of ontological construction, elaboration and enforcement for even a highly constrained domain it seems an intractable problem to construct a generalized solution that applies to virtually any domain scope and, perhaps more importantly contributor scale.

The answer is to the problem is simple. You don’t try. Folksonomies have the singular advantage of divesting content organization away from an institution and handing it back to contributors and, just as importantly, users. Folksonomies also have the advantage of adaptive organization rather than plenary information architecture - they only organize the content they have rather than attempting to organize all content possible. Content is tagged at point of entry into the system and the vocabulary of tags is totally unconstrained to deal with new possible categories.

The obvious solution is to create a project similar to wikipedia for ontologies. Where domain experts/enthusiasts, can generate a singular definitive ontology open for public consumption via web-services for a variety of applications. It would use OWL for data-storage and provide basic inferrence services and other niceties.

The issues with this wiki-ontology would be the same as those on wikipedia, only amplified. Wikipedia suffers facet divergence issues - that is, it’s difficult or impossible to integrate different perspectives on the same issue, especially if there are more than two or three such perspectives and each is mutually exclusive. The reality here is, only one of them is right - so wikipedia appeals to democracy to define correctness. This is a servicable solution for factual information, not so useful for something entirely subjective such as ontologies (since it’s the formalization of notions of classification - a system constrained only by arbitrary self-definition - which (hopefully) regress to axioms)

Wikipedia, because it has the competing tasks of definitiveness and comprehensiveness, has established conventional “hacks” to solve the issue of disagreement - either by wedging controversy into appropriately titled article sections or simply using consensus as the version of reality they choose to represent.

A similar system could be implemented for this wiki-ontology - multiple versions of an ontology could exist in parallel and users could elect to use one ontology over another. Through time, outlying ontological constructs could be pruned and mutually compatible systems could be merged. Since we have a formalized semantic framework this process could be automated - since compatibility of ontological definitions is computable.

Like wikipedia the proportion of people who contribute to the ontologies would be very small relative to the consumers. They key here is that firms that make use of the ontologies have a very strong incentive to commit to the project because they would have influence over the ontological structures of other firms who make use of the system - competing firms would do the same and, essentially, this wiki-ontology would be a platform for establishing industry-wide consensus/standard ontology systems; which is a win for everyone especially the user who can make use of mutually intelligble services.

This collaborative ontological system is compatible with existing “data standards” groups - which are really ontology groups in different clothes. Data Portability, for example could extend its purview beyond the syntactical and tackle the semantic information tracked within various formats.

I realized, as I went through the process of installing an Ubuntu machine that Canonical takes pains many times throughout the process to remind me, the user, that Ubuntu is made by people “just like you.” That it isn’t some product produced by a company with source-code available - such as Red Hat & Fedora Core or Novell and openSUSE.

There’s nothing about the Mozilla installation process that (insofar as I noticed) demonstrated or illustrated the fact that FireFox is the output of a gigantic community and Mozilla.com/.org is but Io to the (unwieldy) cloud of people who make FireFox happen for real.

David Eaves has been talking about Mozilla’s place as standard-bearer for the open web; I’ve taken some issues with the term but the principle of leadership to maintain interoperability and moreover, promote the distribution of open source software writ large is something both I, and the Mozilla Manifesto, agree with. While David is tackling the huge, grand-strategic issues of Mozilla’s self-image and purpose; I seek to redress some pretty basic things that would go a long way to transforming Mozilla from re-branded Netscape to serious(ly welcomed) member of the open source community.

With that in mind I think there are some tweaks Mozilla can make to the overall flow of user-experience to encourage people to take notice of the greater open-n community.

Firstly, rename the link on the “get firefox” page. ‘100% organic software’ doesn’t tell you where that link’s going and thus is a bad candidate for a link name. On the landing page don’t make contradictions within the same paragraph:

As software companies go, we’re a little unusual.

is followed by:

And as a non-profit, public benefit organization, we define success in terms of building communities and enriching people’s lives.

in the margin there is a FAQ asking “what is Mozilla?” which gets this answer:

We’re a global community, a public benefit organization and an open source software project.

If you’re three things there should be three links to three different resources with clear boundaries between each describing what each facet of Mozilla is, why it’s important to the other two and what I, the person just landed there, can do to get involved in any one of the three. This reinforces the salient point that they should drop the notion and pretense of being a software company - either the community builds Firefox or Mozilla does; you cannot have it both ways.

This raises the point that it’s okay for Mozilla to be a company, Red Hat is a company and it’s a pillar of the open source community - they’re profit motivated and people respect them for it. Red Hat is touted as a major source of open source success because it enabled the view that F/LOSS can be a viable business model. Sun blends FLOSS with business in a genuine way, as does Zend. It’s not okay for Mozilla to pretend it’s a civil society actor because it’s cheaper to market than a full-fledged corporation and gives their users warm-fuzzies (they should move offices from Mountain View to Cupertino if they want to do that).

So 1) improve the installation process to make it more obvious that Mozilla is a steering group, not a software factory. Giving away source-code does not a community make, nor does having a bunch of users squawking about your product/company (like I’m doing now). It takes shared interests, values, history and risk to make a community - currently Mozilla calls the shots on all four and calls it “cooperation.”

2) Fix the getting started page to include a call-to-action for involvement. Even if it’s just adding a name to a list of newly minted users, or some other token gesture it’s about establishing a connection which you can capitalize on later. Google knows that search is just the beginning but they’ve got to get users typing text into a form first. Using locale info, IP-tables and other info it’s fairly trivial to isolate the country of origin for a user and showing people the active Mozilla participants from around them would go a long way to making the community a reality rather than a brand-promise.

Since Mozilla is about openness / Libre software, why is it almost closed source proprietary platforms (Google (yeah, like they need the traffic), Remember the Milk, LinkedIn, Topix, HowStuffWorks, Answers, YouTube (Google again), Hype Machine, craigslist, yelp!, Facebook (ha! a MSFT investment!) versus Miro and Wikipedia.

What was the rationale behind picking those sites? Brand recognition? (where’s MySpace, Yahoo! or Hotmail?) Introduction to new things? (Why Facebook, YouTube or Google Docs?) My assumption is they nabbed an “average user” and looked at their bookmarks.

Whatever the reasons, there are libre alternatives which Mozilla could promote instead of shilling the work of their scariest competitor (hint: this competitor is right beside the Landings Dr office).

Also, the actions “Work, Learn, Play, Connect” should have “Participate” added on there with appropriate information for involvement.

3) The Mozilla homepage - the default homepage for a fresh Firefox and the homepage (I would imagine) for a fairly significant chunks of the boxes running FireFox. It’s a branded Google search page. Ubuntu has swapped it out for an Ubuntu about page (very smart move) but Mozilla instead hands over their product (very quickly after boot thanks to speed and caching improvements) over to Google without so much as a second glance at the user except to encourage them to buy their crap, which has horrendous, jaw-dropping shipping charges. While Mozilla probably does a tidy business with the swag - or GatewayCDI does anyway (I’m assuming this is some sinicure, if it was a competitive bid - switch to Spreadshirt and save everyone some money)

So there are three points of contact with a user in which Mozilla could toot the horn of the open web and instead hands business over to closed, proprietary groups (some of them) antithetical to the premise of the open-web (I’m looking at you Zuckerberg). I’m sure there’s a litany of other “tweaks” Mozilla could make but if they were to implement just these three the total ‘conversion’ or ‘up-take’ or ‘evolution’ rate would likely increase - which is the metric for success when you give away your product - you need constituents not customers.

Open Web as Social Movement

Posted on July 15th, 2008

My friend David Eaves has sounded on the topic of the open web as a social movement, you can see his posts here, here and here . He fundamentally believes, and rightly so, that the scope of action to ensure informational freedom on the web is greater than technology.

I do have some issues with a few pillars of his thesis however.

Firstly, “the open web” is a really bad term for a tonne of reasons - primarily its opacity, ambiguity and inaccuracy - this term is so niche that there isn’t even a wikipedia page for it and I’m not about to deal with the flame-trolling to write one.

So, I think Dave should have made his assumptions and biases regarding the open web more explicit, since one can’t engage him on the appropriateness of a method if one doesn’t understand his version of the results.

That said, one can make a logical inference, as to what David is referring with “the open web”. That it is, the maintenance of freedom of interchange, decentralized and undifferentiated control of protocols and user-agency with regards to service providers (e.g. competition).

Dave believes Mozilla is well positioned to be the go-to source for public involvement to retain and expand these freedoms. His reason for this is simple - Firefox is on a lot of desktops and when people use it, it’s a way for Mozilla to interact with them; and Firefox, more than most other open source software is something users elect to install.

While I understand David has strong organizational affiliations, as someone more interested in the principle than any particular agent I find handing over leadership to Mozilla for this sort of thing unsettling.

Firstly, very little of Mozilla’s assets were borne of idealism - neither Steve Case or Marc Andreesen are Richard Stallman. Let’s not forget that Mozilla.org came from AOL - not exactly fertile ground for an organization of open

A Graph of the browser Wars

Secondly, Mozilla is also by no means the bastion of web standards - it’s one VERY TINY member of a standards setting group. Standards to which they adhere at their leisure just like any other member (no browser, save Lynx, is fully standards compliant).

It’s also impossible to rationally by-pass technological expertise when discussing what amounts to regulations, policy and protocols of technology. When you do this you end up inventing the internet, or clogging the series of tubes.

The open web (to be both about openness and about the web) is to be about interoperable communications protocols and specifications. Some may take exception to this, citing various examples but I suspect their scope would fall outside merely the open web (if it’s not about the web it’s not about the open web it’s about open something-else).

What is the web? Well, it’s still basically a few things some geek in a physics lab cooked up to share documents. If you were to randomly pick a web server you’d likely find it’s running Apache, Linux and MySQL. Randomly find a user-agent and you’ll find IE.

Who do you think should be the one to keep Microsoft in its place? The companies or organizations whose products Microsoft must play nice with because they host the content IE users look at, or the product Microsoft wants to kill but can’t because the Department of Justice won’t let them.

It’s the same reason Microsoft doesn’t just disable Google in Windows - access to the competition by using Microsoft tools makes their customers happy.

So, David, my question to you simple. What would a closed web actually look like? How can this be changed by a consumers? How does Mozilla stand better equipped to handle this than, say, Google (WAY more than 15 million users) or the OSI or Apple (you want enemy of standards?) ?

I believe we’ve already GOT an open web, if you disagree, what’s missing? What needs to be “opened up” that can’t be? How are my choices as a consumer different then than now?

Cognitive Drain & The Bottom Billion

Posted on July 8th, 2008

When I have the chance to reflect on this new direction my life has taken and my motivations, there’s always some new information which refines the thesis statement that acts as my driver; the prime directive for my academic and professional discipline. I use this direction to galvanize myself when I need to be focused and disciplined and to revitalize myself when I feel abject or apathetic.

I am learning how to build tools to enable the full capabilities of the globalized world solve those problems we haven’t yet.

The bottom billion, that is, the billion people on this planet earth who are in the most dire of straights; need my help - in fact they need everyone’s help.

As a geek who knows computers, communication technology and other trappings of a sophisticated internetworked world I struggle - seemingly vainly, to connect my skill set with that bottom billion. I’m not a doctor, or a geneticist or a farmer or an economist - what can I do better than anyone else that can help the people who need the most and the best assistance?

The answer to this rather tough question came by way of some depressing statistics of a different sort. I heard them first from Clay Shirkey, an author and futurist, who gave a presentation at this year’s O’Reilly Web 2.0 conference. He made some observations and parallels between the current technological change and its artifacts with that of the industrial revolution and the forgotten artifacts of that transition - namely gin.

Shirkey postulated that the Wikipedia project - in all languages and versions (discussion pages and all) constitutes about 100 million person/hours of work accumulated throughout its history.

That’s 100 million hours of volunteer time clocked to erect the controversial edifice of knowledge that is Wikipedia.

The United States of America will have watched, in 2008, 250 billion hours of television. This is almost entirely idle time (I can retrieve corroborating statistics showing qualitative viewing habits as well as frequency) spent vacuously staring at the phosphor dots.

Shirkey observed this would be approximately 2000+ wikipedia-scale projects every single year (the 100 million person/hours is total accumulated time).

The US watches about 100 million person/hours of advertisements every single weekend - that’s a wikipedia a week based on time spent being told to buy things.

The internet connected world watches over a TRILLION hours of Teevee, that’s 1,000,000,000,000!

How big is the problem of the bottom billion? 10 hours per person? That means the world would have to sacrifice 1% of their television (about 14 minutes a week per person) to solve it within one year.

The techno-savvy are the best hope of channeling that cognitive surplus to solve these problems. We are here to ensure that everyone can do something to make the progress faster, better, more sustainable and even fun (yes, starving people should have fun too).

What have Sid Meier, Mark Zuckerberg, Brin & Page and Michael Dell all failed to do that Bill Gates, Mark Shuttleworth and Nicholas Negroponte have succeeded in doing? They’ve connected being a geek to making a difference in the world where having electricity is a luxury and an iPhone is nothing more than a useless shiny brick.

Bill Gates may be the great satan to open source enthusiasts but, and this is likely to get me pinioned, I would argue that he’s doing substantially more to make the world a better place than Lawrence Lessig or Richard Stallman.

Freedom, of any sort, is obviously not un-important and I’m not saying it an either/or proposition. What I’m saying is techies, by and large, have seriously f-ed up priorities when it comes to kinds of problems they tackle. If we spent the time on developing communications standards for civil-society actors - a protocol for intercommunication and coordination, that we spent on say, the latest version of an obscure Linux distro we could have something. If we had maybe, a slightly smaller selection of wiki-software packages available and a larger collection of translation packages and platforms I think we’d be in better shape.

This is my standing challenge to geeks everywhere - what’s that trace between you and a 14 year old Malawian farm-girl? If you can’t make one and make it plainly it’s time to start thinking how you can and will.

If the geek shall inherit the earth we better damn well prove we’re smarter than everyone else who’s had a chance.

Haxor - Hack Thyself

Posted on July 5th, 2008

Without going into agonizing detail, sleep and I have have a problematic relationship. I have trouble getting to sleep - very serious trouble, to the point that once I finally get to sleep I stay asleep for way too long.

I’ve decided to modify my sleeping schedule to something a little more…idiosyncratic but I hope, ultimately more effective. I’ve adopted the 28 hour day.

I had always toyed with the idea of optimizing sleep schedule to maximize wakeful energy levels (equal to relative energy level times the number of hours awake) and this seems like the best method to ensure I get to sleep quickly, get a healthy quantity of sleep and maintain a productive wakeful period.

The 28 hour day is based explained in this XKCD comic.

It’s quite simple - every 8 hours of sleep is followed by 20 hours of wakefulness. A 2:5 ratio is much better than the typical 1:2 ratio of a 24 hour clock - more wakefulness means greater productivity.

Obviously, during the fall this schedule will be adjusted to accommodate my class times but having no 9 - 5 job means I don’t have to adhere to that schedule during the summer.

Nokia buys, opens Symbian

Posted on June 25th, 2008

Nokia, the largest handset manufacturer in the world (accounting for approximately 40% of the market) purchased their largest software platform Symbian - at least the remaining 49% it didn’t already own. It immediately relaunched the platform as an “open source” initiative under the Eclipse-style license.

While this is not a totally free licensing scheme on par with GPL, it’s certainly as open as a certain member of the competition. What’s interesting to me is that pundits tend to assume that this is Nokia directing their efforts against Android, a Google-led initiative for an open source mobile platform. While they seem like more comparable products, I really believe this is Nokia securing themselves against Apple and RIM - this is their method of battening down the hatches for the impending mobile platform wars.

Symbian is the dominant mobile platform and has been for a long time. What I suspect Nokia is hoping to accomplish is to outmaneuver Apple, RIM and the increasingly irrelevant Palm in terms of feature deployment and developer satisfaction.

As important as it is to satisfy consumers with a high-quality product it’s arguably more important to be an attractive platform for developers to deploy on. The big cloud of third-party software vendors is going to be dramatically more clever than you can ever be at making software for your app. This is, again and again, something that mobile platforms learn as readily as PC operating systems. Palm won the PDA battles by being easier to develop applications. Apple manuevered itself into a competitive space by capturing the piles of free software by switching to a BSD core and their strategy with the iPhone indicates they’re going to have to learn that lesson all over again.

Similar open source projects rarely compete with each other because the development community that’s attracted to one or the other are markedly different and steer the character of the platform in a particular direction. Look at the differences between KDE and Gnome, to suggest they compete because they fulfill the same purpose is to miss the point of serving different audiences with different preferences.

The key difference here is that hardware drives the mobile-market at the moment because there’s enough differentiating factors for certain devices to self-select for certain markets.

This is Nokia securing itself in the future market, not necessarily attempting to shut-down competition, especially from another open source project. I would imagine the only reason Nokia didn’t join Android project is that its handset provider roster made up of Nokia’s major competition -Samsung, Motorola and LG particularly.

Nokia has decided to keep its own pie rather than fight for a slice of the one it helps grow. Given their current share of the market, this is rational.

Who benefits the most from this struggle between Apple’s iPhone, Google’s Android, RIM Blackberry and now Nokia’s Symbian ? Microsoft, naturally.

While Microsoft does have its own mobile platform Windows Mobile is, in-effect, a convenient barrier-to-exit for Windows users more than a full-blown initiative. I own a WinMo phone, and while I use it as an independent device from any PC, it’s very clear it wasn’t designed to do this. These other platforms, however, are about making the handset a stand-alone device rather than a satellite screen.

Silverlight and Live Mesh offer opportunities to integrate readily with these platforms in ways that promote the Vista, Office and Windows Server cash-cows.

What can Nokia do to put itself in a position current un-beatable by any competitor? Provide support for the N-Gage APIs in this new open source initiative. A high-quality gaming API running on any device capable of Symbian would hit a niche nobody else is in.

Green Shift - it’s staying put.

Posted on June 23rd, 2008

Get it? Because red shift means it’s moving away and blue shift -…moving on.

The media has had their take, such as it is, on Dion cum Liberal Party’s submission of a Carbon Tax - dubbed The Green Shift. The variety and veracity of the opinions they publish is astounding - mainly the angry, ignorant semi-bigotry newspapers strut about as if it’s the voice of Canada. I suppose it’s an easier way to dodge things like factual rigor since they don’t need to do all that annoying work like, examining information or understanding complex problems.

I had stopped turning to newspapers for a rational, informed response to world events years ago and The Globe & Mail, National Post et al. have done little to convince me this wasn’t the right decision.

I, despite my misgivings regarding Dion’s leadership, support the Carbon Tax credit in both form and principle. I think, however, there’s some profound misunderstanding of what it all means, how it works and what’s making the Tories so edgy that they’ll send fomenting pack-dog hacks to write letters-to-Ed nationwide.

Most of the opposition to the Carbon Tax premise most of their argument on the two tried-and-true pillars of political sympathy “it’ll hurt the economy” and “it’ll hurt the poor” - I’ll note the rather disgusting notion of separating the two, but this is their logic not mine.

They suggest the Carbon Tax will hurt the economy by making it too damned expensive for our manufacturing and farming sectors to do their work and compete with the unlegislated American producers. Our farmers will then of course have no choice but to shut down and line up at the welfare office, so the logic goes and then we’ll all be out of maple syrup and buffalo.

The same basic story holds true for the manufacturing sector - in this case since most of the big (read automobile) manufacturers in Canada are American companies, these companies won’t want to pay the taxes and will move their factories elsewhere.

Sounds sensical right?

Protecting our farmers has been a serious misstep in Canadian economic history for quite some time. While I sympathize with our yeomen, market realities are what they are and the Carbon Tax does not make or break Canadian farmers; Canadians not buying Canadian farm-goods is breaking the Canadian farmer and they aren’t doing that already. Frankly, I’m tired of my (and your) tax dollars being spent maintaining their polluting machinery so they can continue to under-perform at the grocery store. So it’s a matter of democracy here - a majority of Canadians are not farmers and I don’t think appreciate giving them special treatment over anyone else having a tough time getting paid to work.

Our manufacturing sector is hardly in danger if it opts into less polluting technology which will do two things - make Canada a leader in Green manufacturing and put money into OUR research and development community to spur more efficient manufacturing methods. It’s really expensive to shut-down a unionized plant and set-up a new one and GM is strapped for cash. Toyota is devoted to developing green methods and with the incentives to do so as the Green Shift outlines, it’ll encourage expansion, not reduction of capacity.

Here’s how it’ll play out for GM, Magna etc. They’ve gotta pay this tax, $40 a tonne after four years (adjusted for inflation). So in order for them to shut down the plant this tax has to be greater than the total cost of shutting down the plant (severance pay etc.), building a new one elsewhere and staffing it up, at worst. They could, alternatively, invest in better manufacturing practices to reduce the tax year-over-year and sell this technology to other companies and potentially turn a profit. What would you do if you were GM?

What about the poor? The poor often get trotted out by Conservatives to prove this point or that and then are unceremoniously crammed back in their box when they need to launch policy. In this case many critics suggest that the Carbon Tax will adversely affect the poor.

This just doesn’t pan out - the tax is based on usage is thus progressive. The richer you are the proportionally more carbon you consume - through your SUV, jet-setting, wastefully manufactured goods, etc. While poor people still produce carbon, they do so at a fraction the quantity of the rich (around 25 - 30% the amount).

If one does as The Green Shift suggests and use this policy to shift the revenue from the tax back to the poor you’ve created a virtuous cycle.

The economic argument criticizing the Carbon Tax is arguably the weakest - an economists first resort would be exactly this policy. You tax things that are bad - like pollution, not things that are good - like income; so this is better than some of the things we take for granted (income and property tax).

The danger, some argue, lies in the fact that the Liberals would now have this big chunk of change to squander as they’ve done in the past. (when was the last time a government was hailed as “fiscally prudent” even by their detractors?) Since the plan outlines expenditure as well as collection this is less of a concern, there’s a direct A-to-B correspondence between how the money is gained and spent.

A big issue some of the clever armchair economists argue is the value of our goods in the international market, particularly in combination against our high dollar. The problem with this assertion is it makes the un-motivated assumption that our carbon emission will be static for two reasons. Firstly, no innovation will take place, while this creates a tidy economic model it’s just not the case - especially in Canada. Secondly, the carbon-tax will fail to depress oil consumption because nobody slows down and nobody innovates. The carbon-tax will spur exactly these two activities - that’s what these kinds of taxes do.

Further, our largest trading partner, the United States has both presumptive leaders pledging to put a price on carbon - thus, we might face tariff barriers from the and the EU if we don’t implement Carbon Tax.

The biggest plus for the carbon-tax is the price stability of fuels. Economies aren’t hurt by high-prices they’re hurt by price instability. Carbon-taxes, versus say a cap-and-trade, introduce greater price stability which is probably the best thing for the economy when it comes to fuel.

My issue, perhaps in my rabid cut-throat economic-environmentalism, is that the Carbon Tax doesn’t go far enough. Primarily because it targets exclusively carbon. There are plenty of other emissions just as harmful to our environment which are much more closely associated with our Big Polluters (the 70 worst polluters in Canada). Thankfully, a standard already exists to convert those emissions into equivalent tonnes of carbon, making the application of the tax to them pretty straightforward. This conversion is called the Global Warming Potential (with CO2 being, by definition, 1).

Further is the tacit assumption that the tax will, in four years, bring our carbon emissions to 375 million tonnes - some estimates put our output at twice that level in business-as-usual models.

From Here To the Semantic Web

Posted on June 22nd, 2008

I outlined earlier the inherent difference between the web now and the web to be. That is, the difference between Web 2.0 and Web 3.0. A big question that comes out of that description is how will current use of technology change to allow for this Web 3.0 to emerge?

I argued that Web 2.0 and 3.0 aren’t defined by their technology per se. They’re defined by their usage scenarios which imply, but don’t necessitate, innovation in software. Web 2.0 didn’t do anything new it just did it with new people in a new space. JavaScript has been around for as long as Netscape, XML was created by a 161 people a decade ago. Web 2.0 introduced the notion that everything you do on a computer could be done with a browser and that the web could become as valid a medium for communication as any other - including real-space.

Web 3.0 extends that, it pushes the boundary and posits that not only is the Web as good as anything else, it may, in fact, be better for a tonne of things. As our democratic ideals start catching up to technology we want to develop systems whereby everyone can have a meaningful contribution, where discussion really is discussion and not a room full of murmuring, or an epistemic oligarchy. Through the web, we can enable what is intractable in reality - the promulgation of the ideas, thoughts and discourse of hundreds of thousands, millions or even billions of people in a meaningful way.

The key distinction between the web now versus the web 3.0 is that word ‘meaningful’. The web already integrates everybody with everybody else to some degree, but it makes it a devil of a task to discover content, people and ideas that are meaningful and relevant - especially for humans.

Enter the semantic web. The semantic web, as the name implies, will provide a mechanism for machines to have a facilitated comprehension of meaning - to aid us in discovering new ideas, people and content by the association of meaning rather than hypertext references.

Web 1.0 and even 2.0 has a single-dimensional association between content (web pages/sites), this association is the hyperlink. The context of where the hyperlink appears on a page let’s a human reader know what that association actually means - a machine cannot understand that, and even if it could it can’t expand upon that through entailment. The semantic web allows an unlimited dimensionality of associations between content - even ones that are emergent rather than ascribed.

How will this look? What kinds of tools and purposes will we have for this kind of association? We see some fledging attempts at semantic assocation by way of “tagging”. Tagging works best as a controlled vocabulary - that is for any given subject attribute, there is one and only one word to describe it. Tags tend to break down as semantic data because people want to be comprehensive in their tagging and thus enter semantically redundant tags. Tagging is a step below controlled vocabulary which is arguably the least semantic of the semantic methods of content organization.

The next tier of semantic technology, which provides more information as to the meaning of content is a taxonomy. We’re all familiar with taxonomies even if the term isn’t. The traditional way of categorizing the animal kingdom is a taxonomy (Domain, Kingdom, Phylum, Class etc.), the Dewey Decimal Classification and Library of Congress Classification systems are taxonomies. These provide once described to a machine, a certain kind of semantic understanding - that of generality and abstraction. What is true of a parent element must also be true of its children, e.g. “What’s true of mammals is also true of apes.” This is significantly richer than the rattle-bag of attributes that tagging introduces but it’s most constrictive - typically an entity can only be in one place on a taxonomy and what if the taxonomy isn’t fully understood?

The third semantic system available combines aspects of tagging and taxonomy - only in this case it’s the tags that exist within the taxonomy rather than the entities, and that is the thesaurus. Thesauri allow machines to understand equivalance in tags, homographic relationships while still having the hierarchy and classification inherent to taxonomies.

The fourth and final system is the ontology. The ontology takes the basic framework of the thesaurus and applies logical rules to it. Whereas the thesaurus has no notion of mutual exclusion or entailment; this is something the ontology enculcates. In a biological ontology one need only specify an ape is a mammal rather than it is both a mammal and warm-blooded, because the ontology understands that although these are different things, one entails the other - it would also understand its impossible for an ape to be cold blooded.

I’ve described these systems in deliberately abstract terms because the actual applications are impossible to foresee - however I envision our migration to the semantic web essentially climbing these steps of increasing semantic robustness. Each step gets further and further away from the kind of usage scenarios in which we typically engage with existing technology.

I don’t believe we’ll all hop-in head-first into developing personal ontologies and deploying ontological tools, just as we haven’t gone head-first into the social networking tools. The pace is lightning fast but not instantaneous.

As users become accustomed to the workflow inherent to each one and automation tasks make them almost redundant we’ll see a steady progression.

The technology underpinning all of them, RDF, much like XHTML for the remainder of the web, is robust and simple enough to maintain viability throughout - the more advanced technology GRDDL and OWL in partciular, I predict won’t see adoption until we start moving up the semantic system ladder.