Slashdot Mirror

← Back to Stories (view on slashdot.org)

SVG 1.1 Becomes W3C Proposed Recomendation

Posted by michael on from the step-2-XML-step-3-profit dept.

openbear writes "From the w3c web site... W3C is pleased to announce the advancement of Scalable Vector Graphics (SVG) 1.1 and Mobile SVG to Proposed Recommendations. Comments are welcome through 20 December. SVG delivers vector graphics, text, and images to the Web in XML. SVG 1.1 separates the SVG language into reusable building blocks. Mobile SVG re-combines them into two profiles optimized for cellphones and pocket computers."

7 of 168 comments (clear)

  1. A what now? by ejdmoo · · Score: 5, Funny

    A proposed recommendation for possibility of consideration of partial inclusion...

  2. See also XForms by leighklotz · · Score: 5, Informative

    See also W3C XForms, which has just become a Candidate Recommendation (one step before PR). XForms updates HTML forms to be XML-based, and plays well with other standards, adding forms to SVG and other XML applications. There are already about a dozen XForms implementations, ranging from those for hand-held devices to standalone clients and popular browser plug-ins. (And a Bugzilla entry for Mozilla that is entertaining reading, though a link from Slashdot won't work anyway.)

    Disclaimer: I am one of the editors of the XForms spec.

  3. Linux implementations by raju · · Score: 5, Interesting

    The first place I would expect SVG to appear in is the browser. In Mozilla the beta SVG provided by Adobe does not work. Mozilla's own implementation[mozilla.org] is stuck due to licensing issues (LGPL vs MPL). When can we expect a decent one on our beloved platform? Windows users at least a decent one from Adobe.

  4. SVG vs. Flash by Cheese+Cracker · · Score: 5, Insightful

    Here's a great page that compares SVG vs. Flash.

    Here's two good reasons why you want to implement SVG instead of Flash:

    SVG is a standard, Flash is proprietary.
    SVG can be indexed and searched, Flash can't.

    1. Re:SVG vs. Flash by Khalid · · Score: 5, Informative

      > Here's one good reason why you'd want to implement Flash instead of SVG: SVG is Slooow.

      I am not sure what this really means. This is like saying XML is slow, or better HTML is slow. SVG is a standard, you will have slow, and quick implementations, maybe current implementation have not been really optimised yet, but there is no real reason SVG might be intrinscly slow

  5. No, SVG is real now by wombatmobile · · Score: 5, Informative
    The 1.0 spec has been out for yonks already and there's an active SVG developer community out there.

    Adobe has been distributing SVG viewer as part of the Acrobat 5 download for over a year now.

    Nobody's waiting for Microsoft to innovate SVG or do their XDocs whatever thing; check these static examples generated from MS apps with SVGmaker: Excel, PowerPoint, Word, Project

    For building SVG web applications its true that there aren't comprehensive IDE tools available yet, but that hasn't stopped developers from creating some definitive web apps with simple home grown tools (starting with a text editor since SVG is just XML).

    Like this interactive logical diagram

    Check this awesome mapping example

    And this wonderful airport flight management app.

  6. Like PDF but its XML by wombatmobile · · Score: 5, Informative
    SVG is an image format that can faithfully reproduce a document display context, same like PDF but since SVG is XML you can mark it up by hand in a text editor, script it, transform it, integrate it directly with HTML or whatever you like. And no monopoly controls it.

    This is a shameless plug but we are only 5 guys working out of a house, not a monopoly... (yet... ho ho ho). In the same way that Acrobat can generate PDF out of anything, SVGmaker can generate SVG out of Windows apps.

    These are examples.