[prev in list] [next in list] [prev in thread] [next in thread] 

List:       batik-dev
Subject:    Re: Implicit default namespace for SVG documents
From:       Chris Lilley <chris () w3 ! org>
Date:       2005-09-30 4:49:45
Message-ID: 976039398.20050930064945 () w3 ! org
[Download RAW message or body]

On Friday, September 30, 2005, 3:00:52 AM, Cameron wrote:

CM> Chris Lilley:
>> As I understand it this would be a change for the current codebase - who
>> is adding this?

CM> One final thing I'd like to raise before committing the change is the
CM> text in section G.2, which states:

CM>   An SVG document fragment is a Conforming SVG Document Fragment if it
CM>   adheres to the specification described in this document (Scalable
CM>   Vector Graphics (SVG) Specification) including SVG's DTD (see Document
CM>   Type Definition) and also:

CM>     * (relative to XML) is well-formed.
CM>     * if all non-SVG namespace elements and attributes and all xmlns
CM>       attributes which refer to non-SVG namespaces other than the XLink
CM>       namespace are removed from the given document, and if an
CM>       appropriate XML declaration (i.e., <?xml...?>) is included at the
CM>       top of the document, and if an appropriate document type
CM>       declaration (i.e., <!DOCTYPE svg ... >) which points to the SVG
CM>       DTD is included immediately thereafter, the result is a valid XML
CM>       document.
CM>     * [...]

CM> and that a conforming standalone SVG document also is a conforming SVG
CM> document fragment.

CM> What does "adhering" to the DTD mean?  Does it mean that the DTD should
CM> be applied to the document?  Or that the document should be valid if the
CM> DTD were applied to it, but it should not actually be applied unless it
CM> is explicitly referenced in the document?

The latter.

CM>   Because it if is the former,
CM> the text in 5.1.1 that says "an SVG namespace declaration must be
CM> provided so that all SVG elements are identified as belonging to the SVG
CM> namespace" would be satisfied even without the namespace declarations
CM> appearing in the actual text of the document (especially since the
CM> paragraphs below that say that "The following are possible ways to
CM> provide a namespace declaration", implying that other methods could be
CM> possible, too).





-- 
 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG


---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]