<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/tag/fxg">
<title>Public marks with tag fxg</title>
<description>Public marks with tag fxg</description>
<link>http://blogmarks.net/marks/tag/fxg</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058048400"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058048400">
<title>FXG 1.0 Specification - Flex SDK - Confluence</title>
<link>http://opensource.adobe.com/wiki/display/flexsdk/FXG 1.0 Specification</link>
<description>&lt;blockquote&gt;&lt;p&gt;FXG vs SVG

When initial work on an XML-based graphics interchange format began, the natural first thought was to use SVG. However, there are key differences between SVG and Flash Player's graphics capabilities. These include core differences in SVG and Flash's rendering model with regards to filters, transforms and text. Additionally, the interchange format needed to be able to support future Flash Player features, which would not necessarily map to SVG features. As such, the decision was made to go with a new interchange format, FXG, instead of having a non-standard implementation of SVG. FXG does borrow from SVG whenever possible.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2008-11-04T22:25:38Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>svg, implementation, specification, fxg</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://opensource.adobe.com/wiki/display/flexsdk/FXG 1.0 Specification"><img border="0" src="http://blogmarks.net/screenshots/2008/11/04/602d21b27acf965e1610dbfc2fea70a8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://opensource.adobe.com/wiki/display/flexsdk/FXG 1.0 Specification">FXG 1.0 Specification - Flex SDK - Confluence</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>FXG vs SVG

When initial work on an XML-based graphics interchange format began, the natural first thought was to use SVG. However, there are key differences between SVG and Flash Player's graphics capabilities. These include core differences in SVG and Flash's rendering model with regards to filters, transforms and text. Additionally, the interchange format needed to be able to support future Flash Player features, which would not necessarily map to SVG features. As such, the decision was made to go with a new interchange format, FXG, instead of having a non-standard implementation of SVG. FXG does borrow from SVG whenever possible.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/svg">svg</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/implementation">implementation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/specification">specification</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fxg">fxg</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058048400">Copy</a> | 
<a href="http://blogmarks.net/link/2957904">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>