Hello, I think the schema should be something like this: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://purl.oclc.org/dsdl/schematron"> <pattern> <rule context="xml"> <let name="test" value="topic/test[number(text()) > 5]"/> <report test="$test" subject="$test[1]"> Value greater than 5...

Hello,

I don't know exactly your use case, maybe you can give me an example of an XML document and a Schematron rule, to understand better the situation.
I think you can add the rule on a parent context, and then change the assert to fail if one of the rules is not true.

Best Regards,
Octavian

Hello Cathy, For me it works if I have the stylesheet something like this: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs" version="2.0"> <xsl:output method="xml" indent="...

Hello Cathy, I think a possible solution is to have a stylesheet something like this: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> <xsl:output method="xml" encoding="UTF-8" indent="yes"/> <xsl:variable name="MRPITEMS" select="...

Hi Stefan, We integrated our diff in the Eclipse comparison support. You need to trigger the eclipse comparison support. I think a solution is something like this: https://wiki.eclipse.org/FAQ_How_do_I_create_a_compare_editor%3F But you need to make sure that you set the "xml" type in the CompareIte...

Hello Stefan, The comparison in Eclipse should start automatically in Author mode for any XML document that has a CSS associated. You need to make sure that the "Enable file comparison in Author mode" option from the Preferences > Oxygen XML Editor Eclipse plugin > DIFF option page is set. https://w...

Hello, We just released Oxygen XML Editor version 23.1 and we implemented the support to ignore validation problems. The validation problems that have an ID can now be ignored using quick fix actions. You can find more details on our website: https://www.oxygenxml.com/xml_developer/whats_new.html#23...

Thanks for you feedback.

We have a sample implementation of an intelligent integrated style guide, that works both in Oxygen XML Editor and Oxygen XML Web Author.
https://github.com/oxygenxml/integrated-styleguide

Best Regards,
Octavian

Hello, Thanks for your feedback. Unfortunately, you cannot add the text link in the message. We have an issue on our issue tracker to add this support in a future version. I added your comment on the issue and increased its priority. When the issue will be implemented we will update this thread. Bes...

Hello Frank, Thanks for your feedback. Yes, it seems to be a problem with the Saxon validation in an assert. If the type "ns1:Token3" is set as an element type, no problem is reported. Therefore, it seems that the problem occurs when referring the type in an assert element. I reported the problem at...

Hello, Thanks for your feedback. There is a problem with the Saxon validation, I already reported this problem at Saxon, and they fixed it. Here is the Saxon issue: https://saxonica.plan.io/issues/4518 We need to update the default Saxon library in Oxygen, probably in the next Oxygen major release. ...

Hello David,

I will try to analyze this situation and give you some hints, but it will be more easy for me if you can send me some sample files. You can send them on our "support at oxygenxml dot com" email address.

Best Regards,
Octavian

Hello Martin,

Thanks for your feedback.
There is already an issue on our issue tracker to improve the JavaScript editing support. I added your comment on the issue and I increased its priority. Maybe in the next Oxygen major release we can try to improve this support.

Best Regards,
Octavian

Hello, Thanks for your feedback. Yes, it seems that when Saxon is in streaming mode the xsl:message is not presented in the Messages view. The message is presented in the console view, if open you have opened Oxygen from a console you will see the message there. I added an issue on our issue tracker...

Hello, From what I tested the message is presented also when the ${currentFileURL} is used as XML URL. If you create a transformation scenario for an XSL and you use the ${currentFileURL} for both XML URL and XSL URL, the ${currentFileURL} editor variable will be expended to the location of the XSL....

Hello, Unfortunately I cannot reproduce the problem. I tested with the same version that you used <oXygen/> XML Editor 23.0, build 2020121712. I used Saxon HE 9.9.1.7 for debugging with the default options, and I get the test message in the Messages view. What engine do you use for debugging? Maybe ...

Hello, From what I tested, with <oXygen/> XML Editor 23.0, build 2020111805, the debugging works fine for me. What version of Oxygen XML do you use? Can you send me also the XML document used in the debugging process, or a sample on which you reproduce the problem? What engine do you use for debuggi...

Hello,

New versions for "Saxon XSLT and XQuery Transformer" add-on are now available to install for Oxygen 23.0.

They integrate the latest available engine versions for Saxon 9.9 and 10 (9.9.1.8 and 10.3 respectively).

Best Regards,
Octavian

Hello Leo, Thanks for your feedback. Unfortunately, the error codes where removed from the validation error message and you cannot view them. In Oxygen version 23.0 we added back the links to the W3C specification. You can find more details in our documentation: https://www.oxygenxml.com/doc/version...

Hello, I don't know exactly what rule you want to add, and what is the structure you want to impose. Probably this error occurs because you have two xref elements with the same value in the @product attribute. I think first you need to check if all the xref elements are correct. You can check if you...

Hello, Thanks for the feedback. Yes, it seems to be a problem when you set a static parameter from the transformation scenario. We already have an issue on our internal issue tracker for this problem. I will add your comment on the issue and increase its priority. When it will be fixed we will updat...

Hello, The context must be "*[count(xref) = 3]", and the variables must be without quotes. I think the pattern should be something like this: <sch:pattern> <sch:rule context="*[count(xref) = 3]"> <sch:let name="stag" value="normalize-space(xs:string(xref[@product='staging']))"/> <sch:let name="prod"...

Hello, We just released yesterday Oxygen XML Editor version 23.0, this contains the fix for the problem you reported. You can download the latest build from here: https://www.oxygenxml.com/xml_editor/download_oxygenxml_editor.html The fix is available also in Oxygen XML Editor version 22.1. You can ...

Hello, Thanks for your feedback. In order to be interpreted as a boolean you can set the value of the parameter as true() , and check the Evaluate as XPath box. Even if the value is presented with quotes in the parameters dialog, it will be interpreted as a boolean value. For example, If I run the f...

Hello Scott,

Yes, in case there are multiple text nodes in a paragraph the "text()" function will return a sequence of text nodes. You can replace the "$text" variable with the following one: Best Regards,
Octavian

Hello Scott , I think that a solution can be to count the number of matched keys, then you can write also the matched keys in the assertion message. The pattern must look something like this: <sch:pattern> <sch:let name="keys" value="document('keys-common.ditamap')//keyword"/> <sch:rule context="p">...

Hello, Thanks for your feedback. I think your document is an XHTML (has the namespace "http://www.w3.org/1999/xhtml" set on root ), or it is an HTML document opened in the XHTML editor. You can verify the content type of the opened document in the Properties view (Help menu->Show View->Properties). ...

Hello, If you associate a validation scenario on a folder from Project view, the scenario will be automatically associated with all the files from that folder and subfolders. Then when you open a file from the folder the file will be validated with the associated scenario. You can use the Validate a...

Hello, I think a solution for this is to create a validation scenario for each phase from Schematron.Then you can associate each scenario on the folder where the XML files are located, depending on the phase that you want to use for that folder. For this you need to use the Configure Validation Scen...

Hello,

For the XML-to-JSON conversion we do not use XSLT. We use the json.org library. Therefore, we cannot generate an XSLT for this conversion.

Best Regards,
Octavian