{"push_id":840200462,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"222f14bb6af143e234896ddb2b3a7a485a64932e","before":"f3a0890dd5b0e29ede9f85ff6334f281e14fb462","commits":[{"sha":"222f14bb6af143e234896ddb2b3a7a485a64932e","author":{"email":"1ff4181aab696b798c77705446704f8379072f07@sasktel.net","name":"Mark Sobkow"},"message":"2015.10.25 MSS Code Factory CFAll 2.6.13143 XMsg data streams now validate properly\n\nThe XSDs for the projects have been corrected and brought into sync with the messages\nand parsers produced for the applications by MSS Code Factory.  As a result, I am no\nlonger seeing any validation errors at the client nor the server under the debuggers,\nnot even when doing file imports.\n\nWhile that is good progress, it still doesn't fix the problem I was originally trying\nto fix by getting the schema validation in place -- stopping Xerces from normalizing\nstring attributes.\n\nWhy in the world anything other than an xsd:normalizedString type is being NORMALIZED\nin the first place is beyond me.  Why bother with a normalizedString type if the\ndefault behavior for a REGULAR string is to normalize it?","distinct":true,"url":"https://api.github.com/repos/msobkow/net-sourceforge-MSSCodeFactory-CFFreeSwitch-2-6/commits/222f14bb6af143e234896ddb2b3a7a485a64932e"}]}