oXygen XML Editor provides support for working with projects, allowing you to organize your files so you can easily access resources relevant to a project. More than this, oXygen projects give you batch operations that can be performed on all or selected resources and most of the options can be set at the project level, thus facilitating sharing them with your team.
In this webinar we explore DITA 1.3 functionality and how oXygen XML Editor supports you to take advantage of the new DITA 1.3 features.
In this webinar we explore DITA publishing options from oXygen XML Editor including different HTML formats, PDF, EPUB, etc. and how these can be customized.
This webinar focuses on introductory concepts of working with DITA documents in oXygen XML Editor, covering everything from creating DITA maps and topics from scratch to basic publishing using out-of-the-box scenarios. You will also learn how to edit simple topics, create cross references, insert images and tables and how to benefit from intelligent features such as smart paste and validate, and check for completeness.
When editing documents there are various rules that you want your content authors to follow, such as grammar rules, document structure guidelines, business requirements, style preferences, or rules for the generated output. To enforce these rules, companies often use grammar checking apps, custom schemas or best practice guides. For content authors, there are usually too many rules to remember them all when writing content. The best approach for this challenge is to signal the user when a rule violation is detected and offer suggestions to help them solve possible rule problems and maintain integrity in their documentation.
This webinar focuses on advanced features that justify the return of investment you get from using DITA. REUSE is the key word and it can be implemented either directly through content references or indirectly through profiling/conditional content.
Schematron solves certain limitations that other types of schema have when validating XML documents since it allows the schema developer to define the errors and control the messages that are presented to the user. Therefore, Schematron makes the validation errors more accessible to users and helps to ensures that they understand the problem. These messages may also include hints to help the user to fix the problem, but this doesn't complete the solution since the user still needs to manually correct the issue. This may cause users to waste valuable time and also creates the possibility of making additional errors while trying to manually fix the reported problem. Schematron Quick Fixes provide automatic actions to fix validation errors, thus offering a complete solution, while saving time and avoiding the potential for causing other issues.
oXygen XML Editor version 17 sets the highest standard for XML development and XML authoring. It comes with important functionality updates and focuses on design to make your work not only productive, but also enjoyable.
oXygen XML Editor version 17 focuses on design to make your work not only productive, but also enjoyable.
The new user interface features Retina/HiDPI icons to make everything look crisp and beautiful, and an optional graphite color theme. Also, the toolbars are configurable down to action level, giving you full control of your work environment.
It is important to have documents without errors, but not all users know how to fix the errors from the documents. Even if they do know, ideally they should use a quick and automated solution.
oXygen does not only report errors, it also helps you correct them automatically through the Quick Fix support, which provides automatic fixes for XML documents validated against XSD, Relax NG, and Schematron schemas. In the case of Schematron, the schema developer takes full control over the Quick Fix actions, being able to offer custom solutions to any detected issue using the Schematron Quick Fix language.
The webinar includes:
The XML Refactoring tool helps you change the structure of your XML documents.
It offers a wide variety of operations, such as renaming, deleting, and inserting elements and attributes. If the provided operations are not enough, you can create custom refactoring operations and share them with other team members. All of them are available through a friendly user interface and can be applied across a set of multiple files.
This presentation is structured in two parts:
oXygen XML Editor 17 comes with many new additions to the DITA support.
Topics and maps offer a choice of main rendering styles, as well as the option to add or subtract style layers. Guided DITA authoring was implemented as two optional style layers that allow you to see inline hints and actions. The CSS-based PDF transformation automatically uses the CSS styles you select for authoring, so that you can reuse the same CSS files when publishing DITA to PDF. Both DITA-OT 1.8 and 2.0 are supported and integrating a new transformation is greatly simplified for annotated transformation types, as oXygen will automatically discover their parameters.
The DITA to WebHelp transformation optimizes the page loading time and provides context-sensitive help support, SEO resources, and LDAP authentication. The WebHelp output that now supports both RTL scripts and Japanese content can be easily embedded in a page.
This webinar presents the XSLT Quick Fixes functionality in detail and then describes some of the other important features in oXygen.
oXygen excels in offering support for XSLT technology. This webinar covers XSLT development in oXygen.
oXygen excels in offering support for XSLT technology. This webinar covers XSLT development in oXygen.
oXygen excels in offering support for XSLT technology. This webinar covers XSLT development in oXygen.
In an ideal world, all documentation content would come in one format (and that format should be DITA). But let's face it, content produced in most companies is diverse and comes in many forms and sizes.
So, how can we single source everything? Can we integrate contributors who use formats such as language-specific API documentation, HTML, Markdown, or even Excel spreadsheets or database tables in a DITA-based workflow? Could we convert everything to DITA on the fly? Could we use a magic glass to perceive various data sources as DITA?
We may try to convince everybody to produce DITA content but this may not be always possible. Instead, we can accept these diverse data formats but look at them as different ways of encoding DITA. So, if we put the right decoder in place we will obtain our DITA content.
This webinar focuses on introductory concepts of working with DITA documents in oXygen, covering subjects such as creating DITA maps and topics from scratch, as well as basic publishing using out-of-the-box scenarios. You will also learn how to edit simple topics, create cross references, insert images and tables, and how to benefit from intelligent features such as smart paste, validate, and check for completeness.
This webinar focuses on advanced features that justify the return on investment you get from using DITA. RE-USE is the key word and can be implemented either directly through content references or indirectly through profiling/conditional content. We will also explore publishing by showing how you can change transformation parameters and how you can obtain multiple output formats from DITA.
In this webinar, we present the Profiling Styles functionality in detail and then go through some of the other important features in oXygen.
People are usually afraid of using XML authoring because they perceive this to be a lot more complicated than using non-structured documentation, such as a word processing application. The authoring support for XML has been continuously improved in oXygen and provides user-friendly interfaces, allowing less experienced users to work with XML. These interfaces are a lot easier to use than word processors. In this webinar, we will show a few examples of how oXygen can make XML editing accessible to everyone, and how you can provide similar user interfaces to edit your own XML formats.
Structured content is considered fundamental to content strategy and an organization's ability to deliver content where it is needed across a wide variety of devices and media. However, in the past, authoring structured content has been quite challenging. Coding raw XML and WYSIWYG authoring is not feasible for most authors. Starting with version 14, oXygen introduced form controls as a new approach to authoring, hiding the complexity of XML without obscuring the structure we are trying to capture or creating hard-to-understand errors.
For this webinar, oXygen invited Mark Baker, owner of Analecta Communications and consultant in structured authoring and topic-based writing, to explore a business case for forms-based structured authoring.
When collaboratively working on documents, support for reviewing is a must have. oXygen provides advanced reviewing capabilities, including change tracking, annotations/comments, and highlights that work automatically with any XML vocabulary. There are also visual tools to allow you easily see and manage changes and comments in order to get the final reviewed document. This webinar will present the reviewing functionality and how you can take advantage of it in your XML documents.
The XML Schema version 1.1 adds numerous features that improve the usability of the XML Schema standard. These features include assertions, conditional type assignments, open content, override support, default attributes, negative wildcards, substitution for multiple elements, and more. This webinar presents an overview of these XML Schema features, how they work on simple examples, and how you can use them in oXygen. This is a great opportunity to discover what XML Schema 1.1 makes possible, as well as how easy it is to develop schemas with oXygen.
"Componize Author" brings together best-of-breed Componize DITA CMS and oXygen into an end-to-end web-based collaborative solution.
With “Componize Author”, you can enforce processes, information models, and content control with:
oXygen users already know that XML makes your content flexible. XML allows you to assemble your content for different types of customers and publish it to all the devices they use. Also, users of the content optimization software of Acrolinx already know that by guiding your authors to use simple and clear language, you can create content that your customers will appreciate. In this webinar, you will see how you can do both through a consistent, powerful, and productive user experience.
While tools can be used to simplify many things, localization can still be scary. In this session, we'll go over how the toolkit is set up to handle publishing in multiple languages: what comes out of the box? What should you expect to do on your own? And how has this changed over the last few releases? Also: stories of panic from the past!
This session shows 7 DITA Open Toolkit open source plugins that the developers of Oxygen XML have created or updated this year including:
The internals of DITA-OT are in perpetual motion and most of these changes are not visible to end users. In this talk we go through changes in the black box and describe future development plans.
Now it is very easy to contribute to the DITA-OT documentation - just read the developer docs and use the "Edit" button to open the source topic from GitHub for editing. Save will automate all the contribution process, sending a pull request with your proposed changes.
This talk provides an overview of recent changes to the DITA-OT documentation, points out open issues, highlights ideas for future improvements, and closes with room for suggestions from the community, a call for contributions and a brief demonstration of the pull request approval process that is applied when people submit changes to the development documentation via the /Edit this Page/ links.
There are some significant changes to DITA OT 2.x that can make upgrading PDF plugins written for earlier versions of the OT a challenge. Having just upgraded several plugins, and released a new edition of "DITA For Print," Leigh will share a few of the major things to look out for.
Docker containers make it easy to package and use different configurations of software components. Docker containers can also provide the dependencies needed to run a given piece of software. For the Open Toolkit, you can use Docker containers to easily provision and run the Open Toolkit without worrying about the local Java configuration or other dependencies. Docker also makes it easy to set up custom configurations of the Open Toolkit or use different versions. This presentation shows how to use Docker-based Open Toolkit packages.
This presentation will show how SAP has integrated the DITA Open Toolkit to create a large scale production infrastructure able to create daily builds producing 50 000+ outputs for all SAP Product documentation. This covers the end-to-end process from getting the DITA content from the CMS to publishing the produced outputs to the appropriate delivery channels, using so-called project maps as a key ingredient. Advanced features like peer linking across outputs will be shown, as part of the overall implementation.
Jarno and Robert will discuss how the DITA-OT is tested, get feedback and talk about where we want to go.
Fixing errors during authoring stage is cheap in both technical communication and software development; fixing errors after publishing is expensive. In this talk I demonstrate a QA method for software documentation in DITA.
I'd like to present how we manage and check terminology using the org.doctales.terminology plugin..
A DITA to simplified/resolved DITA transformation provides a solution for some of the possible issues with translating DITA. There are also other advantages, especially in connection to the increased dynamics in DITA-OT development. Join me to discover how a DITA to resolved DITA can help you!
Kris and Robert will discuss the long term future of DITA-OT: what can we all do to ensure the continued health of this critical piece of the overall DITA infrastructure?
Based on the oXygen XML WebApp technology introduced 2 years ago at XML Prague, Syncro Soft releases a new product, oXygen XML Web Author, that provides browser based XML authoring support. This is a web application that comes with connectors for GitHub, and SharePoint while additional connectors can be plugged in and easily configured.
Different types of users working with different XML vocabularies imply different authoring needs. Having this in mind, Oxygen 17.1 provides the means to tailor the authoring environment for specific needs by supporting a new range of CSS properties. We will go through some of these properties and we will present scenarios in which they are helpful. We will also go over another mechanism in Oxygen, designed to help with structure insertion and to keep the document valid. We will quickly remind you of this “smart editing” feature, how you can extend it even further and present what we've improved in the upcoming oXygen version 18.
Due to the feedback that we received from our users, oXygen has continued to improve the support for Schematron and Schematron QuickFix (SQF). You can use XSLT 3.0 in Schematron schemas and as well as multilingual messages. oXygen extended the SQF support for resolving errors in documents other than the current one and allows the users to specify values to be used when executing a fix.
The content completion support in Oxygen is driven by the schema but there are cases in which these values come from an external data source or the schema can't be altered. To handle these situations, in Oxygen 18.0, we've added support for a configuration file that allows not only to specify attribute/element values but also to restrict the elements and their children.
Oxygen version 17.0 and 17.1 focused a lot on design to make a more intuitive and enjoyable working environment. We will cover the new Color Themes and User-defined themes, the customizable toolbars and the HiDPI and Retina support.
Applying line based diff algorithms for detecting the changes in XML documents when a versioning system is used is not ideal, as these algorithms ignore the XML structure and thus they present a lot more changes than the actual XML changes. A three-way XML-aware comparison of documents solves this problem. This is one of the core functionality we have been working on during the last months and which we hope to make generally available in the next oXygen version. Another interesting aspect is the possibility to compare documents in the Author visual editing mode instead of the Text editing mode - this is another area that we explored and we want to share the results with you.
DITA-SEMIA is a set of open-source tools that support information architects creating specialized, semantic DITA frameworks. The plugins integrate well with the oXygen XML editor and DITA-OT to support both authoring and publishing. The session will give an overview of the features currently available and planned for the near future.
Meet oXygen developers and see what is planned for the future. Ask any question and we will be happy to respond. Share your feedback with us and with the other oXygen users!
The support that Oxygen provides for XML vocabularies can be customized to match various audiences' requirements through an extensive array of extension points. To facilitate such customizations, we provide a start-up project that contains samples for every major type of extension.
In this workshop we will present:
What's new in DITA-OT? We'll cover major changes in both 2.1 and 2.2, with a focus on support for new DITA 1.3 features.
What might often seem like a good way to use or extend DITA-OT, but likely result in trouble later? What is the alternative? This session will cover known traps that organizations have fallen into when using DITA-OT, and suggest how to avoid those issues or (perhaps with difficulty) recover from the mistakes. The session will leave time for discussion about other traps that audience members may have fallen into.
The startcmd batch script made it possible for many to easily use DITA-OT, but whether you realize it or not, it's no longer really necessary. I'll briefly explain where it came from, why it was always more of a kludge than a Feature, and how better DITA-OT designs mean it's no longer needed.
This talk introduces Jarno Elovirta’s DITA-OT Markdown plugins, which extend the DITA Open Toolkit so you can use Markdown files directly in topic references and export existing DITA content in Markdown format for use in other publishing systems. This makes it easier for people to contribute content to DITA publications, enables mobile authoring workflows, facilitates review processes with less technical audiences and expands the range of publishing options to workflows based on Markdown.
Presenting new updates made to the DITA OT plugin which can now be used to generate PDF from DITA and CSS using either Prince XML or Antenna House.
When creating a product, a good design is critical; in many cases, this rule applies not only to the outside, but also to the parts inside that normal users will not see. Unfortunately, to those who looked, the inner workings of the early toolkit seemed to have almost no design at all. In this session, we'll talk about how Jarno has cleaned up the hidden inner workings of the toolkit -- and how everyone benefits from these changes to things they might never see.
Professional writing can require several features that the present DITA-OT (2.1.1) has not implemented. There are several expensive plugins available as commercial products to improve that situation. Helmut Scherzer presents a match to highly professional DITA-OT extensions which contains a list of more than 20 new powerful features to PDF2 – offered to become part of the public DITA-OT.
The DITA Community GitHub organization serves as a general place for people to contribute DITA Open Toolkit plugins and other DITA-related tools and utilities that are not maintained by DITA-OT or other projects. This presentation provides an overview of the DITA Community organization, what's there today, and how you can contribute.
This presentation will address the problem of creating DITA constraints/specialisations to customize DITA to meet your specific needs. We will identify a problem, create a Relax NG constraint/specialization to solve it and convert that to DTD. All these will be packaged as a DITA-OT plugin.
There are multiples ways to run DITA-OT and some of them are good, some are bad, and some are just plain ugly. This presentation goes through different interfaces to DITA-OT and when to use them.
Each DITA-OT plugin provides a set of parameters that can be configured to customize the publishing process. As these need to be made available to users it is important to have an automated way of discovering these parameters and additional information about them - what they represent, what values are possible, etc. DITA-OT makes this possible by allowing parameters to be annotated.
Publishing from a CMS imposes specific requirements on the DITA-OT. We will review these requirements while showing how IXIASOFT integrated the DITA-OT into their Output Generator.
Over a couple of years, the Gnostyx team has been preparing and refining a DITA Demonstration Data Set. It's purpose is to provide members of the community a functionally realistic data set with which to demonstrate DITA based applications. It was made available publicly in early 2015 and has since been adopted and used by several members of the DITA Community. This talk is really a demonstration of some of the business use cases that we use to convince business stakeholders that DITA demands serious attention. People will learn a little about the DITA Demonstration Data Set and some of the sales pitches that they might want to use, and to demonstrate, in the future.
If you need to maintain multiple configurations of the OT for day-to-day or minute-by-minute changes to the OT for different projects, clients, etc., you can use git to do it. There are some tricks and gotchas but it does work.
This talk provides an overview of recent changes to the DITA-OT documentation, points out open issues, highlights ideas for future improvements, and closes with room for suggestions from the community and a call for contributions.
Discover the new functionality added in version 17 and how that helps you.
Learn how to create XML authoring interfaces that take advantage of the new functionality added in oXygen 17 - functionality that allows defining custom actions in CSS and to place them directly within the document on different layers as well as using the new HTML content form that can bring hints as static content inside the document. See how this was used to provide enhanced DITA editing support, a nice editor for Saxon configuration files and ISO StratML editing.
When a problem is identified in a set of documents it may occur multiple times, sometimes thousands of times. In order to fix such problems we need a way to change those documents in a controlled way and we can do that with XSLT and XQuery but we need to keep as much as possible the same serialization and formatting of the documents and this is a little challenging. Alex will present the new refactoring support that allows to apply XSLT and XQuery updates on documents while trying to preserve their initial content. This can be used through a simple UI built on top of available scripts to allow also casual users to take advantage of available refactoring actions.
Identifying an error is only the first step in correcting a document - you need also to understand the problem and perform the actions to fix it. Quick fixes offer a choice of possible actions that will fix a reported problem automatically. See how oXygen implemented quick fixes for XSLT and XML documents and discover Schematron Quick Fixes - a language that allows you to define your own quick fix actions.
Web based authoring was presented at XML London last year on mobile devices. See how this evolved and a few sample applications of this technology that make XML authoring and review accessible across platforms and devices.
DeltaXML provide a quick and simple way to run their change management tools from within oXygen using a plugin Add-on. Tristan Mitchell will give an overview of the functionality provided in the Add-on and the oXygen features it relies on, and will demonstrate how easy it is to identify and publish changes without leaving the oXygen interface.
Oxygen XML provides systems integrators with the APIs they need to integrate directly into 3rd party content management platforms. This presentation shows how Mekon have made use of these APIs to provide an editing and system administration front end to their content delivery platform, DITAweb.
Identifying an error is only the first step in correcting a document. You also need to understand the problem and perform actions to fix it. Quick Fixes offer a choice of possible actions that will automatically fix a reported problem. See how oXygen implemented Quick Fixes for XSLT and XML documents and discover Schematron Quick Fixes (a language that allows you to define your own quick fix actions).
Every company has a best practices guide, but it's impossible to learn it, by heart, before starting to write. The best approach for this challenge is to dynamically provide hints, based on the context in which the user is working. The document becomes the entire interface and guides the user through the authoring process. Alex will show you how to achieve this goal by using features that are already available, as well as a few new ones that are coming in version 17.0.
Web-based authoring was presented at XML Prague last year on mobile devices. See how this has evolved, along with a few sample applications of this technology that makes XML authoring and review accessible across platforms and devices.
Are you new to the DITA-OT? Come and get an overview of what it is, how it works, its history, and the people involved. This will be an excellent start to DITA-OT day for novices.
Participate in a deeper, more technical dive with the primary DITA-OT developer. This session will cover the pre-processing architecture of the DITA-OT and information about the output transformations.
Now that the toolkit is hosted on GitHub, it's easier than ever to contribute changes to the DITA-OT code. Roger will demonstrate how to fork the repository, create a new branch, change the necessary files and submit a pull request.
The new version of DITA, version 1.3, will use Relax NG as the normative grammar to express the DITA content models. George proposed this idea and provided a working prototype under the DITA-NG open source project and Eliot took this further making it an official proposal for DITA 1.3 and finalized its implementation. See how Relax NG simplifies the way DITA content models and specializations are defined and what other benefits it brings to DITA 1.3.
DITA-OT includes extension points that let you do any number of things. This session will cover what's available, what you should or shouldn't extend, and give out sample plugins to slice and dice your content.
The dita2rdf plugin is meant to extract metadata from DITA content and produce an RDF/XML output, which is a serialization of the W3C RDF standard. The final objective is to get insights from the DITA content by querying its metadata as a graph, not as a tree-like in XML. It also potentially enables the connection of the DITA metadata with other types of entities such as products, people, events, etc.
With a few simple changes, it's possible to give the DITA-OT's default PDF output much of your own look and feel. If you need to develop a DITA proof of concept for your organization, these changes might be all you need to get the ball rolling. Join Leigh to find out what's easy to do, what's not quite so easy to do, and where the real heavy lifting is.
Did you know that you can create customized PDF plugins using an easy online tool? Join Jarno for an overview of his plugin generator, what it produces, and his work developing the dynamic Web interface.
How about producing and styling PDFs only by using CSS? Join Radu for an overview of a new, innovative, open-source DITA-OT plugin, which produces PDF from DITA content using CSS and an XML+CSS to PDF engine such as the Prince XML or Antenna House engines.
On the example of ice hockey rule books, we show how easy content can be re-used by creating new context variants and how it can be published to EPUB or into an Eclipse help infocenter.
Alin presents a newly introduced set of actions, available for highlighted content and designed to assist the user in quickly solving time consuming repetitive tasks such as fixing XML structure errors, renaming multiple occurrences of an attribute or even correcting misspelled words.
XML tools usually support editing with different helpers, taking advantage of the schema information. What happens when there is no schema, how can a tool assist users to create XML content in the absence of a schema or a DTD? Let's discover what support oXygen offers that does not look into a schema but into the document itself.
oXygen does not provide yet support for Saxon-CE but Radu will show you that there are some things you can do to be able to develop XSLT stylesheets for Saxon-CE.
A quick demo about how to use the 'vc:minVersion' and 'vc:maxVersion' attributes for XML Schema. oXygen automatically detects the version set for the current XML Schema document, and configures the validation and the Content Completion Assistant accordingly.
The support for developing Schematron schemas was improved a lot in the last release of oXygen to include enhanced validation of the Schematron schema, search and refactoring actions. See what is new on developing Schematron in oXygen.
What if some values in the XML document are contained by an external data source? Alex will show you how you can configure oXygen to assist the user to select values defined outside the XML document, in external data sources.
See how you can use oXygen to import existing data from relational databases, Excel sheets or text file (CSV files, tab separated values, etc.) as XML, so you can process that further with XML tools.
We will demo how to turn oXygen into a text analysis tool. The demo is based on freely available automatic text analysis Web services and the oXygen customization facilities. The DocBook 5.0 type has been adapted to allow automatic annotations of entities, while preserving the original DocBook markup. Use cases are, for example, disambiguation of named entities to ease localization of content
The main goal while working for the digitisation of the Romanian Academic Dictionary was to provide an easy way to create dictionary entries while using oXygen, along with reducing the information entered manually, as this can lead to human errors.
For this, they adopted the Author editing mode that allows a fast and easy way of styling the XML using CSS. By using CSS extensions authors can use text boxes, text area, combo boxes to edit XML data, buttons to trigger specific actions, as well as other various in-house developed components.
See how you can work with DocBook modules, referenced through XInclude or as external entities, taking advantage of the Master Files support.
Copy/paste is a simple way of exchanging information between applications and implementing this intelligently allows to automatically convert from spreadsheet formats to XML and back, from different office applications to specific XML formats and to get nicely coloured XML code in your email.
Is it possible to get people that are not familiar with XML to create XML content? The answer is yes, but some work is needed to provide them a customized user interface that is tuned to use the concepts they are familiar with and that makes the editing easier. Alex will show you how such user-friendly XML authoring interfaces look like.
When you create XML content you may need to reference some other information from your current project but you do not know where exactly that information is. If you work on a project together with your colleagues and some of them annotated some files, how can you find those annotations to look over them? The advanced search for resources provides the answer to these questions and more.
oXygen supports user-defined pseudo-classes in CSS and these can be used to create a better user experience when editing XML documents. Alex will show you some examples of using this new functionality.
Watch the exclusive preview of the oXygen XML web/mobile editing platform