- oXygen-user - www.oxygenxml.com

[Ann] New maintenance build available for oXygen 25.1 (2023070306)
by Oxygen XML Editor Support (Adrian Buza) 04 Jul '23

04 Jul '23

Dear oXygen users, We announce the release of a new maintenance build (2023070306) for oXygen 25.1 (XML Editor, XML Developer, XML Author, XML WebHelp, PDF Chemistry, Publishing Engine). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2023070306 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support

1 0

[ANN] The new Oxygen AI Positron Assistant brings chat history, editable entries, user-defined actions, and more!
by Alin Belu 03 Jul '23

03 Jul '23

Hello everyone, We are thrilled to introduce you to the newest version of the *Oxygen AI Positron Assistant* add-on! Version 0.9.3 comes with several exciting features, including a *chat history* so you can revisit previous chats and continue where you left off, *editable user entries* in chat to modify conversations and explore different paths, the introduction of *user-defined actions*, and the possibility to *provide project-specific details for more accurate AI responses*. The *AI Positron Chat* now provides an overall improved experience with the addition of the *History* drop down toolbar button that allows you to go back to previous conversations and continue them. You can also*edit prompts* in the chat discussion thread so you can change the conversation and continue from any point if you want to explore a different path. Additionally, the AI response appears incrementally, as soon as the AI starts generating it, and you now have the option to stop the generation of a response early if you do not consider it fit for your needs. Version 0.9.3 also introduces *user-defined AI actions*. The same approach used for defining built-in actions can now be used to specify actions on the client side through the usage of a JSON configuration file. It may even be linked to a project, making it simple to share actions with everyone who works on a certain project. The newest version of the add-on comes with the possibility to provide *additional options for an action*. To avoid creating too many related actions, it is now possible to specify different facets for an action that the user can choose. This can be best seen in the action that generates short descriptions, as it uses this customization to allow users in choosing different writing styles, such as clear or engaging, as well as setting the number of expected sentences that will be generated. The Oxygen AI Positron Assistant now enables you to *configure a context for all prompts* in the AI Positron Assistant Preferences page. This can be set to be project specific and it allows you to pass certain information to all the built-in actions, so that the AI model will generate better and more relevant results, as it becomes more knowledgeable about your context. It is also worth mentioning that the AI Positron *activity messages have been integrated into the AI Chat view* for a more streamlined and consolidated user experience, thus making the AI Activity View not needed anymore. For additional information on the *Oxygen AI Positron Assistant*, including the installation instructions, you can check out this article on the Oxygen XML Blog: https://blog.oxygenxml.com/topics/ai_positron.html For an in-depth presentation of the various features and use cases for the *Oxygen AI Positron Assistant*, you can view the recent recording of the *AI as a Tool for Technical Content Creation* webinar - https://oxygenxml.com/evs2023-7.html We want to remind you that we plan to frequently release new features and improvements, so please let us know what you think about the current version and stay tuned for exciting new versions of this add-on! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] Webinar: Leveraging the Power of AI and Schematron for Content Verification and Correction (July 5, 2023)
by Alin Belu 29 Jun '23

29 Jun '23

Hello, Your journey into the world of AI continues next week, on the *5th of July*, with the *Leveraging the Power of AI and Schematron for Content Verification and Correction* webinar! During this 1-hour live event, Octavian Nadolu (project manager at Syncro Soft) will be exploring the application of AI in conjunction with Schematron and Schematron Quick Fix (SQF) for content verification and correction. He will begin with a comprehensive overview of AI before going on to highlight the potential advantages it brings and shed light on the challenges we may encounter when utilizing AI for these purposes. Don't miss this opportunity to gain valuable insights into the intersection of AI and content validation by exploring topics such as: * Artificial Intelligence (AI) * OpenAI/Generative Pre-trained Transformer * Schematron and Schematron Quick Fixes (SQF) * Implementing AI in Schematron and SQF * Examples of AI-driven Schematron and SQF Solutions * Benefits of Using AI in Schematron and SQF This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2023-8.html To stay in touch with us and discover what other events we have planned for you, please make sure to check https://www.oxygenxml.com/events_programme.html Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

Why is the JSON Schema $anchor not supported?
by Roger L Costello 22 Jun '23

22 Jun '23

When I add "$anchor" to my JSON Schema, the Oxygen editor gives this error message: The keyword "$anchor" is not part of JSON Schema Draft 2020-12 specification. Therefore, it is ignored by the validation engine. But that's not true. See section 8.2.2 of the 2020-12 specification (https://json-schema.org/draft/2020-12/json-schema-core.html#section-8.2.2) Using JSON Pointer fragments requires knowledge of the structure of the schema. When writing schema documents with the intention to provide re-usable schemas, it may be preferable to use a plain name fragment that is not tied to any particular structural location. This allows a subschema to be relocated without requiring JSON Pointer references to be updated. The "$anchor" and "$dynamicAnchor" keywords are used to specify such fragments. They are identifier keywords that can only be used to create plain name fragments, rather than absolute URIs as seen with "$id"...

1 0

[ANN] Webinar: AI as a Tool for Technical Content Creation (June 28, 2023)
by Alin Belu 15 Jun '23

15 Jun '23

Hello, On the *28th of June*, we invite you to join us for one of the most anticipated Oxygen XML live events - the *AI as a Tool for Technical Content Creation* webinar! In recent months, AI technology has advanced to the point where it is now applicable in a wide range of real-world situations. However, the AI-generated content is not always accurate, making it challenging to introduce this technology to end users. On the other hand, this is precisely why technical writers are an excellent fit for AI since they can serve as mediators between the AI and the end users, using it to boost their productivity while ensuring the content that they deliver is accurate. *Oxygen AI Positron Assistant* is a new plugin for the Oxygen XML tools that connects to the Open AI Chat GPT engine, introducing AI technology for supporting technical writing operations. To keep authors in control, the workflows are optimized to include preview of proposed AI changes and the possibility to refine the results. Custom AI interactions are also possible, and you can easily reuse them with support to save them as favorites. During this 1-hour live webinar, Sorin Carbunaru (senior software developer at Syncro Soft) will: * Show various use cases for the *Oxygen AI Positron Assistant*. * Explore the available actions and show how they can be invoked, refined, and the results previewed in the visual diff to analyze the document changes. * Demonstrate how you can define your own AI processing actions and mark them as favorites. * Highlight the tasks best suited for AI technology use. This is a free event, but registration is required. You can register at https://oxygenxml.com/evs2023-7.html To stay in touch with us and discover what other events we have planned for you, please make sure to check https://www.oxygenxml.com/events_programme.html Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] New release of Oxygen AI Positron Assistant brings chat, preview, new actions, and more
by Alin Belu 29 May '23

29 May '23

Hello everyone, We are excited to announce a new release for the *Oxygen AI Positron Assistant* add-on! Version 0.9.2 comes with a variety of exciting new features, including chat functionality, the ability to preview changes, AI-based quick fixes, AI-based XPath extension functions, and new AI actions for grammar corrections, content rewriting, and checking how your content responds to specific questions. The *AI Positron Chat* side-view provides a better user experience and more control when invoking AI actions, allowing you to see the response and preview its impact on the document using an action that triggers the visual XML-aware comparison. You can also further refine the responses by continuing the discussion with the *AI Positron* platform in the chat view. In a chat message, you can use editor variables that expand to the selected content or the entire document. These allow you to define flexible prompts, and the support to save favorites enables you to store and easily reuse the prompts you find useful. Along with the preview action for the AI responses, you can also use actions to insert the response into your document or copy the response to the system clipboard. Version 0.9.2 of the add-on improves the existing actions and contributes new AI actions: * *Correct Grammar* - Corrects the grammar and spelling of the selected content. * *Use Active Voice* - Converts the selected content from passive voice to active voice. * *Generate Questions* - Displays possible questions that the selected content or the entire document responds to. * *Answer Questions* - Displays AI responses to your questions found in either the selected content or the entire document. The add-on now also helps you with validation problems. If an error message provides a good description of the identified problem and eventually a hint on how to fix it, which is typically the case with Schematron errors, then you can take advantage of the *AI Positron Fix* quick-fix action that tries to find a solution to the validation problem. This action can be triggered from the contextual menu for the validation problems that are displayed in the application's Problems list. The add-on now also contributes two *XPath extension functions* that can be used from XSLT stylesheets, XQuery scripts, and from Schematron schemas to process content or to perform validation checks on existing content. Custom XML refactoring operations (based on XSLT or XQuery) can also take advantage of these AI functions, so you can apply batch processing on multiple documents. For additional information on the *Oxygen AI Positron Assistant* add-on, including the installation instructions, you can check out this article on the Oxygen XML Blog: https://blog.oxygenxml.com/topics/ai_positron.html We want to remind you that we plan to frequently release new features and improvements, so please let us know what you think of the current version and stay tuned for exciting new versions of this add-on! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

[ANN] OpenAPI Documentation add-on version 2.2.0 is now available!
by Alin Belu 26 May '23

26 May '23

Hello everyone, We are excited to announce the release of *version 2.2.0* for the *OpenAPI Documentation add-on*! *Version 2.2.0* sees the implementation of useful upgrades, such as: * The addition of an option to transform the OpenAPI content into DITA output. * The "examples" element is now rendered when transforming to HTML output. * A detailed warning message is now displayed when the transformation’s target file has unsaved changes. For more information regarding the OpenAPI Documentation add-on, check out the following page from our documentation: https://www.oxygenxml.com/doc/versions/25.1/ug-editor/topics/openapi-docume… We hope you will find the newest version of our add-on useful and as always, your feedback is welcome! Best regards, Alin -- Alin Belu Oxygen XML Editor

1 0

VBA to XSLT function conversion
by Sudhakara Allam 26 May '23

26 May '23

Hi, I am trying to convert xslt with msxls vbscript generated out of MS Access application to xslt only file by converting VBScript functions to xslt native functions. Does Oxygen have this functionality? It may not have to be automated, however, beneficial if it could. Please let me know. Regards, Sudhakar

1 0

Schematron doesn't respect the full path in the test attribute.
by Danny MacMillan 18 May '23

18 May '23

Hello, Consider the following XML: <?xml version="1.0"?> <root> <relevant> <element relevant-attribute="this attribute exists only on elements under relevant"/> </relevant> <irrelevant> <element/> </irrelevant> </root> And the following Schematron: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt3" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:map="http://www.w3.org/2005/xpath-functions/map"> <ns prefix="map" uri="http://www.w3.org/2005/xpath-functions/map"/> <let name="some-map" value="map {}"/> <pattern> <rule context="/*/relevant/element[map:contains($some-map, @relevant-attribute)]"> <assert test="true()">Impossible</assert> </rule> </pattern> </schema> When I validate the XML with the Schematron, Oxygen prints a warning that an empty sequence is not allowed as the second argument to map:contains, which I've determined is because it is testing the "element" elements under "irrelevant". I know this because if I add a second such element, the error prints twice. If I have 9, the error prints 9 times. But why is it testing that element? I deliberately used xpath that navigates via the parent because I want to include only elements under that parent, but it seems that it's looking at all elements, anywhere in the document, named 'element'. Is this expected? I can silence the warning if I explicitly check for the presence of the attribute: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt3" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:map="http://www.w3.org/2005/xpath-functions/map"> <ns prefix="map" uri="http://www.w3.org/2005/xpath-functions/map"/> <let name="some-map" value="map {}"/> <pattern> <rule context="/*/relevant/element[@relevant-attribute and map:contains($some-map, @relevant-attribute)]"> <assert test="true()">Impossible</assert> </rule> </pattern> </schema> But not if I precede the broken rule with a rule that should equivalently prevent the broken rule from firing on those elements: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt3" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:map="http://www.w3.org/2005/xpath-functions/map"> <ns prefix="map" uri="http://www.w3.org/2005/xpath-functions/map"/> <let name="some-map" value="map {}"/> <pattern> <rule context="/*/relevant/element[not(@relevant-attribute)]"> <assert test="true()">Impossible</assert> </rule> <rule context="/*/relevant/element[map:contains($some-map, @relevant-attribute)]"> <assert test="true()">Impossible</assert> </rule> </pattern> </schema> Thanks, -- Danny MacMillan Sent with [Proton Mail](https://proton.me/) secure email.

3 4

Schematron validation of documents using XInclude succeeds when it should fail.
by Danny MacMillan 12 May '23

12 May '23

Hello, I'm going through the Schematron book by Erik Siegel and one of his examples improperly passes validation in Oxygen XML while it correctly fails validation using SchXslt. The code for the book is here: [https://github.com/xatapult/schematron-book-code](https://github.com/xatapu… I open both examples/additional-features/subdocuments-1.sch and data/subdocuments-master.xml from that project in Oxygen and select the tab with the XML file. Then I click the dropdown on the Validation button on the toolbar and click Validate with... and then I select the subdocuments-1.sch file using the dropdown. When I proceed Oxygen says it passes. This is the same approach I have used for all other examples in the book. But I created an explicit validation scenario for this also and it behaves the same way. Note that if you want to test this you should clone the repository because the subdocuments-master.xml file incorporates other files in the repository by reference using XInclude and this is indeed what seems not to be working in Oxygen. By contrast if I run the same validation using the schxslt-cli.jar I get the following, expected result. [invalid] /home/user/task/schematron-book-code/data/subdocuments-master.xml [invalid] /home/user/task/schematron-book-code/data/subdocuments-master.xml failed-assert /Q{}document[1]/Q{}p[1] The class brightred is forbidden (file:/home/user/task/schematron-book-code/data/subdocuments-2.xml)! I am using the latest Oxygen: <oXygen/> XML Editor 25.1, build 2023042509 Thanks, -- Danny MacMillan Sent with [Proton Mail](https://proton.me/) secure email.

3 4