DITA (Darwin Information Typing Architecture) is an XML-based architecture for authoring, producing, and delivering information. Publishers are starting to take DITA seriously. And if they aren’t, they should be. This panel session will introduce DITA for publishers, the basic publishing-specific DITA components that are completely generic, and how DITA can really be the tool-set that launches publishers into the XML world.
In this free webinar DITA guru and contributor to the DITA specification, Eliot Kimber, senior solutions architect at Really Strategies, will present DITA for Publishers and provide details about his new community-based, open-source project: DITA For Publishers (dita4publishers.sourceforge.net).
With so many publishing tools on the market how do you select what’s right for you? You know you need a content management system but do you also need a digital asset management system? XML is touted as the game changer to facilitate content re-use but what’s the best approach to create it? And at the end of the day, you still need to publish a physical product as well as an ebook, web content, mobile apps, and more.
This document discusses a case study of implementing a DITA-based HTML5 help system to address issues with a client's traditional help system. The client's issues included time-consuming publishing, inconsistent branding, content duplication, and poor search results. The solution involved authoring content in DITA for reuse, applying consistent branding, publishing to PDF and an accessible HTML5 help system, and using a cloud-based CMS for storage and publishing. This reduced publishing time and costs while improving user experience and satisfaction through accessible, searchable help content.
The document is a presentation about book publishing challenges and strategies for addressing them. It discusses the challenges of expense reduction due to downward price pressure from online retailers and the rise of e-books. It proposes three key strategies: improving composition turnaround and quality with automated publishing tools, integrating XML early in the production process, and using cloud-based solutions. It then provides a case study of a publisher that implemented an automated cloud-based system, achieving faster proof turnaround, shorter production schedules, and automatic EPUB output.
The document announces a webinar hosted by Really Strategies, Inc. on applying content management systems (CMS) and semantic enrichment to transform book publishing. The webinar agenda includes presentations on semantic enrichment, a Wolters Kluwer Health case study, content management with RSuite CMS, and a question and answer session. Background information is provided on Really Strategies, Inc., a consulting firm for publishers, and the presenters, which include representatives from Silverchair and Wolters Kluwer Health.
Unica selected DocZone for authoring, managing, translating, and publishing DITA content. Unica used XML/DITA during content production and needed an efficient, scalable solution to facilitate productivity and adherence to these standards.
In this presentation, Mark Hoeber, Unica’s senior manager of technical documentation, illustrates the:
* business challenges that led Unica to select DocZone
* process that Unica followed to implement the DocZone DITA-based environment
* details of the first production run through with DocZone
* metrics that show the impact DocZone made to Unica's environment: increased content re-use, reduced localization costs, faster time-to-market, and higher productivity
The document is a presentation about choosing the right XML editor for publishers. It discusses various editing options for XML like using Word with conversion tools, InCopy/InDesign with conversion, browser-based editors, and native XML editors. The three main factors to consider are the users, the content type, and the business workflow. The best choices depend on these factors, such as using Word for external authors and native XML editors for regular internal content. The presentation provides tips on conversions, customizations, user testing, and support to help publishers implement the best XML editing solution.
Over the last year the lightweight DITA document types have been used to prototype content from a variety of different sources within IBM, including marketing, learning and training, technical articles, and internal policies/procedures. This presentation will introduce the lightweight DITA document types, demonstrate the feasibility of using a lightweight but still structured approach for integrating content across the enterprise content ecosystem, and show how lightweight DITA can be implemented using either XML or HTML5 as the base.
DITA is an OASIS standard for modular content that can be assembled and published in many different ways. The full DITA standard provides powerful features for single-sourcing and structured authoring but can be intimidating for new adopters who require only a subset of those features.
The OASIS DITA Technical Committee is planning to define a lightweight DITA architecture to allow a broader range of authoring and publishing tools to support a useful subset of the full DITA standard.
This presentation provides a preview of the lightweight DITA proposal for DITA 1.3, including some example markup and possible architectural approaches.
With so many publishing tools on the market how do you select what’s right for you? You know you need a content management system but do you also need a digital asset management system? XML is touted as the game changer to facilitate content re-use but what’s the best approach to create it? And at the end of the day, you still need to publish a physical product as well as an ebook, web content, mobile apps, and more.
This document discusses a case study of implementing a DITA-based HTML5 help system to address issues with a client's traditional help system. The client's issues included time-consuming publishing, inconsistent branding, content duplication, and poor search results. The solution involved authoring content in DITA for reuse, applying consistent branding, publishing to PDF and an accessible HTML5 help system, and using a cloud-based CMS for storage and publishing. This reduced publishing time and costs while improving user experience and satisfaction through accessible, searchable help content.
The document is a presentation about book publishing challenges and strategies for addressing them. It discusses the challenges of expense reduction due to downward price pressure from online retailers and the rise of e-books. It proposes three key strategies: improving composition turnaround and quality with automated publishing tools, integrating XML early in the production process, and using cloud-based solutions. It then provides a case study of a publisher that implemented an automated cloud-based system, achieving faster proof turnaround, shorter production schedules, and automatic EPUB output.
The document announces a webinar hosted by Really Strategies, Inc. on applying content management systems (CMS) and semantic enrichment to transform book publishing. The webinar agenda includes presentations on semantic enrichment, a Wolters Kluwer Health case study, content management with RSuite CMS, and a question and answer session. Background information is provided on Really Strategies, Inc., a consulting firm for publishers, and the presenters, which include representatives from Silverchair and Wolters Kluwer Health.
Unica selected DocZone for authoring, managing, translating, and publishing DITA content. Unica used XML/DITA during content production and needed an efficient, scalable solution to facilitate productivity and adherence to these standards.
In this presentation, Mark Hoeber, Unica’s senior manager of technical documentation, illustrates the:
* business challenges that led Unica to select DocZone
* process that Unica followed to implement the DocZone DITA-based environment
* details of the first production run through with DocZone
* metrics that show the impact DocZone made to Unica's environment: increased content re-use, reduced localization costs, faster time-to-market, and higher productivity
The document is a presentation about choosing the right XML editor for publishers. It discusses various editing options for XML like using Word with conversion tools, InCopy/InDesign with conversion, browser-based editors, and native XML editors. The three main factors to consider are the users, the content type, and the business workflow. The best choices depend on these factors, such as using Word for external authors and native XML editors for regular internal content. The presentation provides tips on conversions, customizations, user testing, and support to help publishers implement the best XML editing solution.
Over the last year the lightweight DITA document types have been used to prototype content from a variety of different sources within IBM, including marketing, learning and training, technical articles, and internal policies/procedures. This presentation will introduce the lightweight DITA document types, demonstrate the feasibility of using a lightweight but still structured approach for integrating content across the enterprise content ecosystem, and show how lightweight DITA can be implemented using either XML or HTML5 as the base.
DITA is an OASIS standard for modular content that can be assembled and published in many different ways. The full DITA standard provides powerful features for single-sourcing and structured authoring but can be intimidating for new adopters who require only a subset of those features.
The OASIS DITA Technical Committee is planning to define a lightweight DITA architecture to allow a broader range of authoring and publishing tools to support a useful subset of the full DITA standard.
This presentation provides a preview of the lightweight DITA proposal for DITA 1.3, including some example markup and possible architectural approaches.
Learn what DITA is and why you might need it to create documentation.
These are the slides from a presentation we gave at Write the Docs/PDX DITA joint meetup in December of 2014.
DITA Quick Start: System Architecture of a Basic DITA ToolsetSuite Solutions
Presenter: Joe Gelb, President, Suite Solutions
Abstract: In this webinar, you will learn about the software, integration and customization which enable you to effectively author, manage, localize, publish and share your DITA XML content. We will review how each tool fits into the content lifecycle and discuss options for an incremental DITA XML implementation using a basic toolset as the starting point.
While open-source solutions may have no purchase cost, total costs including configuration, customization and support can equal proprietary solutions. DITA provides benefits like reuse and translation but has limitations in areas like graphics, equations, custom output and legacy content migration. PDF publishing from DITA is especially challenging due to the complexity of XSL-FO. DITA works best for organizations with significant reuse across contexts and languages, while smaller groups may find its limitations easier to overcome.
Presented at the Content Management Strategies/DITA North America conference in 2016; this version is from a repeat of the presentation in webinar form, and includes some additional slides.
Lightweight DITA is being developed at OASIS by a subcommittee of the OASIS DITA Technical Committee. It is designed to make adoption of DITA easier for both users and tool developers. The subcommittee is looking at usage scenarios in areas such as marketing, education, software development, and machine industries.
The goals of the (in-development) specification are:
- simplified topic and map definitions with tighter content models and fewer elements
- simplified specialization process that makes new specializations as easy to create as new topics
- multi-format content, with mappings to not only XML, but also markdown, HTML5, and JSON
Michael Priestley shares the current state of the lightweight DITA specification, focusing on the current draft document types for topic and map, and reviews the lightweight specialization process.
Painless XML Authoring?: How DITA Simplifies XMLScott Abel
Presented at DocTrain East 2007 by Bob Doyle, DITA Users -- This introduction to XML Authoring will acquaint you with over fifty tools aimed at structuring content with DITA. They are not just DITA-compliant authoring tools (editors) for writers. They also include content management systems (CMS), translation management systems (TMS), and dynamic publishing engines that fully support DITA. You will also need to know about tools that convert legacy documents to DITA and help to design stylesheets for DITA deliverables. The best DITA tools for technical communicators implement the DITA standard while hiding all the complexity of the underlying XML (eXtensible Markup Language).
As a tech writer and not a tech, you should be able to forget about XML - except to know that you are using it (DITA is XML) and that it consists of named content elements (or components) with attributes. You need to know enough about the content elements so you can reference (conref) them for reuse. You need to know about their attributes so you can filter on them for conditional processing. And you should appreciate that because components are uniquely identifiable they lend themselves perfectly to automated dynamic assembly using a publishing engine.
We will describe how you can get started with structured writing without knowing XML or installing anything.
The promise of topic-based structured authoring is not simply better documentation. It is the creation of mission-critical information for your organization, written with a deep understanding of your most important audiences, that can be repurposed to multiple delivery channels and localized for multilingual global markets. You are not just writing content, you are preparing the information deliverables that enhance the value of your organization in all its markets.
To do that well, you must understand the latest tools in structured writing that are revolutionizing corporate information systems - today in documentation but tomorrow throughout the enterprise, from external marketing to internal human resources. Whether you are trying to push a new product into a new market or are “onboarding” a new employee, the need for high quality information to educate the customer or train the new salesperson is a challenge for technical communicators. You need to think outside the docs!
The key idea behind Darwin Information Typing Architecture is to create content in small chunks or modules called topics. A topic is the right size when it can stand alone as meaningful information. Topics are then assembled into documents using DITA maps, which are hierarchical lists of pointers or links to topics. The pointers are called “topicrefs” (for topic references).
Think of documents as assembled from single-source component parts. Assembly can be conditional, dependent on properties or metadata “tags” you attach to a topic. For example, the “audience” property might be “beginner” or “advanced.”
At a still finer level of granularity, individual elements of a topic can also be assigned property tags for conditional assembly. More importantly, a topic element can be assigned a unique ID that makes it a content component reusable in other topics.
As you will learn, DITA is a leading technology for “component content management,” which multiplies the value of your work. You need to leverage DITA and structured content to multiply your income.
An update to my previous lightweight DITA presentations with a focus on scenarios and business value.
Video of the presentation is available here: https://www.youtube.com/watch?v=B7NNYE-G6x0
For content to flow through an ecosystem, it needs to be standardized: structured, modular, classified, semantically meaningful. Lightweight DITA can be that standard, but only if it can transcend the limitations of formats—whether Word, HTML, Markdown, or even XML. We need capabilities available in the tools and environments that match authoring requirements and expectations, whether for technical communicators, software developers, or marketing authors.
In this presentation, Michael Priestley shows how the Lightweight DITA subcommittee is approaching the problem of open content standards for the enterprise content ecosystem, including a diverse range of tools, formats, and especially authoring roles.
Michael Priestley, a lead DITA architect at IBM, presented a preview of the proposed OASIS Lightweight DITA profile. Lightweight DITA is intended to provide a simplified version of DITA that reduces complexity to ease adoption. It would define a subset of DITA elements and features to serve as an entry point for new users. All information in the presentation is preliminary and examples are non-normative. Priestley discussed potential uses and interoperability with full DITA, and provided examples of simplified topic, map, and specialization structures in Lightweight DITA.
One of the key benefits of lightweight DITA is that it frees the value points of DITA from a strict dependency on the XML format. You can author valid lightweight DITA content in multiple formats, including markdown and HTML5.
These slides, developed by Michael Priestley, Jenifer Schlotfeldt, and Carlos Evia, accompanied a demonstration of how lightweight topics of various content types can be created in XML, markdown, and HTML5, while continuing to make use of standard DITA features such as content reuse and conditional processing and flowing into a common published deliverable, such as an HTML web site, PDF, or EPUB.
As the focus on content broadens to include the entire content usage lifecycle, we need to consider not just the needs of individual departments but the need for collaboration and coordination across the entire content management ecosystem, from marketing to support. The good news is that content requirements are converging around a set of core characteristics: modular, structured, semantically rich content that is findable, usable, and reusable across contexts and applications. For content to flow across organizational boundaries, it must be standardized. Does DITA have the answer?
Understanding Content Component ManagementScott Abel
Presented at DocTrain East 2007 Conference by Steve Manning, The Rockley Group -- Reuse has been (and continues to be) a best practice for the technical communications and training communities. Many companies are struggling with big translation localization expenses. DITA is the word most used when you ask about hot trends in the industry. What do the three preceding sentences have in common? Simple. Component-based content is part of the solution.
So what is component-based content management? Thats what this session aims to help you understand. You will learn what component content management is, what the benefits are, and how it is currently being applied in different organizations. You also learn how a content component approach can help you solve your content issues.
How important is component-based content creation and management? It has taken over from DITA as the most talked about subject in documentation. It is being used in many companies who have followed traditional methodologies for creating things like technical documentation, training materials, help systems and so on. But in the push to do things faster, cheaper, more flexibly, and for more people, companies are discovering that by moving to a component based approach, they can do things faster, cheaper and more flexibly.
Some of the advantages they are gaining are in automating the production of outputs—getting PDF for print, PDF for online display, and HTML—with a single push of a button. Or, they are getting flexible content, where reuse is a matter of reconfiguring a list of topics, rather than cutting and pasting chunks of content between large binary files. Or they are beginning to manage extreme time frames, where panic used to be the order of the day come release time, and make release time something that is not so likely to turn hair gray.
This session will describe content component management in detail and help you grasp the concepts needed to figure out if a move to component-based content can help you solve your content challenges.
Media, messaging and telecommunications convergence is now accepted as the norm. Convergence has resulted in greater consumer choice, lower costs and incredible innovation. It is important to note that even incumbent vendors in this space have much to gain from such convergence as it results in the potential to offer higher value services to customers, thus creating more revenue opportunities.
Enterprise IT has not yet seen convergence come home. We continue to create separation between BPM, SOA, EDA, WOA, SaaS, Cloud computing and more. Unlike the case of telecommunications convergence, however, in the enterprise IT world the incumbents are actually not incentivized to fuel convergence as they continue to "cash in" on old investments, slightly refreshed in some cases.
Fortunately, all hope is not lost! As open standards focused on interoperability become more pervasive, many traditional technological
boundaries are rapidly coming down and falling victim to convergence. Open source further accelerates the process by being the breeding grounds of untethered disruptive innovation resulting in simple, easy to use technologies which are made available freely, thus fueling rapid adoption.
In this talk I explore the growth of convergence in enterprise IT and the radical simplicity it is delivering to enterprise architects & developers.
DocBook vs. DITA: Will The Real Standard Please Stand Up?Scott Abel
Presented by Teresa Mulvihill at Documentation and Training West, May 6-9, 2008 Vancouver, BC
Over a decade ago DocBook became the standard for those forging ahead in XML publications. DocBook offered a cheaper and more efficient way to publish to multiple formats. Single-sourcing became a reality for hardware and software companies. However, in recent years, many in technical documentation publications have proclaimed the Darwin Information Typing Architecture (DITA) as standard for XML documentation. DITA offered an architecture in which to create and publish structured content. Makers of XML editors advertise seamless integration with DITA. Does this leave DocBook on the shelf? Are these two seemingly rival standards really that different? This presentation answers these questions with comparative examples, allowing the audience to decide for themselves.
Gone through articles and presentations on the web and got a half-baked understanding of the Darwin Information Typing Architecture (DITA)?
Refer to my DITA Quick Start presentation for the 2007 STC India Conference to learn to evaluate, plan and start implementing DITA.
In this presentation, you will learn about the following:
o Structured authoring and XML
o Key DITA concepts: topics, maps, specialization
o DITA architecture and content model
o Authoring in topics
o Organizing content using DITA maps
o Creating relationship tables
o Conditional text and reuse in DITA
o Metadata support in DITA
o DITA tools, standards and processes
o Publishing with the DITA Open Toolkit
Presented at DocTrain East 2007 by Joe Gelb, Suite Solutions -- Designing, building and maintaining a coherent information architecture is critical to proper planning, creation, management and delivery of documentation and training content. This is especially true when your content is based on a modular or topic-based model such as DITA and SCORM or if you are migrating to such a model.
But where to start? Terms such as taxonomy, semantics, and ontology can be intimidating, and recognized standards like RDF, OWL, Topic Maps (XTM) and SKOS seem so abstract. This pragmatic workshop will provide an overview of the standards and concepts, and a chance to use them hands-on to turn the abstract into tangible skills. We will demonstrate how a well-designed information architecture facilitates reuse and how the information model is integrally connected to conditional and multi-purpose publishing.
We will introduce an innovative, comprehensive methodology for information modeling and content development called SOTA Solution Oriented Topic Architecture. SOTA does not aim to be yet another new standard, but rather a concrete methodology backed up with open-source and accessible tools for using existing standards. We will demonstrate ֖and practice—hands-on—how this powerful methodology can help you organize and express information, determine which content actually needs to be created or updated, and build documentation and training deliverables from your content based on the rules you define.
This workshop is essential for successfully implementing topic models like DITA and SCORM, multi-purpose conditional publishing, and successfully facilitating content reuse.
This document summarizes the additions to DITA standards over multiple versions and discusses the complexity of the DITA standard and tagset. It notes that:
- DITA 1.1-1.3 added many new elements and features over time like bookmaps, keys, and specialized domains.
- However, smaller companies with non-technical writers may struggle to implement many new DITA 1.3 features that require specialized resources.
- The document proposes a "Standard DITA" subset for beginners and a "Advanced DITA" full feature set, arguing constraints do not truly simplify the standard. It notes DITA 2.0 aims to address accessibility and simplification
Building An XML Publishing System With DITAScott Abel
Presented at DocTrain East 2007 Conference by Brian Buehling, Dakota Systems -- Since its inception, DITA has rapidly gained acceptance as a standard document structure used in many XML-based content management and publishing systems. DITA is an XML schema developed primarily to support technical documentation for a wide array of applications. This session will cover the commonly used element, attribute and entity constructs that are defined in the schema. More importantly, recommendations concerning how best to implement DITA solutions will be given. Special attention is given to developing practical DITA applications since, in many cases, some DITA elements will have to be extended through a mechanism called specialization to produce a robust XML-based publishing system.
This document discusses a presentation given by Jessica Dearie and Donna Rodriguez comparing Drupal and SharePoint. Some key similarities between the platforms include requiring developer knowledge, strong support communities, and allowing for rapid website development. Major differences are in technology (Drupal uses PHP/MySQL while SharePoint uses ASP.NET/MS SQL) and intent (Drupal focuses more on public sites while SharePoint is for internal use). The presenters provide examples of how their organizations use both Drupal and SharePoint together.
Introduction to XML and Structured Authoring • Overview of DITA • Topics: The Basic Information Types • Maps: Assembling Topics into Deliverables • Common elements and attributes • Metadata • Examples and exercises
Enterprise Cloud Development and Agile Transformation Strategy - China 2012 Laszlo Szalvay
This is a seminar I gave throughout China the week of Oct 29th 2012. It covers the topics of Agile Software Development (Scrum, Lean, XP) and the new framework of Enterprise Cloud Development that CollabNet has been socializing. Please contact me for similar private talks at your company.
Publishers understand that content management is a pivotal piece in today's publishing environment. Yet budgeting for a CMS initiative can quickly scale to the point where executives question why they should stray from the status quo. In this free webinar, Barry Bealer, CEO of Really Strategies, will lead a panel of publishing professionals who will discuss how they made their business case and got executive buy-in for content management in their organizations.
Learn what DITA is and why you might need it to create documentation.
These are the slides from a presentation we gave at Write the Docs/PDX DITA joint meetup in December of 2014.
DITA Quick Start: System Architecture of a Basic DITA ToolsetSuite Solutions
Presenter: Joe Gelb, President, Suite Solutions
Abstract: In this webinar, you will learn about the software, integration and customization which enable you to effectively author, manage, localize, publish and share your DITA XML content. We will review how each tool fits into the content lifecycle and discuss options for an incremental DITA XML implementation using a basic toolset as the starting point.
While open-source solutions may have no purchase cost, total costs including configuration, customization and support can equal proprietary solutions. DITA provides benefits like reuse and translation but has limitations in areas like graphics, equations, custom output and legacy content migration. PDF publishing from DITA is especially challenging due to the complexity of XSL-FO. DITA works best for organizations with significant reuse across contexts and languages, while smaller groups may find its limitations easier to overcome.
Presented at the Content Management Strategies/DITA North America conference in 2016; this version is from a repeat of the presentation in webinar form, and includes some additional slides.
Lightweight DITA is being developed at OASIS by a subcommittee of the OASIS DITA Technical Committee. It is designed to make adoption of DITA easier for both users and tool developers. The subcommittee is looking at usage scenarios in areas such as marketing, education, software development, and machine industries.
The goals of the (in-development) specification are:
- simplified topic and map definitions with tighter content models and fewer elements
- simplified specialization process that makes new specializations as easy to create as new topics
- multi-format content, with mappings to not only XML, but also markdown, HTML5, and JSON
Michael Priestley shares the current state of the lightweight DITA specification, focusing on the current draft document types for topic and map, and reviews the lightweight specialization process.
Painless XML Authoring?: How DITA Simplifies XMLScott Abel
Presented at DocTrain East 2007 by Bob Doyle, DITA Users -- This introduction to XML Authoring will acquaint you with over fifty tools aimed at structuring content with DITA. They are not just DITA-compliant authoring tools (editors) for writers. They also include content management systems (CMS), translation management systems (TMS), and dynamic publishing engines that fully support DITA. You will also need to know about tools that convert legacy documents to DITA and help to design stylesheets for DITA deliverables. The best DITA tools for technical communicators implement the DITA standard while hiding all the complexity of the underlying XML (eXtensible Markup Language).
As a tech writer and not a tech, you should be able to forget about XML - except to know that you are using it (DITA is XML) and that it consists of named content elements (or components) with attributes. You need to know enough about the content elements so you can reference (conref) them for reuse. You need to know about their attributes so you can filter on them for conditional processing. And you should appreciate that because components are uniquely identifiable they lend themselves perfectly to automated dynamic assembly using a publishing engine.
We will describe how you can get started with structured writing without knowing XML or installing anything.
The promise of topic-based structured authoring is not simply better documentation. It is the creation of mission-critical information for your organization, written with a deep understanding of your most important audiences, that can be repurposed to multiple delivery channels and localized for multilingual global markets. You are not just writing content, you are preparing the information deliverables that enhance the value of your organization in all its markets.
To do that well, you must understand the latest tools in structured writing that are revolutionizing corporate information systems - today in documentation but tomorrow throughout the enterprise, from external marketing to internal human resources. Whether you are trying to push a new product into a new market or are “onboarding” a new employee, the need for high quality information to educate the customer or train the new salesperson is a challenge for technical communicators. You need to think outside the docs!
The key idea behind Darwin Information Typing Architecture is to create content in small chunks or modules called topics. A topic is the right size when it can stand alone as meaningful information. Topics are then assembled into documents using DITA maps, which are hierarchical lists of pointers or links to topics. The pointers are called “topicrefs” (for topic references).
Think of documents as assembled from single-source component parts. Assembly can be conditional, dependent on properties or metadata “tags” you attach to a topic. For example, the “audience” property might be “beginner” or “advanced.”
At a still finer level of granularity, individual elements of a topic can also be assigned property tags for conditional assembly. More importantly, a topic element can be assigned a unique ID that makes it a content component reusable in other topics.
As you will learn, DITA is a leading technology for “component content management,” which multiplies the value of your work. You need to leverage DITA and structured content to multiply your income.
An update to my previous lightweight DITA presentations with a focus on scenarios and business value.
Video of the presentation is available here: https://www.youtube.com/watch?v=B7NNYE-G6x0
For content to flow through an ecosystem, it needs to be standardized: structured, modular, classified, semantically meaningful. Lightweight DITA can be that standard, but only if it can transcend the limitations of formats—whether Word, HTML, Markdown, or even XML. We need capabilities available in the tools and environments that match authoring requirements and expectations, whether for technical communicators, software developers, or marketing authors.
In this presentation, Michael Priestley shows how the Lightweight DITA subcommittee is approaching the problem of open content standards for the enterprise content ecosystem, including a diverse range of tools, formats, and especially authoring roles.
Michael Priestley, a lead DITA architect at IBM, presented a preview of the proposed OASIS Lightweight DITA profile. Lightweight DITA is intended to provide a simplified version of DITA that reduces complexity to ease adoption. It would define a subset of DITA elements and features to serve as an entry point for new users. All information in the presentation is preliminary and examples are non-normative. Priestley discussed potential uses and interoperability with full DITA, and provided examples of simplified topic, map, and specialization structures in Lightweight DITA.
One of the key benefits of lightweight DITA is that it frees the value points of DITA from a strict dependency on the XML format. You can author valid lightweight DITA content in multiple formats, including markdown and HTML5.
These slides, developed by Michael Priestley, Jenifer Schlotfeldt, and Carlos Evia, accompanied a demonstration of how lightweight topics of various content types can be created in XML, markdown, and HTML5, while continuing to make use of standard DITA features such as content reuse and conditional processing and flowing into a common published deliverable, such as an HTML web site, PDF, or EPUB.
As the focus on content broadens to include the entire content usage lifecycle, we need to consider not just the needs of individual departments but the need for collaboration and coordination across the entire content management ecosystem, from marketing to support. The good news is that content requirements are converging around a set of core characteristics: modular, structured, semantically rich content that is findable, usable, and reusable across contexts and applications. For content to flow across organizational boundaries, it must be standardized. Does DITA have the answer?
Understanding Content Component ManagementScott Abel
Presented at DocTrain East 2007 Conference by Steve Manning, The Rockley Group -- Reuse has been (and continues to be) a best practice for the technical communications and training communities. Many companies are struggling with big translation localization expenses. DITA is the word most used when you ask about hot trends in the industry. What do the three preceding sentences have in common? Simple. Component-based content is part of the solution.
So what is component-based content management? Thats what this session aims to help you understand. You will learn what component content management is, what the benefits are, and how it is currently being applied in different organizations. You also learn how a content component approach can help you solve your content issues.
How important is component-based content creation and management? It has taken over from DITA as the most talked about subject in documentation. It is being used in many companies who have followed traditional methodologies for creating things like technical documentation, training materials, help systems and so on. But in the push to do things faster, cheaper, more flexibly, and for more people, companies are discovering that by moving to a component based approach, they can do things faster, cheaper and more flexibly.
Some of the advantages they are gaining are in automating the production of outputs—getting PDF for print, PDF for online display, and HTML—with a single push of a button. Or, they are getting flexible content, where reuse is a matter of reconfiguring a list of topics, rather than cutting and pasting chunks of content between large binary files. Or they are beginning to manage extreme time frames, where panic used to be the order of the day come release time, and make release time something that is not so likely to turn hair gray.
This session will describe content component management in detail and help you grasp the concepts needed to figure out if a move to component-based content can help you solve your content challenges.
Media, messaging and telecommunications convergence is now accepted as the norm. Convergence has resulted in greater consumer choice, lower costs and incredible innovation. It is important to note that even incumbent vendors in this space have much to gain from such convergence as it results in the potential to offer higher value services to customers, thus creating more revenue opportunities.
Enterprise IT has not yet seen convergence come home. We continue to create separation between BPM, SOA, EDA, WOA, SaaS, Cloud computing and more. Unlike the case of telecommunications convergence, however, in the enterprise IT world the incumbents are actually not incentivized to fuel convergence as they continue to "cash in" on old investments, slightly refreshed in some cases.
Fortunately, all hope is not lost! As open standards focused on interoperability become more pervasive, many traditional technological
boundaries are rapidly coming down and falling victim to convergence. Open source further accelerates the process by being the breeding grounds of untethered disruptive innovation resulting in simple, easy to use technologies which are made available freely, thus fueling rapid adoption.
In this talk I explore the growth of convergence in enterprise IT and the radical simplicity it is delivering to enterprise architects & developers.
DocBook vs. DITA: Will The Real Standard Please Stand Up?Scott Abel
Presented by Teresa Mulvihill at Documentation and Training West, May 6-9, 2008 Vancouver, BC
Over a decade ago DocBook became the standard for those forging ahead in XML publications. DocBook offered a cheaper and more efficient way to publish to multiple formats. Single-sourcing became a reality for hardware and software companies. However, in recent years, many in technical documentation publications have proclaimed the Darwin Information Typing Architecture (DITA) as standard for XML documentation. DITA offered an architecture in which to create and publish structured content. Makers of XML editors advertise seamless integration with DITA. Does this leave DocBook on the shelf? Are these two seemingly rival standards really that different? This presentation answers these questions with comparative examples, allowing the audience to decide for themselves.
Gone through articles and presentations on the web and got a half-baked understanding of the Darwin Information Typing Architecture (DITA)?
Refer to my DITA Quick Start presentation for the 2007 STC India Conference to learn to evaluate, plan and start implementing DITA.
In this presentation, you will learn about the following:
o Structured authoring and XML
o Key DITA concepts: topics, maps, specialization
o DITA architecture and content model
o Authoring in topics
o Organizing content using DITA maps
o Creating relationship tables
o Conditional text and reuse in DITA
o Metadata support in DITA
o DITA tools, standards and processes
o Publishing with the DITA Open Toolkit
Presented at DocTrain East 2007 by Joe Gelb, Suite Solutions -- Designing, building and maintaining a coherent information architecture is critical to proper planning, creation, management and delivery of documentation and training content. This is especially true when your content is based on a modular or topic-based model such as DITA and SCORM or if you are migrating to such a model.
But where to start? Terms such as taxonomy, semantics, and ontology can be intimidating, and recognized standards like RDF, OWL, Topic Maps (XTM) and SKOS seem so abstract. This pragmatic workshop will provide an overview of the standards and concepts, and a chance to use them hands-on to turn the abstract into tangible skills. We will demonstrate how a well-designed information architecture facilitates reuse and how the information model is integrally connected to conditional and multi-purpose publishing.
We will introduce an innovative, comprehensive methodology for information modeling and content development called SOTA Solution Oriented Topic Architecture. SOTA does not aim to be yet another new standard, but rather a concrete methodology backed up with open-source and accessible tools for using existing standards. We will demonstrate ֖and practice—hands-on—how this powerful methodology can help you organize and express information, determine which content actually needs to be created or updated, and build documentation and training deliverables from your content based on the rules you define.
This workshop is essential for successfully implementing topic models like DITA and SCORM, multi-purpose conditional publishing, and successfully facilitating content reuse.
This document summarizes the additions to DITA standards over multiple versions and discusses the complexity of the DITA standard and tagset. It notes that:
- DITA 1.1-1.3 added many new elements and features over time like bookmaps, keys, and specialized domains.
- However, smaller companies with non-technical writers may struggle to implement many new DITA 1.3 features that require specialized resources.
- The document proposes a "Standard DITA" subset for beginners and a "Advanced DITA" full feature set, arguing constraints do not truly simplify the standard. It notes DITA 2.0 aims to address accessibility and simplification
Building An XML Publishing System With DITAScott Abel
Presented at DocTrain East 2007 Conference by Brian Buehling, Dakota Systems -- Since its inception, DITA has rapidly gained acceptance as a standard document structure used in many XML-based content management and publishing systems. DITA is an XML schema developed primarily to support technical documentation for a wide array of applications. This session will cover the commonly used element, attribute and entity constructs that are defined in the schema. More importantly, recommendations concerning how best to implement DITA solutions will be given. Special attention is given to developing practical DITA applications since, in many cases, some DITA elements will have to be extended through a mechanism called specialization to produce a robust XML-based publishing system.
This document discusses a presentation given by Jessica Dearie and Donna Rodriguez comparing Drupal and SharePoint. Some key similarities between the platforms include requiring developer knowledge, strong support communities, and allowing for rapid website development. Major differences are in technology (Drupal uses PHP/MySQL while SharePoint uses ASP.NET/MS SQL) and intent (Drupal focuses more on public sites while SharePoint is for internal use). The presenters provide examples of how their organizations use both Drupal and SharePoint together.
Introduction to XML and Structured Authoring • Overview of DITA • Topics: The Basic Information Types • Maps: Assembling Topics into Deliverables • Common elements and attributes • Metadata • Examples and exercises
Enterprise Cloud Development and Agile Transformation Strategy - China 2012 Laszlo Szalvay
This is a seminar I gave throughout China the week of Oct 29th 2012. It covers the topics of Agile Software Development (Scrum, Lean, XP) and the new framework of Enterprise Cloud Development that CollabNet has been socializing. Please contact me for similar private talks at your company.
Publishers understand that content management is a pivotal piece in today's publishing environment. Yet budgeting for a CMS initiative can quickly scale to the point where executives question why they should stray from the status quo. In this free webinar, Barry Bealer, CEO of Really Strategies, will lead a panel of publishing professionals who will discuss how they made their business case and got executive buy-in for content management in their organizations.
Tagging Up - MMS and Taxonomy In SharePoint 2010Chris McNulty
This document discusses managed metadata and taxonomies in SharePoint 2010. It provides an overview of metadata, taxonomies, and folksonomies. It also describes how SharePoint 2010 supports centralized management of metadata through the managed metadata service and content type hubs, allowing for publishing of metadata across sites and farms. The document uses examples to illustrate how information architecture and taxonomy needs grow as organizations and content expand.
This document summarizes an article from the itSM Solutions DITY newsletter. The article discusses the relationship between ITIL and service-oriented architecture (SOA). It explains that ITIL provides best practices for delivering IT infrastructure as services, while SOA describes an architectural approach using loosely coupled software services. The article argues that ITIL provides the processes to implement and support an infrastructure aligned with SOA principles.
BIRT is an open source Eclipse project for business intelligence and reporting. It was created by Actuate in 2004 to provide a free reporting tool with a graphical report designer. BIRT has seen over 6.5 million downloads and has a large community of developers contributing to its growth. It provides powerful and flexible reporting with a variety of charts, cross tabs, and output formats.
Focus is on understanding Information Professionals and how they connect with solution providers.
This was presented at the Document Management Solution Providers Executive Forum (http://www.aiim.org/dmspef).
Moodle is an open-source learning management system used by over 45,000 sites in 210 countries. Moodle 2.0 will include major rewriting of core systems like database handling and file storage. It will also introduce many new features to improve usability, pedagogy, integration with other systems, and control/administration. These changes are driven by requests from Moodle's large global user community.
The document discusses the relationship between ITIL and Service Oriented Architecture (SOA). ITIL provides best practices for delivering IT infrastructure as a set of services, known as IT Service Management (ITSM). SOA deals with designing software architecture using loosely coupled services. While SOA does not specify an implementation framework, many of its concepts can be traced back to principles of reuse from earlier programming approaches. ITSM provides the necessary guidance for an IT organization to plan, design, develop, deploy and support business-aligned IT services, including the infrastructure and guidance needed to realize an SOA.
1) The document discusses WordLift, a startup that provides tools to help with content findability, discovery, and SEO.
2) It describes WordLift's products and services, including content analysis, enrichment, and semantic tagging to help search engines understand content.
3) It presents WordLift 2.0, which aims to take WordPress navigation to a new level by providing a more structured content architecture and semantic-driven user interface to help users better engage with and discover content.
Oracle has been working hard for several years in building Oracle Fusion Applications which are slated to be released sometime during 2010. In this session, you will learn basic concepts of Fusion Applications, User Experience/UI Shell, features and functionality of Applciations. Present information about the Oracle Fusion Applications Present key concepts and ideas behind Fusion Applications Discuss the key technologies used by Oracle for Fusion Applications
The document discusses how information governance can be used to create more adaptable organizations. It states that disruptive businesses often use information in new ways and have more integrated information. The "small worlds" measure of information connectivity can be applied through information governance to test new business models.
Controlling the Complexity of Content LifecyclesZia Consulting
The document discusses how Zia Consulting brings together oXygen, Componize, and Alfresco to provide structured authoring and component content management. It outlines the benefits such as consistency, reuse, lower costs for publishing, updating and translating content. Key benefits of the solution include navigating information quickly, promoting consistency, easy content reuse, and reducing production time and costs through automation.
Deloitte is considering applying for its own generic top-level domain (gTLD), .Deloitte, to increase its brand visibility and better connect with clients. It has evolved its website, Deloitte.com, into a global platform but sees an opportunity to reinforce its brand positioning with a dedicated TLD. Deloitte will need to conduct an internal review of the business, technical, financial and operational aspects before submitting an application to ICANN, which is targeting the first new gTLDs to be added to the root zone in 2010. MarkMonitor recommends companies establish cross-functional teams to evaluate new gTLD opportunities and risks and leverage industry experts to assist with strategic planning and
The document discusses techniques for getting projects approved when budgets are limited. It outlines an agenda for presenting a business case for implementing a dynamic publishing system using XML. The presentation would cover what such a system is, justifying it through cost savings and revenue opportunities, addressing potential resistance from stakeholders, and driving action through a phased approach and training. It cautions against common errors in calculating return on investment.
Content is King - ECM in SharePoint 2010 - SharePoint Saturday DenverChris McNulty
The document discusses enterprise content management (ECM) features in SharePoint 2010. It provides an overview of managed metadata and how it can be used to classify and organize content. Key ECM capabilities covered include versioning and approvals, content routing with drop-off libraries and content organizers, records management both in-place and with records centers, document holds, disposition and information lifecycle management. The presenter emphasizes how these tools help users effectively aggregate, organize and manage large volumes of content and documents.
The document discusses IMS specifications and standards for interoperability, focusing on the QTI specification. It provides an overview of IMS, its member organizations, and its role in developing specifications to foster interoperability between learning systems. It then describes the QTI specification in particular, explaining that it defines an XML format for representing questions and tests to allow interchange between different computer systems. It notes some of the benefits of specifications like QTI and points the reader to the IMS website for more information on the QTI specification.
This document discusses enterprise microblogging and how to implement it in companies. It provides an overview of microblogging use cases for sharing information, asking and answering questions, and status updates. It then outlines a 7 step process for a successful implementation, including defining topics, gaining initial experience, establishing rules, integrating the tool into existing structures, expanding usage, and growing the number of participants and topics over time. The goal is to increase productivity and transparent communication through a traceable and collaborative process.
The document provides an overview of a webinar on achieving true collaboration with SharePoint. It discusses SharePoint introduction, user experience, collaboration capabilities, a NetApp case study, an Infogain SharePoint QuickStart, and a review and Q&A segment. The presentation covers how SharePoint can help unify the enterprise by providing content management, search, communities, and collaboration features to improve processes. It also discusses best practices for designing, managing, and sustaining a SharePoint implementation.
This presentation addresses how some of the challenges that have historically confronted implementers of markup technologies (SGML and XML) and how DITA, together with some of the usability innovations associated with Web 2.0, can be used to address them. Presented at Content Convergence and Integration in Vancouver (12 March 2008).
Similar to DITA For Publishers: How Publishers Can Really Do XML (20)
High performance Serverless Java on AWS- GoTo Amsterdam 2024Vadym Kazulkin
Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...Fwdays
Direct losses from downtime in 1 minute = $5-$10 thousand dollars. Reputation is priceless.
As part of the talk, we will consider the architectural strategies necessary for the development of highly loaded fintech solutions. We will focus on using queues and streaming to efficiently work and manage large amounts of data in real-time and to minimize latency.
We will focus special attention on the architectural patterns used in the design of the fintech system, microservices and event-driven architecture, which ensure scalability, fault tolerance, and consistency of the entire system.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
inQuba Webinar Mastering Customer Journey Management with Dr Graham HillLizaNolte
HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable.
In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed:
Key Takeaways:
Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement.
Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers.
Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Session 1 - Intro to Robotic Process Automation.pdfUiPathCommunity
👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program:
https://bit.ly/Automation_Student_Kickstart
In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC.
📕 Detailed agenda:
What is RPA? Benefits of RPA?
RPA Applications
The UiPath End-to-End Automation Platform
UiPath Studio CE Installation and Setup
💻 Extra training through UiPath Academy:
Introduction to Automation
UiPath Business Automation Platform
Explore automation development with UiPath Studio
👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.