index.html 14.9 KB

Raw Blame History Permalink

<!--
  SVG Color 1.2, Part 1: Primer

  $Id: Overview.html,v 1.8 2009/10/01 05:20:33 clilley Exp $

  Note: This document is generated from ../master/SVGColorPrimer.html.
  Run "make" from ../master/ to regenerate it.
  -->

<!DOCTYPE html
  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/><title>SVG Color 1.2, Part 1: Primer</title><link rel="stylesheet" type="text/css" href="style/svg-style.css"/><link rel="stylesheet" type="text/css" href="style/svg-style-extra.css"/><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD"/></head><body>
  <div class="head">
    <p><a href="http://www.w3.org/"><img height="48" width="72" src="http://www.w3.org/Icons/w3c_home" alt="W3C"/></a></p>
    <h1 id="pagetitle">SVG Color 1.2, Part 1: Primer</h1>
    <h2 id="pagesubtitle">W3C Working Draft 01 October 2009</h2>
    <dl>
    <dt>This version:</dt>
    <dd><a href="http://www.w3.org/TR/2009/WD-SVGColorPrimer12-20091001/">http://www.w3.org/TR/2009/WD-SVGColorPrimer12-20091001/</a></dd>
    <dt>Latest version:</dt>
    <dd><a href="http://www.w3.org/TR/SVGColorPrimer12/">http://www.w3.org/TR/SVGColorPrimer12/</a></dd>
    <dt>Editors:</dt>
    <dd>Chris Lilley, W3C &lt;<a href="mailto:chris@w3.org">chris@w3.org</a>&gt;</dd>
    <dd>Anthony Grasso, Canon Information Systems Research Australia, &lt;<a href="mailto:anthony.grasso@research.canon.com.au">anthony.grasso@research.canon.com.au</a>&gt;</dd>

    <dt>Authors:</dt>
    <dd>The authors of this specification are the participants of the W3C SVG Working Group.</dd>
    </dl>
    <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>  &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup>  (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>  and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
  </div>
  <hr title="Separator from Header"/>
  <h2 id="abstract">
    Abstract
  </h2>
  <p>
    This Working Draft is a primer for use of the Scalable Vector Graphics (SVG) Language
    for color managed workflows. It explains the technical background and gives guidelines
    on how to use the SVG Color specification with SVG 1.2 Tiny and SVG 1.2 Full modules.
    It is purely informative and has no conformance statements.
  </p>
  <h2 id="status">
    Status of This Document</h2>
  <p>
    <em>This section describes the status of this document at the time of its publication.
      Other documents may supersede this document. A list of current W3C publications
      and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">
        W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
  <p>
    This document is  a First Public Working Draft. It defines features of SVG specific to color management.
    It is a draft in progress; some descriptions in this document may be incomplete.
    This document shows the current thoughts of the SVG Working Group on the use of
    SVG for printing and should not yet be considered stable. There is an accompanying
    <a href="#SVG12Color">SVG Color 1.2, Part 2: Language</a> that lists the ways
    SVG Color may be used.
  </p>
  <p>
    This document has been produced by the <a href="http://www.w3.org/Graphics/SVG/WG">W3C
      SVG Working Group</a> as part of the W3C <a href="http://www.w3.org/Graphics/Activity">
        Graphics Activity</a> within the <a href="http://www.w3.org/Interaction/">Interaction
          Domain</a>. The Working Group expects to advance this Working Draft to Recommendation
    Status.
  </p>
  <p>
    We explicitly invite comments on this specification. Please send them to <a href="mailto:www-svg@w3.org">
      www-svg@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/www-svg/">archives</a>).
    Acceptance of the archiving policy is requested automatically upon first post to
    either list. To subscribe to this list send an email to
    <a href="mailto:www-svg-request@w3.org">www-svg-request@w3.org</a>
    with the word subscribe in the subject line.
  </p>
  <p>
    Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">
      W3C</acronym> Membership. This is a draft document and may be updated, replaced
    or obsoleted by other documents at any time. It is inappropriate to cite this document
    as other than work in progress.
  </p>
  <p>  This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. This document is informative only. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/19480/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>. </p>

  <hr/>
  <h2 id="howto">
    How to read this document and give feedback
  </h2>
  <p>
    The main purpose of this document is to encourage public feedback. The best way
    to give feedback is by sending an email to <a href="mailto:public-svg-print@w3.org">
      public-svg-print@w3.org</a>. Please identify in the subject line of your message
    the part of the specificationto which your comment refers (e.g "Print compositing"
    or "Print render formats"). If you have comments on multiple areas of this document,
    then it is preferable to send several separate comments.
  </p>
  <p>
    The public are welcome to comment on any aspect in this document, but there are
    a few areas in which the SVG Working Group are explicitly requesting feedback. These
    areas are noted in place within this document <span class="note">like this.</span>
  </p>

  <h2 id="toc">Table of Contents</h2>
  <ul class="toc">
<li><a href="#intro">1
    Introduction</a></li>
<li><a href="#colorspec">2
    Color specification
  </a><ul class="toc">
<li><a href="#sRGBcolor">2.1
    sRGB colors</a></li>
<li><a href="#iccoutput">2.2
    ICC colors</a></li>
<li><a href="#named">2.3
    Named color</a><ul class="toc">
<li><a href="#iccnamed">2.3.1
    Use of the ICC named color syntax
  </a></li>
<li><a href="#iccnamedmanage">2.3.2
    ICC named color profile management
  </a></li>
</ul></li>
<li><a href="#devcolor">2.4
    CIE LAB color specification
  </a></li>
<li><a href="#devcolor">2.5
    Device color specification
  </a></li></ul></li>
<li><a href="#references">3
    References
  </a><ul class="toc">
<li><a href="#informref">3.1 Informative References</a></li></ul></li></ul>
  <h2 id="intro">1
    Introduction</h2>
  <p>
    Because of its scalable, geometric nature, SVG is inherently  suited to both print
    and screen output. The same colors can be output, using an ICC-based color managed
    workflow on the printer and an sRGB fallback approximation on screen. This has been
    true since SVG 1.0, and so SVG has been used in print workflows (for example, in
    combination with XSL FO) as well as on screen.
  </p>
  <p>
    It is common in cross-media publishing to design content which will be used both
    online and in print media. This specification gives guidance on how to create such
    content and how to indicate that it has been adapted to improve its color capability.</p>


  <h2 id="colorspec">2
    Color specification
  </h2>
  <p>
    SVG Color allows color to be specified in a number of ways. All of the sRGB color
    syntaxes from SVG Print 1.2 are supported. The ICC-based color syntax from SVG 1.1
    Full is also supported, and unlike SVG 1.1 rendering this feature is not optional. New to the SVG Color specification, <a href="#named">ICC named
      colors</a> and <a href="#devcolor">device colors</a> are supported as well: their
    syntax is defined below.</p>
  <h3 id="sRGBcolor">2.1
    sRGB colors</h3>
  <p>
    As with SVG Tiny 1.2, colors may be specified in the sRGB colorspace without providing
    a color profile. This color space, which uuses the chromaticities of a standard
    TV broadcast monitor and viewing conditions typical of an office environment, has
    a reduced gamut suitable for minimising banding on 'real world' colors at the expense
    of being unable to directly represent highly saturated colors. A number of equivalent
    syntactic forms are supported, as <a href="http://www.w3.org/TR/SVGMobile12/painting.html#colorSyntax">
      defined in SVG Tiny 1.2</a>:</p>
  <pre class="example">
  &lt;circle cx="200" cy="135" r="20" fill="#3b3"/&gt;
  &lt;circle cx="240" cy="135" r="20" fill="#33bb33"/&gt;
  &lt;circle cx="200" cy="175" r="20" fill="rgb(51,187,51)"/&gt;
  &lt;circle cx="240" cy="175" r="20" fill="rgb(20%,73.333%,20%)"/&gt;
</pre>
  <h3 id="iccoutput">2.2
    ICC colors</h3>
  <p>
    Since SVG 1.0, SVG has contained functionality for use of ICC color profiles which
    define colors in a different color space than sRGB. This functionality has been
    available since SVG 1.0 but for the most part has not been well understood. SVP
    Print tightens the conformance criteria for using ICC colors.
  </p>
  <p>
    For example, it is possible to specify all objects in terms of an ICC color space
    such as SWOP CMYK and the SVG renderer perform all rendering of the objects entirely
    in the SWOP CMYK space followed by color correction for a printer target CMYK. This
    render workflow would never require conversion into and out of sRGB.
  </p>
  <p>
    In the case where opacity is used and objects overlap a render device must use the
    supplied sRGB fallback color in order to composite objects together.
  </p>
  <p>
    The implication of this is that it is possible to use a fully colormanaged workflow (using
    SVG 1.0 onwards) that supports a full CMYK pipeline via the use of ICC profiles.
    Such an SVG render device must also be capable of handling a switch into the fallback
    render color space (sRGB) for the overlapping portions of objects with transparency.
  </p>
  <p>
    An implementation may determine the areas of an object to render in object's ICC
    color and those areas to render in its sRGB fallback by doing object intersection
    calculations as a pre-render step. An implementation could alternatviely decide
    render color choice on a pixel by pixel basis during rasterisation. Such behaviour
    is implementation specific and can lead to varying rendering results from different
    implementations at the borders of overlapping areas when using ICC colors.
  </p>
  <h3 id="named">2.3
    Named color</h3>
  <p>
    SVG Color introduces the ability to use so-called 'named' or 'spot' colors. Named
    colors are used in many print applications and are supported in SVG Print through
    the use of ICC named color profiles. For color managed displays, the desired color may be accurately simulated. Non color managed user agents will use the sRGB fallback value.
  </p>
  <h4 id="iccnamed">2.3.1
    Use of the ICC named color syntax
  </h4>
  <p>
    The paint specifiers for fill and stroke include the <span class="property">icc-named-color</span>
    keyword. This may be used to look up colors by their name. For example in graphic
    arts workflows it is common to use Pantone®

    color names for specifying paint on objects. The <span class="property">icc-named-color</span>
    keyword may be used for such workflows.
  </p>
  <h4 id="iccnamedmanage">2.3.2
    ICC named color profile management
  </h4>
  <p>
    An SVG 1.2 file may specify ICC named color profiles via use of the <span class="element">
      color-profile</span> element.
  </p>
  <p>
    The ICC specification indicates that named color profiles must contain a PCS (Profile
    Connection Space) representation and can optionally contain a device representation
    for each named color. An implementation may support device representations of ICC
    named colors, however that support is device specific and should be managed outside
    of the SVG file itself by use of some form of job ticket information.
  </p>


  <h3 id="labcolor">2.4
    CIE LAB color specification
  </h3>
  <p>SVG Color allows any visible color to be directly specified in the standard,
    device-independent CIE L*ab color space. Both the cartestian (L*ab)
    and polar (L*CHab) forms are supported. The latter has the advantage that
    chroma and hue are more intuitive to specify than the abstract a and b axes.</p>

  <h3 id="devcolor">2.4
    Device color specification
  </h3>
  <p>
    Occasionally, it is necessary to specify non-colormanaged colors in terms of the
    eventual device colorants. An example  would be the creation of registration marks,
    or  tint bars of pure ink for quality control purposes.
  </p>


  <h2 id="references">3
    References
  </h2>
  <h3 id="informref">3.1 Informative References</h3>
  <dl><dt id="CRC">CRC</dt><dd>C.S. McCamy, H. Marcus, J.G. Davidson, “A Color-Rendition Chart,” <i>J. Appl. Phot. Eng.</i>, Vol. <b>2</b>, No. 3, Summer 1976, pp. 95-99, Society of Photographic Scientists and Engineers (now called “The Society for Imaging Science and Technology (IS&amp;T)”) </dd><dt id="SVG12Full">SVG12</dt><dd>
      <strong>Scalable Vector Graphics (SVG) 1.2 Specification</strong>, Dean Jackson
      editor, W3C, 27 October 2004 (Working Draft). See <a href="http://www.w3.org/TR/2004/WD-SVG12-20041027/">
        http://www.w3.org/TR/2004/WD-SVG12-20041027/</a>
    </dd><dt id="SVG12Requirements">SVG12Reqs</dt><dd>
      <strong>SVG 1.1/1.2/2.0 Requirements</strong>, Dean Jackson editor, W3C, 22 April
      2002 (Working Draft). See <a href="http://www.w3.org/TR/2002/WD-SVG2Reqs-20020422/">
        http://www.w3.org/TR/2002/WD-SVG2Reqs-20020422/</a>
    </dd>
    <dt id="SVG12Color"><strong class="informref">[SVGColor]</strong></dt>
    <dd><cite><a href="http://www.w3.org/TR/SVGColorPrimer12">SVG Color </a></cite>,
      Chris Lilley, Anthony Grasso, eds. World Wide Web
      Consortium, 01 October 2009. <br />
      Latest version available at: <a href="http://www.w3.org/TR/SVGColor12">http://www.w3.org/TR/SVGColor12</a></dd>
  </dl>
<script src="style/expanders.js" type="text/javascript"> </script></body></html>