Don Demsak wrote: > The problem with SVG does not have anything to do with SVG or Adobe, > but with the W3C. SVG and most of the other W3C specs (well other > then the XML ones), were not designed from the beginning to integrate > with each other.
That's simply not true. There are issues, but they integrate better than you characterize. > Microsoft does not suffer from that ailment, since > they are designing their APIs first, and then creating a standard way > to express the APIs thru XML (which is called XAML). Yeah, no offense but I've heard that song sang for every single platform in any domain that's come out in the past ten years at least. Maybe Microsoft got it right somehow, but I'll wait til I see it work for real. It also better be good at integrating with anything not Microsoft, otherwise it'll just be one of those systems that are only as good as their weakest part. It's a hard problem no matter which way you go about it. Doing it by committee in a standards organisation or doing it by committee in a behemoth company isn't likely to make much of a difference. -- Robin Berjon Research Scientist Expway, http://expway.com/ ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
