W3C home > Mailing lists > Public > public-exi@w3.org > January 2017

use of elements for property names in EXI4CSS

From: Takuki Kamiya <tkamiya@us.fujitsu.com>
Date: Tue, 17 Jan 2017 11:51:29 -0800
To: "public-exi@w3.org" <public-exi@w3.org>
Message-ID: <23204FACB677D84EBD57175AB7B5A71C042F8B4BBC6A@FMSAMAIL.fmsa.local>
Hi Daniel and all,

In exi4css.xsd (schema for EXI4CSS [1]), currently enumerated values are used for
propertyType (currently at line 91).

I wonder if we can instead use choice of elements in the following manner.

<xs:element name="style">
    <xs:complexType>
      <xs:sequence minOccurs="0" maxOccurs="unbounded">
        <xs:element name="property">
          <xs:complexType>
            <xs:choice>
              <xs:element name="color">
                <xs:complexType/>
              </xs:element>
              <xs:element name="opacity">
                <xs:complexType/>
              </xs:element>
              ......
              <xs:element name="other">
                <xs:complexType>
                  <xs:sequence>
                    <xsd:any namespace="##targetNamespace" processContents="lax"/>
                  </xs:sequence>
                </xs:complexType>
              </xs:element>

That way, we can inform the pre-defined values but also be able to allow extension
through wildcard.

[1] https://github.com/EXIficient/exificient-for-css/blob/master/src/main/resources/exi4css.xsd

Takuki Kamiya
Fujitsu Laboratories of America
Received on Tuesday, 17 January 2017 19:52:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 17 January 2017 19:52:17 UTC