• Feeds

    Subscribe in a reader

  • Ads

Web description

On a lark, I decided to start lurking in public-web-http-desc@w3.org. I’m interested to see how this discussion evolves. Specifically, I’m most interested to see what scenarios they specifically decide not to support.

Standing up and saying “we’re not going to do X” is an important step in the development cycle. I think XSD would have been better off if this had happened more often during its infancy.

Description languages are models, and as such they are subject to the tradeoffs involved in modeling. Specifically, they must find the right balance between generality, efficiency of representation, and precision (the ability to provide high-fidelity renderings of the concepts they model).

In my thinking the ideal result would be an efficient and precise rendering of a small number of concepts specific to a small number of critical scenarios. The tendency with these things is to go super-abstract and over generalize, which leads to models that are neither efficent or precise.

I guess we’ll see what happens.

#1 Mike Champion on 5.26.2005 at 5:43 AM

It will be interesting to see if theygo thru the 6 Project Stages on the classic office poster: 1) WILD ENTHUSIASM 2) DISILLUSIONMENT 3) TOTAL CONFUSION4) SEARCH FOR THE GUILTY 5) PUNISHMENT OF THE INNOCENT 6) PROMOTION OF THE NON-PARTICIPANTS. At W3C, the typical stages are more like 1) Naive Optimism 2) Evangelism by the RDF advocates 3) Search for the intersection 4) Compromise on the union 5) Hype that they did the Right Thing 6) Bitter realization that Worse is Better :-)public-web-http-desc is already at Stage 2. [ducking for cover]