Posts tagged 'semanticweb' | What Not How | http://duncan-cragg.org/blog/

About All Things...

Declarative, Mobile 2.0, REST, Cloud, Web 2.0, Ajax, Publish / Subscribe, Event-Driven Architectures, JSON, Atom, Microformats, Linked Data, P2P, Identity, Copyright, Multimedia, Cyberspace.

...taking programming beyond:
Threads, Message Queues, Client-Server, CORBA, Web Services, SOAs, Agents, Synchronous Architectures, Imperative Programming - and even Applications, Desktops and Documents

Duncan Cragg...

...works for ThoughtWorks UK; originally from April 2002 to July 2007 and now recently re-joined. Previously worked as a Web Architect for the Financial Times.

...went to both UCL and Imperial College of the University of London (in the Eighties); specialising in Logic during his MSc.

...wonders when his LinkedIn Account will be useful

...has a phone-cam, and used it on himself once, just before his weekly shave:
Photo of Duncan Cragg

...can be contacted by and followed on Twitter.

Posts tagged 'semanticweb'


The Basics \| The Object Network January 20, 2012 18:07 Updated: January 23, 2012 19:45 Right, let's get started with some basic conventions in the Object Network! This part in the Object Network series will cover URLs, HTTP headers and some common JSON patterns. Updated 23/1/12: I changed the URLs in the example to have one of each type. ... Read "The Basics \| The Object Network" semanticweb ■ ■ architecture ■ ■ web2.0 ■ ■ microformats ■ ■ rest ■ ■ json ■ ■ forest ■ ■ object-network ■ ■ Why we should link up our Web APIs \| The Object Network January 19, 2012 20:58 Updated: January 22, 2012 16:05 OK, I'm trying to take a Big Idea and make it as Simple As Possible to grasp. If we link our JSON data together and use the same formats, then our mobile, browser and server apps can become much simpler - through clean, stable, common, shared, re-used code - and much more powerful - through clean, stable, common, shared, linked, cached data. This is the second part in the Object Network series, which will guide you away from building isolated Web APIs to engaging in a linked-up data landscape. ... Read "Why we should link up our Web APIs \| The Object Network" semanticweb ■ ■ architecture ■ ■ web2.0 ■ ■ microformats ■ ■ rest ■ ■ json ■ ■ forest ■ ■ object-network ■ ■ Introduction \| The Object Network November 29, 2011 23:11 Updated: January 22, 2012 16:03 It's interesting to compare the current growth of Web APIs with the early growth of the Web itself. To save you jumping those links: the Web dramatically beats the APIs. I believe that the most likely cause of such relatively slow growth (in what should be a booming ecosystem) is that each API forms a closed silo and cannot benefit from any network effects. Every API is different and there are no links between them. There usually aren't any links within a silo. You can't even use a given API without first consulting the documentation. The Object Network is designed to fix this, with linked-up JSON in common formats. This will allow easier mashing, sharing and cacheing of data and allow client code to be shared and reused. ... Read "Introduction \| The Object Network" semanticweb ■ ■ architecture ■ ■ web2.0 ■ ■ microformats ■ ■ rest ■ ■ json ■ ■ forest ■ ■ object-network ■ ■ Web Objects Ask, They Never Tell \| The REST Dialogues August 13, 2009 11:43 In an exclusive nine-part dialogue with an imaginary eBay Architect, we present an accessible discussion of the REST vs. SOA issue. Although eBay have what they call a 'REST' interface, it is, in fact, a STREST interface, and only works for a few of the many function calls that they make available via SOAP. In this dialogue series, I argue the case for eBay to adopt a truly REST approach to their integration API. Part 9: Web Objects Ask, They Never Tell ... Read "Web Objects Ask, They Never Tell \| The REST Dialogues" semanticweb ■ ■ architecture ■ ■ declarative ■ ■ publishsubscribe ■ ■ p2p ■ ■ app ■ ■ microformats ■ ■ dialogue ■ ■ event-driven ■ ■ rest ■ ■ scalability ■ ■ rest-observer ■ ■ Microformats Challenge Web Feeds and Web APIs! June 7, 2006 19:10 Microformats are subversive: they not only challenge the approach of full-blown Semantic Web approaches, but even question fundamental Web 2.0 building blocks such as Web Feeds and Web APIs. I recently attended XTech 2006, where there were a few talks related to Microformats. After summarising these talks, I'll finish with my shocking revelations about the subversive nature of Microformats! ... Read "Microformats Challenge Web Feeds and Web APIs!" semanticweb ■ ■ xtech ■ ■ declarative ■ ■ web2.0 ■ ■ publishsubscribe ■ ■ app ■ ■ microformats ■ ■ microsummaries ■ ■ rest ■ ■ atom ■ ■ Welcome to 'What Not How' March 22, 2006 17:00 Declarative Architectures focus on the What, not the How, of programming. The How has dominated the field - perhaps 80% of programming is done in the traditional Imperative style, where we tell the computer How to do a task in explicit steps. I'd like to show in this blog how Declarative Architectures and technologies are not just an interesting sideshow to the main Imperative attraction, but a complete and powerful programming alternative in their own right - indeed, one which has already dominated certain fields. Imagine being able to simply express What we want the computer to do - to give it constraints and rules - then let it work out for itself How to achieve our goals. I believe that saying What, not How, will become the dominant paradigm in programming. ... Read "Welcome to 'What Not How'" semanticweb ■ ■ architecture ■ ■ declarative ■ ■ web2.0 ■ ■ socialsoftware ■ ■ p2p ■ ■ event-driven ■ ■ rest ■ ■