Hello,

Yes, the assert condition is satisfied even if the type is not 'INTERNATIONAL', or if the type is 'INTERNATIONAL' and you have an 'IBAN' element.

Best Regards,
Octavian

Hello, For the first example the content completion does not work for your modules because the schema does not define a global "Table" element. For the second example you define a global "Table" element in your schema, but its type is based on an inheritable attribute "@kind...

Hello, Thank you for your feedback. The content completion in text value templates works only for variables and parameters. We have an issue on our issue tracker to implement also XPath content completion in text value templates. This is scheduled for the next oXygen version. We will update this thr...

Hello David, If you want to add link to the Schematrom message you must specify the link in the value of the @see attribute. The attribute can be added on the report/assert element or on the rule (as "xephon" said). The links are presented as a clickable icon, both on the tooltip that is p...

Hello David,

Thank you for your feedback.
We do not have support to set the search scope to the current diff intervals from the editor. The only way to limit the search scope to multiple intervals is by using an XPath expression in the Find/Replace dialog.

Best Regards,
Octavian

Hello.

We released Oxygen XML Editor 19.1 a couple of days ago and we added support for XSLT 3.0 text value templates.

Best Regards,
Octavian

Hello,

We released Oxygen XML Editor 19.1 a couple of days ago and the problem you reported should be fixed.

Best Regards,
Octavian

Hello,

There is no action to do this automatically. You can create a stylesheet that copies the nodes that you need and apply it on the XML files.

Best Regards,
Octavian

Hello, We do not have such a feature. You need to compare the entire documents. You can use the "Ignore nodes by XPath" feature, to ignore the changes from the document that are made in other nodes. For this you need to create an XPath expression that matches all the nodes from the documen...

Hello, For me it works fine. For example if I compare the two documents below using an XML comparison algorithm (XML Fast or XML Accurate), and I have the option Ignore Namespace Declaration set on true, no difference is presented. I tested using oXygen XML Editor 19.0. Maybe you are using a non-XML...

Hello, It is an interesting idea, but you cannot run the Schematron or SQF just on a fragment because the you need entire context from the XML (namespace declarations, ancestors). A Schematron rule can also collect information from different parts of the document in order to be applied. And you need...

Hello, You can create an abstract pattern and then for each word you need to instantiate the pattern and pass the word as parameter. Something like this: <sch:pattern id="warap" abstract="true"> <sch:title>Italic suggestion</sch:title> <sch:rule context="*[not(ancestor-or-se...

Hello, If you want to wrap an word in an element I recommend you to use the sqf:stringReplace operation. You can match the word that you want to wrap and replace it with a fragment. The quick fix should look something like this: <sch:rule context="*[not(ancestor-or-self::title) and not(ancestor...

Hello, You can create a rule that for each languageSpecificBrandName element verifies that there is no previous sibling with the same name and language code. The rule must be something like this: <sch:rule context="languageSpecificBrandName"> <sch:let name="currentLang" value=&qu...

Hello, You can create a rule for the description element that checks the number of functionalName elements that have the @languageCode equal with 'en', something like this: <sch:pattern> <sch:rule context="description"> <sch:assert test="count(functionalName[@languageCode= 'en']) = 1&...

Hello Paul, The "Ignore nodes by Xpath" option is available only for Diff Files. We do not have support in Diff Directories to merge the contents of the files and ignore some nodes. The only way to merge the contents of the files and ignore nodes is by using the Diff Files. I will add an i...

Hello, Thank you for the feedback. It seems that we do not compute the context node correctly in this case. The context node for the insert element operation should be the text node and the quick fix must insert the element after the text node, not after the section. I added an issue on out issue tr...

Hi Ann, This happens because the elements that you are inserting using the quick fix are from the Schematron namespace. The Schematron namespace is defined on the schema root as the default namespace for your document (xmlns="http://purl.oclc.org/dsdl/schematron"), and because you did not ...

Hello, Yes, you can use th[@rowspan='2']. For me it works fine. You can also report a problem only when the value of the rowspan is different from the default one. Something like this: <sch:rule context="th[@rowspan!='1']"> <sch:report test="true()">Don't use the rowspan attribut...

Hello, You can convert to 'xs:date' and compare the dates. To obtain the dateA you need to get the previous sibling using the following XPath 'preceding-sibling::dateA[1]', and then decrease one day to obtain the expected date. You can provide also a fix that will correct the current date. The Schem...

Hello, For the example that you provided You need to create a Schematron something like this: <sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2"> <sch:pattern> <sch:rule context="element1"> <sch:let name="matchElemName" value=&qu...

Hello Grethel, The solution that I can think of is to use abstract patterns. You can create an abstract pattern with the report, and instantiate this pattern for each forbidden word with some specific parameters (the forbidden word, the replace word, maybe a different message). In the abstract patte...

Hello Grethel, A solution is to change the message and add the text "This word should not be used:" only once. Something like this: <xsl:variable name="list-words"> <xsl:for-each select="document('list_of_words.dita')//tbody/row/entry[1]"> <xsl:variable name="word&...

Hi Wojtek, Stating with oXygen v18.1 we changed the "sqf:stringReplace" operation to allow using java regular expressions in the value of the @regex attribute. Therefore, the case-insensitive matching can be enabled via the embedded expression (?i). In your case you can create a quick fix ...

Hello, Thank you for the feedback. I will add an issue on our issue tracker to find a solution for this problem. As an workaround you can deactivate the Schematron checks for XSLT. For this you need to go to Option-Preferences->Document Type Association options page, then edit the XSLT document type...

Hello,

I don't understand the exact problem. Can you send me some sample files to reproduce it? If the samples are too big you can send them to our support email address (support at oxygenxml dot com).
What oXygen version do you use?

Best Regards,
Octavian

Hello, The namespace scope of the path elements in the assertion expression is determined by the value of the xpathDefaultNamespace attribute. If the attribute is absent, its value is assumed to be ##local - which translates into null namespace. This attribute can also be declared to hold any URI, o...

Hello,

You need to add a namespace declaration on you schema root, something like this: xmlns:b="http://magazine.babson.edu"
Then change the assert to use the declared prefix, something like this: <xs:assert test="b:type='Undergraduate'"/>

Best Regards,
Octavian

Hello, Unfortunately I cannot reproduce the problem. For me it works fine. If I validate the following XML with the Schematron that you provided I get both errors, on "office:Date" and "staff:Available". The only thing that I can think of is to have a different namespace URI for ...

Hello, You need to send me also a sample Schematron file in order to find the problem. Is the Schematron embedded in XSD or is in a separate file? Are the rules in different patterns, and you use phases? Make sure that the namepaces for the "office" and "staff" are declared corre...