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

Hello, Thanks for your feedback. Yes, right now for JSON Schema content completion we are using JSON meta-schemas. The meta-schemas are not so strict defined, this is why in the content completion list we present all the properties that can be inserted in a JSON Schema. We need to make the meta-sche...

Hello, This is a Schematron issue, therefore I recommend you to use the schematron@schematronist.org user list to get a better response. For this you need to register on the user list "http://schematronist.org/mailman/listinfo/schematron_schematronist.org". In my opinion you can add 3 checks somethi...

Hello Martin. Thanks for your feedback. We decided to implement the XPath support for JSON by converting the JSON documents to XML and then execute the XPath over the XML documents. The JSON to XML conversion is based on the "json.org" library, is the standard JSON to XML conversion. By executing th...

Hi Michael,

Yes, this can be a solution, to have an option in Oxygen that will enable the XSLT profiling based on Saxon TimingTraceListener.
I will add an issue for this.

Best Regards,
Octavian

Hi Michael, Thanks for your feedback. Unfortunately I don't have a solution for this problem. Yes, we could add support for variables in the Saxon configuration file, such us ${cfn}, but then that configuration file will be used only from Oxygen. Probably this support should be added directly in Sax...

Hello, We plan to update the Oxygen built-in Saxon engine to version Saxon 9.9, in the next release version. But you can install Saxon 9.8.0.15 in Oxygen as an add-on, and use it to validate and transform your documents. You can find more details in our user manual: https://www.oxygenxml.com/doc/ver...

Hi Martin,

The error seems to be generated because in the Options->Preferences-"XML / XSLT-XQuery / XQuery" options page you have the "Create structure indicating the type nodes" option set. Maybe we do not need to use this option when the output method is not xml.

Best Regards,
Octavian

Hello Martin, The Saxon engine generates the output correctly, depending on the output method that you have specified in the XQuery file. To display this result in Oxygen, you need to specify in the XQuery transformation scenario how you want to see the result. If you select "Present as sequence", t...

Hello Martin, Thanks for the feedback. Yes, the XPath support in Oxygen is 3.1. I added an issue to change the XPath version in the user interface. For the XPath result, to return maps and/or arrays, we need to update our internal result model to support this type of constructs. I added an issue als...

Hello Scott, One solution is to check if both words are used in the document and highlight one of the words. You can also propose a quick fix that will replace all occurrences of an word with another, something like this: <sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xsl...

Hello Mike, I cannot reproduce the problem. Maybe you can give me more details about your signing options and Oxygen version. I signed the "robert.taylor" element from "personal.xml" using the following options: Transformation=none, id='robert.taylor', Envelope, Append KeyInfo check, Signature algor...

Hi Frank, In fact Saxon complains about the validation of the XSLT file with Schematron, because the validation with Schematron is schema-aware and the XSLT (that is just an XML for this validation) has an invalid "xml:id" attribute value. The validation of the XSLT with Schematron it is not always ...

Hello Andreas We are using the standard Schematron implementation for compiling Schematron embedded in Relax NG-Schema. It seems that you are not allowed to add global variables. You can define a Schematron sch:let-variable in one of the sch:patterns from the embedded Relax NG-Schema. If a variable ...

Hello Steven, To enable Saxon TRACE_EXTERNAL_FUNCTIONS feature in Oxygen you need to create a Saxon configuration file. For this you can use the "Saxon configuration" new file template. Then crate a transformation scenario for the XSLT document and set the configuration file in the transformation sc...

Hi Frank, When an XSLT is validated using Schematron, the XSLT is considered to be an XML document. Therefore, the attribute value template from the value of the "xml:id" attribute ({rng:define-id(.)}) will not be evaluated, and it is not a valid xs:ID. I think it is correct to get this error if you...

Hello, Sorry for the late response. In Oxygen we do not have a build-in or add-on action that generated the Schematron documentation. Also, we didn't have any requests of such an action until now. But I think it is an interesting idea. Maybe you can provide the XSLT that you have created to generate...

Hi Martin, Thanks for the feedback. There where some problems with the syntax highlighting in maps, some of the tokens are not painted correctly, this is why the dot is painted with red. This issue is already fixed in the current developing stream, and it will be available in the next Oxygen release...

Hello Martin, We have an issue on our issue tracker to add some options that will allow you to turn off the built-in quick fixes. As an workaround I can give you a plugin that will allow you to deactivate all built-in quick fixes. You need to download the plugin from here http://www.oxygenxml.com/fo...

Hello Martin,

The quick fix does not work because the regular expression from the "xsl:analyze-string" element has quotes before and after the expression. You should remove the quotes, something like this:
Best Regards,
Octavian

Hello Mario, If the XML document is well-formed you should be able to execute an XPath expression. The schema validation errors should not affect the XPath execution. Can you tell me what is the XPath expression that you want to execute and what is the error that you obtain when you execute it? Also...