DR 15-0020

[MURATA Makoto]

Dear colleagues,

The original DR provides six elements in which VML can occur.

1) background in WML

Here is a schema fragment for the background element.  Note that two
namespaces are explicitly allowed and no other namespaces are allowed.

  <xsd:complexType name="CT_Background">
    <xsd:sequence>
      <xsd:sequence maxOccurs="unbounded">
        <xsd:any processContents="lax"
namespace="urn:schemas-microsoft-com:vml" minOccurs="0"
          maxOccurs="unbounded"/>
        <xsd:any processContents="lax"
namespace="urn:schemas-microsoft-com:office:office"
          minOccurs="0" maxOccurs="unbounded"/>
      </xsd:sequence>
     ...
  </xsd:complexType>

Thus, I propose to introduce a subclause between 14.1 and 14.2.

  14.2 Main Document Story
  14.2.1 VML in background element

  VML objects are allowed to occur within a background element.  The
  definition and semantics of this object is described in the VML
  subclause (§19.1) and the VML - Office Drawing subclause (§19.2) of
  ISO/IEC 29500.


2) object in WML

Here is a schema fragment for object.  Again, two namespaces are
explicitly allowed and no other namespaces are allowed.

  <xsd:complexType name="CT_Object">
    <xsd:sequence>
      <xsd:sequence maxOccurs="unbounded">
        <xsd:any processContents="lax"
namespace="urn:schemas-microsoft-com:vml" minOccurs="0"
          maxOccurs="unbounded"/>
        <xsd:any processContents="lax"
namespace="urn:schemas-microsoft-com:office:office"
          minOccurs="0" maxOccurs="unbounded"/>
      </xsd:sequence>
...
  </xsd:complexType>

Thus, I propose to introduce a subclause between 14.3.2.1.

  14.3.2.1 VML in object element

  VML objects are allowed to occur within an object element.  The
  definition and semantics of this object is described in the VML
  subclause (§19.1) and the VML - Office Drawing subclause (§19.2) of
  ISO/IEC 29500.

3) pict in WML

At present, the proose is

“...The definition and semantics of this object is described in the
VML subclause (§19.1) and the VML - Office Drawing subclause (§19.2)
of ISO/IEC 29500”.

But the schema allows both namespaces.  Is this a mistake of the schema
or prose?

  <xsd:complexType name="CT_Picture">
    <xsd:sequence>
      <xsd:sequence maxOccurs="unbounded">
        <xsd:any processContents="lax"
namespace="urn:schemas-microsoft-com:vml" minOccurs="0"
          maxOccurs="unbounded"/>
        <xsd:any processContents="lax"
namespace="urn:schemas-microsoft-com:office:office"
          minOccurs="0" maxOccurs="unbounded"/>
      </xsd:sequence>
      <xsd:element name="movie" type="CT_Rel" minOccurs="0"/>
      <xsd:element name="control" type="CT_Control" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>


4) hdrShapeDefaults or shapeDefaults in WML

Here is the schema fragrment for these elements.  Note that only one
namespace is
allowed.

  <xsd:complexType name="CT_ShapeDefaults">
    <xsd:choice maxOccurs="unbounded">
      <xsd:any processContents="lax"
namespace="urn:schemas-microsoft-com:office:office"
        minOccurs="0" maxOccurs="unbounded"/>
    </xsd:choice>
  </xsd:complexType>

Here is prose common to both clauses for these elements.   It is
consistent with the schema

  The definition and semantics of these parameters is described in the
  VML - Office Drawing subclause (§19.2) of ISO/IEC 29500.

I see no problems here.


Regards,

Makoto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20160923/14144e19/attachment-0001.html>