« LocWeb 2009 Call for Papers | Main | Breaking Apps »

Thursday, September 18, 2008

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

yliu

Just wanted to say that this would be great for me. Technologies and syntax come relatively easily to me, but the "why"s and best practices have to be picked up either through trial-error / code critiques, or extensive review of an existing codebase (which may or may not be following best-practices). This is especially problematic if the technology is self-learned, without feedback cycles from, say, homework assignments or projects - one ends up developing some idiosyncratic design methodologies, which may or may be not be a good. An XML 'best-practices' book would be exceedingly useful at a practical level.

I think the crucial questions for this book would to be answer "how" and "why". For example, when presented with some typical design problem, how to go about setting down the 'best' schema design (for some value of 'best'), and why this design over some possible alternatives. For example, the Element vs Attribute question seems to be perennial among new XML'ers, and it'd help if there's a frame of reference ( is it only personal taste? or are there some justification for the choice, given a certain context).

Write the book! I'd buy one :)

dret

yliu: thanks for the comment, and thanks for the encouragement. maybe i'll write it and then sell it using a "buy books, make money" model, so that early adopters can get in at a low price and will get a share of the revenue once it is becoming a new york times bestseller. ;-)

William Vambenepe

Would be very valuable. Doesn't mean you'd make good money on it though... :-)

If you go there, make sure to also cover versioning requirements.

The comments to this entry are closed.

Flickr