Pretty straightforward bug here: the deprecated backwards-compatible
version of parse-xml-fragment() converts the arguments string ("EDSlwf"
in the above example) into an <parse-xml-options:options> element. The
"w" flag introduces a <parse-xml-options:strip-boundary-space/> element
into that <options>. But there's no strip-boundary-space element defined
by the schema. There doesn't seem to be anything at all related to
"boundary" or "whitespace" in the options schema, in fact, which leads
me to believe that perhaps that functionality simply never got
implemented.-- You received this bug notification because you are a member of Zorba Coders, which is the registrant for Zorba. https://bugs.launchpad.net/bugs/1008504 Title: parse-xml-fragment triggers schema error Status in Zorba - The XQuery Processor: New Bug description: When running the attached example a schema validation error inside the xml module is thrown: /home/tryzorba/repo/zorba-2.2.0/build/URI_PATH/com/zorba- xquery/www/modules/xml.xq>:346,5: dynamic error [err:XQDY0027]: "Schema validation failed: no declaration found for element 'parse- xml-options:strip-boundary-space'": unexpected validity property -----------------------------------------------------------------------------Example: xquery version "3.0"; import module namespace parse-xml = "http://www.zorba- xquery.com/modules/xml"; parse-xml:parse-xml-fragment("<xml>test</xml>","EDSlwf") To manage notifications about this bug go to: https://bugs.launchpad.net/zorba/+bug/1008504/+subscriptions -- Mailing list: https://launchpad.net/~zorba-coders Post to : zorba-coders@lists.launchpad.net Unsubscribe : https://launchpad.net/~zorba-coders More help : https://help.launchpad.net/ListHelp
