Hello, Unfortunately I didn't found a solution for this problem. It seems that the serializer that we use in oXygen when we create the fragment to be inserted, generates also the XML namespace declaration. I added an issue on our issue tracker. We will notify you when it will be fixed. Best Regards,...

Hello Ron, The Schematron specification does not mention that you can use XSLT in Schematron. But Schematron was designed somehow to use XSLT. The reference implementation uses XSLT: http://schematron.com/front-page/the-schematron-skeleton-implementation Therefore, the use of XSLT in Schematron is i...

Hello, In <oXygen/> XML Editor 18.1 we updated the sqf:stringReplace operation to allow using Java regular expressions. The Saxon "j" flag is automatically set for the regular expressions of the sqf:stringReplace operation. You can read more about this in our user manual: https://www.oxyge...

Hello, The XPath expression that you used in the assertion excludes the children elements, but you need to exclude the whitespaces when you count the string length of the text node. For this you can use the "normalize-space()" function, something like: <sch:assert test="string-length(...

Hello, If you have a rule with the context set on the "nc:Activity" element, you can execute an XPath expression that will get all activity associations that have the current activity id "//mine:ActivitySubjectAssociation[nc:Activity/@s:ref = $id]". Then from the association you ...

Hello, I don't understand exactly what you want to check. Maybe you can give me some real examples, how many persons can be associated with an activity, or how many activities can be associated with a person, maybe you have a schema for the XML file. If you want to check for example if the persons o...

Hello, According to the SQF Specification , the content of the replace operation has the same functionality as the content of xsl:template element. The problem is that in XSLT when a comment is generated its content must be only text. XSLT Specification says: "It is an error if instantiating th...

Hello, You can create a Schematron rule that matches the keyword element, and check that the text after the element does not start with the 's' character. The rule will be something like this: <sch:rule context="keyword[@keyref]"> <sch:report test="following-sibling::node()[1][self::t...

Hello, Yes, you can obtain the current user name also in Schemtron. You have two solutions: The first one is to use the "system-property()" function, something like this: <xsl:value-of select="system-property('user.name')"/> We are using Saxon processor to validate an XML with a ...

Hi Patrik, In oXygen 18.1 we added support in the validation scenario to specify extension JARs for the Schematron documents validation, and for the validation of XML documents against Schematron. In the Specify Schema dialog box there is an Extensions button that opens a dialog box and allows you t...

Hi Nicholas, Thanks for your feedback. I added an issue on our issue tracker to find a solution for this. The problem is that the Schematron error/warning must be ignored based on the assert/report message, and I don't know if this is accurate. If the Schematron developer uses the same message for a...

Hello, We do not have such an option in oXygen XML Editor. But you can move the rules that you want to ignore in a separate Schematron file. In this way you can just remove that Schematron file from the validation scenario, or create a different validation scenario for the users that want to ignore ...

Hello, You can use the "substring-before()" and "substring-after()" functions to get the characters that you want, as in the following example: <xsl:variable name="var" select="'1313-231-546'"/> <xsl:variable name="value" select="substring-after...

Hello, Because you are using Schematron with XSLT 1.0, you cannot apply a regular expressions to match a string. A solution for XSLT 1.0 to check is if lower case alphabets and digits are used in a text is to use the translate(). Something like in the following example: <sch:let name="vLower&qu...

Hello, You cannot pass the ignore case flag in the stringReplace operation. I will add an issue on the SQF specification to add this support. As an workaround you can use the "sqf:replace" operation instead and the "xsl:analyze-string" instruction. Something like this: <sqf:repla...

Hello, Yes, it is not possible to use a variable in the value of the href attribute of an include element. The value of the href attribute must be an URI reference. More information about Schematron you can find on http://www.schematron.com/ website. ISO Schematron specification: http://www.schematr...

Hi Shabeer, You need to determine each line of text from your "pre" element and check its length. I have created a sample for you using XSLT to determine the lines of text. You can find the sample below: <sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding=&q...

Hello, In oXygen XML Editor 18 we added support in Diff Files tool to ignore nodes using an XPath expression. An XPath panel was added on the toolbar of the File Comparison tool and in the Compare view in the Syncro SVN Client. You can enter an XPath 2.0 expression to ignore certain nodes when compa...

Hello, In oXygen XML Editor 18 we added support in Diff Files tool to ignore nodes using an XPath expression. An XPath panel was added on the toolbar of the File Comparison tool and in the Compare view in the Syncro SVN Client. You can enter an XPath 2.0 expression to ignore certain nodes when compa...

Hello, In oXygen XML Editor 18 we added support to ignore nodes using an XPath expression. An XPath panel was added on the toolbar of the File Comparison tool and in the Compare view in the Syncro SVN Client. You can enter an XPath 2.0 expression to ignore certain nodes when comparing using the XML ...

Hello, If you want the error to be displayed on the "floatfig" element when the @float attribute is not "none" and you do not have the "floatfig-group" as child then you need to change the assert. Instead of <sch:assert test="(string(@float) ne 'none') and exists(c...

Hello Nick, The assert for the "keydef/@processing-role" attribute does not work because the default value for the "processing-role" attribute is "resource-only". When the XML is validated against Schematron you cannot determine if the attribute is set in document or is...

Hello, In oXygen XML Editor 18.0 (that will be released probably at the end of this moth) we added support to ignore nodes by XPath but only for the file comparison ("Diff Files"). We have an issue on our issue tracker to implement this also for "Diff Directories". But this is sc...

Hello, I corrected your Schematron schema, you can find it below. You made some small mistakes: - in the 'qualifierValue' variable the $refValue should not be in apostrophes, instead of @value='$refValue' use @value=$refValue. - in the assert you need to use apostrophes for documentType, instead of ...

Hello,

Yes, we do not support variables in the value of the @subject attribute. You can use an XPath expression that does not contain variables.
I added an issue on our issue tracker regarding this problem. We will notify you when it will be solved.

Best Regards,
Octavian

Hello Gerrit, In oXygen XML Editor 17.1 we support the "Schematron Quick Fixes Specification - Draft April 2015" . This does not include the "@use-for-each" attribute. We want to add support to generate dynamic fixes, but first we need to have this in the specification. There is ...

Hello, Patrik response is correct, you need to set a namespace for the inserted element or use a prefix for the Schematron elements. I always recommend to use a prefix for the Schematron elements. In this way you can insert elements from no namespace without caring about the namespace declaration. T...

Hi Patrik,

I added an issue on our issue tracker regarding this problem. It is a particular case and the replace operation needs to be implemented differently.

Best Regards,
Octavian

Hi Stepan,

Thanks for the sample files. We can understand better the use case.

Best Regards,
Octavian

Hi Stepan,

I already added an issue with your feature request.
A solution can be to change the flattenSchema and allow to specify also the root element to start from.

Best Regards,
Octavian