DR 09-181 WML: Handling of invalid name values

[Shawn Villaron]

Minor edits.  With these changes I believe we can move this to LAST CALL.

From: Shawn Villaron [mailto:shawnv at microsoft.com]
Sent: Thursday, March 18, 2010 4:42 AM
To: 'SC 34 WG4'
Subject: DR 09-181 WML: Handling of invalid name values

This is in regards to the CH defect report.  Our proposed response is as follows.
DR 09-181 WML: Handling of invalid name values
Agreed.

The following changes will be made to both transitional and strict:


*         Create a new simple type, ST_XmlName, with restriction set to xs:NCName

*         The attributes name (attr @name (17.5.1.1) and attr @name (17.5.1.2)) and element (customXml @element (17.5.1.3), customXml @element (17.5.1.4), customXml @element (17.5.1.5), customXml @element (17.5.1.6), and smartTag @element(17.5.1.9)) will be restricted to ST_XmlName instead of ST_String
In summary, this change affects the following elements:


*         attr @name (17.5.1.1)

*         attr @name (17.5.1.2)

*         customXml @element (17.5.1.3)

*         customXml @element (17.5.1.4)

*         customXml @element (17.5.1.5)

*         customXml @element (17.5.1.6)

*         smartTag @element(17.5.1.9)
New subsection needs to be added to Part 1 Section 22.9.2:

22.9.2.X                ST_XmlName (XML Name)

A value of this type shall be an XML non-colonized name (NCName).

[Example: Consider the following WordprocessingML fragment for the properties of a single custom XML element:

<w:customXmlPr>
<w:attr w:name="company"  w:uri="http://schemas.openxmlformats.org/2006/example" ... />
</w:customXmlPr>

The attr element specifies that the NCName associated with the attribute name shall be company. end example]

This simple type's contents are a restriction of the W3C XML Schema NCName datatype.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20100323/b52bf953/attachment-0001.htm>