Issues 460, 461 and 462
"Martin Gudgin" <[email protected]>
| Newsgroups | gmane.text.xml.distributed |
|---|---|
| Message-ID | <DD35CC66F54D8248B6E04232892B63380152510B@RED-MSG-43.redmond.corp.microsoft.com> |
I took ( was given? ) an action at the 2004-02-18 telcon to produce a proposal to address issues 460-462 in terms of the current spec. I propose we add the following text to bullet 4 of section 4.1 of XOP. Note: The requirement that all nodes to be optimized have a type of xs:base64Binary does not mean that all such nodes must be optimized. An implementation might choose not to optimize certain nodes despite them having a type of xs:base64Binary. Note: Implementatons are free to assign the xs:base64Binary type to any node in the data model whose lexical form is as described above. For example, a node whose type was a restriction of xs:base64Binary could still be labelled as xs:base64Binary for the purposes of XOP processing. Cheers Gudge