It’s just data

Doctrine of Minimum Necessary Disclosure

Ryan Tomayko Schemas can be useful when placed far enough up the stack. (i.e., don’t bake schema and language binding in at the protocol level.) Just because WSDL sucks doesn’t mean describing representations using some formal schema is a bad idea

The right question is not “schemas: yes or no?”.

The right question is: what is the absolute minimum you can require in order to achieve meaningful interop?

HTML’s A element is a good example.  XSD used in the context of WSDL is a bad example.

See also: loose coupling.


Six months later and we still don't need WADL

It’s six months later and we still don’t need WADL ....

Excerpt from BitWorking | Joe Gregorio at

On Web Service Definition

There’s a flurry of discussion about whether or not, in the world of REST, you need some sort of formal specification for the services you’re offering. My conclusion: yes, but in a very application-specific way....

Excerpt from ongoing at

On Web Service Definition

There’s a flurry of discussion about whether or not, in the world of REST, you need some sort of formal specification for the services you’re offering. My conclusion: yes, but in a very application-specific way....

Excerpt from ongoing at

This Week's Semantic Web

Selected links related to Semantic Web technologies for the week ending 2008-01-28, all weeks . Also available in RDF as linked data or via GRDDL . In the Media Podcast: Jon Udell interviews Richard Wallis on libraries, the Talis and the Semantic...

Excerpt from Planet RDF at

Add your comment