SVG RNGs

Hi

1. SVG 1.1 RNG
http://www.w3.org/Graphics/SVG/1.1/rng/

In
http://www.w3.org/TR/SVG11/metadata.html#MetadataElement
there is
"The contents of the 'metadata' should be elements from other XML
namespaces"
but
http://www.w3.org/Graphics/SVG/1.1/rng/svg-basic-structure.rng
has
  <define name="SVG.metadata.content">
    <text/>
  </define>

This means that the example provided in 21.3

  <metadata>
    <rdf:RDF [...]

and all other SVGs of this type are invalid in respect to the above
RNG, if I'm not missing something.

Is the 1.1 RNG currently being actively developed?

I didn't yet get any replies to
http://lists.w3.org/Archives/Public/www-svg/2003Sep/thread.html#21
http://lists.w3.org/Archives/Public/www-svg/2003Sep/0021.html
and
http://lists.w3.org/Archives/Public/www-svg/2003Jul/thread.html#74
http://lists.w3.org/Archives/Public/www-svg/2003Jul/0074.html
http://lists.w3.org/Archives/Public/www-svg/2003Jul/0090.html
(there is a zip now, thanks, but if you must include a doctype decl
then a real system identifier (plus optional FPI) would be more useful
for OASIS XML Catalog tools than a relative local path)

http://www.w3.org/TR/SVG12/#rng-schema
says
"This schema should not be considered to be complete or without error.
Even though it is a schema for SVG 1.1, it is still in development and
has not been thoroughly tested."
Perhaps you could publish the latest versions periodically and
announce them here?

2. Versions, Profiles

It would be very useful to have a complete and correct RNG for each
version and profile (not just the planned (normative?) ones for 1.2+):
1.1, 1.1 Basic, and 1.1 Tiny (all three would probably simply be short
drivers referencing a different set of modules).

As Chris wrote in
http://lists.w3.org/Archives/Public/www-svg/2003May/0058.html
"Having an official SVG 1.1 RNG schema would certainly help in
consistency of reference."

3. Normative

No matter if the main schema is maintained in RNG or in some other
schema lang (eg a custom superset), it woud be great to have normative
RNGs (at least for 1.2+), for various reasons such as those decribed
in
http://lists.w3.org/Archives/Public/www-svg/2003Jun/0111.html
and
http://lists.w3.org/Archives/Public/www-svg/2003Apr/0089.html
etc etc

When I get an error message it's tedious to find out if the error is
in the SVG, the RNG, or in the validator. If the RNG would be
complete, correct, and ideally normative, the task would be greatly
simplified: a bug report could be quickly submitted to the validator's
project if the SVG is valid.

4. Instances which don't reference a schema

If a document doesn't reference a schema (eg a DTD) the path to a
schema (eg an RNG) must be provided when validating, which is tedious
to do by hand. I've been pondering this issue for the last months, and
over the last weeks (on and off) I threw together a tiny prototype
which works well so far (parts of the issue remain though, and can't
be fixed locally). If someone's interested in the tool drop me a line
offlist. Here's what the catalog looks like:

<catalog xmlns="http://www.pinkjuice.com/catalog/" version="0.1">

  <language>
    <xpath>
namespace-uri(/*)='http://www.w3.org/2000/svg'
and (
/*/@version='1.0'
or /*/@version='1.1'
or not(/*/@version)
)
and
not(/*/@baseProfile)
    </xpath>
    <local-schema>
/home/tobi/bulk/xml/schemas/svg/1_1/rng/svg11.rng
    </local-schema>
  </language>

  <language>
    <xpath>
local-name(/*)='svg'
and
/*/@version='1.1'
and
/*/@baseProfile='tiny'
and
namespace-uri(/*)='http://www.w3.org/2000/svg'
    </xpath>
    <local-schema>
/home/tobi/bulk/xml/schemas/svg/1_1/tiny/dtd/svg11-tiny-flat.dtd
    </local-schema>
  </language>

[...]

Tobi

-- 
http://www.pinkjuice.com/

Received on Saturday, 6 December 2003 05:40:32 UTC