User talk:Pdengler

From SVG

Introduction to SVG 2.0 Planning

Here is the content we discussed at the Face-to-Face that we will to drive SVG 2.0 We will use goals and scenarios to set the stage. Any and all feedback is welcome. Patrick Dengler

Goals for SVG 2.0

Focus on Vector Graphic Primitives

  • SVG is primarily a part of the web platform
  • SVG is the missing vector graphics markup for HTML
  • Shared styling, animation, etc should be a single model that is implementable

Better Integration with CSS

  • Determine which attributes should have corresponding CSS properties (e.g. x,y)
  • Modularize features that CSS can support through joint development of specs for (some of which may be optional)
  • Transforms
  • Gradients
  • Compositing
  • Filters
  • Animations/Transitions (SMIL?)
  • WOFF

Improve upon core concepts/features of SVG

  • Nesting Structure <g>, <defs>
  • Architecture <use>
  • Geometry
  • Coordinate System Layout (and constraints)


  • Different usage models
  • Mixing SVG and HTML
  • Aligning elements, attributes, properties
  • Deemphasize SVG core architectural features that overlap with HTML
    • Audio/Video
    • Text Flow

Other SVG 2.0 Goals

  • Architect the Spec better
    • Events
    • Timing
  • Organization
    • Clean up the DOM
    • Clean up Primitives
  • Maintain Backwards Compat for existing content
  • Extend SVG
    • Vector Effects
    • Shape Path
    • Constraints based layout
    • Relative positioning
    • (2d Flow (w/ HTML5?)
  • Better focus on interoperability between implementations
    • Tests, Suites, Automation
  • Test Driven Development of Specs
  • Use cases in the spec
  • More samples in the spec
  • All browser vendors pass


Key Scenario #1

Standalone “documents” for viewing/publishing on the Internet (mostly supported)

  • High fidelity graphics that scale
  • High fidelity printing
  • Public interchange format that is now becoming required for government entities


  • CAD Floor Maps
  • Aircraft Engineering Diagrams, Floorplans
  • Lighter weight Diagrams (Visio, PowerPoint)

Supporting Features

  • Non scaling strokes
  • Level of Detail (LOD) for progressively complex diagrams

Key Scenario #2

A Developer wishes to create a richer, more graphic intensive webapps where HTML does not suite the needs well to creating the graphic experience, using a common programming model or framework which increases the productivity of the developer, user experience and satisfaction improve, and is interoperable.

  • Scriptable webapps, whether integrated with HTML or standalone

Key Scenario #3

A web site hosts interactive vector graphic diagrams mixed with HTML such as org charts, calendars, graphs and maps. This includes dynamic and interactive display of information of educational material, data visualization and documentation.

Required Features

  • Connectors
  • Parameters
  • Superpath

Feature that cross Scenarios

  • Z-index
  • Improve the DOM
  • A shared API with <canvas>
  • Accessibility

Other Scenarios to Consider

  • A developer wishes to use SVG as an image interleaved throughout web pages where scalability or image size (where possible) can improve

Provide complete UI experiences for

    • Standalone apps and to control audio/video etc
    • Educational material
    • TV station
    • Long running animation
  • Text Effects
    • basic animation on text and glyphs (like the a glyph on fire)
    • advanced text effects (change fonts dynamically)
    • Text on a map preserved with orientation
  • Games like on OneMoreLevel
    • Seriously consider a math engine and/or physics engine
    • Pseudo 3D

More Questions to Ask

What does SVG mean to the web developer? Developers don't often

  • Don’t use tooling
  • Will use libraries (jquery)
  • Don’t require (like?) XML

What aren’t SVG Features?

  • Filters
  • Transforms
  • Gradients