Hello, Thanks for your feedback. Yes, this seems to be a problem. I added an issue on our issue tracker to analyze it and find a solution. We will update this thread when will be fixed. I reproduce this behaviour also with <oXygen/> XML Editor 21.1, build 2019090904. It seems that this happens becau...

Hello, Unfortunately I don't understand the problem from the examples that you send. Maybe you send us more complete examples. You can use this form: https://www.oxygenxml.com/techSupport.html Also, being an XSLT related question maybe is better to post it on the XSLT list "xsl-list@lists.mulberryte...

Hello Martin,

We plan to have Saxon 10 as a plugin for Oxygen 22.1. I don't think we will provide the Saxon 10 plugin also for Oxygen 22.0.

Best Regards,
Octavian

Hello Rajneesh, I don't know what you do you mean by "always populated". If you want to make sure that a value is set for the alias1, coli1 and operator attributes, you can add a restriction on the string type. For example you can check that the length of the value is greater than one, something lik...

Hello Rajneesh, I think that you can add this constraint only using XSD 1.1 "xs:assert" or "xs:alternative", or maybe using a Schematron schema and create an assert there. You can read more about XSD 1.1 in the specification: https://www.w3.org/TR/xmlschema11-1/ Maybe you can address this question o...

Hello,

I an not sure what you want to do. Maybe you want to declare a prefix for the schema, something like this: .

Best Regards,
Octavian

Hello, Thanks for your feedback. Unfortunately I cannot reproduce de problem. I tested with <oXygen/> XML Editor 22.0, build 2020021016, I created a new HTML file and pasted the content you provided, then run the XPath //p . The XPath result was returned correctly for the HTML5 document. Maybe you a...

Hello, I think that the "idref()" function will work only if you use Saxon-EE (schema-aware) for Schematron validation. For this you need to enable the "Use Saxon EE (schema aware) for xslt2/xslt3 query language binding" option from Options->Preferences dialog -> "XML / XML Parser / Schematron" opti...

Hello,

I think that the problem is that you compare the string values of the numbers. You need to convert the text value into a number using the number() function. The condition must be something like this "number($grossArea) >= $conditionedAreaValue".

Best Regards.
Octavian

Hello Grethel, Unfortunately, in Oxygen XML Editor version 18 the SQF "use-for-each" feature is not available. Therefore, you cannot use a quick fix that has the "use-for-each" attribute. The only way to avoid the error is to have this rule implemented differently for the two versions of Oxygen. May...

Hello,

As an update, the user tested and found that there is a problem on their side.

Best Regards,
Octavian

Hello Shabeer, You can define also a range of characters that are not allowed. You can have also a quick fix that will remove all not allowed characters from the document. I think in this case the Schematron must look something like this: <?xml version="1.0" encoding="UTF-8"?> <sch:schema xmlns:sch=...

Hello Shabeer, You can create a Schematron that will detect and show you an waning when a zero-length character is detected. You can also have some quick fix actions that will replace the character with space for example, or will delete the character. The Schematron can look something like this: <?x...

Hello Martin,

Thanks for your feedback.
Yes, it seems that the content compilation suggestion in this case is not correct, should not propose 'stylesheet-` and should propose `stylesheet-location` instead. I added an issue on our issue tracker to correct this problem.

Best Regards,
Octavian

Hello, You don't need a Saxon EE licence if you are transforming from Oxygen. It seems that there is a problem when you set the stremming mode from the configuration file.If you enable the stremming mode from the Saxon configuration dialog options, by checking "Enable streaming mode", and you unchec...

Hello Stefan, There is a topic in our user manual that explains how to localize the Oxygen XML Editor Eclipse plugin. https://www.oxygenxml.com/doc/versions/21.1/ug-editorEclipse/topics/localizeGUI-eclipse-plugin.html But not all the keys are in "plugin_<locale>.properties". Please send us an email ...

Hello Stefan, Yes, if you will use the Web Editor for DIFFs you will need another licence. If you are interested in this solution you can send an email on our support. The version 22.0 of the Oxygen XML Editor is scheduled to be released in February 2020, and version 22.1 probably few months later. ...

Hello Stefan, Thanks for your interest. We implemented a visual compare using Oxygen XML Web Author, that can be integrated in the Eclipse browser. You can find more details about the comparison tool on our website: https://www.oxygenxml.com/xml_web_author/whats_new.html#21.1.1File_Comparison_Tool a...

Hello, Thanks for your feedback. This type of warning is presented only if you are using "xd:doc" element to document your stylesheet, but you didn't add documentation for all your templates and functions. To deactivate the Schematron checks for XSLT you need to go to Option-Preferences->Document Ty...

Hello,

Thanks for your feedback.
We have an issue on our issue tracker to generate also an HTML report for Diff Directories and Diff Files. I will add your comment and I will increase the issue priority. We will update this thread when it will be implemented.

Best Regards,
Octavian

Hello, The Schematron compilation provided in Oxygen does not generate an SVRL output, it generates only the messages. If you want to generate an SVRL output you can use the Schematron compilation stylesheets from the Schematron Github page: https://github.com/Schematron/ant-schematron There is also...

Hello, Thanks for your feedback. If you are editing an XHTML document I recommend to use the XHTML Editor. By default the ".html" extension is associated with the HTML Editor, and there are some issues with the editing in the HTML Editor Author page (they will be fixed for the next Oxygen release). ...

Hello, Yes, Oxygen uses Jing as default validation engine for RelaxNG and Xerces for XML Schema. For XML Schema you can change the default validation engine from Xerces to Saxon EE. You can set also some validation features. For more details see XML Schema Preferences page from our user manual: http...

Hi Bill,

The quick fixes can be run only inside Oxygen, we so not have support to run them outside.
You can try to use Escali engine, that also supports Schematron Quick Fixes:
https://github.com/schematron-quickfix/escali-package

Best Regards,
Octavian

Hi Bill, The sqf:stringReplace operation applies only on text nodes. The context of your rule are element nodes (title | navtitle | p | dt | dd | li | cmd), and this is why the quick fix does not work. Therefore, you need to specify that the quick fix will match the text from the current element usi...

Hello, Thanks for your feedback. In the latest versions we improved the JSON support in Oxygen, and we plan to add new JSON features also in the future. We already have an issue on our issue tracker to allow users to generate JSON Schema based on a JSON instance. I added your comment on the issue an...

Hi, If I understood correctly you have a structure something like this: <step> <cmd>test2</cmd> </step> <stepresult>2</stepresult> And you want to move the "stepresult" element in the "step" element, something like this: <step> <cmd>test2</cmd> <stepresult>2</stepresult> </step> A solution is to cre...

Hello, In your schema you are using built-in types defined in the XML Schema, such as: gYear, integer, double. All the build-in types define in the XML Schema have the namespace "http://www.w3.org/2001/XMLSchema". Therefore, in order to refer the built-in types in you schema you must specify the pre...

Hello, Thanks for your suggestion. The comparison algorithms that we are using in Oxygen are very complex, in not a simple thing to ignore elements order. Anyway, we can change the algorithms to ignore the elements order, but this is not the only challenge, then we need to present the differences so...

Hello Martin,

We just released Oxygen 21.1. The issue that you reported regarding the XPath version presented in the interface has been solved.
Thanks again for your feedback.

Best Regards,
Octavian