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

I think you just need to copy the following fragment and paste it after a pattern from your current Schematron file. <sch:let name="personIds" value="document('../personography/HAMpersons.xml')/tei:TEI//tei:person/@xml:id"/> <sch:pattern> <sch:rule context="tei:rs"> <sch:let name="refIds" value="for...

Hi David, I changed the Schematron to check all references. I also collect all teh IDs that are missing and I print them in the assert message. <sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2"> <sch:ns uri="http://www.tei-c.org/ns/1.0" prefix="tei"/> <sch:let name="p...

Hello David, A solution can be to tokenize the value of the @ref attribute, and then use a "for" to iterate the values and extract the IDs. Something like this: <sch:let name="refIds" value="for $id in tokenize(@ref, ' ') return substring-after($id, '#')"></sch:let> <sch:assert test="document('../pe...

Hello Nico, I think you need to set the "schemaLanguage" property. Something like this: <project basedir="." name="schema-validation-test" default="test"> <target name="test"> <schemavalidate file="src.xml" noNamespaceFile="schema.xsd" failonerror="true"> <property name="http://java.sun.com/xml/jaxp...

Hello, In Author mode we automatically render "<" with "<", and ">" with ">". But if you switch to Text page you will notice that is correct, based on your replace. How do you want the result to bein text, like this " <q>test1 test2 - Success</q>" or like this " <q>test1 test2 - Success</q>"? Best R...

Hello Ann, I created a Schematron rule that checks if the short description element is in an abstract element. If is not, provides also a quick fix that moves the short description element in an abstract element. In case an abstract element already exists, will move the short description in that ele...

Hello, We are using Trang to generate an XSD schema from XML files. It seems that Trang generates an xsi.xsd schema when you use attributes from "http://www.w3.org/2001/XMLSchema-instance" namespace. There is already an issue for this on the Trang project: https://github.com/relaxng/jing-trang/issue...

Hello Martin, In to see the functions in the content completion list you need to declare the namespace also on the Schematron root element. Something like this: <sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt3" xmlns:array="http://www.w3.org/2005/xpath-functions/array...

Hello, You can also set in Oxygen the "saxon.custom.options" property. For this you need to edit the "Run XSpec Test" transformation scenario, select the "Parameters" tab, then edit the "saxon.custom.options" property and set the value to "-init:no.uib.saxon.ef.SimmetricsInitializer --collection-fin...

Hi,

Yes, the issue was fixed in the latest maintenance build of Oxygen XML Editor 22.1.
https://www.oxygenxml.com/build_history.html#2020072902

Thanks again for your feedback.

Best Regards,
Octavian

Hello, For this type of questions probably is better to use the "schematron at schematronist dot org" mailing list. There are more people that can respond to them, and maybe better answers. I think that a solution for your Schematron rule can be something like this: <?xml version="1.0" encoding="UTF...

Hello,

Thanks for your feedback.
I added your vote on the issue. We will update this thread when the issue will be solved.

Best Regards,
Octavian

Hello, Thanks for your feedback. Yes, the phases from the included files are not collected when you associate a Schemaron in the validation scenario. We collect the phases from the included files only when the validation scenario is applied, and we display them in a dialog. This is because we do not...