<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<br><div><html>On Apr 6, 2008, at 2:43 PM, Cyrille Berger wrote:</html><br class="Apple-interchange-newline"><blockquote type="cite"><blockquote type="cite"><p style="margin: 0.0px 0.0px 0.0px 10.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">That model also lacks swatch informations (name, copyright, license,</font></p> <p style="margin: 0.0px 0.0px 0.0px 10.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">...)</font></p> </blockquote><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Yes this is still under consideration. Wether to add some 'simple' home made<span class="Apple-converted-space"> </span></font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">metadata, or use XMP, or use an other RDF schema, or allow anything.</font></p></blockquote><div><br></div><div>So one opinion on this was that there are a few standard ways this information is dealt with now (including Dublin Core, Creative Commons, etc), and thus there is no need to reinvent the wheel for that. Just use metadata like can be used for SVG.</div><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica"><a href="http://www.w3.org/TR/SVG/metadata.html">http://www.w3.org/TR/SVG/metadata.html</a></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div></div><div><br></div><br><blockquote type="cite"> <blockquote type="cite"><p style="margin: 0.0px 0.0px 0.0px 10.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">and swatch-wide settings ("all rgb values are in Adobe1998 color<span class="Apple-converted-space"> </span></font></p> <p style="margin: 0.0px 0.0px 0.0px 10.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">space", "all color names start with 'PANTONE' and end with 'C'", ...).</font></p> </blockquote><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">I am not sure about the use of this ? Since the file is not really intended<span class="Apple-converted-space"> </span></font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">for being written by hand by an human, I can only see compression, but then I<span class="Apple-converted-space"> </span></font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">think bzip2 or zip will do a better job. And I don't like that change, since<span class="Apple-converted-space"> </span></font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">it makes the parsing more complicated.</font></p> </blockquote></div><br><div><br></div><div>Yes, I strongly agree with this point.</div><div><br></div><div>In fact, I've seen things like that in XML being kept verbose actually improve compression.</div><div><br></div><div>Constraints and such like that are easy do to in code. For example, you can just use a regexp for the name check. Better to leave the format clear and easy to use.</div></body></html>