Evaluation of XML Schema Part 2 PER base64Binary type
"Martin Gudgin" <[email protected]>
| Newsgroups | gmane.text.xml.distributed |
|---|---|
| Message-ID | <DD35CC66F54D8248B6E04232892B6338019CC75D@RED-MSG-43.redmond.corp.microsoft.com> |
Dear XMLPers, I took an action on last weeks call to take a look at the proposed edited recommendation of XML Schema Part 2[1] WRT the base64Binary type[2]. The description of the base64Binary type now contains a BNF and a canonical lexical form. The canonical lexical form contains no whitespace characters within the stream of base64 characters. Whitespace characters at the beginning and/or end of the stream of base64 characters are stripped due to the whitespace facet of the type having a value of collapse. Thus any canonical lexical form of base64Binary is one line of base64 characters. I believe that the addition of a canonical lexical form satisfies our requirements WRT XOP/MTOM. Regards Gudge [1] http://www.w3.org/TR/2004/PER-xmlschema-2-20040318/ [2] http://www.w3.org/TR/2004/PER-xmlschema-2-20040318/#base64Binary