DR 09-0104: DML: Contradiction between text and dml-wordProcessingDrawing schema

[Shawn Villaron]

Greetings,

In this defect report an implied internal inconsistency within the standard is identified between the prose and the schemas for four attributes defined in CT_Anchor:


·         the schema defines the allowOverlap, behindDoc, layoutInCell and locked attributes of CT_Anchor as required attributes.

·         the prose in section 20.4.2.3, in describing each of these attributes, provides guidance for what a consuming application should do if one of these attributes is missing, hence implying that they are optional, when in fact, they are not.

It is acknowledged that the current prose for these attributes could cause confusion regarding the actual definition of CT_Anchor and it is thereby recommended that we modify the prose to remove any such implied optionality for these attributes.  The following are the proposed changes for this response:

Part 1, §20.4.2.3 will be updated as follows:

Attributes

Description

allowOverlap (Allow Objects to Overlap)

Specifies whether a DrawingML object which intersects another DrawingML object at display time is allowed to overlap the contents of the other DrawingML object. If a DrawingML object cannot overlap other DrawingML object, it shall be repositioned when displayed to prevent this overlap as needed.

If this element is omitted on a given DrawingML object, then overlap shall not be allowed between a DrawingML object which intersects another DrawingML object displayed at the same location.

[Example: Consider a document with two DrawingML objects which are allowed to overlap each other. This would be specified as follows within each object's anchor markup:


<wp:anchor allowOverlap="true" ... >

  ...

</wp:anchor>

The allowOverlap attribute has a value of true, which specifies that this object must be allowed to overlap other objects when it is displayed on the document. end example]

The possible values for this attribute are defined by the W3C XML Schema boolean datatype.

behindDoc (Display Behind Document Text)

Specifies whether this floating DrawingML object is displayed behind the text of the document when the document is displayed. When a DrawingML object is displayed within a WordprocessingML document, that object can intersect with text in the document. This attribute shall determine whether the text or the object is  rendered on top in case of overlapping.

If this attribute is omitted, then the parent DrawingML object shall be displayed in front of the text content of the document in cases of overlapping..

[Example: Consider a floating DrawingML object which must be displayed above any text which it intersects within the document's content. This setting would be specified as follows:


<wp:anchor behindDoc="false" ... >
  ...
</wp:anchor>

The behindDoc attribute has a value of false, which specifies that the DrawingML object is displayed above the text of the document in z-order. end example]

The possible values for this attribute are defined by the W3C XML Schema boolean datatype.

layoutInCell (Layout In Table Cell)

Specifies how this DrawingML object behaves when its anchor is located in a table cell; and its specified position would cause it to intersect with a table cell displayed in the document. That behavior shall be as follows:

·         When this attribute has a value of true, then the object shall be positioned within the existing table cell, causing the cell to be resized as needed. This means that all positioning shall be relative to the cell and not the line on which the table appears.

·         When this attribute has a value of false, then the object shall be positioned as specified, but the table shall be resized and/or relocated within the document as needed to accommodate the object. This means that all positioning shall be relative to the line on which the table appears and not the cell in which the anchor is present.

If this attribute is omitted, then its default value shall be considered to be false.

[Example: Consider a DrawingML picture which must be displayed in the center of the document. If the object is contained within a table and is defined as follows:


<wp:anchor layoutInCell="true" ... >
  ...
</wp:anchor>

The layoutInCell attribute has a value of true, which specifies that the object can be placed within the cell if needed, for example:

[cid:image001.png at 01C9E801.3AC3C690]

If the layoutInCell attribute was now set to false, the object must be laid out outside of the cell, causing the table to be repositioned:

[cid:image002.png at 01C9E801.3AC3C690]
end example]

The possible values for this attribute are defined by the W3C XML Schema boolean datatype.

locked (Lock Anchor)

Specifies that the anchor location for this object shall not be modified at runtime when an application edits the contents of this document. [Guidance: An application might have automatic behaviors which reposition the anchor for a DrawingML object based on user interaction - for example, moving it from one page to another as needed. This element must tell applications not to perform any such behaviors. end guidance]

If this attribute is omitted, then the anchor shall not be locked for the parent DrawingML object (i.e. a default value of false).

[Example: Consider a floating DrawingML object which must have its anchor locked at the current location. This setting would be specified as follows:


<wp:anchor locked="true" ... >
  ...
</wp:anchor>

The locked attribute has a value of true, which specifies that the DrawingML object's current anchor location must not be changed by applications editing this content. end example]

The possible values for this attribute are defined by the W3C XML Schema boolean datatype.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090608/7aad7818/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 10057 bytes
Desc: image001.png
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090608/7aad7818/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 7327 bytes
Desc: image002.png
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090608/7aad7818/attachment-0001.png>