24.08.2015 Views

Oxygen XML Author plugin 13.2.0

Oxygen XML Author plugin 13.2.0

Oxygen XML Author plugin 13.2.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Querying Documents | 316}if you drag the review element and drop it between the braces a popup menu will be displayed.Select FLWOR rating and the result document will be:XQuery ValidationWith <strong>Oxygen</strong> <strong>XML</strong> <strong>Author</strong> <strong>plugin</strong> you can validate your documents before using them in your transformation scenarios.The validation uses the Saxon 9.3.0.5 PE processor or the 9.3.0.5 EE, IBM DB2, eXist, Software AG Tamino, BerkeleyDB <strong>XML</strong> or Documentum xDb (X-Hive/DB) 10 if you installed them. Any other XQuery processor that offers an XQJAPI implementation can also be used. This is in conformance with the XQuery Working Draft. The processor is used intwo cases: validation of the expression and execution. Although the execution implies a validation, it is faster tosyntactically check the expression without executing it. The errors that occurred in the document are presented in themessages view at the bottom of editor window, with a full description message. As with all error messages, if you clickon one entry, the line where the error appeared is highlighted.Please note that if you choose a processor that doesn't support XQuery validation you will receive a warning when tryingto validate.Other XQuery Editing ActionsThe XQuery editor offers a reduced version of the popup menu available in the <strong>XML</strong> editor type:• the folding actions• the edit actions• a part of the source actions:• To lower case• To upper case• Capitalize lines• open actions:• Open file at Caret• Open file at Caret in System ApplicationTransforming <strong>XML</strong> Documents Using XQueryXQueries are very similar to the XSL stylesheets in the sense they are both capable of transforming an <strong>XML</strong> input intoanother format. You specify the input URL when you define the transformation scenario. The result can be saved andopened in the associated application. You can even run a FO processor on the output of an XQuery. The transformationscenarios may be shared between many XQuery files, are exported togheter with the XSLT scenarios and can be managedin the dialog Configure Transformation Scenario or in the Scenarios view. The transformation can be performed onthe <strong>XML</strong> document specified in the <strong>XML</strong> URL field, or, if this field is empty, the documents referred from the queryexpression. The parameters of XQuery transforms must be set in the Parameters dialog. Parameters that are in anamespace must be specified using the qualified name, for example a param parameter in thehttp://www.oxygenxml.com/ns namespace must be set with the name {http://www.oxygenxml.com/ns}param.The transformation uses one of the Saxon 9.3.0.5 HE, Saxon 9.3.0.5 PE, Saxon 9.3.0.5 EE processors, a databaseconnection or any XQuery processor that provides an XQJ API implementation.The Saxon 9.3.0.5 EE processor supports also XQuery 1.1 transformations. If the option Enable XQuery 1.1 supportis enabled Saxon EE runs the XQuery transformations as XQuery 1.1.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!