Re: SVG 1.1 : There are some svg elements that are not in acontent set ..Why?

Hi Robert,

On Tue, 13 Aug 2002, Robert Diblasi wrote:

> Hello SVG Working Group,
> 
> I have notice that not all the elements of SVG are in content sets 
> that pretain to there section .....is there any reason for this?

You've been reading the spec very carefully.. well done!
Luckily, this is not an error, it is intentional.

The content sets are used to describe the content models
of other elements.

Some elements are so tightly bound to their parent element
that they don't appear anywhere else. For example, <stop>
is only found within a <radialGradient> or <linearGradient>.
So, there isn't any reason to define a content set for
Stop elements.

Hope this helps,

Dean


> If you read 1.1.3 Profiling the SVG specification:
> http://www.w3.org/TR/SVG11/intro.html#Profiling 
> 
> <snip>
> The Full profile of SVG 1.1 is the collection of all the complete
> modules listed in this specification.
> 
> When applied to conformance, the unqualified term "SVG" implies the
> Full profile of SVG 1.1 defined by this specification. If an
> implementation does not implement the Full profile, it must state either
> the profile to which it conforms, or that it implements a subset of
> SVG.
> </snip>
> 
> Here is a list of Elements that do not belong to any content set:
> 
> GRADIENT MODULE
> stop
> 
> TEXT MODULE
> altGlyphItem
> glyphRef
> 
> FILTER MODULE
> feMergeNode
> feDistantLight
> fePointLight
> feFuncR
> feFuncG
> feFuncB
> feFuncA
> 
> ANIMATION MODULE
> mpath
> 
> FONT MODULE
> font-face
> glyph
> missing-glyph
> hkern
> vkern
> font-face-src
> font-face-uri
> font-face-format
> font-face-name
> defintion-src
> 
> We all learn by sharing what we know
> Robert A. DiBlasi
> http://www.svgnotebook.com

Received on Thursday, 14 November 2002 18:08:21 UTC