Validation scenario bug
This should cover W3C XML Schema, Relax NG and DTD related problems.
-
- Posts: 84
- Joined: Wed Jul 19, 2017 6:04 pm
- Location: Austria
- Contact:
Validation scenario bug
I want to validate an xml-document with two file in one Scenario:
- Relax NG with embedded schematron rules"
- an external schematron file
Configuring Relax NG:
>Configure Transformation Scenario > use detected schema
is not possible to choose Embedded schematron rules
>Configure Transformation Scenario > use custom schema
The problem is with schematron phase:
The schematron phase of RelaxNG is by defualt the one which is defined in the external schematron file. But this phase is not present in the Relax NG and causes an error, there are acutally no phases at all. The workaround is: first edit scenario for an external schematron file: choose "prompt for phase", then edit the scenario for relax NG and choose "prompt for phase", then again go to the external schematron an choose the right phase. Somehow doesn't look well for me.
- Relax NG with embedded schematron rules"
- an external schematron file
Configuring Relax NG:
>Configure Transformation Scenario > use detected schema
is not possible to choose Embedded schematron rules
>Configure Transformation Scenario > use custom schema
The problem is with schematron phase:
The schematron phase of RelaxNG is by defualt the one which is defined in the external schematron file. But this phase is not present in the Relax NG and causes an error, there are acutally no phases at all. The workaround is: first edit scenario for an external schematron file: choose "prompt for phase", then edit the scenario for relax NG and choose "prompt for phase", then again go to the external schematron an choose the right phase. Somehow doesn't look well for me.

Kind regards,
Oleksii Sapov-Erlinger
Oleksii Sapov-Erlinger
-
- Posts: 2879
- Joined: Tue May 17, 2005 4:01 pm
Re: Validation scenario bug
Hi,
For custom validation scenarios, currently there is no support for choosing a specific phase when validating with embedded schematron (RelaxNG or XML Schema). Currently there's no way to specify the phase. It's not a UI bug, it's something that is not implemented in the validation system. I've logged an improvement request to support this in a future version.
I don't see how the workaround you mentioned would be working since there is no implementation that would connect the dots and relay the phase to the validator. If you are relying on what you see grayed out in the UI, that is just a disabled "Schematron phase" combo box that has not been cleared from the previous use of the dialog (when you used a Schematron schema type).
Regards,
Adrian
For custom validation scenarios, currently there is no support for choosing a specific phase when validating with embedded schematron (RelaxNG or XML Schema). Currently there's no way to specify the phase. It's not a UI bug, it's something that is not implemented in the validation system. I've logged an improvement request to support this in a future version.
I don't see how the workaround you mentioned would be working since there is no implementation that would connect the dots and relay the phase to the validator. If you are relying on what you see grayed out in the UI, that is just a disabled "Schematron phase" combo box that has not been cleared from the previous use of the dialog (when you used a Schematron schema type).
Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
-
- Posts: 84
- Joined: Wed Jul 19, 2017 6:04 pm
- Location: Austria
- Contact:
Re: Validation scenarios bug
Hi,
I'd like to ask for update on this issue for oXygen versions higher than 20.1.
To clarify the issue: I do not need a phase when validating Relax NG with embedded schematron (first URL). The phase is defined in the second URL which is pure schematron, not embedded. The problem is that oXygen automatically configures the phase for the first URL based on the phase defined for the second URL. Obviously the first URL does not contain the phase so an error prompts. This is a bug on my opinion.
I'd like to ask for update on this issue for oXygen versions higher than 20.1.
To clarify the issue: I do not need a phase when validating Relax NG with embedded schematron (first URL). The phase is defined in the second URL which is pure schematron, not embedded. The problem is that oXygen automatically configures the phase for the first URL based on the phase defined for the second URL. Obviously the first URL does not contain the phase so an error prompts. This is a bug on my opinion.
Kind regards,
Oleksii Sapov-Erlinger
Oleksii Sapov-Erlinger
-
- Posts: 388
- Joined: Thu Jul 01, 2004 12:29 pm
Re: Validation scenario bug
Hello,
Thanks for your feedback.
From what I tested, using Oxygen XML Editor 24.1 build 2022062007, the phase specified for the Schematron validation is not used for embedded Schematron rules from the RelaxNG schema. In case you declare the phases also in embedded Schematron rules from the RelaxNG schema, you will be able to specify the phase in the validation scenario. In case you do not declare phases in the embedded Schematron rules from the RelaxNG schema, all the rules will be applied.
Maybe you can try to test with Oxygen XML Editor 24.1, in case it does not work maybe you can send us some sample files to try to reproduce the situation.
Best Regards,
Octavian
Thanks for your feedback.
From what I tested, using Oxygen XML Editor 24.1 build 2022062007, the phase specified for the Schematron validation is not used for embedded Schematron rules from the RelaxNG schema. In case you declare the phases also in embedded Schematron rules from the RelaxNG schema, you will be able to specify the phase in the validation scenario. In case you do not declare phases in the embedded Schematron rules from the RelaxNG schema, all the rules will be applied.
Maybe you can try to test with Oxygen XML Editor 24.1, in case it does not work maybe you can send us some sample files to try to reproduce the situation.
Best Regards,
Octavian
Octavian Nadolu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service