Lists Home |
Date Index |
> It would be nice to believe that these cases won't happen but if there
> is no specification out there describing how you are supposed to use
> namespace and how not to, then what's wrong with them?
Nothing. That's why I'm using a new media type. Only XML following
the dispatch rules I'm devising can use this it. It's basically an
easy out for people who don't want to define application/foo+bar+baz+xml
types, but it obviously won't work for all integration jobs.
> One of the problems with this is approach is the coordination between
> different elements. Something has to organize these things into a
> coherent whole.... the summarizer case you gave illustrates this
> point. If the XHTML summarizer doesn't understand the SVG summarizer,
> you may not get an accurate summary (for example, perhaps the XHTML
> says "Be nice!" and the SVG says, in big bold letters "Go away".
I don't agree with that example; there's no need for them to agree
on what summarization is. But generally, yes, there needs to be some
coordination. The main objective of my draft is to define rules of
coordination, and I'd really appreciate some input from folks who have
had some experience with these systems.
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA. email@example.com