After a little more investigating, it looks like there is a problem updating a schema. In this case I'm simply adding some optional element attributes to the schema and updating it in the schemas database, but strict validation of a document is failing. When I revert back to the previous schema it validates just fine. What is up with that?
It also appears that my schema was updated automatically at some point to include the use="optional" attribute for optional schema attributes and that elements were updated with the nillible="false" and abstract="false" attributes. I don't understand why this happened. Fortunately the update posed no problems with validation, but it is out of sync with the original schema in my repository - kind of weird. This is all confusing. In the past I have been able to update the schema without incurring such problems. Any ideas? Thank you! Tim From: [email protected] [mailto:[email protected]] On Behalf Of Tim Sent: Saturday, July 12, 2014 2:20 PM To: 'MarkLogic Developer Discussion' Subject: [MarkLogic Dev General] Strict validation error encountered in ML7 but not in ML6 Hi Folks, When I run strict validation of a document against a schema using MarkLogic 6.0-2 (which has been running consistently and without a problem for years), it passes validation, but when I run strict validation using the same document at the same URI with the same schema using MarkLogic 7.0-2.3, it complains about a missing sub-element in an element list. Have there been any changes to strict validation in ML7 or any similar errors reported? Thank you! Tim Meagher
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
