Oxygen XML Editor
The Premier All-In-One XML Editing Suite
Oxygen XML Author
Single-Source XML Authoring and Multi-Channel Publishing
Oxygen XML Developer
The Required Tools for Designing XML Schemas and Transformation Pipelines
Oxygen JSON Editor
The Perfect Tool to Simplify Your JSON Editing Experience
Oxygen Publishing Engine
The Complete DITA Publishing Solution for WebHelp and PDF Output
Oxygen PDF Chemistry
Chemistry Converts HTML and XML to PDF Using CSS
Oxygen XML WebHelp
Publish DITA and DocBook Content to WebHelp Output
Oxygen Styles Basket
Customize the Look and Feel of Your PDF and WebHelp Output
Oxygen XML Web Author
Engage Your Whole Organization In Content Creation
Oxygen Content Fusion
The Web-based Collaboration Platform to Craft Tomorrow's Content
Oxygen Feedback
Modern Commenting Platform
Cloud
Enterprise
Oxygen AI Positron
Enhance Your Productivity with the Power of AI
Oxygen Scripting
Automate and Run Oxygen Utilities from the Command-Line Interface
Oxygen SDK
Specifically designed for application developers and integrators
Shop
Pricing and licensing for businesses, Academic and individuals
This presentation is meant to explain the JSON languages and the support that you need when this type of documents are edited, validated, queried, or converted. You will also discover what languages and tools can be used when working with these types of documents. JSON it is a common format for data interchange and is adopted by applications as a way to store data. It is a self describing languages, the structure is defined hierarchically, and has schema to define its structure.
November 12, 09:15 - 10:00, Room C5.1
DITA is a great choice for writing technical documentation. Ideally, all contributors to a project should use it to provide content. But sometimes, subject matter experts (like developers, engineers) will prefer to give content in another format. We will explore what possibilities arise when this other format is Markdown, a good match for structured authoring cases in which a minimal markup is enough
We will explore various solutions like:
November 12, 11:45 - 12:30, Room C7.1
Schematron is a rule-based validation language. Has become an ISO standard since 2006 and it is a very popular language in the XML world. In the last few years, Schematron started to be used more and more and in numerous domains. In this tutorial you will learn how to create ISO Schematron schemas, how to use XPath to express your constraints, as well as how to validate your XML files using an ISO Schematron schema and create a report.
November 12, 16:15 - 18:00, Room C5.1
We will explore 3 collaboration scenarios: how to implement continuous improvement loops for d ocumentation, how to integrate documentation as part of product development, and how instant collaboration can take place, initiated by technical writers.
November 12, 16:15 - 17:00, Room C10.5
An exploration of how PDF can be generated from XML, HTML or even Markdown documents and customized simply by styling them with CSS. I will start with styling colors and fonts and end with multi-column layouts and page margin decoration.
November 12, 17:15 - 18:00, Room C10.5
A detailed look at Oxygen Feedback, an online comments managements system where you can interact with your audience. You will see how easy it is to deploy, various configuration options, and how to integrate it into a documentation review workflow.
November 13, 12:15 - 13:00, Room C10.5
I will start with similarities that users experience between using DITA and a word processor. Then, I will highlight unique features of DITA such as conditional content, variables, and table of contents customization.
November 13, 16:30 - 17:15, Room C10.5
I will discuss various aspects necessary to have a successful DITA project, including structure, version control, work-flow, an internal style guide, publishing, validation, ways to receive feedback from subject matter experts or end users, and more.
November 13, 17:30 - 18:15, Room C10.5
Schematron can be used to define rules for quality assurance and consistency in XML documents. I will show how reporting detected issues helps writers correct the problems, how to define various types of problems, and how to set different severities.
November 14, 10:00 - 10:45, Room C10.5
API documentation is usually automatically generated from source code or a specification. I will explore how to leverage DITA features to enrich it with tutorials and concept definitions, and to interlink it with the product documentation.
November 14, 11:15 - 12:00, Room C10.5
Tools and techniques used in software development can also be applied for documentation management: Storage and issue management using GitHub, Automated quality checks and continuous publishing using Travis CI, Editing and collaboration support.
November 14, 12:15 - 13:00, Room C10.5