Master Foo's Taxation Theory of Microformats

May 1, 2006, 10:17 AM —  ITworld.com — 

One bright spring morning in 2006, a delegation of knowledge management experts arrived at the zenith of Pentimenti mountain to meet with Master Foo. Their trip to the mountain top had been a noisy one, featuring a non-stop debate about ontologies, RDF, XML and the Semantic Web.



As they approached him, Master Foo stuffed lumps of his flowing gray beard into his ears to drown out the noise. The knowledge management experts on seeing this, fell silent and sat down.



"Are you familiar", Master Foo began, "with the concept of Value Added Tax?".



The experts were taken aback by this question. Coming from anybody else other than Master Foo, it would have elicited a dismissive response. However, Master Foo's reputation for bizarre analogies was well known to the experts.



"It is a form of taxation in which the value chain itself collects tax on behalf of government.", one of the experts explained. "Enterprises that buy goods to sell on, can re-claim the value added tax (VAT). Only the final consumer actually pays the VAT."



"Indeed", said Master Foo. "Only the consumer pays the VAT. Now, pretend that complexity in information systems is a form of taxation. Would the VAT model be an appropriate model?"



"Hmmm. I don't think so", another expert began. "In information systems, complexity is normally spread out along the value chain. If I publish some information in a custom XML format for example, all consumers and intermediaries who process that information have to pay the XML complexity tax. They need to know about my custom schema, about validation, about stylesheets, about transformation and so on."



"Indeed", said Master Foo. "Now who benefits from the fact that the information is in XML?"



"Well, everyone benefits", responded the expert, puffing out his chest. "Structured information is fundamentally more useful than unstructured information all the way up and down the value chain!"



Master Foo stroked his beard. "But what if I just want to see a piece of information or print it or search it or e-mail it or copy/paste it into my word processor? Should I have to pay the XML complexity tax for these simple requirements?"



"Well..., no, I suppose not.", replied the expert, wondering what sort of trouble he was letting himself in for with this answer.

Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world

I like it!
Post a comment
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
peer-to-peer

Brian Proffitt
Microsoft/Novell: Breaking Down the Coupon Numbers

Esther Schindler
Drupal's Dries Buytaert on Building the Next Drupal

Tom Henderson
Top Ten General Operating Systems Rants

pasmith
PS3 motion controller delayed; goes up against Project Natal

sjvn
Neolithic Windows security hole alive and well in Windows 7

claird
Perl source code comparison makes for good reading

mikelgan
Cell phones don't create stress or interrupt much

Sandra Henry-Stocker
How to: The Unix Interview

 

Where Google Chrome security fails: the password
I heard mention that the Chrome OS will have some sort of encryption available a la bitlocker. If it's possible to encrypt personal data using another password or key, then it may have potential for very secure data.... And Ubuntu has an 'encrypt home directory' option, perhaps google should follow suit.
- Dann

Join the conversation here

The Daily Tip

The Daily TipQuick, practical advice for IT pros. Made fresh daily.

Hot tips:

Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.

Newsletters

Subscribe to ITWORLD TODAY and receive the latest IT news and analysis.

I would like to receive offers via email from ITworld partners.
By clicking submit you agree to the terms and conditions outlined in ITworld's privacy policy.
Marketplace