DR 09-182 WML: Handling of invalid uri values

Shawn Villaron shawnv at microsoft.com
Thu Mar 18 04:42:07 CET 2010


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

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


*         Create a new simple type, ST_Uri, with restriction set to xs:anyURI.

*         The attribute uri (attr @uri (17.5.1.1), attr @uri (17.5.1.2), customXml @uri (17.5.1.3), customXml @uri (17.5.1.4), customXml @uri (17.5.1.5), customXml @uri (17.5.1.6), smartTag @uri(17.5.1.9) , and schema @uri (23.2.1)) will be restricted to ST_Uri instead of ST_String
In summary, this change affects the following elements:


*         attr @uri (17.5.1.1)

*         attr @uri (17.5.1.2)

*         customXml @uri (17.5.1.3)

*         customXml @uri (17.5.1.4)

*         customXml @uri (17.5.1.5)

*         customXml @uri (17.5.1.6)

*         smartTag @uri(17.5.1.9)

*         schema @uri (23.2.1)
New subsection needs to be added to Part 1 Section 22.9.2:

22.9.2.X                ST_Uri (Uniform Resource Identifier Reference)

This simple type specifies that its contents contain a Uniform Resource Identifier Reference (URI).

[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 URI associated with the attribute name whose value is company shall be http://schemas.openxmlformats.org/2006/example. end example]

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20100318/8508ec6f/attachment.htm>


More information about the sc34wg4 mailing list