Re: [rest-discuss] Media Type & Data Format Best Practice
- Hi Phil,
On Sep 27, 2006, at 1:09 PM, Phil Ruelle wrote:
> Where do you draw the line between
> generic and specific such that your type is not meaningless but nor
> is is it so specific as to limit re-use?
I'd say the 80/20 rule is a good guide: design your media type in a
makes it possible to solve 80% of the envisioned problems at 20% of the
effort and you get a chance that your type attracts interest and gains
enough network effect that it eventually becomes a standard of some
If that happens you gain all the benefits of being able to use what
most likely started in order to serve some specific intra-
in communicating with your clients or partners with standadized means.
Note that meanwhile you might have been cought by network effects of
type yourself causing you to adapt your system and abandon *your*
outcome would be the same - more standardization.
I guess this is where the benefit of true document style integration
is found: the above can happen (and in fact often did) if the
already uniform and we only have to deal with the payloads. I doubt that
a similar (decentralized) process of 'natural selection' (excuse the
Darwinistic touch :-) can ever lead to API standardization as WS-*
proponents seem to think.
> And on a related note what strategies have people employed when
> defining data formats to make them extensible? Judicious use of 'any'
> and 'choice' elements in XSDs lead to a horrible mess (IMHO). Are
> people generally using Relax NG and Schematron to define data
> structures? Of course this assumes that people are using XML ...
> I'd be extremely interested to hear any and all opinions on the