--- In [email protected], "Jim Ley" <[EMAIL PROTECTED]> wrote:
> > The XML RSS feeds are broken all over the place, the HTML world, well just > about anything can render that. > > There's no obvious reason why the rendering needs to be shipped around as > XML. > > Jim. > you are absolutley right, who said SVG was the only rendering system? not me I was talking about why is XML is better for SVG than any other mark- up, particuarly if SVG is to grow into a mature rendering mark-up that is part of a component based semantic web that replaces HTML, eventually, because HTML needs to be more than just a rendering mark- up. It's not a technical issue. If XML is the common markup for this symantic matrix of data, transformations, queries, etc then SVG, as a mature UI rendering system should be too. Having a common semantic across different functions of the document object model, including rendering, is good: everything is parsed for validation once, by one process, before it gets distributed for construction - standardisation like this should result in less 'rejection' - that fact that we are not making anything does not mean rejects don't cost money. It is, in economic terms and within a broad statistical framework, efficient for SVG to be in XML, as the common rendering markup of the semantic web. That was my point, not that its a technical requirement. And it really is an humble opinion: in preparing this answer I have rehersed the case for and I still think it make sense for SVG to be in XML, and it I think it will become as instrisicin in the prevailing economic mode as fordism was/is to manufacturing era. The only reason to adopt an alternative mark-up for SVG is that current one -XML, what everything else is being shipped in - is not adequate because it is not specialised enough - e.g for Math, CAD, Chemistry, etc - or its verbosity is a source of congestion where something more streamlined might be in order. But if you think otherwise I would like to know has your view is highly regarded here. And that so much RSS is broken hardly matters - its mostly terminated anyway. It arrives at the final consumer and if it's broken but consumable who cares? Not the consumer. However if your repackaging data for forward use - like Reuters RSS feeds for example - the source has to work, it can't be broken... having it comply and validate in XML is necessary thing... But thanks for the challenge, it was interesting to think this through Garry ------------------------ Yahoo! Groups Sponsor --------------------~--> Most low income households are not online. Help bridge the digital divide today! http://us.click.yahoo.com/I258zB/QnQLAA/TtwFAA/1U_rlB/TM --------------------------------------------------------------------~-> ----- 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/
