W3C home > Mailing lists > Public > www-svg@w3.org > January 2002

Schema for SVG - suggestions

From: Jiri Jirat <Jiri.Jirat@systinet.com>
Date: Fri, 11 Jan 2002 15:01:42 +0100
Message-ID: <3C3EF046.1020600@systinet.com>
To: www-svg@w3.org
Hello,
  I think that SVG WG has chosen very pragmatical
approach when specifying
datatypes (I have heard about the 10kb regexp :-)),
that's a wise decision, thanks!


However, I think that more detailed specification
would be useful in some cases. I think, it would
require only small changes, using the "union" or "list" elements.


1)
As an example, the first defined simpleType ("BaselineShiftValueType").
change:
---------
   <simpleType name="BaselineShiftValueType">
     <annotation>
       <documentation>The actual definition is
			baseline | sub | super | &lt;percentage&gt; | &lt;length&gt; | inherit
			not sure that union can do this
			</documentation>
     </annotation>
     <restriction base="string"/>
   </simpleType>
---------

to:
---------
   <simpleType name="BaselineShiftValueType">
     <annotation>
       <documentation>The actual definition is
			baseline | sub | super | &lt;percentage&gt; | &lt;length&gt; | inherit
			not sure that union can do this
			</documentation>
     </annotation>
<!-- begin -->
     <union>
      <simpleType>
       <restriction base="string">
        <enumeration value="baseline"/>
        <enumeration value="sub"/>
        <enumeration value="super"/>
        <enumeration value="inherit"/>
       </restriction>
      </simpleType>
      <simpleType>
<!-- this should be enough, because percentage is already
in LengthType -->
       <restriction base="svg:LengthType"/>
      </simpleType>
     </union>
<!-- end -->

   </simpleType>
---------

The above suggestion can be applied to the following
types too, using "union":
ClipValueType
ClipPathValueType
CursorValueType
EnableBackgroundValueType
FilterValueType
FontSizeValueType
FontSizeAdjustValueType
GlyphOrientationHorizontalValueType
GlyphOrientationVerticalValueType
KerningValue
MarkerValueType
MaskValueType
etc.

Do you intend to refine the definitions?



2)
Other namespaces:
Current Schema does not allow to use other namespaces
in "metadata" element (such as RDF, Dublin Core or whatever
else).
I would suggest to change:

   <complexType name="metadataType" mixed="true">
    <sequence minOccurs="0" maxOccurs="unbounded"/>
    <attributeGroup ref="svg:stdAttrs"/>
   </complexType>

to, for example:

   <complexType name="metadataType" mixed="true">
    <sequence minOccurs="0" maxOccurs="unbounded">
     <any namespace="##other"/>
    </sequence>
    <attributeGroup ref="svg:stdAttrs"/>
   </complexType>



What are your opinions?


Regards
Jirka Jirat


-- 
  <name firstName="Jirka" surname="Jirat"/>
  <mail>     jiratj@systinet.com  </mail>
  <support>  http://www.zvon.org </support>
  <zvonMailingList> http://www.zvon.org/index.php?nav_id=4 
</zvonMailingList>
Received on Friday, 11 January 2002 09:01:21 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:21 GMT