Any way to control output of Schematron validation?
We are using schematron validation in oXygen, with a custom element in our output messages. I'm finding that this causes the output messages to be unusable, because they are displayed on only one line, and that line is taken up by the custom element, and all of it's various namespace declarations. I'm attaching a screenshot -- not sure if it will get through the mailman. Is there any way to configure oxygen to show the text value of these messages? It would be much more useful. As it is, the user has to hover the mouse over the message, or r-click and do "show messages", and even then, the message is dominated by this element, because of all the (unused) namespace declarations on it. Thanks! -- Chris Maloney NIH/NLM/NCBI (Contractor) Building 45, 4AN36D-12 301-594-2842
Hello, This is the default behavior of the Schematron assert/report messages. If the "allow-foreign" option is set for Schematron validation, then all elements from the Schematron assert/report message will be copied in the output using the "xsl:copy-of" instruction. This will generate all the elements in the output with the namespaces from the context. You can change "allow-foreign" option from the "XML/XML Parser/Schematron" options page. If the "allow-foreign" option is not set, then you will not be allowed to add other elements in the Schematron assert/report message, but I think that you want those elements in the output. We do not have an option to generate the assert/report messages as text values. I added an issue on our issue taker to analyze this problem and maybe generate the elements from the Schematron message without the namespace declarations. We will notify you when this will be fixed. Best Regards, Octavian -- Octavian Nadolu <oXygen/> XML Editor http://www.oxygenxml.com On 07.12.2015 21:16, Maloney, Christopher (NIH/NLM/NCBI) [C] wrote:
We are using schematron validation in oXygen, with a custom element in our output messages. I'm finding that this causes the output messages to be unusable, because they are displayed on only one line, and that line is taken up by the custom element, and all of it's various namespace declarations. I'm attaching a screenshot -- not sure if it will get through the mailman.
Is there any way to configure oxygen to show the text value of these messages? It would be much more useful. As it is, the user has to hover the mouse over the message, or r-click and do "show messages", and even then, the message is dominated by this element, because of all the (unused) namespace declarations on it.
Thanks!
-- Chris Maloney NIH/NLM/NCBI (Contractor) Building 45, 4AN36D-12 301-594-2842
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
We’d like to use that option, too. We are also using allow-foreign, and we generate some HTML markup in the messages that we render in HTML reports. But for debugging purposes and for Schematron reuse we’d like to be able to see the rich messages as plain text in oXygen. On 08.12.2015 09:43, Oxygen XML Editor Support (Octavian Nadolu) wrote:
Hello,
This is the default behavior of the Schematron assert/report messages. If the "allow-foreign" option is set for Schematron validation, then all elements from the Schematron assert/report message will be copied in the output using the "xsl:copy-of" instruction. This will generate all the elements in the output with the namespaces from the context. You can change "allow-foreign" option from the "XML/XML Parser/Schematron" options page. If the "allow-foreign" option is not set, then you will not be allowed to add other elements in the Schematron assert/report message, but I think that you want those elements in the output.
We do not have an option to generate the assert/report messages as text values. I added an issue on our issue taker to analyze this problem and maybe generate the elements from the Schematron message without the namespace declarations. We will notify you when this will be fixed.
Best Regards, Octavian
Hello. I added also your comment on the issue and I increased the its priority. We have also other issue related to this, to render in <oXygen/> the HTML markup from the assert/report messages. Best Regards, Octavian -- Octavian Nadolu <oXygen/> XML Editor http://www.oxygenxml.com On 08.12.2015 10:51, Imsieke, Gerrit, le-tex wrote:
We’d like to use that option, too. We are also using allow-foreign, and we generate some HTML markup in the messages that we render in HTML reports. But for debugging purposes and for Schematron reuse we’d like to be able to see the rich messages as plain text in oXygen.
On 08.12.2015 09:43, Oxygen XML Editor Support (Octavian Nadolu) wrote:
Hello,
This is the default behavior of the Schematron assert/report messages. If the "allow-foreign" option is set for Schematron validation, then all elements from the Schematron assert/report message will be copied in the output using the "xsl:copy-of" instruction. This will generate all the elements in the output with the namespaces from the context. You can change "allow-foreign" option from the "XML/XML Parser/Schematron" options page. If the "allow-foreign" option is not set, then you will not be allowed to add other elements in the Schematron assert/report message, but I think that you want those elements in the output.
We do not have an option to generate the assert/report messages as text values. I added an issue on our issue taker to analyze this problem and maybe generate the elements from the Schematron message without the namespace declarations. We will notify you when this will be fixed.
Best Regards, Octavian
oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Just chiming in with a third vote in support - we'd find it very handy to be able to slim down Oxygen's validation output for non-technical colleagues. Being able to use HTML to control it, as Octavian mentions, would be marvellous icing on the cake! On 08/12/2015 09:36, Oxygen XML Editor Support (Octavian Nadolu) wrote:
Hello.
I added also your comment on the issue and I increased the its priority.
We have also other issue related to this, to render in <oXygen/> the HTML markup from the assert/report messages.
Best Regards, Octavian
Cambridge University Press is the publishing business of the University of Cambridge with VAT registered number GB 823 8476 09. Our principal office is at University Printing House, Shaftesbury Road, Cambridge, CB2 8BS, United Kingdom.
Hello, Thank you for the feedback. I think that in <oXygen/> we should render the HTML from the Schematron assert/report messages, but ignore the other unknown elements. Maybe we should add also an option to see the original message. Best Regards, Octavian On 08.12.2015 12:38, Tom Cleghorn wrote:
Just chiming in with a third vote in support - we'd find it very handy to be able to slim down Oxygen's validation output for non-technical colleagues. Being able to use HTML to control it, as Octavian mentions, would be marvellous icing on the cake!
On 08/12/2015 09:36, Oxygen XML Editor Support (Octavian Nadolu) wrote:
Hello.
I added also your comment on the issue and I increased the its priority.
We have also other issue related to this, to render in <oXygen/> the HTML markup from the assert/report messages.
Best Regards, Octavian
Cambridge University Press is the publishing business of the University of Cambridge with VAT registered number GB 823 8476 09. Our principal office is at University Printing House, Shaftesbury Road, Cambridge, CB2 8BS, United Kingdom. _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi, will you also support cross references (i.e. <a href="..."/>) pointing to some element within the document or another document? When using Schematron to report an inconsistency with another part of the document it would be nice to provide a way for the author to easily go there. And when thinking about options for displaying the messages you could maybe also consider to add a link to the Schematron rule which generated the message. It appears that the bug is not in the validated document but the Schematron rule. And it's not always easy to find the rule - especially when others have implemented it. Thanks and regards, Patrik ------------------------------------------------------------------ Systemarchitektur & IT-Projekte Tel: +49 40 33449-1142 Fax: +49 40 33449-1400 E-Mail: mailto:Patrik.Stellmann@gdv-dl.de -----Ursprüngliche Nachricht----- Von: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] Im Auftrag von Oxygen XML Editor Support (Octavian Nadolu) Gesendet: Dienstag, 8. Dezember 2015 14:03 An: oxygen-user@oxygenxml.com Betreff: Re: [oXygen-user] Any way to control output of Schematron validation? Hello, Thank you for the feedback. I think that in <oXygen/> we should render the HTML from the Schematron assert/report messages, but ignore the other unknown elements. Maybe we should add also an option to see the original message. Best Regards, Octavian GDV Dienstleistungs-GmbH & Co. KG Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de Sitz und Registergericht: Hamburg HRA 93 894 USt.-IdNr : DE 205183123 Komplementärin: GDV Beteiligungsgesellschaft mbH Sitz und Registergericht: Hamburg HRB 71 153 Geschäftsführer: Dr. Jens Bartenwerfer Michael Bathke Volker Sonnenburg ------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet. This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Hello Patrik, It is an interesting idea to have links to the elements from document. I will add your comment on the issue. This can be implemented using the support that <oXygen/> provides to open a specific location using the line/column, simplified XPath index or anchors: https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/opening-docume... I will add an issue for your second suggestion, to add a link to the Schematron rule that generated the message. This can be useful for debugging. So, I think maybe there should be an option to activate it. Best Regards, Octavian -- Octavian Nadolu <oXygen/> XML Editor http://www.oxygenxml.com On 09.12.2015 09:35, Dr. Patrik Stellmann wrote:
Hi,
will you also support cross references (i.e. <a href="..."/>) pointing to some element within the document or another document? When using Schematron to report an inconsistency with another part of the document it would be nice to provide a way for the author to easily go there.
And when thinking about options for displaying the messages you could maybe also consider to add a link to the Schematron rule which generated the message. It appears that the bug is not in the validated document but the Schematron rule. And it's not always easy to find the rule - especially when others have implemented it.
Thanks and regards, Patrik
------------------------------------------------------------------ Systemarchitektur & IT-Projekte Tel: +49 40 33449-1142 Fax: +49 40 33449-1400 E-Mail: mailto:Patrik.Stellmann@gdv-dl.de
-----Ursprüngliche Nachricht----- Von: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] Im Auftrag von Oxygen XML Editor Support (Octavian Nadolu) Gesendet: Dienstag, 8. Dezember 2015 14:03 An: oxygen-user@oxygenxml.com Betreff: Re: [oXygen-user] Any way to control output of Schematron validation?
Hello,
Thank you for the feedback. I think that in <oXygen/> we should render the HTML from the Schematron assert/report messages, but ignore the other unknown elements. Maybe we should add also an option to see the original message.
Best Regards, Octavian
GDV Dienstleistungs-GmbH & Co. KG Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de
Sitz und Registergericht: Hamburg HRA 93 894 USt.-IdNr : DE 205183123
Komplementärin: GDV Beteiligungsgesellschaft mbH Sitz und Registergericht: Hamburg HRB 71 153
Geschäftsführer: Dr. Jens Bartenwerfer Michael Bathke Volker Sonnenburg
------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet.
This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Thanks! Is this issue on a public bug-tracker somewhere? -- Chris Maloney NIH/NLM/NCBI (Contractor) Building 45, 4AN36D-12 301-594-2842 "Tom Cleghorn" wrote:
Just chiming in with a third vote in support - we'd find it very handy to be able to slim down Oxygen's validation output for non-technical colleagues. Being able to use HTML to control it, as Octavian mentions, would be marvellous icing on the cake!
On 08/12/2015 09:36, Oxygen XML Editor Support (Octavian Nadolu) wrote:
Hello.
I added also your comment on the issue and I increased the its priority.
We have also other issue related to this, to render in <oXygen/> the HTML markup from the assert/report messages.
Best Regards, Octavian
Cambridge University Press is the publishing business of the University of Cambridge with VAT registered number GB 823 8476 09. Our principal office is at University Printing House, Shaftesbury Road, Cambridge, CB2 8BS, United Kingdom. _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hello, No, the issue tracker is not public. We scheduled the issue for the next <oXygen/> release version. We will notify you when this issue will be fixed. Best Regards, Octavian -- Octavian Nadolu <oXygen/> XML Editor http://www.oxygenxml.com On 08.12.2015 16:54, Maloney, Christopher (NIH/NLM/NCBI) [C] wrote:
Thanks! Is this issue on a public bug-tracker somewhere?
On 9/12/2015 6:18 pm, Oxygen XML Editor Support (Octavian Nadolu) wrote:
Hello,
No, the issue tracker is not public. We scheduled the issue for the next <oXygen/> release version. We will notify you when this issue will be fixed.
Is that the next build release, point release (if there is a 17.2) or major release? Regards, Ben
participants (6)
-
Ben McGinnes -
Dr. Patrik Stellmann -
Imsieke, Gerrit, le-tex -
Maloney, Christopher (NIH/NLM/NCBI) [C] -
Oxygen XML Editor Support (Octavian Nadolu) -
Tom Cleghorn