Schematron validation restricted to cursor context
Are you missing a feature? Request its implementation here.
-
- Posts: 93
- Joined: Fri Mar 08, 2013 8:58 am
Schematron validation restricted to cursor context
Oftentimes I find myself editing files that are either very large or involve some complicated Schematron rules. Sometimes these rules give tips or aids in editing, and I have to wait a long time to get contextual help via SQF or Schematron-based messages, because the engine is checking the entire file.
I would find it very useful if oXygen had an option to restrict the checking of Schematron rules to only the context marked by the cursor or cursor selection. I am guessing that it would cut down minutes-long validation checks to fractions of seconds, and allow much faster, responsive editing of files. It would, I think, make SQFs much quicker to call and execute, no? Thoughts?
I would find it very useful if oXygen had an option to restrict the checking of Schematron rules to only the context marked by the cursor or cursor selection. I am guessing that it would cut down minutes-long validation checks to fractions of seconds, and allow much faster, responsive editing of files. It would, I think, make SQFs much quicker to call and execute, no? Thoughts?
-
- Posts: 388
- Joined: Thu Jul 01, 2004 12:29 pm
Re: Schematron validation restricted to cursor context
Hello,
It is an interesting idea, but you cannot run the Schematron or SQF just on a fragment because the you need entire context from the XML (namespace declarations, ancestors). A Schematron rule can also collect information from different parts of the document in order to be applied. And you need correct the problems locations after the Schematron is applied.
What I recommend you is to use smaller XML documents and maybe include them using XInclude. You can also analyze the Schematron rules to make them run faster.
Best Regards,
Octavian
It is an interesting idea, but you cannot run the Schematron or SQF just on a fragment because the you need entire context from the XML (namespace declarations, ancestors). A Schematron rule can also collect information from different parts of the document in order to be applied. And you need correct the problems locations after the Schematron is applied.
What I recommend you is to use smaller XML documents and maybe include them using XInclude. You can also analyze the Schematron rules to make them run faster.
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